Re: [ft-devel] Reg:True Type Font display

2010-02-25 Thread mpsuzuki
Hi, On Thu, 25 Feb 2010 12:59:38 +0530 Poornima poornim...@jasmin-infotech.com wrote: We have ported Free Type Font Library (freetype-2.3.11) on fixed point DSP processor (BF533, 600 MHz) in VDSP Platform. Basic functionality is working fine. We have got output display in LCD monitor through

RE: [ft-devel] Reg:True Type Font display

2010-02-25 Thread Poornima
Hi, Thank you for the response. FT_Load_Glyph() takes lot of time compared to FT_Get_Char_Index(). Please find the details below. FT_Get_Char_Index()- It takes around 0.005 ms per character. FT_Load_Glyph() - It takes around 2.9 ms per character. Could you please provide your inputs for

Re: [ft-devel] Reg:True Type Font display

2010-02-25 Thread Werner LEMBERG
We have ported Free Type Font Library (freetype-2.3.11) on fixed point DSP processor (BF533, 600 MHz) in VDSP Platform. Basic functionality is working fine. We have got output display in LCD monitor through HDMI connector. But the FT_Load_Char() function is taking lot of time to execute

Re: [ft-devel] Reg:True Type Font display

2010-02-25 Thread mpsuzuki
On Thu, 25 Feb 2010 14:49:16 +0530 Poornima poornim...@jasmin-infotech.com wrote: FT_Load_Glyph() takes lot of time compared to FT_Get_Char_Index(). Thanks. FT_Get_Char_Index()- It takes around 0.005 ms per character. FT_Load_Glyph() - It takes around 2.9 ms per character. Hmm. In next, could

Re: [ft-devel] Patented bytecode interpretter and fallback to autohinter

2010-02-25 Thread Behdad Esfahbod
On 02/24/2010 06:19 PM, Werner LEMBERG wrote: Not really. A yes/partial/no answer should be enough. why do you need a `partial' if there is no possibility to find out which ranges are hinter or unhinted? What I want to use this info for is to be able to write configurations that say if the

Re: [ft-devel] Patented bytecode interpretter and fallback to autohinter

2010-02-25 Thread Behdad Esfahbod
On 02/25/2010 05:21 PM, Werner LEMBERG wrote: No idea about the in-between. That's what I called maybe. But it's not a very flexible API. Another way would be to get the number of hinted glyphs. I'm not sure. Sounds sensible. The arguments could be `start' and `end' of a range (or