Closed Bug 53288 Opened 26 years ago Closed 25 years ago

Japanese fonts are not used in HTML form when page charset=iso8859-1

Categories

(Core :: Internationalization, defect, P3)

x86
Linux
defect

Tracking

()

VERIFIED DUPLICATE of bug 73697
Future

People

(Reporter: masaki.katakai, Assigned: ftang)

References

()

Details

(Keywords: intl)

45678 is still reproducible on HTML form when page charset is not japanese. 1) Start Mozilla in japanese locale 2) visit www.yahoo.com 3) type japanese in search field Korean fonts are used, Wrong japanese comma and fullstop are displayed. But it works when 1) Start Mozilla in japanese locale 2) visit www.yahoo.co.jp 3) type japanese in search field Those pages does not have charset tag so they are considered as 8859-1 charset.
I can't reproduce this bug on www.yahoo.com. But on kr.yahoo.com I can reproduce.
Reassign to erik.
Assignee: nhotta → erik
We need to decide what to do here. What if the document was Korean, and the HTML form widgets already contained some Korean text (initialized by the Web site)? Would we want to use Japanese fonts to display the Korean text inside the HTML form just because the user happened to be using a Japanese locale? I don't think so. However, if the document is in iso-8859-1, and the locale is Japanese, then it would be nice if Mozilla picked up Japanese fonts instead of Korean fonts for Han characters. Accepting bug.
Status: NEW → ASSIGNED
Target Milestone: --- → Future
Keywords: intl
erik resign. reassign all his bug to ftang for now.
Assignee: erik → ftang
Status: ASSIGNED → NEW
I understand and have verified this can be solved by the tmp patch for bug 73697. Brian@Netscape will post the patch soon.
mark all future new as assigned after move from erik to ftang
Status: NEW → ASSIGNED
I believe this bug has been fixed as bug 73697. Marked as dup. *** This bug has been marked as a duplicate of 73697 ***
Status: ASSIGNED → RESOLVED
Closed: 25 years ago
Resolution: --- → DUPLICATE
Verified as dup.
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.