The proliferation of markdown forks is a mess. Can't you just use something better to begin with, like asciidoc? I think you can likely just use existing asciidoc mechanisms to support the same thing and then existing editors will still be usable.
NovelWriter 1.0 – A markdown-like editor for writing novels
31–40 of 277 posts
Re: NovelWriter 1.0 – A markdown-like editor for writing novels
#32is author here? - Is it suitable for non-technical writers? is there any feedback on them baing able to use markdown, @pov tags etc? - did you try some commercial competitors? How would you compare? I understand scrivener is one popular option
I'm actually support for similar tagging to my own personal editor (for my first two novels I used a mix of Google Docs (yes, really) and Libre Office; using my own editor for my third). I'm definitively going to steal ideas from this one...
I don't think using those kind of features requires any technical understanding at all. If anything, people are used to doing "ad hoc" tagging with easily searchable strings.
Re: NovelWriter 1.0 – A markdown-like editor for writing novels
#33Outside of the more technically inclined; Does anyone who is a long-form (novel) writer actually use markdown? Outside of blogging, which it was invented for and makes total sense for syntax conversion of free formed text to html is there any real use for it? Obviously you don't have to use it if you don't want to, but it sort of feels odd to me that all these developers making writing/notes apps that neglect rich te…
I'm close to 60,000 words into my latest novel and I'm writing in Ulysses using Markdown. Novels, in particular, rarely need more than headings and occasional italics or boldface.
That's the kind of need for text manipulation I would expect of a typical writer. Hence why bother with markdown at all (unless it's the only thing available). Rich text is a much cleaner solution for that. Markdown really shines when it comes to text that has to be formatted just so for web layout. e.g. tables, bullets, multi-headings and linking.
Re: NovelWriter 1.0 – A markdown-like editor for writing novels
#34It would be amazing if it fixed your grammar, removed cliches, fixed wordiness, activated passive language, swapped repeated words, fixed my run on sentences, overall just fixed my englitch. #featurerequest
You'd need a human editor to do all that. Automatically fixing run-on sentences and removing repeated words is possible. Activating passive sentences is challenging; Grammarly gets it wrong all the time, in my experience. Replacing cliches and fixing wordiness would be very challenging without deep linguistic and cultural knowledge.
>You'd need a human editor to do all that. Automatically fixing run-on sentences and removing repeated words is possible. Activating passive sentences is challenging; Grammarly gets it wrong all the time, in my experience. Replacing cliches and fixing wordiness would be very challenging without deep linguistic and cultural knowledge.
Well I don't know why I was downvoted so heavily. I dont disagree.
My goal isn't so much to write a novel but rather improve upon my englitch. Now I have chosen writing a novel in order to improve but I dont know where I went wrong.
I would love a human editor but that costs $. I doubt anyone is giving me a dime for my book. I don't have >$1000 to get my book edited.
Of which any hired editor will just shoot themselves.
Re: NovelWriter 1.0 – A markdown-like editor for writing novels
#35Earlier quoted context omitted.
I'm close to 60,000 words into my latest novel and I'm writing in Ulysses using Markdown. Novels, in particular, rarely need more than headings and occasional italics or boldface.
That's the kind of need for text manipulation I would expect of a typical writer. Hence why bother with markdown at all (unless it's the only thing available). Rich text is a much cleaner solution for that. Markdown really shines when it comes to text that has to be formatted just so for web layout. e.g. tables, bullets, multi-headings and linking.
Because it's not a bother. It's pretty much just plain text.
And having it as plain text means adding your own special annotations is easy. E.g. I'm writing my third novel in my own editor using Markdown, and key for me was that it was easy to write small little scripts to e.g. process front-matter with similar "@pov" tags etc. to let me trivially cross-reference things.
Re: NovelWriter 1.0 – A markdown-like editor for writing novels
#36Outside of the more technically inclined; Does anyone who is a long-form (novel) writer actually use markdown? Outside of blogging, which it was invented for and makes total sense for syntax conversion of free formed text to html is there any real use for it? Obviously you don't have to use it if you don't want to, but it sort of feels odd to me that all these developers making writing/notes apps that neglect rich te…
I'm close to 60,000 words into my latest novel and I'm writing in Ulysses using Markdown. Novels, in particular, rarely need more than headings and occasional italics or boldface.
how do you convert from markdown to standard manuscript format?
starting to write in markdown or even plain text is fine, but once the first draft is submitted to the editor or sent to a publisher for consideration it usually needs to be a word or rtf document in standard manuscript format.
once converted i am stuck using libreoffice to revise and edit the story.
i found tools that convert from markdown to ODF (which i can then load and export as word) but i have not found any way to apply a standard manuscript style in the conversion process.
without that i'd have to manually reformat the document each time i want to submit a new revision.
Re: NovelWriter 1.0 – A markdown-like editor for writing novels
#37I am writing a novel in Markdown using Emacs. For most of the novel writing process Markdown is enough. I have been toying with the idea of tweaking the markdown like this novelWriter does, mostly because I constantly find myself wanting to annotate my text, or temporarily mark out, but not delete, blocks of text.
Re: NovelWriter 1.0 – A markdown-like editor for writing novels
#38Earlier quoted context omitted.
Maybe ghostwriter [0] is what you are looking for? [0] http://wereturtle.github.io/ghostwriter/
I just found typora[0] and Emacs "M-x markdown-toggle-markup-hiding" :) [0] https://typora.io/
> https://support.typora.io/License-Agreement/
EULA?! Thanks, but NO.
P.S. ghtostwriter is fully free & open-source, instead of proprietary Typora.
Re: NovelWriter 1.0 – A markdown-like editor for writing novels
#39Outside of the more technically inclined; Does anyone who is a long-form (novel) writer actually use markdown? Outside of blogging, which it was invented for and makes total sense for syntax conversion of free formed text to html is there any real use for it? Obviously you don't have to use it if you don't want to, but it sort of feels odd to me that all these developers making writing/notes apps that neglect rich te…
I'm using Papyrus Autor because I write in German [1,2]. It's expensive but superior to everything else for the German language. They're expanding to English users, but only offer a super-expensive subscription model for them [3]. If I wrote novels in English, I'd probably use Scrivener [4].
I'm very familiar with markdown, pandoc, and LaTeX, but none of these are relevant or important for writing novels. As a novelist, you need grammar and style correction features, pinboards for ideas, databases for characters and sources form the Net, easy snip management, advanced typography (especially quote correction and automatic quote conversion), name generators, non-continuous selections, selection by font, search & replace of formatting, automatic backups over network and advanced data integrity features, excellent ebook and PDF export, different views for writing/editing/correcting, etc.
[1] https://www.papyrus.de/ [2] https://talumriel.de/ [3] https://www.papyrusauthor.com/ [4] https://www.literatureandlatte.com/scrivener/overview
Re: NovelWriter 1.0 – A markdown-like editor for writing novels
#40Earlier quoted context omitted.
I'm close to 60,000 words into my latest novel and I'm writing in Ulysses using Markdown. Novels, in particular, rarely need more than headings and occasional italics or boldface.
That's the kind of need for text manipulation I would expect of a typical writer. Hence why bother with markdown at all (unless it's the only thing available). Rich text is a much cleaner solution for that. Markdown really shines when it comes to text that has to be formatted just so for web layout. e.g. tables, bullets, multi-headings and linking.
Markdown is "rich text". What distinction are you trying to draw here?