[scribus-dev] GSOC: PDF Embedding

[Thach Tran]

Hi all,

I have put together a final summary for my project---what I have been  
able to do within the scope of this summer.
Due to the high volume of text :-), I enclosed the text file in this  
message for ones who's interested.
FYI, this file also got committed to my project's repo.

Cheers,
Thach
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: gsoc09-pdfexport-summary.txt
URL: <http://lists.scribus.net/pipermail/scribus-dev/attachments/20090819/2ce9f7a1/attachment.txt>
-------------- next part --------------



On 10 Aug 2009, at 17:01, Pierre Marchand wrote:

> Vous (Thach Tran) avez ?crit :
>> I will have about one week to wrap things up before the GSoC' 09 is
>> over. I will try to polish up all the code and fix any bugs I might
>> find in this final week. So it would be great if you could give me a
>> few ideas/suggestions to improve things a little.
>> Thank you and looking forward to hear from you.
>> Thach
>
> Hi Thach,
>
> I didn?t realise that we were so close to the end!
> I?ve started to hack around your code to bring answers to the  
> difficult question
> "What do we do when source content stream and target PDF document  
> have color
> space mismatch?" The way we handle it for other colored resources  
> (images) is
> to perform the conversion or to attach needed material (ICC) to do  
> it. In the
> case of embedded PDF pages, as you?ve pointed out,  we know about  
> target color
> space too late in the process to just insert an item in pre-flighter  
> and
> delegate the pain to the user :-) but even though we would know  
> target color
> space sooner, as long as we don?t do color conversion of objects in  
> the
> content stream of placed PDF pages, we would be unable to take  
> appropriate
> measures in case of mismatch*.
>
> I stop my digression here!
> Now, I think we can spend the last week at preparing the future. I?m  
> already
> happy with the code you wrote and in my opinion you can let it as is  
> (just
> continue to keep in sync with Trunk). What we need is to see it  
> documented to
> be able to easily step into it.
> I would like to have more methods documentations in PDFAnalyzer and  
> esp. where
> you created public interfaces (PDFAnalyzer::inspectCanvas). Writing  
> how it can
> be extended will be good too, and more generally summarize all the  
> work you
> done for the program and how you think we can continue (or even  
> rewrite!) it
> would be interesting.
>
> Someone else?
>
>
> * Would be interesting to look if it?s such a huge job to do  
> conversion though
> and how it could be integrated in images CM system.
>
> -- 
> Pierre Marchand
> http://www.oep-h.com
>