Closed
Bug 65991
Opened 23 years ago
Closed 3 years ago
conversion problem (fromU)- ISO-2022-JP/EUC-JP encoder cannot map \u301C
Categories
(Core :: Internationalization, defect)
Core
Internationalization
Tracking
()
RESOLVED
WONTFIX
People
(Reporter: nhottanscp, Assigned: nhottanscp)
References
Details
(Keywords: helpwanted, intl)
ISO-2022-JP encoder returns NS_ERROR_UENC_NOMAPPING for \u301C. In HTML Editor, set charset to ISO-2022-JP and input the character then save. The character is saved as NCR #12316; instead of JIS 0x2141. Macitoch: Japanese IME, in Japanese mode, type tilda. Windows: Use "Character Map" accessory.
Comment 1•23 years ago
|
||
accept. Mark it as moz0.9
Status: NEW → ASSIGNED
Target Milestone: --- → mozilla0.9
Assignee | ||
Comment 2•23 years ago
|
||
The same problem in EUC-JP encoder, \u301C cannot be converted and saved as NCR 〜
Summary: ISO-2022-JP encoder cannot map \u301C → ISO-2022-JP/EUC-JP encoder cannot map \u301C
Updated•23 years ago
|
Summary: ISO-2022-JP/EUC-JP encoder cannot map \u301C → conversion problem- ISO-2022-JP/EUC-JP encoder cannot map \u301C
Updated•23 years ago
|
Summary: conversion problem- ISO-2022-JP/EUC-JP encoder cannot map \u301C → conversion problem (fromU)- ISO-2022-JP/EUC-JP encoder cannot map \u301C
Comment 4•23 years ago
|
||
jis0208.ump seems to be made by CP932.TXT. In CP932.TXT, JIS 0x2141 mapped to \uFF5E. Other characters(JIS 0x2140,2141,2142,215D,2171,2172) have the same problem. (see http://www.autumn.org/etc/unidif.html) I think,,, 1. Native widgets get chars in native encoding. 2. Convert the native encoded text to UCS-2 (with OS's or Moz's converter?) 3. If a mapping table of the converter converts JIS 0x2141 to \u301C, mozilla converter will fail. (*)OS/2 and MacOS native converter maps SJIS 0x8160 (JIS 0x2141) to \u301C
Comment 5•23 years ago
|
||
cannot make it for moz0.9. push to moz 0.9.1
Target Milestone: mozilla0.9 → mozilla0.9.1
Comment 6•23 years ago
|
||
nhotta- I am overload- can you help this one ?
Assignee: ftang → nhotta
Status: ASSIGNED → NEW
Assignee | ||
Comment 9•23 years ago
|
||
> 1. Native widgets get chars in native encoding. yes > 2. Convert the native encoded text to UCS-2 (with OS's or Moz's converter?) OS converter is used > 3. If a mapping table of the converter converts JIS 0x2141 to \u301C, > mozilla converter will fail. Not sure but this bug is about converting from \u301C to a document charset. The problem can be reproduced without the user input, like a file below. Save as ISO-2022-JP or EUC-JP generate the NCR. <HTML> <BODY> 〜 </BODY> </HTML>
Status: NEW → ASSIGNED
Assignee | ||
Updated•23 years ago
|
Target Milestone: mozilla0.9.1 → mozilla0.9.2
Comment 10•23 years ago
|
||
changing keyword to nsbeta1-.
Comment 11•23 years ago
|
||
not critical. move to moz0.9.3
Target Milestone: mozilla0.9.2 → mozilla0.9.3
Assignee | ||
Updated•23 years ago
|
Target Milestone: mozilla0.9.3 → ---
Assignee | ||
Comment 14•22 years ago
|
||
This is a mapping problem as bug 54135, reassign to ftang.
Assignee: nhotta → ftang
Status: ASSIGNED → NEW
Updated•22 years ago
|
Target Milestone: mozilla0.9.6 → mozilla0.9.7
Comment 15•22 years ago
|
||
reassign to nhotta- sorry, I really not sure what else should I do for this bug.
Assignee: ftang → nhotta
Assignee | ||
Comment 16•22 years ago
|
||
add 'helpwanted' keyword
Keywords: helpwanted
Target Milestone: mozilla0.9.7 → mozilla0.9.8
Assignee | ||
Updated•22 years ago
|
Target Milestone: mozilla0.9.8 → ---
Assignee | ||
Updated•22 years ago
|
Target Milestone: --- → mozilla1.2
Updated•22 years ago
|
Status: NEW → ASSIGNED
Assignee | ||
Updated•22 years ago
|
Target Milestone: mozilla1.2alpha → ---
Comment 17•21 years ago
|
||
I think this bug has resolved by Bug 108136 fix.
Updated•15 years ago
|
QA Contact: amyy → i18n
Depends on: encoding_rs
Even though this bug hasn't been marked fixed, it was actually fixed. However, encoding_rs regresses this due to the Encoding Standard not having this special case. annevk, should the Encoding Standard have this special case? Filed https://github.com/whatwg/encoding/issues/114
See Also: → https://github.com/whatwg/encoding/issues/114
WONTFIXing per spec issue.
Status: ASSIGNED → RESOLVED
Closed: 3 years ago
Resolution: --- → WONTFIX
You need to log in
before you can comment on or make changes to this bug.
Description
•