Bug 60885 - ttmkfdir died when encoding.dir is present
Summary: ttmkfdir died when encoding.dir is present
Keywords:
Status: CLOSED RAWHIDE
Alias: None
Product: Red Hat Raw Hide
Classification: Retired
Component: XFree86
Version: 1.0
Hardware: i386
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Mike A. Harris
QA Contact: David Lawrence
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2002-03-08 07:34 UTC by Young-Ho, Cha
Modified: 2007-04-18 16:40 UTC (History)
0 users

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2002-03-08 07:34:14 UTC
Embargoed:


Attachments (Terms of Use)

Description Young-Ho, Cha 2002-03-08 07:34:10 UTC
From Bugzilla Helper:
User-Agent: Mozilla/5.0 Galeon/1.1.3 (X11; Linux i686; U;) Gecko/20020206

Description of problem:


Version-Release number of selected component (if applicable):
XFree86 4.2.0-6.32

How reproducible:
Always

Steps to Reproduce:
1. cd /usr/X11R6/lib/X11/fonts/TTF/
2. ttmkfdir
3.
	

Expected Results:  

[ganadist@ganadist TTF]$ ttmkfdir 
unexpected token FIRSTINDEX in file
/usr/X11R6/lib/X11/fonts/encodings/large/ksc5601.1992-3.enc.gz, line 8
unexpected token 0x84 in file
/usr/X11R6/lib/X11/fonts/encodings/large/ksc5601.1992-3.enc.gz, line 8
unexpected token 0x31 in file
/usr/X11R6/lib/X11/fonts/encodings/large/ksc5601.1992-3.enc.gz, line 8
unexpected token FIRSTINDEX in file
/usr/X11R6/lib/X11/fonts/encodings/large/big5.eten-0.enc.gz, line 7
unexpected token 0xA0 in file
/usr/X11R6/lib/X11/fonts/encodings/large/big5.eten-0.enc.gz, line 7

...

Additional info:

ttmkfdir that is contained in XFree86 4.2 can't handle word, "FIRSTINDEX"  in
/usr/X11R6/lib/X11/fonts/encodings/large/*.enc.gz 

please modify "encoding.l" in ttmkfdir source

Comment 1 Mike A. Harris 2002-03-11 02:25:45 UTC
This problem was worked around a long time ago by removing the FIRSTINDEX
lines from the encoding files.  If you've got a patch to make ttmkfdir work
properly with FIRSTINDEX however, please attach and reopen the report.

Thanks.


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