<i18n dev> RFR: 8195686: ISO-8859-8-i charset cannot be decoded, should be mapped to ISO-8859-8

Pratiksha.Sawant duke at openjdk.org
Thu Oct 10 05:33:11 UTC 2024


On Sun, 25 Aug 2024 07:21:10 GMT, Alan Bateman <alanb at openjdk.org> wrote:

>> Mapping ISO-8859-8-I charset to ISO-8859-8.
>> Below mentioned 2 aliases are added as part of this:-
>> **ISO-8859-8-I**
>> **ISO8859-8-I**
>> 
>> The bug report for the same:- https://bugs.openjdk.org/browse/JDK-8195686
>
> I've added the "csr" label as this is adding support for "ISO8859-8-I".
> 
> Naoto asked me about it but I'm not 100% sure if it's an alias or a different charset. I think this topic may require input from those more familiar with charsets in environment that require bidi processing. Or if the mappings are available then I think we can see if they are identical to ISO8859-8.

@AlanBateman Since the mapping is just an alias to ISO-8859-8 do we still need CSR request to be created for the pull request?

-------------

PR Comment: https://git.openjdk.org/jdk/pull/20690#issuecomment-2404062521


More information about the i18n-dev mailing list