From version 7.2
edited by Sergiu Dumitriu
on 2015/03/05 22:06
To version 8.1
edited by Sergiu Dumitriu
on 2015/03/05 22:06
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -45,7 +45,7 @@
45 45  **Do not split sentences into smaller translated fragments**. For example, to translate //There are 42 errors in the form//, do not use ##$msg.get('prefix.thereAre') $numberOfErrors $msg.get('prefix.errorsInForm')##, since few languages actually use this topic.
46 46  
47 47  * This could be represented as number followed by text, which could be translated back to //42 errors are in the form//
48 -* Even when in another languages the number is between two fragments of text, the two fragments could contain different parts, which could be translated back to //There are in the form 42 errors//, for example, in which case the two "hints" that we included in the key, ##thereAre## and ##errorsInForm## actually confuse the reader
48 +* Even when in another languages the number is between two fragments of text, the two fragments could contain different parts, which could be translated back to //In the form there are 42 errors//, for example, in which case the two "hints" that we included in the key, ##thereAre## and ##errorsInForm## actually confuse the reader
49 49  * Most of the time, translators work on a list of keys out of context, so they won't actually know that ##.thereAre## is supposed to be followed by ##.errorsInText##, and it actually refers to that specific message. Depending on the full message, different translations might be used to better reflect the specifics of each culture, and a simple //"there are"// piece of text doesn't give any meaning to the translator
50 50  * In many languages the word for //errors// will be written differently depending on the actual number of errors; even in English it would be better to say //1 error// instead of //1 errors//
51 51  

Get Connected