-
**Describe the bug**
A clear and concise description of what the bug is.
**To Reproduce**
Steps to reproduce the behavior:
1. Write title or Description using Korean
4. See error word
**Expe…
-
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…
-
Currently there are UTF-8 and UTF-16 encoder/decoder methods. These work by converting to and from `Rune` (UTF-32). While it's possible to do this through a round-trip, such as UTF-8 → UTF-32 → UTF-16…
-
I was intrigued by this in documentation re UnbufferedCharStream:
> Do not buffer up the entire char stream. It does keep a small buffer for efficiency and also buffers while a mark exists (set by …
-
YAML 1.2 requires UTF-16 and UTF-32 support. Currently, only UTF-8 is processed.
-
### Odoo Version
- [ ] 15.0
- [X] 16.0
- [ ] 17.0
- [ ] Other (specify)
### Steps to Reproduce
I was Following this tutorial: https://www.youtube.com/watch?v=2_Yu_hX85NY&list=PLFSlYEuka9lvpCEFgciH4…
-
If a yaml file has unicode characters like:
`
a: 🛑
`
go-yaml manages to decode this fine (if we print the yaml.Nodes value) however when marshalling the document out it prints out the escaped …
-
Hi, UTF-16 surrogate pairs are incorrectly decoded:
```haskell
λ> Json.decode $ Bytes.fromByteString "\"\\ud800\\udc00\""
Right (String "\65533\65533")
-- should be
λ> Aeson.decode "\"\\ud800\\ud…
-
Self explanatory. Most JS string compression tools require UTF-16 for the output files.
https://pieroxy.net/blog/pages/lz-string/index.html
https://github.com/pieroxy/lz-string
...
They can no…
-
Currently an XML document with `` will throw `Encoding utf-16 not supported`. Would be nice to have official support.