View Single Post
Old 06-28-2018, 01:01 PM   #8
KevinH
Sigil Developer
KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.
 
Posts: 8,809
Karma: 6000000
Join Date: Nov 2009
Device: many
Okay, I think I have this one fixed without have to ignore the entire nav. I was able to use regular expressions to try harder to extract the toc, landmarks, and page-list just in case a parser error exists when asked to parse the nav someplace else. So it should be more robust to parsing errors even just temporary ones.

I have pushed the fixes to master.

If you get a free moment, please give this a try.
KevinH is offline   Reply With Quote