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.
短產出 x 長時間的複利效應:靠三種筆記,更靈活實現年度目標
-
我在「電腦玩物」部落格上,已經持續寫作 17、18 年,累積了超過 6000
篇文章。許多朋友問我,十幾年前是如何設定目標並持續經營部落格?面對不斷變化的趨勢,如何能持續分享提升工作效率的內容,並且堅持這麼多年?
最近在一場線上直播中,分享了:「*如何跳脫計畫,設計更靈活年度目標*」這個主題,我把分享過...
3 天前
0 Comments:
張貼留言