I’ve wrote a PDF parser in my younger days. 0/10 would not do again, even in Rust. The annotations spec is the absolute worst to deal with :/ Well depends on the scope of the parser
Hey, @rustlang folks - who wants to work on a new PS/PDF parser, renderer, and sandbox?https://twitter.com/hanno/status/1066000718589513728 …
-
-
-
I worked a lot with PS (and also some Forth) in my younger days (late 80s and early 90s). I know that the core is quite simple. I have no trouble believing that everything that's accumulated around it on the way to PDF today will be tangled and tricky.
-
The core is quite simple and I’d admit, well made. Annotations were supposed just to well, annotate. But now you can annotate with anything, images, web pages, javascript, like pretty much anything.
-
oh, hell, javascript? I'm out! :)
-
I still have nightmares of the 2k+ pages spec
(and most of it being various annotations) IIRC
End of conversation
New conversation -
-
-
Worth noting most (all?) of these bugs have been logic bugs. So starting from scratch might be useful and Rust might help you get it done faster, but the memory safety wouldn't have helped here.
-
understood, but taking "not fixable" on face value, if you're going to start again you don't want to be making new memory-safety bugs.
-
Absolutely, and sounds like a fun (if ambitious!) project. Just sayin' :)
End of conversation
New conversation -
-
-
https://tectonic-typesetting.github.io/ is mostly actually C code, and is a TeX engine not a PDF renderer, but it has some relevant bits ...
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.