see proposal on
TWiki:Codev.LocalizationFramework
Dakar needs at least two languages; German and English are the obvious choices, since we already have English
Need a way to get at the accept-language and accept-charset set by the browser.
Added the HTTP and HTTPS TWikiVariables to deal with this.
The language your browser says you are using is
SVN 6242
CC
TWiki:Main.AntonioTerceiro has proposed switching to POT files, which sounds pretty sensible to me. This doesn't invalidate what has been done to date, as existing translated content should be easy to transfer across.
CC
Updating this as everyone seems to agree on using PO files instead of per language templates.
AT
SVN:6415 contains my first stab at a spanish translation --
WN
SVN:6457 - german
Small glossary:
- dialect
- sublanguage, specific to a country/region/etc. Examples: pt-br, de-de, en-us, ect
- parent language
- 'mother' generic language. Examples: pt, de, en.
Language detection doesn't give you a dialect if you have configured the browser
to use the parent language (although it gives you the parent language if you specify
the dialect). This makes sense, since in some cases one who speaks the mother languages
could not understand the dialect (extreme cases), but we can expect that the
dialect-speakers would understand the mother language.
I propose we provide
pt instead of
pt-br,
de instead of
de-de. We should keep
it this way until we have enough help to actually mantain language variants' trasnlations.
AT
why? there's nothing wrong with distributing
pt_BR
and
es_MX
if that's all we have. we can distribute the "mother tongue" versions when someone actually contributes those versions.
now, is the problem that if we have multiple dialects, eg,
es_MX
and
es_VZ
and someone has their browser set to
es
, which one to serve?
WN
now, is the problem that if we have multiple dialects, eg, es_MX
and es_VZ
and someone has their browser set to es
, which one to serve?
That's the problem: if the browser is set to
es
, it won't choose
es_MX
nor
es_VZ
. Because detection
does not consider the "mother tongue" as as option.
That's because I think that distributing only
es
would be best. What I think is: if you are going to be only
es*
translators, let your work to be considered
es
. Unless we have people working on both a
es
and a
es_COUNTRY
, we should provide, IMO,
es
.
AT
Agreed. Is this as simple as renaming pt_BR to pt, es_MX to es, etc? If so, please do it!
CC
SVN:6673
WN