> > Well, the glyphs aren't `loaded'; you are rather collecting the file > offsets in an array. >
Yes. > > It loads glyphs in the increasing order of their character code. > > Not necessarily: The order of `char_loc' commands could be arbitrary, > say, > > Character 3: dx 3801088 (58), width 728179 (57.65427), loc 11007 > Character 4: dx 3604480 (55), width 699053 (55.34819), loc 11226 > Character 0: dx 3407872 (52), width 655362 (51.88892), loc 10368 > Character 1: dx 4521984 (69), width 873816 (69.18521), loc 10521 > Character 2: dx 4259840 (65), width 815562 (64.57289), loc 10736 > Character 5: dx 4063232 (62), width 786434 (62.26666), loc 11365 > Yes. > And as the `indices table' is formed in such a way, it will remain > > unsorted, > > You have to do sorting again! I wrote in my last e-mail that you need > *two* *separate* arrays so that you can replace the `linear searching' > with accessing a pre-sorted array instead. > Oh yes! I get it. Thanks. Parth
_______________________________________________ Freetype-devel mailing list Freetype-devel@nongnu.org https://lists.nongnu.org/mailman/listinfo/freetype-devel
