bug#26059: Sorry about the duplicate.

2017-03-13 Thread Andy Wingo
On Sat 11 Mar 2017 19:30, taylanbayi...@gmail.com (Taylan Ulrich "Bayırlı/Kammer") writes: > Please ignore this, as it's a duplicate of #26058.

bug#26058: utf16->string and utf32->string don't conform to R6RS

2017-03-13 Thread Andy Wingo
On Sat 11 Mar 2017 13:19, taylanbayi...@gmail.com ("Taylan Ulrich "Bayırlı/Kammer"") writes: > See the R6RS Libraries document page 10. The differences: > > - R6RS supports reading a BOM. > > - R6RS mandates an endianness argument to specify the behavior at the > absence of a BOM. > > - R6RS a

bug#26058: utf16->string and utf32->string don't conform to R6RS

2017-03-13 Thread Taylan Ulrich Bayırlı/Kammer
Andy Wingo writes: > Hi, > > this is a tricky area that is not so amenable to quick patches :) Have > you looked into what Guile already does for byte-order marks? Can you > explain how the R6RS specification relates to this? > > https://www.gnu.org/software/guile/manual/html_node/BOM-Handling

bug#26058: utf16->string and utf32->string don't conform to R6RS

2017-03-13 Thread Andy Wingo
On Mon 13 Mar 2017 19:10, taylanbayi...@gmail.com (Taylan Ulrich "Bayırlı/Kammer") writes: > If I do binary I/O, the following situations are possible: > > 1. I'm guaranteed to get any possible bytes that happen to form a valid >BOM at the start of the stream as-is in the returned bytevector;