3 ms·
> The author used the wrong tool for composing text. They should have used a text editor. Then you have the opposite problem: most text editors make it non-tri
by oneeyedpigeon 2y ago
> The author used the wrong tool for composing text. They should have used a text editor.
Then you have the opposite problem: most text editors make it non-trivial to work with unicode. I mean, I've taken the time to learn how to type curly quotation marks vs. straight ones, but not everyone has and keyboards don't make it easy.
- pavel_lishin 2y agoMay I ask why you use curly quotation marks instead of the straight ascii ones?
- oneeyedpigeon 2y agoIn written text, I think they're far more attractive. If I need to put forward some kind of 'objective' argument, then differentiating between open and closed seems to make logical sense. Check out any printed material: 99.9% of the time, it uses curly quotes.
- verandaguy 2y agoMy mental framework has been: - Curly quotes are a typographic sugar that's easier on the human eye when reading normal, human-language text. It's reasonable for them to be automatically inserted into your typing in something like a word processor, and depending on which language you're writing in, there may be strong orthographic rules about the use of curly braces (or their cognates, like « guillemets », etc). - Straight quotes belong in code by a combination of convention and practicality; unicode characters should be escaped wherever it's practical to do so (for example, if you must use "→" in your code, prefer to do e.g. "\u2192" instead -- it's clearer for future users which exact unicode arrow you were using there).