[NTG-context] weekend update
Hi,
I uploaded a new version:
-- fix for hraban's svg image (one character patch)
-- more verbose link comments for pablo (for experimenting)
-- support for stacking at the tex end (maybe for presentations)
\starttext
\definestacking[one]
\definestacking[two]
\startbuffer
This is a test \stacking [one] {and a proof} of \stacking [two]
{concept} indeed
\stacking [one] {\blackrule [width=4cm]} is it and the question is how
\stacking
[two] {\scale [s=2] {fancy}} we can go
\startstacking[one]
\startformula
\sqrt{1+x}
\stopformula
\stopstacking
and how useful \stacking[two]{\inframed{it}} is.
\stopbuffer
\startstackingsteps[one,two,{one,two}]
\startTEXpage[offset=1ts]
\getbuffer
\stopTEXpage
\stopstackingsteps
\startTEXpage[offset=1ts] \setupstacking[criterium={one}] \getbuffer
\stopTEXpage
\startTEXpage[offset=1ts] \setupstacking[criterium={two}] \getbuffer
\stopTEXpage
\startTEXpage[offset=1ts] \setupstacking[criterium={one,two}] \getbuffer
\stopTEXpage
\stoptext
-- support for more private pdf
\enabledirectives[backend.pdf.nounicode=noai]
\enabledirectives[backend.pdf.nounicode=nopilot]
\enabledirectives[backend.pdf.nounicode=justread]
\enabledirectives[backend.pdf.nounicode=✅]
\enabledirectives[backend.pdf.nounicode=✅❌]
\enabledirectives[backend.pdf.nounicode=❌]
\startTEXpage[offset=1ts]
\input tufte
\stopTEXpage
The last option can be handy when you don't want to make harvesting your
documents too easy for these ai bots (as in cloud based pdf stuff). It's
the first outcome of the multi-year, multi-stage, very scientific
'inacessible pdf' project that Mikael S. and I recently started.
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 /
https://mailman.ntg.nl/mailman3/lists/ntg-context.ntg.nl
webpage : https://www.pragma-ade.nl / https://context.aanhet.net (mirror)
archive : https://github.com/contextgarden/context
wiki : https://wiki.contextgarden.net
___
Re: [NTG-context] weekend update
For a good number of years now I've been using P4D and P4V from Perforce for version control. As it happens it, one is able to control what ends up in the repository and what is left out, thankfully. Regardless, this should be very helpful Hans. It'll be great to be able to quickly scan the project files that matter, knowing that all the clutter is safely kept somewhere else. So thanks for this. Perforce, by the way. (Freely available for smaller projects): P4D https://www.perforce.com/downloads/helix-core-p4d P4V https://www.perforce.com/downloads/helix-visual-client-p4v And the diff tool is absolutely excellent (the reason I first went with it): https://www.perforce.com/downloads/visual-merge-tool Best, Richard -- *T* +6433121699 *M* +64210640216 *E* rmaho...@indica-et-buddhica.org *IM* https://t.me/rmahoney *W *https://indica-et-buddhica.org/** *Indica et Buddhica *Littledene Bay Road Oxford NZ <https://indica-et-buddhica.org/> - Original message - From: Hans Hagen To: mailing list for ConTeXt users Subject: [NTG-context] weekend update Date: Saturday, 24 July 2021 05:05 Hi, This time the update has, appart from already mentioned mp fixes and additions, another new feature. % runpath=texruns:whatever % runpath=e:/temporary/texruns/runtest % runpath=temp:texruns/runtest % runpath=home:texruns/runtest \starttext test \stoptext In context the first line can be used to control some aspects of the run and runpath (also as command line switch) will process the document elsewhere. The main reason for this feature is that when you have files in for instance a git repository (or export), you don't want the run path to be polluted by temporary files because everything can end up in the repository when it gets updates (after all these years I don't expect this pollution issue to be solved; svn is more explicit in what goes in). So, for instance the manuals are on clean paths (on my machine i (am) put(ting) experiments, todo's etc under an ignored /private subpath which means that styles can still be found if needed). The texruns: prefix resolves to an environment variable with the same name or when not set, to the temp directory. The temp: and home: prefixes resolve (as usual) to their counterparts (prefixes are a very old mkii mechanism but still useful). When not present a path will be created, when no chdir is possible the run aborts. There are probably some cases when resources are not found but that will be dealt with in due time. I might also update the underlying mechanisms at some point. I already adapted some manuals so that means that when users process these themselves they will not see the runfiles fly to the temp path unless 'texruns' is configured. So be it. 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 ___ ___ 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] weekend update
Hi, This time the update has, appart from already mentioned mp fixes and additions, another new feature. % runpath=texruns:whatever % runpath=e:/temporary/texruns/runtest % runpath=temp:texruns/runtest % runpath=home:texruns/runtest \starttext test \stoptext In context the first line can be used to control some aspects of the run and runpath (also as command line switch) will process the document elsewhere. The main reason for this feature is that when you have files in for instance a git repository (or export), you don't want the run path to be polluted by temporary files because everything can end up in the repository when it gets updates (after all these years I don't expect this pollution issue to be solved; svn is more explicit in what goes in). So, for instance the manuals are on clean paths (on my machine i (am) put(ting) experiments, todo's etc under an ignored /private subpath which means that styles can still be found if needed). The texruns: prefix resolves to an environment variable with the same name or when not set, to the temp directory. The temp: and home: prefixes resolve (as usual) to their counterparts (prefixes are a very old mkii mechanism but still useful). When not present a path will be created, when no chdir is possible the run aborts. There are probably some cases when resources are not found but that will be dealt with in due time. I might also update the underlying mechanisms at some point. I already adapted some manuals so that means that when users process these themselves they will not see the runfiles fly to the temp path unless 'texruns' is configured. So be it. 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 ___
