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


------- Additional Comments From madcoder at debian dot org  2009-06-01 20:51 -------
(In reply to comment #0)
> There is no support for the GSM 03.38 character set as part of iconv. Are there
> any plans to support it?

For what it's worth, GSM has multiple issues:

- GSM is not always in its 7bits packed form (for example, when used in SMPP or
UCP/EMI messages), which means that you need two flavors.

- GSM is often used with the latin1 extension (and I know some other are also
defined) which adds another layer of alternatives.

- the 7bit packed encoding makes it rather unsuitable for iconv interfaces which
assumes that codepoint sizes are multiple of 8 bits: there is no way to push
14bits only for example, you can only transcode 8 gsm codepoints at a time, or
you need to _very_ carefuly craft the data you send (and hence know how the
iconv state works) for it to be useful.

- finally in GSM '\0' is ascii '@', which is a PITA, but arguably not relevant
to iconv.

All in all, I'm not sure that iconv and GSM are a good match.


-- 


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-06-01 20:52 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 [this message]
2009-10-30 15:21 ` drepper at redhat dot com
     [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=20090601205151.750.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).