Using localedef to define custom charmaps

[Carlos O'Donell]

On 06/11/2018 02:00 PM, Florian Weimer wrote:
> On 06/11/2018 07:53 PM, Carlos O'Donell wrote:
>> On 06/11/2018 12:51 PM, Florian Weimer wrote:
>>> On 06/11/2018 06:49 PM, Carlos O'Donell wrote:
>>> 
>>>> However, once you've done the work of using the charmap to
>>>> build the output locale data ... why do you need it anymore?
>>>> 
>>>> Conversions will be handled by gconv converters after that.
>>> 
>>> What if there's no gconv converter for my charmap?
>> 
>> Are we talking in the abstract here?
> 
> Not quite.  I suggested a custom charmap as a way to customize
> transliteration for a character which is present in the destination
> character set:
> 
> https://sourceware.org/bugzilla/show_bug.cgi?id=23076
> 
> If there are no custom charmaps, then obviously this will not work.

Right.

I gave my suggestion in that bug :-)

>> I imagine some simple character maps could be automatically driven
>> by the existing data.
> 
> We auto-generate gconv modules from charmaps for most (if not all)
> 8-bit character sets.  This is a bit unfortunate because the code is
> identical, and the overhead of loading the data via dlopen is quite
> large (mostly in terms of private RSS consumption).

That's an implementation detail that can be changed?

Cheers,
Carlos.