-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 11-12-13 01:26 AM, Robert Collins wrote: > We could say 'utf8' and leave it at that. Or we could say 'the > printable subset of ascii' or some such. I'd just say non > whitespace utf8, as strings are easier to deal with, and avoiding > whitespace avoids most likely encoding issues.
If we're using Unicode identifiers, do we need to specify a normalization form (NFC or NFD), or would we impose that on the data after receiving it? Aaron -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.11 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk7nYOIACgkQ0F+nu1YWqI35RwCghOAMri5/6IBlXv1gjqDAelWI 9vsAn2Ka0zVUHLjB9MHWWvcwnnMNjBrJ =KCY3 -----END PGP SIGNATURE----- _______________________________________________ Mailing list: https://launchpad.net/~launchpad-dev Post to : launchpad-dev@lists.launchpad.net Unsubscribe : https://launchpad.net/~launchpad-dev More help : https://help.launchpad.net/ListHelp
