From: Florian Weimer <fweimer@redhat.com>
To: sotrdg sotrdg via Libc-help <libc-help@sourceware.org>
Cc: sotrdg sotrdg <euloanty@live.com>
Subject: Re: Why iconvdata does not provide UTF-EBCDIC but other EBCDIC encodings?
Date: Tue, 29 Aug 2023 10:09:35 +0200 [thread overview]
Message-ID: <87h6oinubk.fsf@oldenburg.str.redhat.com> (raw)
In-Reply-To: <SA1PR11MB7130B5E5A54A12834190241FB2E7A@SA1PR11MB7130.namprd11.prod.outlook.com> (sotrdg sotrdg via Libc-help's message of "Tue, 29 Aug 2023 01:35:57 +0000")
* sotrdg sotrdg via Libc-help:
> UTF-EBCDIC is the most commonly used EBCDIC coding but gconv does not
> support that. Why?
Wikipedia says it's rarely used, so maybe that's why no one has
contributed a codec.
Thanks,
Florian
next prev parent reply other threads:[~2023-08-29 8:09 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-29 1:35 sotrdg sotrdg
2023-08-29 8:09 ` Florian Weimer [this message]
2023-09-01 15:26 ` sotrdg sotrdg
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=87h6oinubk.fsf@oldenburg.str.redhat.com \
--to=fweimer@redhat.com \
--cc=euloanty@live.com \
--cc=libc-help@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).