I've answered some of this for myself:

1. The doctype was being stripped off by the XML serializer producing the XML for the various editors. Using a serializer that outputs the doctype I want solved this part of the problem.

2. Interestingly, it's the FILE GENERATOR that adding the "shape='rect'" to the <a> tags. So this is a cocoon thing after all. Anyone dealt with this issue before? I'll take it to the cocoon lists.

Sorry for emailing myself via the list ;-),

-doug


On Mar 30, 2006, at 1:38 PM, Douglas Hurbon wrote:

I'm sure this has been hashed through before, but I can't find much about it in the list archives.

Using Lenya 1.2 and BXE, Source and Form Editors, is there a way to get character entities (like &middot; or &nbsp;) to be resolved correctly?

If I add a doctype declaration into an xhtml doc outside of any of the Lenya web-based editors, entities get resolved via the Cocoon entities catalogue as expected.

But if I open an xhtml doc in the Source Editor, BXE or the Forms editor, several problems occur:

1. All the <a> tags get a shape="rect" parameter added to them (like MAGIC!)

        2. The doctype declaration gets RIPPED OFF the page.

I can remove all the "shape="rect" tags, then the editor accepts the document (otherwise they fail the RNG validation), but then with no doctype declaration cocoon cannot resolve the entities and so throws an "entitiy used but not defined error."

Is there any way to use the Lenya web-based editors AND entity catalogs at the same time? Can the editors be made to preserve the doctypes, or, can I tell cocoon to always use certain entity catalogs even if there is no doctype declaration?

Anyone (or everyone) been through this before?

I'm trying to implement my own catalogs, which is why this is important.

-doug


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to