[Bug 578038] lang-specific overrides rule doesn't work as expected

[bugzilla at redhat.com]

Please do not reply directly to this email. All additional
comments should be made in the comments box of this bug.


https://bugzilla.redhat.com/show_bug.cgi?id=578038

--- Comment #2 from Akira TAGOH <tagoh at redhat.com> 2010-04-28 06:58:19 EDT ---
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

-- 
Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.