[NTG-context] problem with non-printing hex 0x0C

Hans Hagen j.hagen at xs4all.nl
Wed Feb 6 09:51:42 CET 2019


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
-----------------------------------------------------------------


More information about the ntg-context mailing list