Closed GoogleCodeExporter closed 9 years ago
http://www.google-melange.com/gci/task/view/google/gci2011/7189239
Original comment by AaronPer...@gmail.com
on 25 Dec 2011 at 1:27
Original comment by peli0...@googlemail.com
on 25 Dec 2011 at 1:06
GCI task unclaimed.
Original comment by peli0...@googlemail.com
on 30 Dec 2011 at 10:35
Instead of modifying the existing fonts, I think we should just add two or more
fonts like (ICS) Normal - this should be a font that looks "normal" on a Ice
Cream Sandwich. And (ICS) Tiny that is tiny. But one will also be able to
select the others on ICS, if they want bigger sizes, the others will just be
recommended for ICS?
Original comment by dkremov
on 8 Jan 2012 at 8:37
By "fonts", do you mean the font size menu entries? I think new entries should
not be necessary, the problem appears to be that the application doesn't handle
the very high resolution screen on the Galaxy nexus correctly (>300 dpi,
1280x720 or so). In which units are you expressing the font sizes, and are you
applying any additional density-dependent correction factors? For example, this
effect could be caused by specifying sizes in dp (density-independent pixels)
and then separately multiplying by a density scaling factor, which would apply
the scaling factor twice.
Original comment by Klaus.We...@gmail.com
on 8 Jan 2012 at 9:56
Good point, it looks like the scaling factor is applied twice somehow. Not sure
where this exactly happens - maybe when a theme is applied?
Original comment by peli0...@googlemail.com
on 8 Jan 2012 at 10:15
Related issue 435 for OI Notepad.
Original comment by peli0...@googlemail.com
on 12 Jan 2012 at 11:08
Problem and solution are described here:
http://stackoverflow.com/questions/5032355/android-textview-settextsize-incorrec
tly-increases-text-size
http://stackoverflow.com/questions/3687065/textview-settextsize-behaves-abnormal
ly
Fix is on the way.
Original comment by peli0...@googlemail.com
on 21 Jan 2012 at 8:54
This issue was closed by revision r4085.
Original comment by peli0...@googlemail.com
on 21 Jan 2012 at 9:16
Original issue reported on code.google.com by
peli0...@googlemail.com
on 10 Dec 2011 at 11:21Attachments: