Quoting Junio C Hamano <gitster@xxxxxxxxx>:
+++ b/po/glossary/git-gui-glossary.txt
@@ -0,0 +1,34 @@
+"English Term (Dear translator: This file will never be visible to
the user!)" "English Definition (Dear translator: This file will
never be visible to the user! It should only serve as a tool for
you, the translator. Nothing more.)"
+"amend" ""
+"annotate" ""
+"branch [noun]" "A 'branch' is an active line of development."
+"branch [verb]" ""
+"checkout [noun]" ""
+"checkout [verb]" "The action of updating the working tree to a
revision which was stored in the object database."
+"commit [noun]" "A single point in the git history."
I wonder.... couldn't this be written as a Tcl array that maps
word to its definition, marked with [mc] 'gettext'ese, perhaps,
glossary.tcl? Then perhaps git-gui can include it and have a
user-visible glossary as part of its help system.
I'm not so sure about this idea. I'd expect the glossary definitions
for the translators to emphasize other issues than what a user-visible
glossary would explain. For the user, the glossary should explain what
each term means and what the user can *do* with this. For the
translator, the glossary should explain what each term means and where
it appears in the project (and which other terms it should be
distinguished from). Also, the translator glossary IMHO should collect
warnings about potential ambiguities as well (including the very clear
distinction between noun and verb). Whereas the user glossary is
probably much more verbose in what it explains, but doesn't emphasize
as much the clear differences between verb and noun and so on.
Am I dreaming, or too drunk?
You tell me :-)
Christian
-
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
