[XeTeX] Problems with some fonts and font names

[Peter Dyballa]

Hello!

There are some fonts in DFONT files which are not handled correctly.  
XeTeX/XeLaTeX seems to handle the issue fine:


	This is XeTeX, Version 3.141592-2.2-0.997 (Web2C 7.5.6)  
(format=xelatex 2007.12.21)  22 DEC 2007 11:26
	
	(/usr/local/gwTeX/texmf.local/tex/xelatex/fontspec/fontspec.sty
	Package: fontspec 2007/09/01 v1.16 Advanced font selection for XeLaTeX
	
	(/usr/local/gwTeX/texmf.texlive/tex/latex/tools/calc.sty
	Package: calc 2005/08/06 v4.2 Infix arithmetic (KKT,FJ)
	
	(/usr/local/gwTeX/texmf.local/tex/xelatex/xkeyval/xkeyval.sty
	Package: xkeyval 2005/11/25 v2.5e package option processing (HA)
	
	(/usr/local/gwTeX/texmf.local/tex/xelatex/xkeyval/xkeyval.tex
	\XKV at toks=\toks14
	\XKV at depth=\count94
	File: xkeyval.tex 2005/11/25 v2.5e key=value parser (HA)
	
	(/usr/local/gwTeX/texmf.texlive/tex/latex/base/fontenc.sty
	Package: fontenc 2005/09/27 v1.99g Standard LaTeX package
	
	(/usr/local/gwTeX/texmf.local/tex/xelatex/euenc/eu1enc.def
	File: eu1enc.def 2006/08/13 v0.1a Experimental unicode font encoding
	)
	
	(/usr/local/gwTeX/texmf.local/tex/xelatex/euenc/lm/eu1lmr.fd
	File: eu1lmr.fd 2007/01/14 v1.3 Font defs for Latin Modern
	))
	
	fontspec.cfg loaded.
	(/usr/local/gwTeX/texmf.local/tex/xelatex/fontspec/fontspec.cfg))
	\c at zf@famc at Gill Sans=\count95
	Package fontspec Info: Defining font family for 'Gill Sans' with  
options
	 [Mapping=tex-text,] on input line 69.

When I invoke

	xdv2pdf -v -o Bug-x.pdf Bug

it writes to LOG file

	Output written on Bug.xdv (1 page, 688 bytes).

but no PDF file exists. OK, making it read Bug.xdv produces a working  
PDF file. Invoking

	xdvipdfmx -v -o Bug-d.pdf Bug

nothing is added to the LOG file, but the shell contains:

	** ERROR ** Could not open specified DVI (or XDV) file: Bug
	
	Output file removed.

This tells me, too, that I need to add .xdv to the input file name!  
Doing so I get from xdvipdfmx-0.5:

	DVI Comment:  XeTeX output 2007.12.22:1612
	Bug.xdv -> Bug-d.pdf
	[1<GillSans(Gill Sans:Regular)@10.87pt<NATIVE-FONTMAP:GillSans/H/ 
65536/0>
	pdf_font>> Input encoding "Identity-H" requires at least 2 bytes.
	pdf_font>> The -m <00> option will be assumed for "GillSans/H/65536/0".
	>
	** ERROR ** Invalid font: -1 (0)
	
	Output file removed.

It's a TrueType font inside the Data-Fork Suitcase. It contains 257  
glyphs.

Quite similar is the situation with Futura, another TrueType font  
inside the Data-Fork Suitcase. It contains 417 glyphs.

	xdvipdfmx -vv -o Bug-d.pdf Bug.xdv

reports

	DVI Comment:  XeTeX output 2007.12.22:1648
	Bug.xdv -> Bug-d.pdf
	[1<Optima(Optima:Roman)@10.87pt<NATIVE-FONTMAP:Optima/H/65536/0>
	fontmap: Optima/H/65536/0 -> Optima/H/65536/0(Identity-H)
	
	pdf_font>> Input encoding "Identity-H" requires at least 2 bytes.
	pdf_font>> The -m <00> option will be assumed for "Optima/H/65536/0".
	>
	** ERROR ** Invalid font: -1 (0)
	
	Output file removed.

Again, xdv2pdf has no problem.

Other fonts that show the same behaviour:

	Osaka		Osaka.dfont
	Osaka-Mono	OsakaMono.dfont
	Fang Song	Fang Song.dfont
	Song		Song.dfont
	Times		Times.dfont
	Helvetica	Helvetica.dfont
	Courier		Courier.dfont
	Symbol		Symbol.dfont


Another problem is that XeTeX/XeLaTeX cannot access some fonts by  
their family or PostScript names:

	Family Name:		Casual		AppleCasual.dfont
	PostScript Name:	GenevaCY	GenevaCY.dfont

In both cases a TFM file name is assumed where there is none.

--
Greetings

   Pete

Bigamy is having one wife too many. Monogamy is the same.
				– Oscar Wilde