Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at bugzilla.redhat.com.
Bug 578038 - lang-specific overrides rule doesn't work as expected
Summary: lang-specific overrides rule doesn't work as expected
Keywords:
Status: CLOSED RAWHIDE
Alias: None
Product: Fedora
Classification: Fedora
Component: lohit-punjabi-fonts
Version: rawhide
Hardware: All
OS: Linux
low
medium
Target Milestone: ---
Assignee: Pravin Satpute
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On: 578015
Blocks: F13Target
TreeView+ depends on / blocked
 
Reported: 2010-03-30 03:48 UTC by Akira TAGOH
Modified: 2010-04-28 13:20 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2010-04-16 17:40:13 UTC
Type: ---
Embargoed:

Attachments (Terms of Use)

Description Akira TAGOH 2010-03-30 03:48:16 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:
 66-lohit-punjabi.conf
Comment 1 Pravin Satpute 2010-04-16 17:40:13 UTC 
fixed in lohit-punjabi-fonts-2.4.4-1 for fc13 as well in devel
Comment 2 Akira TAGOH 2010-04-28 10:58:19 UTC 
just for the note in the future, here is the testing result as I usually did for other fonts packages in this issue:
# rpm -qa lohit-punjabi-fonts
lohit-punjabi-fonts-2.4.4-1.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=pa
Lohit-Punjabi.ttf: "Lohit Punjabi" "Regular"
# fc-match monospace:lang=pa-in
Lohit-Punjabi.ttf: "Lohit Punjabi" "Regular"
# fc-match monospace:lang=pa-pk
DejaVuSansMono.ttf: "DejaVu Sans Mono" "Book"
# 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=pa
Lohit-Punjabi.ttf: "Lohit Punjabi" "Regular"
# fc-match serif:lang=pa-in
Lohit-Punjabi.ttf: "Lohit Punjabi" "Regular"
# fc-match serif:lang=pa-pk
DejaVuSerif.ttf: "DejaVu Serif" "Book"

No explicit rules for monospace and serif in lohit-punjabi-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=pa
Lohit-Punjabi.ttf: "Lohit Punjabi" "Regular"
# fc-match sans:lang=pa-in
Lohit-Punjabi.ttf: "Lohit Punjabi" "Regular"
# fc-match sans:lang=pa-pk
DejaVuSans.ttf: "DejaVu Sans" "Book"

That looks good. getting different result for pa-pk is expected behaviour since fontconfig has different orth file for pa-pk.

# for i in $(ls /usr/share/locale|grep -v -E "^(pa)$"); do fc-match sans:lang=$i|grep -E "^(Lohit Punjabi)$"; [ $? = 0 ] && echo $i; done
Note You need to log in before you can comment on or make changes to this bug.