Hello Marc, Am Tue, Nov 19, 2024 at 06:52:35PM +0100 schrieb Marc Haber: > On Mon, Nov 18, 2024 at 05:43:05PM +0000, Helge Kreutzmann wrote: > > Am Mon, Nov 18, 2024 at 04:00:59PM +0100 schrieb Marc Haber: > > > On Thu, Oct 31, 2024 at 08:51:20PM +0000, Helge Kreutzmann wrote: > > > > Ah, you do everything in the debian/rules file, there you make the > > > > appropriate call. So then the Makefile is pure cosmetic, isn't it? > > > > > > Maybe. I have removed it in my experimental work tree and will see > > > whether this breaks anything. Will report back. Probably not this week. > > > > > > > And since you set the limit to 95% (rather than the common 80%) quite > > > > a few files are currently not build. > > > > > > That's a matter of style. I despise switching back and forth between > > > langauges in the same paragraph, so I have set the hurdle a bit higher. > > > Is that bad? > > > > Po4a is paragraph based, so either a paragraph is rended in english > > (if the translation does not exist or is outdated) or in the target > > language. > > > > Jumping back and forth between languages is of course not optimal, but > > usually 80% is a good compromise, especially since translators are a > > scarce ressource. > > I might overlook the connection between incomplete translations not being > used and the scarce resource translators. Am I wasting translator's time > by waiting for them to work?
No, I probably expressed myself not very well.
I've seen many translators who have lots of projects they work in. So
they do not update any project regularly, but only once in a while.
During this time frame the original text evolves, hence more and more
parts get outdated.
Then a project with a high limit has little chance of showing the
translated text, because with relative few changes the *entire* text
is in English again. And maybe the translator just returns in a few
month time, or just after this major release which goes int (Debian)
stable …
> > And consider the following scenario:
> > You add a new sections with lots of paragraphs, or quite a few new
> > options. Then the translation might drop below 95%, but actually the
> > new text is not "randomly" scattered over the man page, but limited in
> > one part. So having the rest in the users language can still be a
> > coherent reading experience (and the user might not be interested in
> > these new options or might not need the new section).
>
> With short phrases it might even result in lange changing mid-sentence.
Well, of course you can scatter (by accident or by design) sentences
over several paragraphs. But if possible, please avoid this. Even just
because you cannot really translate half sentence well.
> > If you want it really simple, then take my toy package linuxinfo. But
> > I cannot guarantee that I considered all corner cases correctly, I'm
> > not a programmer and my autoconf is, well, basic.
>
> Will look.
>
> > And I'm pretty sure some right combination of "apt*" tool command will
> > print you all packages using (build depending on) po4a.
>
> Yes, but that doesnt show me whether po4a is being used correctly or
> just by another maintainer with semi-knowledge like mine.
That's why I pointed you to po4a itself, hopefully the author knows
the best usage. And the documentation is extensive there.
I don't recommend you looking at my primary project, namely
manpages-l10n. This uses po4a in the "old" fashion, Toddy is
investigating to modernize it.
Greetings
Helge
--
Dr. Helge Kreutzmann [email protected]
Dipl.-Phys. http://www.helgefjell.de/debian.php
64bit GNU powered gpg signed mail preferred
Help keep free software "libre": http://www.ffii.de/
signature.asc
Description: PGP signature
