14
Quote:
Mamba wrote:
That's we we are leaving to the experts to decide how they want to have it
Ok: Portuguese is a language. "Brazilian Portuguese" and "Portuguese from Portugal" are DIALECTS, not languages. The same to "US English" and "European English".
Good example: In Blogger, anyone can see the options "Portuguese" (neutral), "Brazilian Portuguese", and "Portuguese from Portugal" Because Blogger can support many dialects.
Will be great in the "perfect world" a XOOPS Language folder for each country or city, but is impossible. Too much work for too many modules.
Scripts like WordPress can support dialects because they are just small scripts (used as XOOPS module, for example) supported by a by BIG community. XOOPS Community is BIG, but not to translate all modules to all dialects.
What I mean is: XOOPS is not a "Stand Alone Web Application", is modular. Is "ok" to translate the XOOPS Core to dialects but is impossible and UNNECESSARY to translate ALL XOOPS modules to dialects. This is the point.
Is really necessary to translate internal modules like the System or AltSys to EN-UK? The same question is valid to Portuguese BR and Portuguese PT.Ah, and actually, the XOOPS Portugal support is inactive.
My 20 Euros.