Developing with web standards, refreshed

Developing with web standards, my (long) article on web standards and accessibility, turned out to be more popular than I could ever imagine, with links to it showing up in places like A Roadmap to Standards, Web Standards Link Bonanza, CSS Vault Resources, and webgraphics.

Based on feedback from readers, I’ve made some updates to the article, corrected some mistakes, and rephrased a few paragraphs that were potentially misleading or confusing, particularly with regards to XHTML versus HTML, MIME types and character encoding. If you read it and find more mistakes, errors, or confusing passages, please tell me so I can correct whatever is wrong.

There is now a Finnish translation (by Yoji Hirabayashi, Mikko Kekki and Pekka Peltonen). A French translation, by Clément Hardouïn, was recently completed, and is available at CYBERcodeur.net.

That makes the article available in English, Finnish, French, and Swedish. More translations are in the works. Let me know if you’d like to translate it to another language.

Posted on August 11, 2004 in Web Standards

Comments

  1. Is anyone doing a Spanish translation?

    I’ve tried using the contact form but the page has an error.

  2. August 12, 2004 by kazu

    How about Japanese version? If anyone hasn’t translated the article, I wanna do that.

  3. August 12, 2004 by Roger (Author comment)

    Hermann: Yes, someone is working on a Spanish version. I’ll check with that person to see how it’s coming along. The contact form works now. I had somehow neglected to encode an ampersand in a URL. Bleh. Kazu: No Japanese version is in the works, so start working on it ;)

  4. August 12, 2004 by kazu

    Thanks Roger. Well, I’ll send you the Japanese ver. in 1 week or so.

  5. You should really start using UTF-8 now, with a Japanese version coming up ;-). And using some content negotiation wouldn’t hurt as well, or are you already doing that?

  6. August 12, 2004 by Roger (Author comment)

    Anne: Hehe. Yeah, I guess I’ll have to go to UTF-8. Giving it another try as soon as I have time. I’m already (since some time in June I think) using content negotiation where it’s possible/safe, i.e. on all pages that do not have Google ads or comments.

  7. I meant for the different languages on that article.

  8. August 12, 2004 by Roger (Author comment)

    Do you mean serving the language version preferred by the requesting browser?

  9. Exactly, that is called content negotiation as well ;-)

  10. Is there a Dutch version in the making? Or do I have the honour to do it?

  11. August 12, 2004 by Roger (Author comment)

    Anne: Right. I guess I could, but I’m not so sure it’s a good idea. That’s just my personal opinion, of course, but I don’t like it when I’m redirected that way. Google for example insists on sending me to google.se and show everything in Swedish just because I’m located in Sweden, even though I want the English version. Fabian: nobody has offered to do a Dutch version yet, so go ahead! A note about translations. I only speak Swedish and English fluently, so I can’t judge the quality of translations to other languages. A good idea is to get someone to help you proofread :)

  12. Roger, that probably has to do with your personal preferences. You don’t have to get the Swedish version of Google, you get it because that is the way you prefer it to get. At least, your browser is configured that way. (I like to get the Dutch Google for example, since it allows me to search both in English and Dutch content; the results are slightly differenct from google.com though.)

Comments are disabled for this post (read why), but if you have spotted an error or have additional info that you think should be in this post, feel free to contact me.