mirror of
git://git.gnupg.org/gnupg.git
synced 2024-11-10 21:38:50 +01:00
dc107b7850
* README, agent/command.c, agent/keyformat.txt, common/i18n.c,
common/iobuf.c, common/keyserver.h, dirmngr/cdblib.c,
dirmngr/ldap-wrapper.c, doc/DETAILS, doc/TRANSLATE,
doc/announce-2.1.txt, doc/gpg.texi, doc/gpgsm.texi,
doc/scdaemon.texi, doc/tools.texi, doc/whats-new-in-2.1.txt,
g10/export.c, g10/getkey.c, g10/import.c, g10/keyedit.c, m4/ksba.m4,
m4/libgcrypt.m4, m4/ntbtls.m4, po/ca.po, po/cs.po, po/da.po,
po/de.po, po/el.po, po/eo.po, po/es.po, po/et.po, po/fi.po,
po/fr.po, po/gl.po, po/hu.po, po/id.po, po/it.po, po/ja.po,
po/nb.po, po/pl.po, po/pt.po, po/ro.po, po/ru.po, po/sk.po,
po/sv.po, po/tr.po, po/uk.po, po/zh_CN.po, po/zh_TW.po,
scd/app-p15.c, scd/ccid-driver.c, scd/command.c, sm/gpgsm.c,
sm/sign.c, tools/gpgconf-comp.c, tools/gpgtar.h: replace "Allow to"
with clearer text.
In standard English, the normal construction is "${XXX} allows ${YYY}
to" -- that is, the subject (${XXX}) of the sentence is allowing the
object (${YYY}) to do something. When the object is missing, the
phrasing sounds awkward, even if the object is implied by context.
There's almost always a better construction that isn't as awkward.
These changes should make the language a bit clearer.
Signed-off-by: Daniel Kahn Gillmor <dkg@fifthhorseman.net>
62 lines
2.2 KiB
Plaintext
62 lines
2.2 KiB
Plaintext
$Id$
|
|
|
|
Note for translators
|
|
--------------------
|
|
|
|
Some strings in GnuPG are for matching user input against. These
|
|
strings can accept multiple values that mean essentially the same
|
|
thing.
|
|
|
|
For example, the string "yes" in English is "sí" in Spanish. However,
|
|
some users will type "si" (without the accent). To accomodate both
|
|
users, you can translate the string "yes" as "sí|si". You can have
|
|
any number of alternate matches seperated by the | character like
|
|
"sí|si|seguro".
|
|
|
|
The strings that can be handled in this way are of the form "yes|yes",
|
|
(or "no|no", etc.) There should also be a comment in the .po file
|
|
directing you to this file.
|
|
|
|
|
|
Help files
|
|
----------
|
|
|
|
GnuPG provides a little help feature (entering a ? on a prompt). This
|
|
help used to be translated the usual way with gettext but it turned
|
|
out that this is too inflexible and does for example not allow
|
|
correcting little mistakes in the English text. For some newer features
|
|
we require editable help files anyway and thus the existing help
|
|
strings have been moved to plain text files names "help.LL.txt". We
|
|
distribute these files and allow overriding them by files of that name
|
|
in /etc/gnupg. The syntax of these files is documented in
|
|
doc/help.txt. This is also the original we use to describe new
|
|
possible online help keys. The source files are located in doc/ and
|
|
need to be in encoded in UTF-8. Strings which require a translation
|
|
are disabled like this
|
|
|
|
.#gpgsm.some.help-item
|
|
This string is not translated.
|
|
|
|
After translation you should remove the the hash mark so that the
|
|
entry looks like.
|
|
|
|
.gpgsm.some.help-item
|
|
This string has been translated.
|
|
|
|
The percent sign is not a special character and if there is something
|
|
to watch out there will be a remark.
|
|
|
|
|
|
|
|
Sending new or updated translations
|
|
-----------------------------------
|
|
|
|
Please note that we do not use the TP Robot but require that
|
|
translations are to be send by mail to translations@gnupg.org. We
|
|
also strongly advise to get subscribed to i18n@gnupg.org and request
|
|
assistance if it is not clear on how to translate certain strings. A
|
|
wrongly translated string may lead to a security problem.
|
|
|
|
A copyright disclaimer to the FSF is not anymore required since
|
|
December 2012.
|