![]() ![]() Simply save your document in Writer as an ODT (writer's native format) and open that file (do not "insert from file") in Word.Īt least that works on the file I made for testing (without Scrivener and Zotero involved). Most of the procedures I described above fall back onto default settings. Edit: Sorry, I missed one essential part: Arabic numerals are desired for endnote numbering. To examine this, we would need your default Word template, and also your document as exported to ".odt" (or some dummy file created in Scrivener which displays the issue). The source of the issue may be settings for new Word documents, settings/styles for Zotero notes, or some difference in notes handling between Scrivener and Writer (ODF is not Scrivener's native file format). Still, numbering is just like in the source.ĭid you try to export from Scrivener to a Word document? (Zotero also works with MS Office.) Keeps the flow of existing text but loses structure. notes were converted to text body, placed inline as they appeared on the page. Copied everything from a Writer window and pasted into Word.Saved from Writer to a Word ".doc" file, and opened it in Word.New notes insert nicely, renumbering everything and keeping numbering style. Inserted again, this time into an existing document with footnotes and endnotes.Inserted the same file into an empty document in Word.The only change is that endnotes are moved from a separate page to just after body text on the final page. Footnotes and endnotes maintain numbering. Kept default numbering styles, so footnotes have arabic numerals and endnotes are with lowercase roman. I created a simple document with footnotes and endnotes. Testing with Word 2016 and Writer 4.1.3 (missing the initial Scrivener step of content creation and the Zotero finalizing), I cannot replicate the behaviour as described. When I export to Word, they become roman numerals.You have the additional step of "Scrivener", which may complicate things. Tdenmead wrote:Did you solve this problem? I have the same one.
0 Comments
Leave a Reply. |