Hi all, just my 2 cents as a translator since I want to point out some problem I find when I translate (not specific for YaST, but I think you should consider also such problems in your discussion about coding attitude). 2011/6/8 Lukas Ocilka <lukas.ocilka@suse.cz>:
Coding Standards - The code should be not only understandable to ourselves but also to the others.
In particular messages should be easily understandable also to translators.
- Examples:
* avoid string concatenation For translators it is difficult to write good sentences when the original message is split in several parts as a consequence of concatenation of strings and parameters. This affects in particular languages that distinguish genre as well as singular/plural. For me (but I think it is the same for other translators), it is better to have more strings (with placeholders) and repeated parts than short but split strings. For instance, the msgid "should not be empty" can be translated in Italian in several ways, depending on the actual subject.
* Useful comments
Please consider to add useful comments also for translators: sometimes it is difficult to translate in a right way some message involving placeholders since it is not so easy to guess the term that replaces the placeholder, so there can be a genre or singular/plural mismatch in the resulting translation. Moreover, the order of placeholders should not be imposed. Similarly, since usually translators are not familiar as you with the message context, sometimes it is difficult to parse correctly complex messages, in particular when there is a quite long sequence of adjectives and nouns that can be bound in different ways such that the correct one depends on the context. Regards, Andrea -- To unsubscribe, e-mail: yast-devel+unsubscribe@opensuse.org For additional commands, e-mail: yast-devel+help@opensuse.org