Closed Bug 43395 Opened 25 years ago Closed 24 years ago

Japanese fonts cannot be set in User Defined Character coding

Categories

(Core :: Internationalization, defect, P3)

defect

Tracking

()

VERIFIED WONTFIX

People

(Reporter: teruko, Assigned: erik)

References

()

Details

(Keywords: intl, Whiteboard: [nsbeta2-])

When you set the User defined font to Japanese fonts, MS Gothic or other, the characters are not displayed as the fonts after you change the menu View|Character coding->More->User Defined. Steps of reproduce 1. Open Preferences dialog 2. In Preferences dialog, Select Fonts from Appearance category, Choose User Defiend in Fonts for. Change every fonts to "MS Gothic" and change the size of the fonts to "24" Then, close the preferences dialog 3. Go to above URL 4. Select menu View|Character coding->More->User Defined The font size is changed to "24", but the font is not changed to "MS Gothic". So, the Japanese characters are displayed as garbage. Tested 2000-06-21-08 Win32 and Mac build.
Status: NEW → ASSIGNED
Target Milestone: --- → M17
I would like to nominate this bug for beta2 because User-Define is beta2 criteria.
Keywords: nsbeta2
Putting on [NEED INFO] radar. PDT needs to know impact to user and risk of fix to make a call on this bug. Erik, please let us know what you think.
Whiteboard: [NEED INFO]
Impact to user: The User Defined feature is only used by users who have documents and fonts for an encoding that we don't already support. In Netscape6, we support a lot of encodings, so this feature affects a relatively small number of users. For the users that are affected, it appears to work for some fonts (e.g. the Bengali font I downloaded the other day) and not on others (e.g. the Japanese font mentioned in this bug report). Risk of fix: I don't really know what the fix would be, but it would be isolated to the User Defined code, so it would be low risk.
I tested this in 2000-06-29-08 Win32 build. I found that this does not work not only Japanese font but also Chinese and Korean fonts. GulimCh, Mingliu, Ms Hei, Ms Gothic, Ms P Gothic, MS Mincho, and MS Mincho do not work. Tahama, Bitstream, Comic Sans MS, Lucida Console works fine.
Putting on [nsbeta2-] radar. Not critical to beta2. Adding "nsbeta3" keyword for consideration of a fix for that milestone.
Keywords: nsbeta3
Whiteboard: [NEED INFO] → [nsbeta2-]
remove nsbeta3. User defined is used for simple single byte languages. We already support Japanese. Is there are a NEED to use Japanese in the user-defined ?
Keywords: nsbeta3
There are virtually no multibyte **private fonts** in circulation which would require the use of User-defined. All the fonts I am aware of can be used under the multibyte encodings we support. User-defined are meant for fonts which do not use the encodings or charset tables we support and virtually all such fonts are for one-byte languages and are for encodings we don't list in our charset menu. We should mark this bug as Wontfix.
Keywords: intl
Mark this bug as won't fix since we already support Japanese and there are no need for them to use Japanese font with USer defined
Status: ASSIGNED → RESOLVED
Closed: 24 years ago
Resolution: --- → WONTFIX
Verified as Wontfix.
Status: RESOLVED → VERIFIED
*** Bug 77786 has been marked as a duplicate of this bug. ***
You need to log in before you can comment on or make changes to this bug.