-
Notifications
You must be signed in to change notification settings - Fork 5
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Feature] Unicode characters in text file [sf#3] #47
Comments
Commented by andrewpunch on 2004-06-10 10:50 UTC Another quick possibility is to use UTF-32 (little endian) The technical specification is here: |
Commented by andrewpunch on 2004-10-11 06:43 UTC Detirmination: ASCII, UTF16/32 and other mappings will be available as |
Updated by andrewpunch on 2004-10-11 06:43 UTC
|
Updated by andrewpunch on 2004-10-11 06:45 UTC
|
Commented by andrewpunch on 2005-04-11 12:41 UTC This is scheduled for inclusion in 3.2.0 as UTF8 output for |
Reported by andrewpunch on 2004-06-09 03:25 UTC
Characters which are non-ASCII are thrown away when
writing to a text file.
There is no way around this while we write to an ASCII
file.
There are some other options for file formats:
From a design perspective this could be achieved by
creating maps from a single unicode character to one or
more bytes.
There could be a map for:
The map need not be static. It may be dynamic. For
example the ASCII map may allow through all character
codes with a unicode value less than 0x0080.
There must be a process for when a unicode character is
not mappable using the current map.
Created on behalf of David at Nutmeg.
The text was updated successfully, but these errors were encountered: