Thanks for the comment. I agree. This is the reason why I liked Zsolt Vasvari's code, and I did not change the RelativeSizeSpan to AbsoluteSizeSpan. But you have to remember an absolute size in pixels can get bigger or smaller depending on the displayed screen's density (dpi), meaning AbsoluteSize is no longer absolute when displayed on the old (less dense) cellphone screen and on high resolution Android4 hardware. So I try to use dip (dp) sizes as much as I can, and specifying "absolute" dp size often yields more consistent results.
On May 7, 5:39 pm, "Jason Teagle" <[email protected]> wrote: > >i.e. using an html string like "<big>199</big> <small>km/h</small>" seems > >to work, > >although you cannot specify the sizes exactly... > > Just a quick note, specifying big / small or similar is considered better > than specific sizes in the world of accessibility since they refer to a size > *relative* to the user's current default font - so if they have enlarged the > font to cope with having difficulty reading it, then an application won't > suddenly change to a font that is too small to be readable for the user. -- You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
