Community
Participate
Working Groups
java.awt.Font has a series of methods to query available glyphs. SWT Font or FontData should provide similar methods. Otherwise, SWT client can not select appropriate Font for strings with unicode encoding.
Is there any comments? I am still waiting.
FYI... Saitoh-san has agreed to quantify the performance gain.
We need this functionality so that we can use alternate characters and avoid the default character glyph. See the code I submitted to bug 181166 as a way of implementing this for windows.
Please fix this. Inserting a character which is not available from the font in use results in the character being inserted in another font, which then increases the line height (at least in my case).
This bug/feature request seems to be looked at every 2 years. Is there a solution in sight? There's still a workaround if the font to be checked is a "system font": just use the AWT font... it's kinda sad! But what if the font is loaded straight from a file?
*** Bug 181166 has been marked as a duplicate of this bug. ***
I am trying to create a character map. It's a dialog in which you select a font from a combo box and then see a table with all the characters that the font can render. A fix would help me to test if a specific font can render a certain character.
Twenty years later, I want to know if I can use the symbols for union and intersection with the user's display font, and ... find this issue.