-
Hello,
I am interested in using Fork for my version control needs, and I am considering purchasing a license. However, I have a specific requirement that is crucial for my workflow: support for UTF…
-
When calling `jsonFromData` with an array of UTF-16-encoded bytes, Jay throws `unimplemented`.
The RFC recommends to determine the encoding by looking at the initial bytes (section 3).
I don't real…
remko updated
8 years ago
-
No DBMS_SQLSERVE estava aparecendo o erro quando no SQL da DAO tinha algum caráter especial !
Esse problema está relacionado #28
-
facebook return the comments and reply messages in UTF-16, but the package seems encoding in UTF-8, this cause problems for emoji display
-
Currently, we can display UTF-16 characters, but you can't really edit them. Look at this screenshot:
### Morphic
* `StringMorph` `TextMorph` `CursorMorph` need to be UTF-16+-aware.
* Uses of…
-
Can you please add support for UTF-16?
-
Hi, is it possible to Output Windows Unicode instead of UTF8.
In Branch 0.5 I could use
IfcParse::IfcCharacterDecoder::DEFAULT
But 0.6 don't have Default anymore.
Thanks,
and kind Regards,…
-
**Describe the bug**
The source code I need to analyze contains UTF-16 encoded source files (mixed with ASCII encoded files) and semgrep does not detect patterns in them.
**To Reproduce**
Creat…
-
String support in stdlib is currently limited to ASCII, @wclodius2 brought up the issue of supporting UTF-8, UTF-16 and UTF-32 as well:
> FWIW for a "string type" to supplant the intrinsic `charact…
-
UTF-16 support -- support for surrogates -- is crucial for "modern" texts like Emoji and other new charcters. Microsoft Windows has supported UTF-16 since 2000. The Cairo backend currently used can to…