Bug 84034 - Chinese(Simplified) (<span lang="zh_CN.GB18030">简体中文</span>) doesn't look right
Chinese(Simplified) (<span lang="zh_CN.GB18030">简体中文</span>) doesn't ...
Status: CLOSED RAWHIDE
Product: Red Hat Linux Beta
Classification: Retired
Component: pango (Show other bugs)
beta4
All Linux
medium Severity medium
: ---
: ---
Assigned To: Owen Taylor
:
Depends On:
Blocks: 82082
  Show dependency treegraph
 
Reported: 2003-02-11 01:12 EST by Matt Wilson
Modified: 2008-05-01 11:38 EDT (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2003-02-11 14:21:44 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Matt Wilson 2003-02-11 01:12:03 EST
Description of problem:
"Chinese(Simplified) (<span lang="zh_CN.GB18030">简体中文</span>)" shows 简体中
文 in non-anti-aliased font, instead of picking the right font for zh_CN

Expected results:
Use the right font for zh_CN
Comment 1 Matt Wilson 2003-02-11 01:54:22 EST
better example: 

Japanese (<span lang="ja_JP.UTF-8">日本語</span>)

"日本" are bitmap "語" is anti-aliased
Comment 2 Owen Taylor 2003-02-11 08:41:19 EST
What if you do it without the encodings? span="zh_CN" and span="ja"?
Pango doesn't know anything about encodings, it doesn't care anything
about encodings, it doesn't support encodings in language tags.

(Wow, this is the first time I've seen bugzilla not mangle i18n text
in a bug report...)
Comment 3 Owen Taylor 2003-02-11 11:02:15 EST
Pretty obvious bug, I'll build a package with a fix in a few minutes.

(Basically, the LANG attribute is misclassified as not affecting
the font.)
Comment 4 Owen Taylor 2003-02-11 11:05:37 EST
Hmm, no, that wasn't it... need to look further.
Comment 5 Owen Taylor 2003-02-11 14:21:44 EST
Fixed in 1.2.1-2.

* Tue Feb 11 2003 Owen Taylor <otaylor@redhat.com>
- Fix problem where language tag wasn't causing relookup of font (#84034)

Note You need to log in before you can comment on or make changes to this bug.