Bug 203748 - [as_IN] font failed to match
Summary: [as_IN] font failed to match
Keywords:
Status: CLOSED RAWHIDE
Alias: None
Product: Fedora
Classification: Fedora
Component: fontconfig
Version: rawhide
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Behdad Esfahbod
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks: Indic
TreeView+ depends on / blocked
 
Reported: 2006-08-23 15:37 UTC by A S Alam
Modified: 2013-07-03 00:39 UTC (History)
2 users (show)

Fixed In Version: fontconfig-2.4.1-2.fc6
Clone Of:
Environment:
Last Closed: 2006-09-28 09:07:27 UTC
Type: ---
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
FreeDesktop.org 8050 0 None None None Never

Description A S Alam 2006-08-23 15:37:26 UTC 
Description of problem:
LANG=as_IN.UTF-8 fc-match

Version-Release number of selected component (if applicable):
fonts-bengali-2.0.1-1

How reproducible:
Everytime

Steps to Reproduce:
1. run above command
2.
3.
  
Actual results:
DejaVuLGCSans.ttf: "DejaVu LGC Sans" "Book"

Expected results:
some fonts for Lohit
Comment 1 Lawrence Lim 2006-08-24 00:23:42 UTC 
Reassigning to the more appropriate component. Prolly need to reassign
maintainer too.
Comment 2 Leon Ho 2006-08-28 06:51:32 UTC 
Smell like a fontconfig problem, as the required codepoints in Bengali are
exactly the same as Assamese. Reassigning to fontconfig.
Comment 3 Behdad Esfahbod 2006-09-01 20:40:21 UTC 
"Created as.orth which references bn.orth" upstream.  Will be in next upgrade of
fontconfig.
Comment 4 Akira TAGOH 2006-09-27 11:44:23 UTC 
looks like working fine now.

$ rpm -q fonts-bengali fontconfig
fonts-bengali-2.0.2-1
fontconfig-2.4.1-2.fc6
$ LANG=as_IN.UTF-8 fc-match
lohit_bn.ttf: "Lohit Bengali" "Regular"

changing to MODIFIED.
Comment 5 Nicole Dai 2006-09-28 09:07:27 UTC 
Confirmed it has been fixed in latest FC6:
# rpm -q fonts-bengali fontconfig
fonts-bengali-2.0.2-1
fontconfig-2.4.1-2.fc6
# LANG=as_IN.UTF-8 fc-match
lohit_bn.ttf: "Lohit Bengali" "Regular"
Note You need to log in before you can comment on or make changes to this bug.