[DM] 'structure' directive support within tal:attributes (TAL)

[Andreas Jung]

2. Introduction

The "HRS" is still based on SGML and uses SGML entities to represent special characters. The "iDesk" production follows this tradition and delivers objects with SGML entities in associated attributes.

TAL supports SGML entities in element bodies via the structure keyword. Unfortunately, occasionally, SGML entities are also required in element attributes -- and TAL does not support this use case as structure is unsupported in tal:attributes.

3. Feature

Support structure in tal:attributes.

4. Example Use Cases

Necessary for "iDesk" to be able to handle SGML entities in attributes.

An alternative would be to convert the HRS and/or the "iDesk" production to use unicode instead of SGML entities.

[Andreas Jung (ajung)]

Patch committed:

http://svn.zope.org/zope.tal/branches/haufe-legacy-integration/?rev=99838&view=rev

[Christian Zagrodnick (zagy)]

Could this be merged to zope.tal trunk?

[Tres Seaver (tseaver)]

"Fix committed" means that the fix has been merged to the trunk or appropriate release branches.

[Colin Watson (cjwatson)]

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.

[Colin Watson (cjwatson)]

The zope2 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/zope2.