On Sat, Nov 3, 2012 at 4:54 AM, Andrea Pescetti <[email protected]> wrote: > On 02/11/2012 jan iversen wrote: > >> On 2 November 2012 22:43, Andrea Pescetti wrote: >>> >>> * "We have en-GB, en-ZA but no en-US[ and no].". What does this mean? >>> Simply that we don't have a BugZilla subcomponent under "l10n" for en-US >>> strings? >> >> What I meant is that we have translation to en-GB and en-ZA but there are >> no translation to en-US, that is quite puzzling to me > > > Ok, got it. "en" (or en-US) is the interface language. There are no > translations to en-US since en-US is the original. en-GB is a translation. > So the original (en-US) would say "color", the en-GB translation would say > "colour" and so on. > > Note that this has an impact on l10n: when an English ("original") string is > spelled wrong, all translations must be synchronized after it is corrected. >
In particular note that the en-US "original" strings are authored by an international team, not all native English, speakers and some of whom might have studied British English. So it is always possible for there to be errors or inconsistencies in the en-US text. And even a native speaker can make spelling errors. So from a translation quality perspective I wonder if we want to treat it the same as the translations? > >> I did not manage to download all da files as a zip file, but I might have >> overseen something. If we can download all files for a language that is >> ok. > > > Yes, it is just our configuration. So you don't see it in our current > instance but it's supported by Pootle. > > >> I for sure hope that we can get all the discussion settled before I get >> too >> deep into the development > > > Yes, at least let's make sure that before each development phase we leave > time to others to express their opinion. > > Regards, > Andrea.
