Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. VO
      singulars
      1. This table or related slice is empty.
    1. COI have the Win7 version of SimSun installed here, and I am sure it contains all these characters as MS Word displays them in a unifrom style when using this font. The rest of your suggestions I'll need to play with. Yes, it seems to be true for most software (including Windows itself) that Western language versions always try a Japanese font first. I have modified my WinXP to look for Simplified Chinese first, so I'd get the version of e.g. 直 that I like.
      singulars
    2. CO@Szabolcs In that case maybe the "Font name"/"Font family" of the SimSun font is not "SimSun". I have three simsun files, whoes "Font name"/"Font Family"s are separately "宋体", "新宋体"(both of which cover the *CJK Unified Ideographs* and *CJK Unified Ideographs Extension A*) and "SimSun-ExtB"(which covers the *CJK Unified Ideographs Extension B* only). Maybe use software like Babel Map ( http://www.babelstone.co.uk/software/babelmap.html ) to check the exact range of the font.
      singulars
    3. COand I found that in the **UnicodeLanguageFontMapping.tr** file, many common characters for both Japanese and Simplified Chinese are placed only in the **# Japanese** section. I tried to move those ones belonging to *CJK Unified Ideographs* and *CJK Unified Ideographs Extension A* to the **# Chinese simplified** section, with changing the encode from ShiftJIS to CP936, and found those characters are automatically recognized as Chinese characters and then assigned with DefaultChineseSimplifiedFont/DefaultMonoChineseSimplifiedFont now.
      singulars
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload