Closed Bug 284165 Opened 20 years ago Closed 20 years ago

Minimum font size in Western changes the font sizes in Unicode pages

Categories

(Firefox :: Settings UI, defect)

Product:
Firefox
Component:
Settings UI
Platform:
PowerPC
macOS
Type:
defect
Priority:
Not set
Severity:
major

Tracking

()

Status:
RESOLVED INVALID

People

(Reporter: stephen, Assigned: bugs)

References

(
URL
)

Details

(Keywords: intl)

User-Agent: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.7.6) Gecko/20050225 Firefox/1.0.1 Build Identifier: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.7.6) Gecko/20050225 Firefox/1.0.1 Changing the minimum font size in Western also affects the font sizes used to render Unicode pages. Reproducible: Always Steps to Reproduce: 1.Go to the sample Google page which is a Traditional Chinese page in UTF-8 encoding. 2.Open Firefox's Western fonts settings and change the minimum font size to some big number list 24. 3.OK the preferences change Actual Results: The sample page is rendered with the new minimum font size even thought the page is in Unicode and there's a different minimum font size setting for Unicode. Expected Results: The sample page should be rendered exact the same as before the minimum font size change. This is tested on Mac and Windows versions of Firefox with the same result.
What's the language at the top of your Mac OS X language list? If it's English or other Western European language, this is expected. See bug 283295. Btw, why don't you urge google to specify 'lang=zh-TW' explicitly for TC page, 'lang=fr' for French pages, 'lang=ja' for Japanese pages, etc? Google doesn't seem to be a very good citizen of the internet in terms of the standard compliance, which is rather worrisome.
Status: UNCONFIRMED → RESOLVED
Closed: 20 years ago
Keywords: intl
Resolution: --- → INVALID
Oops. it's bug 283925
really sorry for bug spam. I really meant bug 280007
(In reply to comment #1) > What's the language at the top of your Mac OS X language list? If it's English > or other Western European language, this is expected. See bug 283295. OK. That explains it. Thanks > Btw, why don't you urge google to specify 'lang=zh-TW' explicitly for TC page, > 'lang=fr' for French pages, 'lang=ja' for Japanese pages, etc? Google doesn't > seem to be a very good citizen of the internet in terms of the standard > compliance, which is rather worrisome. You mean like Firefox? :) <http://www.mozilla.org/products/firefox/> I can actually understand why Google doesn't have "lang=zh-TW" in the TC pages. Google returns SC pages hits from the same search terms, which is a very neat feature. I can type in a search term in TC and get SC pages contains such term, or vice versa. It sometimes even finds Japanese pages with the same kanjis. I am not sure what will happen to those entries if the page is set to zh-TW. Also, from what I undersatnd by reading the W3C pages, lang setting is still a draft. Most pages out there doesn't have it. I guess it all comes down to what Firefox wants to be. A standard enforcer or a user friendly browser.
Hmm... I got it wrong. The toturial is a draft. Not the standard. Sorry.
Setting the overall 'lang' of a page (in html or body) does NOT affect browser's ability to render contents in languages other than the the overall language at all. Moreover, google already has a very good language detector (otherwise, their 'translate' butoon wouldn't work) so that they can label *individual* hits with languages it detected. <body lang="zh-TW"> <ul> <li lang="en-US">Hit #1</li> <li lang="zn-TW">Hit #2</li> <li lang="ja">Hit #3</li> <li lang="zh-CN">Hit #4</li> ..... </ul> As for 'lang' and 'xml:lang', they have been in the standard (read the spec for HTML 4.x, XHTML 1.x and XML). Needless to say, there's NO obligation to specify them (so it's not a matter of the standard compliance per se), but it's a good I18N practice and accessibility practice to specify them whenever possible.(actually, WCAG (http://www.w3.org/WAI) requires that lang be specified explicitly) Anyway, google's html and css are very rusty and needs a lot of 'standard-compliance love'.
sorry for bugspam, long-overdue mass reassign of ancient QA contact bugs, filter on "beltznerLovesGoats" to get rid of this mass change
QA Contact: mconnor → preferences
You need to log in before you can comment on or make changes to this bug.