Hi, I cannot use xits fonts if they are placed in $HOME/.fonts. For example, if I use \setupbodyfont[xits] I get a series of messages define fonts > forced type otf of xits-regular not found define fonts > font with name xits-regular is not found define fonts > unknown font xits-regular, loading aborted define fonts > unable to define xits-regular.otf as \*xits11ptrmtfc* I also tried to use the fonts with simplefonts. \usemodule[simplefonts] \setmainfont[XITS] \setmathfont[XITS Math] falls back to LM math while \usemodule[simplefonts] \setmainfont[XITS] \setmathfont[XITS] gives XITS-Regular as the math font (and not XITS-Math). Other fonts in $HOME/.fonts, in particular cambria, work with both methods. \setupbodyfont[cambria] and \usemodule[simplefonts] \setmainfont[Cambria] \setmathfont[Cambria] both work. Here is the output of mtxrun --script font --list "cambria*" --all cambria cambriabold /home/adityam/.fonts/microsoft/cambriab.ttf cambriabold cambriabold /home/adityam/.fonts/microsoft/cambriab.ttf cambriabolditalic cambriabolditalic /home/adityam/.fonts/microsoft/cambriaz.ttf cambriaitalic cambriaitalic /home/adityam/.fonts/microsoft/cambriai.ttf cambriamath cambriamath /home/adityam/.fonts/microsoft/cambria.ttc index: 0 cambriamathnormal cambriamath /home/adityam/.fonts/microsoft/cambria.ttc index: 0 cambrianormal cambriaitalic /home/adityam/.fonts/microsoft/cambriai.ttf and mtxrun --script font --list "xits*" --all brushscriptxitalic brushscriptxitalic BrushScriptX-Italic.afm venturissansadfexitalic venturissansadfexitalic VenturisSansADFEx-Italic.otf venturissansadfno2exitalic venturissansadfno2exitalic VenturisSansADFNo2Ex-Italic.otf xits xits /home/adityam/.fonts/xits-math/xits-regular.otf xitsbold xitsbold /home/adityam/.fonts/xits-math/xits-bold.otf xitsbolditalic xitsbolditalic /home/adityam/.fonts/xits-math/xits-bolditalic.otf xitsitalic xitsitalic /home/adityam/.fonts/xits-math/xits-italic.otf xitsmath xitsmath /home/adityam/.fonts/xits-math/xits-math.otf xitsmathnormal xitsmath /home/adityam/.fonts/xits-math/xits-math.otf xitsmathregular xitsmath /home/adityam/.fonts/xits-math/xits-math.otf xitsnormal xitsitalic /home/adityam/.fonts/xits-math/xits-italic.otf xitsregular xits /home/adityam/.fonts/xits-math/xits-regular.otf Any idea what is going on. If I move the fonts inside $TEXMF everything works. Aditya
On Sun, Aug 15, 2010 at 12:44:40PM -0400, Aditya Mahajan wrote:
Hi,
I cannot use xits fonts if they are placed in $HOME/.fonts.
For example, if I use
\setupbodyfont[xits]
I get a series of messages
define fonts > forced type otf of xits-regular not found define fonts > font with name xits-regular is not found define fonts > unknown font xits-regular, loading aborted define fonts > unable to define xits-regular.otf as \*xits11ptrmtfc*
The typescript uses file names, however ConTeXt can not load system fonts by filename. Hans, I think it would be nice to be able to load fonts by either font name or file name regardless of where they reside (I'm not sure how easy is that, though, with luaotfload and kpse setting OSFONTDIR is all what I need, since kpathsea appends it to its font searching paths).
I also tried to use the fonts with simplefonts.
\usemodule[simplefonts] \setmainfont[XITS] \setmathfont[XITS Math]
falls back to LM math while
AFAIK, simple fonts don't support math fonts beyond the pre-defined typescripts. [...]
Other fonts in $HOME/.fonts, in particular cambria, work with both methods.
\setupbodyfont[cambria]
Because the typescript references font names.
and
\usemodule[simplefonts] \setmainfont[Cambria] \setmathfont[Cambria]
both work.
Because there already a working typescript? Regards, Khaled -- Khaled Hosny Arabic localiser and member of Arabeyes.org team Free font developer
On 17-8-2010 3:00, Khaled Hosny wrote:
The typescript uses file names, however ConTeXt can not load system fonts by filename. Hans, I think it would be nice to be able to load fonts by either font name or file name regardless of where they reside (I'm not sure how easy is that, though, with luaotfload and kpse setting OSFONTDIR is all what I need, since kpathsea appends it to its font searching paths).
\starttext
\definedfont[vera at 50pt] test
\definedfont[file:vera.ttf at 100pt] test
\stoptext
works quite ok on my machine and the log reports:
On Tue, Aug 17, 2010 at 03:08:23PM +0200, Hans Hagen wrote:
On 17-8-2010 3:00, Khaled Hosny wrote:
The typescript uses file names, however ConTeXt can not load system fonts by filename. Hans, I think it would be nice to be able to load fonts by either font name or file name regardless of where they reside (I'm not sure how easy is that, though, with luaotfload and kpse setting OSFONTDIR is all what I need, since kpathsea appends it to its font searching paths).
\starttext
\definedfont[vera at 50pt] test \definedfont[file:vera.ttf at 100pt] test
\stoptext
works quite ok on my machine and the log reports:
so it must be something in the typescripts .. maybe the old names?
This works for me, but not with .otf fonts. -- Khaled Hosny Arabic localiser and member of Arabeyes.org team Free font developer
On 17-8-2010 4:53, Khaled Hosny wrote:
On Tue, Aug 17, 2010 at 03:08:23PM +0200, Hans Hagen wrote:
On 17-8-2010 3:00, Khaled Hosny wrote:
The typescript uses file names, however ConTeXt can not load system fonts by filename. Hans, I think it would be nice to be able to load fonts by either font name or file name regardless of where they reside (I'm not sure how easy is that, though, with luaotfload and kpse setting OSFONTDIR is all what I need, since kpathsea appends it to its font searching paths).
\starttext
\definedfont[vera at 50pt] test \definedfont[file:vera.ttf at 100pt] test
\stoptext
works quite ok on my machine and the log reports:
so it must be something in the typescripts .. maybe the old names?
This works for me, but not with .otf fonts.
\starttext
\definedfont[file:STIXGeneral at 100pt] test
\stoptext
On Tue, Aug 17, 2010 at 05:26:19PM +0200, Hans Hagen wrote:
On 17-8-2010 4:53, Khaled Hosny wrote:
On Tue, Aug 17, 2010 at 03:08:23PM +0200, Hans Hagen wrote:
On 17-8-2010 3:00, Khaled Hosny wrote:
The typescript uses file names, however ConTeXt can not load system fonts by filename. Hans, I think it would be nice to be able to load fonts by either font name or file name regardless of where they reside (I'm not sure how easy is that, though, with luaotfload and kpse setting OSFONTDIR is all what I need, since kpathsea appends it to its font searching paths).
\starttext
\definedfont[vera at 50pt] test \definedfont[file:vera.ttf at 100pt] test
\stoptext
works quite ok on my machine and the log reports:
so it must be something in the typescripts .. maybe the old names?
This works for me, but not with .otf fonts.
\starttext
\definedfont[file:STIXGeneral at 100pt] test
\stoptext
I'm getting unpredictable results here, some fonts are found and some are not, but I can't identify a pattern, I thought it is related to symbolic links but could not prove it (replacing symlinks by a copy, and updating the databases but still the font is not found by file name). -- Khaled Hosny Arabic localiser and member of Arabeyes.org team Free font developer
On 17-8-2010 6:01, Khaled Hosny wrote:
On Tue, Aug 17, 2010 at 05:26:19PM +0200, Hans Hagen wrote:
On 17-8-2010 4:53, Khaled Hosny wrote:
On Tue, Aug 17, 2010 at 03:08:23PM +0200, Hans Hagen wrote:
On 17-8-2010 3:00, Khaled Hosny wrote:
The typescript uses file names, however ConTeXt can not load system fonts by filename. Hans, I think it would be nice to be able to load fonts by either font name or file name regardless of where they reside (I'm not sure how easy is that, though, with luaotfload and kpse setting OSFONTDIR is all what I need, since kpathsea appends it to its font searching paths).
\starttext
\definedfont[vera at 50pt] test \definedfont[file:vera.ttf at 100pt] test
\stoptext
works quite ok on my machine and the log reports:
so it must be something in the typescripts .. maybe the old names?
This works for me, but not with .otf fonts.
\starttext
\definedfont[file:STIXGeneral at 100pt] test
\stoptext
I'm getting unpredictable results here, some fonts are found and some are not, but I can't identify a pattern, I thought it is related to symbolic links but could not prove it (replacing symlinks by a copy, and updating the databases but still the font is not found by file name).
files in OSFONTDIR normally are located runtime (no database) .. depends a bit on the configuration Hans ----------------------------------------------------------------- Hans Hagen | PRAGMA ADE Ridderstraat 27 | 8061 GH Hasselt | The Netherlands tel: 038 477 53 69 | voip: 087 875 68 74 | www.pragma-ade.com | www.pragma-pod.nl -----------------------------------------------------------------
I also had problems at first with the XITS fonts, especially with the built-in typescripts. First, make sure that you have put the fonts somewhere ConTeXt can find them, and run mtxrun --script font --reload You can check that they have installed properly by running mtxrun --script font --list --all --pattern=xits* and you should see a list of the fonts. Then, copy the typescript from the XITS font zip file which you can get from Khaled's website. Put this in the root directory of your .tex file (or in a suitable place in the ConTeXt tree) and load it in your preamble with \usetypescriptfile[type-xits] I then loaded the font with \usetypescript[xits] \setupbodyfont[xits] You might get conflict with the internal typescipt (although I didn't, if I remember correctly); if so, rename [xits] in the typescript to [my-xits], then do \usetypescript[my-xits] \setupbodyfont[my-xits] On 17/08/2010 18:04, Hans Hagen wrote:
On 17-8-2010 6:01, Khaled Hosny wrote:
On Tue, Aug 17, 2010 at 05:26:19PM +0200, Hans Hagen wrote:
On 17-8-2010 4:53, Khaled Hosny wrote:
On Tue, Aug 17, 2010 at 03:08:23PM +0200, Hans Hagen wrote:
On 17-8-2010 3:00, Khaled Hosny wrote:
The typescript uses file names, however ConTeXt can not load system fonts by filename. Hans, I think it would be nice to be able to load fonts by either font name or file name regardless of where they reside (I'm not sure how easy is that, though, with luaotfload and kpse setting OSFONTDIR is all what I need, since kpathsea appends it to its font searching paths).
\starttext
\definedfont[vera at 50pt] test \definedfont[file:vera.ttf at 100pt] test
\stoptext
works quite ok on my machine and the log reports:
so it must be something in the typescripts .. maybe the old names?
This works for me, but not with .otf fonts.
\starttext
\definedfont[file:STIXGeneral at 100pt] test
\stoptext
I'm getting unpredictable results here, some fonts are found and some are not, but I can't identify a pattern, I thought it is related to symbolic links but could not prove it (replacing symlinks by a copy, and updating the databases but still the font is not found by file name).
files in OSFONTDIR normally are located runtime (no database) .. depends a bit on the configuration
Hans
----------------------------------------------------------------- Hans Hagen | PRAGMA ADE Ridderstraat 27 | 8061 GH Hasselt | The Netherlands tel: 038 477 53 69 | voip: 087 875 68 74 | www.pragma-ade.com | www.pragma-pod.nl ----------------------------------------------------------------- ___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the Wiki!
maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context webpage : http://www.pragma-ade.nl / http://tex.aanhet.net archive : http://foundry.supelec.fr/projects/contextrev/ wiki : http://contextgarden.net ___________________________________________________________________________________
-- Michael Murphy MPhys Institute für Quanteninformationsverarbeitung Universität Ulm Albert-Einstein-Allee 11 89081 Ulm Deutschland tel +49 731 50 22931 fax +49 731 50 22839 www.quantenbit.de
On Tue, Aug 17, 2010 at 06:04:47PM +0200, Hans Hagen wrote:
On 17-8-2010 6:01, Khaled Hosny wrote:
On Tue, Aug 17, 2010 at 05:26:19PM +0200, Hans Hagen wrote:
On 17-8-2010 4:53, Khaled Hosny wrote:
On Tue, Aug 17, 2010 at 03:08:23PM +0200, Hans Hagen wrote:
On 17-8-2010 3:00, Khaled Hosny wrote:
The typescript uses file names, however ConTeXt can not load system fonts by filename. Hans, I think it would be nice to be able to load fonts by either font name or file name regardless of where they reside (I'm not sure how easy is that, though, with luaotfload and kpse setting OSFONTDIR is all what I need, since kpathsea appends it to its font searching paths).
\starttext
\definedfont[vera at 50pt] test \definedfont[file:vera.ttf at 100pt] test
\stoptext
works quite ok on my machine and the log reports:
so it must be something in the typescripts .. maybe the old names?
This works for me, but not with .otf fonts.
\starttext
\definedfont[file:STIXGeneral at 100pt] test
\stoptext
I'm getting unpredictable results here, some fonts are found and some are not, but I can't identify a pattern, I thought it is related to symbolic links but could not prove it (replacing symlinks by a copy, and updating the databases but still the font is not found by file name).
files in OSFONTDIR normally are located runtime (no database) .. depends a bit on the configuration
Dunno then, it is very confusing, some fonts are found by file name and some are not. Putting them in TEXMF tree makes them found. Regards, Khaled -- Khaled Hosny Arabic localiser and member of Arabeyes.org team Free font developer
On Wed, Aug 18, 2010 at 01:01:13PM +0200, Taco Hoekwater wrote:
Khaled Hosny wrote:
Dunno then, it is very confusing, some fonts are found by file name and some are not. Putting them in TEXMF tree makes them found.
Wild guess: could it be related to the dot in ".fonts" ?
Other fonts in that directory are found, font names works for all fonts there too. Regards, Khaled -- Khaled Hosny Arabic localiser and member of Arabeyes.org team Free font developer
On Aug 18, 2010, at 1:06 PM, Khaled Hosny wrote:
On Wed, Aug 18, 2010 at 01:01:13PM +0200, Taco Hoekwater wrote:
Khaled Hosny wrote:
Dunno then, it is very confusing, some fonts are found by file name and some are not. Putting them in TEXMF tree makes them found.
Wild guess: could it be related to the dot in ".fonts" ?
Other fonts in that directory are found, font names works for all fonts there too.
May I chime in here? Hans, a couple of weeks ago, I reported a similar problem: none of the fonts in my personal texmf-trees ends up in the database. I can still reproduce the problem: luatools AGaramondPro-Regular.otf /Users/tas/texmf/fonts/opentype/adobe/agaramond/AGaramondPro-Regular.otf mtxrun --script fonts --list --all "agaramond*" (i.e. nothing found). I can only use all these personal fonts via the file: syntax; name: does not work. Maybe these problems are related? Something's not quite kosher in the font database... Thomas
On Wed, 18 Aug 2010, Thomas A. Schmitz wrote:
On Aug 18, 2010, at 1:06 PM, Khaled Hosny wrote:
On Wed, Aug 18, 2010 at 01:01:13PM +0200, Taco Hoekwater wrote:
Khaled Hosny wrote:
Dunno then, it is very confusing, some fonts are found by file name and some are not. Putting them in TEXMF tree makes them found.
Wild guess: could it be related to the dot in ".fonts" ?
Other fonts in that directory are found, font names works for all fonts there too.
May I chime in here? Hans, a couple of weeks ago, I reported a similar problem: none of the fonts in my personal texmf-trees ends up in the database. I can still reproduce the problem:
luatools AGaramondPro-Regular.otf /Users/tas/texmf/fonts/opentype/adobe/agaramond/AGaramondPro-Regular.otf
mtxrun --script fonts --list --all "agaramond*"
(i.e. nothing found). I can only use all these personal fonts via the file: syntax; name: does not work. Maybe these problems are related? Something's not quite kosher in the font database...
I had also noticed a similar behavior in the past with Fontin... the font was not found in $TEXMFHOME tree. That was one of the reasons that I started storing fonts in ~/.fonts (the other being that other applications on Linux can also find the font). I will try to see if I can reproduce that with the latest beta. Aditya
On 18-8-2010 10:07, Aditya Mahajan wrote:
I had also noticed a similar behavior in the past with Fontin... the font was not found in $TEXMFHOME tree. That was one of the reasons that I started storing fonts in ~/.fonts (the other being that other applications on Linux can also find the font).
taco and I tested texmfhome some time ago and it worked on our machines so we need more input on where it fails Hans ----------------------------------------------------------------- Hans Hagen | PRAGMA ADE Ridderstraat 27 | 8061 GH Hasselt | The Netherlands tel: 038 477 53 69 | voip: 087 875 68 74 | www.pragma-ade.com | www.pragma-pod.nl -----------------------------------------------------------------
On 18-8-2010 9:03, Thomas A. Schmitz wrote:
On Aug 18, 2010, at 1:06 PM, Khaled Hosny wrote:
On Wed, Aug 18, 2010 at 01:01:13PM +0200, Taco Hoekwater wrote:
Khaled Hosny wrote:
Dunno then, it is very confusing, some fonts are found by file name and some are not. Putting them in TEXMF tree makes them found.
Wild guess: could it be related to the dot in ".fonts" ?
Other fonts in that directory are found, font names works for all fonts there too.
May I chime in here? Hans, a couple of weeks ago, I reported a similar problem: none of the fonts in my personal texmf-trees ends up in the database. I can still reproduce the problem:
luatools AGaramondPro-Regular.otf /Users/tas/texmf/fonts/opentype/adobe/agaramond/AGaramondPro-Regular.otf
mtxrun --script fonts --list --all "agaramond*"
(i.e. nothing found). I can only use all these personal fonts via the file: syntax; name: does not work. Maybe these problems are related? Something's not quite kosher in the font database...
ah, this could be because a runtime scanned tree is not scanned for fonts in the database; this is somewhat disputable as such a tree is not expected to be stable i.e. files can come and go i can look into it but now now (no time now) and only if there is no performance penalty it's why I would always make a local tree 'databased' Hans ----------------------------------------------------------------- Hans Hagen | PRAGMA ADE Ridderstraat 27 | 8061 GH Hasselt | The Netherlands tel: 038 477 53 69 | voip: 087 875 68 74 | www.pragma-ade.com | www.pragma-pod.nl -----------------------------------------------------------------
On 18-8-2010 9:03, Thomas A. Schmitz wrote:
(i.e. nothing found). I can only use all these personal fonts via the file: syntax; name: does not work. Maybe these problems are related? Something's not quite kosher in the font database...
btw, I put my personal fonts in texmf-fonts anyway -) ----------------------------------------------------------------- Hans Hagen | PRAGMA ADE Ridderstraat 27 | 8061 GH Hasselt | The Netherlands tel: 038 477 53 69 | voip: 087 875 68 74 | www.pragma-ade.com | www.pragma-pod.nl -----------------------------------------------------------------
On Thu, 19 Aug 2010, Hans Hagen wrote:
On 18-8-2010 9:03, Thomas A. Schmitz wrote:
(i.e. nothing found). I can only use all these personal fonts via the file: syntax; name: does not work. Maybe these problems are related? Something's not quite kosher in the font database...
btw, I put my personal fonts in texmf-fonts anyway -)
But then you don't use any application other than ConTeXt, do you? :-) Anyways, for now I have added a simlink from ~/.fonts to ~/texmf/fonts/opentype/data and everything seems to work. Aditya
On 19-8-2010 12:48, Aditya Mahajan wrote:
But then you don't use any application other than ConTeXt, do you? :-)
I do, but I seldom bother about fonts in other applications.
Anyways, for now I have added a simlink from ~/.fonts to ~/texmf/fonts/opentype/data and everything seems to work.
Also, when I use fonts in tex, I make sure that I have a copy in texmf-fonts as I don't want surprised when fonts change (I probably had too many bad experiences). Also, I don't want to enter a font mess when moving to a new system. Hans ----------------------------------------------------------------- Hans Hagen | PRAGMA ADE Ridderstraat 27 | 8061 GH Hasselt | The Netherlands tel: 038 477 53 69 | voip: 087 875 68 74 | www.pragma-ade.com | www.pragma-pod.nl -----------------------------------------------------------------
On Wed, Aug 18, 2010 at 06:48:53PM -0400, Aditya Mahajan wrote:
On Thu, 19 Aug 2010, Hans Hagen wrote:
On 18-8-2010 9:03, Thomas A. Schmitz wrote:
(i.e. nothing found). I can only use all these personal fonts via the file: syntax; name: does not work. Maybe these problems are related? Something's not quite kosher in the font database...
btw, I put my personal fonts in texmf-fonts anyway -)
But then you don't use any application other than ConTeXt, do you? :-)
Anyways, for now I have added a simlink from ~/.fonts to ~/texmf/fonts/opentype/data and everything seems to work.
That what I ended up doing while ago (actually, my master copy is on the local git repository, and I've symlinks in ~/.fonts and ~/texmf). Regards, Khaled -- Khaled Hosny Arabic localiser and member of Arabeyes.org team Free font developer
Khaled, a while ago I was getting strange results: wanted to use roman font got bold italic, etc. Font listing roman name and italic filename, all with several fonts. I just deleted the font cache folder.... Did the trick for the time being. ./tex/texmf-cache/luatex-cache/context/<hexnumber>
Dunno then, it is very confusing, some fonts are found by file name and some are not. Putting them in TEXMF tree makes them found.
Regards, Khaled
On Tue, 17 Aug 2010, Hans Hagen wrote:
\starttext
\definedfont[file:STIXGeneral at 100pt] test
\stoptext
(I don't have stix fonts so testing with xtis) \starttext \definedfont[file:xits-regular.otf at 100pt] test \stoptext gives define fonts > forced type otf of xits-regular not found define fonts > font with name xits-regular is not found define fonts > unknown font xits-regular, loading aborted define fonts > unable to define xits-regular.otf as \**thedefinedfont** (which is consistent with the previous error message). The error message says "font with ***name*** xits-regular is not found". Not sure if name means font name or file name. As Khalid said, \starttext \definedfont[name:XITS at 100pt] test \stoptext works as expected. mtxrun --script font --list can find xits-regular but luatools --locate cannot. I don't think that should matter. Some diagnostic information: * The result of $mtxrun --script font --list --all | grep xits-regular xits xits /home/adityam/.fonts/xits-math/xits-regular.otf (No fontname, instead the font location is given). * The result of $mtxrun --script font --list --file --pattern=xits-regular.otf xits normal normal normal normal xits /home/adityam/.fonts/xits-math/xits-regular.otf conflict: regular (What does the conflict: regular flag mean) * Custom setuptex file TEXMFOS=/opt/context-minimals/texmf-linux export TEXMFOS TEXMFCACHE=$HOME/texmf-cache export TEXMFCACHE unset TEXINPUTS MPINPUTS MFINPUTS PATH=$TEXMFOS/bin:$PATH export PATH OSFONTDIR="$HOME/.fonts;/usr/share/fonts;" export OSFONTDIR (No other customizations of the environments). I have no idea what is going on here. Can it be a linux vs windows things? Can someone else on linux (with xits fonts in OSFFONTDIR) test the above examples? Hans, is there some tracing that I can enable to see how the fonts are being searched? Aditya
participants (7)
-
Aditya Mahajan -
Hans Hagen -
Khaled Hosny -
Martin Althoff -
Michael Murphy -
Taco Hoekwater -
Thomas A. Schmitz