public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "bruno at clisp dot org" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sourceware.org
Subject: [Bug locale/30694] New: The iconv program no longer tells the user which given encoding name was wrong
Date: Fri, 28 Jul 2023 10:12:25 +0000 [thread overview]
Message-ID: <bug-30694-131@http.sourceware.org/bugzilla/> (raw)
https://sourceware.org/bugzilla/show_bug.cgi?id=30694
Bug ID: 30694
Summary: The iconv program no longer tells the user which given
encoding name was wrong
Product: glibc
Version: 2.32
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: locale
Assignee: unassigned at sourceware dot org
Reporter: bruno at clisp dot org
Target Milestone: ---
When the user invokes the iconv program with an invalid FROM_ENCODING or
invalid TO_ENCODING, the error message no longer indicates which of the two was
wrong. Which leaves the user puzzled. Thus, it is a bad usability experience.
How to reproduce:
In glibc 2.32:
$ echo abc | iconv -f ARMSCII-8 -t UCS_4BE
iconv: failed to start conversion processing
In glibc 2.30:
$ echo abc | iconv -f ARMSCII-8 -t UCS_4BE
iconv: conversion to `UCS_4BE' is not supported
Try `iconv --help' of `iconv --usage' for more information.
--
You are receiving this mail because:
You are on the CC list for the bug.
next reply other threads:[~2023-07-28 10:12 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-28 10:12 bruno at clisp dot org [this message]
2023-07-28 10:15 ` [Bug locale/30694] " bruno at clisp dot org
2023-07-28 10:45 ` schwab@linux-m68k.org
2023-07-28 11:05 ` bruno at clisp dot org
2023-08-02 11:36 ` schwab@linux-m68k.org
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=bug-30694-131@http.sourceware.org/bugzilla/ \
--to=sourceware-bugzilla@sourceware.org \
--cc=glibc-bugs@sourceware.org \
/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).