| ||
Sat 2024-12-21
Fri 2024-12-20
Thu 2024-12-19
Wed 2024-12-18
hydroxychloroquine fraud withdrawn Tue 2024-12-17
Sun 2024-12-15
Sat 2024-12-14
Fri 2024-12-13
Thu 2024-12-12
Tue 2024-12-10
Search
Archives
2023
12 11 10 09 08 07 06 05 04 03 02 01
2022
2021
2020
2019
2018
2017
2016
2015
2014
2013
2012
2011
2010
2009
2008
2007
2006
2005
2004
2003
One good site
MDN
Nelson Minar
Blog licensed under a Creative Commons License
|
I had a lively discussion with
Cory
about using typographic quotes in reaction to
Rael's post about a
SmartyPants plugin for Blosxom.
I want to use fancy Unicode characters like U+201C and U+201D
(“smart quotes”) in my blog. Cory hates that idea because
non-ASCII characters behave badly when you paste them into your email
or text editor and that they don't work well in RSS.
The underlying problem is an impedence mismatch between new Unicode oriented tech like the Web and XML and old ASCII oriented tech like email and text editors. Browsers and RSS readers should mediate between the two but software often gets it wrong. For instance on a cut and paste MSIE translates U+201C into the byte 0x93, which I guess means something in some proprietary Microsoft encoding but is not valid ASCII. If it just turned it into a proper ASCII 0x22 quote life would be so much better. So because of buggy software we're left with poor typography. This may all seem a bit pedantic for a design nicety, but handling non-ASCII correctly really matters if you write in almost any language other than English. Unicode and UTF-8 really are the right things. The ironic thing is that in this blog's preferred font (Arial 12pt) smart quotes don't really look any better than normal quotes. So for now I can ignore the whole issue. |
|
