In XML specification,
xml:lang can be used to specify the language of the content. If these
attribute presents, we should use it to choose the right font for specified
languages. Similar problem for HTML was fixed in bug 105199. In that bug,
html "lang" attribute is mapped to RuleData and populated in Rule tree.
I think we should do same thing here.
Created attachment 61620 [details]
test case to show the problem
I zip a xml file and associate css file into a package of zip file.
(browser seems unable to download css attachment.)
cc to a couple of people.
This bug is blocking us to fix font problem for xul file.
See also bug 35768.
The blocker has been futured, and bug 35768 has been moved to 1.1. Futuring
this, but hopefully I'll get to this in 1.1.
FYI, according to XHTML 1.0 <URL:http://www.w3.org/TR/xhtml1/#C_7>, if both the
lang and xml:lang attributes are present, xml:lang takes precedence.
Starting with XHTML 1.1, the lang attribute is no longer allowed and xml:lang
must be used instead. Since Mozilla does not handle the xml:lang attribute as
suggested, XHTML 1.1 documents in languages other than the default may not
display properly. For example, on one of my systems with LANG=en_US, Mozilla
1.1 [Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.1) Gecko/20020913
Debian/1.1-1] and Netscape 6.2, this page
<URL:http://graphics.stanford.edu/~naemura/memo/xhtml-css.html> fails to display
Japanese characters. My own XHTML 1.1 welcome page
<URL:http://www.bacchus.com/~ccwf/>, containing Chinese, Japanese, and Korean
characters, displays those characters properly with Netscape 6.2 but NOT with
*** This bug has been marked as a duplicate of 41978 ***