5:06 a.m.
Hi,
I'm currently trying to use po4a for the aptitude documentation, and
here are the few problems I have:
* if there is a comment in a sentence such as
In the <!-- TODO: <link linkend='secHier'>
-->hierarchy editor, stores the hierarchy location
then the result will be:
msgid "In the"
msgstr ""
msgid "hierarchy editor, stores the hierarchy location"
msgstr ""
* the <screen> tag in Docbook must be set as translatable and "no-wrap"
It is easy to fix in Docbook.pm, please just add in the tags option:
+ W<screen>
* if there is a footnote, such as
<para>
Begining of the sentence
<footnote><para>footnote text</para></footnote>
end of the sentence.
</para>
then once again it will be divided into three strings:
msgid "Begining of the sentence"
msgid "footnote text"
msgid "end of the sentence."
I'm afraid that for this last problem, there is no easy solution and
we will have to keep the current situation.
* In the Debian package, there is still the encoding problem in the xml
header, which has been fixed in the CVS version. I'm waiting for a new
release :-)
Thanks for your work.
Cheers,
--
Thomas Huriaux
10 a.m.
New subject: [Po4a-devel] Re: Problems with Docbook/Xml module
Hi again,
Thomas Huriaux <thomas.huriaux(a)kti.ae.poznan.pl> (21/10/2005):
I'm currently trying to use po4a for the aptitude documentation,
and
here are the few problems I have:
* if there is a comment in a sentence such as
In the <!-- TODO: <link linkend='secHier'>
-->hierarchy editor, stores the hierarchy location
then the result will be:
msgid "In the"
msgstr ""
msgid "hierarchy editor, stores the hierarchy location"
msgstr ""
* the <screen> tag in Docbook must be set as translatable and "no-wrap"
It is easy to fix in Docbook.pm, please just add in the tags option:
+ W<screen>
* if there is a footnote, such as
<para>
Begining of the sentence
<footnote><para>footnote text</para></footnote>
end of the sentence.
</para>
then once again it will be divided into three strings:
msgid "Begining of the sentence"
msgid "footnote text"
msgid "end of the sentence."
I'm afraid that for this last problem, there is no easy solution and
we will have to keep the current situation.
* In the Debian package, there is still the encoding problem in the xml
header, which has been fixed in the CVS version. I'm waiting for a new
release :-)
Another problem found:
<book lang="en">
will be translated
<book lang="fr
"
I think the solution is to modify Xml.pm as following:
if ($options->{'type'} eq "tag") {
[...]
} elsif ($options->{'type'} eq "attribute") {
$comment =
"Attribute'".$options->{'attribute'}."' of:
".$self->get_path;
$wrap = 0;
} else {
i.e. to force $wrap = 0 for the attributes;
A related question: is there any way if the original does not contain
the lang="en" attribute to add it in the translations? I don't think,
but we never know.
Cheers,
--
Thomas Huriaux
6:52 a.m.
New subject: [Po4a-devel] Re: Problems with Docbook/Xml module
On Fri, Oct 21, 2005 at 05:00:29PM +0200, thomas.huriaux(a)kti.ae.poznan.pl wrote:
Hi again,
Another problem found:
<book lang="en">
will be translated
<book lang="fr
"
I think the solution is to modify Xml.pm as following:
if ($options->{'type'} eq "tag") {
[...]
} elsif ($options->{'type'} eq "attribute") {
$comment =
"Attribute'".$options->{'attribute'}."' of:
".$self->get_path;
$wrap = 0;
} else {
i.e. to force $wrap = 0 for the attributes;
I think this problem is more generic.
Attached is a patch for the Po.pm module.
(It restore exactly the same spaces at the end of the wrap method)
The problem is that it may have some consequences on many modules.
I will make some tests, and I would appreciate others' opinion.
A related question: is there any way if the original does not
contain
the lang="en" attribute to add it in the translations? I don't think,
but we never know.
I don't think it's possible at this time.
--
Nekral
2:14 p.m.
New subject: [Po4a-devel] Problems with Docbook/Xml module
Hi Thomas,
On Fri, Oct 21, 2005 at 12:06:06PM +0200, thomas.huriaux(a)kti.ae.poznan.pl wrote:
Hi,
I'm currently trying to use po4a for the aptitude documentation, and
here are the few problems I have:
* if there is a comment in a sentence such as
In the <!-- TODO: <link linkend='secHier'>
-->hierarchy editor, stores the hierarchy location
then the result will be:
msgid "In the"
msgstr ""
msgid "hierarchy editor, stores the hierarchy location"
msgstr ""
Can anyone check the attached patch?
It makes the comments non-breaking, and just removes them from the
paragraphs.
* the <screen> tag in Docbook must be set as translatable and
"no-wrap"
It is easy to fix in Docbook.pm, please just add in the tags option:
+ W<screen>
Done. Thanks.
* if there is a footnote, such as
<para>
Begining of the sentence
<footnote><para>footnote text</para></footnote>
end of the sentence.
</para>
then once again it will be divided into three strings:
msgid "Begining of the sentence"
msgid "footnote text"
msgid "end of the sentence."
I'm afraid that for this last problem, there is no easy solution and
we will have to keep the current situation.
There must be a way to indicate that the footnote tag should never be
separated from its paragraph.
However, it is not perfect (because you will want to extract the footnot
if it appear at the end of a paragraph).
The TeX module uses the following method: if the tag appears at the end of
a bloc, it is extracted, otherwise, we let the tag inlined in the
paragraph.
* In the Debian package, there is still the encoding problem in the
xml
header, which has been fixed in the CVS version. I'm waiting for a new
release :-)
seconded ;)
Kind Regards,
--
Nekral
6:30 a.m.
New subject: [Po4a-devel] Problems with Docbook/Xml module
Nicolas François <nicolas.francois(a)centraliens.net> (21/10/2005):
Hi Thomas,
Hi again,
On Fri, Oct 21, 2005 at 12:06:06PM +0200,
thomas.huriaux(a)kti.ae.poznan.pl wrote:
> I'm currently trying to use po4a for the aptitude documentation, and
> here are the few problems I have:
> * if there is a comment in a sentence such as
> In the <!-- TODO: <link linkend='secHier'>
> -->hierarchy editor, stores the hierarchy location
> then the result will be:
> msgid "In the"
> msgstr ""
>
> msgid "hierarchy editor, stores the hierarchy location"
> msgstr ""
Can anyone check the attached patch?
It makes the comments non-breaking, and just removes them from the
paragraphs.
It works perfectly, at least for aptitude. Thanks.
> * if there is a footnote, such as
> <para>
> Begining of the sentence
> <footnote><para>footnote text</para></footnote>
> end of the sentence.
> </para>
> then once again it will be divided into three strings:
> msgid "Begining of the sentence"
> msgid "footnote text"
> msgid "end of the sentence."
>
> I'm afraid that for this last problem, there is no easy solution and
> we will have to keep the current situation.
There must be a way to indicate that the footnote tag should never be
separated from its paragraph.
However, it is not perfect (because you will want to extract the footnot
if it appear at the end of a paragraph).
The TeX module uses the following method: if the tag appears at the end of
a bloc, it is extracted, otherwise, we let the tag inlined in the
paragraph.
Do you intend to fix it before the next release? I'm waiting to know
approximatly how the next release of po4a will be to ask Jean-Luc Coulon
to update the French translation of the aptitude documentation in order
to detect potential additional problems. It could be better if he works
on a "stable" po file.
Have you seen my other mail addressing the problem with the attributes?
Cheers,
--
Thomas Huriaux
10:02 a.m.
New subject: [Po4a-devel] Problems with Docbook/Xml module
On Sat, Oct 22, 2005 at 01:30:02PM +0200, thomas.huriaux(a)kti.ae.poznan.pl wrote:
Nicolas François <nicolas.francois(a)centraliens.net>
(21/10/2005):
> On Fri, Oct 21, 2005 at 12:06:06PM +0200, thomas.huriaux(a)kti.ae.poznan.pl wrote:
> > I'm currently trying to use po4a for the aptitude documentation, and
> > here are the few problems I have:
> > * if there is a comment in a sentence such as
> > In the <!-- TODO: <link linkend='secHier'>
> > -->hierarchy editor, stores the hierarchy location
> > then the result will be:
> > msgid "In the"
> > msgstr ""
> >
> > msgid "hierarchy editor, stores the hierarchy location"
> > msgstr ""
>
> Can anyone check the attached patch?
> It makes the comments non-breaking, and just removes them from the
> paragraphs.
It works perfectly, at least for aptitude. Thanks.
> > * if there is a footnote, such as
> > <para>
> > Begining of the sentence
> > <footnote><para>footnote text</para></footnote>
> > end of the sentence.
> > </para>
> > then once again it will be divided into three strings:
> > msgid "Begining of the sentence"
> > msgid "footnote text"
> > msgid "end of the sentence."
> >
> > I'm afraid that for this last problem, there is no easy solution and
> > we will have to keep the current situation.
>
> There must be a way to indicate that the footnote tag should never be
> separated from its paragraph.
>
> However, it is not perfect (because you will want to extract the footnot
> if it appear at the end of a paragraph).
>
> The TeX module uses the following method: if the tag appears at the end of
> a bloc, it is extracted, otherwise, we let the tag inlined in the
> paragraph.
Do you intend to fix it before the next release? I'm waiting to know
approximatly how the next release of po4a will be to ask Jean-Luc Coulon
to update the French translation of the aptitude documentation in order
to detect potential additional problems. It could be better if he works
on a "stable" po file.
It's more complicated than expected: The problem is not with the <footnote>
tag (which is already in the inline category). The problem is caused by
the <para> tag, which impose the break in the footnote.
I don't know what can be done. Don't expect it in the next release.
Thus, with the following paragraph:
<para>
Begining of the sentence
<footnote><para>footnote text</para></footnote>
end of the sentence.
</para>
The following 3 messages are generated:
msgid "Begining of the sentence <footnote>"
msgid "footnote text"
msgid "</footnote> end of the sentence."
Maybe we could do as in poxml (or xml2po, I don't remember). When they
encounter something like this, they use something like:
msgid "footnote text"
msgid "Begining of the sentence <placeholder -1/> end of the sentence."
Kind Regards,
--
Nekral
9:50 p.m.
New subject: [Po4a-devel] Problems with Docbook/Xml module
Hi!
2005/10/22, Nicolas François:
It's more complicated than expected: The problem is not with the
<footnote>
tag (which is already in the inline category). The problem is caused by
the <para> tag, which impose the break in the footnote.
I don't know what can be done. Don't expect it in the next release.
IIRC, the XML module is ready to handle this. You can add
"<footnote><para>" to the inline option. It's a documented but
currently unused feature. I hope it works! :D
Regards,
Jordi Vilalta
7:49 a.m.
New subject: [Po4a-devel] Problems with Docbook/Xml module
Hello,
On Sun, Oct 23, 2005 at 04:50:55AM +0200, jvprat(a)gmail.com wrote:
Hi!
2005/10/22, Nicolas François:
> It's more complicated than expected: The problem is not with the
<footnote>
> tag (which is already in the inline category). The problem is caused by
> the <para> tag, which impose the break in the footnote.
>
> I don't know what can be done. Don't expect it in the next release.
IIRC, the XML module is ready to handle this. You can add
"<footnote><para>" to the inline option. It's a documented but
currently unused feature. I hope it works! :D
This is not possible at this time.
When an inline tag is found, it is not added to the tags path.
Thus, in:
<para>
foo
<footnote>
<para>
bar
</para>
</footnote>
</para>
The tags path for "bar" is <para><para>, so
<footnote><para> never match.
I attach a patch that should fix this.
I used it for the aptitude man page. I had to remove the <arg> and
<replaceable> tags from the Docbook module [0].
Then I used the following options:
-o tags="<arg><replaceable> <term><replaceable>"
-o inline="<arg> <literal><replaceable>
<para><replaceable> <filename><replaceable>"
This permitted do reduce the number of strings from 186 to 130 on the
aptitude man page (the aptitude commands and options are no more
translatable, and some strings are grouped and provide more context).
(The choice of the above options are quite empirical and are probably only
valid for this aptitude man page. I don't plan to add these options to the
default tags in the Docbook module. This is just to show that it permits
to do what I want.)
[0] This is IMO another issue: it is not possible to remove a tag from the
default list. It could be better, when a tag is provided in an
option, to first remove it from the default categories. For example,
putting <arg> in the inline category (-o inline="<arg>") is not
perfect because <arg> will also stay in the 'tags' category.
I will submit a patch for this later.
Cheers,
--
Nekral
9:37 p.m.
New subject: [Po4a-devel] Problems with Docbook/Xml module
Hello,
2005/10/21, Nicolas François:
There must be a way to indicate that the footnote tag should never
be
separated from its paragraph.
However, it is not perfect (because you will want to extract the footnot
if it appear at the end of a paragraph).
The TeX module uses the following method: if the tag appears at the end of
a bloc, it is extracted, otherwise, we let the tag inlined in the
paragraph.
I think it isn't a good solution (at least for the XML module, I don't
know about the TeX one), because the position of the footnote may
change in the translation, and extracting it alone doesn't allow it.
Regards,
Jordi Vilalta
9:56 a.m.
New subject: [Po4a-devel] Problems with Docbook/Xml module
Nicolas François <nicolas.francois(a)centraliens.net> (21/10/2005):
> * the <screen> tag in Docbook must be set as translatable
and "no-wrap"
> It is easy to fix in Docbook.pm, please just add in the tags option:
> + W<screen>
Done. Thanks.
Another similar problem:
In the manpage of aptitude, there is the following string:
<term><literal>-q<arg
choice='opt'>=<replaceable>n</replaceable></arg></literal>,
<literal>--quiet<arg
choice='opt'>=<replaceable>n</replaceable></arg></literal></term>
which is gettextized as following:
# type: Content of:
# <refentry><refsect1><variablelist><varlistentry><term>
#: en/manpage.xml:827
msgid "<literal>-q"
msgstr ""
# type: Content of:
#
<book><chapter><section><variablelist><varlistentry><term>
#: en/manpage.xml:827
msgid "=<replaceable>n</replaceable>"
msgstr ""
# type: Content of:
#
<book><chapter><section><variablelist><varlistentry><term>
#: en/manpage.xml:827
msgid "</literal>, <literal>--quiet"
msgstr ""
# type: Content of:
# <refentry><refsect1><variablelist><varlistentry><term>
#: en/manpage.xml:827
msgid "</literal>"
msgstr ""
Shouldn't the <arg> tag treated as inline?
Cheers,
--
Thomas Huriaux
3:25 p.m.
New subject: [Po4a-devel] Problems with Docbook/Xml module
Hello Thomas,
On Tue, Nov 08, 2005 at 04:56:11PM +0100, thomas.huriaux(a)gmail.com wrote:
Shouldn't the <arg> tag treated as inline?
I'm not sure of this.
This may be an issue for:
<arg choice='opt'
rep='repeat'><replaceable>options</replaceable></arg>
or
<arg choice='plain' rep='repeat'>packages</arg>
(Also in the aptitude man page)
Here, "options" and "packages" must be translated.
Maybe (-o inline="<arg>") can be specified if <replaceable> is
always
used when the argument must be translated.
In this case (-o tags="<arg><replaceable>") should be specified to
indicate that the "options" and "packages" arguments must be
translated.
(But I can't make it work currently. This seems to be caused by the
inline="<arg>")
I will investigate this.
Cheers,
--
Nekral
6979
days inactive
7001
days old
10 comments
4 participants
participants (4)
-
Jordi Vilalta -
Nicolas François -
Thomas Huriaux -
Thomas Huriaux