On 2/14/07, Paul Barrett <[EMAIL PROTECTED]> wrote: > I still feel this way, but maybe I should change my tune and let the > changes go in.
What do you think about the comments made earlier in this thread: > FT2Font.get_charmap() returns a mapping from glyph index to character code. > This looks like a very bad design decision to me, because several character > codes can correspond to one glyph. For example, in Times New Roman, both 0x32 > (space) and 0xA0 (nbsp) are mapped to glyph index 3. Of course, the first one > gets lost in get_charmap(). I don't remember why we did it this way originally, or if was you or I who did it, but if it is correct that the mapping is sometimes many codes point to one one glyph index, but there each glyph index must point to a single character code (the latter must be correct, right?) then reversing it seems to be the right course. But it's been a long time since I delved into freetype internals ... JDH ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ Matplotlib-devel mailing list Matplotlib-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
