Dieser Abschnitt ist in Englisch geschrieben, um
internationalen Ãbersetzern die Arbeit zu erleichtern.
This section describes how localization packages in kivitendo
are built. Currently the only language fully supported is German, and
since most of the internal messages are held in English the English
version is usable too.
A stub version of French is included but not functunal at this
- point.
4.4.2. File structure
The structure of locales in kivitendo is:
kivitendo/locale/<langcode>/
where <langcode> stands for an abbreviation of the
+ point.
4.4.2. Character set
All files included in a language pack must use UTF-8 as their encoding.
4.4.3. File structure
The structure of locales in kivitendo is:
kivitendo/locale/<langcode>/
where <langcode> stands for an abbreviation of the
language package. The builtin packages use two letter ISO 639-1 codes,
but the actual name is not relevant for the program and can easily be
extended to IETF language
@@ -14,14 +14,7 @@
recognized:
LANGUAGE
This file is mandatory.
The LANGUAGE file contains the self
descripted name of the language. It should contain a native
representation first, and in parenthesis an english translation
- after that. Example:
Deutsch (German)
charset
This file should be present.
The charset file describes which
- charset a language package is written in and applies to all
- other language files in the package. It is possible to write
- some language packages without an explicit charset, but it is
- still strongly recommended. You'll never know in what
- environment your language package will be used, and neither
- UTF-8 nor Latin1 are guaranteed.
The whole content of this file is a string that can be
- recognized as a valid charset encoding. Example:
UTF-8
all
This file is mandatory.
The central translation file. It is essentially an inline
+ after that. Example:
Deutsch (German)
all
This file is mandatory.
The central translation file. It is essentially an inline
Perl script autogenerated by locales.pl. To
generate it, generate the directory and the two files mentioned
above, and execute the following command:
scripts/locales.pl <langcode>
Otherwise you can simply copy one of the other languages.
@@ -78,4 +71,4 @@ filenames
The last of which is very machine dependant. Remember that
case you made a typo, so that you don't have to translate
everything again. If a tranlsation is missing, the lost file is
checked first. If you maintain a language package, you might
- want to keep this safe somewhere.
\ No newline at end of file
+ want to keep this safe somewhere.
![[Anmerkung]](../../../../system/docbook-xsl/images/note.png)
![[Anmerkung]](system/docbook-xsl/images/note.png)