When I send to my editor I just tell her to modify the files as she sees fit. When I get them back I put the new files on a branch and create a PR so I can start discussions on changes, etc.
I think the process is pretty darn efficient but it's hard to sell it to non-techie writers/editors.
I pass `-V documentclass:scrbook` to pandoc and then I can use e.g. '\frontmatter' and '\mainmatter' in the MD source.
As I say, I'm getting reasonable results, but it's one of those "I can't be the first person to do this" situations. Got any tips or links to share?
There were also some manual transformation steps occurring on their end, because there was a cutover point where the Word doc was no longer accepted and you had to just quote page and line numbers to get further changes made.
This was probably the point at which the text had been moved into InDesign for typesetting by the designer.
:: Convert Markdown to DOCX format, adding a pagebreak at every \newpage
pandoc -f markdown -t docx --filter=pandoc-docx-pagebreakpy -o build.docx ^
foreword.md ^
preface.md ^
acknowledgments.md ^
part_a.md ^
1.md ^
2.md ^
3.md
:: File needs to be opened in Word, saved, and then closed to generate physical Table of Contents :/
@echo off
echo Please open build.docx in Word, save, and then close.
pause
:: Set e-book metadata
ebook-meta build.docx --authors "First M. Last" --author-sort "Last, First M." --title "Book Title" --title-sort "Book Title"
:: Convert DOCX to MOBI (Kindle)
:: --share-not-sync Makes it so cover shows up in Kindle for PC but also breaks Kindle WhisperSync. Remove if you want WhisperSync.
:: See https://manual.calibre-ebook.com/faq.html#the-covers-for-my-mobi-files-have-stopped-showing-up-in-kindle-for-pc-kindle-for-android-ipad-etc
:: --cover "media/cover.jpg" --share-not-sync
ebook-convert build.docx build.mobi