Verflixt und zugenäht noch eins …

Ich möchte doch nur, dass #pacman auf einem Schlag alle #haskell-Pakete entfernt. Aber offensichtlich bin ich unfähig, den richtigen Befehl einzugeben. Zumal sich #fish beim * immer als zickige Diva aufführt. Aber selbst beim Wechsel zu #bash beschwert sich pacman, nichts finden zu können.

sudo pacman -Rns haskell-\*
sudo pacman -Rns haskell\*

sind zumindest falsch. Mich nervt aber auch, dass haskell bei der Installation von #pandoc aufs System kam und "sudo pacman -Rns pandoc-cli" zwar einige haskell-Pakete entfernte, aber eben nicht alle. #Arch #ArchLinux

Hmmm, unexpected Pandoc issue: when converting from ODT to HTML, single words in italics are correctly carried over, but entire paragraphs in italics are not.

No idea why; the content.xml inside the .odt assigns each paragraph its own style inside the <office:automatic-styles> tag, and the styles for the italicised paragraphs correctly say <style:text-properties fo:font-style="italic" and all that. But Pandoc converts them into <p> elements without a style, and no <i> or <em> elements.

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.

#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

https://github.com/jgm/pandoc/releases/tag/3.6.4

Horay, I've successfully converted a markdown.file into a html-file via @pandoc !

TeXLive 2024 was frozen a few days ago, and this always leads to issues with the pandoc/latex Docker images. We have pushed new images for the currently supported pandoc versions 3.5 and 3.6.3, and are in the process of updating 3.2.1, too.
#pandoc #docker

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

I'm happy to announce #notesbash v1.1.0 ! New features include:
- A customizable export system to export your #markdown #notes using e.g. #pandoc
- a preview feature using the new term-open script, a #xdg-open like utility, but for the terminal
- a `.desktop` file for your favorite app-launcher
- completion scripts for #bash and #zsh
- the default extension set in the config is now used for all notes
https://codeberg.org/carmatani/notesbash/releases/tag/v1.1.0
#opensource #tui #terminal #foss

@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!

Das #Pandoc-Plugin ergänzt #Obsidian um einige wichtige Exportfunktionen. Die Installation ist etwas ungewöhnlich und erfordert zudem ein wenig Geduld ...

#ObsidianMD #PKM

https://www.mathoi.at/2025/03/03/das-pandoc-plugin-fuer-obsidian/

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:

https://github.com/jgm/pandoc/discussions/10602

pandoc release 3.6.3! This is a bugfix release, but it comes with minor behavior changes:

• The way wikilinks are represented internally changed (marked via a "wikilinks" class instead of a title attribute).
• Babel support in the LaTeX writer changed in a way that should better support most European languages. Users of custom LaTeX templates may need to revise those.

Please see the changelog for more info.

https://github.com/jgm/pandoc/releases/tag/3.6.3

If you want to export a table out of #joplin into, for example, an .odt document, don't:

- export to PDF from Joplin, libreoffice will open the PDF as a drawing
- try to copy things with the mouse and right click — it doesn't work
- make a screenshot (people can't copy-paste text from it)

What I opted for was: copy (or export) the markdown into a markdown file, let #pandoc do the conversion directly:

pandoc -o output.odt input.md

Presto.