[quote=“Hellstorm”]But even with a word processor, this just does not look right. A font with included readings just looks far more pleasing (in principle, I would prefer this ruby option, but right now, this is not useful. I wonder how Indesign handles this).
About the incorrect tones: It saves the correct tones, but the display will be incorrect. If you have ㄕˋ (e.g. 是), it will be displayed as ㄕˊ. Try it out for yourself. ˇ will be displayed like <. This is not just ugly, this is plain wrong.[/quote]
I’m using Chinese Word for windows and my version does not have this problem. I just entered a sample paragraph, and the tones are all correctly identified, and correctly displayed (including ㄕˋ). I do agree that because it doesn’t recognize variant tones, its use is quite limited.
This is a silly generalization. Of course, when translating names, a good translator will first check available resources to see whether a person’s name has a standard English rendering, as is the case with many public figures. In the case of legal documents we will try to determine whether an official or authoritiative English spelling of their name exists, for example on a passport or birth certificate. When appropriate, we will also try to identify whether a person has a preferred English spelling of their name.
But there have been plenty of times when I’ve also used the Word function as a down-and-dirty way to quickly confirm the pronunciation of obscure characters in names when translating long list of names of non-public figures (for example translating a list of names of hundreds of shareholders in a company for purely formality purposes, where this aspect of the translation does not bear directly on any rights or interests at stake). I would do this in cases where I am around 90 percent sure of the pronounciation of a character already and just want to reconfirm it (which happens a lot with given names). If I’ve never seen a character before, on the other hand, I’ll look it up in the online MOE dictionary.