Website updates
by Jean-Christophe Helary
I see that now that 0.70 is released, the release summary is in English on the French page.
Is the web update process automatic? For ex, if I updated the FR translation on Weblate, would the modifications be taken into account right away?
2 months, 4 weeks
po4a v0.70 released
by Martin Quinson
Hello friends,
I finally took the time to release po4a. The changelog and all information is
on the github webpage: https://github.com/mquinson/po4a/releases/tag/v0.70
Thanks to every individual who made this release possible. Please test it and
report any problem you encounter. Note that the convertion to PerlIO introduced
in this release may break some setups, so please be careful when updating.
Thanks, and have a good day.
Mt
2 months, 4 weeks
Re: Planned po4a release on January 15. Please translate & test]
by Marco Ciampa
On Sun, Jan 14, 2024 at 10:53:10PM +0000, Jean-Christophe Helary via Devel wrote:
>
>
> > On Jan 15, 2024, at 9:17, Martin Quinson <Martin.Quinson(a)ens-rennes.fr> wrote:
> >
> > Hello,
> >
> > thanks you guys for taking care of these things. I must say that "traductaire"
> > sounds a bit weird in French, doesn't it?
>
> When you're used to it, it doesn't :) Je suis un traductaire libre.
>
> > My personal way of making a text
> > gender-inclusive is to alternate from one sentence to the other, or to write it
> > all in feminin form after a footnote explaining the fact this arbitrary choice.
> > In the case of po4a, I don't have any strong opinion, but I would really
> > appreciate if someone finds a way to make it inclusive.
>
> Ok. Thank you.
>
> Jean-Baptiste, let's find ways to improve the documentation. Modify my
> proposals as you think is appropriate and let's consider ways to adapt
> the current documentation until the next version.
>
Please note that grammar gender has nothing to do with any meaning in any
language. So all this work is a waste of time.
See for example: https://blog.duolingo.com/what-is-grammatical-gender/
but there are tons of examples almost everywhere...
--
Amike,
Marco Ciampa
3 months, 1 week
Planned po4a release on January 15. Please translate & test
by Martin Quinson
Hello friends,
I think we have a rather interesting set of changes in the git, and would like
to go for a release in a week or so. Please test the current git if you have an
opportunity, and update your translations if you have some. The current state
of the translations are the following:
Binaries:
1 language >= 95%: es (96%).
14 languages >= 90%: de (94%), eo (92%), fr (94%), hr (90%), it (94%),
ja (94%), nb (93%), nl (94%), pt (94%), pt_BR (94%),
sr_Cyrl (94%), uk (94%), zh_Hans (90%), zh_Hant (90%).
2 languages >= 80%: hu (88%), ru (89%).
1 language >= 70%: id (74%).
8 languages >= 50%: cs (56%), da (62%), et (65%), eu (54%), pl (60%),
sl (54%), sv (69%), vi (65%).
1 language >= 33%: ca (43%).
6 starting languages: ace (2%), af (7%), ar (13%), ka (16%), kn (7%),
ko (18%).
Documentation:
8 languages >= 95%: de (96%), es (97%), fr (96%), it (96%), ja (96%),
nl (96%), sr_Cyrl (96%), uk (96%).
4 languages >= 90%: pt (91%), pt_BR (91%), zh_Hans (90%), zh_Hant (90%).
2 languages >= 50%: pl (65%), ru (62%).
1 language >= 33%: ca (42%).
4 starting languages: eo (2%), hr (0%), hu (0%), nb (4%).
The changelog is here: https://github.com/mquinson/po4a/blob/master/NEWS
There is a possibility that we need another release shortly after this one, in
case some bugs are reported against all those changes, but maybe not. Will see.
Thanks for your help, and have a good one.
Mt
3 months, 1 week
Re: Planned po4a release on January 15. Please translate & test
by Martin Quinson
Hello,
I just added this TODO to the source before the offending line:
# TODO: rewrite to "msgmerge suffers some bugs when PO files are not
# encoded in UTF-8; Recoding %s to UTF-8 (was %s) to circumvent the issue"
I hope it helps understanding the current wording.
Thanks for your help, and for the remark.
Mt
Le samedi 13 janvier 2024 à 00:26 +0000, suzume(a)protonmail.com a écrit :
> "Force the encoding of %s to UTF-8 (was %s), as mixing encodings may break
> msgmerge."
>
> What does this do?
>
> Force an interpretation of the file as UTF-8? Force a conversion to UTF-8?
>
> JC
>
> > On Jan 13, 2024, at 7:22, Martin Quinson <Martin.Quinson(a)ens-rennes.fr>
> > wrote:
> >
> > Hello,
> >
> > This is a gentle reminder that we have a release scheduled over the week-
> > end.
> > The current translation stats follow. Thanks to anyone involved in this
> > upcoming release.
> >
> > Binaries:
> > 3 languages = 100%: es, it, ru.
> > 13 languages >= 90%: de (94%), eo (92%), fr (94%), hr (90%), ja (94%),
> > nb (93%), nl (94%), pt (94%), pt_BR (94%),
> > sr_Cyrl (94%), uk (94%), zh_Hans (90%), zh_Hant (90%).
> > 1 language >= 80%: hu (88%).
> > 1 language >= 70%: id (74%).
> > 8 languages >= 50%: cs (56%), da (62%), et (65%), eu (54%), pl (60%),
> > sl (54%), sv (69%), vi (65%).
> > 1 language >= 33%: ca (43%).
> > 6 starting languages: ace (2%), af (7%), ar (13%), ka (16%), kn (7%),
> > ko (18%).
> >
> > Documentation:
> > 1 language = 100%: it.
> > 7 languages >= 95%: de (96%), es (99%), fr (96%), ja (96%), nl (96%),
> > sr_Cyrl (96%), uk (96%).
> > 4 languages >= 90%: pt (91%), pt_BR (91%), zh_Hans (90%), zh_Hant (90%).
> > 2 languages >= 50%: pl (65%), ru (64%).
> > 1 language >= 33%: ca (42%).
> > 4 starting languages: eo (2%), hr (0%), hu (0%), nb (4%).
> >
> > Thanks again,
> > Mt
> >
> > Le samedi 06 janvier 2024 à 11:07 +0100, Martin Quinson a écrit :
> > > Hello friends,
> > >
> > > I think we have a rather interesting set of changes in the git, and would
> > > like
> > > to go for a release in a week or so. Please test the current git if you
> > > have
> > > an
> > > opportunity, and update your translations if you have some. The current
> > > state
> > > of the translations are the following:
> > >
> > > Binaries:
> > > 1 language >= 95%: es (96%).
> > > 14 languages >= 90%: de (94%), eo (92%), fr (94%), hr (90%), it (94%),
> > > ja (94%), nb (93%), nl (94%), pt (94%), pt_BR
> > > (94%),
> > > sr_Cyrl (94%), uk (94%), zh_Hans (90%), zh_Hant
> > > (90%).
> > > 2 languages >= 80%: hu (88%), ru (89%).
> > > 1 language >= 70%: id (74%).
> > > 8 languages >= 50%: cs (56%), da (62%), et (65%), eu (54%), pl (60%),
> > > sl (54%), sv (69%), vi (65%).
> > > 1 language >= 33%: ca (43%).
> > > 6 starting languages: ace (2%), af (7%), ar (13%), ka (16%), kn (7%),
> > > ko (18%).
> > >
> > > Documentation:
> > > 8 languages >= 95%: de (96%), es (97%), fr (96%), it (96%), ja (96%),
> > > nl (96%), sr_Cyrl (96%), uk (96%).
> > > 4 languages >= 90%: pt (91%), pt_BR (91%), zh_Hans (90%), zh_Hant (90%).
> > > 2 languages >= 50%: pl (65%), ru (62%).
> > > 1 language >= 33%: ca (42%).
> > > 4 starting languages: eo (2%), hr (0%), hu (0%), nb (4%).
> > >
> > > The changelog is here: https://github.com/mquinson/po4a/blob/master/NEWS
> > >
> > > There is a possibility that we need another release shortly after this
> > > one,
> > > in
> > > case some bugs are reported against all those changes, but maybe not.
> > > Will
> > > see.
> > >
> > > Thanks for your help, and have a good one.
> > > Mt
> >
> > _______________________________________________
> > Devel mailing list -- devel(a)lists.po4a.org
> > To unsubscribe send an email to devel-leave(a)lists.po4a.org
>
>
3 months, 2 weeks
Please test the current git version of po4a
by Martin Quinson
Hello friends,
I just pushed a big cleanup in the po4a source code. Instead of messing up
manually with encoding, I switched to PerlIO, the modernity introduced 15 years
ago to Perl.
This makes the code more maintainable on the long term, but it will very
probably break things around. We have a comprehensive test suite, but I doubt
that it will be enough.
I had a breakage on po4a itself that didn't show up when running the tests, but
only when using po4a to build itself, thus showing the limits of our tests. In
particular, we have almost no tests about how po4a reacts to misconfiguration.
Bingo, po4a was declaring an XML file with Latin1 encoding while the file was
actually UTF-8. The new version is more picky about it.
@Tobias, it'd be really great if you had the time to test the debian package
build-depending on us. I always forget how to do that seamlesly (ie, without
uploading a package to unstable). Maintainers of other distributions are
welcome to test po4a as extensively as they can, too.
Please report any issue either here per email, or through the github bug
tracker. We can also chat over IRC on OFTC #po4a, or even through Discord on
https://discord.gg/fcgF7nTXtb
Also, these changes invalidated the translations quite a bit. Translators may
want to start updating their files, but nothing is frozen yet and the strings
may change if we find bugs around the new strings. I would personnaly advise to
wait before updating the translations, but do as you see fit.
Have a good one,
Mt
3 months, 3 weeks
