two things in export

Scrivener Scrivener for macOS
1

The first is a very minor UI thing. If you are exporting and click on an existing file name to overwrite a previous export, and you have the interface set to show the file extensions, the file name is changed correctly but the number of characters hilighted stays the same, which looks rather odd when the file name is a different length than “Untitled”. It appears to set the hilight correctly if file extensions are not shown.

The second is in the interface between Scrivener and MMD, but definitely on the Scrivener side. The one setting on the “Text Options” screen in export that applies to both the normal and MMD export (namely, what to put between scene files) doesn’t show up in an MMD exported file. I set it and exported my novel to LaTeX, then after I printed the whole thing I noticed that I had nothing separating scenes! If Scrivener could slide those into the text it hands to MMD, that would be fantastic.

Thanks for letting us play with an update :slight_smile:

2

Nothing to see here… Move along, move along. :slight_smile:

This is nothing to do with Scrivener. This is entirely to do with the Apple save panel, which acts as it will.

Nope, this isn’t a bug. The scene separators have no effect on MMD export, and neither should they - they would not be true MMD syntax. If you want scene separators between scenes exported via MMD, you have to use an XSLT file that supports that. I believe Fletcher has written one for standard manuscript format that does just that. But this is 100% intended behaviour.

Best,
Keith

3

Ok. I hadn’t checked any other apps, my mistake :slight_smile:

If it’s intended then it’s intended, but about them not being correct syntax, if I put the exact same thing at the end of a scene file it is handled correctly in the MMD portion of the export. That’s why I didn’t notice it earlier - I had forgotten about that feature and was putting my scene separator right in the file, which meant I had to make sure not to forget it, and also to remove it if the next scene started a chapter because otherwise it looked goofy.

Out of curiosity, how would MMD know where scenes begin and end for an appropriate XSLT to chew on if nothing is inserted between them by Scrivener? Or does MMD actually get all of the individual files handed to it instead of the single assembled file that I assumed it got?

4

Well, in the case of the manuscript sffms class, the XSLT takes the scene title generated by Scrivener, and turns it into:

\newscene

…which informs the class to put a centred hash mark just as the default Scrivener export does. So to enable this, you’ll need to turn titles on in export for your documents.

5

That’s handy. I wonder if any of the others do that too. Like the 6x9 book :slight_smile:

I never thought of turning on titles doing anything other than printing the titles as a header.

I will have to investigate further…

6

Ok, now that I’m thinking about this again, I did a few test exports. For the sffms export, MMD knows that stuff one level below “chapter” takes a \newscene - that’s cool.

For the memoir-based ones (memoir, 2 sided, and the 6x9 book formats) stuff one level below “chapter” gets a \section command with the title of the file. Memoir doesn’t understand \newscene either, if I manually type it in.

Is there a workaround so that I can get a scene separator when exporting to 6x9 book for lulu, without the error-prone and tedious step of typing it into each file that needs it? The file separator character used for RTF export would be perfect if it were used on MMD exports too (or had the option to be used), since I know that memoir will be used for things requiring both chapters and sections and can’t assume the way sffms can. I’d be perfectly ok with typing out the \centerline{#} that is all I want in that field, and I imagine other people using the LaTeX export wouldn’t find that too onerous either.

7

I think this is one for Fletcher to field, being about MMD -> LaTeX…

8

I have not tested this, but this should actually be pretty simple to do. I would just create a copy of the XSLT responsible for making the 6x9 book, and add the following code to it:

[code] <xsl:template match=“h3”>
xsl:text\centerline{#}</xsl:text>
<xsl:value-of select="$newline"/>
<xsl:value-of select="$newline"/>
</xsl:template>

<xsl:template match="h4">
	<xsl:text>\centerline{\#}</xsl:text>
	<xsl:value-of select="$newline"/>
	<xsl:value-of select="$newline"/>
</xsl:template>

<xsl:template match="h5">
	<xsl:text>\centerline{\#}</xsl:text>
	<xsl:value-of select="$newline"/>
	<xsl:value-of select="$newline"/>
</xsl:template>

<xsl:template match="h6">
	<xsl:text>\centerline{\#}</xsl:text>
	<xsl:value-of select="$newline"/>
	<xsl:value-of select="$newline"/>
</xsl:template>[/code]

There might be a more optimised way of doing that, like match=“h3|4|5|6”, or something. I don’t know XSLT that well. Anyway, that will just insert the LaTeX code you specified, wherever it encounters a new document deeper than the chapter level.

The last step would be visiting the MultiMarkdown settings in Scrivener, and adding a new header meta-data, “XSLT File”, and supplying the name of the modified 6x9 XSLT file.

9

ahaha! Thanks for the pointer AmberV. I don’t know much of anything about XSLT, so I shall do some research to get the customizations exactly right. But now, I have an idea of where I’m going :slight_smile: