2014-04-22 6:30 GMT+02:00 Tudor Girba <[email protected]>: > One question is why do still have the disable free type fonts option? > This was useful when free type was still in development, but I think now > it is no longer useful. > Or are there still use cases for it? > > Doru > > > At the risk of repeating myself (that's maybe 10 times I say it here, but it's like shouting in the desert...) , freetype is pretty inefficient because it displays characters one by one (call a primitive foreach and every character). So if you are on a not so fast device, strike fonts are still a good option because the primitive displays groups of characters in a batch. So please, please, please, for once before breaking things that works and replacing them by a thing that works only partially, do it the other way around: - first make it fully work (that means add a new freetype primitive displaying batch of chars) - then drop any historical bits you want
Of course, you are free to completely drop support for slow machines, but it must be consciously. > On Mon, Apr 21, 2014 at 7:32 PM, stepharo <[email protected]> wrote: > >> Hi >> >> when freetype is on do you think that it makes sense to have strikeFont >> proposed as default fonts? Like it is done right now, I get bitmapVera >> even if I >> want to see FreeType fonts. >> >> Stef >> >> > > > -- > www.tudorgirba.com > > "Every thing has its own flow" >
