Filip Miletic wrote:

Axel Hecht wrote:

Well, even -RS is subject to politics, so let's just use 'sr' and you can blame the Germans (me) for messing that up yet another time ;-)

Ok, 'sr' it is.

You're not actually checking out anymore, but creating your locale over and over. You only want to do that once. After that, you should only have to check out en-US until you actually have your locale in CVS.

Thanks for the instructions. But of course, having done that I started the automatic question generator (sorry:) so I'll be reverting often. Is there a checklist of things that need to be done to complete the localization? Apart from the obvious that is, which is translating the properties, the dtds and whatnot.

Yes, for the not-so-easy stuff, the best document today is  http://wiki.mozilla.org/Firefox2/L10n_Requirements. There are a bunch of common pitfalls,  http://developer.mozilla.org/en/docs/Encodings_for_localization_files talks about encodings and friends. And you want to be careful about translating CSS lengths as well as values like "true", "false" etc. Those may actually be values in a set of english words.

Finally, some questions from your friendly automatic question generator: - What language label should I put for MOZ_LANG_TITLE: Serbian, or Српски?

Good questions, other localizers may know better ad-hoc.

- Should I change ab-CD tags throughout to sr-RS?

No, just "sr", unless it is @ab-CD@ or so (the two @ being key), then it is just a variable which is going to be replaced by the build system.

- How can I find a fairly complete locale to learn from an example? (I suppose bonsai is the answer, but I'd be grateful to get a pointer to a well-done locale so that I don't drift around too much.)

 http://lxr.mozilla.org/l10n-mozilla1.8/source, pick your favorite.

Axel