On 2/5/2019 9:28 PM, martin wrote:
I had a problem that kept me busy for a few hours. A \page command had
no effect, the text just continued in the pdf.
The culprid turned out to be a hex 0x0C, a formfeed character. Once I
removed them all was good. It got introduced by extracting the text from
a PDF.
I realize my files should be "clean" of control characters and ConTexT
should (maybe) not be stripping those characters. Then again, they serve
no purpose in the document. So...
My question: Isn't some more resilience sensible so commands don't
break? Or error messages?
a formfeed is acting like a newline
\catcode\tabasciicode \spacecatcode
\catcode\endoflineasciicode \endoflinecatcode
\catcode\formfeedasciicode \endoflinecatcode
\catcode\spaceasciicode \spacecatcode
-----------------------------------------------------------------
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
___________________________________________________________________________________
