Unicode Conversion- ISO-2022-JP page does not display hankaku katakana characters

VERIFIED FIXED in M7

Status

()

P2
normal
VERIFIED FIXED
20 years ago
20 years ago

People

(Reporter: teruko, Assigned: ftang)

Tracking

Trunk
x86
Windows 95
Points:
---

Firefox Tracking Flags

(Not tracked)

Details

(URL)

(Reporter)

Description

20 years ago
Tested 3-17-99 Win32 build.

The page contains Kanji and hankaku katakana.  After the double-byte characters are displayed, the page does not
display anything.  The part of hankaku katakana is the point the page does not display anything.

I put the simple test case in http://babel/tests/browser/bft/jis/aiu-jis.html which contains only hankaku katakana.
It does not display anything even though I click on Reload button.
(Reporter)

Updated

20 years ago
Priority: P3 → P2
Target Milestone: M4
(Assignee)

Comment 1

20 years ago
It is ESC ( I 123 ESC ( B
erik: what is ESC (  I ?
I don't think hankaku is part of ISO-2022-JP. We should think carefully about
the error handling of our converter. Should accept ESC ( I ? ( in my opinion, we
may not want to but 4.x did. We  may be foreced to do it for backward
compatability) or we should at least make sure it convert correctly after the
ESC ( B.

Erik, please help to give us opinion.

Updated

20 years ago
Status: NEW → ASSIGNED

Comment 2

20 years ago
The iso-2022-jp escape sequences are as follows:

  ESC(B   ASCII
  ESC(J   JIS X 0201-1976 Roman
  ESC$@   JIS X 0208-1978
  ESC$B   JIS X 0208-1983

The following escape sequences are not part of iso-2022-jp:

  ESC(I   JIS X 0201-1976 Kana
  ESC$(D  JIS X 0212-1990

However, our old code base accepted these escape sequences. Also, in networking
it is better to be liberal in what you accept, and conservative in what you
send out. So we should accept these escape sequences at least for receiving,
and we may even need to use one or both of them for sending to remain compatible
with our old code base.

Naoki may have further input on the Hankaku Kana issue for mail/news.
(Assignee)

Updated

20 years ago
Summary: ISO-2022-JP page does not display hankaku katakana characters → Unicode Conversion- ISO-2022-JP page does not display hankaku katakana characters

Updated

20 years ago
Target Milestone: M4 → M5

Updated

20 years ago
Target Milestone: M5 → M6

Comment 3

20 years ago
Moved to M6 to give Cata time to assist Nisheeth on external DTD support
in the XML parser.

Updated

20 years ago
Target Milestone: M6 → M7
(Assignee)

Updated

20 years ago
Status: NEW → ASSIGNED
(Assignee)

Updated

20 years ago
Target Milestone: M9 → M10
(Assignee)

Comment 4

20 years ago
push to M10
(Assignee)

Updated

20 years ago
Target Milestone: M10 → M7
(Assignee)

Comment 5

20 years ago
Mark this back to M7 since I have already have fix in local dist. Need to check
in monday morning
(Assignee)

Updated

20 years ago
Status: ASSIGNED → RESOLVED
Last Resolved: 20 years ago
Resolution: --- → FIXED
(Assignee)

Comment 6

20 years ago
check in and Mark it fix. Please verify ASAP
(Reporter)

Comment 7

20 years ago
I changed the URL.  I verified this in 6-14-09 build.
You need to log in before you can comment on or make changes to this bug.