Andrew's git
/
gitweb.git
/ diff
summary
|
log
|
commit
| diff |
tree
commit
grep
author
committer
pickaxe
?
re
git-gui: Document the new i18n context support
author
Shawn O. Pearce
<spearce@spearce.org>
Wed, 12 Sep 2007 21:03:27 +0000
(17:03 -0400)
committer
Shawn O. Pearce
<spearce@spearce.org>
Wed, 12 Sep 2007 21:05:16 +0000
(17:05 -0400)
Translators working on po files will likely need to know what the
@@noun and @@verb parts are in the original message text, and why
these are different messages in the po files.
Signed-off-by: Shawn O. Pearce <spearce@spearce.org>
po/README
patch
|
blob
|
history
raw
|
patch
|
inline
| side by side (parent:
a9813cb
)
diff --git
a/po/README
b/po/README
index e7cf40524755e1b66add9e2e3ac3200290e3eb48..9d8b7364fd8dda62a5acf2cb99e1c0a59205df9e 100644
(file)
--- a/
po/README
+++ b/
po/README
@@
-88,6
+88,15
@@
matching msgid lines. A few tips:
you would typically want to have corresponding ones in the string on
your msgstr line.
you would typically want to have corresponding ones in the string on
your msgstr line.
+ - Some messages contain an optional context indicator at the end,
+ for example "@@noun" or "@@verb". This indicator allows the
+ software to select the correct translation depending upon the use.
+ The indicator is not actually part of the message and will not
+ be shown to the end-user.
+
+ If your language does not require a different translation you
+ will still need to translate both messages.
+
- Often the messages being translated are format strings given to
"printf()"-like functions. Make sure "%s", "%d", and "%%" in your
translated messages match the original.
- Often the messages being translated are format strings given to
"printf()"-like functions. Make sure "%s", "%d", and "%%" in your
translated messages match the original.