I took liberty to update po for debian-faq

[Beatrice Torracca]

Hi!

In the debian-faq repo the original version has been updated several
times, but the .pot and .po files (and the corresponding translations,
I imagine) were stuck at 2017 (IIRC).

Having commit rights on salsa for my translation work, I took the
liberty to update the po files ("make update-po"). As a result several
.po files are to be updated: de, fr, it, ja, nl, ru, zh_CN.

In case I made the wrong move, please tell me if I should not do this
again, or if I need to revert the changes (or keep them only for
Italian).

Thanks,

beatrice

[Joost van Baal-Ilić]

Hi Beatrice,

Post by Beatrice Torracca
In the debian-faq repo the original version has been updated several
times, but the .pot and .po files (and the corresponding translations,
I imagine) were stuck at 2017 (IIRC).
Having commit rights on salsa for my translation work, I took the
liberty to update the po files ("make update-po"). As a result several
.po files are to be updated: de, fr, it, ja, nl, ru, zh_CN.
In case I made the wrong move, please tell me if I should not do this
again, or if I need to revert the changes (or keep them only for
Italian).

It looks fine to me; thanks! I've just recorded your commit in a new entry for
debian/changelog.

Bye,

Joost

[Beatrice Torracca]

Hi,

Post by Joost van Baal-Ilić

Post by Beatrice Torracca
In case I made the wrong move, please tell me if I should not do this
again, or if I need to revert the changes (or keep them only for
Italian).

It looks fine to me; thanks! I've just recorded your commit in a new entry for
debian/changelog.

So now that I have updated the Italian translation, can I simply commit that or should I make a record in debian/changelog. (I am inclined to think only maintainer should touch the debian/changelog file).

Thanks,

beatrice

[Joost van Baal-Ilić]

Hi Beatrice,

Post by Beatrice Torracca

Post by Joost van Baal-Ilić

Post by Beatrice Torracca
In case I made the wrong move, please tell me if I should not do this
again, or if I need to revert the changes (or keep them only for
Italian).

It looks fine to me; thanks! I've just recorded your commit in a new
entry for debian/changelog.

So now that I have updated the Italian translation, can I simply commit that
or should I make a record in debian/changelog. (I am inclined to think only
maintainer should touch the debian/changelog file).

I have a slight preference for you updating debian/changelog too, along with
your commit.

Thanks! Bye,

Joost

[Holger Wansing]

Hi,

Post by Joost van Baal-Ilić
Hi Beatrice,

Post by Beatrice Torracca
In the debian-faq repo the original version has been updated several
times, but the .pot and .po files (and the corresponding translations,
I imagine) were stuck at 2017 (IIRC).
Having commit rights on salsa for my translation work, I took the
liberty to update the po files ("make update-po"). As a result several
.po files are to be updated: de, fr, it, ja, nl, ru, zh_CN.
In case I made the wrong move, please tell me if I should not do this
again, or if I need to revert the changes (or keep them only for
Italian).

It looks fine to me; thanks! I've just recorded your commit in a new entry for
debian/changelog.

Today I committed a French translation update from
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=920492

However, this translation seems outdated as Beatrice mentions above.
When I now call "make update-po", all po files (!) are changed again because
of changings like this:


@@ -3185,7 +3185,7 @@ msgid ""
"management system (dpkg) will send an error message that it also needs "
"<package>binutils</package>, and stop installing "
"<package>gcc</package>. (However, this facility can be overridden by the "
-"insistent user, see <manref section=\"8\" name=\"dpkg\">.) See more in <ref "
+"insistent user, see <manref name=\"dpkg\" section=\"8\">.) See more in <ref "
"id=\"depends\"> below."


