4 ms·
I wonder if someone could shed some light on this (from type composition straight and curly quotes): > Computer scientists and documentation writers, ta
by buttproblem 13y ago
I wonder if someone could shed some light on this (from type composition straight and curly quotes):
> Computer scientists and documentation writers, take note: straight quotes and backticks in software code should never be converted to curly quotes. Those marks are, of course, part of the functional syntax of the code and must be reproduced literally. While fans of LaTeX have often written me to trumpet its typesetting superiority, I’ve never seen any LaTeX-created documentation that’s gotten this right.
As a LaTeX user (and not a very good one) I'm not too sure what I've been doing wrong.
- mzs 13y agoIf you have been doing this: \usepackage{listings} \usepackage{textcomp} ... upquote=true ... You have been doing nothing wrong.
- mariusae 13y agoAlso make sure you read Eddie Kohler's LaTeX usage notes: http://www.read.seas.harvard.edu/~kohler/latex.html
- ygra 13y agoIt's very common to see ”Hello World” in LaTeX-written documents. The problem in my eyes is often that well-meaning people tell others that LaTeX will automagically make your document look good and professional, yet neglect to point out that you still have to know the details to achieve that. Proper quotes, proper usage of non-breaking spaces, proper hyphenation when the default breaks down, etc. are all things you have to consider regardless of the application. LaTeX may have nicer default styles and a few superiour algorithms (e.g. line breaking for justified text), but overall result quality for people without any clue is in my experience not higher than with Word.