From: Mike Gran <INVALID.NOREPLY@gnu.org>
To: "Mike Gran" <spk121@yahoo.com>, "Ludovic Courtès" <ludo@gnu.org>,
bug-guile@gnu.org
Subject: [bug #29643] Current locale has higher precedence than `coding:' when determining file port encoding [1.9.10]
Date: Sat, 05 Jun 2010 21:51:08 +0000 [thread overview]
Message-ID: <20100605-215108.sv73118.34960@savannah.gnu.org> (raw)
In-Reply-To: <20100605-162922.sv73118.84516@savannah.gnu.org>
Update of bug #29643 (project guile):
Status: Confirmed => Ready For Test
_______________________________________________________
Follow-up Comment #1:
I pushed a new branch to the repo "mike-port-encodings" that may solve the
problem.
Consider the top commit
62abf139798af3f35ca3c89200389dc75d51a159
Note that while I was in there, I decided that a similar problem to this bug
is that open-file doesn't honor binary-mode it its port encoding, so I added
that feature.
Working this revealed unrelated bugs in read-line and
scm_i_scan_for_encoding, which are also patched in that branch.
_______________________________________________________
Reply to this item at:
<http://savannah.gnu.org/bugs/?29643>
_______________________________________________
Message sent via/by Savannah
http://savannah.gnu.org/
next prev parent reply other threads:[~2010-06-05 21:51 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-22 16:36 [bug #29643] Current locale has higher precedence than `coding:' when determining file port encoding [1.9.10] Ludovic Courtès
2010-06-05 16:29 ` Mike Gran
2010-06-05 21:51 ` Mike Gran [this message]
2010-07-17 11:25 ` Mike Gran
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20100605-215108.sv73118.34960@savannah.gnu.org \
--to=invalid.noreply@gnu.org \
--cc=bug-guile@gnu.org \
--cc=ludo@gnu.org \
--cc=spk121@yahoo.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).