73035 - JIS X 0213 support

Status: RESOLVED INVALID

(Core :: Internationalization, defect)

Description

[nhottanscp]

This is a tracking bug so we can keep information about JIS 0213.
Currently, no IANA registry for charset and some chars
Following information was provided by [e-mail].


The JIS X0213 code table is in

   http://www.jca.apc.org/%7Eearthian/aozora/0213/jisx0213code.zip
This table contains Japanese characters encoded by Shift_JIS.  Some
X0213 characters are not members of the Unicode.  The graphical shape
tables are in

   http://www.itscj.ipsj.or.jp/ISO-IR/228.pdf 		
   http://www.itscj.ipsj.or.jp/ISO-IR/229.pdf

These are ISO-2022 registry.

Comment 1

[nhottanscp]

Mark as future.

In the table, there are 491 characters which are not mapped to unicode.

Comment 2

[nhottanscp]

MacOS X supports input JIS 0213 characters.
They have glyphs for some characters. I will attach a screen shot once I learn 
how to take a screen shot.
On e-mail (Apple's default mail client), those characters are sent as UTF-8.

Comment 3

[nhottanscp]

Attachment: Screen shot, Mac OSX kotoeri support for JIS0213.

Comment 4

[WADA:World Anti-bad-Duping Agency]

Correction. Change "blocks" to "depends on". Sorry for spam.

Comment 5

[Jean-Marc Desperrier]

Maybe the data pointers for this bug must be updated ?
It will be necessary to take care of Shift_JIS-2004/Shift_JISX0213 when doing that :
http://homepage1.nifty.com/nomenclator/perl/ShiftJIS-X0213-MapUTF.html

A first step would be to include support for characters from JIS 213 that are
inside the BMP, to remove the dependance on bug 162431.

Comment 6

[Masayuki Nakano [:masayuki] (he/him)(JST, +0900)]

What issues want to fix in this bug?

I think that we should not support JIS X 0213 on Japanese local encodings, i.e, on Shift_JIS, EUC-JP and ISO-2022-JP*. Because if we support JIS X 0213 on these encodings, Japanese people will be confused by the difference between Gecko and other UAs. E.g., now, WinIE6 and Opera8.5 don't support JIS X 0212 on EUC-JP that is 3 bytes per a charcter.(Gecko and KHTML are supporting it.) By this reason, the *users* of some EUC-JP sites are confused. The Gecko and KHTML users can post and read the JIS X 0212 characters on EUC-JP sites. But many users(i.e., WinIE users) cannot post and read it. Therefore, JIS X 0213 on JA local encodings will make trouble for JA lang users. JIS X 0213 should be supported on UTF-8. I think that it's enough for Japanese people on the (current) internet.

If this bug wants to fix this, we should mark to WONTFIX.

Please clarify what should be fixed by this bug.
If nobody answer to my question, I'll mark to WONTFIX this bug.

Comment 7

[Masatoshi Kimura [:emk]]

What about bug 144891?
I agree with you that we don't have to support JIS X 0213 encodings for web page or e-mail.
However we need JIS X 0213 converter to support JIS X 0213 font on UNIX even if external encoding is only Unicode.
IMO we should seek the opinions of Japanese Linux users' community before marking WONTFIX.

Comment 8

[Masayuki Nakano [:masayuki] (he/him)(JST, +0900)]

Yeah, but if bug 144891 needs JIS X 0213 converter, I think that it should be created on bug 144891, so not on this bug. I think that this bug is to expand JA local encodings. If so, we don't need this bug.

I don't deny to fix bug 144891.

# If we need to expand the encodings, this bug is a step of fixing bug 144891.
# But not so. We don't need to expand it. Therefore, this bug will be never
# FIXED. So, this bug will be blocking bug 144891 forever.
# This is not a good state for bug 144891.
# We should clarify this bug's state for bug 144891.

Comment 9

[Masatoshi Kimura [:emk]]

According to comment #0, this is a meta bug to track JIS X 0213 related issue.
Therefore it's reasonable that this blocks bug 144891.
Of course, if you think that it's overkill to open meta bug to track only one bug, feel free to close this :-)

Comment 10

[Masayuki Nakano [:masayuki] (he/him)(JST, +0900)]

Thanks, I didn't understand this is a meta bug (because the keywords doesn't have meta keyword).

O.K. I'm closing this bug as INVA. This is not a good meta bug.

Comment 11

[Jungshik Shin]

(In reply to comment #7)
> What about bug 144891?

> However we need JIS X 0213 converter to support JIS X 0213 font on UNIX even if
> external encoding is only Unicode.
> IMO we should seek the opinions of Japanese Linux users' community before
> marking WONTFIX.

Linux user community can't care less these days. Virtually no one uses XLFD-based X11 core fonts. Linux users just use truetype and opentype fonts with fontconfig and Xft.