This is the mail archive of the
mailing list for the glibc project.
Re: acceptable new gconv modules
- From: "Carlos O'Donell" <carlos at systemhalted dot org>
- To: Akihiro TSUKADA <tskd08 at gmail dot com>, "libc-help at sourceware dot org" <libc-help at sourceware dot org>
- Date: Thu, 5 Mar 2015 18:17:20 -0500
- Subject: Re: acceptable new gconv modules
- Authentication-results: sourceware.org; auth=none
- References: <544D1D93 dot 5080005 at gmail dot com> <20150305223255 dot GD19311 at vapier>
On Thu, Mar 5, 2015 at 5:32 PM, Mike Frysinger <email@example.com> wrote:
> On 27 Oct 2014 01:13, Akihiro TSUKADA wrote:
>> I have a question about contribution to the iconv modules.
>> I wrote new gconv modules for the character encodings
>> which are used only in digital television systems,
>> and I'd like to contribute them if it is possible.
>> Is a contribution of gconv module for such an application-domain
>> specific character encoding acceptable to glibc?
>> [I posted the same question to libc-alpha but
>> it seems that it was inappropriate and did not get any responses,
>> so I re-post it here.]
> i don't think we have a policy here. the problem is that encodings are largely
> a "solved" problem: everything is unicode based now. the trouble with adding
> more modules now is that people see it as a support issue.
> i guess you could attach the file here and we can see how much overhead it
> actually adds.
Exactly what I was thinking.