-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 2012-01-31 15:41, Martin Peach wrote: > On 2012-01-31 03:41, IOhannes m zmoelnig wrote: >> -----BEGIN PGP SIGNED MESSAGE----- >> Hash: SHA1 >> >> On 2012-01-31 00:52, Hans-Christoph Steiner wrote: >>> That does make more sense, so something like [bytes2utf8], etc. >> >> utf8 is always a list of bytes. >> if you get values>255 than it is not utf-8; do you mean unicode points? > > The same idea could be used for unicode, converting pairs of bytes into > single numbers, taking care of endianness.
yes, something like [1] which does it the other way round (and doesn't care about endianness) and btw, isn't utf-8 agnostic of byte-endianness? at least [2] suggests this. mfgasdr IOhannes [1] https://pure-data.svn.sourceforge.net/svnroot/pure-data/trunk/externals/iem/unicode/utf82codenumber.pd [2] http://en.wikipedia.org/wiki/Byte_order_mark#UTF-8 -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.11 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk8oBjgACgkQkX2Xpv6ydvR0yQCgt9xhKaqpGqaiH830SDuW6YIH b+kAn3dDS5UjYBINE2OZkIhhSlHE65d8 =EkZE -----END PGP SIGNATURE-----
smime.p7s
Description: S/MIME Cryptographic Signature
_______________________________________________ Pd-dev mailing list [email protected] http://lists.puredata.info/listinfo/pd-dev
