pjkersten wrote: > > Not yet. Can you be more specific? When is that exception thrown, during > server start or during report generation?
I've tried myself and solved this. I didn't try all fonts, so I can't give a general solution. Here is what I did: I set the logging level to INFO on the server and restarted. After first connection of a client, all modules start logging, including report_truetype. For every font loaded, a message is spit out. Courier New as it seems, get registered under the name CourierNewPSMT. As the registration process uses the names in the font files themselves, I can't influence this naming scheme. However, using this name in the reports, no exception gets thrown. I guess that the other fonts you mentioned use unexpected names as well. This sheds some new light on the documentation, which states that the name from ttmkfdir is the name to use. As these two clearly differ, some further investigation is needed. For the next week, I don't have time to dive in. You can however use this as a workaround. Good luck and thanks for using. ------------------------ Pieter J. Kersten EduSense BV -------------------- m2f -------------------- -- http://www.openobject.com/forum/viewtopic.php?p=37609#37609 -------------------- m2f -------------------- _______________________________________________ Tinyerp-users mailing list http://tiny.be/mailman2/listinfo/tinyerp-users
