Allow <sometag> in DCR (custom DTD?)

Hi all,

I've poked around the (very sparse) documentation around custom DTD's and I must admit... not too helpful. Here's what I'm looking to do:

I would like to allow some tag (like: <my_tag>****</my_tag>) to be allowed as input inside the textarea input of a Datacapture Form and to not be rewritten (like >my_tag... ). Anybody know where I can control this behaviour of Forms Publisher?

Thanks,

Jeremy Anderson
Independent TeamSite Consultant
www.miletwo.com/TeamSite

Quis custodit custodem

Find more posts tagged with

Comments

Adam Stoller

Is this a VF textarea or a non-VF textarea?
Is it being rewritten within the textarea in the GUI or in the DCR?
You can correct it in the PT if need be.

--fish
Senior Consultant, Quotient Inc.
http://www.quotient-inc.com

miletwo

Ah... allow me to clarify.

In either a VFE or non-VFE textarea(depending upon user platform) ... we want the user to be able to enter any of a number of custom tags that are being developed. If an occurance of that tag exists in the VFE (which we are handling by passing the dcr node directly to a parent tag) then we will perform some function according to the tag entered. What we need to be able to do is to allow that tag to exist, just like a <p> or <br /> tag. I've looked for documentation around modifying either the visualformatconfig.xml file, but that doesn't seem to be appropriate since it's mostly focused around how you clean the html, and what is forced to be forbidden as opposed to allowed.

The client's first priority usage of this is to enable glossary keywords to be "tagged" in the body content and then highlighted in the generated HTML. We are also parsing the body content programatically for 1st occurance of each keyword, but the users also want to be able to tag content that would not normally be parsed by the program.

Does that make sense?

Thanks for you input.

Jeremy Anderson
miletwo, Inc.
www.miletwo.com/TeamSite

Quis custodit custodem

Migrateduser

There is no direct support in FormsPublisher to allow form users to introduce arbitrary, unescaped XML into a DCR. The only unescaped XML elemetns that will appear in a DCR are those modelled by a form element.
This ensures well-formedness and helps to insure validity of the DCR saved.
Suppose, for example, that your user forgets to properly close a tag and saves the DCR: the result will be that the DCR may fail to open or possibly have items omitted when the DCR is reopened for editing.

The typical solution for this is to have your Presentation Template unescape the content that you wish to output in the generated HTML, as the previous poster suggested. Any tags that your users enter will be escaped with standard entity references and it should be trivial using the presentation templates or XSL to unescape that data and employ it as you wish.

______________________
Kerry Kartchner
Interwoven, Inc.

miletwo

That makes sense. I hadn't thought about the introduction of a malformed xml element being introduced and thereby causing errors with the DCR. We will be proceeding using another format for tagging the content along the lines of *tag*somecontent*/tag* which will allow us to do the same thing, then passing the entire DCR node to a custom tag to parse the tags out as required.

So, instead of <iw_value name="dcr.x.y" />

We'll have: <xy_tag name="dcr.x.y" />

Thanks for the input,

Jeremy Anderson
miletwo, Inc.
www.miletwo.com/TeamSite

Quis custodit custodem