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

Can I pass the --splitcol argument without executing it? #63

Open
tophee opened this issue Feb 27, 2023 · 0 comments
Open

Can I pass the --splitcol argument without executing it? #63

tophee opened this issue Feb 27, 2023 · 0 comments

Comments

@tophee
Copy link

tophee commented Feb 27, 2023

I'm not sure how briss determines how many rectangles it suggests after loading a file (or where to position them), but the default seems to be one rectangle per page cluster and it seems to select all text on the page (I believe it only selected the text on left half of the page in briss 0.9).

Since we typically use briss to split double-page pdfs into single-page pdfs, I think the 0.9 behaviour makes more sense, but it would be even better if we get two rectangles on each page to work with from the start. I was hoping that the --splitcol argument would do that but found that it will immediately execute the split without giving me a chance to make corrections.

So I wonder whether there is any way of telling briss (in manual mode) that each page should be split into columns?

If it is not yet possible, a basic version could be implemented by adding a routine that splits the existing rectangles exactly into half (almost the same as right-clicking on the rectangle and selecting "Split into columns", except that the split is currently not in the middle of the rectangle, I don't know why).

Another thing: In briss 0.9, it was also possible to set all rectangles to the width and height of the biggest one (by ctrl-left clicking). Is this feature no longer available?

Finally (while I'm at it): is there any way of stopping the briss window from maximizing itself after loading a page. I don't see the point... (if only because it makes the "Crop" and "Preview" buttons harder to find...
Briss-2023-02-27 at 10 08 13@2x

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant