mailing list of musl libc
 help / color / mirror / code / Atom feed
From: Florian Weimer <fweimer@redhat.com>
To: Bruno Haible <bruno@clisp.org>
Cc: Rich Felker <dalias@libc.org>,
	 musl@lists.openwall.com, "A. Wilcox" <awilfox@adelielinux.org>,
	 bug-bison@gnu.org, bug-gnulib@gnu.org,
	Arjun Shankar <ashankar@redhat.com>
Subject: Re: [musl] Building Bison 3.7 with musl (was Re: portability issues with unicodeio)
Date: Thu, 30 Jul 2020 11:02:25 +0200	[thread overview]
Message-ID: <87d04djrz2.fsf@oldenburg2.str.redhat.com> (raw)
In-Reply-To: <2117749.CLknGyfR5K@omega> (Bruno Haible's message of "Thu, 30 Jul 2020 03:43:40 +0200")

* Bruno Haible:

> Yes and no. The code is not making assumptions about a particular iconv()
> implementation. But it needs to distinguish two categories of replacements
> done by iconv():
>   - those that are harmless (for example when replacing a Unicode TAG
>     character U+E00xx with an empty output),
>   - those that are better not presented to the user, if the programmer has
>     specified a fallback (for example, replacing all non-ASCII characters
>     with NUL, '?', or '*').
>
> The standards don't help in making the distinction.
>
> Therefore whether you consider said glibc and libiconv behaviour as
> "non-conforming" or not is irrelevant.

Could you sketch briefly what you need?  We have identified some issues
with the existing iconv interface.  If we add an enhancement, it would
make sense to cover these requirements.

Thanks,
Florian


  reply	other threads:[~2020-07-30  9:02 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-29 23:23 A. Wilcox
2020-07-29 23:48 ` A. Wilcox
2020-07-30  0:05 ` Rich Felker
2020-07-30  0:12   ` A. Wilcox
2020-07-30  1:43   ` Bruno Haible
2020-07-30  9:02     ` Florian Weimer [this message]
2020-07-30  9:39       ` [musl] Re: iconv replacements Bruno Haible

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=87d04djrz2.fsf@oldenburg2.str.redhat.com \
    --to=fweimer@redhat.com \
    --cc=ashankar@redhat.com \
    --cc=awilfox@adelielinux.org \
    --cc=bruno@clisp.org \
    --cc=bug-bison@gnu.org \
    --cc=bug-gnulib@gnu.org \
    --cc=dalias@libc.org \
    --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).