Re:Brian Kernighan on the Typesetting of “The Go Programming...
by tomjen3 on Monday April 11, 2016 @12:28PM
(#11472736)
It also means your documents are locked to a proprietary standard that isn't that widely used (compared to say MS Word) and as such, may not be totally recoverable 10,20 or 30 years from now. You want to keep that in mind when you choose which typesetting system to use - for the record, I keep a digital diary that I intend should still exist 50 years from now. I use only markdown, and the occasional entry that mention really private stuff is ascii encrypted with GPG.
[ Parent
| on HN ]
Re:Brian Kernighan on the Typesetting of “The Go Programming...
by jnbiche on Monday April 11, 2016 @02:32PM
(#11473967)
>It also means your documents are locked to a proprietary standard that isn't that widely used (compared to say MS Word)
HTML and CSS?
Re:Brian Kernighan on the Typesetting of “The Go Programming...
by tomjen3 on Monday April 11, 2016 @04:54PM
(#11475015)
I assume there is some additional special sauce that enables you to do things that are not possible in a browser, which means you still won't get the exact formatting, index, etc correct.
Re:Brian Kernighan on the Typesetting of “The Go Programming...
by oxplot on Tuesday April 12, 2016 @06:19AM
(#11478331)
To extent of my knowledge, Prince only implements web standards set by w3. The reason browsers can't do what Prince does is because they lack support for those standards.
Wikipedia lists some of what Prince does that others don't:
https://en.wikipedia.org/wiki/Comparison_of_layout_engines_(...