public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "drepper at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sources.redhat.com
Subject: [Bug libc/10226] Support for GSM 03.38 character set in iconv
Date: Fri, 30 Oct 2009 15:21:00 -0000	[thread overview]
Message-ID: <20091030152111.16264.qmail@sourceware.org> (raw)
In-Reply-To: <20090601171019.10226.jens.k.mueller@gmx.de>


------- Additional Comments From drepper at redhat dot com  2009-10-30 15:21 -------
I don't want to go this route.  From what I heard, there are a myriad of these
"encodings".  Just like in the olden ASCII days, everybody picks a "standard"
and then modifies it slightly to their own needs.  You can collect these
converteers in a third-party package, if you want.

-- 
           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|WAITING                     |RESOLVED
         Resolution|                            |WONTFIX


http://sourceware.org/bugzilla/show_bug.cgi?id=10226

------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.


  parent reply	other threads:[~2009-10-30 15:21 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-01 17:10 [Bug libc/10226] New: " jens dot k dot mueller at gmx dot de
2009-06-01 17:27 ` [Bug libc/10226] " drepper at redhat dot com
2009-06-01 18:06 ` jens dot k dot mueller at gmx dot de
2009-06-01 20:52 ` madcoder at debian dot org
2009-10-30 15:21 ` drepper at redhat dot com [this message]
     [not found] <bug-10226-131@http.sourceware.org/bugzilla/>
2011-11-10 20:35 ` arnotixe at gmail dot com
2014-07-01 20:15 ` fweimer at redhat dot com

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=20091030152111.16264.qmail@sourceware.org \
    --to=sourceware-bugzilla@sourceware.org \
    --cc=glibc-bugs@sources.redhat.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).