<html><head><meta http-equiv="Content-Type" content="text/html charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;">Hi all,<div><br></div><div>with luaotfload 2.7-fix-3 now on CTAN, the symlinks are automatically filtered out from the database</div><div><br></div><div>Hence doing on mac os x </div><div><br></div><div><span style="font-family: Courier;">ln -s /Library/TeX/Root/texmf-dist/fonts/opentype ~/Library/Fonts/TeXOpenType</span><br style="font-family: Courier;"><br style="font-family: Courier;"><span style="font-family: Courier;">ln -s /Library/TeX/Root/texmf-dist/fonts/truetype ~/Library/Fonts/TeXTrueType</span><br style="font-family: Courier;"><br style="font-family: Courier;"><span style="font-family: Courier;">to make all opentype/truetype fonts inside the texlive/mactex</span><br style="font-family: Courier;"><span style="font-family: Courier;">tree visible to XeTeX hasn't anymore an impact on increased font</span><br style="font-family: Courier;"><span style="font-family: Courier;">database for LuaTeX</span></div><div><font face="Courier"><br></font></div><div><font face="Courier">Jean-François</font></div><div><font face="Courier"><br></font><div><div>Le 16 mai 2016 à 01:24, Zdenek Wagner <<a href="mailto:zdenek.wagner@gmail.com">zdenek.wagner@gmail.com</a>> a écrit :</div><br class="Apple-interchange-newline"><blockquote type="cite"><div dir="ltr"><div><div>Hi,<br><br></div>this is good to know. A friend of mine just copied all the font files which I do not consider good. Imagine that one year later you will have to remove TL fonts and install the new versions. Copying all files can then turn into a nightmare. This is why I sggested to try to symlink the directory tree. It is good news that it works.<br><br></div>I have not only the TL fonts but also a huge collection of commercial fonts. Yes, when I want to see the font list in any Linux application, it takes some time but I do not need it frequently. I prefer having the fonts available.<br><br></div><div class="gmail_extra"><br clear="all"><div><div class="gmail_signature">Zdeněk Wagner<br><a href="http://ttsm.icpf.cas.cz/team/wagner.shtml" target="_blank">http://ttsm.icpf.cas.cz/team/wagner.shtml</a><br><a href="http://icebearsoft.euweb.cz/" target="_blank">http://icebearsoft.euweb.cz</a></div></div>
<br><div class="gmail_quote">2016-05-15 16:38 GMT+02:00 jfbu <span dir="ltr"><<a href="mailto:jfbu@free.fr" target="_blank">jfbu@free.fr</a>></span>:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hi<br>
<br>
<br>
Le 14 mai 2016 à 09:37, Zdenek Wagner <<a href="mailto:zdenek.wagner@gmail.com">zdenek.wagner@gmail.com</a>> a<br>
écrit :<br>
<span class=""><br>
>> 2016-05-14 0:49 GMT+02:00 Karl Berry <<a href="mailto:karl@freefriends.org">karl@freefriends.org</a>>:<br>
>> because in recent years I don't think that was the case.<br>
>><br>
>> I suppose you're right. I'll have to ask about what can be<br>
>> sensibly said instead. Thanks.<br>
>><br>
>> Else one must use filenames, or fontspec with ExternalLocation<br>
>><br>
>> Well, that's preferable anyway :). --karl<br>
> As I remember, someone has already mentioned that the font<br>
> instructions for Mac OSX are wrong.<br>
<br>
</span>I think that was me, a few weeks ago ;-) and perhaps also<br>
last year ;-)<br>
<br>
Then the formulation changed but the new formulation says that<br>
things are automatically set-up for XeTeX on mac os x, which is<br>
<span class="">wrong.<br>
<br>
<br>
> I do not have Mac so I cannot try whether it is really necessary<br>
> to copy the fonts, maybe the symlink would be sufficient. And I do<br>
> not know whether the font files must be symlinked, maybe just the<br>
> parent directory may be symlinked. I do not know whether Mac can<br>
> look for fonts into subdirectories.<br>
><br>
<br>
</span>1. I had not tried earlier the symlink approach because the Mac<br>
comes with FontBook app which has a concept of "Font Library"<br>
which one can add to it without having to copy or symlink the<br>
fonts. Also I feared that perhaps I would have to symlink<br>
individually files or many repertories.<br>
<br>
The "Font Library" method initially seemed to work but I soon<br>
realized it was a nightmare, because FontBook.app is seriously<br>
broken (at least on Mavericks, but Herb indicates he also has had<br>
bad experiences).<br>
<br>
Thus I dropped it some months ago and entered resignation mode.<br>
<br>
(Michael Sharpe has some very nice extras to his font packages so<br>
that even when accessing a font by filename with xelatex one does<br>
not have to list explicitely the bold, italic, etc.. variants, but<br>
doing this for all fonts obviously requires extra work)<br>
<br>
2. But Herb Schulz gave me very good advice to simply symlink the<br>
texmf-dist/fonts/opentype (and I did also texmf-dist/fonts/truetype)<br>
from $HOME/Library/Fonts. The miracle is :<br>
<br>
a. FontBook.app is still usable after that. There is only a<br>
slight delay in opening it, about two seconds during which the font<br>
list is prepared.<br>
<br>
b. all fonts in sub-repertories are found nicely<br>
<br>
c. there are a few duplicates between .otf and .ttf (FreeSerif,<br>
FreeSans, FreeMono in particular) but the FontBook GUI allows to<br>
choose which fonts to validate and this works with no hiccup.<br>
(which is surprising regarding FontBook.app)<br>
<br>
d. there is slight disadvantage that some fonts with names<br>
starting with "drm" occupies many (dozens) lines in FontBook<br>
display, but that's cosmetic.<br>
<br>
After my bad experience with the concept of "Font Library" I was<br>
very much surprised that simply putting symlinks worked out so<br>
well. Thanks Herb !<br>
<br>
And I could confirm that after that, all the TeXLive distributed<br>
opentype/truetype fonts become generally available to Mac<br>
Applications such as TextEdit, OpenOffice, etc... and to XeTeX<br>
naturally. The delay I mentioned above applies only to FontBook.app,<br>
applications such as OpenOffice have their font popup instantly<br>
available with TeX Gyre Termes etc... and naturally XeTeX works<br>
with no delay either.<br>
<br>
3. There is perhaps an impact on LuaTeX+luaotfload, because the<br>
TeXLive distributed fonts will be indexed twice. I do not know if<br>
this slows down LuaTeX. I opened a ticked on github site of<br>
luaotfload about this asking for info.<br>
<br>
<a href="https://github.com/lualatex/luaotfload/issues/359" rel="noreferrer" target="_blank">https://github.com/lualatex/luaotfload/issues/359</a><br>
<br>
4. The specific way to symlink by Herb takes advantage of the<br>
TeXDist structure which has been part of MacTeX install for some<br>
years, in /Library/TeX. This way the symlinks are dynamical and<br>
obey on the fly change of TeXLive distribution year.<br>
<br>
ln -s /Library/TeX/Root/texmf-dist/fonts/opentype<br>
~/Library/Fonts/TeXOpenType<br>
<br>
I did also<br>
<br>
ln -s /Library/TeX/Root/texmf-dist/fonts/truetype<br>
~/Library/Fonts/TeXTrueType<br>
<br>
but had to resolve a few duplicates then as mentioned above.<br>
<br>
(the point is that /Library/TeX/Root is already itself a symlink,<br>
and when changing distribution year via the former Panel or via<br>
TLU, its target is automatically updated)<br>
<br>
5. To make my story complete: took me a while to go to the root<br>
of the following problem. I was surprised to see that log files<br>
with \XeTeXtracingfonts1 indicated the opentype fonts were picked<br>
always from texlive/2015, even if working with TL2014 or TL2016<br>
pretest.<br>
<br>
Turns out that my earlier attempt at adding TeXLive OpenType fonts<br>
to general mac os availability via a "Font Library" added to FontBook.app<br>
had resulted in some non-removed cache in /private/var/folders.<br>
<br>
I looked<br>
in vain everywhere in my $HOME and in obvious system locations,<br>
for such a file, as it was obviously the only explanation to the<br>
observed behavior and was finally saved by the tip at<br>
<br>
<a href="http://osxdaily.com/2015/01/08/clear-font-caches-databases-mac-os-x/" rel="noreferrer" target="_blank">http://osxdaily.com/2015/01/08/clear-font-caches-databases-mac-os-x/</a><br>
<br>
which is to do $ sudo atsutil databases -remove<br>
<br>
it is important to reboot immediately after that.<br>
<br>
This last item is only of relevance to people who messed up with<br>
FontBook.app before, I guess.<br>
<br>
To sum up: For smooth experience with XeTeX on Mac OS X, some<br>
people (me following Herb) have found that<br>
<br>
ln -s /Library/TeX/Root/texmf-dist/fonts/opentype ~/Library/Fonts/TeXOpenType<br>
<br>
and<br>
<br>
ln -s /Library/TeX/Root/texmf-dist/fonts/truetype ~/Library/Fonts/TeXTrueType<br>
<br>
is a well-working approach. In some rare cases, it might be needed to do<br>
(before or after it does not matter)<br>
<br>
sudo atsutil databases -remove<br>
<br>
and<br>
to reboot. That's only to clean-up a pre-existing dysfunctional font situation.<br>
<br>
Hope it helps.<br>
<br>
Jean-François<br>
<br>
</blockquote></div><br></div>
</blockquote></div><br></div></body></html>