Problem with i18n:name + i18n:translate

Hi all,

We just noticed a problem (bug?) in
PlacelessTranslationService: If
you have a structure like

<p i18n:translate="text_foo">You need to
go <a i18n:name="back"
i18n:translate="snippet_back"
href="bar">back</a> to where you came
from.</p>

and the language used by the viewer doesn't contain
translations for
these strings "text_foo" and
"snippet_back", then the rendered page is
something like:

<p>You nede to go <a href="bar">to
where you came from.</p>

which is just plain wrong! If the translation strings are
present,
rendering is done properly.

This can be fixed by rewriting to something like this:

<p i18n:translate="text_foo">You need to
go <span i18n:name="back">
<a i18n:translate="snippet_back"
href="bar">back</a></span> to
where
you came from.</p> 

effectively separating the i18n:name and i18n:translate to
separate
tags. Is this a requirement of PTS, or is PTS just doing
something
nasty? This effect happens in both Plone 2.1.x and Plone
2.5.

-- 
Tarmo Toikkanen
      - NP Solutions
      - tarmoiki.fi
      - http://tarmo.fi/

------------------------------------------------------------
-------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the
chance to share your
opinions on IT & business topics through brief surveys
-- and earn cash
http://www.techsay.com/default.php?page=join
.php&p=sourceforge&CID=DEVDEV_______________________
________________________
Plone-i18n mailing list
Plone-i18nlists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/plone-i18n

Hi all,

We just noticed a problem (bug?) in
PlacelessTranslationService: If
you have a structure like

<p i18n:translate="text_foo">You need to
go <a i18n:name="back"
i18n:translate="snippet_back"
href="bar">back</a> to where you came
from.</p>

and the language used by the viewer doesn't contain
translations for
these strings "text_foo" and
"snippet_back", then the rendered page is
something like:

<p>You nede to go <a href="bar">to
where you came from.</p>

which is just plain wrong! If the translation strings are
present,
rendering is done properly.

This can be fixed by rewriting to something like this:

<p i18n:translate="text_foo">You need to
go <span i18n:name="back">
<a i18n:translate="snippet_back"
href="bar">back</a></span> to
where
you came from.</p> 

effectively separating the i18n:name and i18n:translate to
separate
tags. Is this a requirement of PTS, or is PTS just doing
something
nasty? This effect happens in both Plone 2.1.x and Plone
2.5.

-- 
Tarmo Toikkanen
      - NP Solutions
      - tarmoiki.fi
      - http://tarmo.fi/

------------------------------------------------------------
-------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the
chance to share your
opinions on IT & business topics through brief surveys
-- and earn cash
http://www.techsay.com/default.php?page=join
.php&p=sourceforge&CID=DEVDEV_______________________
________________________
Plone-i18n mailing list
Plone-i18nlists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/plone-i18n

Hi all,

We just noticed a problem (bug?) in
PlacelessTranslationService: If
you have a structure like

<p i18n:translate="text_foo">You need to
go <a i18n:name="back"
i18n:translate="snippet_back"
href="bar">back</a> to where you came
from.</p>

and the language used by the viewer doesn't contain
translations for
these strings "text_foo" and
"snippet_back", then the rendered page is
something like:

<p>You nede to go <a href="bar">to
where you came from.</p>

which is just plain wrong! If the translation strings are
present,
rendering is done properly.

This can be fixed by rewriting to something like this:

<p i18n:translate="text_foo">You need to
go <span i18n:name="back">
<a i18n:translate="snippet_back"
href="bar">back</a></span> to
where
you came from.</p> 

effectively separating the i18n:name and i18n:translate to
separate
tags. Is this a requirement of PTS, or is PTS just doing
something
nasty? This effect happens in both Plone 2.1.x and Plone
2.5.

-- 
Tarmo Toikkanen
      - NP Solutions
      - tarmoiki.fi
      - http://tarmo.fi/

------------------------------------------------------------
-------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the
chance to share your
opinions on IT & business topics through brief surveys
-- and earn cash
http://www.techsay.com/default.php?page=join
.php&p=sourceforge&CID=DEVDEV_______________________
________________________
Plone-i18n mailing list
Plone-i18nlists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/plone-i18n

Hi.

The problem you observed is a known long standing bug of
Zope's TAL 
engine and not the PlacelessTranslationService.

We have worked around this problem in the same way you did
so far. I 
looked into this for Zope 2.10 where we got rid of the old
Zope 2 TAL 
engine and replaced it with the one from Zope 3 which
luckily doesn't 
have this bug.

