[OpenJDK 2D-Dev]  Review request for 8073400: Some Monospaced logical fonts have a different width
philip.race at oracle.com
Wed Feb 10 20:25:16 UTC 2016
I expect the exclusion range is there for a reason.
I think (guess) that the intent was that where there is a sequence like
then those code points should come from the chinese font.
Perhaps your adjusted exclusion range should apply only to the
which are already putting the locale font first.
Unfortunately it doesn't appear that this is possible with the supported
i.e it supports selection only by charactersubsetname, not also by
But you should check the code to see if this is in fact the case.
There may need to be a non-ideal decision or a revision to that spec.
And why be so narrow ? It seems you have made an even odder situation
in having just those two code points 'un'-excluded.
The argument that those were the two a customer complained about does not
hold up very well.
I think you should also run this whole change+discussion by i18n-dev ..
On 01/14/2016 02:32 AM, dmitry markov wrote:
> Could you review the fix for jdk9, please?
> bug: https://bugs.openjdk.java.net/browse/JDK-8073400
> webrev: http://cr.openjdk.java.net/~dmarkov/8073400/jdk9/webrev.00/
> Problem description:
> On Windows some characters (in particular, left and right double
> quotation marks) have width differing from other characters' widths,
> when Monospaced logical font is used.
> The default monospaced font for windows platform is Courier New. It
> contains the desired characters, (i.e. '\u201c' and '\u201d'). However
> the characters are in 'exclusion ranges' for this font due to settings
> in windows.fontconfig.properties. So when we try to obtain glyphs for
> these characters and calculate their bounds, we fallback to another
> font (Lucida) and use its glyphs.
> Remove the following set of characters u2018 - u201F from the
> exclusion ranges.
More information about the 2d-dev