I can only guess why this range was excluded.
My guess is that it was something to do with an attempt at
allowing as many of these glyphs as possible to come from
(for example) a Chinese font in a chinese locale even though we
always put the latin font first ..
The interesting reason why adding
Hi,
Kindly review fix for JDK-8202537. Fix is to upgrade Unicode
consortium's CLDR data into JDK from current version 29 to 33.
For more info : http://cldr.unicode.org/index/downloads/cldr-33
Bug : https://bugs.openjdk.java.net/browse/JDK-8202537
Patch:
BTW I think the synopsis really needs updating !
Once you know what is going on, continuing to title it after the random
empirical observation of the reporter is not necessary. I've changed it to :
"Remove exclusion range for phonetic chars in windows fontconfig.properties"
Please use that in
