[XeTeX] missing everything

[Jonathan Kew]

On 18 Jan 2006, at 10:27 pm, Martin Henning wrote:

>
> On Jan 16, 2006, at 4:12 PM, Jonathan Kew wrote:
>
>> On 16 Jan 2006, at 12:43 pm, Yves Codet wrote:
>
>>> I recently upgraded to XeTeX 0.99b and in a document which I had  
>>> started writing before I upgraded italics don't appear anymore (a  
>>> sample file is attached below). There is a message I don't  
>>> understand in the .log file:
>>> 	LaTeX Font Warning: Font shape `U/CharisSIL/m/sl' undefined
>>> 	(Font)              using `U/CharisSIL/m/n' instead on input  
>>> line 27.
>>> I didn't ask for slanted letters.
>
> i just upgraded, too, now my document is more or less completely  
> broken....

I don't think your problem is the xetex upgrade.... see below...

> i'm using:
>
> \defaultfontfeatures{Mapping=tex-text}
> \setromanfont[%
> 		Numbers=Lining,%
> 		ItalicFont={Charis SIL Italic},%
> 		BoldFont={Charis SIL Bold},
> 		BoldItalicFont={Charis SIL Bold Italic}%
> 		]%
> 		{Charis SIL}
> \setsansfont[Scale=1.01]{Lucida Grande}
> \setmonofont[Scale=0.90]{Monaco}
>
> and get:
>
> LaTeX Font Warning: Font shape `T2A/CharisSIL+map:tex-text 
> +lnumit:CharisSILItal
> icbf:CharisSILBoldbfit:CharisSILBoldItalic/m/n' undefined
> (Font)              using `T2A/cmr/m/n' instead on input line 14.
>

This indicates that LaTeX is looking for the Charis font with T2A  
encoding, which doesn't exist; fonts loaded through fontspec use  
encoding "U".

> LaTeX Font Warning: Font shape `T2A/LucidaGrande+map:tex-text+scale: 
> 1.01/m/n' u
> ndefined
> (Font)              using `T2A/cmr/m/n' instead on input line 22.
>

(Same problem for Lucida)

> LaTeX Font Warning: Font shape `T2A/LucidaGrande+map:tex-text+scale: 
> 1.01/bx/n'
> undefined
> (Font)              using `T2A/LucidaGrande+map:tex-text+scale:1.01/ 
> m/n' instea
> d on input line 22.
>
> and so on...
>
> Is it a bug or is it me? Before upgrade it worked, but i also  
> changed the languages in my tetex-installation for correct use of  
> babel with russian, as suggested by bruno in another thread. using  
> a KOMA-class,

That's probably what is changing the font encoding, and breaking the  
fontspec fonts. I know little about Babel and nothing about KOMA  
(what's that?), but in general packages designed to support non-Latin  
text in pre-Unicode TeX systems are not going to work very smoothly  
with xetex and Unicode fonts, as they assume the use of other  
(usually non-standard) input and font encodings. For xetex, that's  
largely unnecessary (and actually interferes with simple operation).

> yet after
> selecting russian language, everything appears (for the first time)  
> correctly in russian.

....in Russian, but (I'm guessing) not in fonts you've requested via  
fontspec, but rather some legacy fonts chosen for you by the Russian  
package you're loading.

> seems to me it is not a bug in Charis, because i get it for all my  
> fonts...

Right, this is not at all the same issue as Yves ran into.

>
> in console.log i get:
>
> Jan 19 01:21:50 tigabook xdv2pdf: WARNING: Type1 font data returned  
> by OFAStreamPSDownload isn't in the correct format required by the  
> Adobe Type 1 Font Format specification.
>
> after each run of xelatex... which, frankly speaking, doesn't tell  
> me anything :)
>

This warning appears because 10.4 doesn't like the font format we're  
using to get old .pfb PostScript fonts (e.g., Computer Modern, etc)  
into the PDFs that xetex (actually xdv2pdf) generates. It's annoying  
but seems to be harmless.

> maybe one of you knows what this should tell me?

I don't know enough about Babel, and its Russian support in  
particular, to give a definite answer, but perhaps the notes above  
will point you or others in the right direction.

JK