Like the Unicode

Started by c_redman, June 29, 2007, 06:24:18 AM

Previous topic - Next topic

0 Members and 1 Guest are viewing this topic.

c_redman

I like the better support for unicode, as it has made it easier for me to work with pinyin entries. In the old version, These fields had to be defined as Chinese, because if it was set to "English (Latin)" some of the tone marks (1st and 3rd, I think) weren't displayed. But pinyin displayed in a Chinese font looked horrible. I'm glad I have a better option. I define the relevant field as English, and the dialogs happily display it correctly, as long as I have defined English to use the right font. Is this approach safe, or is there some gotcha that hasn't reared its head yet?

I have a question on the behavior of the pinyin when editing from the learn or test mode. I have data that I imported with tone marks. When editing, the pinyin is converted from tone marks to tone numbers. It does this even though I have defined the field language as English. However, if I define the file itself as English instead of Chinese, it doesn't do the mark-->number conversion. Is this the preferred way of enabling/disabling this feature?