Okay, so here comes a hole in my "#markdown as #WordProcessor" strategy: sharing #documents.
I got .md files that I need to convert into #PDF, and it needs to be done on #Android.
Sure, the markdown editor supports printing to PDF, but it doesn't allow templating, so there is little to no margins, no font size control, or anything that's necessary to make a document readable through formatting.
Has anyone solved this problem, beyond using #pandoc with #termux?
Since I discovered Markdown and Pandoc, Vim is my favorite word processor!
As a book translator I spend my days working with texts. Also it means I have to deal with user-hostile file formats like docx. Because editors, designers...
My long-time friend was LibreOffice. I used it since version 5.something. It's a great alternative to Microsoft Office. But in other respects you have to put up with this huge bulky piece of legacy code that probably still has Sun engineers' souls trapped inside.
And I want to boast with my little personal victory. I have finally finished a book fully typed in #vim and #emacs (for the glory of both editors) in Markdown format and later processed via #pandoc to docx (with all required styles and formatting). I used LibreOffice only on the last stage to iron out some quirks and typos. It seems this workflow works.
Which means I don't have to use this huge and unhandy LibreOffice suite every day.
Now I want to figure out if I can use org format for my translations or should I stay with Markdown. Because it seems I like it here with Emacs.
I decided to go with the landscape pdf option. Students' chromebooks can't read epubs natively, and it would take a while for IT to okay an extension (and I prefer to avoid extensions).
Also, #pandoc didn't add inter-document links when converting from #TexLatex to epub.* This is a "choose your own adventure" story, so jumping around the doc is 100% necessary.
End of day, a roughly 6x9 inch landscape pdf will probably work best.
* to be fair, I spent zero time looking for solution
#pandoc release 3.6.4
• The `--citeproc` option now automatically disables the `citations` extension in the writer
• Better error reporting when YAML block parsing fails in Markdown
• Fewer space characters when writing Markdown lists
• Many other fixes and improvements
Turning 80-ish (usa letter-sized) pages of reading into Google Slides so students can read more comfortably on their Chromebooks.
I really wish I could just use an HTML page, but last I looked Google Drive won't display HTML files as web pages.
I suppose I could make it 8.5x5.5 landscape PDF, but not sure how well that would work on their screens.
Any thoughts?
(Reading started in #TexLatex, so I can #pandoc it into just about anything.)
TIL there is an account posting about #Pandoc in the #Fediverse: @pandoc
Thanks to it I learned about Pandoc Templates: https://pandoc-templates.org/
YAY! My Pandoc Manuscript template made it into this Pandoc template directory! https://pandoc-templates.org/ #Pandoc #Markdown
I think any large interesting program you might write could well have an embedded language within it, in which the user can write stuff that is just as good, and just as deep as built-in functionality. You want this. It’s a thing that makes programs compelling.
In #Vim, that embedded language is #VimScript. In #emacs, that’s #elisp (which in fact, I think the whole thing is written in). In a #smalltalk environment, you control the entire environment with Smalltalk, just as elisp applies to Emacs. For many, many things, that language is #lua ( #NeoVim, many games, #pandoc, #redis, this list goes on).
I used to think there were really two reasonable mainstream languages you could use here: #Python or #javascript. Between those two, for a long time I felt that JavaScript was the winner. I think that has changed as Python has gotten faster, more powerful, and better known. But also, I think the answer might actually not be either of these two. It might be Lua. Lua is simpler and faster than either JavaScript or Python. It’s more embeddable. It’s designed specifically for this purpose. It’s in much wider use as an embedded scripting language. I don’t want Lua to be the answer. I like Python better. But I think Lua actually is the right answer.
The site https://pandoc-templates.org/ features a list of open source pandoc templates and provides a preview image for each template.
Created by Pascal Wagner.
#pandoc #template
My Arch Linux updates 216 packages again.
That's right, we are updating #Pandoc
@SimonRoyHughes Ah, that makes sense since most people today would probably just export to PDF.
I like EPUB since it lets me export to markdown to wikicode for personal annotations in #mediawiki via #pandoc.
If this were academia, I would suggest a LaTeX or TeXmacs source with macros that could handle the annotations and let readers export their own format to their liking.
Congratulations on assembling your books, though!
Level up your project with our latest tutorial, we show you how to us Pandoc to convert your HTML pages into a single Markdown file ready for AI training 
And learn how to install Pandoc on an Upsun project—whether you prefer a quick shell script or the flexible composable image approach—dive into our tutorial now 
https://brnw.ch/21wQV2l
mes blogs sont faits avec #orgmodeToGemini un outil maison qui transforme mes pages au format orgmode en un blog html statique naviguable par tags. Plusse d'infos dans le readme.
@nonlinear Not sure I get the whole question, but for me (as casual writer or book composer) authoring in a simple "pivot format" such as Markdown/Djot and managing the work under #git (to track my changes, etc.) are key points. At the moment I am using #SILE to get a PDF for print. But having a pivot format is also a key too towards having HTML, ePub or whatever if I eventually want them, without having to recompose too much (and yes #pandoc is then in the mix)
Does anyone have a tool they prefer for #writing printable #books, committing it in #git, and rendering it as static html site (or maybe just good navigation in #codeberg itself), and also rendering a nice #pdf with table of contents, footers, indices, etc.? Something like #mdbook, #bookdown, #pandoc, or the like? I'm flexible with the exact syntax of the docs. I'm using mdbook with mdbook-pdf at the moment. I haven't tried mdbook-latex yet. (Using something like jinja would be nice.)
Contribution by Rodrigo Dias Correa: documento, a #LuaFilter that extracts documentation from a C header file.
https://codeberg.org/rodrigo-dc/documento.git
Feedback can be given in this thread:
