Discussion
Once Papyrix has loaded a Markdown ebook, it uses a MarkdownParser class to render it.
Skipping past the character-testing utils, near-empty constructor & destructor, resetter, & accessors... There's a helper to append a validated word (with nil byte appended & normalized to NFC Unicode-form) to the current text block while checking whether its Arabic & hence should be laid out right-to-left.
There's a helper to flush the existing text-block if any & set a new one with a given style.
1/?
That method invoked via that callback adds a line of text to a page by computing the lineheight (as per before), checking whether it fits on the page or if a new page should be created, adds it to the page, & increments the Y coordinate by the lineheight. If it didn't fit it checks if there's a callback it should invoke, & if so also checks if RAM's so low we should leave the rest of this work until later. Regardless it creates & remembers a new page checking if we've hit the limit.
3/?
There's a helper for carefully reading a line of text byte-by-byte from a file while applying simple character-encoding conversions.
There's a callback for the markdown parser which checks if we've hit the page limit & branches over the given token to invoke any of the helpers I've described while updating appropriate properties.
While the primary method opens the given file, retrieves the filesize validating that its non-empty, seeks to a remembered offset, ...
4/5!
... if at start of file carefully checks for a byte-order-mark, logs what its doing, initializes various properties, inits the actual parser (which I'll describe tomorrow!), checks if there's a pending page to remember, retrieves a pending page it remembered, flushes or remembers a pending text-block, increments the Y axis by the pending spacing, starts a new text block, inits some properties, enters a mainloop, cleans up with flushes, & updates its progress properties.
5/6!!
Flushing a text block involves flushing the rest of the current word, validating that the paragraph's non-empty, initializing a new page if necessary, calculating line height taking into account configured line-compression, asking the text-block to apply its text-wrapping with a callback deferring valid data to another method, & checks whether we've exceeded a page-limit & the spacing level to update the Y coordinate or a `pendingSpacing_` property.
2/?