need to add LANG to nsFont

VERIFIED WONTFIX

Status

()

Core
CSS Parsing and Computation
P3
normal
VERIFIED WONTFIX
19 years ago
12 years ago

People

(Reporter: Erik van der Poel, Assigned: Peter Linss)

Tracking

Trunk
All
Other
Points:
---
Dependency tree / graph

Firefox Tracking Flags

(Not tracked)

Details

(Reporter)

Description

19 years ago
Unicode unifies the CJK (Chinese, Japanese, Korean) range. HTML has introduced
the LANG attribute. The spec says that this is to be used for CJK
disambiguation, among other things. So if the CSS resolves to a generic font
like "serif", then we need to select the right font (C, J or K) depending on
the language.

The LANG attribute can be specified for individual elements, and is inherited
from parent elements. If the HTML document does not have any LANG attributes,
the HTTP headers should be examined for the Content-Language header. If that is
missing too, the LANG should be NULL in nsFont. In that case, we can use the
charset of the document as a fallback (heuristic). A separate bug report will
be filed for the charset.

Since LANG is an ASCII string, the nsFont field can be either char* or nsString.
If it is simpler to use nsString, please do so.

Updated

19 years ago
Target Milestone: M6

Comment 1

19 years ago
Erik is dependent upon this before M7.
(Assignee)

Updated

18 years ago
Target Milestone: M6 → M7

Updated

18 years ago
Blocks: 7228, 7521
(Assignee)

Updated

18 years ago
Status: NEW → ASSIGNED
Target Milestone: M7 → M8
(Assignee)

Updated

18 years ago
Target Milestone: M8 → M9
(Assignee)

Updated

18 years ago
Status: ASSIGNED → RESOLVED
Last Resolved: 18 years ago
Resolution: --- → WONTFIX
(Assignee)

Comment 2

18 years ago
Adding lang to nsFont is not the right location, the style system re-uses
nsFont for different content nodes which may be in dofferent languages.

Updated

18 years ago
Status: RESOLVED → VERIFIED

Comment 3

18 years ago
Verified WONTFIX

Comment 4

18 years ago
See peterl's 08/06/99 16:01 comment in bug 6451.
You need to log in before you can comment on or make changes to this bug.