Closed
Bug 119284
Opened 24 years ago
Closed 24 years ago
Invalid language attribute selects Arabic glyphs
Categories
(Core :: Internationalization, defect)
Tracking
()
VERIFIED
DUPLICATE
of bug 128338
People
(Reporter: jes, Assigned: smontagu)
References
()
Details
(Keywords: fonts, intl)
Attachments
(2 files)
|
896 bytes,
patch
|
Details | Diff | Splinter Review | |
|
1.67 KB,
patch
|
Details | Diff | Splinter Review |
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:0.9.7) Gecko/20011226
BuildID: 2001122617
<font> tags containing an invalid 'lang' attribute (e.g. lang="0") select an
Arabic glyph set.
GIGO of course, except that the AOL mailer apparently generates these tags, thus
they are very commonly encountered. IE6 and the other browsers I have access to
simply ignore invalid langage codes.
Reproducible: Always
Steps to Reproduce:
1.render any html with a <font lang="0"> tag. The default font, or a font
specified in the <font> tag must be a Unicode font (otherwise it won't have
alternate encoding).
Actual Results: Text is rendered in Arabic glyphs.
Expected Results: Ignore the invalid language attribute.
Comment 1•24 years ago
|
||
tentatively ->il8n
Assignee: attinasi → yokoyama
Component: Layout → Internationalization
Keywords: fonts
QA Contact: petersen → ruixu
Comment 2•24 years ago
|
||
assigning to smontagu for i18n-bidi
smontagu: do you know why it results to arabic?
Assignee: yokoyama → smontagu
| Assignee | ||
Comment 3•24 years ago
|
||
I can't reproduce the bug, but I think there is a problem with the handling of
unrecognized language attributes at
http://lxr.mozilla.org/mozilla/source/intl/locale/src/nsLanguageAtomService.cpp#204
| Assignee | ||
Comment 4•24 years ago
|
||
| Assignee | ||
Comment 5•24 years ago
|
||
Comment 6•24 years ago
|
||
I can not reproduce the original problem either (don't see the aribic part).
But since simon has a patch, I'd confirm this bug in order to get fix check in.
Status: UNCONFIRMED → NEW
Ever confirmed: true
| Assignee | ||
Comment 7•24 years ago
|
||
ftang, can you r= the patch?
| Assignee | ||
Comment 8•24 years ago
|
||
Reporter, do you make your own builds? If so, can you try applying attachment
65135 [details] [diff] [review] to test if it solves the problem? If nobody here can reproduce the bug,
this may be difficult to review ;-)
> Reporter, do you make your own builds?
Never have, but I should be able to try one.
It seems to be an interaction with the particular X installation.
I can only reproduce the problem when it is displayed on my workstation.
Even the same Linux install (RH7.2) and the same mozilla binary on another
machine don't show the problem (unless I display it on my workstation). I'm not
sure what the differences (upgrades, etc) are between the two installs.
| Assignee | ||
Updated•24 years ago
|
Status: NEW → ASSIGNED
Comment 10•24 years ago
|
||
This is a dup of bug 128338. Simon, could you review that patch?
*** This bug has been marked as a duplicate of 128338 ***
Status: ASSIGNED → RESOLVED
Closed: 24 years ago
Resolution: --- → DUPLICATE
Comment 11•24 years ago
|
||
It's a dup of bug 128338 for me too.
Mark it as verified, please re-open if disagree.
Status: RESOLVED → VERIFIED
| Reporter | ||
Comment 12•24 years ago
|
||
Verified fixed for me using locally compiled nightly:
Mozilla/5.0 (X11; U; Linux i686; en-US; rv:0.9.9+) Gecko/20020328
You need to log in
before you can comment on or make changes to this bug.
Description
•