Start using AsciiDoc with the AsciiDocFX editor. That is similar to MarkDown text format files. The AsciiDocFX editor comes with an automatic (real-time) preview, so it very easy to see how your content will look like, while you are typing it. Which should cover most, if not all, of your needs to alter the layout afterwards. But if you still find a need to do so, you can alter the default CSS style sheet that editors like AsciiDocFX use to render the content as preview.-Shades
Thanks.
I had a quick look. Preview feature worked well, but I couldn’t set up a colour scheme to suit me, so that rules it out.
Also doubt preview as a solution. Goes back to the days of print and proofing marks (and preview would have been wonderful then). The problem is that it works by splitting writing and reading modes, and this has an impact on focus and efficiency. Like many writers, I typically write first, check and format later. Putting headers in wouldn’t affect focus, but putting in a bullet list would - especially if there was a need to check the preview to see if it achieved the desired appearance. Also formatting is easier done with just a mouse - at least for me.
There’s then the assumption that post-writing mode is reading. In some cases it might be, but with the zkn notes it isn’t really. I design the note format to help direct my attention appropriately when I next look at the note. But when I do, I am as likely to be in edit/change mode as in read - and that means not wanting to switch between panes.
Text files like MarkDown and AsciiDoc have also the advantage that these are very easy to search through by any and all types of search engine software (local or remote). These documents are also easy to store in any database of your choosing or to serve up as (internal) web content, if you so desire. With RTF and other document types created by word processing software, such options are very limited in the best case scenarios to non-existent.
Depending on RTF and/or other document types, will bite you in the long run, in ways you'll never expected. -Shades
I accept text files are easier to search and plaintext is easier to manipulate (not so sure about markdown etc - it isn’t, for instance, recognised by docfetcher as a separate file type which means text shown includes formatting).
I also accept that there are risks in using RTFs, or other more complex document types, but here I have to weigh the risk against the efficiency gains I have from using them.
And I have to be aware that many of my sources are held in document formats of all types, including PDFs, doc/docx and ebooks, as well as informational image files. And all these I suspect are more likely to give problems than RTFs. As it is, I use text files where they are sufficient and RTFs where I need the formatting.