In studying Papyrix's HTML engine... I'd be tempted to rewrite my own for #merephone!
What they have makes perfect sense for an ereader's firmware, but... If you're not going to reread any given webpage getting rid of an XHTML5 conversion pass makes more sense, & I have a few reasons I'd want a better styling engine!
With a proper CSS implementation I can improve accessibility with more config options & a nice screenreader!
But I also want something I can reuse for streetmap rendering.
1/2!
I have experience in building my own browser engines so I know some tricks I can apply, but at the same time I should be careful to favor performance over features!
Codesize matters too because I'd rather dedicate ROM to other features.
So I wouldn't support much of CSS, & I'd use a simpler non-standard algorithm for repairing improper HTML. Papyrix's code will handle text layout/rendering.
And Arduino-Flite gives me SSML I can use for a nice HTML/ePub screenreader!
2/2!