Slashdot Mirror


Has the Internet Killed Curly Quotes? (theatlantic.com)

Glenn Fleishman, writing for The Atlantic: Many aspects of website design have improved to the point that nuances and flourishes formerly reserved for the printed page are feasible and pleasing. But there's a seemingly contrary motion afoot with quotation marks: At an increasing number of publications, they've been ironed straight. This may stem from a lack of awareness on the part of website designers or from the difficulty in a content-management system (CMS) getting the curl direction correct every time. It may also be that curly quotes' time has come and gone. Major periodicals have fallen prey, including those with a long and continuing print edition. Not long ago, Rolling Stone had straight quotes in its news-item previews, but educated them for features; the "smart" quotes later returned. Fast Company opts generally for all "dumb" quotes online, while the newborn digital publication The Outline recently mixed straight and typographic in the same line of text at its launch. Even the fine publication you're currently reading has occasionally neglected to crook its pinky.(Via DaringFireball -- John's take on this is insightful.) At Slashdot, we also avoid curly quotes -- and when we miss, you see them as weird characters on the site!

38 of 207 comments (clear)

  1. Twitter isn't helping by TomR+teh+Pirate · · Score: 2

    Some news sites have gone straight to embedding Tweets rather than using classic citation. Frankly, I think it's sloppy writing.

    1. Re:Twitter isn't helping by Xenographic · · Score: 4, Informative

      I don't think curly quotes are dead, either. I think they just keep getting morphed into Ã(TM) trash, as can be seen in many past Slashdot stories.

    2. Re:Twitter isn't helping by v1 · · Score: 2

      that causes a problem later when you try to search your document for and it can't find it because your "smart word processor" changed the quote to a smart start-quote and now you have no way to type that as part of the search string.

      The other problem being they aren't ascii so they have to be represented by unicode. Basic text editors are hit-and-miss on their support for unicode, causing a litany of problems. Screwing up character counts and indexing, right/left arrows attempting to step over the ansii one byte at a time, etc.

      The first thing I do before using a "smart" word processor is to turn off those smart quotes, hyphens (the double long -) and hyperlink auto embedding. Oh, and try copying some code out of a word processor or website that has "educated" your quotes, into your IDE. oh, those just LOVE smart quotes... (and LOVE to blow up with creative and unhelpful errors, at often incorrectly offset locations as a result of your pasting in garbage)

      --
      I work for the Department of Redundancy Department.
    3. Re: Twitter isn't helping by BarbaraHudson · · Score: 4, Insightful
      Curly quotes didn't exist on manual typewriters, and neither did the numbers zero (used an uppercase oh) or one (use a lowercase ell).

      When it was absolutely essential to distinguish between an uppercase oh and a zero, an easy way was to backspace and type a slash through it. Differentiation between a lowercase ell and a one was sometimes done by underlining the ell to represent the number one, but this was rare.

      We got along fine without stupid smart quotes, and they add nothing to readability.

      --
      "Transparent" is a shit show that trades on every stereotype going. A man in drag is NOT a transsexual.
    4. Re: Twitter isn't helping by Z00L00K · · Score: 2

      And those "smart" quotes that appears on and off really messes up some documentation where you document command lines in a document. The straight quotes are good enough, any software that automagically replaces them makes it impossible to do a copy/paste of command lines in documentation and other similar stuff.

      So the "smart" quotes and dashes are a good example of how you overdo stuff without providing any real value for the users.

      --
      If builders built buildings the way programmers wrote programs, then the first woodpecker would destroy civilization.
    5. Re: Twitter isn't helping by Misagon · · Score: 2

      There has been great diversity among typewriters layouts. They have not been standardized as much as computer keyboard layouts and characters sets have. Different typewriter brands did not need to be interoperable.

      Some brands of typewriters got different keys between I/1 and O/0 back in the early 1900's. Other brands did not separate the keys even in the 1980's.

      Among computers and teletypes, the single biggest influence might have been the ASCII character set - which had only one type of quote character.
      The order of characters in ASCII was designed to mimic one convention for typewriter and teletype keyboards for US-English, so that you would have to change only a single bit to get a shifted variation of a character. Then IBM changed their keyboard layout a little bit on their teletypes and typewriters, and that layout led to the US-ANSI standard which was picked up by other brands.
      ASCII's order of shifted keys on the numeric still remains in most European computer keyboard layouts.

      --
      "We mustn't be caught by surprise by our own advancing technology" -- Aldous Huxley
    6. Re: Twitter isn't helping by Anonymous+Brave+Guy · · Score: 2

      Curly quotes didn't exist on manual typewriters, and neither did the numbers zero (used an uppercase oh) or one (use a lowercase ell).

      Neither did many other useful typographic symbols, but that doesn't mean I want to read a book (or, say, a scientific paper) with notation constrained by what I could have typed on a clunky device from the 19th century.

      We got along fine without stupid smart quotes, and they add nothing to readability.

      Unless, for example, you're reading an article that actually does use quantities in degrees, minutes and seconds, or a mathematical paper where primes are used for distinction in a mathematical context. Then it's like saying you could still read and understand this paragraph if I substituted a colon for every full stop: no doubt it's true, but it would be slightly harder, particularly if I happened to also be using a colon correctly as well.

      There is definitely an element of typographical snobbery about things like proper use of quotation marks and dashes, and they certainly aren't the most important aspects of good typography, but that doesn't mean that the little incremental improvements you get from careful punctuation and the typography that goes with it aren't useful to some readers.

      --
      If you disagree, post your argument. (-1, Overrated) isn't your personal censorship tool for views you don't like.
  2. “Meet me later in the gymnasium. by hey! · · Score: 3, Funny

    Next to the dumbbells... You'll know me, I got a hat.”

    I guess not, then.

    --
    Post may contain irony: discontinue use if experiencing mood swings, nausea or elevated blood pressure.
  3. Hardest part of smart quotes by michael_cain · · Score: 2

    The hardest part for any software that converts from straight to curly to get right are contractions with a leading quote: 'twas, 'tis, '12, and so forth. Especially in fiction and attempts at vernacular.

  4. Re:Not just curly quotes by arth1 · · Score: 2

    Also, some countries use double chevron quotes instead of curlies. There's less confusion with those.

    Then there's the difference in whether punctuation goes inside the closing quote or outside it.

  5. Re:Good Riddance by KiloByte · · Score: 4, Insightful

    Aren't they the ones that randomly mutate into Â(TM)?

    Any site that breaks them also fails utterly for non-English text or for most symbols. No one sane would use a site that broken, right? Right?!?

    --
    The creatures outside looked from Alt-Right to Antifa; but already it was impossible to say which was which.
  6. Are you kidding? by kwerle · · Score: 4, Insightful

    First: who gives a flying...

    Second: my manual typewriter only had quotes in one direction. So, no, the internet didn't kill smart quotes.

    1. Re:Are you kidding? by g01d4 · · Score: 3, Insightful

      who gives a flying...

      People who really care about typography or the presentation of their content.

      my manual typewriter only had quotes in one direction

      Indeed. Though typical typewriters weren't intended to generate content for mass consumption. Back in the day personal computers were supposed to change that by enabling desktop publication. (Recall the Mac/PC is Not a Typewriter books by Robin Williams.) However as the media for consuming written content migrated from paper to screen, things got a lot more complicated and in some ways a step back is taken here and there. Eliminating curly braces might be one of those small steps back.

    2. Re:Are you kidding? by Oligonicella · · Score: 2

      People who really care about typography or the presentation of their content.

      Your opinion or preference does not constitute fact.

  7. Re:Good Riddance by bluefoxlucid · · Score: 2

    Yes, but it's hard to hack an ATM anyway. It happens once in a while, but they're generally secure, so this has not been a concern.

  8. Weird characters? by colinrichardday · · Score: 5, Insightful

    At Slashdot, we also avoid curly quotes -- and when we miss, you see them as weird characters on the site!

    I thought the weird characters on this site were the editors! :)

  9. Re:Good Riddance by lgw · · Score: 5, Insightful

    Curly quotes, like serif fonts, make text less fatiguing to read. Typesetting is a very mature science.

    We have the screen resolutions now to allow screen text to benefit from some of the optimization that is present in print (especially phones, where the pixel density it starting to get high enough to make real fonts work). Sadly, the web is infested with "designers", who only want the site to look trendy and care not a bit about the reader.

    --
    Socialism: a lie told by totalitarians and believed by fools.
  10. Smart quotes break technical content by MobyDisk · · Score: 5, Insightful

    One problem with smart quotes is that you can't enter source code, or anything machine-readable, into an editor that uses smart quotes. I am sure many of us here have pasted something from documentation into XML or source-code, only to have it fail because the compiler doesn't want them.

    1. Re:Smart quotes break technical content by Cinnamon+Beige · · Score: 4, Insightful

      Honestly the main problem with them is that they're not smart--most implementations are pretty buggy and annoying, and it's ultimately easier to turn the 'feature' off than have to grovel over any text of decent length in order to make sure all of them are right. They'll curl when they oughtn't, they'll not curl when they ought, and they'll go the wrong way, pretty much entirely at random. About the only decent way I can see of making any implementation of an automatic text adjuster so it's not mangling things is to make it so you have to flag things--so it doesn't just cheerfully go altering apostrophes and quote marks, but you have to do something extra (from using a hotkey combo to having it followed by a different character that flags it for the program) to get it to do so.

      I did use the latter technique a lot for making my life easier when I was taking scientific and technical notes on a computer--I used particular key combos as placeholders, so I could go back on a unicode-capable machine and insert the proper characters or alter the formatting, since I could type that pretty much as fast as the instructor went. As shorthands go, it worked very well for setting up for later adjustment for proper formatting.

    2. Re:Smart quotes break technical content by Reziac · · Score: 2

      I just had occasion to look into the reason why curly quotes often go the wrong way (and grow spurious spaces around themselves), and it's because of a quirk (or bug) in how RTF (and exported-from-RTF) handles nesting for formatting codes.

      Smart quotes depend on finding ON and OFF codes with a single block of formatting, but RTF likes to put paragraph breaks INSIDE the nearest adjacent paired formatting or on/off code. Which means the parser can't find the OFF code so it uses another ON code, and the user gets curly quotes pointing the wrong direction.

      Same thing with smart single quotes.

      Basically, it's bad tag nesting.

      Once I got to really examining all the various cases, it was clear it was all one problem that can be triggered by any change in formatting including line breaks, but may look different depending on what else is adjacent, especially when there also a code with multiple manifestations, like that for the M-dash (which has two possible codes, and behaves differently depending on whether there are trailing spaces).

      Every RTF editor and export-to-RTF I looked at had the same problem. So it's probably a failing of the RTF standard (such as that is... so many to choose from!) that sorta neglected to specify how code nesting must be handled.

      --
      ~REZ~ #43301. Who'd fake being me anyway?
  11. Re:Good Riddance by dinfinity · · Score: 5, Funny

    Come on, man. You could have at least tried to write “designers”.

  12. It's killed the question mark and the apostrophe. by newdsfornerds · · Score: 2

    And maybe they were dead long before the Internet and the Internet is just showing us how illiterate people really are.

    --
    Damping absorbs vibrations. Dampening is caused by moisture.
  13. Re:Good Riddance by msauve · · Score: 5, Informative

    Huh? They're in UTF-8 (U+201C=\xE2\x80\x9C and U+201D=\xE2\x80\x9D), as are all Unicode characters.

    --
    "National Security is the chief cause of national insecurity." - Celine's First Law
  14. Re:Good Riddance by AthanasiusKircher · · Score: 4, Insightful

    Yup. "Smart Quotes" or "Curly Quotes" were always a Typesetter's affectation, not universal, and not available in all historic Fonts. They add _nothing_ to legibility; they have no unique function. (Unlike say the m-dash and the n-dash... and nobody gives a damn about those distinctions either.)

    While I don't necessarily disagree, there are loads of typographical conventions that could be similarly declared a "typesetter's affectation," just like various irregularities in spelling or grammar could just be declared a "pedantic grammarian's affectation."

    There are conventions. Some of them are more useful than others. The convention regarding curly quotes is only really "useful" in a limited set of circumstances (mostly having to do with very tightly set text, where spaces are small enough that ambiguity about the direction of the quote can help parse the text).

    But to the headline's question -- NO, the internet did NOT "kill" curly quotes. Standard typewriters never had them, for example. They've always been something "extra" for typographers to add into published material.

    And in the grand scheme of things, I agree with you that there are much "bigger fish to fry" in terms of more meaningful typographical conventions that have fallen out of favor in the internet age, like your example of dash distinctions.

    Personally, I'd point to the problem of treating all spaces alike in HTML. Yes, you can insert non-breaking spaces, thin spaces, etc. if you want, but most people don't know how -- and the few that do don't tend to bother much. This is an actual legibility issue: for example, where line breaks occur is important. If they occur in certain places, it can create confusion for the reader. Sure -- most of the time it's just a fraction of a second where your eyes skip back and you figure out what's really going on, but in most of the cases the reader can be spared those minor issues with just a few insertions of places for proper line breaks (and places to avoid them).

    In general, the internet has basically killed a lot of typography, in the sense of detailed design and typesetting. Sure, it happens on some sites, but even those that seem to try hard often end up with stuff that looks like crap compared to print. (Example -- how many times have you seen drop caps that actually look right online? And yes, they can actually serve a purpose as they did in print -- they help readers quickly navigate around major sections. Without the page numbers of print, one could argue they can be MORE useful. And yes, there are other ways of doing it than drop caps -- my point is that even the sites that attempt to use them tend to look like abominations from a reasonable graphical design perspective that might include some nuance about pushing some drop caps out into the margin by a smidge or pulling in some lines subtly to flow around the letter or whatever.)

    I know many people here will argue that these things don't matter. Yeah, a lot of the nuances are mostly aesthetic. But is there a reason that text can't (or shouldn't?) be pretty as well as legible? Or should we all just use black Times New Roman text on a white background with default spacing and formatting everywhere?

  15. Re:Good Riddance by lgw · · Score: 3, Interesting

    Well played, sir, well played.

    But I actually didn't know /. supported those non-7-bit-ascii characters - that's new!

    --
    Socialism: a lie told by totalitarians and believed by fools.
  16. Re:Has Slashdot Killed Itself? by slashdice · · Score: 3, Funny

    it's like a dozen voices screamed out, and nothing of value was lost.

    --
    Copyright (c) 1990 - 2014 Dice. All rights reserved. Use of this comment is subject to certain Terms and Conditions.
  17. Re:It's killed the question mark and the apostroph by Anonymous Coward · · Score: 5, Funny

    Killed the apostrophe? Surely you cannot be serious!

    "I went to look at the car's over in the other lot's".
    "These are my favorite's!"
    "They're dogs are cute. It like's it's new vest SO much!"
    "He want's to go to the movie's with us."

    The apostrophe has found success beyond its wildest dreams (or perhaps I should say, "it's wildest dream's") since the general public discovered the internet. Never before was it held in such widespread esteem.

  18. Re:It's killed the question mark and the apostroph by iggymanz · · Score: 2

    the hyphen, dash and emdash seem to have taken a beating too.

  19. Re:Good Riddance by Luthair · · Score: 2

    Science implies it was studied, I think its more likely based on supposition and old wives tales much like 'sports medicine' was for a very long time.

  20. Has the Internet Killed Curly Quotes? by JustAnotherOldGuy · · Score: 2

    "Has the Internet Killed Curly Quotes?"

    Good god, let us hope so.

    Curly quotes are useless, they convey absolutely no useful information beyond what simple straight quotes do. They're the confetti of punctuation marks and should just die out along with buggy whips and mustache wax.

    --
    Just cruising through this digital world at 33 1/3 rpm...
    1. Re:Has the Internet Killed Curly Quotes? by GuB-42 · · Score: 2

      They do convey information. It makes the difference between " start quote " and " end quote ".
      Parenthesis, brackets, as well as French guillemets, CJK brackets and Spanish punctuation all differentiate between start and end.
      From a computer perspective, straight quotes just make parsing harder : you can't quote within a quote without escaping. It is even worse with single quotes being apostrophes. It results in unreadable mess like "Can't open file "'"'"$filename"'"' just because "Can't open file "$filename"" is ambiguous.

  21. This! Don't change my text without permission! by raymorris · · Score: 4, Insightful

    I don't give a darn about curly quotes - use them if you want, but it pisses me off when certain Windows and Mac software silently CHANGES my normal quotes to some curly bullshit. For technical stuff, SQL, command lines, or programming code, they are in no way interchangeable amd silently changing them can cause data to be messed up or even deleted. That's not okay.

    1. Re:This! Don't change my text without permission! by Jason+Levine · · Score: 2

      As a writer, it's also annoying when automatic curly quotes put the wrong quote in. For example (using curly braces instead of quotes since curly quotes wouldn't appear):

      {He walked to the store, { she said.

      There's two opening quotes there and the only way to spot it is to look closely. Not hard with one sentence, but try doing that in an entire 60,000+ word novel. (I have. It's not fun.)

      --
      My sci-fi novel, Ghost Thief, is now available from Amazon.com.
  22. Re:Good Riddance by NoImNotNineVolt · · Score: 2

    They're also in Windows-1252 (cp1252) as 0x93 and 0x94, which are control codes in utf-8. However, many web sites using this encoding claim (falsely) that they're utf-8, which causes these characters to fail to render properly. The blame can be shared between Microsoft (for having their own idiotic encoding) and web developers (who don't understand the concept of character encoding at all).

    --
    Chuuch. Preach. Tabernacle.
  23. Why not use HTML tags? by gregraven · · Score: 3, Insightful

    Why not use HTML tags? Then if you wish, you can style them in CSS if you wish, to appear as curly quotes.

    --
    Greg Raven
    As long as there's any left, I'll take mine first.
  24. Curly quotes are the devil by nwaack · · Score: 2

    As someone whose job requires them to move between multiple systems with multiple font formatting (or lack thereof) I absolutely despise curly quotes. They make simple two second copy-paste jobs into five minute find-the-busted-character goose chases. For normal everyday usage, please just let them die already.

  25. Goddammit, 2016! by wonkey_monkey · · Score: 2

    Has the Internet Killed Curly Quotes?

    Fuck 2016. You've killed Bowie, Rickman, Fisher... and now you've killed my favourite Vaudeville act of the 1920s.

    RIP Curly.

    --
    systemd is Roko's Basilisk.
  26. Re:Good Riddance by Anonymous+Brave+Guy · · Score: 2

    Actually, it is a character set, or really, a set of character sets (including ANSI/ASCII character sets).

    No, it isn't. The GP was right.

    This discussion is becoming surreal: I'm reading typographical advice from people who apparently don't know the difference between a hyphen and a dash, advice on character sets from people who apparently don't know the difference between Unicode and UTF-8, and advice on the difficulties of programming in the 21st century from people who apparently write their code in a word processor and then copy and paste it into an IDE that can't handle Unicode. It's a good job I only come here for the laughs these days. :-)

    --
    If you disagree, post your argument. (-1, Overrated) isn't your personal censorship tool for views you don't like.