From: Gregory L. <gre...@ff...> - 2004-06-25 20:45:46
|
Ok, I did the test, removed this strange file (not a valid TTF file, checked that too) and everything work nicely now with 0.60b. If you want to reproduce this behavior (cannot call it a bug anymore, it is really my fault having a corrupted font directory), it is sufficient to create a non-font file in the Font directory, with TTF extension (a copy in a dos prompt is necessary, file explorer try to install the "font" on drag&drop), remove the font cache to force a rescanning, and the crash occur (using numarray, I still do not know why it worked with numeric...All I can say is that a non-valid ttf file cause a crash on matplotlib+numarray...) I do not know if nvestigating this is worthy, as nobody should have a non-valid ttf file in the font directory anyway, but maybe this will make the TTF scanning code more robust? Thanks for your help and sorry crying "Bug, bug" without real reason :-/ Best regards, Greg. |