#Tag · bonfire.cafe

- Arm64 Linux support,
- Improved UI for Citations
- New Fetchers: #OpenAlex and #EuropePMC
- Initial Cite As You Write endpoint
- First CLI version #JabKit with integrity check
- #CSL style fixes for #LibreOffice
- #JavaFX 25

#java #opensource #linux #arm #bibliography #academia #citations #texlatex #JabRef #GSOC #gsoc2025

Screenshot of the about dialog of JabRef 6.0-alpha3 showing the list of maintainers and the version details

JabRef

@jabref@foojay.social · 2 weeks ago

👻 🎃 JabRef 6.0-alpha.3 Release 🎃 👻

Trick or treat! Happy Halloween from the JabRef team! We are happy to announce the release of JabRef 6.0 Alpha 3

Release Highlights:

#java #opensource #linux #arm #bibliography #academia #citations #texlatex #JabRef #GSOC #gsoc2025

Jürgen Hubert

@juergen_hubert@mementomori.social · 3 weeks ago

I've come to the conclusion that, while I am still using #Windows 11 out of inertia, it's time to contemplate an exit plan towards #Linux . The switch won't be any time soon (I have too much other stuff on my plate for the foreseeable future), but I do want to avoid paying further license fees to #Microsoft .

Major areas of concern:

- My #Steam library. I am by no means a heavy gamer, but I want to check if the major games I enjoy are known to work on Linux.
- Migrating away from #GoogleDrive towards #NextCloud is going to be a major chore, but it's something I can start in advance.
- I am a very heavy user of Notepad++ for my #TeXLaTeX typesetting, so I need a replacement whose user experience comes close (and no, neither vim nor emacs count).

As for what distribution to choose... I dunno. Lots of people at my place of work use #Debian , so maybe that would be a good idea?

Chip Butty boosted

pandoc

@pandoc@fosstodon.org · 3 weeks ago

Simplify custom LaTeX templates maintenance with "partials" & baked-in internal template snippets: The `common.latex` partial is the most important, as it contains almost all LaTeX definitions and instructions necessary to compile pandoc-generated LaTeX code.

% In LaTeX templates, use
$common.latex()$

Manual template updates become mostly unnecessary this way.

See the contents of the partial with

pandoc --print-default-data-file=templates/common.latex

#pandoc #TeXLaTeX #template #partial

pandoc

@pandoc@fosstodon.org · 3 weeks ago

% In LaTeX templates, use
$common.latex()$

Manual template updates become mostly unnecessary this way.

See the contents of the partial with

pandoc --print-default-data-file=templates/common.latex

#pandoc #TeXLaTeX #template #partial

pandoc

@pandoc@fosstodon.org replied · 3 weeks ago

Besides the `common.latex` partial, there are also:

• `passoptions.latex` – options for packages that may be loaded implicitly (should come before `\begin{document}`)
• `fonts.latex` – Fonts setup
• `font-settings.latex` – Fonts configs
• `hypersetup.latex` – Options for the “hypertext” package (hyperlinks and metadata)
• `after-header-includes.latex` – Everything that *must* happen late.

Using all of these partials in custom templates gives maximum robustness.

#pandoc #TeXLaTeX #template

pandoc

@pandoc@fosstodon.org · 3 weeks ago

% In LaTeX templates, use
$common.latex()$

Manual template updates become mostly unnecessary this way.

See the contents of the partial with

pandoc --print-default-data-file=templates/common.latex

#pandoc #TeXLaTeX #template #partial

devSJR :python: :rstats: boosted

pandoc

@pandoc@fosstodon.org · 3 weeks ago

The aspect ratio of LaTeX Beamer presentations can be controlled via the `aspectratio` variable. E.g., to switch from the default 4:3 ratio of slides to the 16:9 HD format:

pandoc --to=beamer --variable=aspectratio:169 …

#pandoc #TeXLaTeX #Beamer #slides

pandoc

