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.
The structure of locales in kivitendo is:
kivitendo/locale/<langcode>/
where <langcode> stands for an abbreviation of the + version is usable too.
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
@@ -71,13 +72,13 @@ filenames The last of which is very machine dependant. Remember that
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. This subdir and file is not a part of the language package
- itself. If the directory more exists and contains a file called all
- it will be parsed in addition to the mandatory all (see above).
- The file is useful if you want to change some translations for
- the current installation without conflicting further upgrades.
- The file is not autogenerated and has the same format as the all,
- but needs another key (more_texts). See the german translation
- for an example or copy the following code:
+ itself. If the directory more exists and contains a file called
+ all it will be parsed in addition to the mandatory all (see
+ above). The file is useful if you want to change some
+ translations for the current installation without conflicting
+ further upgrades. The file is not autogenerated and has the same
+ format as the all, but needs another key (more_texts). See the
+ german translation for an example or copy the following code:
-
#!/usr/bin/perl
# -*- coding: utf-8; -*-
@@ -96,5 +97,4 @@ $self->{more_texts} = {
'Shipping Point' => 'Delivery time',
}