i18n - leveraging analogs i18n support
This section describes how Timian makes use of existing analog i18n, of course subject to the
analog licensing terms.
summary
When Timian is built, analogs various language files are converted to UTF-8 and XML. This is of little interest to the
casual Timian user, but if you worked on or provided some of analogs existing i18n support, or if you are interested
in contributing to Timians support, you will probably find this information useful.
analogs language files
Analog uses 3 separate files per language:
| General language file | *.lng |
| Top Level Domain names | *dom.tab |
| Report descriptions | *desc.txt |
| Filetype descriptions | [a TYPEALIAS direcotive] |
Analog may have some of these in 2 or more versions, depending on the characterset used, or in some cases
on the actual translations. Also, not all languages have a descriptions, a domain-name file or a filetypes file, and simply use
the english original texts instead.
The analog scheme for naming language files is based on country rather than language. The language files
are all prefixed by a 2-character code, which ...[tbc]
timians language file
Timian uses a single XML-formatted file per combination of language and territory. Each of these files is
built based on 5 other files:
| Contents | Filename | |
| General information | timian-<cc>_<TT>.xml | Manually maintained |
| Descriptions | descriptions-xx.xml | The analog report descriptions are automatically converted from analogs "*desc.txt" files. |
| TLD names | domains-xx.xml | The Top level Domain names are automatically converted from analogs "*dom.tab" files. |
| analog strings | analogstrings-xx.xml | The general language strings are automatically converted from analogs "*.lng" files. |
| file types | filetypes-xx.xml | Manually maintained. |
analog and Timian?
For now analogs and Timians i18n work will continue to coexist, and Timian will continue to benefit from work done in analog.
Propagating work forward requires only minimal effort, and for the time being I intend to keep up with future analog release at
a reasonable pace.
maintaining consistency?
If you currently maintain language/i18n catalogues for analog, I suggest you continue to do so, unless you were to decide to
switch completely to Timian for report formatting. My intention is, as said above, to propagate i18n efforts from
analog to Timian, and I aim to do so for a while. Analogs release-frequency is low enough for me to do this with
a minimum of effort.
Depending on the take up of Timian, I have not yet set a "cut-off' point where updates to analogs i18n catalogues
will no longer be propagated to Timian, but it is likely to happen at some point in the near future.
In particular, when I see major c
|
Last time this page was updated:
Friday 9 May 2003 21:01
|
|
|