Hi, I am trying to compile an academic report to odt, but the section headings don’t appear as headings when I open the compiled odt-file in Libre Office. The section headings are text formatted as ‘headings’ or ‘sub-headings’ via the ‘apply preset’ dialogue in ‘formatting’ in Scrivener. Compiling to .docx or .rtf equally doesn’t work.
If I compile to pdf, the created file does have headings as bookmarks with which I can jump to the respective sections. However, these are not taken from the scrivener text lines I had formatted as headings. Instead, they are taken from the titles of the subdocuments (files?) of the scrivener document that I compiled. Sorry, I hope I am not mixing up the terminology here.
So maybe I have not well understood how to designate text to be formatted as headings? But nevertheless, the issue remains that I don’t manage to get any headings in a file that I can then work on in Libre Office - which I mainly need to convert the Scannable Cite-Citations into real citations with Zotero.
As recommended elsewhere, I have tried toggling on/off the enhanced docx converters (in Scriv prefs) without effect.
PS: sorry, I am still on Scrivener2. My Mac is running Sierra (10.12.6) and I am afraid updating to Scrivener3 would be too much for the old horse…
I believe what you’re looking for is a styled result from the compiled document, but you won’t find that anywhere in Scrivener v2, unfortunately. What you are referring to as a “preset” is only that, just a storage for formatting that can be applied to text. It is not a style, where by definition the text then becomes identified by the style you apply to it, in addition to any formatting that is established by that style.
You can verify this simply by creating a test preset and applying it to two paragraphs, then changing one paragraph’s formatting, and using the menu command to update the preset’s formatting from the selection. The other paragraph will not change, as we would expect it to if it were styled.
The old-school method of getting a styled ODT/DOCX file is described in this post. It’s really the same thing you would do for any document you receive that is lacking styles, and needs to be cleaned up. What we can do to make things easier for ourselves is make sure presets are very distinct from one another, even if artificially so.
As noted further down in that linked thread, proper style support was added to the software in v3.
Amber, thank you very much! This old-school method could actually do the trick in my case, given that I only have two levels of headings.
But how comes that the compiled pdf had bookmarks and not the .odt/.docx/.rtf-files?
With the limitations of Scrivener2 that you mention, I should probably not expect to be able to insert internal links in the Scrivener text, right? I am referring to references like “for an extended discussion of the issue cf. section 3.1”, where this number would be automatically assigned. That was the next task on my mind… But maybe I’ll go the old-school way here as well and assign these numbers manually, hoping I will not have to change section numbering again…
Sorry, I misunderstood your use of the word “bookmark” before, to be a way of describing how style-based headings are listed in your word processor’s heading navigation tool.
If you’re referring to the anchor points you can insert wherever, and link to from other areas of the text as a cross-reference, Scrivener should in fact be inserting those if you tell it to. Refer to §24.11, where the Formatting compile option pane is discussed, and on page 376 you’ll find the setting to “Include in RTF bookmarks” (which conveys through to other word processing formats that support anchor points).
As far as I can tell, Scrivener 3 doesn’t require more power to run, so you’re fine upgrading if you want to. It is, however, a big change when it comes to how compile works. I wouldn’t recommend upgrading if you don’t have time to throw out all you know about compiling and start over.
It is for some people. We’ve both seen people loosing their minds over the changes, having mastered v2’s compile, but cannot wrap their heads around the extra layer of abstraction introduced in v3. Better to not under-sell how big an adjustment it is and frustrate someone on deadline.
