From: Eloi G. <el...@re...> - 2004-07-12 22:35:17
|
> I'd guess that what is being alluded to is that if the user has > selected 'French' then if there are translations of announcements into > French then these are presented instead of the English in the front > page list and as full announcements. If no translation matching the > users language is available then the default language version is > presented. It would have to be simpler than that. I the user selects 'French' and there's no French version of that announcement, they don't see anything. Once you start adding 'default language' abilities, every module serving information on any specific page would have to track down default & alternate versions of whatever content they're displaying. I'm sure it can be done efficiently with some fancy SQL coding, but because phpws is intended to work across all db backends, this extra feature would come at a cost of either extra db usage or extra memory usage. > I don't think it needs anything added that's not there already and the > use of PO files is incidental to the translation and presentation of > dynamic content. You just need someone to step up and create a > multi-language capable version of the announce module that pays > attention to the language setting. > You're right. All the Language module has to do is keep a flag in memory indicating what language is being used. Everything else is up to the module. PHPWS_Dynamic can be retired. I'm researching version control features right now, but I can *probably* pop in multi-language capability if we can agree on a non-resource intensive method. |