Open kakaroto opened 5 years ago
Good news, I've managed to fix pretty much everything with workarounds: the reference.docx trick held the answer to everything.
\n###### \n\n
and I edited the style for Heading 6 in the reference doc and enabled the "Insert page break before" option in Word. Now I get the page breaks where I want them.# <center>
into <center>\n#
that I enable if I export to HTML or disable otherwise.###
with heading 3 style for centered text which I automatically change the html tag to using transformations as well, and I enable it if I export to docx.>
into ####
and > >
into #####
and set my Heading 4 and Heading 5 styles to different fonts, alignements, etc.. to reproduce the "different voice" effect I wanted (I use it for epigraphs actually and for some right aligned quotes I wanted to have).``" for verbatim to add empty lines (between chapter subtitle and first paragraph for example), and that's still broken in Manuskript's HTML renderer, but it works fine with pandoc, so with my other transformations to fix the
# Overall, I have everything I need right now, though it took a lot of workarounds. I would still suggest adding the feature for the page break separator in the combobox, and the option to specify the reference document or template, as well as the option for docx to enable the custom styles (will be easier to set a custom style in the reference doc and specify it by name rather than having to rely on unused headings) as it can help others. If not, at least this issue has information on how the behavior can be achieved with pandoc for others to refer to in the future.
EDIT: I added the docx+styles support, but it turns out it wasn't needed because the styles extension is enabled by default. I've used that to create new styles and not re-use headings for my needs, this way the resulting docx doesn't have bookmarks everywhere a text is centered or styled differently.
Especially the lack of options (or documentation for options) for separators is annoying. I can see that "\n" produces a newline. What other codes are there? I'd really love to have page breaks. Also, "I want more granularity". For the top two levels of folders I want page breaks, whereas for deeper levels a newline is just fine. Thank you for working on this program!
I've just started using Manuskript and I like it a lot (other than the frequent crashes unfortunately, slow downs and a couple of issues, but I can live with most of that). The thing that is annoying me the most at the moment though is the compile options because we can only export to HTML with Manuskript itself (which works quite well), but for doc/openoffice/epub, we have to use pandoc and it has trouble with some things, such as text alignment (I've seen their open issue on the subject https://github.com/jgm/pandoc/issues/719 and I've seen the issue reported here as well https://github.com/olivierkes/manuskript/issues/301).
When I use :
It works well in Manuskript's HTML export (centered heading), but with pandoc, it will show the
#
on a line on its own, then followed by the centered text on the next line. If I instead write :Then in Manuskript's HTML export, it will show a centered
# Chapter 1
but it will appear correctly in pandoc's HTML export. This difference in behavior between Manuskript and pandoc is very annoying and I wanted to mention it, even though you probably can't do much about it (not without introducing a regression).The main issue for me is that the exported document by pandoc has a very bad formatting.
<Book title>\nby <name>
in the middle of the page).<Folder name> : <POV> \n <One line Summary>
. This made me have a Text element under each chapter just to write the chapter title/subtitle my custom way. Having a 'template for folder->text conversion' would be cool though this isn't particularly critical.A solution to my issues are the following :
$title: $pov \n$summary
).[text]{custom-style="some voice"}
but for it to work, the output format needs to be "docx+styles" (see custom styles) so having that by default, or having it as a checkbox for additional pandoc options would be great.For the template idea, have a look at this repo with template docs. pandoc has a --template option for those, or a --reference-doc option for docx/pptx/odt. If I place a reference.docx in my data dir (../AppData/Roaming/pandoc), it picks it up automatically and it works (but it's not so obvious for users, and people might want different templates per book). This helped me fix a lot of my issues. I added a transform to replace all the
<center>
with######
and I set the reference template to set the heading 6 style to be centered, which works great for my* * *
scene breakers, and I could set my styles for each heading and body text, etc..!I think it would be great if we could generate manuscripts with manuskript which follows the standard manuscript format. With the reference.docx/reference.odt file, and a few regexp tricks, I can now achieve that. All I'd need after an export is to add the header which shows page numbers and do a page break on each chapter (note: the
<center> #
issue and the triple apostrophe not being recognized for verbatim are remaining which makes manuskript's HTML export break as I tailor the markdown for pandoc).