“Nigel Vickers” nigel@v-and-b.de escribió:
Hallo David,
That depends on which side of the Atlantic you were born…
Certainly, and it can be solved, but surely in time we would find the same
issue over and over again.
The solution would be to have more than one “en-*” (surely “en-gb” and
"en-us") set of lang files. This looks nice, but has a terrible problem: is
it possible to maintain properly one (or all) of them? I don’t know the
answer to this question (or maybe sadly I think I do).
Most developers are german, but even so, I don’t feel capable to predict the
english flavour they (will/want to) use (taking they all always “stick” to
one). I’m not even sure of the flavour I use myself 
(taking that I always
stick to one).
Taking that the exposed human part finds a successfull answer and solution,
there’s the initial work to achieve this. I could do it, but I at least
would need:
- Agreement of at least core team and main developers to choose and
maintain one main flavour
- Compromise from assigned translator(s)
- Time to implement in trunk and even a deadline
I might be forgetting something, but I think these are the minimal points
for a debate.
Please everybody take that this is an special case. When I started
translating spanish, and because of previous experiences, I quickly renamed
"es" to “es-es”, and there are two portuguese flavours, “pt-pt” (Portugal)
and “pt-br” (Brazil), together with chinese (zh) cases. It’s not a bad time
if someone wants to extend another language for another existing flavour.
Regards.
David C. Rankin schrieb:
Ralf, all,
In emailadmin when you edit an account, the "Organization" group
is
misspelled as “Organisation”
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft® Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
eGroupWare-developers mailing list
eGroupWare-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/egroupware-developers
