Closed
Bug 5941
Opened 27 years ago
Closed 25 years ago
CSS1 fonts not mapped correctly for double-byte content
Categories
(Core :: Internationalization, defect, P2)
Tracking
()
VERIFIED
WORKSFORME
M14
People
(Reporter: jpm, Assigned: erik)
References
()
Details
(This bug imported from BugSplat, Netscape's internal bugsystem. It
was known there as bug #122897
http://scopus.netscape.com/bugsplat/show_bug.cgi?id=122897
Imported into Bugzilla on 05/04/99 22:37)
When using style sheets (CSS1) to define fonts for HTML elements for a Shift_JIS
document, it appears that fonts not able to display SJIS are used, even though a
valid SJIS font (Osaka) is defined in the style sheet. Also, the default styles
(serif, sans-serif, ...) seem to use wrong fonts for SJIS display.
(The use of "serif" etc. is described in
http://developer.netscape.com/docs/manuals/communicator/dynhtml/jss34.htm#103040
2)
Using the US client on an US system with a language kit installed should still
have valid font mappings for sans-serif etc. for the encodings we support.
Reporter | ||
Comment 1•27 years ago
|
||
Added URL for testing:
http://rocknroll/users/jpm/publish/l10n/tests/122987.html.
Notice that the document displays correctly on a Windows 4.x client.
Comment 3•27 years ago
|
||
Half of this is not a bug but half of them is.
The bug part -
> Using the US client on an US system with a language kit installed should still
> have valid font mappings for sans-serif etc. for the encodings we support.
Agree, dp, please assign engineer to solve this.
Not a bug part-
The reason this page does not render correctly (except H4, which use san-serif
as mention above) is it list Osaka font AFTER Helvetica. Since all Mac have
Helvetica font installed, it will use Helvetica to render the Japanese text, the
solution is (1) delete Helevetica from the list (why you put there any way ?) or
(2) put Osaka before Helvetica.
Reporter | ||
Comment 4•27 years ago
|
||
Frank,
Notice how the Windows client renders the page correctly using Japanese fonts,
even though the font list specifies "Ariel", but no Japanese fonts.
If using "Ariel" to display Japanese content works on Windows, so should using
"Helvetica" on Mac OS. There probably is some special-case code for dealing with
this on WinFE that the MacFE (possibly XFE) would need.
Comment 5•27 years ago
|
||
can someone figure out if this is regression since 4.05?
Comment 6•27 years ago
|
||
I tested 4.05 MAC PPC and 7-17-98 4.06 PPC build. This happens in both build.
Comment 7•27 years ago
|
||
gotta move to to 5.0. might consider in 4.5 if a fix appears..
Comment 8•26 years ago
|
||
My favorite question, "Is this bug still relevant in the new 5.0 world?"
------- Additional Comments From paulmac May-04-1999 17:59 -------
Okay, time to close out old bugsplat bugs - Please move to bugzilla if this
one is still relevant or mark won't fix, please.
Updated•26 years ago
|
Assignee: harishd → erik
Status: ASSIGNED → NEW
OS: All
Priority: P1 → P2
Target Milestone: M6
Assignee | ||
Updated•26 years ago
|
Status: NEW → ASSIGNED
Target Milestone: M6 → M15
Assignee | ||
Comment 9•26 years ago
|
||
I will decide later which milestone to fix this in.
Assignee | ||
Updated•26 years ago
|
Target Milestone: M15 → M10
Assignee | ||
Updated•26 years ago
|
Target Milestone: M10 → M12
Assignee | ||
Updated•26 years ago
|
Target Milestone: M12 → M14
Comment 10•25 years ago
|
||
Teruko, Is this bug still valid?
Updated•25 years ago
|
Status: ASSIGNED → RESOLVED
Closed: 25 years ago
Resolution: --- → WORKSFORME
Updated•25 years ago
|
Status: RESOLVED → VERIFIED
Comment 11•25 years ago
|
||
This does not happen in 110909 MAC build.
You need to log in
before you can comment on or make changes to this bug.
Description
•