One of the more interesting aspects of having lived in NYC and Washington D.C. is that I’m used to hearing many accents from new Americans from all over the World; including many who attend my church.
With the recent surge in the Hispanic population in our area, and with a Korean Church that leases space from my church, I’ve often thought it might be useful to offer the Redland Baptist website in many colors and flavors that bless our geographic region. In other words, or actually in terms of the Internet, we’re talking Localization and Internationalization – something I suppose I ought to explore when I upgrade the Redland site to MovableType 3.1.
But what about those of you who don’t use MovableType, especially those of you rolling your own content ‘manglement’ solutions for church or charity website?
How it works
Whether you use someone else’s system or your own to publish your church’s website, it doesn’t hurt to know how it works. Which is why I’d like to direct your attention to a set of articles by Karl Seguin entitled:
While Mr. Seguin discusses Internationalization from a .NET perspective, how he goes about using this programming tool can and should be applied to any just about any architecture I can think of. Here are just a few quick reasons why:
- He inherits and overrides the ‘Resource Manager’ to dynamically feed upon XML files so you don’t have to compile the site every time you add or change a language.
- Content is further separated from formatting and processing.
- He eliminates the need for multiple pages using an Apache/Mod_Rewrite like technique.
- The door is thrown wide-open to offer localization functionality into a web service.
- He drives the site using meta-data that is data that describes the data; only he goes the extra step to make sure it is well normalized.
- Placeholders, or what we in blogging refer to as templates, allow for programmatic changes to what is (dynamically) display.
If nothing else, how to set up the database and the how to run a re-direct on an IIS server is worth the bandwidth.
So is your site bi-lingual? If so, how do you go about getting it done? Have you ever developed a multilingual solution? If so, how did your approach differ from that of Mr. Seguin? Inquiring minds want to know – so leave a comment.