Scrivener 3 is on the way…
< Next Topic | Back to topic list | Previous Topic >
Pages: ‹ First < 9 10 11 12 13 14 15 16 >
Posted by Anthony
Dec 2, 2017 at 09:43 PM
OS: Win
You can write a letter with Word not a book. But it is a standard still largely accepted (to be imported in Pro DTP software).
Let me mention a weak point of Scrivener and a good point of Writing Outliner as Word Add-on.
If you need to write a technical document with equations Scrivener even in its v.3 - for what I read on the Manual - shows its limitations. Mathtype Equations once exported, for instance in RTF, cannot be edited: they are turned into images.
In the Win version (as compared to Mac version) it is still worse than that, because images are very low quality, and they are not always placed correctly in the baseline as they should.
The use of Latex with Scrivener is not easy and suffers some limitations.
WO simulates a Scrivener-like environment. Math equations and Bblio-add ons, which are quite necessary for most technical-academic writing, work normally. Unfortunately it saves in a proprietary format and the development, while promised in the blog homepage, seems continually delayed.
Posted by Franz Grieser
Dec 2, 2017 at 11:35 PM
Anthony wrote:
>You can write a letter with Word not a book. But it is a standard still
>largely accepted (to be imported in Pro DTP software).
Yes, you can write books in Word. I wrote more than 10 books in Word. Four of them were even typeset in Word (not by me, I’d never use Word for that).
But I wrote each chapter in a separate DOC file.
Posted by tightbeam
Dec 3, 2017 at 12:37 PM
Anthony wrote:
>>You can write a letter with Word not a book. But it is a standard still
>>largely accepted (to be imported in Pro DTP software).
Of the 200+ authors signed to my publishing company, all but four or five wrote their books in Word. I’d wager that the majority of books are written in Word.
Posted by Dr Andus
Dec 3, 2017 at 01:25 PM
Graham Rhind wrote:
Indeed, and since you suggested it I have been looking into it. There
>are lots of reports online from users about instability and crashes when
>the master file gets too large, even in Word 2016, and it did crash on
>me already today when trying just with smaller files. As far as I can
>see, every time I want to create/insert/merge or split I have to expand
>all the sub-documents. So that means having to open (wait wait wait)
>then edit (in a horrible view - Outline view is not exactly
>user-friendly) a 3000 plus page 110 plus mB document, which is exactly
>what I want to avoid. I can’t see an easy way to nest sub-documents.
>There’s no drag and drop should I need to re-order the documents as far
>as I can see. There’s no way to add flags or tags to, for example, show
>which files have certain changes made to them. There’s no way to assign
>for each sub-document how the link to the next document is to be created
>(page break, return, line break ...); and so on.
Graham,
May I ask why this document needs to end up as an MS Word file? Is it your choice or an external requirement?
My understanding is that MS Word is a software to make typesetting/desktop publishing (what is commonly referred to as “formatting”) available to non-specialists.
But as it also allows you to write the document from scratch or edit existing documents, these lines between writing, editing, and typesetting (before it is consumed as a ‘published’ document in the form of a .docx file, PDF file, some other digital file, or as a printed doc) become blurred.
Since Word is an entry-level typesetting software, my experiences confirm yours in that it is only suitable for relatively small and simple documents without too much complex formatting and tables and documents.
I have found it unsuitable for dealing with 300+ page documents (with multiple chapters, EndNote references, multiple images and tables, headings, TOC etc.), so I can’t image trying to use it for 3000+ page docs.
It would suggest to me that you might need a more professional typesetting (desktop publishing) software, if that’s the need. I’ve never used one, but I presume that’s what the likes of Adobe InCopy and InDesign do.
However, if you’re only using Word for writing and organising a large document, and want the ability to have meta-comments on the process and the overall document itself, then there are plenty of other options.
You could either look for one software that can do it all within (such as Scrivener), or use other software to use as an overlay by linking from within that software to smaller chunks of Word files, if you must use Word.
ConnectedText (whether from within a CT topic or CT’s Outliner) comes to mind, but there must be other outliners that allow you to link to Word files. And then it becomes a matter of organising, annotating etc. those links to smaller Word files.
This inadequacy of Word was one of the reasons that drove me to a Markdown-based writing process in plain text (in WriteMonkey and Gingko). LaTeX is another option, but I didn’t need that complexity, plus I also need a Word file as a final output, due to it being the standard required by publishers in my field (unfortunately).
I found writing in plain text with Markdown in WriteMonkey hugely liberating, as it freed me from the obsession fostered by Word to keep formatting the document as I write, only to discover that Word regularly messed it up, and then I felt compelled to be fixing the look of the document, instead of focusing on the content and the writing process (not to mention that much of the formatted text ended up being edited out, so it was a waste of time to format it in the first place).
These days I do all my writing outside of Word, and only export stuff into Word at the very latest moment, for the very final act of formatting (i.e. typesetting), before sending it out.
Posted by Stephen Zeoli
Dec 3, 2017 at 02:01 PM
Those who are writing hefty technical tomes on a Mac would do well to check out Mellel.
It’s not for people who want to write with Markdown, but it appears to have a full feature set and claims to handle long, long texts without any crashes or issues.
Steve Z.