|
|
Rank: Newbie
Groups: Member
Joined: 1/20/2012
Posts: 6
|
We have a requirement to create a "booklet" PDF from an existing PDF. This would require reading in the pages of an existing PDF scaling them to a "half sheet" size and then combine two pages from the original to a single page in the new PDF. This is usually refered to as Nupping. Acm objects look like they could do this, but I see no way to read in an existing PDF with PDfDocument and then passing those pages into Acm as somethong to draw on a new page.
|
|
Rank: Administration
Groups: Administration
Joined: 5/27/2007
Posts: 24,194
|
I do not believe you can do that with our PDF product. You can load an existing PDF file with PdfDocument (simply pass the file name to the constructor), get all the pages and "half size" or even rotate each page. However you can't put two pages on a single page. So whatever you do, a 10 page PDF goes in will still be a 10 page PDF comes out (unless you delete or add pages). Sorry about that!
|
|
Rank: Newbie
Groups: Member
Joined: 1/20/2012
Posts: 6
|
Thanks for the very quick response. We are currently using another tool to get what we want but was hoping to use a single tool set (yours). Is it feasible for EO to add this functionality in a future release. I saw other posts in here asking for similar "repaging" support.
|
|
Rank: Administration
Groups: Administration
Joined: 5/27/2007
Posts: 24,194
|
Hi,
It is technical possible for us to implement this but we need to be sure that it fits into our design, be flexible enough, and also is very easy use to use for our users. If you can provide some additional information about how you would use your current tool to do that (just some pseudo to demonstrate the idea) it would be very helpful for us.
Thanks!
|
|
Rank: Newbie
Groups: Member
Joined: 1/20/2012
Posts: 6
|
This is the flow based on the other tool we use. Doesn't have to flow like this but you get the idea of the concept. For simplicity this Psuedo code does not account for partial pages.
PdfDocument inDoc = new PdfDocument(existing PDF);
PdfDocument outDoc = new PdfDcoument();
for ( int i = 0; i < inDoc.Pages.Count; )
{
PdfPage outPage = new PdfPage();
// set outPage size, margins
PdfPage in1 = inDoc.Pages[i++];
PdfPage in2 = inDoc.Pages[i++];
// Offset, scale, rotate in1 and in2 fit in a part of outPage
outPage.Merge(in1, in2);
outDoc.Pages.Add(outPage);
}
ouDoc.Save
|
|
Rank: Administration
Groups: Administration
Joined: 5/27/2007
Posts: 24,194
|
This one looks too much like our own. We would be very curious to know which product you are using since their interface almost look exactly like ours, which could be a serious problem because that would raise the issue of whether they are copying elements of our product. Can you provide an exact name/Url so that we can verify this? If you don't feel comfortable posting publically in the forum, you can send a private message to us.
Thanks!
|
|
Rank: Newbie
Groups: Member
Joined: 1/20/2012
Posts: 6
|
When I wrote the Psuedo code I purposely used your class names as an example of how to do this with your classes. The tool we are using does not have these classes.
|
|
Rank: Administration
Groups: Administration
Joined: 5/27/2007
Posts: 24,194
|
We will still need to verify and evaluate their interface first in order to get a basic idea of how this feature is supported by other products on the market because we have not have any request on this feature before. We won't put in a feature just because a single user requested it, we have to have enough information to thoroughly evaluate it to determine that it is both useful enough and practically enough to support it. If we don't do that, we would end up with a product with thousands of different features that don't work well together with each other at all.
Thanks!
|
|