the japanese kanas in ptt.cc was converted to Private Used Area in unicode
Bug #424677 reported by
LI Daobing
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Ubuntu Translations |
Invalid
|
Medium
|
Ubuntu Japanese Translators | ||
fqterm (Ubuntu) |
Invalid
|
Undecided
|
Unassigned | ||
pcmanx-gtk2 (Ubuntu) |
Invalid
|
Undecided
|
Unassigned | ||
qterm (Ubuntu) |
Invalid
|
Undecided
|
Unassigned | ||
ttf-wqy-zenhei (Ubuntu) |
Invalid
|
Undecided
|
Unassigned |
Bug Description
Binary package hint: ttf-wqy-zenhei
the following character has a wrong display under "WenQuanYi Zen Hei" and "WenQuanYi Zen Hei Mono"
"☆"
many other japanese characters also has this problem.
three screenshot in leafpad in attachment, the file name is the font name.
tags: | added: fonts i18n |
Changed in ubuntu-translations: | |
importance: | Undecided → Medium |
status: | New → Triaged |
To post a comment you must log in.
what you typed are not Japanese characters. Their encodings belongs to Private Used Area (PUA), and are arbitrarily defined for specific fonts. The corresponding unicode values are:
"U+f73f U+f703 U+2606 U+f70f U+f715"
What you should be using are "らき☆すた", with corresponding unicode values
"U+3089 U+304D U+2606 U+3059 U+305F"
these are the true "Japanese" kanas, Zen Hei and many other CJK fonts can display them very well.
Perhaps Arne should consider removing these PUA glyphs from Uming. Using them causing more confusions. I can find a bunch of reports on this:
http:// wenq.org/ forum/viewtopic .php?f= 5&t=744& p=3985 wenq.org/ forum/viewtopic .php?f= 12&t=874
http://
Another frequently encountered problem is U+E5D9 (mapped to U+23EBF), the string "" are often seen at the beginning of a paragraph (may be a result of using MS Word) and causing confusions, for example:
http:// forum.ubuntu. org.cn/ viewtopic. php?f=8& t=221913& p=1423546
I understand that Uming defines these code points based on HKSCS-2004 Annex (http:// www.ogcio. gov.hk/ ccli/unicode/ hkscs/download/ 2003cmp. txt), however since uming has far less code points than the 65535 limit, it is entirely possible to restore these code points to their official unicode encoding.
Arne, do you want to comment on this?