[Sputnik-list] Translation table format

[Dado Sutter]

Hello again :)

On 7/6/07, Yuri Takhteyev <yuri at sims.berkeley.edu> wrote:
>
> Well, under the approach that I described, it only makes sense to have
> pt_BR when we have alternative strings for pt_BR and pt_PT.  Until
> then, it should all be labeled as "pt".


   OK, I'll keep it under pt =... for now.

   The proposed fallback scheme is interesting but I'm afraid it can be
somewhat dificult for the locale peopleware :)
   Maybe we could keep the simpler (and also verbose) pt_BR = ..., pt_PT=
...., en_EN=  ...., en_GB = ...., even if we have lot's of redundant terms
(pt_BR = "Entrar", pt_PT = "Entrar", .....).
   This would make people concentrate only in ther locale key entries and
not bother with anything else.
   After all, we don't expect to have tons of dialects handled for a single
site, do we ?

   But yes, it's important to let the locale scheme right from the start so
the best thing to do is to wait a bit for some other opinions.
   My suggestion in the moment is that we keep every (used) key in every
table, like:

LOGIN = {
  en_US = "Login",
  pt_BR = "Entrar",
  ...
}

   ... and a simple config like:

LANGUAGE = pt_BR

   Missing entries would generate errors and force translators to complete
the job. Not sure if it's the best choice though.
   Even dealing with some redundance, it seems to be easier for
non-programmers to help with the translations.


Dado
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.luaforge.net/pipermail/sputnik-list/attachments/20070706/7fadc4c6/attachment.htm