We need a specific JSF tag to be allowed in the RTF (this component is abstracted away from 'general editors' and is part of a more technical aspect).
Whilst we can update the TcmXHTML.config and this works for the tag that I need... however as this is a JSF tag I actually need
< h:output >something< \h:output >
I've tried putting h:output into new-blocklevel-tags and tried with
output in new-inline-tags and h in the new-blocklevel-tags
Current contents of the tcmXhtml.config are:
numeric-entities: true drop-empty-paras: true drop-proprietary-attributes: false break-before-br: true word-2000: false wrap: 0 tidy-mark: false uppercase-tags: false uppercase-attributes: false output-xml:true logical-emphasis: true fix-backslash: false char-encoding: utf8 input-encoding: utf8 output-encoding: utf8 fix-uri: true indent-cdata: false //indent: auto new-blocklevel-tags: article aside canvas details figcaption figure footer header hgroup nav output progress section video h new-inline-tags: audio datalist mark meter summary time output new-empty-tags: command source track
Any suggestions on the format to get this permitted (short of creating the same holder as a plain text field)?
So this text+JSF tag+text is already what we (as Jaime and ThatITBloke suggest) already use as part of a resolved "merge field". As this is likely a one-off scenario the technical team wanted to avoid parsing another 'format' of string during the publish process and simply allow this syntax directly.
I think the main answer to the question is that this can't be done through the tcmxhtml configuration without specific 'work' so it's either a case of
- support another content placeholder for this merge-field and use a plain text block or
- support another format of 'snippet/merge-field'