You can always put symlinks in an easily remembered place like ~/fontlinks/
/bpj
torsdag 28 juli 2016 skrev maxwell :
> On 2016-07-28 07:28, Herbert Schulz wrote:
>
>> You can load the font using file names rather than font names. It's a
>> bit more complicated but
On 2016-07-28 07:28, Herbert Schulz wrote:
You can load the font using file names rather than font names. It's a
bit more complicated but certainly doable. That resolves any ambiguity
the way you wish.
Yeah, I was hoping there was an easier way than that, like
[prioritizeOTF=true]. (Although
Herbert Schulz wrote:
> Howdy,
>
> You can load the font using file names rather than font names.
Should that not read "full path to file" rather than "file name", Herb ? File
names can be duplicated, but full path to file cannot.
** Phil.
--
Howdy,
You can load the font using file names rather than font names. It's a bit more
complicated but certainly doable. That resolves any ambiguity the way you wish.
Good Luck,
Herb Schulz
> On Jul 27, 2016, at 5:47 PM, Karljürgen Feuerherm
> wrote:
>
> I can
I can answer part of this… It loads TTF just fine, as I’ve a font of my own
design that I’ve used with no problems. (Just retested now to be sure nothing
has changed.)
I don’t know about part two :)
Karljürgen
> On Jul 27, 2016, at 16:30, maxwell wrote:
>
> Does
Does fontspec load *only* OpenType fonts?
The intro to the fontspec package documentation says
The fontspec package allows users of either XETEX or
LuaTEX to load OpenType fonts in a LATEX document.
Does that mean it doesn't load TrueType etc. fonts, even if there are no
OpenType