Re: [XeTeX] asterisk in font name - font error

2020-12-24 Thread Carlos Franke
Am Donnerstag, den 24.12.2020, 11:13 + schrieb David Carlisle: > >if that doesn't go anywhere, I will try at latex2e's (their bug > tracker > is much more active than fontspec's). > > Please don't do that, it just increases our administrative overload. > > If it is fixable on our side then

Re: [XeTeX] asterisk in font name - font error

2020-12-24 Thread David Carlisle
>if that doesn't go anywhere, I will try at latex2e's (their bug tracker is much more active than fontspec's). Please don't do that, it just increases our administrative overload. If it is fixable on our side then all relevant people will already have seen your report here and at fontspec

Re: [XeTeX] asterisk in font name - font error

2020-12-23 Thread Carlos Franke
> > the problem should be reported to the > > authors of the "fontspec" and "LaTeX2e" packages, as it is > > probable that the problem lies solely therein. > > That LaTeX2e is involved is very improbable. fontspec could be > involved as it uses the * as a wildcard in some places. Alright, I have

Re: [XeTeX] asterisk in font name - font error

2020-12-15 Thread Carlos Franke
Hi! On 12/14/2020 9:42 AM, Ulrike Fischer wrote: > > I wouldn't use xltxtra, and the Mapping is unneeded too, but beside > > this it should work. > > > > […] > > > > If you get an error with this the fonts are perhaps not correctly > > installed. Where did you put them? Did you really installed

Re: [XeTeX] asterisk in font name - font error

2020-12-14 Thread Akira Kakuto
On 2020/12/15 0:31, Ulrike Fischer wrote: It doesn''t work for me in windows. With plain + xetex I still get error because of the * kpathsea:make_tex: Invalid filename `Jost*', contains '*' Loading the font by file name works fine: \font\test="[Jost-500-Medium.otf]" Recent installer adds

Re: [XeTeX] asterisk in font name - font error

2020-12-14 Thread Lorna Evans
It may be a font installation issue if you are on Windows. Windows made a change awhile back where the default place to install is to a user folder. On my system it is: C:\Users\username\AppData\Local\Microsoft\Windows\Fonts If the fonts are in there, delete them. Then reinstall the fonts

Re: [XeTeX] asterisk in font name - font error

2020-12-14 Thread David Carlisle
On Mon, 14 Dec 2020 at 16:10, Apostolos Syropoulos via XeTeX wrote: > >Works for me, Ulrike : > > > > > > \font \Jost = "Jost*" > > \Jost Hallo > > > > \end > > > > > >Of course, one has to install the font in the first place. > > The above code works just fine in Solaris. > A.S. > >

Re: [XeTeX] asterisk in font name - font error

2020-12-14 Thread Apostolos Syropoulos via XeTeX
>Works for me, Ulrike : > > > \font \Jost = "Jost*" > \Jost Hallo > > \end > > >Of course, one has to install the font in the first place. The above code works just fine in Solaris. A.S. -- Apostolos Syropoulos Xanthi, Greece

Re: [XeTeX] asterisk in font name - font error

2020-12-14 Thread Philip Taylor
Ulrike Fischer wrote: It doesn''t work for me in windows. With plain + xetex I still get error because of the * kpathsea:make_tex: Invalid filename `Jost*', contains '*' Works for me, Ulrike : \font \Jost = "Jost*" \Jost Hallo \end Of course, one has to install the font in the first

Re: [XeTeX] asterisk in font name - font error

2020-12-14 Thread Ulrike Fischer
Am Sun, 13 Dec 2020 17:01:16 +0100 schrieb Carlos Franke: > This would be a neat workaround. However it doesn't compile on my > system either. Running "xelatex temp2.tex" (temp2.tex being Apostolos' > code, only with Minion Pro replaced with another font as I don't have > Minion Pro installed) I

Re: [XeTeX] asterisk in font name - font error

2020-12-14 Thread Ulrike Fischer
Am Sun, 13 Dec 2020 16:10:59 + schrieb Philip Taylor: > I can see no reason why XeLaTeX users of "Jost*" should be forced > to use a work-around.  As the font "Jost*" can be successfully > loaded and used with XeTeX, It doesn''t work for me in windows. With plain + xetex I still get error

Re: [XeTeX] asterisk in font name - font error

2020-12-13 Thread Philip Taylor
Carlos Franke wrote: [Apostolos Syropoulos's suggestion] would be a neat workaround. However it doesn't compile on my system either. Running "xelatex temp2.tex" (temp2.tex being Apostolos' code, only with Minion Pro replaced with another font as I don't have Minion Pro installed) I get a

Re: [XeTeX] asterisk in font name - font error

2020-12-13 Thread Carlos Franke
Apostolos Syropoulos via XeTeX: > When I use the command \setsansfont{Jost*} I get exactly the sme > error, however, in the following sample file I have used an > alternative syntax and this works just fine. [...] This would be a neat workaround. However it doesn't compile on my system either.

Re: [XeTeX] asterisk in font name - font error

2020-12-02 Thread Apostolos Syropoulos via XeTeX
>When I try to compile a pdf using Jost* as main font ( >\setmainfont[]{Jost*}), I get the following error: > >  kpathsea:make_tex: Invalid filename >  `JostJost*/OT:script=latn;language=dflt;', contains '*' > >  ! Package fontspec Error: The font "JostJost*" cannot be found. When I use the

Re: [XeTeX] asterisk in font name - font error

2020-12-02 Thread Zdenek Wagner
Is it possible that some macro package changes the category of * to 13 and defines it somehow? Zdeněk Wagner http://ttsm.icpf.cas.cz/team/wagner.shtml http://icebearsoft.euweb.cz st 2. 12. 2020 v 18:12 odesílatel Philip Taylor napsal: > > No problems here, Carlos, using XeTeX rather than

Re: [XeTeX] asterisk in font name - font error

2020-12-02 Thread Philip Taylor
No problems here, Carlos, using XeTeX rather than XeLaTeX \font \Jost = "Jost*" \Jost Hallo \end This is XeTeX, Version 3.14159265-2.6-0.92 (TeX Live 2020/W32TeX) (preloaded format=xetex) \write18 enabled. entering extended mode (./untitled-1.tex [1] ) Output written on

[XeTeX] asterisk in font name - font error

2020-12-02 Thread Carlos Franke
Hello! I'm having trouble using the typeface Jost* [0] [1] with xelatex. My impression is that the asterisk in the font name is the source of the trouble, and this is a bug either in xelatex or in the font itself (in cade it would be violating some standard for font names). However I am not