[
https://issues.apache.org/jira/browse/NETBEANS-4135?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17445642#comment-17445642
]
Eirik Bakke commented on NETBEANS-4135:
---------------------------------------
Using StyleContext.getDefaultStyleContext().getFont was a nice trick! It seems
to make a difference for physical fonts such as "Segoe UI" or "Consolas", but
not for the logical Java fonts such as "Monospaced" or "Dialog", which are
always loaded as composite fonts.
I tried using this call from the NetBeans editor libraries as well, and it
successfully makes e.g. Chinese and Japanese characters displayable in the
editor even when a physical font that does not support them is selected (e.g.
"Consolas"). I might make a PR out of that later, as a solution for
NETBEANS-904.
> FlatLaf on Windows does not render all Unicode characters
> ---------------------------------------------------------
>
> Key: NETBEANS-4135
> URL: https://issues.apache.org/jira/browse/NETBEANS-4135
> Project: NetBeans
> Issue Type: Bug
> Components: FlatLaf
> Affects Versions: 11.3
> Reporter: Karl Tauber
> Assignee: Karl Tauber
> Priority: Major
> Fix For: 12.0
>
>
> reported here [https://github.com/JFormDesigner/FlatLaf/issues/81]
> On Windows, FlatLaf components can not render all Unicode characters because
> the used font "Segoe UI" does not contain all characters and FlatLaf does not
> create a Swing "composite font", which could render all Unicode characters.
> On Linux, FlatLaf already creates a composite font.
> On Mac, the used font seems to contain all (or more) Unicode characters.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
