-
Notifications
You must be signed in to change notification settings - Fork 1
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
Feature Request: The ability to split text on multiple pages. (i.e. Support form feed character.) #15
Comments
Can you give me an example text that's not working? This is supposed to work
|
What I'm talking about is the ability to tell the program "go to the next page" for formatting reasons, not to split words that overflow the page. For example, if you are writing a diary and you want to separate the days with one or two blank pages between them. |
Ah, thanks for the clarification. Gutencraft currently purposefully removes blank pages because it's difficult to know if the page break was intentional when coming from other formats (like online books). An escaped character for a page break is an interesting idea. I'll think about how best to do that. |
The best way to do this is probably to support the form feed character. https://en.wikipedia.org/wiki/Page_break If you want to ensure the text will skip to the next page, use a form feed character. If you want to skip two pages (have a blank page between text), use two form feed characters. Gutencraft needs to add support for this. |
If I may give a suggestion on the Gui implementation, I think that an easy and useful addiction would be adding a button in the Gutencraft interface that would copy the form feed character in the user's clipboard, so that they could then paste it in the text where their original page breaks were located. |
This program is really useful, but as of now there is no way of formatting long texts on multiple pages. It would be really nice to have a way to tell the program "go to the next page" instead of manually entering many newlines until it's right.
Maybe some sort of escape character could be a solution?
The text was updated successfully, but these errors were encountered: