I18n in digestible chunks
The W3C draft on Authoring Techniques for XHTML & HTML Internationalization 1.0, while chock-full of good advice on living and writing in a world with more than 26 letters, wasn’t much more digestible than its title. Now the I18N WG is splitting the material up, starting with:
While I can’t imagine myself needing to handle bidirectional text, there’s enough good useful advice in the first two that I’m putting the third on my list to read anyway. Having just learned the other day that you have to use utf-8 rather than iso-8859-1 on pages with forms, even if everything’s going to be in English, to reliably get things like curly quotes passed through in the encoding you expect, I won’t be too surprised to find something equally useful about bidi.
(Aside: wondering why anyone cares about whether the content model for RSS’s title element is text or HTML, or why anyone would want HTML in their titles? I’d really like to have put an acronym element around I18N in the title, but because RSS doesn’t admit which it is, every reader would barf in a different way.)
Internationalization
Say you want to tag some text on a web page as being in a language other than the main…
Na(t)ive speakers hardly ever get it
Phil Ringnalda wijst naar de sinds 9 mei in hapklare brokken opgedeelde W3C-richtlijnen voor het gebruik van tekens en coderingen, het aanduiden van de taal van tekstmateriaal en hoe om te gaan met bidirectionele tekst. Het kan, als je ook een sporadis…
I18n in digestible chunks
phil ringnalda dot com: I18n in digestible chunks ”The W3C draft on Authoring Techniques for XHTML & HTML Internationalization 1.0, while chock-full of good advice on living and writing in a world with more than 26 letters, wasn’t much more…