Quote:
Originally Posted by jbjb
I've not read the thread completely, but at first sight it looks like there's a hard-coded array of sizes presented by the UI, and a different hard-coded array of sizes supported by the renderer. These hard-coded sizes can clearly be changed (as detailed in the thread), but that's not the same as saying that the renderer can handle sizes specified by arbitrary numbers at runtime. (Of course, it also doesn't mean it can't!).
In any case, that's a digression - the point that several of us have been making is simply that despite the fact that it might be thought that it should be simple, and that it's 'Programming 101' , there's a great deal of professional experience (30-odd years in my case) which says that in the real world, code is frequently badly structured, badly written and an unmaintainable and unmodifiable mess.
Again, that's not to say that the Kindle firmware is such a mess, just that to assume without knowledge that it isn't is perhaps a tad optimistic.
/JB
|
And this design might actually be good if all fonts do not render properly for all sizes.