Are you surprised by those results? It seems that #AsciiDoc and #reStructuredText are (way) less popular than I thought, and that #orgmode is way more popular than I expected.
Of course, we should take those results with a grain of salt, as I assume many of my followers are #Emacs users. 😀
For historical reasons, I mostly use #Markdown for my writing, although I've started to use #AsciiDoc (through #AsciiDoctor) more and more these days.
One of the things I #amWriting is intended to be in a more “playwright” style, so I've been looking around for stuff more focused on #playwriting (for either theater or screen, I'm not picky at the moment.).
Playing around with #typst it’s like a dream come true so far. I edit in #emacs, changes show up in the generated pdf very quickly with the command line tool in watch mode. No fussing around with ponderous toolchains. Next up converting a medium size doc with a lot of equations from #asciidoc.
Since the input for this module is a standard #Asciidoc document, “weaving” isn't strictly necessary (a processor like #Asciidoctor can output a reasonable approximation of the final HTML without many issues), but we do some transformation to normalize code block titles and add cross reference hyperlinks where appropriate. These cross references now have a default styling that fits better with the default stylesheet used by Asciidoctor.
Is there a way of getting Pandoc to detect a style or font in a DOCX file?
I'm specifically thinking of in-line preformatted text, so converting (say) a Source Code character style in Word to backticks for #Markdown or #AsciiDoc. Or a different paragraph style to a triple-backtick (or [source] for AsciiDoc) block.
Could this be scripted with Pandoc's Lua engine?
Or is there a better tool to do DOCX to AsciiDoc than pandoc?
#NeoVim update. The discovery of registers has made me very happy. Macros are saving me a lot of time!
I'm slowly improving my speed with movements. It's also forcing me to address some bad typing habits of mine.
#AsciiDoc support using vim-asciidoctor is better than the built-in syntax highlighting, but it's still mediocre and breaks. In an ideal world there would be a #Treesitter parser for it, but I don't know if I have the energy/skill to work on that.
"Nimm doch Markdown", haben sie gesagt.
"Das ist total einfach", haben sie gesagt.
"Damit arbeitet man ganz flott", haben sie gesagt.
"Das funktioniert in ganz vielen Editoren", haben sie gesagt.
@Mela und deswegen mag ich #AsciiDoc lieber. Zusammen mit #Antora (Docs-as-Code) lassen sich so ganze Dokumentationen erstellen und mit #Pandoc kann man das auch in fast beliebige Ausgabeformate umwandeln...
P.S.: und es wird direkt von GitLab unterstützt...
I'm in the early stages of writing some #opensource technical documentation. It's just some notes in #markdown right now but I'll probably pivot to #ASCIIDoc before releasing it. I need to simulate an LED display in an #SVG: basically a fancy 7 segment plus some small status icons.
I could make each SVG of the display manually, but it seems like I should be able to use a #macro of some sort to accomplish the SVG generation. Has anyone else done something like this #AskFedi
Suppose I was thinking about writing #manpages for the command-line tools I build, but I don’t want to learn a 50 year old typesetting language (#troff) to do that.
What are my options? #Asciidoc? What would you use? What do you use?
I looked into #Pandoc Markdown to man conversion, and it seemed to suck.
Is there anywhere a #wysiwyg editor for #asciidoc ?
Like we had in the olden days for html.
You type where see the result but you still can edit the underlying pure asciidoc, if wanted.
More #Psion documentation fun, this time with headings/sections.
Psion made much of the SIBO/EPOC16 documentation in Microsoft Word. Looking at a .DOC file, I've realised that they often skipped "Heading 3", going straight from Heading 2 to Heading 4. They only used Heading 3 in specific circumstances, such as function and syscall names.
Earlier today, after some hunting, I found the text version of the #OPL Programming Manual that came with the Series 3a. So, while I was sitting in front of the TV this evening, I thought I'd start converting it to #AsciiDoc.
First chapter is pretty much done.
I think (hope) I've got a paper copy in a box somewhere, so I can compare it to the original.
A graça de usar umas máquinas mais velhas pra rodar #Linux ou algum #BSD está na exploração dos limites e tipos de softwares viáveis dentro deles. Programas para modo texto, concentração de atividades em editores (como #Emacs), linguagens de marcação para escrever documentos (como #LaTeX e #AsciiDoc etc. O desafio de montar um ambiente leve, elegante e, ao mesmo tempo, poderoso e muito funcional, é bastante satisfatório.