Lines Matching refs:font
31 package sun.font;
33 import sun.font.GlyphLayout.*;
43 * 2) we keep a mapping independent of font using the key Most likely
46 * Once we know which engine to use for a font, we always know, so we
51 * font/script pair. The engine would hold onto the table(s) from the
52 * font that it needs. If we have multiple threads using the same
58 * still requires a separate layout engine per font, because of the
66 * potentially half a dozen per font. But we'd have to stack-allocate
67 * some state that included the pointer to the required font tables.
70 * selector and the font. The selector indicates which engine to use,
72 * font tables (the selector indicates which). Then layout is called,
74 * exit. So the association is between the font/script (layout engine
80 * just uses the mapper from the font/strike. Another default case
82 * the font (or script or lang?) it wouldn't need to extract this
84 * upcalls to check if the font supports a particular unicode
88 * a particular font. Loading the hastable with 40 or so keys 30+ of
90 * instead having a per-font list of 'scripts with non-default
101 * script/font combinations will be small, so a flat hashtable should
126 public LayoutEngine getEngine(Font2D font, int script, int lang) {
127 return getEngine(new LayoutEngineKey(font, script, lang));
155 Font2D font = key.font();
156 FontStrike strike = font.getStrike(desc);
158 if (font instanceof TrueTypeFont) {
159 layoutTables = ((TrueTypeFont) font).getLayoutTableCache();
161 nativeLayout(font, strike, mat, gmask, baseIndex,
164 font.getUnitsPerEm(), layoutTables);
168 nativeLayout(Font2D font, FontStrike strike, float[] mat, int gmask,