- 
    Bug 
- 
    Resolution: Fixed
- 
     P3 P3
- 
    9, 10, 11
- 
        b14
- 
        Verified
| Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build | 
|---|---|---|---|---|---|---|
| JDK-8203552 | 11.0.1 | Jonathan Gibbons | P3 | Resolved | Fixed | team | 
                    From Martin Desruisseaux on javadoc-dev:
Hello
I noticed a behavioural change of {@code} inline tag with Java 10. In Java versions 5 to 8, text inside {@code} was rendered literally, including Unicode characters outside ASCII range. But in Java 10, Unicode characters are replaced by the "\u" escape sequence. For example:
{@code foo(…)}
Was rendered as foo(…) in HTML javadoc generated by Java 8, but is now rendered as foo(\u2026) in javadoc generated by Java 10. Is this behavioural change intentional? I do not see notice about handling of Unicode characters in [1].
Martin
Hello
I noticed a behavioural change of {@code} inline tag with Java 10. In Java versions 5 to 8, text inside {@code} was rendered literally, including Unicode characters outside ASCII range. But in Java 10, Unicode characters are replaced by the "\u" escape sequence. For example:
{@code foo(…)}
Was rendered as foo(…) in HTML javadoc generated by Java 8, but is now rendered as foo(\u2026) in javadoc generated by Java 10. Is this behavioural change intentional? I do not see notice about handling of Unicode characters in [1].
Martin
- backported by
- 
                    JDK-8203552 javadoc handles non-ASCII characters incorrectly. -           
- Resolved
 
-         
- relates to
- 
                    JDK-8271258 @param with non-ascii variable names produces incorrect results -           
- Resolved
 
-         
- links to
