[HN Gopher] Typesetting the LaTeX Way (2013)
___________________________________________________________________
Typesetting the LaTeX Way (2013)
Author : tosh
Score : 43 points
Date : 2024-03-29 12:11 UTC (2 days ago)
(HTM) web link (chriscummins.cc)
(TXT) w3m dump (chriscummins.cc)
| contr-error wrote:
| What a bait-and-switch Google Chrome has been...
| Kwpolska wrote:
| (2013) shows here, and it's about web pages, not typesetting
| printable documents.
|
| Hyphenation is built into CSS now:
| https://developer.mozilla.org/en-US/docs/Web/CSS/hyphens
| (although I personally don't think hyphenation is really useful
| on the Web).
|
| Also, the sans versions of Computer Modern don't really scream
| LaTeX at me like the classic serif version does...
| spockz wrote:
| I found that hyphenation doesn't get the same quality of
| typesetting as latex did, also because there are no page breaks
| to take into account.
|
| One exception though is documentation. I find justified and
| hyphenated pages of documentation much easier to ingest than
| without. Maybe that is because my mind has a trained response
| to go into learning mode because of reading so many papers.
|
| For me the results are significant. Without hyphenation and
| justified alignment, my eyes "glide" off texts on screen as if
| they were islands. With, I can stay on it.
| philsnow wrote:
| Looking at https://checkmyworking.com/cm-web-fonts/ with firefox
| on macos, it doesn't look like the kerning is quite right. In
| "consectetur" there is too much space between the 't' and 'e'.
|
| I don't know enough about font formats, but is something lost
| when translating from metafont to ttf? Is there something
| specific about how TeX kerns fonts that hasn't been copied ^W
| ported to web browsers?
___________________________________________________________________
(page generated 2024-03-31 23:01 UTC)