Re: [XeTeX] ".ttf" automatically added to font names

[Dirk Hünniger]

Hi Ulrike,

thanks for your help so far. Since this way of writing it seems to work 
today.


\setmainfont[Path=/usr/share/fonts/truetype/cmu/,UprightFont=cmunrm,BoldFont=cmunbx,ItalicFont=cmunti,BoldItalicFont=cmunbi]{cmunbx.ttf}

I changed my source code to use this way of writing it. I will wait for 
a few days, to see if someone objects. I will then publish a new version 
of mediawiki2latex.


Thanks a lot

Yours Dirk


On 12.05.2017 16:59, Ulrike Fischer wrote:

Am Fri, 12 May 2017 16:32:10 +0200 schrieb Dirk Hünniger:


look at the error message closely. It talks about
  

cmunrm.ttf.ttf

I saw this. But it comes from the UprightFont option. So I'm asking
again: why don't you drop it? Fontspec obviously don't expect that
the value of this key has an extension.

  

So its a bug.

Perhaps. \setmainfont[UprightFont=arial.ttf]{arial.ttf} worked in
TL15 but not in TL16. But as I don't see the reason for this setting
I don't know if it a bug or if simply some unsupported side-effect
no longer works. But you should better ask this in the issue tracker
of fontspec: https://github.com/wspr/fontspec/issues






--
Subscriptions, Archive, and List information, etc.:
 http://tug.org/mailman/listinfo/xetex

Re: [XeTeX] ".ttf" automatically added to font names

[Ulrike Fischer]

Am Fri, 12 May 2017 16:32:10 +0200 schrieb Dirk Hünniger:

> look at the error message closely. It talks about
 
>> cmunrm.ttf.ttf

I saw this. But it comes from the UprightFont option. So I'm asking
again: why don't you drop it? Fontspec obviously don't expect that
the value of this key has an extension. 

 
> So its a bug.

Perhaps. \setmainfont[UprightFont=arial.ttf]{arial.ttf} worked in
TL15 but not in TL16. But as I don't see the reason for this setting
I don't know if it a bug or if simply some unsupported side-effect
no longer works. But you should better ask this in the issue tracker
of fontspec: https://github.com/wspr/fontspec/issues


-- 
Ulrike Fischer 
http://www.troubleshooting-tex.de/



--
Subscriptions, Archive, and List information, etc.:
  http://tug.org/mailman/listinfo/xetex

Re: [XeTeX] ".ttf" automatically added to font names

[Dirk Hünniger]

Hi,
look at the error message closely. It talks about


cmunrm.ttf.ttf


This file obviously does not exist since it got a doubled extension.


causes the following error

kpathsea:make_tex: Invalid fontname
`[/usr/share/fonts/truetype/cmu/cmunrm.ttf.ttf]/OT', contains '['

Yes, as I wrote the UprightFont key gives this error. But why do you
use it in this way? It is normally only need to add some suffix to
the font.


So the only question remaining is: Will the xetex compiler developers

It is not a xetex but a fontspec question. And fontspec certainly
won't drop the use of extensions -- it is actually normally
recommended to use them. So if you get errors it either a bug or you
are trying to use a font that doesn't exist on your system (or can't
be found).

So its a bug.
Yours Dirk


--
Subscriptions, Archive, and List information, etc.:
 http://tug.org/mailman/listinfo/xetex

Re: [XeTeX] ".ttf" automatically added to font names

[Ulrike Fischer]

Am Fri, 12 May 2017 16:02:32 +0200 schrieb Dirk Hünniger:

> \setmainfont[Path=/usr/share/fonts/truetype/cmu/,UprightFont=cmunrm.ttf,BoldFont=cmunbx,ItalicFont=cmunti,BoldItalicFont=cmunbi]{cmunbx.ttf}
 
> causes the following error
>>
>> kpathsea:make_tex: Invalid fontname 
>> `[/usr/share/fonts/truetype/cmu/cmunrm.ttf.ttf]/OT', contains '['

Yes, as I wrote the UprightFont key gives this error. But why do you
use it in this way? It is normally only need to add some suffix to
the font. 

> So the only question remaining is: Will the xetex compiler developers 

It is not a xetex but a fontspec question. And fontspec certainly
won't drop the use of extensions -- it is actually normally
recommended to use them. So if you get errors it either a bug or you
are trying to use a font that doesn't exist on your system (or can't
be found).




-- 
Ulrike Fischer 
http://www.troubleshooting-tex.de/



--
Subscriptions, Archive, and List information, etc.:
  http://tug.org/mailman/listinfo/xetex

Re: [XeTeX] ".ttf" automatically added to font names

[David Carlisle]

> So the only question remaining is: Will the xetex compiler developers
keep it like this


Note that mostly this is not a xetex question as you are using the syntax
of the fontspec macro package rather than the xetex primitive font loading
syntax (although of course these are not unrelated)

it might be more portable to use the opentype cm Unicode distributed with
tex than the ttf ones that you are pulling from /usr/share/fonts eg I have

/usr/local/texlive/2017/texmf-dist/fonts/opentype/public/cm-unicode/cmunrm.otf

I don't have them as .ttf  as far as I can see in tl2016 or tl2017.

David




On 12 May 2017 at 15:02, Dirk Hünniger  wrote:

> Hi,
>
> this works for me:
>
> \setmainfont[Path=/usr/share/fonts/truetype/cmu/,UprightFont
> =cmunrm,BoldFont=cmunbx,ItalicFont=cmunti,BoldItalicFo
> nt=cmunbi]{cmunbx.ttf}
>
> but this
>
> \setmainfont[Path=/usr/share/fonts/truetype/cmu/,UprightFont
> =cmunrm.ttf,BoldFont=cmunbx,ItalicFont=cmunti,
> BoldItalicFont=cmunbi]{cmunbx.ttf}
>
> causes the following error
>
>>
>> kpathsea:make_tex: Invalid fontname 
>> `[/usr/share/fonts/truetype/cmu/cmunrm.ttf.ttf]/OT',
>> contains '['
>>
>>
>> 
>> !
>> ! fontspec error: "font-not-found"
>> !
>> ! The font "cmunrm.ttf" cannot be found.
>> !
>> ! See the fontspec documentation for further information.
>> !
>> ! For immediate help type H .
>> !...
>>
>> l.23 ...=cmunti,BoldItalicFont=cmunbi]{cmunbx.ttf}
>>
> So the only question remaining is: Will the xetex compiler developers keep
> it like this will a later version again require to write out the extensions
> like in
>
> \setmainfont[Path=/usr/share/fonts/truetype/cmu/,UprightFont
> =cmunrm.ttf,BoldFont=cmunbx.ttf,ItalicFont=cmunti.ttf,Bold
> ItalicFont=cmunbi.ttf]{cmunbx.ttf}
>
> I just need to know so I can use the right form when generation latex code
> in my system.
> Yours Dirk
>
>
>
>
>
> --
> Subscriptions, Archive, and List information, etc.:
>  http://tug.org/mailman/listinfo/xetex
>


--
Subscriptions, Archive, and List information, etc.:
  http://tug.org/mailman/listinfo/xetex

Re: [XeTeX] ".ttf" automatically added to font names

[Ulrike Fischer]

Am Fri, 12 May 2017 11:29:20 +0200 schrieb Dirk Hünniger:

> Hello,
> my name is Dirk Hünniger. Since approx 10 years I am working on 
> mediawiki2latex a pdf and latex export tool for mediawiki. I am 
> currently using Ubuntu 17.04 and observe a behavior of the \setmainfont 
> command that I don't understand. The string ".ttf" seems to be added 
> magically, which causes problems for me.
> 
> Everything works fine if I write it like this:
> 
> \setmainfont[Path=/usr/share/fonts/truetype/cmu/,UprightFont=cmunrm,BoldFont=cmunbx,ItalicFont=cmunti,BoldItalicFont=cmunbi]{cmunti}
> 
> I am using
> 
> This is XeTeX, Version 3.14159265-2.6-0.6 (TeX Live 2016/Debian) 
> (preloaded format=xelatex)
>   restricted \write18 enabled.
> 
> In an older version of xetex I had to write it like this.
> 
> \setmainfont[Path=/usr/share/fonts/truetype/cmu/,UprightFont=cmunrm.ttf,BoldFont=cmunbx.ttf,ItalicFont=cmunti.ttf,BoldItalicFont=cmunbi.ttf]{cmunrm.ttf}
> 
> If I do this now I get the following error:
> 
>> kpathsea:make_tex: Invalid fontname 
>> `[/usr/share/fonts/truetype/cmu/cmunrm.ttf.ttf]/OT', contains '['


> So the string .ttf is automatically added which causes the problem. The 
> problem gets serious If I want to uses east-asian fonts like

In my texlive 2016 (in windows) the fonts are otf and not ttf-font,
so using ttf as extension leads to errors. 

Beside this I get the error if I use the UprightFont-key, which
looks a bit senseless anyway. 

This works without problems:

\setmainfont{cmunrm.otf}[BoldFont=cmunbx.otf,ItalicFont=cmunti.otf,BoldItalicFont=cmunbi.otf]


-- 
Ulrike Fischer 
http://www.troubleshooting-tex.de/



--
Subscriptions, Archive, and List information, etc.:
  http://tug.org/mailman/listinfo/xetex