1. *.properties - How to translate A message of these files is formated with 'key=value'. The value part should be translated. key=translate here -------------- 2. mnemonic character or Shortcut key (a) A message with mnemonic key should be localized as follows. mnemonic key is "&[one letter]". key=English &Message "&M" is mnemonic key -- ==> key=Translated Message(&M) Add (&M) ---- (b) A message with separate mnemonic key should be localized as follows. key=English Message key_mnemonic=M ==> key=Translated Message(M) key_mnemonic=M --- 3.Singlar and Plural forms In English, most nouns have singular and plural forms (like file and files). But in Chinese, there is no such forms unit words are used. The keys for this kind of messages can look like: xxxxSinglar = 1 xxxxPlural = {0} s or onexxxx = 1 manyxxxx = {0} s After translated, a unit (such as 个) should be added between the number and the noun. For example: xxxxSinglar = 1 个 xxxxPlural = {0} 个 or onexxxx = 1 个 manyxxxx = {0} 个 4. VALUE_fetchGroups={0,choice,0#0 Groups|1#1 Group|1<{0} Groups} The translation should be: VALUE_fetchGroups={0,choice,0#0 XX|1#1 XX|1<{0} XX} Here, "XX" means translation in local languages. The word "choice" should not be translated and should be left in English as it's type name of message format. And, "Group" should be translated here. Please note that it's not just issue of the "choice" parameter. We most often find overtranslations of the following parameter formats: {0,number,integer} {0,date} {0,time} too, so please do use your judgement to judge if they are parameter and should not be translated, if you sure don't know, raise your questions, we do have the Q&A form available to you, isn't it? Reminder: translate carefully for these kind of perperties. 5. also: - make sure all format holder ({0}, {1}...) in original sort. - don't convert any marks ( , | ' : . ) to double bytes inside of { }, actually, not manotray, but will be much more safe from vendor's view. 6. Note: a. In most cases, the format of *.properties file is like "Key=string", and "string" is to be translated. However, other formats exist, such as "Key: string". The string here is to be translated. But colon in such cases should not be changed. It should be kept as English colon. Otherwise, it will cause build error. b. About back slash "\" which indicates continuance to next line. i)If it appears in the middle of the line, not the end, then it has to be to be deleted. Otherwise, it causes native2ascii problem for double-byte languages. For example: XXXXXX\n\XXXXX (XXXXX means Chinese characters) will cause problem. It needs to be fixed as: XXXXXX\nXXXXX. ii)If it appears at the end of the line, it must be kept. For example: XXXXXXXXXX\n\n\ XXXXXXXX should NOT be changed to XXXXXXXX\n\n XXXXXXX c. Back slash plus colon "\:" Please translate the English colon into Chinese colon, and remove the back slash "\". e.g. "CvsAdd.error=Error\:" should be translated to "CvsAdd.error=错误:" After translated, the colon is Chinese (double-byte) colon and the back slash "\" should be removed. Special character Meaning -------------------------------------------------------- \t /* \u0009: horizontal tab HT */ \n /* \u000a: linefeed LF */ \f /* \u000c: form feed FF */ \r /* \u000d: carriage return CR */ \\ /* \u005c: backslash \ */ -------------------------------------------------------- Table: Special text formating strings and their meaning 7. The line which "#" appears in the top of the it, stands for comments line, No need to translate. the content of comments line is not only applied to the next one line, but for all related lines.