Revision dbda14c2
Von Moritz Bunkus vor fast 12 Jahren hinzugefügt
| doc/html/ch04s04.html | ||
|---|---|---|
|
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.</p><p>A stub version of French is included but not functunal at this
|
||
|
point.</p></div><div class="sect2" title="4.4.2. File structure"><div class="titlepage"><div><div><h3 class="title"><a name="translations-languages.file-structure"></a>4.4.2. File structure</h3></div></div></div><p>The structure of locales in kivitendo is:</p><pre class="programlisting">kivitendo/locale/<langcode>/</pre><p>where <langcode> stands for an abbreviation of the
|
||
|
point.</p></div><div class="sect2" title="4.4.2. Character set"><div class="titlepage"><div><div><h3 class="title"><a name="translations-languages.character-set"></a>4.4.2. Character set</h3></div></div></div><p>All files included in a language pack must use UTF-8 as their encoding.</p></div><div class="sect2" title="4.4.3. File structure"><div class="titlepage"><div><div><h3 class="title"><a name="translations-languages.file-structure"></a>4.4.3. File structure</h3></div></div></div><p>The structure of locales in kivitendo is:</p><pre class="programlisting">kivitendo/locale/<langcode>/</pre><p>where <langcode> stands for an abbreviation of the
|
||
|
language package. The builtin packages use two letter <a class="ulink" href="http://en.wikipedia.org/wiki/ISO_639-1" target="_top">ISO 639-1</a> codes,
|
||
|
but the actual name is not relevant for the program and can easily be
|
||
|
extended to <a class="ulink" href="http://en.wikipedia.org/wiki/IETF_language_tag" target="_top">IETF language
|
||
| ... | ... | |
|
recognized:</p><div class="variablelist"><dl><dt><span class="term">LANGUAGE</span></dt><dd><p>This file is mandatory.</p><p>The <code class="filename">LANGUAGE</code> 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:</p><pre class="programlisting">Deutsch (German)</pre></dd><dt><span class="term">charset</span></dt><dd><p>This file should be present.</p><p>The <code class="filename">charset</code> 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.</p><p>The whole content of this file is a string that can be
|
||
|
recognized as a valid charset encoding. Example:</p><pre class="programlisting">UTF-8</pre></dd><dt><span class="term">all</span></dt><dd><p>This file is mandatory.</p><p>The central translation file. It is essentially an inline
|
||
|
after that. Example:</p><pre class="programlisting">Deutsch (German)</pre></dd><dt><span class="term">all</span></dt><dd><p>This file is mandatory.</p><p>The central translation file. It is essentially an inline
|
||
|
Perl script autogenerated by <span class="command"><strong>locales.pl</strong></span>. To
|
||
|
generate it, generate the directory and the two files mentioned
|
||
|
above, and execute the following command:</p><pre class="programlisting">scripts/locales.pl <langcode></pre><p>Otherwise you can simply copy one of the other languages.
|
||
Auch abrufbar als: Unified diff
Unterstützung für andere Datenbankencodings als Unicode/UTF-8 entfernt