Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merge double sided scanned document #67

Closed
loxK opened this issue May 9, 2019 · 8 comments
Closed

Merge double sided scanned document #67

loxK opened this issue May 9, 2019 · 8 comments
Labels
feature Request for a new feature
Milestone

Comments

@loxK
Copy link

loxK commented May 9, 2019

I often have to scan double sided documents. I scan one side then the other. Finnally I merge them using PDFSam which has the functionality to properly arrange double sided documents on merge.

I'd rather use pdfarranger for that task.

@jeromerobert
Copy link
Member

What do you mean by "properly arrange double sided documents on merge" ?

@loxK
Copy link
Author

loxK commented May 13, 2019

Having a double sided document of multiple pages:

  • you scan one side of all pages to a PDF document
  • you scan the other side of all pages to another PDF document
  • you merge them with an app and have the pages properly ordered (first page doc one, then first page doc two, second page doc one, then second page doc two and so on)

@dreua
Copy link
Member

dreua commented May 14, 2019

The logic sounds easy enough. More important question imo is the user interface. I am just thinking about an "Add interleaved" option where you add a new PDF and set that pages should be inserted at every 2nd (3rd, 4th if there is a use case for that) position in the current buffer starting at position 0, 1, ...

But actually a dedicated "Merge double sided" wizard might be more appropriate and easier to use.

@dreua
Copy link
Member

dreua commented May 14, 2019

Now I'm curious how PDFSam does the UI..

@loxK
Copy link
Author

loxK commented May 15, 2019

I can only show it in french, but PDFsam basic is free (not open source). The UI is rather simple.

image

@jeromerobert
Copy link
Member

@dreua I would prefer not to have a GUI for that feature. I think that having an interleave action would be enough. It should take the current selection into account and work on all pages if nothing is selected. I would like to do the undo/redo refactoring (#59) before we (you ?) work on this issue to void conflicts.

@dreua
Copy link
Member

dreua commented May 15, 2019

Yes, waiting for the undo/redo makes sense, thanks for the reminder! To be honest, I'm not sure if I will have the time to work on this, but I might.

@loxK Here is a simple command line python script for the purpose, in case that helps you in the meantime.

@dreua
Copy link
Member

dreua commented May 15, 2019

Oh and for the UX:

Are you planning to include selection in the undo/redo? (I.e. selection of multiple pages is restored after a "interleave" action is undone. Might be very useful if users need a second try to get the "which of my interleaved ranges becomes the first page"-problem fixed.)

My current idea for a user story would be:

  1. User adds both pdf files in pdfarranger, either via command line argument, file open action or drag and drop (pdf file from file manager or pages from other pdfarranger instance). [Nothing to be done here, just for completeness sake.]
  2. User selects a range of pages, either the front sides or the back sides (usually this would be one of the files but I would not like to add restrictions here) [Done, dito.]
  3. User has two actions in the context or Edit menu: "Interleave (first)" or "Interleave (second)"
  4. The selected pages are inserted (moved) between the unselected pages. In case of "first" the first selected pages becomes the first page in the result, in case of "second", the first unselected page becomes the first page in the result.
    Ideally, the selection would be preserved so that the user has good visual feedback.

Every feedback is appreciated. I'm especially unsure about the names of the actions.

@jeromerobert jeromerobert added the feature Request for a new feature label Jun 25, 2019
@jeromerobert jeromerobert added this to the 1.4 milestone Jul 30, 2019
@jeromerobert jeromerobert modified the milestones: 1.4, 1.5 Feb 3, 2020
@jeromerobert jeromerobert added this to the 1.5 milestone Mar 22, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature Request for a new feature
Projects
None yet
Development

No branches or pull requests

3 participants