system fonts access under macosx (again)

j. van den hoff

23 Dec 2014 23 Dec '14

9:42 a.m.

as advised I have installed standalone context in order to get better support of system fonts under macosx. I now have had the following happen to me: 1. after installation of `standalone' and straightening out unrelated problems with `\usemodule' usage I managed to get proper support of -- that's the specific font I wanted to use -- the `Optima' font family. Notably I got italics where I wanted them. so far so good. 2. then I discovered that standalone context does not include the very nice `EB Garamond' font (although there are some files in the context tree apparently related to tweaking some things related to this font) -- contrary to texlive where `context` finds this font just fine. 3. instead of putting this font into the standalone `context' tree (which I tried initially without luck -- on second thought I probably would have needed to do a `mtxrun --script fonts --reload' ...) I installed these (otf) fonts systemwide. (as an aside: is there a way of notifying standalone context of the location of the `texlive' font directories?) 4. contrary to what I seem to have read in the documentation somewhere (??) the fonts were than _not_ looked up "on demand" (i.e. where not found automatically when compiling the document wanting to use this font) but only found after I did a manual `mtxrun --script fonts --reload' 5. now `ebgaramond' works fine _but_ out of the `Optima' fonts now only the regular font is found and reported by `mtxrun ... fonts` if I interpret this output correctly: optima optimaregular /System/Library/Fonts/Optima.ttc index: 4 optimanormal optimaregular /System/Library/Fonts/Optima.ttc index: 4 optimaregular optimaregular /System/Library/Fonts/Optima.ttc index: 4 so I seem back to square one in this respect :-(. I can only assume that this has been caused by the `--reload' run (see item 1. above: intitially `optima' italics worked) and/or maybe still fragile support of these `ttc' (true type collection) files? just a guess. what am I doing wrong _this_ time? thx, joerg -- Using Opera's revolutionary email client: http://www.opera.com/mail/

Show replies by date

Hans Hagen

23 Dec 23 Dec

11:14 a.m.

On 12/23/2014 5:42 PM, j. van den hoff wrote:

...

what am I doing wrong _this_ time?

hard to guess from a distance but whenever i want to use some font and want also to be sure that i use the same one each time (esp system fonts) i just copy them to someplace under texmf-fonts/fonts/data after copying a font you need to run mtxrun --generate in order to update the file database (after that not found founds will trugger a remake of the font database) 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 -----------------------------------------------------------------

j. van den hoff

3:53 p.m.

On Tue, 23 Dec 2014 19:14:26 +0100, Hans Hagen wrote:

...

On 12/23/2014 5:42 PM, j. van den hoff wrote:

...
what am I doing wrong _this_ time?

hard to guess from a distance but whenever i want to use some font and want also to be sure that i use the same one each time (esp system fonts) i just copy them to someplace under texmf-fonts/fonts/data

understood.

...

after copying a font you need to run mtxrun --generate in order to update the file database (after that not found founds will trugger a remake of the font database)

could you please explain what the difference is between `mtxrun --generate' and `mtxrun fonts --rebuild {-force}'? thx, joerg

...

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 ___________________________________________________________________________________

-- Using Opera's revolutionary email client: http://www.opera.com/mail/

Pablo Rodriguez

11:44 a.m.

On 12/23/2014 05:42 PM, j. van den hoff wrote:

...

[...] so I seem back to square one in this respect :-(. I can only assume that this has been caused by the `--reload' run (see item 1. above: intitially `optima' italics worked) and/or maybe still fragile support of these `ttc' (true type collection) files? just a guess.

what am I doing wrong _this_ time?

Hi Jörg, I cannot tell, but maybe there is something that might work.

...

From your ConTeXt Suite directory, remove tex/texmf-cache/luatex-cache/.

And then compile the documents with Optima and EB Garamond. (ConTeXt will perform the required tasks before.) --reload didn’t work for me and this method worked. I remove tex/texmf-cache/luatex-cache/ everytime I install a new font. Just in case it helps, Pablo -- http://www.ousia.tk

Wolfgang Schuster

12:31 p.m.

...

Am 23.12.2014 um 19:44 schrieb Pablo Rodriguez :

On 12/23/2014 05:42 PM, j. van den hoff wrote:

...
[...] so I seem back to square one in this respect :-(. I can only assume that this has been caused by the `--reload' run (see item 1. above: intitially `optima' italics worked) and/or maybe still fragile support of these `ttc' (true type collection) files? just a guess.

what am I doing wrong _this_ time?

Hi Jörg,

I cannot tell, but maybe there is something that might work.

From your ConTeXt Suite directory, remove tex/texmf-cache/luatex-cache/.

And then compile the documents with Optima and EB Garamond. (ConTeXt will perform the required tasks before.)

--reload didn’t work for me and this method worked. I remove tex/texmf-cache/luatex-cache/ everytime I install a new font.

There is no need to remove the latex-cache folder because you can use the force option (i.e. mtxrun —script font —reload —force) to rebuild the whole cache. Wolfgang

j. van den hoff

3:32 p.m.

On Tue, 23 Dec 2014 20:31:46 +0100, Wolfgang Schuster wrote:

...

...
Am 23.12.2014 um 19:44 schrieb Pablo Rodriguez :

On 12/23/2014 05:42 PM, j. van den hoff wrote:

...
[...] so I seem back to square one in this respect :-(. I can only assume that this has been caused by the `--reload' run (see item 1. above: intitially `optima' italics worked) and/or maybe still fragile support of these `ttc' (true type collection) files? just a guess.

what am I doing wrong _this_ time?

Hi Jörg,

I cannot tell, but maybe there is something that might work.

From your ConTeXt Suite directory, remove tex/texmf-cache/luatex-cache/.

And then compile the documents with Optima and EB Garamond. (ConTeXt will perform the required tasks before.)

--reload didn’t work for me and this method worked. I remove tex/texmf-cache/luatex-cache/ everytime I install a new font.

There is no need to remove the latex-cache folder because you can use the force option (i.e. mtxrun —script font —reload —force) to rebuild the whole cache.

thanks to both of you. in fact, just doing `mtxrun —script font —reload —force' restored sane behaviour (italics back again etc.). so, I understand that _this_ actually rebuilds the font data base? what, then, is just issuing `--reload' good for? I also don't understand, why `context' got apparently confused (i.e. stopped recognizing `optima italics') by issuing just `mtxrun —script font —reload' (which I did -- successfully -- to make `context' recognize the newly installed EB Garamond font). joerg

...

Wolfgang ___________________________________________________________________________________ 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 ___________________________________________________________________________________

-- Using Opera's revolutionary email client: http://www.opera.com/mail/

Wolfgang Schuster

24 Dec 24 Dec

12:41 a.m.

...

Am 23.12.2014 um 23:32 schrieb j. van den hoff :

thanks to both of you. in fact, just doing `mtxrun —script font —reload —force' restored sane behaviour (italics back again etc.).

so, I understand that _this_ actually rebuilds the font data base? what, then, is just issuing `—reload’ good for?

When you make a new installation and context runs for the first time it make a scan for all available fonts and store some information about each font but this will take some time (although this is now faster than it has been in the past). To add a new font to this list you can use "mtxrun —script font —reload“ which adds only new fonts to the list which is faster than a complete rebuild of the list which is done with the "force“ option. Wolfgang

j. van den hoff

3:14 a.m.

On Wed, 24 Dec 2014 08:41:53 +0100, Wolfgang Schuster wrote:

...

...
Am 23.12.2014 um 23:32 schrieb j. van den hoff :

thanks to both of you. in fact, just doing `mtxrun —script font —reload —force' restored sane behaviour (italics back again etc.).

so, I understand that _this_ actually rebuilds the font data base? what, then, is just issuing `—reload’ good for?

When you make a new installation and context runs for the first time it make a scan for all available fonts and store some information about each font but this will take some time (although this is now faster than it has been in the past).

To add a new font to this list you can use "mtxrun —script font —reload“ which adds only new fonts to the list which is faster than a complete rebuild of the list which is done with the "force“ option.

I see. but could there be some "loose ends" in this? since what happenend in my case was: 1. after de-novo installation of `context' standalone, `optima.ttc' was recognized completely (including italics and bold). 2. after adding `ebgaramond' it was not recognized before doing a `mtxrun —script font —reload'. so up to here this is perfectly in accord with your explanation. but 3. at this point `optima' was no longer recognized beyond the `regular' variant. so something "bad" happened to the database during step 2 it seems although according to your explantion it only should have led to appending information for ebgaramond without affecting the rest. 4. the complete rebuild (`-force') restored everything to normal. just in case this deserves further inspection. joerg

...

Wolfgang

-- Using Opera's revolutionary email client: http://www.opera.com/mail/

j. van den hoff

23 Dec 23 Dec

3:50 p.m.

On Tue, 23 Dec 2014 20:31:46 +0100, Wolfgang Schuster wrote:

...

There is no need to remove the latex-cache folder because you can use the force option (i.e. mtxrun —script font —reload —force) to rebuild the whole cache. Wolfgang

FYI: `-force' seems not to be documented, at least I can't find it at `http://wiki.contextgarden.net/Mtxrun'. -- Using Opera's revolutionary email client: http://www.opera.com/mail/

3502

Age (days ago)

3503

Last active (days ago)

List overview

Download

8 comments

4 participants

participants (4)

Hans Hagen
j. van den hoff
Pablo Rodriguez
Wolfgang Schuster