Re: [NTG-context] MacOsX Mavericks and Luatex
On 24 Oct 2013, at 07:41, Pierre Bovet pierr...@me.com wrote: Hi all! It seems that Luatex (0.76 2013/04/05) don't works with Mavericks? Thank's in advanced for your help and testimonies Best wishes I’m afraid you’re right! I installed Mavericks yesterday; trying to build the format, I get this: fontsnames globbing path '/Library/Fonts/**.ttf' mtx-context | fatal error: no return code, message: luatex: execution interrupted It may be a new wacky font in /Library/Fonts. But so far, I have not been able to unset OSFONTDIR and make context ignore this directory. (Unlike some people in a recent discussion, my preference would be to NOT include any system fonts by default: it slows rebuilding the formats down, people who want it can achieve it, and it’s generally a bad idea). I’ll see if I can figure out how to do this and will report back, but for the time being, context cannot be used on Mavericks… Thomas ___ 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] MacOsX Mavericks and Luatex
Am 24.10.2013 um 07:41 schrieb Pierre Bovet pierr...@me.com: Hi all! It seems that Luatex (0.76 2013/04/05) don't works with Mavericks? Thank's in advanced for your help and testimonies There are no problems for me with the last version of the context suite and OS 10.9. This is LuaTeX, Version beta-0.76.0-2013040508 (TeX Live 2013/dev)(rev 4627) 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 ___
Re: [NTG-context] MacOsX Mavericks and Luatex
On 24 Oct 2013, at 09:01, Schmitz Thomas A. thomas.schm...@uni-bonn.de wrote: But so far, I have not been able to unset OSFONTDIR and make context ignore this directory. (Unlike some people in a recent discussion, my preference would be to NOT include any system fonts by default: it slows rebuilding the formats down, people who want it can achieve it, and it’s generally a bad idea). I’ll see if I can figure out how to do this and will report back, but for the time being, context cannot be used on Mavericks… I’m getting slightly annoyed, please excuse my rant. I DO NOT want context to search for system fonts. What I have done is: 1. delete the lines elseif osname==macosx then ossetenv(OSFONTDIR,$HOME/Library/Fonts//;/System/Library/Fonts//“ etc. in mtxrun.lua. Rebuild formats. Result when I compile a file: fontsnames globbing path '/Library/Fonts/**.ttf’ mtx-context | fatal error: no return code, message: luatex: execution interrupted 2. set an environment variable OSFONTDIR, rebuild formats. Result: same as above Why, oh why is context doing this? Just because some lazy people want their “system fonts” used, why is it impossible to make a clean separation? I only want fonts in my tex-trees used and searched, nothing else. Thomas ___ 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] MacOsX Mavericks and Luatex
On 24 Oct 2013, at 09:04, Wolfgang Schuster wolfgang.schus...@gmail.com wrote: There are no problems for me with the last version of the context suite and OS 10.9. This is LuaTeX, Version beta-0.76.0-2013040508 (TeX Live 2013/dev)(rev 4627) Wolfgang not on my system. I have this version and the latest suite, and context bails out (see my other messages). Thomas ___ 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] MacOsX Mavericks and Luatex
Context (luatex) works without problem under Mavericks, but it don't works with external font: \usetypescript[lucida][ec] \setupbodyfont[lucida,12pt] \starttext Hello world! \stoptext Pierre Le 24 oct. 2013 à 09:24, Wolfgang Schuster wolfgang.schus...@gmail.com a écrit : Am 24.10.2013 um 09:13 schrieb Schmitz Thomas A. thomas.schm...@uni-bonn.de: On 24 Oct 2013, at 09:04, Wolfgang Schuster wolfgang.schus...@gmail.com wrote: There are no problems for me with the last version of the context suite and OS 10.9. This is LuaTeX, Version beta-0.76.0-2013040508 (TeX Live 2013/dev)(rev 4627) Wolfgang not on my system. I have this version and the latest suite, and context bails out (see my other messages). I get also a error message when I update the font database fonts | names | globbing path '/Library/Fonts/**.ttf'Segmentation fault: 11 but it doesn’t prevent me from using LuaTeX or regenerating the context format. 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 ___ ___ 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] MacOsX Mavericks and Luatex
Am 24.10.2013 um 09:30 schrieb Pierre Bovet pierr...@me.com: Context (luatex) works without problem under Mavericks, but it don't works with external font: \usetypescript[lucida][ec] \setupbodyfont[lucida,12pt] \starttext Hello world! \stoptext This is unrelated to the problem. MkIV has no support for the Type1 version of the Lucida fonts, use the OpenType version instead (new version which can be purchased from TUG). \setupbodyfont[lucidaot] \starttext Hello world! \stoptext 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 ___
Re: [NTG-context] MacOsX Mavericks and Luatex
OK, that was not a good example… But the the message above is coming with any other otf fonts: fontsnames globbing path '/Library/Fonts/**.ttf' mtx-context | fatal error: no return code, message: luatex: execution interrupted Pierre Le 24 oct. 2013 à 09:36, Wolfgang Schuster wolfgang.schus...@gmail.com a écrit : Am 24.10.2013 um 09:30 schrieb Pierre Bovet pierr...@me.com: Context (luatex) works without problem under Mavericks, but it don't works with external font: \usetypescript[lucida][ec] \setupbodyfont[lucida,12pt] \starttext Hello world! \stoptext This is unrelated to the problem. MkIV has no support for the Type1 version of the Lucida fonts, use the OpenType version instead (new version which can be purchased from TUG). \setupbodyfont[lucidaot] \starttext Hello world! \stoptext 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 ___ ___ 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] MacOsX Mavericks and Luatex
Am 24.10.2013 um 09:45 schrieb Pierre Bovet pierr...@me.com: OK, that was not a good example… But the the message above is coming with any other otf fonts: fontsnames globbing path '/Library/Fonts/**.ttf' mtx-context | fatal error: no return code, message: luatex: execution interrupted Can you remove the Skia.ttf (copy it to another directory) font from /Library/Fonts, this helped on my system to get rid of the error message. 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 ___
Re: [NTG-context] MacOsX Mavericks and Luatex
On 24 Oct 2013, at 10:00, Wolfgang Schuster wolfgang.schus...@gmail.com wrote: Can you remove the Skia.ttf (copy it to another directory) font from /Library/Fonts, this helped on my system to get rid of the error message. Wolfgang Yes, that helped, and I can at least compile my documents again. (How did you find out it was this particular font?). Thanks a lot Thomas ___ 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] MacOsX Mavericks and Luatex
Oh yes, thank you very much! I can compile again with Myriad Pro and all other otf fonts! Thank you! Pierre Le 24 oct. 2013 à 10:08, Schmitz Thomas A. thomas.schm...@uni-bonn.de a écrit : On 24 Oct 2013, at 10:00, Wolfgang Schuster wolfgang.schus...@gmail.com wrote: Can you remove the Skia.ttf (copy it to another directory) font from /Library/Fonts, this helped on my system to get rid of the error message. Wolfgang Yes, that helped, and I can at least compile my documents again. (How did you find out it was this particular font?). Thanks a lot Thomas ___ 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] MacOsX Mavericks and Luatex
Hi Pierre, I have Mavericks installed and no problems. But, I did a clean install, migrated User Folder from a TM-Backup, and my ConTeXt Suite (latest beta) work fine. Since I did a clean install I had to install MacTeX. -- Tried an older LuaLaTeX and got an error -- Ran TeXLive Utility and update TeXLive Everything works fine. I did notice that LuaTeX binaries were updated. Since you have not said where you got your version from try repairing permission on your disk. You should do this especially you did not do this before the update. or just update or reinstall! Sorry for going slightly OT. regards Keith. Am 24.10.2013 um 07:41 schrieb Pierre Bovet pierr...@me.com: Hi all! It seems that Luatex (0.76 2013/04/05) don't works with Mavericks? Thank's in advanced for your help and testimonies Best wishes ___ 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] MacOsX Mavericks and Luatex
Hi All, Wolfgang, The PROBLEM is that Skia.ttf has the wrong permissions! Everyone is set to none. meaning this file can not be read! Solution copy to somewhere else, remove from /Library/Fonts and reinstall. This suggest to me that when scanning the fonts and building the support files there is a sanity check missing! Whether this sanity is truly needed is a matter of taste, as I assume this is most likely a very rare case, where a system font has for some reason bad permissions. Interestingly enough on my clean OSX only emergency drive Skia.ttf has the proper permissions. Since I did a clean and migrated the my user with Migration Assistant I assume it mangled the permissions. regards Keith. Am 24.10.2013 um 10:00 schrieb Wolfgang Schuster wolfgang.schus...@gmail.com: Am 24.10.2013 um 09:45 schrieb Pierre Bovet pierr...@me.com: OK, that was not a good example… But the the message above is coming with any other otf fonts: fontsnames globbing path '/Library/Fonts/**.ttf' mtx-context | fatal error: no return code, message: luatex: execution interrupted Can you remove the Skia.ttf (copy it to another directory) font from /Library/Fonts, this helped on my system to get rid of the error message. 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 ___ ___ 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] Nested itemize (spaces before and after inside environment)
Hello ConTeXist.
I tried convert plainTeX source code into ConTeXt source code so that
the output PDF gave the same (or approximately the same) result. I did
it for one of plainTEX developers (Mr. Olšák), which compared results of
PlainTeX, LaTeX and ConTeXt. However, I encountered the following problem.
Is there a way to adjust the spacing before internal itemize environment
when the external itemize environment is set as PACKED?
Thanx JaroslavHajtmar
Here is my minimal example:
\setupitemize[1][packed][symbol=n,before={\blank[medium]},after={\blank[medium]}]
\setupitemize[2][packed][symbol=a,stopper=),before={\blank[big]},after={\blank[big]}]
\starttext
This is normal text before itemize list.
\startitemize
\item First 1 level
\item Second 1 level
\startitemize
\item First 2 level (before this line should be big space)
\item Second 2 level
\item Third 2 level (after this line should be big space)
\stopitemize
\item Third 1 level
\item Fourth 1 level
\stopitemize
This is normal text after itemize list.
\stoptext
___
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] ConTeXt standalone - in what situations is it better?
Hello, I was looking into simplefonts (http://wiki.contextgarden.net/simplefonts) and noticed the clause if you’re running ConTeXt Standalone http://wiki.contextgarden.net/ConTeXt_Standalone (which is a better option) Well I'm using TeXLive, but am happy to take good advice, so I looked at http://wiki.contextgarden.net/ConTeXt_Standalone to see why it would be a better option. The basic reason I can see is that Standalone is updated more frequently. So if you're using bleeding-edge features of ConTeXt (including recent fixes to simplefonts?), I can see wanting to use Standalone and have access to the latest features and fixes. On the other hand, if you're working on a large production project that has to be careful of stability, is there any advantage to Standalone over TeXLive? Sure, you can keep a standalone version frozen in place, but then that seems equivalent to staying with an existing version of TeXLive. The other issue for me with Standalone is that the only version listed for Windows is W32TeX. When I go to the web page for that platform, I don't see any information about what W32TeX is; just how to install it. It sounds like it's specific to 32-bit systems, and mine is 64-bit. But I suppose in that regard it's no different from TeXLive -- the executables are 32-bit but they run fine on 64-bit systems. Does anybody have advice for me on other reasons for switching from TeXLive to ConTeXt Standalone, or reasons not to? Thanks, Lars ___ 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] Nested itemize (spaces before and after inside environment)
Hi Jarda and all,
I tested it on my computer using CTX from TL 2010 and 2013 and I have got
the same result in both cases. It seems that the content of the option before
is completely ignored. I tested another values for this option
(\page,\vskip,\godown...), no result.
The only one way which works is the manual addition of \blank before and
after the nested itemize environment, unfortunatelly.
---
Another interesting thing is that the compiler of CTX in TL 2013 does not
report an error when I forgot the opening \starttext, or the closing
\stoptext, or both, whereas in TL 2010 it does. Is this expected behaviour?
Best regards,
Tomas Hala
Thu, Oct 24, 2013 ve 12:45:01PM +0200 Jaroslav Hajtmar napsal(a):
# Hello ConTeXist.
#
# I tried convert plainTeX source code into ConTeXt source code so
# that the output PDF gave the same (or approximately the same)
# result. I did it for one of plainTEX developers (Mr. Olšák), which
# compared results of PlainTeX, LaTeX and ConTeXt. However, I
# encountered the following problem.
#
# Is there a way to adjust the spacing before internal itemize
# environment when the external itemize environment is set as PACKED?
#
# Thanx JaroslavHajtmar
#
# Here is my minimal example:
#
#
#
\setupitemize[1][packed][symbol=n,before={\blank[medium]},after={\blank[medium]}]
#
\setupitemize[2][packed][symbol=a,stopper=),before={\blank[big]},after={\blank[big]}]
#
# \starttext
#
# This is normal text before itemize list.
#
# \startitemize
# \item First 1 level
# \item Second 1 level
# \startitemize
# \item First 2 level (before this line should be big space)
# \item Second 2 level
# \item Third 2 level (after this line should be big space)
# \stopitemize
# \item Third 1 level
# \item Fourth 1 level
# \stopitemize
#
# This is normal text after itemize list.
#
#
# \stoptext
#
#
___
# 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
#
___
Tomáš Hála
Mendelova univerzita, Provozně ekonomická fakulta, ústav informatiky
Zemědělská 1, CZ-613 00 Brno, tel. +420 545 13 22 28
http://akela.mendelu.cz/~thala
___
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] Nested itemize (spaces before and after inside environment)
Thanx Tomas.
Of course I know about the possibility of solving the problem by
directly entering a space before internal environment. However, I prefer
setting off the source text, so I wonder how it can be solved.
Jarda Hajtmar
Dne 24.10.2013 14:21, Tomas Hala napsal(a):
Hi Jarda and all,
I tested it on my computer using CTX from TL 2010 and 2013 and I have got
the same result in both cases. It seems that the content of the option before
is completely ignored. I tested another values for this option
(\page,\vskip,\godown...), no result.
The only one way which works is the manual addition of \blank before and
after the nested itemize environment, unfortunatelly.
---
Another interesting thing is that the compiler of CTX in TL 2013 does not
report an error when I forgot the opening \starttext, or the closing
\stoptext, or both, whereas in TL 2010 it does. Is this expected behaviour?
Best regards,
Tomas Hala
Thu, Oct 24, 2013 ve 12:45:01PM +0200 Jaroslav Hajtmar napsal(a):
# Hello ConTeXist.
#
# I tried convert plainTeX source code into ConTeXt source code so
# that the output PDF gave the same (or approximately the same)
# result. I did it for one of plainTEX developers (Mr. Olšák), which
# compared results of PlainTeX, LaTeX and ConTeXt. However, I
# encountered the following problem.
#
# Is there a way to adjust the spacing before internal itemize
# environment when the external itemize environment is set as PACKED?
#
# Thanx JaroslavHajtmar
#
# Here is my minimal example:
#
#
#
\setupitemize[1][packed][symbol=n,before={\blank[medium]},after={\blank[medium]}]
#
\setupitemize[2][packed][symbol=a,stopper=),before={\blank[big]},after={\blank[big]}]
#
# \starttext
#
# This is normal text before itemize list.
#
# \startitemize
# \item First 1 level
# \item Second 1 level
# \startitemize
# \item First 2 level (before this line should be big space)
# \item Second 2 level
# \item Third 2 level (after this line should be big space)
# \stopitemize
# \item Third 1 level
# \item Fourth 1 level
# \stopitemize
#
# This is normal text after itemize list.
#
#
# \stoptext
#
#
___
# 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
#
___
Tomáš Hála
Mendelova univerzita, Provozně ekonomická fakulta, ústav informatiky
Zemědělská 1, CZ-613 00 Brno, tel. +420 545 13 22 28
http://akela.mendelu.cz/~thala
___
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] ConTeXt standalone - in what situations is it better?
On Thu, Oct 24, 2013 at 2:13 PM, Lars Huttar wrote: The other issue for me with Standalone is that the only version listed for Windows is W32TeX. When I go to the web page for that platform, I don't see any information about what W32TeX is; just how to install it. It sounds like it's specific to 32-bit systems, and mine is 64-bit. But I suppose in that regard it's no different from TeXLive -- the executables are 32-bit but they run fine on 64-bit systems. http://w32tex.org/ It's another distribution created by a Japanese guru for compiling binaries with Visual Studio. You don't need to install W32TeX yourself, but those binaries are used in both TeX Live and ConTeXt distribution, so you basically get the same binaries (only maybe slightly newer version with ConTeXt distribution). And yes, the binaries work fine on a 64-bit system. Since recently there are 64-bit binaries available, but I didn't manage to fix the scripts yet to fetch those binaries when applicable. Does anybody have advice for me on other reasons for switching from TeXLive to ConTeXt Standalone, or reasons not to? If TeX Live works for you, there is no real need to switch, but if you ever need a patch or some new functionality, it would be easier to use the latest version. 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 ___
Re: [NTG-context] ConTeXt standalone - in what situations is it better?
On Thu, 24 Oct 2013 14:57:35 +0200 Mojca Miklavec mojca.miklavec.li...@gmail.com wrote: On Thu, Oct 24, 2013 at 2:13 PM, Lars Huttar wrote: The other issue for me with Standalone is that the only version listed for Windows is W32TeX. When I go to the web page for that platform, I don't see any information about what W32TeX is; just how to install it. It sounds like it's specific to 32-bit systems, and mine is 64-bit. But I suppose in that regard it's no different from TeXLive -- the executables are 32-bit but they run fine on 64-bit systems. http://w32tex.org/ It's another distribution created by a Japanese guru for compiling binaries with Visual Studio. You don't need to install W32TeX yourself, but those binaries are used in both TeX Live and ConTeXt distribution, so you basically get the same binaries (only maybe slightly newer version with ConTeXt distribution). And yes, the binaries work fine on a 64-bit system. Since recently there are 64-bit binaries available, but I didn't manage to fix the scripts yet to fetch those binaries when applicable. Does anybody have advice for me on other reasons for switching from TeXLive to ConTeXt Standalone, or reasons not to? If TeX Live works for you, there is no real need to switch, but if you ever need a patch or some new functionality, it would be easier to use the latest version. Mojca There is a problem with using Texlive and a problem with using Standalone. In the simplefonts area in particular documentation and examples may rely on changes that weren't in place when Texlive 2103 was put together. This is a rapidly developing area. The problem with Standalone is that the full range of fonts found with Texlive is not available. Standalone has 258 otf fonts and TexLive has 508 otf fonts. So I am opting for TeXLive, although I have both. Another dfficulty is that many of the examples for simplefonts are apparently developed on a Windows system and I use Linux. Font names are different. -- John Culleton Wexford Press Free list of books for self-publishers: http://wexfordpress.net/shortlist.html PDF e-book: Create Book Covers with Scribus available at http://www.booklocker.com/books/4055.html ___ 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] ConTeXt standalone - in what situations is it better?
On Thu, 24 Oct 2013, Lars Huttar wrote: Hello, I was looking into simplefonts (http://wiki.contextgarden.net/simplefonts) and noticed the clause if you’re running ConTeXt Standalone http://wiki.contextgarden.net/ConTeXt_Standalone (which is a better option) Well I'm using TeXLive, but am happy to take good advice, so I looked at http://wiki.contextgarden.net/ConTeXt_Standalone to see why it would be a better option. The basic reason I can see is that Standalone is updated more frequently. Three or four years ago, when ConTeXt was moving from MkII to MkIV, you had to run through hoops to get context working with TL. Since the last two years, ConTeXt works out of the box in TL. So if you're using bleeding-edge features of ConTeXt (including recent fixes to simplefonts?), I can see wanting to use Standalone and have access to the latest features and fixes. On the other hand, if you're working on a large production project that has to be careful of stability, is there any advantage to Standalone over TeXLive? Sure, you can keep a standalone version frozen in place, but then that seems equivalent to staying with an existing version of TeXLive. No. In some sense, it is better to use the frozen version that is part of TL rather than an arbitrary beta version from standalone. Every once in a while, the beta version has bugs (those are usually fixed in a matter of hours). But it can be tricky to decide which version to freeze for a long term production environment. On the other hand, the version of ConTeXt that ships with TL is tested more thoroughly. So, there is some guarantee that it will not include any serious bugs. 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://tex.aanhet.net archive : http://foundry.supelec.fr/projects/contextrev/ wiki : http://contextgarden.net ___
Re: [NTG-context] MacOsX Mavericks and Luatex
On 10/24/2013 4:12 PM, Schmitz Thomas A. wrote: On 24 Oct 2013, at 09:01, Schmitz Thomas A. thomas.schm...@uni-bonn.de wrote: But so far, I have not been able to unset OSFONTDIR and make context ignore this directory. (Unlike some people in a recent discussion, my preference would be to NOT include any system fonts by default: it slows rebuilding the formats down, people who want it can achieve it, and it’s generally a bad idea). I’ll see if I can figure out how to do this and will report back, but for the time being, context cannot be used on Mavericks… I’m getting slightly annoyed, please excuse my rant. I DO NOT want context to search for system fonts. What I have done is: 1. delete the lines elseif osname==macosx then ossetenv(OSFONTDIR,$HOME/Library/Fonts//;/System/Library/Fonts//“ etc. in mtxrun.lua. Rebuild formats. Result when I compile a file: fontsnames globbing path '/Library/Fonts/**.ttf’ mtx-context | fatal error: no return code, message: luatex: execution interrupted 2. set an environment variable OSFONTDIR, rebuild formats. Result: same as above Why, oh why is context doing this? Just because some lazy people want their “system fonts” used, why is it impossible to make a clean separation? I only want fonts in my tex-trees used and searched, nothing else. Hm. The problem is that we get some oscillation (with a few year cycle) between the 'demand' for os fonts support vs tree only (as far as remember os font support was mostly requested by osx users). Anyhow, we can make it an option, but then the question is: what is the default (and who is going to defend that choice to distributers and users). Hans (who never uses system 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 - ___ 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] ConTeXt standalone - in what situations is it better?
The problem with Standalone is that the full range of fonts found with Texlive is not available. Standalone has 258 otf fonts and TexLive has 508 otf fonts. So I am opting for TeXLive, although I have both. I use standalone in parallel with texlive (which I need for latex). In the Arch PKGBUILD that I maintain, I use: # If texlive exists, use fonts from texlive if [ -d $_texlivefontdir ] then mkdir -p $srcdir/tex/texmf-fonts if [ -L $srcdir/tex/texmf-fonts/fonts ] then rm $srcdir/tex/texmf-fonts/fonts fi ln -s $_texlivefontdir $srcdir/tex/texmf-fonts/fonts fi So, if TL is installed, the TL font directory is symlinked at an appropriate location and all the TL fonts are available with ConTeXt standalone as well. Another dfficulty is that many of the examples for simplefonts are apparently developed on a Windows system and I use Linux. Font names are different. I haven't had any trouble with using simplefonts in Linux (but then, I rarely consult the wiki for usage examples). Could you point to specific examples. 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://tex.aanhet.net archive : http://foundry.supelec.fr/projects/contextrev/ wiki : http://contextgarden.net ___
Re: [NTG-context] MacOsX Mavericks and Luatex
On Thu, 24 Oct 2013 23:17:13 +0900 Hans Hagen pra...@wxs.nl wrote: Hm. The problem is that we get some oscillation (with a few year cycle) between the 'demand' for os fonts support vs tree only (as far as remember os font support was mostly requested by osx users). Anyhow, we can make it an option, but then the question is: what is the default (and who is going to defend that choice to distributers and users). Users can set OSFONTDIR in their environment if they wish, and this can be specified in the wiki. Also, the standalone script can include a (harmless) message informing the user of this possibility. Alan ___ 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] MacOsX Mavericks and Luatex
On 24 Oct 2013, at 16:17, Hans Hagen pra...@wxs.nl wrote: Hm. The problem is that we get some oscillation (with a few year cycle) between the 'demand' for os fonts support vs tree only (as far as remember os font support was mostly requested by osx users). Anyhow, we can make it an option, but then the question is: what is the default (and who is going to defend that choice to distributers and users). Hans Yes, I’m aware that any default will make some users unhappy. I would prefer to have osfontdir unset by default because there’s a real speed penalty in having it set so I would agree with Alan on that one. (It would also abolish the inconsistency between platforms.) But for me the real question is: what do I have to do to have osfontdir unset as things are now? I tried some things, none worked. (see my earlier mail). Thomas ___ 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] MacOsX Mavericks and Luatex
On Thu, 24 Oct 2013, Schmitz Thomas A. wrote: On 24 Oct 2013, at 16:17, Hans Hagen pra...@wxs.nl wrote: Hm. The problem is that we get some oscillation (with a few year cycle) between the 'demand' for os fonts support vs tree only (as far as remember os font support was mostly requested by osx users). Anyhow, we can make it an option, but then the question is: what is the default (and who is going to defend that choice to distributers and users). Hans Yes, I’m aware that any default will make some users unhappy. I would prefer to have osfontdir unset by default because there’s a real speed penalty in having it set so I would agree with Alan on that one. (It would also abolish the inconsistency between platforms.) But for me the real question is: what do I have to do to have osfontdir unset as things are now? I tried some things, none worked. (see my earlier mail). You need to set it to a dummy directory! See: http://tex.stackexchange.com/a/136073/323 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://tex.aanhet.net archive : http://foundry.supelec.fr/projects/contextrev/ wiki : http://contextgarden.net ___
[NTG-context] Mavericks and Standalone ConTeXt
After installing Mavericks and attempting to update to the latest Standalone— Problem 1: with sh ./first-setupsh I get Context current version: 2013.10.15 13:52. though it should. I think, be version 2013-10-20 07:11. Problem 2: (noted before?) compiling with this Standalone (ConTeXt ver: 2013.10.15 13:52 MKIV beta fmt: 2013.10.24) fails at/with fontsnames identifying system font files with suffix 'ttf' fontsnames globbing path '/Users/alancbowen/Library/Fonts/**.ttf' fontsnames globbing path '/Library/Fonts/**.ttf' mtx-context | fatal error: no return code, message: luatex: execution interrupted Curiosity 1: compiling with the same version of the Standalone (ConTeXt ver: 2013.10.15 13:52 MKIV beta fmt: 2013.10.15) which had been installed *before *upgrading to Mavericks works. I fear Mavericks is living up to its name. Alan ___ 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] Mavericks and Standalone ConTeXt
Am 24.10.2013 um 22:48 schrieb Alan Bowen bowenala...@gmail.com: After installing Mavericks and attempting to update to the latest Standalone— Problem 1: with sh ./first-setupsh I get Context current version: 2013.10.15 13:52. though it should. I think, be version 2013-10-20 07:11. Problem 2: (noted before?) compiling with this Standalone (ConTeXt ver: 2013.10.15 13:52 MKIV beta fmt: 2013.10.24) fails at/with fontsnames identifying system font files with suffix 'ttf' fontsnames globbing path '/Users/alancbowen/Library/Fonts/**.ttf' fontsnames globbing path '/Library/Fonts/**.ttf' mtx-context | fatal error: no return code, message: luatex: execution interrupted Curiosity 1: compiling with the same version of the Standalone (ConTeXt ver: 2013.10.15 13:52 MKIV beta fmt: 2013.10.15) which had been installed before upgrading to Mavericks works. Please read the thread from this morning: http://www.ntg.nl/pipermail/ntg-context/2013/075689.html 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 ___
Re: [NTG-context] ConTeXt standalone - in what situations is it better?
Am 24.10.2013 um 16:18 schrieb Aditya Mahajan adit...@umich.edu: Another dfficulty is that many of the examples for simplefonts are apparently developed on a Windows system and I use Linux. Font names are different. I haven't had any trouble with using simplefonts in Linux (but then, I rarely consult the wiki for usage examples). Could you point to specific examples. That’s interesting because I use in many of my examples fonts from the TeX Gyre Project and also fonts from the DejaVu family which are available on Linux. Which example leads to the thought simplefonts was written on a Windows system? 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 ___
Re: [NTG-context] MacOsX Mavericks and Luatex
On 10/24/2013 11:39 PM, Schmitz Thomas A. wrote: On 24 Oct 2013, at 16:17, Hans Hagen pra...@wxs.nl wrote: Hm. The problem is that we get some oscillation (with a few year cycle) between the 'demand' for os fonts support vs tree only (as far as remember os font support was mostly requested by osx users). Anyhow, we can make it an option, but then the question is: what is the default (and who is going to defend that choice to distributers and users). Hans Yes, I’m aware that any default will make some users unhappy. I would prefer to have osfontdir unset by default because there’s a real speed penalty in having it set so I would agree with Alan on that one. (It would also abolish the inconsistency between platforms.) But for me the real question is: what do I have to do to have osfontdir unset as things are now? I tried some things, none worked. (see my earlier mail). I don't understand the speed issue. We're talking about relatively few fonts only and context will not scan them unless there is a change. After a remake a rescan takes 9 sec on my laptop and 6 sec once the directories have been cached (windows 8 / 64 bit / i7 / ssd). Only an initial full scan takes a while (deleted cache), but that's mostly because I have a pretty large font collection in my texmf-fonts tree. 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 ___
Re: [NTG-context] MacOsX Mavericks and Luatex
On 24 Oct 2013, at 16:44, Aditya Mahajan adit...@umich.edu wrote: You need to set it to a dummy directory! See: http://tex.stackexchange.com/a/136073/323 No, even that doesn’t help: echo $OSFONTDIR /tmp/dummy and then on a first run (after regnerating the format with this variable set), I get lines such as fontsnames 'OSFONTDIR' specifies path '/Users/tas/Library/Fonts' fontsnames 'OSFONTDIR' specifies path '/Library/Fonts' fontsnames 'OSFONTDIR' specifies path '/System/Library/Fonts' fontsnames globbing path '/System/Library/Fonts/**.OTF' fontsnames 68 system files identified, 2 skipped, 2 duplicates, 66 hash entries added, runtime 43.223 seconds So something appears to be overriding the variable that I set. But what? And why? And how do I stop it? On 24 Oct 2013, at 23:40, Hans Hagen pra...@wxs.nl wrote: I don't understand the speed issue. We're talking about relatively few fonts only and context will not scan them unless there is a change. After a remake a rescan takes 9 sec on my laptop and 6 sec once the directories have been cached (windows 8 / 64 bit / i7 / ssd). Only an initial full scan takes a while (deleted cache), but that's mostly because I have a pretty large font collection in my texmf-fonts tree. You’re right of course that it’s only the initial run when a new font cache has to be built, but the time I get on os x is much longer than what you report: with rescanning of system fonts: system | total runtime: 114.131 (yes, that’s almost 2 minutes!) And I don’t want to twiddle my thumbs for two minutes, and don’t want to use those “system fonts” (or if I want to use them, I will copy them to my texmf directories)! Thomas ___ 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] MacOsX Mavericks and Luatex
On 10/25/2013 7:01 AM, Schmitz Thomas A. wrote:
On 24 Oct 2013, at 16:44, Aditya Mahajan adit...@umich.edu wrote:
You need to set it to a dummy directory! See:
http://tex.stackexchange.com/a/136073/323
No, even that doesn’t help:
echo $OSFONTDIR
/tmp/dummy
and then on a first run (after regnerating the format with this variable set),
I get lines such as
fontsnames 'OSFONTDIR' specifies path '/Users/tas/Library/Fonts'
fontsnames 'OSFONTDIR' specifies path '/Library/Fonts'
fontsnames 'OSFONTDIR' specifies path '/System/Library/Fonts'
fontsnames globbing path '/System/Library/Fonts/**.OTF'
fontsnames 68 system files identified, 2 skipped, 2 duplicates,
66 hash entries added, runtime 43.223 seconds
So something appears to be overriding the variable that I set. But what? And
why? And how do I stop it?
On 24 Oct 2013, at 23:40, Hans Hagen pra...@wxs.nl wrote:
I don't understand the speed issue. We're talking about relatively few fonts only and
context will not scan them unless there is a change. After a remake a rescan takes
9 sec on my laptop and 6 sec once the directories have been cached (windows
8 / 64 bit / i7 / ssd).
Only an initial full scan takes a while (deleted cache), but that's mostly
because I have a pretty large font collection in my texmf-fonts tree.
You’re right of course that it’s only the initial run when a new font cache has
to be built, but the time I get on os x is much longer than what you report:
with rescanning of system fonts:
system | total runtime: 114.131 (yes, that’s almost 2 minutes!)
And I don’t want to twiddle my thumbs for two minutes, and don’t want to use
those “system fonts” (or if I want to use them, I will copy them to my texmf
directories)!
hm, i wonder why that takes so long as i get:
tex tree:
561 tree files identified,5 skipped, 5 duplicates, 556 hash entries
added, runtime 14.282 seconds
426 tree files identified,7 skipped, 5 duplicates, 419 hash entries
added, runtime 12.297 seconds
8 tree files identified,0 skipped, 0 duplicates, 8 hash
entries added, runtime 0.188 seconds
0 tree files identified,0 skipped, 0 duplicates, 0 hash
entries added, runtime 0.156 seconds
677 tree files identified,1 skipped, 1 duplicates, 676 hash entries
added, runtime 0.672 seconds
system:
2 system files identified, 0 skipped, 0 duplicates, 2 hash
entries added, runtime 0.047 seconds
437 system files identified, 57 skipped, 57 duplicates, 380 hash entries
added, runtime 20.001 seconds
20 system files identified, 1 skipped, 1 duplicates, 19 hash
entries added, runtime 0.063 seconds
0 system files identified, 0 skipped, 0 duplicates, 0 hash
entries added, runtime 0.031 seconds
0 system files identified, 0 skipped, 0 duplicates, 0 hash
entries added, runtime 0.047 seconds
anyway, in a next beta you can set this in texmf.cnf.lua:
return {
content = {
directives = {
[fonts.usesystemfonts] = false,
},
},
}
Best do that in texmf-local as a next update will overwrite the main cnf
file. Entries in the he local file overload main ones.
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
___
Re: [NTG-context] MacOsX Mavericks and Luatex
Hi, Concerning unix: Norbert Preining (tex live maintainer) found out that when font directories are symlinks, file access is much slower due to more lookups (esp with long names as then the lookup is indirect which means more disk access). Of course on a modern machine with ssd this is neglectable. 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 ___
Re: [NTG-context] dejavu: inline math fraction spacing too tight?
On 10/24/2013 2:46 PM, H. Özoguz wrote: \setupbodyfont [dejavu,12pt] \starttext $a/b$ $1/2$ $π/3$ \stoptext Is this indeed the desired spacing? What do others think? Thanks. I think you are right, I don't know if this is really desired, but I don't think so. Escpecially one gets problems with 2 in the denominator. \setupbodyfont [dejavu,12pt] \starttext $1/2$ $1\,/\,2$ \stoptext The second hand-tuned example is obviously nicer. it looks like a font issue to me .. i could hack a solution but prefer not to do that (the less exceptions we have the better) 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 ___
Re: [NTG-context] MacOsX Mavericks and Luatex
On Fri, 25 Oct 2013, Hans Hagen wrote: On 10/25/2013 7:01 AM, Schmitz Thomas A. wrote: On 24 Oct 2013, at 16:44, Aditya Mahajan adit...@umich.edu wrote: You need to set it to a dummy directory! See: http://tex.stackexchange.com/a/136073/323 No, even that doesn’t help: echo $OSFONTDIR /tmp/dummy and then on a first run (after regnerating the format with this variable set), I get lines such as fontsnames 'OSFONTDIR' specifies path '/Users/tas/Library/Fonts' fontsnames 'OSFONTDIR' specifies path '/Library/Fonts' fontsnames 'OSFONTDIR' specifies path '/System/Library/Fonts' fontsnames globbing path '/System/Library/Fonts/**.OTF' fontsnames 68 system files identified, 2 skipped, 2 duplicates, 66 hash entries added, runtime 43.223 seconds So something appears to be overriding the variable that I set. But what? And why? And how do I stop it? On 24 Oct 2013, at 23:40, Hans Hagen pra...@wxs.nl wrote: I don't understand the speed issue. We're talking about relatively few fonts only and context will not scan them unless there is a change. After a remake a rescan takes 9 sec on my laptop and 6 sec once the directories have been cached (windows 8 / 64 bit / i7 / ssd). Only an initial full scan takes a while (deleted cache), but that's mostly because I have a pretty large font collection in my texmf-fonts tree. You’re right of course that it’s only the initial run when a new font cache has to be built, but the time I get on os x is much longer than what you report: with rescanning of system fonts: system | total runtime: 114.131 (yes, that’s almost 2 minutes!) And I don’t want to twiddle my thumbs for two minutes, and don’t want to use those “system fonts” (or if I want to use them, I will copy them to my texmf directories)! hm, i wonder why that takes so long as i get: tex tree: 561 tree files identified,5 skipped, 5 duplicates, 556 hash entries added, runtime 14.282 seconds 426 tree files identified,7 skipped, 5 duplicates, 419 hash entries added, runtime 12.297 seconds 8 tree files identified,0 skipped, 0 duplicates, 8 hash entries added, runtime 0.188 seconds 0 tree files identified,0 skipped, 0 duplicates, 0 hash entries added, runtime 0.156 seconds 677 tree files identified,1 skipped, 1 duplicates, 676 hash entries added, runtime 0.672 seconds system: 2 system files identified, 0 skipped, 0 duplicates, 2 hash entries added, runtime 0.047 seconds 437 system files identified, 57 skipped, 57 duplicates, 380 hash entries added, runtime 20.001 seconds 20 system files identified, 1 skipped, 1 duplicates, 19 hash entries added, runtime 0.063 seconds 0 system files identified, 0 skipped, 0 duplicates, 0 hash entries added, runtime 0.031 seconds 0 system files identified, 0 skipped, 0 duplicates, 0 hash entries added, runtime 0.047 seconds That is similar to what I get (regular hard drive, no SSD) mtxrun --script fonts --reload --force | grep time fonts | names | 757 tree files identified, 245 skipped, 244 duplicates, 512 hash entries added, runtime 7.720 seconds fonts | names | 224 tree files identified, 60 skipped, 48 duplicates, 164 hash entries added, runtime 3.052 seconds fonts | names | 2 tree files identified, 1 skipped, 1 duplicates, 1 hash entries added, runtime 0.404 seconds fonts | names | 0 tree files identified, 0 skipped, 0 duplicates, 0 hash entries added, runtime 0.406 seconds fonts | names | 1503 tree files identified, 210 skipped, 113 duplicates, 1293 hash entries added, runtime 1.034 seconds fonts | names | 50 system files identified, 14 skipped, 14 duplicates, 36 hash entries added, runtime 4.429 seconds fonts | names | 126 system files identified, 21 skipped, 21 duplicates, 105 hash entries added, runtime 0.548 seconds fonts | names | 0 system files identified, 0 skipped, 0 duplicates, 0 hash entries added, runtime 0.005 seconds fonts | names | 0 system files identified, 0 skipped, 0 duplicates, 0 hash entries added, runtime 0.005 seconds fonts | names | 35 system files identified, 0 skipped, 0 duplicates, 35 hash entries added, runtime 0.007 seconds fonts | names | total scan time 39.783 seconds 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://tex.aanhet.net archive : http://foundry.supelec.fr/projects/contextrev/ wiki : http://contextgarden.net ___
Re: [NTG-context] Aligning Part-Title in TOC
Any ideas ... ? :) ___ 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 ___
