Typst has a simpler markup system and easier customization.

There are several reasons for this dissatisfaction: the LaTeX installation is huge, compilation of large documents is not fast, and its error messages are riddles delivered by an infuriating oracle

In 2019 two German developers, Laurenz Mädje and Martin Haug, decided to try to write a LaTeX replacement "just for fun". In 2022, Mädje wrote his computer science master's thesis about Typst. In March 2023, its first pre-release beta version was announced; a month later, semantic versioning was adopted with the release of v0.1.0. Typst is now at v.0.13.1 and shows 365 contributors on its GitHub repository.

Markup in Typst is less verbose and easier to read than in LaTeX.

The simplest markup looks similar to markdown.

Typst drawbacks:

• Typst's page layout algorithm doesn't always permit the refinements that LaTeX is capable of.
• lack of specialized package (it's obvious compared to LaTeX)
• the documentation is criticized:
• inability to include PDF documents (for now)

One day, one line.

YYYY-MM-DD wWW Aaa HH event. HH-HH another event.

For example: 2021-02-15 w07 Mon 9-12 project groups. 17 jogging.

It has limits if informations needs to be stored for each event though :/

An argumentation against Xz. For later in case I will come up to the topic.

TL;DR: Who is This Book For?

1. If your primary goal is to understand a modern, efficient binary serialization format that offers significant performance and size benefits over JSON, Part I provides a comprehensive guide to CBOR.
2. If your application requires absolute, verifiable consistency – for digital signatures, content hashing, consensus, or interoperable verification – Part II delves into the principles of determinism and the specifics of dCBOR, including a tutorial for the dcbor Rust crate.
3. For those building applications that require structured, verifiable, and privacy-preserving data – smart documents – Part III explores the groundbreaking capabilities of Gordian Envelope, including usage of the bc-envelope Rust crate.

How a QR code encodes information step by step. How to decode it by hand.

PNG 3.0 https://www.w3.org/TR/png-3/

1. Animated PNG will be supported (.apng)
2. HDR support
3. Exif metadata support

The working group work on better interoperability of HDR/SDR.

More on https://www.programmax.net/articles/png-is-back/

application/x-www-form-urlencoded and multipart/form-data are still messy years later.

All smallest possible file per format

10 topics to consider while creating a file format.

Import et Export of software forges (issues, PR/MR, milestones, release assets, etc...)

age.xml is a free and easy-to-use website label that gives parental control systems information about a website’s age rating

(via https://nicolas-delsaux.hd.free.fr/Shaarli/shaare/LMJ21Q)

I like the format of the checkboxes:

[ ] Open
[@] Ongoing
[x] Checked
[~] Obsolete
[?] In question

Due Dates:

• -> 2025-03-18
• -> 2025-Q1
• -> 2025-W09
• -> 2025

Groups:

Group name
[ ] item 1
[ ] item 2

[ ] Another task

C’est la notation qui comprend la notation des dates au format « 2025-02-15 », par exemple, où la granularité la plus fine de la notation se fait à droite.

Dans le code pénal, Le livre 1, titre 2, chapitre 3, article 4 est noté « article 123-4 ».
Le seul défaut de retirer les séparateurs entre les différents niveaux de granularité : cela limite à 9 le nombre de titres ou chapitres

Concernant les dates, j’ai définitivement pris l’habitude d’écrire au format YYYY-MM-DD.
– Non seulement c’est plus logique : les nombres sont écrit dans cet ordre aussi (on commence avec les milliers, puis les centaines, puis les dizaines, puis les unités : donc les grands à gauche et les petits à droite).
– En plus l’ordre naturel est l’ordre chronologique, dans le cas des dates
– Ça limite la confusion quand un américain parle à quelqu’un de censé
– C’est l’ISO 8601.

Idem

See also https://jpegxl.info/art/