Is your software or document ready for localization?
It usually is not that simple to localize anything. Giving you "Hello world" and ask you to localized it into several languages might already have some problems to be resolved first before localizing it.
People who speak English may not be aware of that the nouns have gender in several languages. People who wrote technical document in German might not be aware of that other people might not be able to know how to translate it properly due to it's too specific in a particular area.
Imagine if you receive this word "Entropy", how should you translate it properly if there is not enough context to be reference?
"Entropy" is a physic term and widely used in physics, thermodynamic, and some other fancy area such as image processing.
If you are familiar with PhotoShop, then you probably know the term "entropy" appeared there. Translator will need to look up many different areas' dictionaries and might also need to consult some professors in order to translate it properly.
Imagine I now send you "%s Power" and then ask you to translate it into French, the translated result may not be good due to I did not give you enough information. See below examples (translated results from Google Translate):
Maximum Power ==> La puissance d'attaque
Minimum Power ==> Moins d'énergie
Efficient Power ==> Puissance efficace
So, how can you translate it properly if I only give you "%s Power"? If I only give you that, that means it's not ready to be localized. Actually it's an I18N issue that the codes are trying to manipulate strings, which should not happen if you are going to localize it into several languages.
執行優先於整理,不要憑空設計系統:以我的防彈筆記法實踐為例
-
之前分享如何設計標籤的文章(如何用標籤管理上萬則筆記?Evernote, Notion, obsidian 都適用
),有讀者提問說:「標籤的使用對我來說有點抽象😂,可能因為情境總是難以明確的定義?常常會覺得同一個任務又具有每日推進的性質、但也具有思考醞釀的性質,結果在下標籤的時候就猶豫不決,不知道您是否曾...
5 小時前
0 Comments:
張貼留言