Andre Poenitz schrieb:
The string in the source is basically an id in string form. There
is no conceptional difference between "„text“" and "Fo-bar-0x341e3",
except that the latter is 7-bit-clean and won't confuse translation
systems.
"Fo-bar-0x341e3" gives me "Fo-bar-0x341e3" in the dialog, so 0x341e3 is not changed to a character.
How can I specify a character by its character table code so that I can see it in the dialog?
Sure. The _translations_ can be whatever you want, the source strings
are better plain ASCII. [As I said, it can be make work with others,
but that requires more attendance]
So that means that one is forced to use English a design language? What about users that wants to
write a small program only in German and want to fill a combobox e.g. with "grün"?
I at least applied the working tr() method for the guillemets:
http://www.lyx.org/trac/changeset/26041
Please use, say, "<foo>text</foo>" and provide suitable translations.
What do you mean? Should I user instead of
tr("„text“")
this:
"<„>text<\“>"
No. Some plain ASCII string. In fact, verbatim "<foo>text</foo>" would
do ;-)
Are you playing with me? I need "„text“" and not a plain ASCII string!
Uwe
