lingo.lol is one of the many independent Mastodon servers you can use to participate in the fediverse.
A place for linguists, philologists, and other lovers of languages.

Server stats:

59
active users

#pandoc

3 posts3 participants0 posts today
pandoc<p>Create a local, reusable URL database by putting Markdown reference link definitions into a file, e.g.</p><p> [example]: <a href="https://example.com" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://</span><span class="">example.com</span><span class="invisible"></span></a></p><p>Make use of the database by passing the file to pandoc as an additional input. The reference links can then be used normally.</p><p> See this [example][].</p><p> As seen on [this page][example]...</p><p><a href="https://fosstodon.org/tags/pandoc" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>pandoc</span></a> <a href="https://fosstodon.org/tags/Markdown" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Markdown</span></a></p>
pandoc<p>IDML (InDesign Markup Language) pandoc reader by <span class="h-card" translate="no"><a href="https://mastodon.design/@yann_t" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>yann_t</span></a></span>.<br><a href="https://outdesign.deborderbollore.fr/en/index.html" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://</span><span class="ellipsis">outdesign.deborderbollore.fr/e</span><span class="invisible">n/index.html</span></a></p><p><a href="https://fosstodon.org/tags/pandoc" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>pandoc</span></a> <a href="https://fosstodon.org/tags/IDML" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>IDML</span></a> <a href="https://fosstodon.org/tags/reader" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>reader</span></a></p>
Éditions Burn~Août<p>Enfin, dans l’objectif de&nbsp;répondre aux contraintes d’une temporalité éditoriale extraordinairement restreinte, un <a href="https://piaille.fr/tags/convertisseur" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>convertisseur</span></a> de&nbsp;fichiers (<a href="https://outdesign.deborderbollore.fr/" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://</span><span class="">outdesign.deborderbollore.fr/</span><span class="invisible"></span></a>) a été produit afin que les textes figurant sur&nbsp;deborderbollore.​fr puissent être générés directement à&nbsp;partir du fichier <a href="https://piaille.fr/tags/InDesign" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>InDesign</span></a> ayant servi à&nbsp;l’impression du <a href="https://piaille.fr/tags/PDF" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>PDF</span></a>.</p><p>6/9</p><p><a href="https://piaille.fr/tags/pandoc" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>pandoc</span></a></p>
scy<p>Okay, das ist jetzt gut genug, um's mal zu releasen.</p><p>Pan5008 ist eine HTML- und CSS-Vorlage, um mit Pandoc halbwegs mit DIN&nbsp;5008 konforme Briefe aufzusetzen. Es kommt ganz ohne LaTeX aus und ist deshalb angenehmer anzupassen für Leute, die in Webtechnologien zu Hause sind.</p><p>Eingabedokumente können Markdown sein, oder prinzipiell beliebige andere von Pandoc unterstützte Formate.</p><p>Es gibt "Profile", um z.B. bequem unterschiedliche Designs zu definieren.</p><p><a href="https://codeberg.org/scy/pan5008" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://</span><span class="">codeberg.org/scy/pan5008</span><span class="invisible"></span></a></p><p><a href="https://chaos.social/tags/Pandoc" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Pandoc</span></a> <a href="https://chaos.social/tags/DIN5008" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>DIN5008</span></a></p>
pandoc<p>Disable the `citation` extension when combining the Typst writer with pandoc's "citeproc" handler, as native Typst citation settings don't interact well with citeproc.</p><p> pandoc --to=typst-citation --citeproc …</p><p><a href="https://fosstodon.org/tags/pandoc" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>pandoc</span></a> <a href="https://fosstodon.org/tags/typst" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>typst</span></a> <a href="https://fosstodon.org/tags/citeproc" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>citeproc</span></a></p>
pandoc<p>"Moloch" is a clean, simple, and freshly modernized LaTeX beamer theme. It's the successor to the popular "Metropolis" theme, brought up to current standards by <span class="h-card" translate="no"><a href="https://mastodon.social/@jolars" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>jolars</span></a></span> with some help from <span class="h-card" translate="no"><a href="https://fosstodon.org/@samcarter" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>samcarter</span></a></span>.</p><p>Usage with pandoc:</p><p> pandoc --to=beamer --variable=theme:moloch …</p><p>Blog post: <a href="https://jolars.co/blog/2024-05-30-moloch/" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://</span><span class="ellipsis">jolars.co/blog/2024-05-30-molo</span><span class="invisible">ch/</span></a></p><p><a href="https://fosstodon.org/tags/pandoc" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>pandoc</span></a> <a href="https://fosstodon.org/tags/TeXLaTeX" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>TeXLaTeX</span></a> <a href="https://fosstodon.org/tags/beamer" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>beamer</span></a> <a href="https://fosstodon.org/tags/moloch" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>moloch</span></a></p>
Andrew Leland<p>Before that I was jamming with a <a href="https://mas.to/tags/plaintext" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>plaintext</span></a> workflow using markdown, coteditor + terminal.app (zsh) + <a href="https://mas.to/tags/pandoc" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>pandoc</span></a> after getting red-pilled by <span class="h-card" translate="no"><a href="https://fosstodon.org/@patric" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>patric</span></a></span>. (2/8)</p>
Matt Gemmell<p>Working on my <a href="https://mastodon.scot/tags/pandoc" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>pandoc</span></a>-based Markdown publishing system. Seems to me that the big gap is with non-fiction, where you often want to show or explain something technical or detailed, and need to decide how to mark it up. Full syntax-highlighting is of little use because it lacks focus or annotation (and only works for source code), and manual tagging with HTML/CSS is tedious and lacks automation.</p>
pandoc<p><span class="h-card" translate="no"><a href="https://social.edu.nl/@foxy" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>foxy</span></a></span> created a custom writer to output Scribus `.sla` documents.<br><a href="https://codeberg.org/foxy/scribus-writer.lua" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://</span><span class="ellipsis">codeberg.org/foxy/scribus-writ</span><span class="invisible">er.lua</span></a><br>Scribus is an open source, desktop publishing application, see <a href="https://www.scribus.net" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://www.</span><span class="">scribus.net</span><span class="invisible"></span></a>. The exporter is also available as a Scribus plugin.<br><a href="https://fosstodon.org/tags/pandoc" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>pandoc</span></a> <a href="https://fosstodon.org/tags/customWriter" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>customWriter</span></a> <a href="https://fosstodon.org/tags/scribus" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>scribus</span></a></p>
Stefano "Foxy🦊" Volpe<p>Want to convert from any <a href="https://social.edu.nl/tags/Pandoc" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Pandoc</span></a>-compatible file format to <a href="https://social.edu.nl/tags/Scribus" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Scribus</span></a>? Just use my latest <a href="https://social.edu.nl/tags/sideProject" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>sideProject</span></a> (´。• ω •。`)</p><p><a href="https://codeberg.org/foxy/scribus-writer.lua" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://</span><span class="ellipsis">codeberg.org/foxy/scribus-writ</span><span class="invisible">er.lua</span></a></p><p>I wrote this to lighten the workload of the board behind my Master's programme's magazine. The Pandoc writer itself is in pure <a href="https://social.edu.nl/tags/Lua" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Lua</span></a>. Only the GUI wrapper had to be necessarily written in <a href="https://social.edu.nl/tags/Python" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Python</span></a> (since it is a Scribus plugin).</p>
Robert Kingett<p>Link at end but Tagging <span class="h-card" translate="no"><a href="https://polymaths.social/@dmoonfire" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>dmoonfire</span></a></span> and also seeing if other <a href="https://caneandable.social/tags/Pandoc" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Pandoc</span></a> experts have a solution. In one of my templates, link at end, I'm trying to make a version that will generate/add page numbers when I convert with Pandoc using this template. For some reason, Microsoft Word won't let me add page numbers to the template itself. Has anyone done this with templates? Made it so page numbers are added upon conversion? Literary agents and publishers don't like plain text files, and they need things in Shun Manuscript format, some agents and publishers want page numbers so I wanna just add it to a template and never have to think about it again. This is my template. <a href="https://github.com/rkingett/writertools/blob/main/Pandoc%20templates/PandocReferenceWithHeadingsCreatingNewPages.docx" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://</span><span class="ellipsis">github.com/rkingett/writertool</span><span class="invisible">s/blob/main/Pandoc%20templates/PandocReferenceWithHeadingsCreatingNewPages.docx</span></a></p>
Matt Gemmell<p>Another example of using Publish, my <a href="https://mastodon.scot/tags/pandoc" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>pandoc</span></a> wrapper, this time to publish any instalment in a novel series, using shared front-/back-matter for consistency, and clean manuscript Markdown files. <a href="https://mattgemmell.scot/publishing-a-novel-series-with-pandoc-publish/" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://</span><span class="ellipsis">mattgemmell.scot/publishing-a-</span><span class="invisible">novel-series-with-pandoc-publish/</span></a></p>
Matt Gemmell<p>Achievement unlocked: added a proprietary regular-expressions flag(!) to enable a useful, if somewhat niche, feature in my <a href="https://mastodon.scot/tags/pandoc" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>pandoc</span></a>-based publishing system. <a href="https://github.com/mattgemmell/pandoc-novel/blob/main/README.org#exclusions-based-on-metadata" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://</span><span class="ellipsis">github.com/mattgemmell/pandoc-</span><span class="invisible">novel/blob/main/README.org#exclusions-based-on-metadata</span></a></p>
Matt Gemmell<p>Using my <a href="https://mastodon.scot/tags/pandoc" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>pandoc</span></a> wrapper to build genre-specific anthologies of stories, as well as novels: <a href="https://mattgemmell.scot/automating-novel-and-anthology.publishing/" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://</span><span class="ellipsis">mattgemmell.scot/automating-no</span><span class="invisible">vel-and-anthology.publishing/</span></a></p>
Matt Gemmell<p>I spent yesterday evening overhauling the recently-added exclusions feature in my <a href="https://mastodon.scot/tags/pandoc" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>pandoc</span></a> wrapper for publishing novels. It’s pretty fancy now, and I'm pleased with it. Here's the relevant section of the docs: <a href="https://github.com/mattgemmell/pandoc-novel/blob/main/README.org#exclusions" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://</span><span class="ellipsis">github.com/mattgemmell/pandoc-</span><span class="invisible">novel/blob/main/README.org#exclusions</span></a></p>
Matt Gemmell<p>My little <a href="https://mastodon.scot/tags/pandoc" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>pandoc</span></a> wrapping novel-publishing system is getting really useful (for me!). Today I added pattern-based file-exclusions. There's a lot of functionality to make repeatable, automatable, book-specific customisations.</p>
Matt Gemmell<p>For those interested, significant improvements to my <a href="https://mastodon.scot/tags/foss" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>foss</span></a> <a href="https://mastodon.scot/tags/pandoc" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>pandoc</span></a> config for publishing Markdown fiction as ebooks and in print, which I use from <a href="https://mastodon.scot/tags/emacs" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>emacs</span></a>. Brief notes here, with links to full docs and git repo: <a href="https://mattgemmell.scot/pandoc-novel/#addendum" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://</span><span class="ellipsis">mattgemmell.scot/pandoc-novel/</span><span class="invisible">#addendum</span></a></p>
Lanie Molinar Carmelo<p>Hoping those familiar with <a href="https://allovertheplace.ca/tags/LaTeX" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>LaTeX</span></a> can give me some advice here. I've started using it to create my assignments for school. I'm not writing technical papers yet, but I find using LaTeX with <a href="https://allovertheplace.ca/tags/Zotero" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Zotero</span></a> in <a href="https://allovertheplace.ca/tags/VSCode" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>VSCode</span></a> more <a href="https://allovertheplace.ca/tags/accessible" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>accessible</span></a> with a <a href="https://allovertheplace.ca/tags/ScreenReader" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>ScreenReader</span></a> than most other setups I've tried.<br>Since my discussion posts have to follow <a href="https://allovertheplace.ca/tags/APA" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>APA</span></a> style, I’m using LaTeX for those as well as full papers. That part is going well—but I’m running into trouble when I need to actually post what I’ve written.<br>My school uses Brightspace, which allows discussion posts in either rich text or <a href="https://allovertheplace.ca/tags/HTML" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>HTML</span></a>. I have <a href="https://allovertheplace.ca/tags/Pandoc" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Pandoc</span></a> installed, so I tried converting my LaTeX source to HTML and pasting the code. But Pandoc didn’t include my references section in the output.<br>I also tried copying from the PDF, but that stripped all formatting.<br>Does anyone know how I can get a clean HTML version of my work—with references included—that I can paste into Brightspace?<br>Here’s the command I’ve been using:<br>pandoc main.tex \<br> --bibliography=references. Bib \<br> --csl=apa.csl \<br> --standalone \<br> -o main.html<br>It creates the HTML file, but the references section is missing.<br>Any tips?<br><a href="https://allovertheplace.ca/tags/Accessibility" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Accessibility</span></a> <a href="https://allovertheplace.ca/tags/AssistiveTech" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>AssistiveTech</span></a> <a href="https://allovertheplace.ca/tags/Pandoc" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Pandoc</span></a> <a href="https://allovertheplace.ca/tags/APAstyle" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>APAstyle</span></a> <a href="https://allovertheplace.ca/tags/Brightspace" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Brightspace</span></a> <a href="https://allovertheplace.ca/tags/EdTech" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>EdTech</span></a> <a href="https://allovertheplace.ca/tags/AcademicWriting" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>AcademicWriting</span></a> <a href="https://allovertheplace.ca/tags/InclusiveTech" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>InclusiveTech</span></a> <a href="https://allovertheplace.ca/tags/BlindTech" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>BlindTech</span></a> <a href="https://allovertheplace.ca/tags/HigherEd" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>HigherEd</span></a> <a href="https://allovertheplace.ca/tags/CitationTools" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>CitationTools</span></a> <a href="https://allovertheplace.ca/tags/OpenSource" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>OpenSource</span></a> <a href="https://allovertheplace.ca/tags/WritingWorkflow" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>WritingWorkflow</span></a></p>
Frederik Elwert<p>Hivemind: I noticed that my academic CV is the last document I maintain in <a href="https://fedihum.org/tags/TeXLaTeX" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>TeXLaTeX</span></a>. Is there a <a href="https://fedihum.org/tags/Markdown" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Markdown</span></a> (preferably <a href="https://fedihum.org/tags/pandoc" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>pandoc</span></a>) based CV system/template/filter that you can recommend? PDF output is required, HTML output a plus. And yes, I did like the <a href="https://fedihum.org/tags/ModernCV" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>ModernCV</span></a> style.</p>
Allan ChainToday I converted some DOCX documents to Markdown. I thought <a href="https://venera.social/search?tag=markitdown" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>markitdown</span></a> is better at extracting texts from DOCX, since it's maintained by Microsoft. However, after trying it out, I found it's worse than <a href="https://venera.social/search?tag=pandoc" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>pandoc</span></a>. <a href="https://venera.social/search?tag=pandoc" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>pandoc</span></a> is able to handle the LaTeX formulas and preserves more formattings, while <a href="https://venera.social/search?tag=markitdown" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>markitdown</span></a> cannot.