On Fri, 26 Jun 2026 05:54:20 GMT, Shruthi Acharya <[email protected]> wrote:
> When XSLT output method is html, characters supported by the target encoding > were serialized as HTML entity references (for example, é as eacute;). This > caused failures when the generated output was later processed as XML. > > **Solution:** > Update HTML serializer to write characters directly when they are supported > by the configured encoding, and retain existing entity escaping behavior for > unsupported characters. > > **Testing:** > Verified XSLT transformation with accented characters and confirmed generated > output can be parsed successfully without XML parsing failures. > > Performed Tier1 and Tier2 tests in Linux with and without the fix. No > regression found > > > The bug report for the same: https://bugs.openjdk.org/browse/JDK-8387291 > > --------- > - [x] I confirm that I make this contribution in accordance with the [OpenJDK > Interim AI Policy](https://openjdk.org/legal/ai). I can't comment on the specifics of the branch condition, but there are formatting issues that need to be addressed and this change should incorporate a test case to verify what this issue fixes. ------------- PR Review: https://git.openjdk.org/jdk/pull/31689#pullrequestreview-4634791614
