On encodings: Americans: "I don't want to know"; Japanese: "How can you not know?!"; Europeans: "Unicode solves everything"
I really like Ruby's solution to the problem (I worked on Rails encodings around this tweet)
-
-
I think emojis will not cause American programmers to care any more ;) Nor do I think emoji idents are a good feature;)
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
interested in deets (good link?)
-
the TLDR is that strings have a tagged encoding. Binary is an encoding. Incompatible encodings produce errors.pic.twitter.com/A5V4Ghm4UC
-
the default encoding is picked up from the locale, but Rails sets it to UTF-8, which impacts File IO.
-
All operations allow you to optionally specify an encoding.
-
The legacy C string APIs create BINARY strings, but the new APIs have an encoding parameter.
-
there is a configuration called "default internal encoding", which Rails sets to UTF-8. Libraries trancode to that 1/
-
after tagging the original string with the right encoding. 2/2
- 6 more replies
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.