Re: [matplotlib-devel] [PATCH] don't print undefined glyphs in ps backend

2007-02-15 Thread Evgeniy Stepanov
On Thursday 15 February 2007 21:41, Nicolas Grilly wrote: > On 2/14/07, Paul Barrett <[EMAIL PROTECTED]> wrote: > > My first reply: > > > > I suggest that this patch not be applied, since this was the intended > > behavior when the font manager was implemented. The standard behavior > > for indic

Re: [matplotlib-devel] [PATCH] don't print undefined glyphs in ps backend

2007-02-14 Thread Evgeniy Stepanov
On Wednesday 14 February 2007 21:53, Nicolas Grilly wrote: > On 2/14/07, Evgeniy Stepanov <[EMAIL PROTECTED]> wrote: > > FT2Font.get_charmap() returns a mapping from glyph index to character > > code. This looks like a very bad design decision to me, because several &g

Re: [matplotlib-devel] [PATCH] don't print undefined glyphs in ps backend

2007-02-14 Thread Evgeniy Stepanov
Sorry, I was too hasty. The patch is wrong, here is the real reason: 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 0x

[matplotlib-devel] [PATCH] don't print undefined glyphs in ps backend

2007-02-14 Thread Evgeniy Stepanov
Hi, currently, PS backend does not work well with some fonts. For instance, it displays a dotted square instead of whitespace with Arial, and some strange dots instead of whitespace with Times New Roman. This patch fixes it by omitting glyphs named ".notdef" from PS output. diff -urN matplotlib-0