Bug 578041

Summary: lang-specific overrides rule doesn't work as expected
Product: [Fedora] Fedora Reporter: Akira TAGOH <tagoh>
Component: madan-fontsAssignee: Parag Nemade <pnemade>
Status: CLOSED ERRATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: low    
Version: rawhideCC: i18n-bugs, petersen, pnemade, psatpute
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: madan-fonts-2.000-2.fc13 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
: 586870 (view as bug list) Environment:
Last Closed: 2010-04-27 02:25:42 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On: 578015    
Bug Blocks: 507684, 586870    

Description Akira TAGOH 2010-03-30 03:51:19 UTC
Description of problem:
All of detailed information is available on my post at the fonts list:
http://lists.fedoraproject.org/pipermail/fonts/2010-March/001117.html

binding="same" in the fontconfig config file prevents to apply the rule for the
specific
language only properly. As a result, fonts is used for non-targetted languages
and it may gives different look and feel in some cases.

I'd propose to get rid of binding="same" from:
 65-madan.conf

Comment 1 Fedora Update System 2010-04-20 05:01:12 UTC
madan-fonts-2.000-2.fc13 has been submitted as an update for Fedora 13.
http://admin.fedoraproject.org/updates/madan-fonts-2.000-2.fc13

Comment 2 Fedora Update System 2010-04-21 02:20:56 UTC
madan-fonts-2.000-2.fc13 has been pushed to the Fedora 13 testing repository.  If problems still persist, please make note of it in this bug report.
 If you want to test the update, you can install it with 
 su -c 'yum --enablerepo=updates-testing update madan-fonts'.  You can provide feedback for this update here: http://admin.fedoraproject.org/updates/madan-fonts-2.000-2.fc13

Comment 3 Akira TAGOH 2010-04-22 12:12:15 UTC
Testing result:
# rpm -q madan-fonts
madan-fonts-2.000-2.fc13.noarch
# fc-match monospace:lang=en
DejaVuSansMono.ttf: "DejaVu Sans Mono" "Book"
# fc-match monospace:lang=en-us
DejaVuSansMono.ttf: "DejaVu Sans Mono" "Book"
# fc-match monospace:lang=ne
Lohit-Devanagari.ttf: "Lohit Devanagari" "Regular"
# fc-match monospace:lang=ne-np
Lohit-Devanagari.ttf: "Lohit Devanagari" "Regular"
# fc-match serif:lang=en
DejaVuSerif.ttf: "DejaVu Serif" "Book"
# fc-match serif:lang=en-us
DejaVuSerif.ttf: "DejaVu Serif" "Book"
# fc-match serif:lang=ne
Lohit-Devanagari.ttf: "Lohit Devanagari" "Regular"
# fc-match serif:lang=ne-np
Lohit-Devanagari.ttf: "Lohit Devanagari" "Regular"

No explicit rules for monospace and serif in madan-fonts.

# fc-match sans:lang=en
DejaVuSans.ttf: "DejaVu Sans" "Book"
# fc-match sans:lang=en-us
DejaVuSans.ttf: "DejaVu Sans" "Book"
# fc-match sans:lang=ne
Lohit-Devanagari.ttf: "Lohit Devanagari" "Regular"
# fc-match sans:lang=ne-np
Lohit-Devanagari.ttf: "Lohit Devanagari" "Regular"

For this issue, the above result isn't bad. the reasons why fontconfig didn't pick up Madan font is:

 * madan-fonts doesn't have certain glyph coverages that fontconfig is expecting in ne.orth.

   $ fc-match -v Madan | grep -E "^    ]*lang"
           lang: (s)

 * since the locale-specific overrides rule adds Madan as the weak binding now, Lohit Devanagari has a priority since it appears in 65-nonlatin.conf. 65-madan.conf should be renamed to 65-0-madan.conf or something like that.

# for i in $(ls /usr/share/locale|grep -v -E "^ne$"); do fc-match sans:lang=$i|grep "Madan"; [ $? = 0 ] && echo $i; done
#

No affects to other languages so far. but I'm not really sure when the above issues got fixed once.

Anyway, it's good enough for this issue but need further fixes to make this package useful for Nepali.

Comment 4 Fedora Update System 2010-04-27 02:25:38 UTC
madan-fonts-2.000-2.fc13 has been pushed to the Fedora 13 stable repository.  If problems still persist, please make note of it in this bug report.