Conversation

Notices

1. DEATH TO GASTONS DESU~ (roka@pl.smuglo.li)'s status on Monday, 30-Mar-2020 14:35:30 JST DEATH TO GASTONS DESU~

   • DEATH TO GASTONS DESU~
   Daily reminder that Unicode is bloat and ISO 8859-2 is inappropriate for Polish despite being standard due to inappropriate punctuation glyphs available. ASCII quotations are not permissible. Thankfully the Baltic encoding has full Polish coverage.
   1585546350.png
   • DEATH TO GASTONS DESU~ (roka@pl.smuglo.li)'s status on Monday, 30-Mar-2020 14:39:25 JST DEATH TO GASTONS DESU~
     @tuxcrafting here's byte-length of my work e-mail from last week, it is a bit on the short side. One file is encoded as UTF-8, the other as ISO 8859-13. See what I mean? :rokalife:
     1585546648.png
   • DEATH TO GASTONS DESU~ (roka@pl.smuglo.li)'s status on Monday, 30-Mar-2020 14:39:45 JST DEATH TO GASTONS DESU~
     @amerika @tuxcrafting like forth
   • DEATH TO GASTONS DESU~ (roka@pl.smuglo.li)'s status on Monday, 30-Mar-2020 14:42:03 JST DEATH TO GASTONS DESU~
     @amerika @tuxcrafting that is acceptable if you also accept ALGOL 60.
   • DEATH TO GASTONS DESU~ (roka@pl.smuglo.li)'s status on Monday, 30-Mar-2020 14:43:04 JST DEATH TO GASTONS DESU~
     @amerika @tuxcrafting fine.
   • DEATH TO GASTONS DESU~ (roka@pl.smuglo.li)'s status on Monday, 30-Mar-2020 15:02:45 JST DEATH TO GASTONS DESU~
     @tuxcrafting UTF-8 is US-ASCII with extra latches for switching to multibyte mode. There is no benefit to using it if you're either:

     1. writing a text in English only (but then why the fuck would you not declare it as ASCII in the first place?!)
     2. not mixing characters or glyphs from a different 8bit single-byte encoding

     . For a document or e-mail written purely in, say, Polish, using Unicode is just harmful. A proper declaration of a charset is sufficient and certainly more elegant a solution than fucking Unicode :rokalife: