Re: byte-order marks

2013-01-30 Thread Andy Wingo
Hi, On Tue 29 Jan 2013 18:09, Mark H Weaver writes: > Having slept on this, I think I agree that 'open-input-file' should > auto-consume BOMs. Patch attached. > However, 'open-input-file' should not auto-detect the encoding by > default, The ball is in your court now :) > and should only con

guile-json 0.1.0 released

2013-01-30 Thread Aleix Conchillo Flaqué
Hi, I just release guile-json 0.1.0. https://github.com/aconchillo/guile-json This is my first guile related release, so comments are more than welcome. guile-json is a JSON module for Guile. It supports parsing and building JSON documents according to the http:://json.org specification. Th

Re: guile-json 0.1.0 released

2013-01-30 Thread Nala Ginrut
On Wed, 2013-01-30 at 01:48 -0800, Aleix Conchillo Flaqué wrote: > Hi, > > I just release guile-json 0.1.0. > > https://github.com/aconchillo/guile-json > > This is my first guile related release, so comments are more than welcome. > > guile-json is a JSON module for Guile. It supports pars

Re: guile-json 0.1.0 released

2013-01-30 Thread Billy O'Connor
Aleix Conchillo Flaqué writes: > Hi, > > I just release guile-json 0.1.0. > > https://github.com/aconchillo/guile-json > Nice. Looks like you have a small typo in README.org: diff --git a/README.org b/README.org index e7d9c91..a10d75a 100644 --- a/README.org +++ b/README.org @@ -93,7 +93,7

Re: guile-json 0.1.0 released

2013-01-30 Thread Ian Price
Aleix Conchillo Flaqué writes: > I just release guile-json 0.1.0. > > https://github.com/aconchillo/guile-json I've uploaded it to my guildhall repo. Current users can guild update guild install json to obtain it. People who aren't using Guildhall can find instructions at https://githu

Re: guile-json 0.1.0 released

2013-01-30 Thread Aleix Conchillo Flaqué
On Wed, Jan 30, 2013 at 9:17 AM, Billy O'Connor wrote: > > Nice. Looks like you have a small typo in README.org: > Thanks! Fixed. Aleix

Re: guile-json 0.1.0 released

2013-01-30 Thread Aleix Conchillo Flaqué
On Wed, Jan 30, 2013 at 10:19 AM, Ian Price wrote: > > I've uploaded it to my guildhall repo. Current users can > > guild update > guild install json > > to obtain it. People who aren't using Guildhall can find instructions at > https://github.com/ijp/guildhall/wiki/Getting-Started > Thanks I

Re: byte-order marks

2013-01-30 Thread Ludovic Courtès
Hello! Andy Wingo skribis: > On Tue 29 Jan 2013 18:09, Mark H Weaver writes: [...] >> However, 'open-input-file' should not auto-detect the encoding by >> default, > > The ball is in your court now :) Can we discuss this one in the other thread, so my little brain and mailbox don’t get confu

[PATCHES] Discard BOMs at stream start for UTF-{8,16,32} encodings

2013-01-30 Thread Mark H Weaver
Hello all, I researched this some more, and discovered that removal of byte-order marks (BOMs) is the responsibility of iconv, which discards BOMs from the beginning of streams when using the UTF-16 or UTF-32 encodings, but *not* for UTF-16LE, UTF-16GE, UTF-32LE, UTF-32GE or any other encoding. It

[PATCH] Do not scan for coding declarations in open-file

2013-01-30 Thread Mark H Weaver
Andy Wingo writes: > On Tue 15 Jan 2013 10:32, l...@gnu.org (Ludovic Courtès) writes: >> As usual, backward-compatibility gives us an incentive not to change >> anything in 2.0. But perhaps we should change that in 2.2. >> >> Thoughts? > > IMO we should update the docs and leave it as it is, thou