Recent commits to derivepassphrase.git (01bff8cba2afa4b25d804df972a0e6350107b88d)

Add new help text messages with option specs and metavars expanded inline

2026-08-16T09:20:06+02:00

For all option one-line descriptions, add variants where the option
specification (as it appears in the help text) is included inline, as
a first line/first paragraph, and the one-line description as the second
paragraph.  In these variants, metavars are expanded inline, as in the
previous commit.

The inline expansion of metavars follows the reasoning from the previous
commit.  The one-line description is due to a planned new command-line
argument parser, which is strictly a parser and thus leaves option
grouping, mutually exclusive options and help text generation to the
application.  Keeping the formatted option specification in the help
text string gives the translators more context, and also allows the
application (the help text formatting part at least) to rediscover the
grouping or mutual exclusivity based on identical help text strings.
</pre>

Add new help and error messages with metavars expanded inline

2026-08-16T08:52:13+02:00

For all texts that aren't one-line option descriptions, add versions of
the text where the metavar is expanded inline, instead of referencing
a different translation string inline.  If multiple texts need to use
the same metavar consistently, pick one of them, and reference that
canonical entry in the other entries' commentary.

This is partly based on search engine/AI feedback on how other projects
solve the problem of wanting to explain mini-formats or other
conventions common to multiple messages to translators: there is no
place to put (machine-readable) references or common explanation, so it
is typical instead to refer inline in the translation commentary to
a canonical entry that contains longer-form explanation instead.  This
is rather awkward to work with if there are multiple layers of expansion
(metavars) in the messages, so it is probably easier on the translators
to include the metavar inline and just note that "canonical text X" uses
the same metavar.  Of course, the canonical text should be short enough
to be easily included inline in the commentary.
</pre>

Update wishlist to post-v0.6.1

2026-07-06T21:29:46+02:00

</pre>

Release 0.6.1

2026-07-06T21:28:06+02:00

</pre>

Merge branch 'release-0.6.1-preparations'

2026-07-06T21:20:40+02:00

Prepare to release derivepassphrase v0.6.1

* release-0.6.1-preparations:
  Update wishlist
  Update the translation template, the German translation, and the message catalogs
  Add changelog entries for economic-test-suite, click-8.4.2-compatibility and openssh-bug3967-workaround
  Reformat everything with ruff
  Update wishlist
  Set the Python path correctly during pytest invocation
</pre>

Update wishlist

2026-07-06T20:19:03+02:00

Also reference the new entry in the changelog.
</pre>

Update the translation template, the German translation, and the message catalogs

2026-07-05T22:34:45+02:00

</pre>

Add changelog entries for economic-test-suite, click-8.4.2-compatibility and openssh-bug3967-workaround

2026-07-05T22:22:00+02:00

</pre>

Reformat everything with ruff

2026-07-05T21:47:45+02:00

Linting and type checking passes, so nothing to do there.
</pre>

Update wishlist

2026-07-05T21:46:51+02:00

</pre>