[PyX-devel] [ pyx-Bugs-760764 ] TFMError "width_index should not be zero"

[SourceForge.net <no...@so...>]

Bugs item #760764, was opened at 2003-06-25 20:52
Message generated for change (Tracker Item Submitted) made by Item Submitter
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=442886&aid=760764&group_id=45430

Category: None
Group: None
Status: Open
Resolution: None
Priority: 5
Submitted By: Gert Ingold (gertingold)
Assigned to: Nobody/Anonymous (nobody)
Summary: TFMError "width_index should not be zero"

Initial Comment:
Hello,

I am trying to use a commercial font (Garamond Standard
from Softmaker) with PyX 0.3.1. Unfortunately, a
TFMError "width_index should not be zero" is raised. A
closer look at the TFM files shows indeed that CHARWD
is zero for certain characters, namely "17x in the T1
encoding (8t) and "17x and "1Fx in the TS1 encoding
(8c). Character "17x is defined as /compoundwordmark
while "1Fx is /ffl. The font tables in
CTAN:fonts/utilities/fontinst-prerelease/doc/talks/et99-font-tables.pdf
don't show glyphs for compoundwordmark in the T1 and
TS1 encodings and for the ffl ligature in the TS1
encoding (of course, the ffl ligature is present in the
T1 encoding).

The same problem arises if I use the package mathptmx
while the use of the palatino package leads to:
After parsing this message, the following was left:
  *(/usr/TeX/texmf/tex/latex/psnfss/ot1phv.fd)
If the described effect is caused by PyX checking the
CHARWD's of all
characters, this should, in my opinion, be considered a
bug.

Best regards,
Gert

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=442886&aid=760764&group_id=45430