On 2009-11-19 17:28-0500 Hazen Babcock wrote:
> Alan W. Irwin wrote:
>> That leaves the "modern" unicode text rendering path used by the cairo, qt,
>> ps, psttf, and other devices that does not use plfreetype. If I recall
>> correctly you may have added at least one centralized helper function for
Alan W. Irwin wrote:
> On 2009-11-14 21:22-0500 Hazen Babcock wrote:
>
>> This should be fixed in v10591. The problem was with the two different text
>> rendering paths. The second text rendering path seemed like a good idea at
>> the time, but now I'm sort of leaning towards reverting it. It do
On 2009-11-14 21:22-0500 Hazen Babcock wrote:
> This should be fixed in v10591. The problem was with the two different text
> rendering paths. The second text rendering path seemed like a good idea at
> the time, but now I'm sort of leaning towards reverting it. It doesn't really
> make driver
Alan W. Irwin wrote:
> Hi Hazen:
>
> I am addressing this post mostly to you as the principal cairo device
> driver
> maintainer. It might also be of concern to the developers of plbuf.c as
> well, but I don't think plbuf.c is the issue, see below.
>
> Recently I have been testing the -save opt
Hi Hazen:
I am addressing this post mostly to you as the principal cairo device driver
maintainer. It might also be of concern to the developers of plbuf.c as
well, but I don't think plbuf.c is the issue, see below.
Recently I have been testing the -save option for example 1. This uses
plreplot
