You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
What steps will reproduce the problem?
1. take a pdf with two columns
2. use vector pdf output OR kindle 3 output.
(e.g. input two column, output vector pdf + portrait vertical scroll single
image per file
OR
input two column, output kindle 3: gives images no pdf with text preserved)
3. vector pdf output gives a not correct output (using vector pdf: does not
crop and convert to pdf in the order it showed during processing), while kindle
3 output gives images (useless)
What is the expected output? What do you see instead?
Pdf files (not images file) cropped in the correct order. Instead i get pdf
files completely messed up or image files (not utilizable on kindle touch: poor
quality image, text not preserved).
What version of the product are you using? On what operating system?
paperCrop_0.51_rev117 on windows 7 64 bit.
Please provide any additional information below.
File input and two different file output given below. First is vector pdf,
second kindle 3.
Kindle 3 output given below would be fantastic and the final solution for two
column pdf conversion if only the output file would be a pdf with text
preserved. There is a great program called cut2col-v34c.jar (which you can find
here http://www.cp.eng.chula.ac.th/~somchai/cut2col/ )that output pdfs with
text but yours program is far better in detecting the crop order (crop areas 1,
2, 3 etc). It only does not give a pdf output which is very bad when you try to
read the document on kindle touch (no correct text zooming, not good quality
image, moving around the image is a pain, etc.)
Could you please talk with this programmer of cut2col and work together to make
a this tool even better? (correct crop order and pdf with text preserved)?
Original issue reported on code.google.com by [email protected] on 10 Jul 2012 at 7:30
Original issue reported on code.google.com by
[email protected]
on 10 Jul 2012 at 7:30Attachments:
The text was updated successfully, but these errors were encountered: