[SG16-Unicode] P1689: Encoding of filenames for interchange
Lyberta
lyberta at lyberta.net
Fri Sep 6 15:28:00 CEST 2019
> My reading of their paper was that they want to encode non-UTF8
> sequences into UTF8 paths in a JSON file. I don't think they should take
> that path, because it loses too much information.
What if non-UTF8 part will be stored in the same way HTML encodings do?
So we would have UTF-8 string as the name of encoding such as "WTF-16"
for NTFS and array of numbers that are "abstract units of text" (code
units for UTF, characters for US-ASCII, not sure about other encodings).
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: OpenPGP digital signature
Url : http://www.open-std.org/pipermail/unicode/attachments/20190906/f102ed52/attachment.bin
More information about the Unicode
mailing list