https://git.schokokeks.org/derivepassphrase.git/tree/c4574c9f06dd37f8a95af0efafb068ad62a8b7d7Recent commits to derivepassphrase.git (c4574c9f06dd37f8a95af0efafb068ad62a8b7d7)2025-01-11T18:54:56+01:00tag:gitlist.org,2012:commit/c4574c9f06dd37f8a95af0efafb068ad62a8b7d7Merge topic branch 'usage-fixes' into master2025-01-11T18:54:56+01:00Marco Riccisoftware@the13thletter.info
<pre>* t/usage-fixes:
Fix tests for rephrased "Cannot update the %s settings" message
</pre>
tag:gitlist.org,2012:commit/f2585c5ec1b1cb0f5bc7a2d924e294497696d9d6Fix tests for rephrased "Cannot update the %s settings" message2025-01-11T18:51:01+01:00Marco Riccisoftware@the13thletter.info
<pre>The rephrasing was introduced in
1b29904d789be7742119bfa06ce11aa5b7ffb6f9.
</pre>
tag:gitlist.org,2012:commit/be9ba21a9696c59cea79365f9567decc7fa761baMerge topic branch 'usage-fixes' into master2025-01-11T16:39:58+01:00Marco Riccisoftware@the13thletter.info
<pre>* t/usage-fixes:
Fix translation string formatting of preformatted paragraphs
Make debug and info messages from exporter subcommands translatable
</pre>
tag:gitlist.org,2012:commit/70be2295f958ed99bac34e2adc469d6d94a68a11Fix translation string formatting of preformatted paragraphs2025-01-11T16:33:03+01:00Marco Riccisoftware@the13thletter.info
<pre>Due to a sign error, the paragraph content was being dropped.
And since we now actively include translation strings with preformatted
paragraphs, include coverage tracking for this case.
</pre>
tag:gitlist.org,2012:commit/fe7b6349a5c5781a4d1b1ecf16d976e43d0e7f95Make debug and info messages from exporter subcommands translatable2025-01-11T16:28:48+01:00Marco Riccisoftware@the13thletter.info
<pre>We add all debug and info messages from the `derivepassphrase export
vault` subcommand to the translatable strings enums. We also improve
several debug messages from the "inline calculation" style to the more
easily translatable "tabular listing of relevant data" style.
Two unimportant info messages were dropped:
* Attempting to parse as v0.2 configuration
* Attempting to parse as v0.3 configuration
</pre>
tag:gitlist.org,2012:commit/dc8b8f9976eddf243c67415bcd3c3cbcc250363eMerge topic branch 'documentation-fixes' into master2025-01-11T15:50:31+01:00Marco Riccisoftware@the13thletter.info
<pre>* t/documentation-fixes:
Overhaul all other manpages and copyedit everything for consistency
</pre>
tag:gitlist.org,2012:commit/a8c8e836c3a10834415a51e15a8cfadb1c752334Overhaul all other manpages and copyedit everything for consistency2025-01-11T15:38:02+01:00Marco Riccisoftware@the13thletter.info
<pre>The top-level `derivepassphrase` command, and the subcommands `export`
and `export vault` now have proper manpages (both manpage and online
formats) similar to `derivepassphrase vault`.
All manpages document the `--help`, `--version`, `--debug`, `--verbose`
and `--quiet` options. If a command only delegates to subcommands,
a SUBCOMMANDS section is now present, and the DESCRIPTION section has
the subcommand listing deduplicated. The COMPATIBILITY section details
compatibility only for this command, and refers to subcommand manpages
as necessary.
The new manpages do not tabulate their diagnostics yet, nor do they
include examples.
</pre>
tag:gitlist.org,2012:commit/50a83cf2b55863760234c34f54c0ed8e69d30ac2Move manpage directory out of docs, to top-level2025-01-08T14:52:31+01:00Marco Riccisoftware@the13thletter.info
<pre>The `docs` directory contains sources for the documentation website, to
be uploaded to the WWW. While also "online" documentation (in the sense
that they are browsable on the customer's computer system), manpages are
not typically distributed online (in the WWW sense).
Besides, the `docs` directory already contains a rendering of the
manpage.
</pre>
tag:gitlist.org,2012:commit/2b1ca491019b2366b079155ad2a40353814c21e2Merge topic branch 'usage-fixes' into master2025-01-07T23:42:07+01:00Marco Riccisoftware@the13thletter.info
<pre>* t/usage-fixes:
Incorporate revised wording from the manpage into the README
</pre>
tag:gitlist.org,2012:commit/43032ef813ac40a46e08eda067e015fafaa1475bIncorporate revised wording from the manpage into the README2025-01-07T23:36:49+01:00Marco Riccisoftware@the13thletter.info
<pre>The revised wording spells out the strength guarantee of the derivation
scheme and the purpose of the configuration file more explicitly.
We intentionally keep the introductory sentences (one-line description
and first sentence of the first explanatory paragraph) different,
because they have different contexts to work with; in particular, the
manpage contains a synopsis section and can refer to the SERVICE metavar
in its one-line description, whereas the README cannot, and should also
mention SSH keys early.
</pre>