Means the "section=xxx" and "name=yyy" parts within <manref ... > are swapped,
leading to 18 fuzzy strings :-((

I remember such issue from years ago. But is this still an unfixed issue?

This way we cannot get the translations up-to-date, hrrrr ...

Is this known? How to deal with this?

Beatrice: which Debian version are you using? I wonder if the tools in Debian
unstable behave different from those in Debian stable (I'm trying to explain,
what happens here).
I am using Debian stable.


Holger

[Beatrice Torracca]

Post by Holger Wansing
Hi,

Hi,

Post by Holger Wansing
Today I committed a French translation update from
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=920492
However, this translation seems outdated as Beatrice mentions above.
When I now call "make update-po", all po files (!) are changed again because
@@ -3185,7 +3185,7 @@ msgid ""
"management system (dpkg) will send an error message that it also needs "
"<package>binutils</package>, and stop installing "
"<package>gcc</package>. (However, this facility can be overridden by the "
-"insistent user, see <manref section=\"8\" name=\"dpkg\">.) See more in <ref "
+"insistent user, see <manref name=\"dpkg\" section=\"8\">.) See more in <ref "
"id=\"depends\"> below."

In the past when I saw that with make update-po all the resulting
changes were like the one you mention, I just reverted the
changes. With my first update-po, at least for Italian, there were
some real "updates" with new messages and changed messages, not only
this kind of changes with just a different order of the items in the
tags.

After all, you only need one "make update-po" after some changes in the
original text. Then you won't need to run it again until the original
text changes. But, yes, it is an annoying problem.

Post by Holger Wansing
Means the "section=xxx" and "name=yyy" parts within <manref ... > are swapped,
leading to 18 fuzzy strings :-((
I remember such issue from years ago. But is this still an unfixed issue?
This way we cannot get the translations up-to-date, hrrrr ...
Is this known? How to deal with this?

See https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=725931

Anyway as far as I can see, the proposed work around is already implemented
in the Makefile of the faq that already contains "PERL_PERTURB_KEYS=0
PERL_HASH_SEED=0".

Post by Holger Wansing
Beatrice: which Debian version are you using? I wonder if the tools in Debian
unstable behave different from those in Debian stable (I'm trying to explain,
what happens here).
I am using Debian stable.

I am using testing.

Ciao,

beatrice

[Holger Wansing]

Hi,

Post by Beatrice Torracca

Post by Holger Wansing
Today I committed a French translation update from
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=920492
However, this translation seems outdated as Beatrice mentions above.
When I now call "make update-po", all po files (!) are changed again because
@@ -3185,7 +3185,7 @@ msgid ""
"management system (dpkg) will send an error message that it also needs "
"<package>binutils</package>, and stop installing "
"<package>gcc</package>. (However, this facility can be overridden by the "
-"insistent user, see <manref section=\"8\" name=\"dpkg\">.) See more in <ref "
+"insistent user, see <manref name=\"dpkg\" section=\"8\">.) See more in <ref "
"id=\"depends\"> below."

In the past when I saw that with make update-po all the resulting
changes were like the one you mention, I just reverted the
changes. With my first update-po, at least for Italian, there were
some real "updates" with new messages and changed messages, not only
this kind of changes with just a different order of the items in the
tags.
After all, you only need one "make update-po" after some changes in the
original text. Then you won't need to run it again until the original
text changes. But, yes, it is an annoying problem.

Ah, I see.
I did not expected this behaviour, but anyway: thanks for the clarification.

Post by Beatrice Torracca

Post by Holger Wansing
Means the "section=xxx" and "name=yyy" parts within <manref ... > are swapped,
leading to 18 fuzzy strings :-((
I remember such issue from years ago. But is this still an unfixed issue?
This way we cannot get the translations up-to-date, hrrrr ...
Is this known? How to deal with this?

See https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=725931
Anyway as far as I can see, the proposed work around is already implemented
in the Makefile of the faq that already contains "PERL_PERTURB_KEYS=0
PERL_HASH_SEED=0".

Post by Holger Wansing
Beatrice: which Debian version are you using? I wonder if the tools in Debian
unstable behave different from those in Debian stable (I'm trying to explain,
what happens here).
I am using Debian stable.

I am using testing.

Ok, but apparently this seems to of no relevance.


Thanks, Beatrice

Holger