I'm excited for the future of this project! Developed by #paligo
As far as I know the current source formatting is a custom format. It is quite efficient as only few characters are used to mark a page ending or a colored capital. It can be improved in ways for new use-cases. Some suggestions for improvements on the current syntax: - Ability to add commen...
@es0mhi @david_megginson Besides plain TeX, I also use DocBook XML with xslTNG stylesheets, and ndw who made these stylesheets is also editor of DocBook spec, had made an emacs library to dump XML representation of org-mode document, which might be interests to you https://github.com/ndw/org-to-xml
This opposition of org-mode vs. (LaTeX, SGML) XML in publishing is something that resonates very strongly with me - though I'm afraid it's hard for many org users to understand.
I do almost all of my daily work in org-mode, but whenever I start a writing project that needs to be published, I use XML. There are all kinds of reasons for this, some very specific to my case of academic writing, where the handling of citations, footnotes and bibliography can get very complex and specific. But I feel that in the end it comes down to something much simpler.
For decades I have been using docbook-xml for all my writing projects, starting with drafting in asciidoc (and this co-existence of asciidoc and org-mode as two "markdown" dialects still leaves me unsatisfied). The deeper reasons however seem to be that in org-mode you start designing your text from an outline. For me, this is the wrong approach, as I need to write a text as a stream-of-consciousness, adding paragraph after paragraph, and only later get to an outline. The way I'm used to using org-mode seems to make this impossible for me.
fwiw, I used #DocBook #SGML in #Emacs to generate LaTeX/LilyPond, even when Macmillan demanded I submit MSWord¹ docs, I'd just emit them as an output! Mind you, that was last century, but I'd still do it that way today, if I had to.
___
¹ I call those apps "font painters', or WYSIAYG (what you see is ALL you get
OK, so my fantasy #worldbuilding / #writing project notes live in a massive #Scrivener project. 164,686 words.
Now, *editing* the thing in Scrivenever is fine and good and I have no problems coming up with new stuff and just putting it there. However...!
The export process is kinda janky. At current state I can't export this to HTML, for starters. If I want a usable PDF document out of this (compiles into a 344 page document, half of which isn't even formatted right because I'm lazy and it looks OK in Scrivener side), I need to compile it into a LaTeX file via MultiMarkDown. Involves a little bit of hand-fiddling too.
It's *hhhella slow*. It's *janky*.
I really would like this to be a much more easily editable and compilable thing. With fully text-based markdown(esque) input, able to export to static HTML and PDF (via LaTeX, preferably).
Lots of options to choose from. I'm currently looking investigating #DocBook solutions. Am I mad? ...I am mad, aren't I?
Nico Rikken
Niklas Rosenqvist
Norm Tovey-Walsh
LdBeth
es0mhi
teledyn 𓂀
Yesterday's Rose