Would love to see Windows support codepage 65001 (UTF-8). Then all existing Windows 8-bit character APIs would magically support UTF-8, instead of this horrible old UTF-16 encoding.
-
-
Yeah, that part definitely isn't fun, but it's a small fraction of the code that uses FStrings, improving >99% of the usage by defaulting to UTF-8 at the expense of the Windows/Xbox platform layers would be nice.
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
I can see why changing internal encoding should wait until an appropriate time to make a breaking change (ue++). Passing a utf8 string to a utf16 API because a customer merged the latest is dangerous. You are wrapping win32 calls in a portability layer though, this limits ugly.
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
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.
