Δαφνη Ευτυχια Αρθουρος

In response to moominmuppet's reacting to a "Tattoos done while you wait!" sign with, "Um... There's another option?", calebbullen wrote:

If you've a prosthetic there is. Personally, I'd just send it in but I'm lazy.

Actually, if one were going to get something really intricate like one of those tattoos with the special nanotech in[k] that reads your mood and changes the picture accordingly, then you might want to go for the amputation and re-attachment plan. That's what I did. It was weird spending the weekend without a torso but totally worth it. Not only for the tattoo but also for the experience. The tatoo itself is actually kind of embarrasing. It shows the face of whomever I'm currently lusting over. Which is fine when it's someone you know or like but when you get that freaky mood where you think, "I bet Nancy Reagan likes it really rough". Well... people look at you weird. Of course they might just be surprised about a man walking around with no shirt on in January.

Not feeling very talkative today. Took me a while to recognize what I was feeling as early warning signs of another migraine and medicate myself against it -- hoping it works that way. (One thing I liked about Midrin is that it seemed to provide a few days of protection in addition to taking care of the migraine I took it for. AC&C doesn't do that, but it's what I've got. OTOH, it also doesn't give me that frustrating, dopey "drugged feeling" that Midrin does.) Anyhow, in addition to an "I'm alive" ping, I felt like tossing out a thought to get other folks' perspectives on...

What do y'all think about using proper typographic non-ASCII punctuation in LiveJournal entries or on other web pages? I'm thinking mostly about the correct uses of hyphens, en-dashes, and em-dashes instead of just using an ASCII dash ('-'/45/0x2D) for both the first two, and a pair ("--") in place of the em-dash ("—"), but this would also apply to opening and closing quotation marks (“ ”) instead of the symmetrical ASCII quote ('"'/34/0x22), and so on.

On the one hand, it's not a Big Deal, people are used to reading typewriter/email conventions on computer screens and know what is meant, and coding the right codes as though typesetting instead of merely typing is more effort for little gain

On the other hand, with Unicode and HTML &-codes we are no longer limited to only those characters that could've been produced on a manual typewriter and displayed on an ADM3a or VT52 computer terminal. We do not have to make do with the same conventions on the web as make sense in email, and we can make our sites and our blogs look more professional, more like books and magazines, by going back to the typographical conventions that predate the typewriter and putting the nuances of punctuation into how we type what we write for the web.

On the gripping hand¹, those non-ASCII characters can be a pain in the arse when using copy-and-paste, especially when one wishes to paste text into some place where the full range of Unicode characters isn't supported or if one's operating system pastes its own special Extended-ASCII code or the Unicode value where an HTML &#; code is what is actually needed. (For example: although the Telnet client I usually use seems to be able to deal with a certain amount of Unicode, the vim editor displays numeric codes for non-ASCII characters, and if I fail to notice such characters when pasting text into email, at least one friend's mail server will reject the message. I also have to clean up non-ASCII characters when posting quoted text here in my journal.)

So ... pointless affectation, useful or aesthetically appealing liberation from the typewriter mindset, or annoying menace? I do not expect consensus, but I'm interested in how people feel about this and what they can tell me about why they feel the way they do. (Obviously, using Unicode characters so as to be able to correctly spell names and other words from languages that have letters (or accents) that English does not would be a different question -- the existence of Unicode is a Good Thing; I'm specifically asking about the use of it for punctuation that can be approximated in ASCII.)

And now to see what the second paragraph of this entry looks like in Lynx.

ETA: Lynx translated the opening and closing quotation marks to ASCII quotes and translated the em-dash to a pair of ASCII dashes. A similar browser, Links, handled the quotation marks the same way but translated the em-dash to a single ASCII dash. And I just realized this should've been a start-of-the-workday entry since I want lots of people to comment, but I'm not feeling sufficiently motivated to delete it and hand it to the 'at' daemon for reposting eleven hourse hence, now that I've already posted it.