[Bf-translations-dev] Ambiguous translations

[Yain Vieyra]

will this be compatible with softs like PoEdit as now?



________________________________
De: Michael Färber <01mf02 at gmail.com>
Para: bf-translations-dev at blender.org
Enviado: lunes, 7 de noviembre de 2011 15:19
Asunto: [Bf-translations-dev] Ambiguous translations

Hi fellow translators,


I found a problem in the current way Blender strings are translated: 
When one word in English has to be translated to different words in 
another language, it seems there currently is no way to do that!

Examples:
"Manual" can mean either "documentation" or manual as in "manually".
"Group" can mean a verb ("to group") or a noun ("one group").


However, the gettext library seems to provide functionality to solve 
that problem: The pgettext() function takes an additional "context", 
which can be used to differentiate between different translations of one 
word. See 
http://www.gnu.org/software/gettext/manual/gettext.html#Ambiguities for 
a good description. (They've also got a nice example with ASCII art. :) )

In my opinion, one should use calls like to following in the Blender source:
pgettext ("adjective", "Manual")
pgettext ("noun", "Manual")

pgettext ("verb", "Group")
pgettext ("noun", "Group")


What do you think about that? Would it be a good idea to use pgettext()? 
How would you call the different contexts? Would a solution like 
"adjective", "noun", "verb" be enough?
Have you also found such ambiguous words?


All the best,
Michael
_______________________________________________
Bf-translations-dev mailing list
Bf-translations-dev at blender.org
http://lists.blender.org/mailman/listinfo/bf-translations-dev
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.blender.org/pipermail/bf-translations-dev/attachments/20111107/e4a982fb/attachment.htm