index : pacman | |
Archlinux32 fork of pacman | gitolite user |
summaryrefslogtreecommitdiff |
author | Dan McGee <dan@archlinux.org> | 2007-03-07 16:57:22 +0000 |
---|---|---|
committer | Dan McGee <dan@archlinux.org> | 2007-03-07 16:57:22 +0000 |
commit | 4268eda3a6a52ccfbcdd5d339e8b755fc05fdbc7 (patch) | |
tree | 87b04a2c37fcb7e13447af368c6d3cb058b6aeb3 /translation-help | |
parent | fd312c35eb44cd505f81b066a050d8cfe4beebc8 (diff) |
-rw-r--r-- | translation-help | 10 |
diff --git a/translation-help b/translation-help index 7c8e20dc..1a092ea3 100644 --- a/translation-help +++ b/translation-help @@ -43,13 +43,21 @@ following command, substituting 'libalpm.pot' or 'pacman.pot' depending on which directory you are currently working in: msginit -l <lang code> -o <lang code>.po -i <potfile> +You can then also add your language code to the end of the LINGUAS file located +in each po directory. + Look at the current message files for more guidance if necessary. Once you create the new language file, you may need to slightly modify the headers; try to make them look similar to the other .po file headers. In addition, for all new translations we would strongly recommend using UTF-8 encoding. +Finally, submitting your translations in patch form is not essential for new +languages, but highly recommended for future updates to the translations. + Some other notes: -msgid and msgstr 'variables' can be on as many lines as necessary. Line breaks are ignored- if you need a literal line break, use an '\n' in your string. The following two translations are equivalent: +msgid and msgstr 'variables' can be on as many lines as necessary. Line breaks +are ignored- if you need a literal line break, use an '\n' in your string. The +following two translations are equivalent: msgstr "This is a test translation" |