Talk:Interface guidelines: Difference between revisions
Ahmet Demir (talk | contribs) (Language Strings, prepositions and non-standard linguistics) |
Ahmet Demir (talk | contribs) No edit summary |
||
| Line 22: | Line 22: | ||
I think, this problem can be avoided by setting a guideline for it like: | I think, this problem can be avoided by setting a guideline for it like: | ||
"Use whole sentences or sub-sentences as language strings, do not divide your sentence into words of prepositions to avoid dublication in translations. Because not all the languages have the same grammer and linguistics that | "Use whole sentences or sub-sentences as language strings, do not divide your sentence into words of prepositions to avoid dublication in translations. Because not all the languages have the same grammer and linguistics that English built on." | ||
This way, the the translated UI would be much more understandable. | This way, the the translated UI would be much more understandable. | ||
Revision as of 13:50, 4 April 2009
I want to contribute for the "Language Strings" title.
The prepositions in English usually does not correspond to meaningfull words in other languages. Say "3 of 10 is being displayed" string should be coded in the language file as is.
Wrong Approach:
Phrase 1: of
Phrase 2: is being displayed
Instead, the correct approach is:
Phrase: %s of %s is being displayed
Because the preposition may or may not exist in the translation as a word, therefore the translated string may also be shuffled, i.e. may not be starting with "3" for the specific example above.
I think, this problem can be avoided by setting a guideline for it like:
"Use whole sentences or sub-sentences as language strings, do not divide your sentence into words of prepositions to avoid dublication in translations. Because not all the languages have the same grammer and linguistics that English built on."
This way, the the translated UI would be much more understandable.
