From: Karsten D. <k.d...@tu...> - 2001-11-30 15:07:42
|
On Fri, Nov 30, 2001 at 09:40:27AM -0500, Brian W. Brown wrote: > > Ah, about the language system: yes, it may generally > > cause a performance slowdown... this > > could be considered by some people a right price to pay > > to have runtime per-user localization. > > Obviously, the current language system could use some > improvement. I do, however, very much like a package-time > translation system. A few thoughts: [...] > o I have never understood the need for runtime translation (if > someone wants to explain, please do). What good is the ability > to display, say the text "Main Menu" in many different > languages when all of your content is locked-in to the > language in which it was written? I agree. This would in no way be of any help. But I would love to see even that: multi language content. As soon as the "core language" can be set during run time, it (would|should) be relatively easy to add a "lang" field to e.g. the article database to distinguish between different version of one article (one would have to connect those, etc., but you get the point). And voila - a multi language capable CMS. Which is not too useful for a university setting (you might argue), unless you consider students from foreign countries (who, again, should speak the language of their university's country, ok :-). But we were asked to set up phpWS for a school here in Germany, and they want to have the thing multi-language (that might rule out phpWS, although this would be sad) because this is a german-italian school. Or think about international partnerships between whatever you can imagine... Thoughts? Regards, Karsten -- Why do we have to hide from the police, daddy? Because we use emacs, son. They use vi. ----------------------------- mailto:k.d...@tu... w³: http://www.k-fish.de/ gpg: http://www.k-fish.de/mykeys.gpg |