ignore i18n: in the same way as tal:

Bug #143047 reported by ChrisW on 2004-06-29
2
Affects Status Importance Assigned to Milestone
zope.tal
Invalid
Wishlist
Unassigned

Bug Description

It would be "way cool" if I could do:

<i18n:x name="fish"/>

...in the same way I can do:

<tal:x repalce="fish"/>

...and not have the i18n tag in the output...

ChrisW (chris-simplistix) wrote :

Status: Pending => Resolved

It apparently already works this way :-)

ChrisW (chris-simplistix) wrote :

Status: Resolved => Pending

Well, by the looks of it, tags which contain only an i18n:name work this way, but show up in the output if they include any othe attribute, including those from the tal: namespace.

ChrisW (chris-simplistix) wrote :

Changes: edited transcript, new comment

http://zope.org/Collectors/Zope/1551 is related to this, and I believe explains more about why i18n:name behaves like it does.
That makes this a bug, not a feature request.
Where in the ZPT process is i18n: handled and how is i18n:name handled that's different to this?

Florent Guillaume (efge) wrote :

Testcase mentionned in 1551 is:

ZPT source:
---
 <span i18n:translate="foo">
   <b i18n:name="bar">test 1</b>
   <b i18n:name="baz" tal:content="default">test 2</b>
 </span>
---

HTML output:
---
 <span>
   test 1
   <b>test 2</b>
 </span>
---

And I agree it's not logical.

Changed in zope2:
importance: Medium → Wishlist
affects: zope2 → zope.tal
Colin Watson (cjwatson) wrote :

The zope.tal project on Launchpad has been archived at the request of the Zope developers (see https://answers.launchpad.net/launchpad/+question/683589 and https://answers.launchpad.net/launchpad/+question/685285). If this bug is still relevant, please refile it at https://github.com/zopefoundation/zope.tal.

Changed in zope.tal:
status: New → Invalid
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers