![](https://secure.gravatar.com/avatar/23c65792d6f3eb5f6194f6ec9eadc2ac.jpg?s=120&d=mm&r=g)
Hi, Hans. The last release is considerably faster for smaller documents (for larger documents differences seem to be neglectable). Thank you for such an improvement. However, something is wrong with one manual: luametatex manual won't compile: 156 Beware: the values are always saved in the format, independent of the setting 157 of \prm {savinghyphcodes} at the moment the format is dumped. 158 159 A boundary node normally would mark the end of a word which interferes with for 160 instance discretionary injection. For this you can use the \prm {wordboundary} 161 as a trigger. Here are a few examples of usage: 162 163 \startbuffer 164 discrete---discrete 165 \stopbuffer 166 >> \typebuffer \startnarrower \dontcomplain \hsize 1pt \getbuffer \par \stopnarrower 167 \startbuffer 168 discrete\discretionary{}{}{---}discrete 169 \stopbuffer 170 \typebuffer \startnarrower \dontcomplain \hsize 1pt \getbuffer \par \stopnarrower 171 \startbuffer 172 discrete\wordboundary\discretionary{}{}{---}discrete 173 \stopbuffer 174 \typebuffer \startnarrower \dontcomplain \hsize 1pt \getbuffer \par \stopnarrower 175 \startbuffer 176 discrete\wordboundary\discretionary{}{}{---}\wordboundary discrete A number should have been here; I inserted '0'. (If you can't figure out why I needed to see a number, look up 'weird error' in the index to The TeXbook.) The prepackaged PDF manual is also broken: an error banner. Regards, Jairo :) El vie., 30 de oct. de 2020 a la(s) 17:29, Hans Hagen (j.hagen@xs4all.nl) escribió:
Hi,
I might have uploaded a new version by accident so be careful when you update. Make a backup first. Sorry,
The test suite compiles, which doesn't day all is ok as i just run it.
There are no funcional changes, only a bit of conceptual reworking of some internals in the process of adapting to new features as well as protection, so
\starttext
\start \def\framed{oeps} \stop
\stoptext
is permitted, but when you run with
context --overloadmode=warning
you get a warning and with
context --overloadmode=error
the run aborts. Here is a user macro example:
\frozen \def\foo{oeps} \def\foo{oeps} % warning or error \overloaded\def\foo{oeps} % okay
eventually all system macros will be way more protected, being primitive, permanent, immutable to mention some of the possible properties. It's work in progress as you can imagine some pitfals and in order for it to work well quite some has to be flagged. Also, I have to play with some related additions.
(This version also makes more extensive use of some new macro features but that's for later.)
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
___________________________________________________________________________________