12:55 p.m.
hi,
i am using the XHTML module from po4a, and i would like to specify
attributes that i don't want to be translated.
i do know about the "untranslated" option, which i already use in some
places, but that option only applies to tags. here i would like to ignore
modifications done by translators on attributes of an inline tag.
example: the text "abc <a href=\"file.html\" target=\"_blank\"
title=\"link-name\"> def". as of now, the text appears as is in the .pot
file, and if a translator mistakenly translates \"file.html\" into
\"translated_name.html\", then the link will point to a non-existing page.
when a translator translates that text to "abc_translated <a
href=\"file_translated.html\" target=\"wrong_target\"
title=\"link-name_translated\"> def_translated", i would like
modifications
to the "href" and "target" attributes to be ignored. or as an
alternative
solution, simply exit po4a with an error stating that the translation file
is incorrect.
i assume there is no current way of doing it; i could try, but i don't know
Perl much and even less po4a. i have noticed the recent work on the XHTML
module (thanks for <br> and <u>, much appreciated!), so i was hoping a po4a
maintainer could give this a try.
otherwise, i would like pointers on where to start...
thanks,
poy
11:30 a.m.
New subject: [Po4a-devel] XML: prevent some attributes from being translated
Hi,
On Sun, Dec 14, 2008 at 07:55:45PM +0100, poy(a)123gen.com wrote:
example: the text "abc <a href=\"file.html\"
target=\"_blank\"
title=\"link-name\"> def". as of now, the text appears as is in the
.pot
file, and if a translator mistakenly translates \"file.html\" into
\"translated_name.html\", then the link will point to a non-existing page.
when a translator translates that text to "abc_translated <a
href=\"file_translated.html\" target=\"wrong_target\"
title=\"link-name_translated\"> def_translated", i would like
modifications
to the "href" and "target" attributes to be ignored. or as an
alternative
solution, simply exit po4a with an error stating that the translation file
is incorrect.
i assume there is no current way of doing it; i could try, but i don't know
Perl much and even less po4a. i have noticed the recent work on the XHTML
module (thanks for <br> and <u>, much appreciated!), so i was hoping a po4a
maintainer could give this a try.
otherwise, i would like pointers on where to start...
No, there are currently no way to do this.
In the next version, I would like to add "placeholder" tags.
In that case, it should be possible to po4a to generate such PO files:
msgid "abc_translated <placeholder a_1/> def_translated"
msgstr ""
msgid "content of the link"
msgstr ""
If the placeholder tag is specified as untranslatable, that should also do
the trick for you.
With the current version, the only think you can do is to execute some
scripts on the translation to check that translators did not change the
content of the links.
Best Regards,
--
Nekral
7 a.m.
New subject: [Po4a-devel] XML: prevent some attributes from being translated
thanks for your answer.
i was thinking about sub-classing "found_string" but i guess i'll just wait
for your placeholder idea which might just do the trick as well.
poy
4:57 p.m.
New subject: [Po4a-devel] XML: prevent some attributes from being translated
In the next version, I would like to add "placeholder"
tags.
In that case, it should be possible to po4a to generate such PO files:
msgid "abc_translated <placeholder a_1/> def_translated"
msgstr ""
msgid "content of the link"
msgstr ""
hi,
i have been playing with the current CVS version of po4a, especially these
placeholder changes.
in the command-line i use when calling po4a-gettextize, i add:
-o nodefault=<a> [to prevent <a> from being considered an inline tag]
-o placeholder=<a>
and it works like a charm! :)
i get exactly the result you wrote above, except that the placeholder tag is
"<placeholder0>".
now i have the following suggestions:
1) make it "<placeholder0/>" (slash added) instead? it would just look
more
correct, though if it works like this it's not much of a problem.
2) being able to define the name of that "placeholder" tag; eg, in my case,
i would like to call it "link".
3) the caption of the link is cut out of its context; i would love the
following:
msgid "abc <placeholder0>click here</placeholder0> def"
msgstr ""
#1 and #2 are really cosmetics; however, #3 is quite important in my mind,
because translators might get confused if the caption of the link has to be
translated elsewhere than in the sentence they are currently translating.
thanks,
poy
4:46 p.m.
New subject: [Po4a-devel] XML: prevent some attributes from being translated
On Sun, Feb 01, 2009 at 11:57:48PM +0100, poy(a)123gen.com wrote:
now i have the following suggestions:
1) make it "<placeholder0/>" (slash added) instead? it would just look
more correct, though if it works like this it's not much of a problem.
That one was implemented.
The placeholder is named <placeholder type=\"address\"
id=\"0\"/>
I received request to put the type to help the translator.
2) being able to define the name of that "placeholder" tag;
eg, in my
case, i would like to call it "link".
I need to find how to do this.
Messages in PO files should usually be independent from the context (e.g.
placeholders are numbered starting from 0 in the message, not in the
file).
Maybe I can use the line reference field for this (that would not be a
line reference anymore, but that's probably not a big issue). Currently,
the actual line in the document is used, but there might be better way to
identify the placeholder.
3) the caption of the link is cut out of its context; i would love
the
following:
msgid "abc <placeholder0>click here</placeholder0> def"
msgstr ""
I cannot do this in po4a.
This would require a standard to put links in PO files.
Best Regards,
--
Nekral
10:07 a.m.
New subject: [Po4a-devel] XML: prevent some attributes from being translated
> 3) the caption of the link is cut out of its context; i would
love the
> following:
> msgid "abc <placeholder0>click here</placeholder0> def"
> msgstr ""
I cannot do this in po4a.
This would require a standard to put links in PO files.
oh this is not what i meant... i don't want the ability to jump between one
translation and another inside a PO file, not at all.
i meant to show an example of a text which would be hard to translate if it
were cut out of its context, ie the fact that the text englobed in the
placeholder isn't inlined within the rest of the message.
a better example:
Welcome to our project. Make sure you download it from the <a
href="alioth.debian.../po4a">official site</a>!
that would result in these 2 separate translations:
msgid "Welcome to our project. Make sure you download it from the
<placeholder ... />!"
msgstr ""
msgid "official site"
msgstr ""
what i wanted was to embed the caption of the link (2nd translation) in the
1st, main translation, because often the context is relevant to the way the
caption of the link will have to be translated. something like:
msgid "Welcome to our project. Make sure you download it from the
<placeholder ... >official site</placeholder>!"
thanks,
poy
11:22 a.m.
New subject: [Po4a-devel] XML: prevent some attributes from being translated
On Mon, Feb 23, 2009 at 05:07:07PM +0100, poy(a)123gen.com wrote:
>> 3) the caption of the link is cut out of its context; i would
love the
>> following:
>> msgid "abc <placeholder0>click here</placeholder0> def"
>> msgstr ""
>
> I cannot do this in po4a.
> This would require a standard to put links in PO files.
oh this is not what i meant... i don't want the ability to jump between
one translation and another inside a PO file, not at all.
i meant to show an example of a text which would be hard to translate if
it were cut out of its context, ie the fact that the text englobed in the
placeholder isn't inlined within the rest of the message.
a better example:
Welcome to our project. Make sure you download it from the <a
href="alioth.debian.../po4a">official site</a>!
that would result in these 2 separate translations:
Yes, it might be a drawback of placeholders.
But it will highly depend on which tags are added to the placeholder
category. Currently, Xhtml has none.
You can have a look at Docbook.pm, where I added more placeholders (e.g.
<address>, <cmdsynopsis>, many <*info>, <example>, <figure>,
<footnote>,
<funcprototype>, ...)
If useful, I could also provide an option to indicate that placeholders
should be changed to inline if they have less than XXX characters.
Currently, I don't think it is necessary. Placeholders should be used when
the block is context free enough so that translation can be reused.
Best Regards,
--
Nekral
12:17 p.m.
New subject: [Po4a-devel] XML: prevent some attributes from being translated
If useful, I could also provide an option to indicate that
placeholders
should be changed to inline if they have less than XXX characters.
Currently, I don't think it is necessary. Placeholders should be used when
the block is context free enough so that translation can be reused.
such an option would be just fine, i would always use it regardless of the
number of chars.
i understand the purpose of placeholders and how useful they must be for
other modules, it's just that without inlining i can't use them for html
links. good job though!
maybe placeholders are just not the right way to go around this; i've
thought of simple regexp replacements so that:
<a href=... target=...>link text</a>
in the master document is changed into:
<link>link text</link>
in the pot file.
the challenge then will be to replace <link>s back into corresponding <a
...> tags when generating translated pages.
poy
5:59 p.m.
New subject: [Po4a-devel] XML: prevent some attributes from being translated
On Mon, Feb 23, 2009 at 07:17:10PM +0100, poy(a)123gen.com wrote:
> If useful, I could also provide an option to indicate that
placeholders
> should be changed to inline if they have less than XXX characters.
> Currently, I don't think it is necessary. Placeholders should be used when
> the block is context free enough so that translation can be reused.
such an option would be just fine, i would always use it regardless of
the number of chars.
i understand the purpose of placeholders and how useful they must be for
other modules, it's just that without inlining i can't use them for html
links. good job though!
In that case, the option is useless. Defining tags as inline instead of
placeholder would have the same result.
maybe placeholders are just not the right way to go around this;
i've
thought of simple regexp replacements so that:
<a href=... target=...>link text</a>
in the master document is changed into:
<link>link text</link>
in the pot file.
the challenge then will be to replace <link>s back into corresponding <a
...> tags when generating translated pages.
I will need to identify the <link> by adding an ID (otherwise, I cannot
support "<link>txt1</link> <link>txt2</link>" to be
translated to
"<link>txt2</link> <link>txt1</link>"
I will probably also need a type attribute to help translator finding what
kind of tag it is.
But in that case, <a href=... target=...> is probably much clearer.
The goal of placeholders was not to hide something, but to help splitting
blocks, without loosing too much context.
To hide attributes of tags, but keeping the tag's content inline, another
option could be added.
It could change <tag attributes=...> to <tag id=#>.
This could be used to avoid typos to be introduced in attributes if they
are known to be untranslatable, and to reduce the amount of data that need
to be translated.
Best Regards,
--
Nekral
3:23 a.m.
New subject: [Po4a-devel] XML: prevent some attributes from being translated
On Tue, Feb 24, 2009 at 12:59:30AM +0100, Nicolas François wrote:
I will need to identify the <link> by adding an ID (otherwise, I cannot
support "<link>txt1</link> <link>txt2</link>" to be
translated to
"<link>txt2</link> <link>txt1</link>"
But in that case, <a href=... target=...> is probably much clearer.
Actually I think Poy's idea is great: when translating you
don't really care where the link goes, and all the
attributes end up being clutter more than anything else.
The goal of placeholders was not to hide something, but to help
splitting
blocks, without loosing too much context.
BTW, I must be dense, but I can't understand the help in
Xml.pm about placeholders. Even through the discussion here
I'm not sure at all what they're for and how they work (I
have to admit I haven't followed the development of Po4a
much since 2006 or so, though).
To hide attributes of tags, but keeping the tag's content inline,
another
option could be added.
It could change <tag attributes=...> to <tag id=#>.
This could be used to avoid typos to be introduced in attributes if they
are known to be untranslatable, and to reduce the amount of data that need
to be translated.
That'd be a nice thing to have in Xml, a list of 'foldable'
tags to hide away markup clutter.
Cheers,
Y.
5:57 p.m.
New subject: [Po4a-devel] XML: prevent some attributes from being translated
On Tue, Feb 24, 2009 at 10:23:35AM +0100, debian.anti-spam(a)rutschle.net wrote:
On Tue, Feb 24, 2009 at 12:59:30AM +0100, Nicolas François wrote:
> The goal of placeholders was not to hide something, but to help splitting
> blocks, without loosing too much context.
BTW, I must be dense, but I can't understand the help in
Xml.pm about placeholders. Even through the discussion here
I'm not sure at all what they're for and how they work (I
have to admit I haven't followed the development of Po4a
much since 2006 or so, though).
Just for the record. The idea about placeholder was to avoid very long
paragraphs, which are very hard to translate and maintain.
Here is an example:
#. type: Content of: <sect1><sect2><para><footnote><para>
#: boot-installer/trouble.xml:330
msgid ""
"The parameter <userinput>vga=788</userinput> will activate the VESA
"
"framebuffer with a resolution of 800x600. This will probably work, but may "
"not be the optimal resolution for your system. A list of supported "
"resolutions can be obtained by using <userinput>vga=ask</userinput>, but
you "
"should be aware that list may not be complete."
msgstr ""
#. type: Content of: <sect1><sect2><para>
#: boot-installer/trouble.xml:324
msgid ""
"Some systems (especially laptops) that have a native resolution that is not "
"a 4:3 ratio (i.e. not for example 800x600 or 1024x768) may have a blank "
"display after the installer has been booted. In that case adding the boot "
"parameter <userinput>vga=788</userinput><placeholder
type=\"footnote\" "
"id=\"0\"/> may help. If that does not work, try adding the boot
parameter "
"<userinput>fb=false</userinput>."
msgstr ""
More to come for the new option...
--
Nekral
8:19 a.m.
New subject: [Po4a-devel] XML: prevent some attributes from being translated
To hide attributes of tags, but keeping the tag's content inline,
another
option could be added.
It could change <tag attributes=...> to <tag id=#>.
This could be used to avoid typos to be introduced in attributes if they
are known to be untranslatable, and to reduce the amount of data that need
to be translated.
yes this sounds great. i don't really care if <a>s are changed into
<link>s
or not; it actually makes more sense to just keep them as <a>s.
regarding whether adding id="#" adds clutter, in the case of our links, many
of them look like:
"supports connection to hubs using the earlier <a
href=\"http://en.wikipedia.org/wiki/Direct_Connect_network\"
target=\"_blank\" class=\"external\">NeoModus Direct Connect
(NMDC)</a>
protocol"
so yes, changing [href= target= class=] into a simple id="#" tag is much
neater.
this could be useful in other places too, for example with <span> tags when
these specify complicated CSS styles.
thanks,
poy
6:05 p.m.
New subject: [Po4a-devel] XML: prevent some attributes from being translated
Hi,
On Tue, Feb 24, 2009 at 03:19:59PM +0100, poy(a)123gen.com wrote:
> To hide attributes of tags, but keeping the tag's content
inline, another
> option could be added.
> It could change <tag attributes=...> to <tag id=#>.
> This could be used to avoid typos to be introduced in attributes if they
> are known to be untranslatable, and to reduce the amount of data that need
> to be translated.
yes this sounds great. i don't really care if <a>s are changed into
<link>s or not; it actually makes more sense to just keep them as <a>s.
Let's talk about the user interface now.
What the option should look like?
It seems to me that this would be useful for inline tags only.
I would propose to use another modifier before the tag. For example:
A<a>
(A for "no attributes")
or
f<a>
(f for foldable)
You seems to also want an option to specify that all attributes of inline
tags should be folded.
I propose to add an 'a' or 'A' (or 'f' or 'F') to
defaulttranslateoption
Do you have other ideas?
Best Regards,
--
Nekral
2:43 a.m.
New subject: [Po4a-devel] XML: prevent some attributes from being translated
Let's talk about the user interface now.
What the option should look like?
It seems to me that this would be useful for inline tags only.
I would propose to use another modifier before the tag. For example:
A<a>
(A for "no attributes")
or
f<a>
(f for foldable)
You seems to also want an option to specify that all attributes of inline
tags should be folded.
I propose to add an 'a' or 'A' (or 'f' or 'F') to
defaulttranslateoption
Do you have other ideas?
for specific tags, 'f' for "foldable" sounds reasonable to me. however,
i
understand that 'defaulttranslateoption' is for tags that were not specified
in any other category, right?
as there's already '_default_break', '_default_inline',
'_default_placeholder', how about adding '_default_foldable', and changing
the '_default_inline' found in Xhtml.pm to a '_default_foldable' list
instead, thus marking all inline tags as also foldable? for XHTML at least,
i can't see any reason for an inline tag not to be foldable too.
and yes, any foldable tag is considered inline, it doesn't make any sense to
fold its attributes if these aren't going to be included in the translation
file.
so perhaps keep them tags in '_default_inline', and instead have a bool
option called 'fold_inline_tags'? these are really implementation details
and i trust your judgement in knowing how to expose the option the easiest
way.
thanks,
poy
3:57 p.m.
New subject: [Po4a-devel] XML: prevent some attributes from being translated
Hello,
I've added a foldattributes option to the Xml module.
(The name can change until it appear in a release ;)
I did not add a 'f' modifier yet. This will probably no appear before the
next release. Lets get some feedback first.
Kind Regards,
--
Nekral
4:50 p.m.
New subject: [Po4a-devel] XML: prevent some attributes from being translated
Hello,
I've added a foldattributes option to the Xml module.
(The name can change until it appear in a release ;)
hi, thanks, this is great news! i've done a quick test (by passing "-o
foldattributes" in command-line to po4a-gettextize), and my links were
changed to tags like:
<a po4a-id=0>
- i'm not sure whether "=0" without quotes around "0" is valid;
but in any
case this is only as a help to translators, so better just leave it as is.
- to translate back, i did not have to pass any option to po4a-translate; it
automatically guessed that po4a-id attributes had to be unfolded. that's
nifty, but if one were forced to pass "-o foldattributes" to po4a-translate,
above tag could become:
<a id=0>
which is even simpler. there would be no confusion as to whether that "id"
attribute comes from po4a or not: if po4a-translate was called with "-o
foldattributes", then the "id" attribute has to be unfolded to actual
attributes (which may even be real "id" attributes); otherwise, if no option
passed, then leave attributes untouched.
I did not add a 'f' modifier yet. This will probably no
appear before the
next release. Lets get some feedback first.
i thought you did, i saw some when skimming through the diff. haven't tested
it though.
for my XHTML usage, this global boolean switch is perfectly fine.
thanks,
poy
5:24 p.m.
New subject: [Po4a-devel] XML: prevent some attributes from being translated
On Mon, Mar 02, 2009 at 11:50:00PM +0100, poy(a)123gen.com wrote:
> Hello,
>
> I've added a foldattributes option to the Xml module.
> (The name can change until it appear in a release ;)
hi, thanks, this is great news! i've done a quick test (by passing "-o
foldattributes" in command-line to po4a-gettextize), and my links were
changed to tags like:
<a po4a-id=0>
- i'm not sure whether "=0" without quotes around "0" is valid;
but in
any case this is only as a help to translators, so better just leave it
as is.
It's probably not
(http://www.w3.org/TR/2008/REC-xml-20081126/#NT-AttValue)
but widely I think used, and quotes are too boring in PO files ;)
- to translate back, i did not have to pass any option to
po4a-translate;
it automatically guessed that po4a-id attributes had to be unfolded.
that's nifty, but if one were forced to pass "-o foldattributes" to
I think it's a bug.
Can you check again (i.e. having the translation different from the
original string).
po4a-translate, above tag could become:
<a id=0>
which is even simpler. there would be no confusion as to whether that
"id" attribute comes from po4a or not: if po4a-translate was called with
"-o foldattributes", then the "id" attribute has to be unfolded to
actual
attributes (which may even be real "id" attributes); otherwise, if no
option passed, then leave attributes untouched.
This works with the foldattributes option, but might be confusing if the
'f' modifier gets implemented. Also if the id attribute exist for a tag,
translators may think they can change it.
I also think it is too long. An option could be to use a slightly invalid
XML construct <tag 0>, or a very improbable valid XML construct <tag-0>
Best Regards,
--
Nekral
5:44 p.m.
New subject: [Po4a-devel] XML: prevent some attributes from being translated
> - to translate back, i did not have to pass any option to
po4a-translate;
> it automatically guessed that po4a-id attributes had to be unfolded.
> that's nifty, but if one were forced to pass "-o foldattributes" to
I think it's a bug.
Can you check again (i.e. having the translation different from the
original string).
when i pass "-o foldattributes" to po4a-translate, it translates and unfolds
everything correctly.
when i don't, it unfolds attributes but it doesn't translate strings that
contained foldable attributes (it does translate other standard strings,
however). it's indeed confusing and a check would be good to avoid this
mistake.
I also think it is too long. An option could be to use a slightly
invalid
XML construct <tag 0>, or a very improbable valid XML construct <tag-0>
sure, these look good, just pick the easier to implement. :)
poy
6:19 p.m.
New subject: [Po4a-devel] XML: prevent some attributes from being translated
On Tue, Mar 03, 2009 at 12:44:59AM +0100, poy(a)123gen.com wrote:
>> - to translate back, i did not have to pass any option to
po4a-translate;
>> it automatically guessed that po4a-id attributes had to be unfolded.
>> that's nifty, but if one were forced to pass "-o foldattributes"
to
>
> I think it's a bug.
> Can you check again (i.e. having the translation different from the
> original string).
when i pass "-o foldattributes" to po4a-translate, it translates and
unfolds everything correctly.
when i don't, it unfolds attributes but it doesn't translate strings that
contained foldable attributes (it does translate other standard strings,
however). it's indeed confusing and a check would be good to avoid this
mistake.
I cannot do that.
po4a-gettextize extracts the strings from the document.
po4a-translate extracts the strings from the document, then look for the
translation of these strings in the PO file to generate the translated
document.
If the 2 sets of extracted strings differ, then it is as providing an
outdated PO file.
The options should always be the same for each invocation of po4a.
Best Regards,
--
Nekral
4:55 p.m.
New subject: [Po4a-devel] XML: prevent some attributes from being translated
just noticed that if i change the content of a tag, that content isn't
translated; eg:
#. type: Content of: <html><body>
#: test.html:19
msgid "abc <a po4a-id=0>link!</a> def"
msgstr "abc <a po4a-id=0>lioonk!</a> def"
is changed to:
abc <a href="correct_link.html" target="bla">link!</a>
def
in the translated document. "link!" wasn't translated into
"lioonk!";
attributes were correctly folded and unfolded, however.
poy
5:26 p.m.
New subject: [Po4a-devel] XML: prevent some attributes from being translated
On Mon, Mar 02, 2009 at 11:55:21PM +0100, poy(a)123gen.com wrote:
just noticed that if i change the content of a tag, that content
isn't
translated; eg:
#. type: Content of: <html><body>
#: test.html:19
msgid "abc <a po4a-id=0>link!</a> def"
msgstr "abc <a po4a-id=0>lioonk!</a> def"
is changed to:
abc <a href="correct_link.html" target="bla">link!</a>
def
in the translated document. "link!" wasn't translated into
"lioonk!";
attributes were correctly folded and unfolded, however.
Can you re-check with -o foldattributes set for po4a-translate?
Given your previous mesage, that's my current guess.
--
Nekral
5:33 p.m.
New subject: [Po4a-devel] XML: prevent some attributes from being translated
Can you re-check with -o foldattributes set for po4a-translate?
Given your previous mesage, that's my current guess.
good guess, sorry, it works as expected when passing the option to
po4a-translate.
poy
1:24 p.m.
New subject: [Po4a-devel] XML: prevent some attributes from being translated
hi,
i have tried turning on the "foldattributes" option on our whole project,
and it seems the generated .pot file sometimes has weird numbering regarding
po4a-id attributes.
it seems that the po4a-id number isn't always reset to 0; if a translation
has multiple foldable attributes, eg:
msgid "<span po4a-id=0>aaa</span> <span po4a-id=1>bbb</span>
<span
po4a-id=2>ccc</span>"
then on the next (totally unrelated, could even be in a separate file)
translation, the po4a-id counter stays at 2, so i will get something like:
msgid "blah <a po4a-id=2>blah</a> <span po4a-id=3>blah</span>
..."
and etc.
as a result, by the end of the .pot file, i find things like:
msgid ""
"TLS can't be used because no certificate files set. You should set or "
"generate them properly in the <a po4a-id=78>Security certificates</a>
page."
poy
2:08 p.m.
New subject: [Po4a-devel] XML: prevent some attributes from being translated
----- Original Message -----
From: "poy" <poy(a)123gen.com>
To: <po4a-devel(a)lists.alioth.debian.org>
Sent: Sunday, March 08, 2009 7:24 PM
Subject: Re: [Po4a-devel] XML: prevent some attributes from being translated
hi,
i have tried turning on the "foldattributes" option on our whole project,
and it seems the generated .pot file sometimes has weird numbering
regarding
po4a-id attributes.
it seems that the po4a-id number isn't always reset to 0; if a translation
has multiple foldable attributes, eg:
msgid "<span po4a-id=0>aaa</span> <span po4a-id=1>bbb</span>
<span
po4a-id=2>ccc</span>"
then on the next (totally unrelated, could even be in a separate file)
translation, the po4a-id counter stays at 2, so i will get something like:
msgid "blah <a po4a-id=2>blah</a> <span
po4a-id=3>blah</span> ..."
and etc.
as a result, by the end of the .pot file, i find things like:
msgid ""
"TLS can't be used because no certificate files set. You should set or "
"generate them properly in the <a po4a-id=78>Security certificates</a>
page."
oh, and translation of texts containing these wrongly-numbered ids doesn't
work.
here's a test-case:
<p>
abc <a href="correct_link.html" target="bla">link!</a> def
<a
href="link2.html">link2</a> x <span
style="">span1</span> b <a h=0>a3</a>
<span x=y>span2</span>bbbbbb
</p>
<p>
abcd <a xx=yy>sss</a>
</p>
the 1st paragraph is ok in the .pot file, but the 2nd appears as:
msgid "abcd <a po4a-id=5>sss</a>"
instead of:
msgid "abcd <a po4a-id=0>sss</a>"
hence the 2nd paragraph (and all subsequent translations that will contain a
po4a-id) is impossible to translate.
poy
4:25 p.m.
New subject: [Po4a-devel] XML: prevent some attributes from being translated
Hello,
This should be fixed in CVS now.
Best Regards,
--
Nekral
4:54 p.m.
New subject: [Po4a-devel] XML: prevent some attributes from being translated
----- Original Message -----
From: "Nicolas François" <nicolas.francois(a)centraliens.net>
To: <po4a-devel(a)lists.alioth.debian.org>
Sent: Sunday, March 08, 2009 10:25 PM
Subject: Re: [Po4a-devel] XML: prevent some attributes from being translated
Hello,
This should be fixed in CVS now.
Best Regards,
--
Nekral
_______________________________________________
Po4a-devel mailing list
Po4a-devel(a)lists.alioth.debian.org
http://lists.alioth.debian.org/mailman/listinfo/po4a-devel
perfect, thanks!
poy
5528
days inactive
5612
days old
25 comments
3 participants
participants (3)
-
Nicolas François -
poy -
Yves Rutschle