Closed Bug 19589 Opened 25 years ago Closed 22 years ago

Latin Extended characters rendering problem

Categories

(Core :: Internationalization, defect, P3)

PowerPC
Mac System 8.6
defect

Tracking

()

VERIFIED FIXED
Future

People

(Reporter: teruko, Assigned: ftang)

References

()

Details

(Keywords: intl, platform-parity, Whiteboard: [nsbeta1-])

Some nicode range for Latin Extended-A and B characters are not displayed in
Mac.

Go to Latin Extended-A range
http://warp/u/ftang/utf8test/ncr.cgi?r=0x0&c=0x1

Many characters are not displayed.

Go to Latin Extended-B range
http://warp/u/ftang/utf8test/ncr.cgi?r=0x0&c=0x2

Many characters are not displayed.

Tested 11-18-08 Mac build.
Status: NEW → ASSIGNED
Summary: [PP] Latin Extended characters rendering problem → [PP] Latin Extended characters rendering problem
Target Milestone: M16
Specifically, which characters?  Should this be marked [BETA] in the summary?
In http://warp/u/ftang/utf8test/ncr.cgi?r=0x0&c=0x1
0102, 0103,0108, 0109, 010A, 010B, 0110, 0104, 0105, 010C,010D, 010E, 010F, 0120, 0121, 0124, 0125, 0128, 0129,
012C,012D, 0130, 0134, 0135, 014E, 014F, 015C, 015D, 015E, 015F, 0162, 0163, 0168, 0169, 016C, 016D, 0174, 0175, 0176,
0177,
 cannot be seen.
after 0180,
only 0192, 01CE, 01D0, 01D2, 01D4, 01D6, 01D8, 01DA, 01DC can be seen.  Rest of the characters from 0180 are displayed
as <?>.

In http://warp/u/ftang/utf8test/ncr.cgi?r=0x0c=0x2
only 0251, 0261, 02BC, 02C6, 02C7, 02C9, 02CA, 02CB, 02D0, 02D8, 02D9, 02DA, 02DC, 02DD can be seen.  Rest of the
characters are displayed as <?>.
Summary: [PP] Latin Extended characters rendering problem → [PP][BETA] Latin Extended characters rendering problem
Target Milestone: M16 → M13
Teruko says this is a Beta stopper, so moved from M16 to M13.
Have the fix for Latin Extend A (U+0100-U+017F) except U+012C, U+012D and U+017F
due to the way Apple make their font. The fix use ATSUI in a limited way.
Do not have fix for Latin Extended B or IPA range. But it should be treat as
lower priority...
Whiteboard: fix for some chars in local tree.
Target Milestone: M13 → M20
I check in the fix for the Latin Extend A part. (as the limitation stated
above). Since the remaining part is low priority, move it to M20.
Keywords: pp
Due to Beta indication in Summary, putting beta1 into keyword field.
Keywords: beta1
Put on PDT- per ftang comments.
Whiteboard: fix for some chars in local tree. → [PDT-]fix for some chars in local tree.
Summary: [PP][BETA] Latin Extended characters rendering problem → Latin Extended characters rendering problem
FYI, these are the descriptive names for the Latin Extend A characters
mentioned earlier:
  U+012C: LATIN CAPITAL LETTER I WITH BREVE
  U+012D: LATIN SMALL LETTER I WITH BREVE
  U+017F: LATIN SMALL LETTER LONG S

We could choose to tranliterate these to a similar ASCII glyph.
reassign garywade@desisoftsystems.com
Assignee: ftang → garywade
Status: ASSIGNED → NEW
Status: NEW → ASSIGNED
move to future
Target Milestone: M20 → Future
Keywords: beta1intl, nsbeta1
gary no longer work for us. reassing to ftang
Assignee: garywade → ftang
Status: ASSIGNED → NEW
We already did some transliteration now. Most of the Latin characters in this
range which could easily find a ASCII as base character are transliterate. I
don't think the rest of the characters are worth for us to fix for nsbeta1. Keep
this as Futre. Mark it P5. nsbeta1- for this bug.
Status: NEW → ASSIGNED
Whiteboard: [PDT-]fix for some chars in local tree. → [nsbeta1-]
Changed QA contact to andreasb@netscape.com.
QA Contact: teruko → andreasb
Changing QA contact to ylong@netscape.com.
QA Contact: andreasb → ylong
Blocks: 104166
this should be fixed now 
Status: ASSIGNED → RESOLVED
Closed: 22 years ago
Resolution: --- → FIXED
Mark as verified with this old problem cause the extension A characters are
displayed fine.  See comment #12 for extension B characters displayed problem.
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.