Slashdot Mirror

← Back to Stories (view on slashdot.org)

Judge In Pirate Bay Trial Biased

Posted by CmdrTaco on from the aren't-we-all dept.

maglo writes "The judge who handed down the harsh sentence to the four accused in the The Pirate Bay trial was biased, writes Sveriges Radio (Sweden Public Radio): sr.se (swedish). Google translation. The judge is member of two copyright lobby organizations, something he shares with several of the prosecutor attorneys (Monique Wadsted, Henrik Pontén and Peter Danowsky). The organizations in question are Svenska Föreningen för Upphovsrätt (SFU) and Svenska föreningen för industriellt rättsskydd (SFIR)."

5 of 415 comments (clear)

  1. Re:English Language Article. by TheThiefMaster · · Score: 0, Offtopic

    And in other news, Slashdot still fails at UTF8.

    It's not just slashdot, it's also the fact that HTML/HTTP provides no way to know what charset a form was submitted in. Some browsers append a charset to the content-type http header they send, but most try to send in the same charset as the page, or utf-8 if that's not possible, but don't tell the server which...

    I.E. is even better, as it ignores the charset the server sends in its HTTP content-type header and tries to guess instead, unless you put a content-type meta tag in the page.

  2. Re:English Language Article. by Yetihehe · · Score: 0, Offtopic

    Poraka (should be porazka with dot over z, but doesn't really work)

    --
    Extreme Programming - Redundant Array of Inexpensive Developers
  3. Re:English Language Article. by Yetihehe · · Score: 0, Offtopic

    Have you checked content-type meta tag of any slashdot page? Hint: it isn't utf.

    --
    Extreme Programming - Redundant Array of Inexpensive Developers
  4. Re:English Language Article. by Z00L00K · · Score: 0, Offtopic

    Only way around it seems to be to use HTML entities like Å for Å and so on.

    --
    If builders built buildings the way programmers wrote programs, then the first woodpecker would destroy civilization.
  5. Re:English Language Article. by TheThiefMaster · · Score: 0, Offtopic

    I never said it was.
    I said browsers submit forms (e.g. the comment form) in either the page's charset or in utf-8 if that isn't possible, but don't tell the server which. Which implies that the page's charset isn't already utf-8.

    It's possible that the server is safely storing and handling utf-8 data, and it is just the charset being sent by the server in the content-type header which is causing the BROWSER to screw up the rendering. I'll check.