<i18n dev> RFR: 8195686: ISO-8859-8-i charset cannot be decoded, should be mapped to ISO-8859-8
Jason Mehrens
duke at openjdk.org
Fri Oct 11 13:39:22 UTC 2024
On Thu, 10 Oct 2024 16:51:09 GMT, Justin Lu <jlu at openjdk.org> wrote:
>...(if there is sufficient demand)...
I don't fully understand the conditional acceptance. Can't @psawant19 abandon the alias PR and use the existing ISO-8859-8 source from OpenJDK to create new ISO-8859-8-I Charset? The level off effort to share common code, proxy wrap, or so forth between two Charsets wouldn't be that much of a lift or long term debt. If the community is willing to to the work then acceptance is really a willingness to approve the change. Are all housed OpenJDK solutions around this a no?
>Naoto pointed out, utilize the CharsetProvider would seem like appropriate solutions to me.
That has been the solution suggested for years. They have been documented JavaMail/JakartaMail FAQ. I copied them into the ticket here:
https://github.com/eclipse-ee4j/angus-mail/issues/147#issuecomment-2354433380
I'll leave that AngusMail ticket open until this comes to a close.
-------------
PR Comment: https://git.openjdk.org/jdk/pull/20690#issuecomment-2407433620
More information about the i18n-dev
mailing list