Closed Bug 79273 Opened 24 years ago Closed 24 years ago

add GB18030 4 byte conversion support to unicode conversion engine

Categories

(Core :: Internationalization, defect)

x86
Windows NT
defect
Not set
normal

Tracking

()

RESOLVED FIXED
mozilla0.9.1

People

(Reporter: ftang, Assigned: ftang)

References

Details

(Whiteboard: patch reviewed by bstell. need super review2001-05-07 18:08)

This is a sup part of fixing Basically, GB18030 is a 1,2,4 byte encoding the 4 byte part encode character in the following range byte 1: 0x81-0xfe byte 2: 0x30-0x39 byte 3: 0x81-0xfe byte 4: 0x30-0x39 This 4 byte form a 126 x 10 x 126 x 10 linear space and the unicode which defined in Unicode 3.0 and do not have mapping in GBK get map to this space in 149 range. We need to add functionality to our unicode conversion engine to convert this 4 byte range to a linear space and back
This is part of 75928 We seperate this into different bug report so we can land it quickly here is the patch http://bugzilla.mozilla.org/showattachment.cgi?attach_id=33421 bstell already review it. Notice we also fix a problem in uscan.c which last time we forget to include uCnSAlways8BytesGLComposedHangul in the array.
Whiteboard: patch reviewed by bstell. need super review
Whiteboard: patch reviewed by bstell. need super review → patch reviewed by bstell. need super review2001-05-07 18:08
Blocks: 75928
Status: NEW → ASSIGNED
Target Milestone: --- → mozilla0.9.1
Changing QA contact to teruko@netscape.com for now.
QA Contact: andreasb → teruko
Actually, can you fix the hard tabs in that patch?
fix and check in
Status: ASSIGNED → RESOLVED
Closed: 24 years ago
Resolution: --- → FIXED
Frank, do you have a table for GB18030? If you have it, please attach it. QA cannot verify this if we do not have table.
We do not have fonts for Windows, so we cannot verify this. I change QA contact to the reporter.
QA Contact: teruko → ftang
You need to log in before you can comment on or make changes to this bug.