What steps will reproduce the problem?
The current fix to support the display speedup requires additional work to
unbreak the font attributes. The AttributedString turned in to a total waste of
time/energy.
What is the expected output? What do you see instead?
I'm thinking of a font container that can appropriately resize the fonts. The
italic and bold fonts may need to be slightly smaller to support being inside a
cell. We can also think about supporting different fonts for different Unicode
block regions. We should be able to handle it in a manner in which we can keep
the glyph well within bounds of our cell.
Original issue reported on code.google.com by yam...@gmail.com on 2 Aug 2012 at 2:35
Original issue reported on code.google.com by
yam...@gmail.comon 2 Aug 2012 at 2:35