With [ExternalLocation], I was unable to use my font "Gauß Text" with filename "GaußText.ttf" with this in the log:<br><div style="margin-left: 40px; font-family: courier new,monospace;">fontspec.cfg loaded.<br>
("F:\Program Files\MiKTeX 2.7\tex\xelatex\fontspec\fontspec.cfg"))<br>! Font \zf@basefont=[GaußText.ttf] at 10.0pt not loadable: Metric (TFM) file o<br>r installed font not found.<br>\zf@fontspec ...ntname \zf@suffix " at \f@size pt <br>
\unless \ifzf@icu \zf@set@...<br>l.3 \setmainfont[ExternalLocation]{GaußText.ttf}<br> <br>? <br></div>The command prompt window, unable to display UTF-8, shows something a little different (attached xelatexgausstest1.png).<br>
<br>Without [ExternalLocation], the PDF compiles without a problem, but when viewing the font list, Adobe Reader 9 shows "GauText" i.e. without ß.<br><br>(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.)<br>
<br>Andrew<br><br><div class="gmail_quote">2008/7/6 Will Robertson <<a href="mailto:wspr81@gmail.com">wspr81@gmail.com</a>>:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Hello,<br>
<br>
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?!<br>
<br>
Can anyone either confirm this problem or let me know that something else funny is going on here?<br>
<br>
Many thanks,<br>
Will<br>
<br>
Begin forwarded message:<br>
<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
From: Michiel Kamermans [EMAIL REDACTED]<br>
To: Will Robertson <<a href="mailto:wspr81@gmail.com" target="_blank">wspr81@gmail.com</a>><br>
<br>
Hi Will,<br>
<br>
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... =/<br>
<br>
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 =)<br>
<br>
Best regards,<br>
<br>
-- <br>
Michiel Kamermans, M.Sc<br>
</blockquote>
<br>_______________________________________________<br>
XeTeX mailing list<br>
<a href="mailto:postmaster@tug.org">postmaster@tug.org</a><br>
<a href="http://tug.org/mailman/listinfo/xetex" target="_blank">http://tug.org/mailman/listinfo/xetex</a><br>
<br></blockquote></div><br>