[NTG-context] OSFONTDIR
Hi everybody, just a short question: I was under the impression that ConTeXt would not look for system fonts unless we set OSFONTDIR explicitly; this appears to be the basis of the page Use_the_fonts_you_want on the wiki, and I prefer this behavior because it lets me control the fonts I want to use. Recently, however (when exactly? I don't know.) this seems to have changed, and ConTeXt now searches the system font directories by default. I found this out because one of my documents is set up to use the STIX2 fonts. In the most recent versions of macos, some files of these fonts are included as system fonts under /System/Library/Fonts/Supplemental, but not all of them. It took me some head scratching to figure out why every run complained about missing glyphs until I saw that ConTeXt was using the wrong font. I had to set the variable OSFONTDIR to some value to prevent this from happening. So my question is: is looking for system fonts by default the new standard? Is it a good idea? Thank you and all best Thomas ___ If your question is of interest to others as well, please add an entry to the Wiki! maillist : ntg-context@ntg.nl / https://www.ntg.nl/mailman/listinfo/ntg-context webpage : https://www.pragma-ade.nl / http://context.aanhet.net archive : https://bitbucket.org/phg/context-mirror/commits/ wiki : https://contextgarden.net ___
Re: [NTG-context] OSFONTDIR defined in texmf.cnf not used
> > There’s unfortunately still a lot of outdated information in the wiki. > But it’s a wiki, you can fix it yourself. > I can indeed edit the wiki and in fact I did four days ago, but for this specific problem which just confused me, I don't think I am the correct one to be able to guarantee that an edit of it is necessary a fix. Why do you refer to an old revision of that page? > It's not an old version. It's a permanent link to the most recent version at the time of writing. On Wed, Jan 8, 2020 at 4:37 PM Henning Hraban Ramm wrote: > Am 08.01.20 um 11:48 schrieb Exp: > > It works, thanks! > > > > But the mentioning of texmf.cnf and OSFONTDIR in > > > https://wiki.contextgarden.net/index.php?title=Custom_Configuration=24290 > > is indeed a bit misleading though. Hope someone could fix it. > > The environment variable OSFONTDIR, to be set in .bashrc, .profile or > the like, works as well. > > There’s unfortunately still a lot of outdated information in the wiki. > But it’s a wiki, you can fix it yourself. > Why do you refer to an old revision of that page? > > Best regards, Hraban > --- > https://www.fiee.net > http://wiki.contextgarden.net > https://www.dreiviertelhaus.de > GPG Key ID 1C9B22FD > > ___ > 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://context.aanhet.net > archive : https://bitbucket.org/phg/context-mirror/commits/ > wiki : http://contextgarden.net > > ___ > -- Shuwei Hu TU München Department of Informatics ___ 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://context.aanhet.net archive : https://bitbucket.org/phg/context-mirror/commits/ wiki : http://contextgarden.net ___
Re: [NTG-context] OSFONTDIR defined in texmf.cnf not used
Am 08.01.20 um 11:48 schrieb Exp: It works, thanks! But the mentioning of texmf.cnf and OSFONTDIR in https://wiki.contextgarden.net/index.php?title=Custom_Configuration=24290 is indeed a bit misleading though. Hope someone could fix it. The environment variable OSFONTDIR, to be set in .bashrc, .profile or the like, works as well. There’s unfortunately still a lot of outdated information in the wiki. But it’s a wiki, you can fix it yourself. Why do you refer to an old revision of that page? Best regards, Hraban --- https://www.fiee.net http://wiki.contextgarden.net https://www.dreiviertelhaus.de GPG Key ID 1C9B22FD ___ 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://context.aanhet.net archive : https://bitbucket.org/phg/context-mirror/commits/ wiki : http://contextgarden.net ___
Re: [NTG-context] OSFONTDIR defined in texmf.cnf not used
It works, thanks! But the mentioning of texmf.cnf and OSFONTDIR in https://wiki.contextgarden.net/index.php?title=Custom_Configuration=24290 is indeed a bit misleading though. Hope someone could fix it. On Wed, Jan 8, 2020 at 11:39 AM Aditya Mahajan wrote: > On Wed, 8 Jan 2020, Exp wrote: > > > I've put `OSFONTDIR=/usr/share/fonts` in ~/.../texlive/2019/texmf.cnf, > > but `mtxrun --script fonts --reload` refuses to look it up, even though > > `kpsewhich --expand-path '$OSFONTDIR'` gives /usr/share/fonts. > > > > `export OSFONTDIR=/usr/share/fonts` does work, but doesn't feel very > tex-y. > > Context (MkIV) uses variables defined in texmfcnf.lua and not texmf.cnf. > You can copy the one that comes with texlive (should be in $TEXMF/web2c > directory) to $TEXMFHOME/web2c and edit it. > > You can check the value of a variable using > > mtxrun --expand-var OSFONTDIR > mtxrun --expand-path OSFONTDIR > mtxrun --resolve-path OSFONTDIR > > Aditya > > ___ > 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://context.aanhet.net > archive : https://bitbucket.org/phg/context-mirror/commits/ > wiki : http://contextgarden.net > > ___ > -- 胡树伟 PKU EECS 2012 ___ 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://context.aanhet.net archive : https://bitbucket.org/phg/context-mirror/commits/ wiki : http://contextgarden.net ___
Re: [NTG-context] OSFONTDIR defined in texmf.cnf not used
On Wed, 8 Jan 2020, Exp wrote: I've put `OSFONTDIR=/usr/share/fonts` in ~/.../texlive/2019/texmf.cnf, but `mtxrun --script fonts --reload` refuses to look it up, even though `kpsewhich --expand-path '$OSFONTDIR'` gives /usr/share/fonts. `export OSFONTDIR=/usr/share/fonts` does work, but doesn't feel very tex-y. Context (MkIV) uses variables defined in texmfcnf.lua and not texmf.cnf. You can copy the one that comes with texlive (should be in $TEXMF/web2c directory) to $TEXMFHOME/web2c and edit it. You can check the value of a variable using mtxrun --expand-var OSFONTDIR mtxrun --expand-path OSFONTDIR mtxrun --resolve-path OSFONTDIR Aditya ___ 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://context.aanhet.net archive : https://bitbucket.org/phg/context-mirror/commits/ wiki : http://contextgarden.net ___
[NTG-context] OSFONTDIR defined in texmf.cnf not used
Hi all, I've put `OSFONTDIR=/usr/share/fonts` in ~/.../texlive/2019/texmf.cnf, but `mtxrun --script fonts --reload` refuses to look it up, even though `kpsewhich --expand-path '$OSFONTDIR'` gives /usr/share/fonts. `export OSFONTDIR=/usr/share/fonts` does work, but doesn't feel very tex-y. Any help is appreciated. ___ 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://context.aanhet.net archive : https://bitbucket.org/phg/context-mirror/commits/ wiki : http://contextgarden.net ___
Re: [NTG-context] OSFONTDIR
On 8/16/2019 7:40 AM, Henning Hraban Ramm wrote: Am 2019-08-15 um 23:57 schrieb Hans Hagen : On 8/15/2019 11:06 PM, Henning Hraban Ramm wrote: Am 2019-08-15 um 08:08 schrieb Huseyin Özoguz : I just moved to Win 10 (coming from Win 7) with a fresh system and installed Context. My problem: The manual installed fonts are not stored in "Windows/Font" like before, but in "AppData/Local/Microsoft/Windows/Fonts" – the default Fonts, which came with windows, are still there in Windows/Font. If I change OSFONTDIR to the new path and execute "mtxrun --script font --reload" after that, the new fonts are found by Context, but that seems no good way, because now the default-fonts are not found. How to solve this situation? How can I prevent Win10 from installing manual installed fonts into this other path and instead install it into "Windows/Font"directly? (Other programs like Corel etc. have no problems finding those other fonts, regardles of there location or OSFONTDIR.) Another solution: Give Context two pathes to look for fonts, is that possible? OSFONTDIR is like other PATH variables, it can contain several paths, separated by ; (at least on Linux and OSX, maybe it’s : on Windows). My OSFONTDIR is rather lengthy to include my collections of commercial and free fonts (beware, that makes ConTeXt slow). in what sense slow ... more fonts means of course a longer identification time when the database is made but that happen seldom (unless you refer to an unknown font in your document in which case a scan happens, but that should then be fixed in the style) It’s been a while since I had my whole collection of literally thousands of fonts in OSFONTDIR, but re-scanning happens quite often – yes, probably something’s wrong in my typescripts, or I call for an invalid combination somewhere. At the moment I just get this error message on every run: resolvers | globbing | confusing filename, name: 'SourceSansPro-SemiBold.ttf', lower: 'sourcesanspro-semibold.ttf', already: 'SourceSansPro-Semibold.ttf' maybe \enabletrackers[fonts.names,fonts.warnings,fonts.specifications,fonts.rejections] gives some clue. Normally the database is rescanned when there is a font not found (maybe new one) or the format is remade, but that then should be once. After that a bad typescript should jkust trigger missing font warnings. I don’t understand what’s wrong with that font. maybe nothing but some fonts can be on the system twice or have an internal name that is wrong or clashs with another one. In the worst case the clash could result in (maybe) this random hash ordering (per run), so you toggle between instances. It's anyway why I always put fonts in texmf-fonts/fonts/data, even system fonts, just to be sure that i get want i expect. Hans - Hans Hagen | PRAGMA ADE Ridderstraat 27 | 8061 GH Hasselt | The Netherlands tel: 038 477 53 69 | www.pragma-ade.nl | 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://context.aanhet.net archive : https://bitbucket.org/phg/context-mirror/commits/ wiki : http://contextgarden.net ___
Re: [NTG-context] OSFONTDIR
> Am 2019-08-15 um 23:57 schrieb Hans Hagen : > > On 8/15/2019 11:06 PM, Henning Hraban Ramm wrote: >>> Am 2019-08-15 um 08:08 schrieb Huseyin Özoguz : >>> >>> I just moved to Win 10 (coming from Win 7) with a fresh system and >>> installed Context. >>> >>> My problem: The manual installed fonts are not stored in "Windows/Font" >>> like before, but in "AppData/Local/Microsoft/Windows/Fonts" – the default >>> Fonts, which came with windows, are still there in Windows/Font. >>> >>> If I change OSFONTDIR to the new path and execute "mtxrun --script font >>> --reload" after that, the new fonts are found by Context, but that seems no >>> good way, because now the default-fonts are not found. >>> >>> How to solve this situation? How can I prevent Win10 from installing manual >>> installed fonts into this other path and instead install it into >>> "Windows/Font"directly? (Other programs like Corel etc. have no problems >>> finding those other fonts, regardles of there location or OSFONTDIR.) >>> >>> Another solution: Give Context two pathes to look for fonts, is that >>> possible? >> OSFONTDIR is like other PATH variables, it can contain several paths, >> separated by ; (at least on Linux and OSX, maybe it’s : on Windows). My >> OSFONTDIR is rather lengthy to include my collections of commercial and free >> fonts (beware, that makes ConTeXt slow). > in what sense slow ... more fonts means of course a longer identification > time when the database is made but that happen seldom (unless you refer to an > unknown font in your document in which case a scan happens, but that should > then be fixed in the style) It’s been a while since I had my whole collection of literally thousands of fonts in OSFONTDIR, but re-scanning happens quite often – yes, probably something’s wrong in my typescripts, or I call for an invalid combination somewhere. At the moment I just get this error message on every run: resolvers | globbing | confusing filename, name: 'SourceSansPro-SemiBold.ttf', lower: 'sourcesanspro-semibold.ttf', already: 'SourceSansPro-Semibold.ttf' I don’t understand what’s wrong with that font. Greetlings, Hraban --- https://www.fiee.net http://wiki.contextgarden.net https://www.dreiviertelhaus.de GPG Key ID 1C9B22FD ___ 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://context.aanhet.net archive : https://bitbucket.org/phg/context-mirror/commits/ wiki : http://contextgarden.net ___
Re: [NTG-context] OSFONTDIR and Windows 10
Ok, solved. The problem was that Windows 10 by default installs new fonts only for the current User, not for all. I changed that, now everything is back to normal. Huseyin Özoguz Schilfweg 52a 27751 Delmenhorst E-Mail: h.oezo...@mmnetz.de Tel.: 0176/20203416 Am 15.08.2019 um 08:08 schrieb Huseyin Özoguz: Hello, I just moved to Win 10 (coming from Win 7) with a fresh system and installed Context. My problem: The manual installed fonts are not stored in "Windows/Font" like before, but in "AppData/Local/Microsoft/Windows/Fonts" – the default Fonts, which came with windows, are still there in Windows/Font. If I change OSFONTDIR to the new path and execute "mtxrun --script font --reload" after that, the new fonts are found by Context, but that seems no good way, because now the default-fonts are not found. How to solve this situation? How can I prevent Win10 from installing manual installed fonts into this other path and instead install it into "Windows/Font"directly? (Other programs like Corel etc. have no problems finding those other fonts, regardles of there location or OSFONTDIR.) Another solution: Give Context two pathes to look for fonts, is that possible? Thank you. ___ 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://context.aanhet.net archive : https://bitbucket.org/phg/context-mirror/commits/ wiki : http://contextgarden.net ___
[NTG-context] OSFONTDIR and Windows 10
Hello, I just moved to Win 10 (coming from Win 7) with a fresh system and installed Context. My problem: The manual installed fonts are not stored in "Windows/Font" like before, but in "AppData/Local/Microsoft/Windows/Fonts" – the default Fonts, which came with windows, are still there in Windows/Font. If I change OSFONTDIR to the new path and execute "mtxrun --script font --reload" after that, the new fonts are found by Context, but that seems no good way, because now the default-fonts are not found. How to solve this situation? How can I prevent Win10 from installing manual installed fonts into this other path and instead install it into "Windows/Font"directly? (Other programs like Corel etc. have no problems finding those other fonts, regardles of there location or OSFONTDIR.) Another solution: Give Context two pathes to look for fonts, is that possible? Thank you. -- Huseyin Özoguz Schilfweg 52a 27751 Delmenhorst E-Mail: h.oezo...@mmnetz.de Tel.: 0176/20203416 ___ 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://context.aanhet.net archive : https://bitbucket.org/phg/context-mirror/commits/ wiki : http://contextgarden.net ___
Re: [NTG-context] OSFONTDIR kills gui fonts.
On Fri, 26 Jul 2013 21:59:28 -0400 john Culleton j...@wexfordpress.com wrote: On Fri, 26 Jul 2013 22:38:10 +0200 Philipp Gesang philipp.ges...@alumni.uni-heidelberg.de wrote: Hi John! ···date: 2013-07-26, Friday···from: john Culleton··· I am tryihg to follow the wiki on Fonts in Luatex. It suggests the following statement for Linux systems: export OSFONTDIR=/usr/local/share/fonts;$HOME/.fonts But I store my fonts in /usr/share/fonts so I used: export OSFONTDIR=/usr/share/fonts The net effect of this statement was to wipe out all my text fonts used with XFCE4 or KDE, at least when I use my regular user signon. I examined my /etc/profile, $HOME/.profile, @HOME/.bashrc files and deleted or commented out all references to OSFONTDIR. I still have no gui fonts. Can you clarify what you mean by “wipe out”? Were the font files deleted? Are other kinds of fonts (e.g. bitmap/pfb) still working? If anyone has any suggestions on how I can revive my gui fonts that would be welcome. Only my regular user signon is affected, But I really want to know what kind of OSFONTDIR statement I can use that won't wipe out my gui fonts. OSFONTDIR is a tex specific (kpathsea and Context) variable that I don’t think is used by the system (fontconfig, desktop environment). While you were fiddling with font paths, is it possible that you accidentally modified something else, like ~/.config/fontconfig or /etc/fonts/* ? Best regards, Philipp When signed on as my usual username and I fire up the gui I get squares instead of characters. It works OK if I sign on as an alternate user or root. I'll try the sudo fc-cache -fv route and see what happens. ___ 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 _ My solution to the missing or miscalled gui fonts is to reestablish Slackware Linux 14 on a new partition and copy pertinent stuff over. Everything is OK so far. I used texlive 2013 since it is simpler to setup and use then stand alone context. My solution to the original problem was suggested in part by a reply on comp.text.tex newsgroup. Basically I gave up on trying to cajole context/luatex to use the fonts I have in /usr/share/fonts/OTF. Instead I copied the ones I need for this project into texmf-local/fonts. And I didn't use any subdirectory structure. Having been burned once I did not use OSFONTDIR at all. Instead I used these methods: context --generate mtxrun--script fonts --reload mtxrun --script fonts --list --all --pattern=Minion* and the same except for my sanserif choice Myriad Now I am in business. John Culleton ___ 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 ___
Re: [NTG-context] OSFONTDIR kills gui fonts.
On Fri, 26 Jul 2013 22:15:58 +0200 Pablo Rodríguez oi...@web.de wrote: On 26/07/13 21:08, john Culleton wrote: I am trying to follow the wiki on Fonts in Luatex. It suggests the following statement for Linux systems: export OSFONTDIR=/usr/local/share/fonts;$HOME/.fonts But I store my fonts in /usr/share/fonts so I used: export OSFONTDIR=/usr/share/fonts Hi John, sorry to read that. Using the ConTeXt Suite the command I use is: export OSFONTDIR=/usr/share/fonts// But I append it at the end of tex/setuptex. I’m afraid I cannot help you with the system fonts, because I don’t use ConTeXt from TeXLive 2013. All I guess is removing all OSFONTDIR from your configuration. (Running grep -irl OSFONTDIR . on your home directory should do the searching job.) Sorry for not being more helpful. I hope it helps, Pablo Hmm. Why do you use // at the end of the statement? Does that have some kind of magic? John Culleton ___ 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 ___
Re: [NTG-context] OSFONTDIR kills gui fonts.
On 27/07/13 16:34, john Culleton wrote: On Fri, 26 Jul 2013 22:15:58 +0200 Pablo Rodríguez oi...@web.de wrote: [...] Using the ConTeXt Suite the command I use is: export OSFONTDIR=/usr/share/fonts// Hmm. Why do you use // at the end of the statement? Does that have some kind of magic? I was told this makes ConTeXt to look for fonts in subdirectories. Pablo -- http://www.ousia.tk ___ 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 ___
[NTG-context] OSFONTDIR kills gui fonts.
I am tryihg to follow the wiki on Fonts in Luatex. It suggests the following statement for Linux systems: export OSFONTDIR=/usr/local/share/fonts;$HOME/.fonts But I store my fonts in /usr/share/fonts so I used: export OSFONTDIR=/usr/share/fonts The net effect of this statement was to wipe out all my text fonts used with XFCE4 or KDE, at least when I use my regular user signon. I examined my /etc/profile, $HOME/.profile, @HOME/.bashrc files and deleted or commented out all references to OSFONTDIR. I still have no gui fonts. If anyone has any suggestions on how I can revive my gui fonts that would be welcome. Only my regular user signon is affected, But I really want to know what kind of OSFONTDIR statement I can use that won't wipe out my gui fonts. I can of course move the pertinent fonts to the fonts directories in my /usr/local/texlive etc. file structure. But I am looking for a more general solution. Slackware 14 64 bit and texlive 2013 As always, thanks in advance to those who reply: John Culleton ___ 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 ___
Re: [NTG-context] OSFONTDIR kills gui fonts.
On 26/07/13 21:08, john Culleton wrote: I am trying to follow the wiki on Fonts in Luatex. It suggests the following statement for Linux systems: export OSFONTDIR=/usr/local/share/fonts;$HOME/.fonts But I store my fonts in /usr/share/fonts so I used: export OSFONTDIR=/usr/share/fonts Hi John, sorry to read that. Using the ConTeXt Suite the command I use is: export OSFONTDIR=/usr/share/fonts// But I append it at the end of tex/setuptex. I’m afraid I cannot help you with the system fonts, because I don’t use ConTeXt from TeXLive 2013. All I guess is removing all OSFONTDIR from your configuration. (Running grep -irl OSFONTDIR . on your home directory should do the searching job.) Sorry for not being more helpful. I hope it helps, Pablo -- http://www.ousia.tk ___ 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 ___
Re: [NTG-context] OSFONTDIR kills gui fonts.
Do you perhaps needs to rebuild your font cache? From the terminal: sudo fc-cache -fv Best, Mica On Fri, Jul 26, 2013 at 1:15 PM, Pablo Rodríguez oi...@web.de wrote: On 26/07/13 21:08, john Culleton wrote: I am trying to follow the wiki on Fonts in Luatex. It suggests the following statement for Linux systems: export OSFONTDIR=/usr/local/share/fonts;$HOME/.fonts But I store my fonts in /usr/share/fonts so I used: export OSFONTDIR=/usr/share/fonts Hi John, sorry to read that. Using the ConTeXt Suite the command I use is: export OSFONTDIR=/usr/share/fonts// But I append it at the end of tex/setuptex. I’m afraid I cannot help you with the system fonts, because I don’t use ConTeXt from TeXLive 2013. All I guess is removing all OSFONTDIR from your configuration. (Running grep -irl OSFONTDIR . on your home directory should do the searching job.) Sorry for not being more helpful. I hope it helps, Pablo -- http://www.ousia.tk ___ 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 ___ ___ 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 ___
Re: [NTG-context] OSFONTDIR kills gui fonts.
Hi John! ···date: 2013-07-26, Friday···from: john Culleton··· I am tryihg to follow the wiki on Fonts in Luatex. It suggests the following statement for Linux systems: export OSFONTDIR=/usr/local/share/fonts;$HOME/.fonts But I store my fonts in /usr/share/fonts so I used: export OSFONTDIR=/usr/share/fonts The net effect of this statement was to wipe out all my text fonts used with XFCE4 or KDE, at least when I use my regular user signon. I examined my /etc/profile, $HOME/.profile, @HOME/.bashrc files and deleted or commented out all references to OSFONTDIR. I still have no gui fonts. Can you clarify what you mean by “wipe out”? Were the font files deleted? Are other kinds of fonts (e.g. bitmap/pfb) still working? If anyone has any suggestions on how I can revive my gui fonts that would be welcome. Only my regular user signon is affected, But I really want to know what kind of OSFONTDIR statement I can use that won't wipe out my gui fonts. OSFONTDIR is a tex specific (kpathsea and Context) variable that I don’t think is used by the system (fontconfig, desktop environment). While you were fiddling with font paths, is it possible that you accidentally modified something else, like ~/.config/fontconfig or /etc/fonts/* ? Best regards, Philipp pgpdYAlCL7WqL.pgp Description: PGP signature ___ 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 ___
Re: [NTG-context] OSFONTDIR kills gui fonts.
On Fri, 26 Jul 2013 22:38:10 +0200 Philipp Gesang philipp.ges...@alumni.uni-heidelberg.de wrote: Hi John! ···date: 2013-07-26, Friday···from: john Culleton··· I am tryihg to follow the wiki on Fonts in Luatex. It suggests the following statement for Linux systems: export OSFONTDIR=/usr/local/share/fonts;$HOME/.fonts But I store my fonts in /usr/share/fonts so I used: export OSFONTDIR=/usr/share/fonts The net effect of this statement was to wipe out all my text fonts used with XFCE4 or KDE, at least when I use my regular user signon. I examined my /etc/profile, $HOME/.profile, @HOME/.bashrc files and deleted or commented out all references to OSFONTDIR. I still have no gui fonts. Can you clarify what you mean by “wipe out”? Were the font files deleted? Are other kinds of fonts (e.g. bitmap/pfb) still working? If anyone has any suggestions on how I can revive my gui fonts that would be welcome. Only my regular user signon is affected, But I really want to know what kind of OSFONTDIR statement I can use that won't wipe out my gui fonts. OSFONTDIR is a tex specific (kpathsea and Context) variable that I don’t think is used by the system (fontconfig, desktop environment). While you were fiddling with font paths, is it possible that you accidentally modified something else, like ~/.config/fontconfig or /etc/fonts/* ? Best regards, Philipp When signed on as my usual username and I fire up the gui I get squares instead of characters. It works OK if I sign on as an alternate user or root. I'll try the sudo fc-cache -fv route and see what happens. ___ 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 ___
[NTG-context] OSFONTDIR
Dear Hans, Some time ago the following code was working. On Mac it seems to have no influence now (OSFONTDIR doesn't get fixed), but if I set it in environment to the same string, it works. local function check_configuration() -- not yet ok, no time for debugging now if os.env[OSFONTDIR] then -- ok elseif os.type == windows then os.setenv(OSFONTDIR,c:/windows/fonts//) elseif os.type == macosx then os.setenv(OSFONTDIR,$HOME/Library/Fonts//;/Library/Fonts//;/System/Library/Fonts//) end end Can it be that setenv doesn't really set anything (it just sets it locally to some variable) and then resolvers only look for proper environmental or texmf.cnf variables? I have an impression that that function has been removed from LuaTeX a while ago, but I may be wrong. Mojca ___ 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 ___
