|
|
“Character Sets "Oops"” |
|||
| From: | Seth Dillingham | In Response To: | 5474 Character Sets and Conversant (and the Eudora Problem) |
| Date Posted: | Friday, April 21, 2006 9:00:01 AM | Replies: | 0 |
| Enclosures: | None. | ||
After my last post about switching to UTF-8 for all of our content in Conversant, people wrote to say that my XML feed had problems since we made the change.
Heh. That's ironic.
Anyway, some wrote to me privately, as if a bug is something I'd be embarrassed about. "Oh no! A bug in the software! Say it isn't so!" All this time I thought my software was bug-free, like everybody else's. (What matters is how we deal with them. They're inevitable.)
Well, now the bug should be fixed. All "above ascii" text in the XML output was being automatically converted to numerical entities (like &234;), but that's no longer necessary when the output is UTF-8.
In other words, my “curly quotes” — and long dashes — should all look fine now. Feel free to give me a shout if something looks wrong, though.
There are no trackbacks.
|
TruerWords
is Seth Dillingham's personal web site. From now on, ending a sentence with a preposition is something up with which I will not put. - WC |