GNU bug report logs - #17044
R6RS open-input-file failed to recognize UTF-8 encoded file

Previous Next

Full log

View this message in rfc822 format

From: help-debbugs <at> gnu.org (GNU bug Tracking System)
To: Xin Wang <dram.wang <at> gmail.com>
Subject: bug#17044: closed (Re: bug#17044: R6RS open-input-file failed to
 recognize UTF-8 encoded file)
Date: Thu, 20 Mar 2014 03:47:03 +0000

[Message part 1 (text/plain, inline)]

Your bug report

#17044: R6RS open-input-file failed to recognize UTF-8 encoded file

which was filed against the guile package, has been closed.

The explanation is attached below, along with your original report.
If you require more details, please reply to 17044 <at> debbugs.gnu.org.

-- 
17044: http://debbugs.gnu.org/cgi/bugreport.cgi?bug=17044
GNU Bug Tracking System
Contact help-debbugs <at> gnu.org with problems

[Message part 2 (message/rfc822, inline)]

From: Mark H Weaver <mhw <at> netris.org>
To: Xin Wang <dram.wang <at> gmail.com>
Cc: 17044-done <at> debbugs.gnu.org
Subject: Re: bug#17044: R6RS open-input-file failed to recognize UTF-8 encoded
 file
Date: Wed, 19 Mar 2014 23:45:26 -0400

Xin Wang <dram.wang <at> gmail.com> writes:

> `open-input-file' in (rnrs io simple) can not recognize UTF-8 encoded
> file, `open-input-file' in core do not have this problem.
>
> I think it is caused by a bug in definition of `open-input-file',
> which forget to pass third argument `buffer-mode' to
> `open-file-input-port'.

Indeed, thanks for tracking this down.

> BTW, `open-output-file' seems to have a similar problem.

Fixed in 5dcbcfcef8eefd1f9e57d8ba69efe1ca945c95b1.  This will be in
2.0.11, which will most likely be released within a couple of days.

   Thanks,
     Mark

[Message part 3 (message/rfc822, inline)]

From: Xin Wang <dram.wang <at> gmail.com>
To: bug-guile <at> gnu.org
Subject: R6RS open-input-file failed to recognize UTF-8 encoded file
Date: Thu, 20 Mar 2014 08:41:15 +0800

[Message part 4 (text/plain, inline)]

`open-input-file' in (rnrs io simple) can not recognize UTF-8 encoded file,
`open-input-file' in core do not have this problem.

I think it is caused by a bug in definition of `open-input-file', which
forget to pass third argument `buffer-mode' to `open-file-input-port'.

BTW, `open-output-file' seems to have a similar problem.

[Message part 5 (text/html, inline)]

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.