Conversation

Notices

1. 𝘾𝙔𝘽𝙀𝙍𝙁𝙍𝙄𝙀𝙉𝘿 (ninjawedding@sdfn-01.ninjawedding.org)'s status on Monday, 17-Jul-2017 02:01:53 UTC 𝘾𝙔𝘽𝙀𝙍𝙁𝙍𝙄𝙀𝙉𝘿
   "IBM comment on preparing for a
   Trigraph-adverse future in C++17", in which a justification for trigraphs for EBCDIC(!) compatibility is made:
   
   http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2014/n4210.pdf
   
   This is a great reminder that somewhere, someone is dealing with an older software legacy than you.
   • Hallå Kitteh likes this.
   • Hallå Kitteh repeated this.
   • Hallå Kitteh (clacke@social.heldscal.la)'s status on Monday, 17-Jul-2017 02:08:21 UTC Hallå Kitteh

     in reply to
     @ninjawedding The fact that somebody even thought to define http://en.qrwp.org/UTF-EBCDIC is my go-to example for this. :-)
   • Hallå Kitteh (clacke@social.heldscal.la)'s status on Monday, 17-Jul-2017 02:13:54 UTC Hallå Kitteh
     @ninjawedding That's not the only freaky thing about Oracle charsets:
     
     > "The Oracle database uses CESU-8 for its "UTF8" character set. Standard UTF-8 can be obtained using the character set "AL32UTF8" (since Oracle version 9.0)."
     
     http://en.qrwp.org/CESU-8
     
     CESU-8 is UTF-8-with-surrogate-pairs.
   • Hallå Kitteh (clacke@social.heldscal.la)'s status on Monday, 17-Jul-2017 02:25:57 UTC Hallå Kitteh
     @ninjawedding I wouldn't know. I have not been directly exposed to Oracle APIs. But I assume that anyone post-9.0 who cares about things uses AL32UTF8.
     
     At least this beats the old broken UTF-8 type in MySQL that couldn't even go outside the BMP.
     
     https://dev.mysql.com/doc/refman/5.5/en/charset-unicode-utf8mb4.html is the name for actual UTF-8 there.