[Etoys-notify] [JIRA] Updated: (SQ-103) Etoys shows wrong font size if fallback to Pango
jira at immuexa.com
jira at immuexa.com
Mon Apr 13 06:59:34 EDT 2009
[ http://tracker.immuexa.com/browse/SQ-103?page=all ]
timothy updated SQ-103:
Fix Version: 2010 release
> Etoys shows wrong font size if fallback to Pango
> Key: SQ-103
> URL: http://tracker.immuexa.com/browse/SQ-103
> Project: squeakland
> Type: Bug
> Components: etoys
> Reporter: team
> Fix For: 2010 release
> From TRAC 8290 (korakurider, sept 2008)
> Etoys89 on Joyride2369
> If Etoys run with Pango and there is a morph using font that is in-image one and doesn't exist for Pango, that fallbacks to other font. But at same time font size change silently while in halo font menu shows original size. It seems correct font size is used if that is set manually. I think size change should be avoided. And if size is changed actually, font menu should show actual setting.
> How to reproduce: (Preparation) Install Sazanami font onto XO, set locale of Sugar to Japanese.
> (1) Start Etoys, then locale automatically switched to Japanese. "GALLERY OF PROJECT" cloud on index screen that original font is KomikaTextKaps 36pt shrinks to size of about 24point. But in halo menu, font setting is displayed same as original.
> (2) If font setting is changed manually to 24, then to 36point, result appearance is close to original.
> (yoshiki) This is another biggie but nice to have item. The ink rectangle and logical rectangle can be very different from font to font. So figuring out the ink size would need a lot of work.
> (korakurider) Please document design and limitation of current implementation. Without that from you developers, very few people can understand what explained.
> It seems to me you are addressing why smaller text is shown with Pango fallback, but why (1)and(2) in my test case displays differently haven't been addressed; both use same font family and size and what you explained seems not the case. I am not convinced why this inconsistency is nice-to-have.
> (bert) The phrase "biggie but nice to have" meant it's a big bug, and it would be nice to have a fix, but we cannot effort to work immediately on this.
This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
For more information on JIRA, see:
More information about the Etoys-notify