1
$Id: TRANSLATE 4641 2007-12-04 15:00:14Z wk $
6
Some strings in GnuPG are for matching user input against. These
7
strings can accept multiple values that mean essentially the same
10
For example, the string "yes" in English is "sí" in Spanish. However,
11
some users will type "si" (without the accent). To accomodate both
12
users, you can translate the string "yes" as "sí|si". You can have
13
any number of alternate matches seperated by the | character like
16
The strings that can be handled in this way are of the form "yes|yes",
17
(or "no|no", etc.) There should also be a comment in the .po file
18
directing you to this file.
24
GnuPG provides a little help feature (entering a ? on a prompt). This
25
help used to be translated the usual way with gettext but it turned
26
out that this is too inflexible and does for example not allow to
27
correct little mistakes in the English text. For some newer features
28
we require editable help files anyway and thus the existing help
29
strings have neen moved to plain text files names "help.LL.txt". We
30
distribute these files and allow overriding them by files of that name
31
in /etc/gnupg. The syntax of these files is documented in
32
doc/help.txt. This is also the original we use to describe new
33
possible online help keys. The source files are located in doc/ and
34
need to be in encoded in UTF-8. Strings which require a translation
35
are disabled like this
37
.#gpgsm.some.help-item
38
This string is not translated.
40
After translation you should remove the the hash mark so that the
44
This string has been translated.
46
The percent sign is not a special character and if tehre is something
47
to watch out there will be a remark.
51
Sending new or updated translations
52
-----------------------------------
54
Please note that we do not use the TP Robot but require that
55
translations are to be send by mail to translations@gnupg.org. We
56
also strongly advise to get subscribed to i18n@gnupg.org and request
57
assistance if it is not clear on how to translate certain strings. A
58
wrongly translated string may lead to a security problem.
60
A copyright disclaimer to the FSF is required by all translators.