Re: [Rlib-devel] RPDF font embedding

[Zoltan B. <zb...@du...>]

Zoltan Boszormenyi =C3=ADrta:

> Hi,
>
> Bob Doan =C3=ADrta:
>
>> Hey,
>>
>> Patch looks good so far!  You probably want to update from CVS, I've
>> =20
>>
>
> Thanks! OK, I update my local CVS copy, although I did a checkout on=20
> Monday. :-)
> I will send a newer patch soon.
>
>> been playing in RPDF a little.  I made some gchar * GStrings for speed
>> improvement.  In general, RLIB is now 2x faster with some of the
>> speedups I made over the past few days.  One of the worst things it wa=
s
>> doing was doing a getlocale on every format!  That's quite expensive
>> because it has to do a getenv.
>> =20
>>
>
> Impressive speedup.
>
>> We probably don't want to check for ttf2pt1 on rpdf_new because that
>> would be expensive.  We probably only want to check for it once if we
>> are actually going to embed fonts.
>> =20
>>
>
> What about doing it on the first rpdf_new()?
> A global static variable may keep this info.


On second thought, I would like to introduce rpdf_init()
so the test for ttf2pt1 can be done here, and later, when we are actually
embed fonts, the generated font metrics can be collected in a
hash table with the same key as the fonts themselves.
The hash table could also be initialized here.
Also, rpdf_shutdown() destroys the info.

>> We also might want to be able to cache the results of ttf2pt1 in some
>> sorta binary form to load from in order to optionally speed up interna=
l
>> font loading.  Maybe provide some sorta utility w/ RLIB to do it.
>

The cached metrics could also be saved in rpdf_shutdown and
reloaded next time in rpdf_init().

>> In general you are headed in the right direction and it looks good.  H=
ow
>> far do you plan on taking this?  Is your plan to only support fixed
>> width fonts in RLIB or were you thinking about variable width fonts?
>

I guess you want to compete with CrystalReports in the long term. :-)
A visual editor would also come handy...

Best regards,
Zolt=C3=A1n B=C3=B6sz=C3=B6rm=C3=A9nyi