[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#493789: (fwd) Re: [tex-live] (fwd) Bug#493789: missing files prevent xelatex compiling Italian document

Answer from tex live list. Try to change the order, first babel, then

Best wishes


Dr. Norbert Preining <preining@logic.at>        Vienna University of Technology
Debian Developer <preining@debian.org>                         Debian TeX Group
gpg DSA: 0x09C5B094      fp: 14DF 2E6C 0307 BE6D AD76  A9C0 D2BF 4AA3 09C5 B094
You're one hundred percent positive that the ship which is
crashed on the bottom of this ocean is the ship which you
said you were one hundred percent positive could one
hundred percent positively never crash?
                 --- Douglas Adams, The Hitchhikers Guide to the Galaxy
--- Begin Message ---
Am Tue, 5 Aug 2008 18:40:07 +0200 schrieb Norbert Preining:

> Hi everyone,
> I know it is TL2008 time, but I still get bug reports for TL2007 on
> Debian.
> There is one quite funny:
> ----- Forwarded message from "W. Martin Borgert" <debacle@debian.org> -----
>> During testing of a fix for #492304, I stumbled about xelatex
>> not being able compile Italian (example attached). Upstream of
>> dblatex found, that lgrlmr.fd and lgrlmro.fd are missing. In
>> fact, copying those files to my CWD, fixes the problem for me.
>> See http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=492304#11
>> \documentclass{article}
>> \usepackage{fontspec}
>> \usepackage[italian]{babel}
>> \title{Italian}
>> \begin{document}
>> Italian
>> \end{document}
> ----- End forwarded message -----
> The point is here:
> - you have to use xelatex
> - you have to use 
> 	\usepackage{fontspec}
> fontspec defaults to lm-default, ie latin modern default fonts.
> But why does it switch to lgr encoding.

It doesn't. babel (more exactly italian.ldf) is doing it. 

I would say (I haven't checked carefully) that the problem is that
fontspec not only set the font family to latin modern but also define
lmr to be the default fall back family and so latex no longer falls back
to lgrcmr but searches lgrlmr. 

In any case: language files that set encodings are problematic in xetex,
they can break the unicode support. It is best to either avoid them (and
use polyglossia instead) or to at least to load them so early that xetex
aware packages have chance to reset and overwrite as much encoding and
definitions as possible.

> Our current babel ships these two files (lgrlmr.fd and lgrlmro.fd), so
> would it be a solution to just copy those files to the TL2007 dir and
> let it be gone? 

In this case it is enough if babel is loaded before fontspec, then
lgrcmr.fd is loaded.

Ulrike Fischer 

--- End Message ---

Reply to: