Peter, RFE was probably right. But its moot for 1.6 as we are in the very final stages of stabilising the release so unless it can be shown to be a regression (something that used to work in 1.5 but now doesn't) it too late.
-phil. Peter B. West wrote:
On Tue, 2006-07-04 at 13:12 -0700, Doug Felt @ Sun wrote:Peter: Please file bugs on both issues. There are a few characters we special case when converting to glyphs - tab, cr, lf are it in the ASCII range, and we also filter bidi control characters and some other formatting characters. Everything else goes through the regular font CMAP, and if the font maps it, most of the time it will provide the missing glyph for these characters. If the font doesn't map the character at all, we use the missing glyph. The missing glyph typically looks like an empty rectangle. Currently the characters we map ourselves are the following. 0x0009, 0x000A, 0x000D, 0x200C, 0x200D, 0x200E, 0x200F, 0x2028, 0x2029, 0x202A, 0x202B, 0x202C, 0x202D, 0x202E, 0x206A, 0x206B, 0x206C, 0x206D, 0x206E, 0x206F You'll note we don't currently handle ZERO WIDTH SPACE (U+200B)... This is an implementation detail, of course, and some vendors (Apple, in particular) probably do something different. This is just FYI. DougDoug, I think I made a little mistake. I've put both of these in as RFEs, which I (now) assume means they won't be considered for 1.6. Should I change these to bugs when the opportunity arises? Peter =========================================================================== To unsubscribe, send email to [EMAIL PROTECTED] and include in the body of the message "signoff JAVA2D-INTEREST". For general help, send email to [EMAIL PROTECTED] and include in the body of the message "help".
=========================================================================== To unsubscribe, send email to [EMAIL PROTECTED] and include in the body of the message "signoff JAVA2D-INTEREST". For general help, send email to [EMAIL PROTECTED] and include in the body of the message "help".
