Export Feature Requests

This is feature request to consider adding to your backlog.

I currently finished an MD doc that translates to ~200 pages in a PDF. It includes images as well as link previews.

As I’ve mentioned before, page breaks are important to me at a minimum on H1 & H2.

This request isn’t just about PDF page breaks because I mentioned that already. I am also exporting to ePub and noticed when embedding the appropriate HTML tag to indicate page-breaks they are treated as text in both the PDF (understandable) and ePub.

My understanding is that ePub would treat the following html as a page break. Apple Books treats it as plain text and is visible in the ePub output.

It is possible I’m simply not entering it correctly and needs to be embedded as a comment for both PDF and ePub or this is something to add to your list if you agree it’s something you can implement. Entering it as a comment hides it in both PDF and ePub formats but neither act on implementing the page break. I understand it for PDF but was hopeful it would work for ePub.

I’m now leaning to focusing on ePub simply as I was only considering PDF to share with others. Reading or printing 100’s of pages of a PDF is not realistic but reading via ePub is a much better format. In the end, I’ll probably want to export to both formats and page breaks in both are a necessity (maybe not).

I will acknowledge page breaks in ePub might not make sense as it was intended to be a free-flowing implementation and does work well. Thankfully the MD headers translate to the TOC.

As for PDF, yea that is needed since it’s really meant to be a printed doc and having a new section start in the middle of another page looks & feels strange.

In the end, I might still be figuring this all out and am sharing and making requests that I hope you feel free to correct me.

btw, how would I know if you’ve accepted a feature request and added it to your backlog, do you share that info anywhere?

thanks -tom