So once you switch to Zope 2.10 the problem is gone. If you
have the 
time and knowledge to fix the bug in the Zope 2 TAL
implementation 
please do so ;)

Hanno

Tarmo Toikkanen wrote:
> Hi all,
> 
> We just noticed a problem (bug?) in
PlacelessTranslationService: If
> you have a structure like
> 
> <p i18n:translate="text_foo">You need
to go <a i18n:name="back"
> i18n:translate="snippet_back"
href="bar">back</a> to where you came 
> from.</p>
> 
> and the language used by the viewer doesn't contain
translations for
> these strings "text_foo" and
"snippet_back", then the rendered page is
> something like:
> 
> <p>You nede to go <a
href="bar">to where you came from.</p>
> 
> which is just plain wrong! If the translation strings
are present,
> rendering is done properly.
> 
> This can be fixed by rewriting to something like this:
> 
> <p i18n:translate="text_foo">You need
to go <span i18n:name="back">
> <a i18n:translate="snippet_back"
href="bar">back</a></span> to
where
> you came from.</p>
> effectively separating the i18n:name and i18n:translate
to separate
> tags. Is this a requirement of PTS, or is PTS just
doing something
> nasty? This effect happens in both Plone 2.1.x and
Plone 2.5.


------------------------------------------------------------
-------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the
chance to share your
opinions on IT & business topics through brief surveys
-- and earn cash
http://www.techsay.com/default.
php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Plone-i18n mailing list
Plone-i18nlists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/plone-i18n

Hi.

The problem you observed is a known long standing bug of
Zope's TAL 
engine and not the PlacelessTranslationService.

We have worked around this problem in the same way you did
so far. I 
looked into this for Zope 2.10 where we got rid of the old
Zope 2 TAL 
engine and replaced it with the one from Zope 3 which
luckily doesn't 
have this bug.

So once you switch to Zope 2.10 the problem is gone. If you
have the 
time and knowledge to fix the bug in the Zope 2 TAL
implementation 
please do so ;)

Hanno

Tarmo Toikkanen wrote:
> Hi all,
> 
> We just noticed a problem (bug?) in
PlacelessTranslationService: If
> you have a structure like
> 
> <p i18n:translate="text_foo">You need
to go <a i18n:name="back"
> i18n:translate="snippet_back"
href="bar">back</a> to where you came 
> from.</p>
> 
> and the language used by the viewer doesn't contain
translations for
> these strings "text_foo" and
"snippet_back", then the rendered page is
> something like:
> 
> <p>You nede to go <a
href="bar">to where you came from.</p>
> 
> which is just plain wrong! If the translation strings
are present,
> rendering is done properly.
> 
> This can be fixed by rewriting to something like this:
> 
> <p i18n:translate="text_foo">You need
to go <span i18n:name="back">
> <a i18n:translate="snippet_back"
href="bar">back</a></span> to
where
> you came from.</p>
> effectively separating the i18n:name and i18n:translate
to separate
> tags. Is this a requirement of PTS, or is PTS just
doing something
> nasty? This effect happens in both Plone 2.1.x and
Plone 2.5.


------------------------------------------------------------
-------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the
chance to share your
opinions on IT & business topics through brief surveys
-- and earn cash
http://www.techsay.com/default.
php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Plone-i18n mailing list
Plone-i18nlists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/plone-i18n

Hi.

The problem you observed is a known long standing bug of
Zope's TAL 
engine and not the PlacelessTranslationService.

We have worked around this problem in the same way you did
so far. I 
looked into this for Zope 2.10 where we got rid of the old
Zope 2 TAL 
engine and replaced it with the one from Zope 3 which
luckily doesn't 
have this bug.

So once you switch to Zope 2.10 the problem is gone. If you
have the 
time and knowledge to fix the bug in the Zope 2 TAL
implementation 
please do so ;)

Hanno

Tarmo Toikkanen wrote:
> Hi all,
> 
> We just noticed a problem (bug?) in
PlacelessTranslationService: If
> you have a structure like
> 
> <p i18n:translate="text_foo">You need
to go <a i18n:name="back"
> i18n:translate="snippet_back"
href="bar">back</a> to where you came 
> from.</p>
> 
> and the language used by the viewer doesn't contain
translations for
> these strings "text_foo" and
"snippet_back", then the rendered page is
> something like:
> 
> <p>You nede to go <a
href="bar">to where you came from.</p>
> 
> which is just plain wrong! If the translation strings
are present,
> rendering is done properly.
> 
> This can be fixed by rewriting to something like this:
> 
> <p i18n:translate="text_foo">You need
to go <span i18n:name="back">
> <a i18n:translate="snippet_back"
href="bar">back</a></span> to
where
> you came from.</p>
> effectively separating the i18n:name and i18n:translate
to separate
> tags. Is this a requirement of PTS, or is PTS just
doing something
> nasty? This effect happens in both Plone 2.1.x and
Plone 2.5.


------------------------------------------------------------
-------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the
chance to share your
opinions on IT & business topics through brief surveys
-- and earn cash
http://www.techsay.com/default.
php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Plone-i18n mailing list
Plone-i18nlists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/plone-i18n

Hi.

The problem you observed is a known long standing bug of
Zope's TAL 
engine and not the PlacelessTranslationService.

We have worked around this problem in the same way you did
so far. I 
looked into this for Zope 2.10 where we got rid of the old
Zope 2 TAL 
engine and replaced it with the one from Zope 3 which
luckily doesn't 
have this bug.

So once you switch to Zope 2.10 the problem is gone. If you
have the 
time and knowledge to fix the bug in the Zope 2 TAL
implementation 
please do so ;)

Hanno

Tarmo Toikkanen wrote:
> Hi all,
> 
> We just noticed a problem (bug?) in
PlacelessTranslationService: If
> you have a structure like
> 
> <p i18n:translate="text_foo">You need
to go <a i18n:name="back"
> i18n:translate="snippet_back"
href="bar">back</a> to where you came 
> from.</p>
> 
> and the language used by the viewer doesn't contain
translations for
> these strings "text_foo" and
"snippet_back", then the rendered page is
> something like:
> 
> <p>You nede to go <a
href="bar">to where you came from.</p>
> 
> which is just plain wrong! If the translation strings
are present,
> rendering is done properly.
> 
> This can be fixed by rewriting to something like this:
> 
> <p i18n:translate="text_foo">You need
to go <span i18n:name="back">
> <a i18n:translate="snippet_back"
href="bar">back</a></span> to
where
> you came from.</p>
> effectively separating the i18n:name and i18n:translate
to separate
> tags. Is this a requirement of PTS, or is PTS just
doing something
> nasty? This effect happens in both Plone 2.1.x and
Plone 2.5.


------------------------------------------------------------
-------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the
chance to share your
opinions on IT & business topics through brief surveys
-- and earn cash
http://www.techsay.com/default.
php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Plone-i18n mailing list
Plone-i18nlists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/plone-i18n

Hi.

The problem you observed is a known long standing bug of
Zope's TAL 
engine and not the PlacelessTranslationService.

We have worked around this problem in the same way you did
so far. I 
looked into this for Zope 2.10 where we got rid of the old
Zope 2 TAL 
engine and replaced it with the one from Zope 3 which
luckily doesn't 
have this bug.

So once you switch to Zope 2.10 the problem is gone. If you
have the 
time and knowledge to fix the bug in the Zope 2 TAL
implementation 
please do so ;)

Hanno

Tarmo Toikkanen wrote:
> Hi all,
> 
> We just noticed a problem (bug?) in
PlacelessTranslationService: If
> you have a structure like
> 
> <p i18n:translate="text_foo">You need
to go <a i18n:name="back"
> i18n:translate="snippet_back"
href="bar">back</a> to where you came 
> from.</p>
> 
> and the language used by the viewer doesn't contain
translations for
> these strings "text_foo" and
"snippet_back", then the rendered page is
> something like:
> 
> <p>You nede to go <a
href="bar">to where you came from.</p>
> 
> which is just plain wrong! If the translation strings
are present,
> rendering is done properly.
> 
> This can be fixed by rewriting to something like this:
> 
> <p i18n:translate="text_foo">You need
to go <span i18n:name="back">
> <a i18n:translate="snippet_back"
href="bar">back</a></span> to
where
> you came from.</p>
> effectively separating the i18n:name and i18n:translate
to separate
> tags. Is this a requirement of PTS, or is PTS just
doing something
> nasty? This effect happens in both Plone 2.1.x and
Plone 2.5.


------------------------------------------------------------
-------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the
chance to share your
opinions on IT & business topics through brief surveys
-- and earn cash
http://www.techsay.com/default.
php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Plone-i18n mailing list
Plone-i18nlists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/plone-i18n