@pandoc@fosstodon.org · 3 weeks ago

The aspect ratio of LaTeX Beamer presentations can be controlled via the `aspectratio` variable. E.g., to switch from the default 4:3 ratio of slides to the 16:9 HD format:

pandoc --to=beamer --variable=aspectratio:169 …

#pandoc #TeXLaTeX #Beamer #slides

Lukas C. Bossert

@lukascbossert@mastodon.social · 4 weeks ago

The meta poster frames the concept: clarity + openness → resilience. It traces the lineage from Knuth’s Literate Programming to Org-mode and NFDI practice, and introduces the ROOT badge as a compact signal for robust, open, ongoing, time-tested tools. It also spotlights resilient stalwarts often hiding in plain sight—find, LaTeX, perl, rsync, SQLite—showing why they remain reliable RDM building blocks.
#ResilientTech #LiterateProgramming #OrgMode #RDM #NFDI #FAIR https://doi.org/10.5281/zenodo.17157588

Zenodo

Resilient Technologies. Why Decades-Old Tools Define the ROOT of Modern Research Data Management

Research data management (RDM) today is characterized by a multitude of new platforms and specialized software solutions. These innovations are undoubtedly important, but they also involve risks: short life cycles, proprietary dependencies, and limited sustainability. In contrast, there are tools that have existed for decades and have proven to be remarkably resilient. These “resilient technologies” are distinguished by longevity, openness, interoperability, and the support of active communities. Examples include Emacs (established in 1976 as a highly customizable editor), awk (1977) for efficient text and data processing, sed and grep (indispensable in pattern recognition and transformation since the 1970s), as well as perl (1987) as a flexible scripting language for data pipelines. In the field of documentation, LaTeX (1984) stands for sustainable, reproducible, and platform-independent text processing. For the automation of complex workflows, make (1976) has proven its worth, while rsync (1996) remains unrivaled as a robust tool for data backup and transfer to this day. This is complemented by curl (1997), which has enabled stable and universal data transfer over the internet for decades. This three-poster series argues that decades-old, community-maintained tools form the ROOT of sustainable research data management—Robust, Open, Ongoing, Time-tested. The Concept/Meta poster motivates the idea of “resilient technologies,” tracing its lineage from literate programming and the Unix philosophy to contemporary RDM/NFDI practice. It introduces the ROOT badge as a compact signal for tools that are transparent, composable, well-documented, and maintained across years. The Main poster translates the concept into practice by mapping resilient tools (e.g., Emacs/Org-babel, Make, curl/sed/awk/grep/diff, cron, tar/rsync, SQLite, LaTeX, find) onto the research data life cycle (planning, production, analysis, archiving, access, re-use). It highlights simple, inspectable patterns—small steps that chain together into pipelines you can audit, version, and rebuild long after fashions and GUIs change. The Source poster closes the loop by disclosing the full build of the posters themselves: a reproducible, text-first publication that can be re-generated from a single source using the very tools it advocates. Together, the trilogy provides a coherent “why–what–how”: a rationale for resilience, a concrete mapping to RDM tasks, and an executable artifact that embodies the approach. The intended outcome is pragmatic: lower maintenance burden, higher reproducibility, and infrastructures that improve with age.

Meta poster defining ‘resilient technologies’, showing the ROOT badge, citing lineage, and listing further long-lived tools with RDM relevance.

Lukas C. Bossert

@lukascbossert@mastodon.social replied · 4 weeks ago

The source poster shows the guts: Emacs/Org-babel + LaTeX; noweb tangling; minted listings; multi-column layout. The complete source code! The poster is both publication and working research object. Example flow: query Zenodo via curl, download dataset, compute checksum, compare, then proceed with scripted transforms—transparent steps you can re-run. Everything is fully specified, so you can regenerate all of it from source. #Emacs #OrgBabel #TeXLaTeX #orgmode
https://doi.org/10.5281/zenodo.17157588