Unicode support in Django and Feedjack

(ǝʇısqǝʍ dılɟ ǝpoɔıun ǝɥʇ ɟo dlǝɥ ǝɥʇ ɥʇıʍ ǝlqıssod uǝǝq sɐɥ ʇsod sıɥʇ)

˙ʇı ɥʇıʍ sɯǝlqoɹd ǝʌɐɥ noʎ ɟı ʍouʞ ǝɯ ʇǝl ˙ǝʇıs oƃuɐɾp ǝɥʇ uı ʇsılʞɔǝɥɔ ƃuıʇɹod ǝɥʇ ɥʇıʍ ʎsɐǝ ʎɹǝʌ sɐʍ ʇı ˙ʇı ʇɹoddns oʇ ǝƃuɐɥɔ ǝlqıʇɐdɯoɔuı spɹɐʍʞɔɐq ʇsɹıɟ (ʞuıɥʇ ı) ǝɥʇ ƃuıʇıɯɯoɔ ɯɐ ı os ‘ʞɔɐɾpǝǝɟ ɟo uoısɹǝʌ ʇsǝʇɐl ǝɥʇ ǝʞoɹq ǝpɐɹƃdn sıɥʇ

˙(ʇıɯɯoɔ ʇɐɥʇ ɟo ǝzıs ǝɥʇ ʇɐ ʞool ʇsnɾ) ɥɔuɐɹq sıɥʇ uı ʞɹoʍ ƃuızɐɯɐ sıɥ ɹoɟ ʞɔıuuıpǝɹʇ ɯloɔlɐɯ oʇ sopnʞ ˙ʇɹoddns ǝpoɔıun ʇɐǝɹƃ sɐɥ ‘sǝƃɐnƃuɐl ɹǝɥʇo ǝʞılun ‘uoɥʇʎd ǝsnɐɔǝq ǝlqıssod ƃuıɥʇǝɯos ‘ǝɹɐʍɐ ǝpoɔıun ʎlʇǝldɯoɔ ʇoƃ oƃuɐɾp oƃɐ sʎɐp ǝɯos

Some days ago Django got completly Unicode aware, something possible because Python, unlike other languages, has great Unicode support. Kudos to Malcolm Tredinnick for his amazing work in this branch (just look at the size of that commit).

This upgrade broke the latest version of Feedjack, so I am commiting the (I think) first backwards incompatible change to support it. It was very easy with the Porting Checklist in the Django site. Let me know if you have problems with it.

(this post has been possible with the help of the Unicode Flip website)

8 Responses to “Unicode support in Django and Feedjack”

  1. Anonymous Says:

    You know, trying to read this thing backwards and upside down is stupid. I won’t be coming here if the feed isn’t something I can read next time.

  2. tabo Says:

    @Anon:

    That is why I included the “normal” text in the post. This was just a unicode-related joke, which I think was in topic with the subject of the post.

  3. ich Says:

    tu pagina es invalida, mierda?
    W3C QA Markup Validation Service
    v0.7.4

    * Skip Navigation | Home
    * About…
    * News
    * Docs
    * Help & FAQ
    * Feedback

    Jump To:

    * Results

    Result: Failed validation, 3 errors
    Address: http://tabo.aurealsys.com/archives/2007/07/09/unicode-support-in-django-and-feedjack/
    Encoding: utf-8
    Doctype: XHTML 1.1
    Root Namespace: http://www.w3.org/1999/xhtml
    Revalidate With Options
    : Show Source Show Outline
    Validate error pages Verbose Output

    Help on the options is available.

    Note: The Validator XML support has some limitations.
    This page is not Valid XHTML 1.1!

    Below are the results of checking this document for XML well-formedness and validity.

    1. Error Line 8 column 11: there is no attribute “name”.

    You have used the attribute named above in your document, but the document type you are using does not support that attribute for this element. This error is often caused by incorrect use of the “Strict” document type with a document that uses frames (e.g. you must use the “Transitional” document type to get the “target” attribute), or by using vendor proprietary extensions such as “marginheight” (this is usually fixed by using CSS to achieve the desired effect instead).

    This error may also result if the element itself is not supported in the document type you are using, as an undefined element will have no supported attributes; in this case, see the element-undefined error message for further information.

    How to fix: check the spelling and case of the element and attribute, (Remember XHTML is all lower-case) and/or check that they are both allowed in the chosen document type, and/or use CSS instead of this attribute. If you received this error when using the element to incorporate flash media in a Web page, see the FAQ item on valid flash.


    2. Error Line 8 column 31: there is no attribute “content”.


    3. Error Line 8 column 79: element “META” undefined.

    …c1g/wC50EoGYO/SC8r/8yHyhdOaUTmd52I=” />

    You have used the element named above in your document, but the document type you are using does not define an element of that name. This error is often caused by:
    * incorrect use of the “Strict” document type with a document that uses frames (e.g. you must use the “Frameset” document type to get the “” element),
    * by using vendor proprietary extensions such as “” or “” (this is usually fixed by using CSS to achieve the desired effect instead).
    * by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case

  4. karim Says:

    tabo: it was a funny and very “à propos” joke :) and thanks for the good work

  5. Jj Says:

    Chevere!, salvo que Chichaplanet aun no es unicode-aware :-P

  6. tabo Says:

    ich:

    Fixed, it was a META (in caps) from google webmaster central.

  7. Alisha (aka Lishux) Says:

    Hi tabo! I’m sure you remember me - (hint: airc).
    This is the first time I have seen the Unicode Flip website - thanks for sharing, it’s something I’ll have to read more about.

    Unlike the anonymous person, it was funny trying to read it!

  8. macdet Says:

    http://mobbing-gegner.de/planet/tag/brandst%C3%A4tter/ que passa, que occurre?

    busco una solucion :(

    gracias

Leave a Reply