Your message dated Sun, 04 Sep 2022 22:47:33 +0200
with message-id <[email protected]>
and subject line This is fixed upstream, and uploaded
has caused the Debian Bug report #1017837,
regarding po4a: This page defines a new macro - cannot get rid of error message
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
1017837: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1017837
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: po4a
Version: 0.67-2
Severity: normal
If I try to generate the pot file for e.g. icewm.1, using:
po4a-gettextize -f man --option groff_code=verbatim --option generated --option
untranslated="a.RE,\|" --option unknown_macros=untranslated --master
../upstream/debian-unstable/man1/icewm.1 -M utf-8 > /tmp/bazbar.pot
(Here ../upstream/debian-unstable/man1/icewm.1 refers to the man page
icewm.1 as found in icewm-common in debian-unstable).
I get the following error messages:
po4a::man: This page defines a new macro 'Sp \" Vertical space (when we can't
use .PP)' with '.de', but you did not specify the expected po4a behavior when
'Sp \" Vertical space (when we can't use .PP)' is used. You will get an error
if this macro is actually used in your page.
Add your macro to one of the 'untranslated', 'noarg', 'translate_joined',
'translate_each', 'no_wrap' or 'inline' parameters to avoid issues.
For example, passing '-o untranslated=Sp \" Vertical space (when we can't use
.PP)' to po4a will ensure that the defined macro remains hidden from
translators.
Please refer to the manpage of Locale::Po4a::Man for more info on these
parameters.
po4a::man: This page defines a new macro 'Vb \" Begin verbatim text' with
'.de', but you did not specify the expected po4a behavior when 'Vb \" Begin
verbatim text' is used. You will get an error if this macro is actually used in
your page.Add your macro to one of the 'untranslated', 'noarg',
'translate_joined', 'translate_each', 'no_wrap' or 'inline' parameters to avoid
issues.
For example, passing '-o untranslated=Vb \" Begin verbatim text' to po4a will
ensure that the defined macro remains hidden from translators.
Please refer to the manpage of Locale::Po4a::Man for more info on these
parameters.
po4a::man: This page defines a new macro 'Ve \" End verbatim text' with '.de',
but you did not specify the expected po4a behavior when 'Ve \" End verbatim
text' is used. You will get an error if this macro is actually used in your
page.
Add your macro to one of the 'untranslated', 'noarg', 'translate_joined',
'translate_each', 'no_wrap' or 'inline' parameters to avoid issues.
For example, passing '-o untranslated=Ve \" End verbatim text' to po4a will
ensure that the defined macro remains hidden from translators.
Please refer to the manpage of Locale::Po4a::Man for more info on these
parameters.
These messages are new, they are not present in older versions of po4a, e.g. in
stable.
So I try to do as the message says:
po4a-gettextize -f man --option groff_code=verbatim --option generated -o
untranslated=Sp \" Vertical space (when we can't use .PP) --option
unknown_macros=untranslated --master ../upstream/debian-unstable/man1/icewm.1
-M utf-8 > /tmp/bazbar.pot
-bash: Syntaxfehler beim unerwarteten Symbol »(«
(English: Syntax error at the unexpected symbol "(")
That one is easy, the suggestion misses quoting. Now:
po4a-gettextize -f man --option groff_code=verbatim --option generated -o
untranslated="Sp \" Vertical space (when we can't use .PP)" --option
unknown_macros=untranslated --master ../upstream/debian-unstable/man1/icewm.1
-M utf-8 > /tmp/bazbar.pot
po4a::man: This page defines a new macro 'Sp \" Vertical space (when we can't
use .PP)' with '.de', but you did not specify the expected po4a behavior when
'Sp \" Vertical space (when we can't use .PP)' is used. You will get an error
if this macro is actually used in your page.
Add your macro to one of the 'untranslated', 'noarg', 'translate_joined',
'translate_each', 'no_wrap' or 'inline' parameters to avoid issues.
For example, passing '-o untranslated=Sp \" Vertical space (when we can't use
.PP)' to po4a will ensure that the defined macro remains hidden from
translators.
Please refer to the manpage of Locale::Po4a::Man for more info on these
parameters.
po4a::man: This page defines a new macro 'Vb \" Begin verbatim text' with
'.de', but you did not specify the expected po4a behavior when 'Vb \" Begin
verbatim text' is used. You will get an error if this macro is actually used in
your page.Add your macro to one of the 'untranslated', 'noarg',
'translate_joined', 'translate_each', 'no_wrap' or 'inline' parameters to avoid
issues.
For example, passing '-o untranslated=Vb \" Begin verbatim text' to po4a will
ensure that the defined macro remains hidden from translators.
Please refer to the manpage of Locale::Po4a::Man for more info on these
parameters.
po4a::man: This page defines a new macro 'Ve \" End verbatim text' with '.de',
but you did not specify the expected po4a behavior when 'Ve \" End verbatim
text' is used. You will get an error if this macro is actually used in your
page.
Add your macro to one of the 'untranslated', 'noarg', 'translate_joined',
'translate_each', 'no_wrap' or 'inline' parameters to avoid issues.
For example, passing '-o untranslated=Ve \" End verbatim text' to po4a will
ensure that the defined macro remains hidden from translators.
Please refer to the manpage of Locale::Po4a::Man for more info on these
parameters.
And in both cases the output is the same (except the POT-Creation-Date of
course).
So this is the hard part, how to handle this error message, the
suggested solution does not change anything.
Background:
===========
With the new poo4a I get tons of these error messages, for many man
pages. This makes it very hard to spot real errors. The second best
option to resolve this is to filter those messages out (i.e. ignore
them) before reviewing the build logs.
-- System Information:
Debian Release: bookworm/sid
APT prefers testing
APT policy: (500, 'testing')
Architecture: amd64 (x86_64)
Kernel taint flags: TAINT_UNSIGNED_MODULE
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) (ignored: LC_ALL
set to de_DE.UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
Versions of packages po4a depends on:
ii gettext 0.21-8
ii libpod-parser-perl 1.65-1
ii libsgmls-perl 1.03ii-37
ii libsyntax-keyword-try-perl 0.27-1
ii libyaml-tiny-perl 1.73-1
ii opensp 1.5.2-13+b2
ii perl 5.34.0-5
Versions of packages po4a recommends:
ii liblocale-gettext-perl 1.07-4+b2
ii libterm-readkey-perl 2.38-2
ii libtext-wrapi18n-perl 0.06-9
ii libunicode-linebreak-perl 0.0.20190101-1+b4
po4a suggests no packages.
-- no debconf information
--
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
--- End Message ---
--- Begin Message ---
package po4a
fixed 1016753 0.68-1
fixed 1017837 0.68-1
thanks
signature.asc
Description: This is a digitally signed message part
--- End Message ---
