| Commit message (Collapse) | Author | Files | Lines |
|---|
|
|
|
|
|
|
|
|
|
The goal is to make a TODO entry be able to move category, say from a
question to a decision, without chaging its id.
|
|
|
|
|
|
|
|
|
|
This is an improvement over 67f7c956239a7bc811a1d655d389666048e45fc3,
and a final step for #task-7c5cd2aa-6d92-0423-bfa7-81f2e8436586.
Now instead of trying to convince po4a and mdpo to work together, each
tools gets it own folder and a pofile for each language. This means
that if I want to translate files FOO.md and a-dir/BAR.txt to pt and
fr, the directory structure of po/ will be:
po/
FOO.md/
pt.po
fr.po
a-dir/
BAR.txt/
pt.po
fr.po
The po/ folder mirrors the directory structure of the input files, also
nesting down directories.
This way mdpo can do extration and update on its own way, and po4a can
do extraction and update on its on way.
The downside is that some translations will be duplicated, because
they can appear on more than one file.
|
|
|
|
|
|
- aux/workflow/l10n.sh: fix handling of $@;
- Makefile: remove circular dependency between dev-check and public by
adding the "l10n-gen" target.
|
|
I didn't like the previous version of aux/workflow/manpages.sh mainly for 2 reasons:
1. its CLI was terrible, ugly and fragile;
2. it mixed handling manpages and handling *translations*.
The first step was to split the translations part to a different file:
aux/workflow/l10n.sh. Now it has the base logic for running po4a, and
can apply it to manpages. It is useful for updating translated files
in other scenarios, such as catgets() message catalogs, markdown files,
etc.
After I used the venerable getopts to handle the command line
arguments, and give aux/workflow/manpages.sh a saner interface.
I disliked the fact that aux/workflow/manpages.sh still is being used
for the "install" and "uninstall" targets. Before this file, the
canonical workflow of "make && make install/uninstall" was 100%
embedded within the Makefile itself. But now the Makefile calls to an
external script for that. This isn't a real cost, other than how
obvious the behaviour is for someone looking at the Makefile for the
first time.
I still chose to do it anyway, because there was already too many
things in the Makefile itself, and it was getting worse with time. I
made sure to never cross the line of relying on an external tool for
the canonical "make && make install/uninstall", and even for
"make check". Those all work without requiring any extra tool outside
what POSIX defines, such as "sed", "awk", etc. Despite the cost of
adding this detour from the liner Makefile flow, I found it to be worth
it to call to the external script, as this script can now also be
shared across projects, and the customized Makefile be made simpler.
In other to remove the "-- $(do_subst)" horrendous hack, I chose to use
an inference rule for ".in" files, and remove the "$(do_subst)"
variable altogether. Now all the files that need to go through sed
should end in ".in", and the Makefile will take care of producing it.
The upside is that this model is much better integrater into make
itself.
Addresses #task-9ee2bbc8-295f-52b7-4104-483869bad017.
|
|
|
|
|
|
|
|
Make SUPPORTED REMOTES and OVERRIDES subsections (.SS) of a new
parent section: CONFIGURATIONS.
Also put SUPPORTED REMOTES before OVERRIDES on the order.
|
|
Also improve french translation: s/FICHIERS/FICHIER/.
|
|
option
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
