Home » U++ Library support » U++ Libraries and TheIDE: i18n, Unicode and Internationalization » Translation Problems (German)
| Translation Problems (German) [message #3780] |
Sun, 25 June 2006 11:38  |
Werner
Messages: 234
Registered: May 2006
Location: Cologne / Germany
|
Experienced Member |
|
|
I am adding the German language to a dede2.tr file (LANGUAGE "DE-DE windows-1252") which I will make available to the community (if somebody is interested in  ).
The peculiarities of the German language lead to problems when parameterized strings are to be translated. For example,
enUS: "Do you really want to delete the selected %s ?"
needs 4 different translations depending on what "%s" means:
1) %s = "Bereich" (area)
deDE: "Möchten Sie wirklich den ausgewählten %s löschen?"
2) %s = "Zeile" (row)
deDE: "Möchten Sie wirklich die ausgewählte %s löschen?"
3) %s = "Objekt" (object)
deDE: "Möchten Sie wirklich das ausgewählte %s löschen?"
4) %s = "Bereiche" (areas), "Zeilen" (rows), "Objekte" (objects)
deDE: "Möchten Sie wirklich die ausgewählten %s löschen?"
Actually, the translation depends on the linguistic gender (masculine/feminine/neuter) and the number of what will be substituted for %s. "Bereich", "Zeile", etc. are just examples.
This brings up the following questions:
Is it possible to create universally usable context-dependent translations? (As far as I understand " t_("XXX\vYYY")" needs to know beforehand what "XXX" means in the individual case.)
Is it ok to add only bilingual translations even though the other entries already contain more languages?
Werner
[Updated on: Sun, 25 June 2006 11:47] Report message to a moderator |
|
|
|
Current Time: Tue Apr 28 12:10:20 GMT+2 2026
Total time taken to generate the page: 0.01220 seconds
|
U++ framework
Search
Help
Members
Register
Login
Home
