Send patches - preferably formatted by git format-patch - to patches at archlinux32 dot org.
summaryrefslogtreecommitdiff
path: root/translation-help
diff options
context:
space:
mode:
authorDan McGee <dan@archlinux.org>2007-02-16 22:04:23 +0000
committerDan McGee <dan@archlinux.org>2007-02-16 22:04:23 +0000
commitc40c2e1137f92d11d3aa62341c892c0c0ba6eb9a (patch)
treedc5d87f1969480468ce32e03987a53e02f742868 /translation-help
parent0ca178fcd52e81cc6665322d80dab1c55b75abd1 (diff)
* Updated German translation
Pierre Schmitz <pierre@archlinux.de> * Added a blurb to 'translation-help' about wrapped messages in po files
Diffstat (limited to 'translation-help')
-rw-r--r--translation-help11
1 files changed, 10 insertions, 1 deletions
diff --git a/translation-help b/translation-help
index c26c6887..7c8e20dc 100644
--- a/translation-help
+++ b/translation-help
@@ -37,7 +37,7 @@ If you are working in the src/pacman tree, replace libalpm.pot with pacman.pot:
Making a new language is not too hard, but be sure to follow all the steps.
You will have to do the following steps in both the lib/libalpm/po/ and
-src/pacman/po/ directories, substituting where approriate. First, edit the
+src/pacman/po/ directories, substituting where appropriate. First, edit the
LINGUAS file and add your new language code at the bottom. Next, run the
following command, substituting 'libalpm.pot' or 'pacman.pot' depending on
which directory you are currently working in:
@@ -48,6 +48,15 @@ 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.
+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:
+
+msgstr "This is a test translation"
+
+msgstr ""
+"This is a test translation"
+
+
Translating Manpages
--------------------