Alan Manuel Gloria: > Guile 1.6 and 1.8 don't support Unicode out-of-box AFAIK. On 2.0 the > encoding is done on a per-port basis using set-port-encoding!
Sure, but we can do *some* stuff without it. I've commented out the parts you can't. > On 2.0 there is also a file-encoding function that tries to autodetect > the file encoding somehow. But that won't be everywhere. In any case, it wasn't hard to make it more general, and it should work just fine with Guile's auto-detection. > I think that Unicode support is sufficiently non-universal that > next-line and line-separator should probably go into the portability layer. Next-line isn't really a Unicode thing. That's the EOL marker for IBM systems, and it's < 128. Since it's easy to support, and officially required by R6RS, I included it. > For Scheme's that don't support Unicode out-of-box, define > those to be #f; if the Scheme supports Unicode, then preferentially > use (integer->char) as much as possible. This should also allow us to > support Unicode on Guile 2.0 and disable that support in Guile > 1.8/1.6, where character encodings are even bigger headaches and would > badly complicate the code if we forced the decoding. Reasonable enough. In any case, I've pushed a version that can read form-feed and friends. Tell me how it works for you! --- David A. Wheeler ------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ _______________________________________________ Readable-discuss mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/readable-discuss
