[open-beos-printing] Re: PDF Writer 2

12/6/01 8:56:51 AM, "Philippe Houdoin" <philippe.houdoin@xxxxxxx> wrote:

>>- clipping to inverse picture is not implemented
>
>Well, with current PDFlib features, it wouldn't be easy.
>Maybe we can ask help PDFlib' Thomas Wertz about this topic... 

Please do so :-)

Honestly, I think he can not help us.
What we need is an operation that takes the BPicture and calculates 
the difference from the paper rectangle, the result should be
the clipping area.
Don't ask me, how to implement that ;)

>>- clipping to text or image is not implemented
>
>DrawShape on font glyph shapes=3F
>For image, I don't even know how to figure this kind of clipping in my 
>mind!
>
>>Text is now encoded as MacRoman. Interestingly I have
>>not managed to encode text in WinAnsi correctly!
>
>In previous version (unreleased pre v0.3, the one I send to you first 
>time), I was using the BFont encoding code, as the font was/is 
>embebded. 

The version I changed yesterday did not display umlaute correctly,
was that the version (more or less) you sent me? Sorry, can't remember.

>It seem to work to me, but I'm not a PDF font encoding guru...
>In fact, there is still a comment about that before the 
>convert=5Ffrom=5Futf8 call in PDFWriter::DrawString()

Do you know how the string is encoded that DrawString receives?
Is it always utf8 or the encoding of the current font?

>Could you tell me why I was wrong=3F

The version I changed encoded the characters in utf8,
which AFAIK is not supported by PDFLib and the enconding
for the font in the PDF file was set to "host", which
I guess under BeOS is winansi.

>>Other issues:
>>There seems to be a bug in the image drawing routine.
>
>Could you give details here=3F

Not ATM have to analyze the problem first, 
but maybe you can reproduce it with Productive when
you make a with color gradient filled polygon.

- Michael

Other related posts: