4 ms·
Not to 100%. I used a combination for tex4ht, tex4ht configuration, several hacky post processing scripts, and manual editing. Converting a Latex document to a
by smarr 11y ago
Not to 100%. I used a combination for tex4ht, tex4ht configuration, several hacky post processing scripts, and manual editing. Converting a Latex document to a nice HTML site is easily the worst part of the whole writing process :-/
- anonymousDan 11y agoLooks great. Out of interest, what were the main things that tex4ht doesn't give you out of the box?
- smarr 11y agoClean HTML (no superfluous tags), proper links to references (the rendering splits the links between author and year), ligatures are broken in browsers, standard footnotes are insensible for HTML, the standard HTML used for headers, figures, and others wasn't to my liking.
- jacobolus 11y agoOne recommendation: use ragged-right rather than justified text in the HTML version. Because browsers use a line-by-line text composer instead of full-paragraph composition, and don’t do any hyphenation, fully justified text looks terrible on web pages, especially in relatively narrow columns. In the case of this specific document, there’s all kinds of nasty gappy whitespace in the webpage version. It’s made worse by the spaces in “et al. 19XX” getting turned into non-breaking spaces. You really want to fix that if you can. For example, look at the 3rd and 9th line in this screenshot. http://i.imgur.com/H6ROnyQ.png http://i.imgur.com/H6ROnyQ.png But even disregarding that problem, many lines end up looking pretty bad. [Note: don’t read this as personal criticism. The fault lies about 90% with the browser vendors who care more about saving a few microseconds of compute time than making legible documents.]
- wakaflockafliz 11y agoI didn't notice this ever before, then I read your comment. Now I see it all over the place...oh man.
- anewhnaccount 11y agohttps://github.com/bramstein/typeset https://github.com/bramstein/typeset