[XeTeX] Fwd: fontspec question on windows

Andrew Moschou andmos at gmail.com
Sun Jul 6 15:24:32 CEST 2008

With [ExternalLocation], I was unable to use my font "Gauß Text" with
filename "GaußText.ttf" with this in the log:
fontspec.cfg loaded.
("F:\Program Files\MiKTeX 2.7\tex\xelatex\fontspec\fontspec.cfg"))
! Font \zf at basefont=[GaußText.ttf] at 10.0pt not loadable: Metric (TFM) file
r installed font not found.
\zf at fontspec ...ntname \zf at suffix " at \f at size pt
                                                  \unless \ifzf at icu \zf at set
l.3 \setmainfont[ExternalLocation]{GaußText.ttf}

The command prompt window, unable to display UTF-8, shows something a little
different (attached xelatexgausstest1.png).

Without [ExternalLocation], the PDF compiles without a problem, but when
viewing the font list, Adobe Reader 9 shows "GauText" i.e. without ß.

(Incidently, Gauss Text is my modification of Gentium to include (somewhat
crude) small caps and (very crude) old style figures. Let me know if you'd
like a copy to try.)


2008/7/6 Will Robertson <wspr81 at gmail.com>:

> Hello,
> I've got a request below that I'm rather ignorant about. (I stopped using
> Windows a while back, so I can't really test XeTeX-related stuff on Windows
> very easily.) Apparently XeTeX can't load fonts under Windows when they've
> got names than involve certain UTF-8 characters?!
> Can anyone either confirm this problem or let me know that something else
> funny is going on here?
> Many thanks,
> Will
> Begin forwarded message:
>  From: Michiel Kamermans [EMAIL REDACTED]
>> To: Will Robertson <wspr81 at gmail.com>
>> Hi Will,
>> I was wondering whether you knew how to work around this problem: xetex
>> files are utf8 files, but font names in windows are not encoded in utf8, so
>> fontspec cannot load every system font available. As long as the font name
>> contains only ascii characters this is not a problem, but for 'foreign'
>> named fonts it means xetex throws up an error because it cannot find the
>> font specfied, as windows is still using the utterly moronic codepage system
>> behind the scenes. Even in vista/windows 2008 this is still the case, and
>> the last thing I'm counting on is microsoft rewriting their core to be fully
>> utf8 unicode compliant... =/
>> How (im)possible would it be to detect which OS fontspec is being used on,
>> and using an iconv-like conversion for font names from UTF-8 to whichever
>> codepage windows is set to use, so that all system fonts can be used in
>> xetex on windows systems? (this problem does not exist on utf8 supporting
>> *nixen like ubuntu etc. but running a virtual machine just for xetex is a
>> bit silly if a solution to the fontspec package is an option =)
>> Best regards,
>> --
>> Michiel Kamermans, M.Sc
> _______________________________________________
> XeTeX mailing list
> postmaster at tug.org
> http://tug.org/mailman/listinfo/xetex
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://tug.org/pipermail/xetex/attachments/20080706/55ca4b01/attachment-0001.html 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: xelatexgausstest1.png
Type: image/png
Size: 21766 bytes
Desc: not available
Url : http://tug.org/pipermail/xetex/attachments/20080706/55ca4b01/attachment-0001.png 

More information about the XeTeX mailing list