On 7/10/25 10:54, Hans Hagen via ntg-context wrote:
On 7/10/2025 9:08 AM, Max Chernoff via ntg-context wrote: [...]
Some notes:
here's the thing: without yoyur changes (like markinfo which I'm was checking for the version for a reason, i don't add that kind of checks for fun), the document validates here, so then i thought, well, let's update verapdf and for sure a document that validated a while ago doesn't now .. one can wondert how many validated documents there are around that actually invalidate now ...
I’m afraid that the validator is also work in progress.
- I had to manually tag every paragraph with \startparagraph/\stopparagraph, which was annoying.
well, that also depends on the concept of paragraph i guess .. one can't make structure from non-structure
Well, paragraphs may contain line breaks and TeX seems to mark paragraphs as text that is between two or more blank lines (or `\par`). Otherwise, I don’t see how this behaves differently: \setupindenting[yes, big] \setupwhitespace[big] \setupheads[indentnext=yes] \starttext \section{Line break} \dorecurse{5}{Line \recurselevel\ in paragraph. \ifnum\recurselevel<5\\\fi} \section{Different paragraphs} \dorecurse{5}{Paragraph \recurselevel. } \stoptext
- The file validates successfully, but there are lots of "Nested MCID" warnings.
But not invalid, right?
I have seen these too (with MCID 30 to 35): WARNING: Content stream (object 1 0 obj): Nested MCID - 30 But that a GUI validator uses the terminal to give warnings for the text it is validating is something way beyond my understanding. I mean, what happens if I invoke the validator by double-clicking? At least in Linux, it is possible not to have a terminal window which displays these warnings. Many thanks for your help again, Pablo