Regarding removal of auto-detection of ISO-2022-JP charset in HTML

[Jun Kokatsu]

Hi All,

I'm planning to remove support for auto-detection of ISO-2022-JP charset.

https://chromestatus.com/feature/6576566521561088

I wanted to ask if I should file a standard position to Mozilla for this removal, and if so, what is the spec which defines this? Note that Safari does not support auto-detection of ISO-2022-JP.

Thanks,

Jun

[David Baron]

For what it's worth, https://hsivonen.fi/chardetng/ is a write-up of the approach Firefox uses for encoding auto-detection (unless things have changed substantially since 2020, which I think is unlikely).  If you do file a Mozilla position, I recommend at-mentioning @hsivonen on the github issue.

-David

--
You received this message because you are subscribed to the Google Groups "blink-api-owners-discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to blink-api-owners-d...@chromium.org.
To view this discussion visit https://groups.google.com/a/chromium.org/d/msgid/blink-api-owners-discuss/CAOWKMF59tvHPTKX6od-RM2ebNJfPLZSG3rmE-fa1n76fwbeYVA%40mail.gmail.com.

[TAMURA, Kent]

On Fri, Mar 21, 2025 at 9:18 AM David Baron <dba...@chromium.org> wrote:

For what it's worth, https://hsivonen.fi/chardetng/ is a write-up of the approach Firefox uses for encoding auto-detection (unless things have changed substantially since 2020, which I think is unlikely).  If you do file a Mozilla position, I recommend at-mentioning @hsivonen on the github issue.

-David

On Thu, Mar 20, 2025 at 6:06 PM 'Jun Kokatsu' via blink-api-owners-discuss <blink-api-ow...@chromium.org> wrote:

Hi All,

I'm planning to remove support for auto-detection of ISO-2022-JP charset.

https://chromestatus.com/feature/6576566521561088

I wanted to ask if I should file a standard position to Mozilla for this removal, and if so, what is the spec which defines this? Note that Safari does not support auto-detection of ISO-2022-JP.

I think there are no specifications about the encoding auto-detection.

However, this change affects browser interoperability, and filing a standard position would be helpful.

 

Thanks,

Jun

--
You received this message because you are subscribed to the Google Groups "blink-api-owners-discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to blink-api-owners-d...@chromium.org.
To view this discussion visit https://groups.google.com/a/chromium.org/d/msgid/blink-api-owners-discuss/CAOWKMF59tvHPTKX6od-RM2ebNJfPLZSG3rmE-fa1n76fwbeYVA%40mail.gmail.com.

--
You received this message because you are subscribed to the Google Groups "blink-api-owners-discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to blink-api-owners-d...@chromium.org.

To view this discussion visit https://groups.google.com/a/chromium.org/d/msgid/blink-api-owners-discuss/CAG0MU3jE5AyD%3DMr6%2B%2BKLNHZKhn-syr_57FGs29oiOuko2VrLoQ%40mail.gmail.com.

--

TAMURA Kent
Software Engineer, Google

[Domenic Denicola]

On Fri, Mar 21, 2025 at 9:34 AM TAMURA, Kent <tk...@chromium.org> wrote:

On Fri, Mar 21, 2025 at 9:18 AM David Baron <dba...@chromium.org> wrote:

For what it's worth, https://hsivonen.fi/chardetng/ is a write-up of the approach Firefox uses for encoding auto-detection (unless things have changed substantially since 2020, which I think is unlikely).  If you do file a Mozilla position, I recommend at-mentioning @hsivonen on the github issue.

-David

On Thu, Mar 20, 2025 at 6:06 PM 'Jun Kokatsu' via blink-api-owners-discuss <blink-api-ow...@chromium.org> wrote:

Hi All,

I'm planning to remove support for auto-detection of ISO-2022-JP charset.

https://chromestatus.com/feature/6576566521561088

I wanted to ask if I should file a standard position to Mozilla for this removal, and if so, what is the spec which defines this? Note that Safari does not support auto-detection of ISO-2022-JP.

I think there are no specifications about the encoding auto-detection.

However, this change affects browser interoperability, and filing a standard position would be helpful.

Kent is right that there is no specification of how encoding auto-detection is done. In the HTML Standard, this part just says "The user agent may attempt to autodetect the character encoding from applying frequency analysis or other algorithms to the data stream."

I agree that filing a position with Mozilla would be helpful for this.

 

 

Thanks,

Jun

--
You received this message because you are subscribed to the Google Groups "blink-api-owners-discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to blink-api-owners-d...@chromium.org.
To view this discussion visit https://groups.google.com/a/chromium.org/d/msgid/blink-api-owners-discuss/CAOWKMF59tvHPTKX6od-RM2ebNJfPLZSG3rmE-fa1n76fwbeYVA%40mail.gmail.com.

--
You received this message because you are subscribed to the Google Groups "blink-api-owners-discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to blink-api-owners-d...@chromium.org.
To view this discussion visit https://groups.google.com/a/chromium.org/d/msgid/blink-api-owners-discuss/CAG0MU3jE5AyD%3DMr6%2B%2BKLNHZKhn-syr_57FGs29oiOuko2VrLoQ%40mail.gmail.com.

--

TAMURA Kent
Software Engineer, Google

--
You received this message because you are subscribed to the Google Groups "blink-api-owners-discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to blink-api-owners-d...@chromium.org.

To view this discussion visit https://groups.google.com/a/chromium.org/d/msgid/blink-api-owners-discuss/CAGH7WqGWCHkJhMhHunWU4XMGXNi2F5YU_XOsZmNH%2B%3DDV-n_dOA%40mail.gmail.com.

[Jun Kokatsu]

Thank you all!
I'll file a position then!

Thanks,

Jun