- dev-context - NTG Mailing Lists

Automatic generation of filename database
by Oliver Buerschaper 14 Feb '11

14 Feb '11

Hi, it seems that the minimals have lost their ability to automatically generate the luatex filename database… now mtxrun --generate is needed (again) before anything else works. Formats are still generated automatically though. I'm afraid I can't pin down when that change happened but it's present at least in 2011.02.11 18:18 2011.02.05 11:37 Would it be much work to (re)enable this? I'm aware that all things configuration files have undergone a massive overhaul recently but this feature would really be nice to have again :-) Best, Oliver

2 2

context installation/setup/texmfcnf.lua
by Mojca Miklavec 09 Feb '11

09 Feb '11

Hans, I was away for a while. What exactly is the current status of ConTeXt beta and what exactly do I need to change? Is the change for "selfautoparent:" ready now? Is there anything else that I should do right away? Mojca

2 3

beta
by Hans Hagen 07 Feb '11

07 Feb '11

Hi, I uploaded a beta to the ftp server. Changes are: -- cleaned up logging, consistently using logs.new -- this makes it possible to disable log categories (using --silent or using directive logs.blocked) -- cleaned up regime code (also a hack to force loading under utf) -- as a side effect some code moved to lfg files I probably made some types as logging happens all over the place. I hope that it does not break third party modules. 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 -----------------------------------------------------------------

1 0

\nonknuthmode breaks _ in protected mode
by Wolfgang Schuster 02 Feb '11

02 Feb '11

Hi Hans, the \nonknuthmode in core-def.mkiv breaks _ in modules: \starttext \the\catcode`\_ \unprotect \the\catcode`\_ \protect \the\catcode`\_ \stoptext It helps when you enable \nonknuthmode with \everystarttext (or \everyjob), e.g. \appendtoks \nonknuthmode \to \everystarttext Wolfgang

2 4

beta
by Hans Hagen 30 Jan '11

30 Jan '11

Hi, [for those with access to the ftp server] There have been some changes to the resolver code. In order to make trees relocatable (handy if you run from a usb stick or so), the texroot is now more abstract. The final implemention might change but it seems to work ok (here). It can be tested with an existing minimal: - delete the context path under texmf-cache - unzip cont-tmf.zip in texmf-context - copy mtxrun.lua from the scripts path to the bin path - update the texmfcnf.lua file (just copy contextcnf.lua) - remake the file database In logs you will notice prefixes like selfautoparent:texmf which comes from the texmfcnf.lua file (plus a preset TEXMF). That abstraction is used in cached names and is resolved at runtime. It might change to an url like syntax at some point. I hope that Mojca does not get too fed up after this change -) 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 -----------------------------------------------------------------

2 7

Help regarding Kpsewhich and mtxrun
by Julius Canute 23 Jan '11

23 Jan '11

Please correct me if i am wrong. If kpsewhich is not used and replaced by mtxrun why is it included in context minimals?? Doubt: Inside texexec file i find this line: mtxrun --usekpse --execute texexec "$@" Suppose say i type the following command. texexec --pdf sample.tex It will somehow call mtxrun which in turn will invoke 'texmfstart.rb' i guess. The above command somehow invokes 'pdftex' which processes sample.tex file. But pdftex is a binary how does it come to know about location of fonts and all other information unless there is some interface that is hard coded???

3 2

\usemodule and prtcatcodes
by Wolfgang Schuster 18 Jan '11

18 Jan '11

Hi, why does \usemodule load the requested file with “prtcatcodes” settings when nearly each module has \unprotect and \protect at the begin and end of the file? I ask this because of a recent question [1] on the list where a user defined shortcuts for math. Maybe a module isn’t the perfect thing for these things and he can put them in a environment but now comes the next problem. When you load a environment in this way: \environment myenvironment \starttext … \stoptext the file is loaded again with prtcatcodes while in the following form \startproduct myproduct \environment myenvironment … \stopproduct the environment is loaded with ctxcatcodes. While prtcatcodes make sense for a module i can’t understand why they are used for environments. [1] http://www.ntg.nl/pipermail/ntg-context/2011/055915.html Wolfgang

2 5

Help regarding context architecture and compilation
by Julius Canute 17 Jan '11

17 Jan '11

Hi, I am doing a study about context. I wanted to understand context and its interaction with other components in the system. Is there a architecture diagram that could describe it ? Also i want to make context available through fink. For which i need to understand the dependencies of context. Looking for a way to build context from the source manually without using minimal context? Can anyone help me do the compilation manually from source or at-least point to some references to do that? Regards A.Julius Canute

5 9

new beta
by Hans Hagen 10 Jan '11

10 Jan '11

Hi, I uploaded a new beta: The character definitions have been updated (esp math, thanks to Aditya). After some testing by Wolfgang the decision was made to permit _ in macronames in modules. So, the following works: \unprotect \def\test_test_test#1#2{#1+#2=whatever} \test_test_test{1}{2} \protect In principle we can also support ^. The mkiv code base no longer uses _ and ^ in math in modules and those who write modules should avoid them as well. So, when writing macros in unprotected mode, one schould use: $x\normalsuperscript2\normalsubscript n$ Taco and I think that we can safely switch to \nonknuthmode in mkiv so this might happen soon (which means that _ and ^ become normal characters in text mode). Actually, being permanently in \nonknuthmode would permit _ and ^ in modules again. We could even make _ and ^ always letters outside math in which case \text_test etc would become possible everywhere but that needs some more consideration. In that case \def\make_subscript#1#2{\mathematics{#1_{#2}}} \make_subscript{x}{2} becomes valid everywhere. We can discuss this in detail at the dev list. 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 -----------------------------------------------------------------

2 1

Bugs regarding module documentation
by Wolfgang Schuster 06 Jan '11

06 Jan '11

Hi Hans, 1. Typo (s-mod-01.mkii|mkiv) Line 40: two ! in the stretch value [\v!verytolerant,\v!!stretch] 2. It’s not possible to produce a pdf from mkvi file (mtx-modules.lua) Line 121: Add “mkvi” to the list of suffixes local suffixes = table.tohash { 'tex','mkii','mkiv','mp' } Kind regards, Wolfgang

2 1