From: Steffen Nurpmeso <steffen@sdaoden.eu>
To: musl@lists.openwall.com
Subject: Re: Re: iconv failure (ISO-2022-JP) since musl update on AlpineLinux
Date: Tue, 27 Feb 2018 22:28:54 +0100 [thread overview]
Message-ID: <20180227212854.Wo26a%steffen@sdaoden.eu> (raw)
In-Reply-To: <20180227201940.GR1436@brightrain.aerifal.cx>
Hello Rich Felker.
Rich Felker <dalias@libc.org> wrote:
|On Tue, Feb 27, 2018 at 08:44:32PM +0100, Steffen Nurpmeso wrote:
|> Rich Felker wrote:
...
|> but i wrote:
|>||After updating to musl-1.1.19-r0 there i saw test failures for the
|>||MUA i maintain, namely regarding the mentioned charset. I will
..
|>|Does the data round-trip correctly? I don't think you can expect
|>
|> Ok, i see what you mean, yes, musl iconv(1) can roundtrip. But..
...
|> Well... In my cases the MUA fails to convert to ISO-2022-JP at
|> all, because an iconv(3) error happens. And when i instrument my
..
|I think the test is just using an output buffer that's under the
|worst-case size needed for conversion to ISO-2022-JP. The E2BIG error
|is specified for "Input conversion stopped due to lack of space in the
|output buffer" and is not really an error; is just means the
|conversion stopped before reaching the end and you need to resume with
|a new buffer for the remainder of the conversion.
That iconv(3) wrapper i had hacked into that MUA in 2014 was
indeed complete nonsense and entirely false. Now corrected.
Thanks for answering the brain damage.
And i will adjust the tests to checksum only the headers and the
roundtrip output of the body content, thanks for pointing this
out. Be aware you have been credited.
Ciao,
--steffen
|
|Der Kragenbaer, The moon bear,
|der holt sich munter he cheerfully and one by one
|einen nach dem anderen runter wa.ks himself off
|(By Robert Gernhardt)
prev parent reply other threads:[~2018-02-27 21:28 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-27 16:57 Steffen Nurpmeso
2018-02-27 17:34 ` Rich Felker
2018-02-27 19:44 ` Steffen Nurpmeso
2018-02-27 20:19 ` Rich Felker
2018-02-27 21:28 ` Steffen Nurpmeso [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20180227212854.Wo26a%steffen@sdaoden.eu \
--to=steffen@sdaoden.eu \
--cc=musl@lists.openwall.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.
Code repositories for project(s) associated with this public inbox
https://git.vuxu.org/mirror/musl/
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 NNTP newsgroup(s).