You can create a custom tag for each special character you need. I have set up a couple myself for characters like the trademark symbol. Check out http://ez.no/ez_publish/documentation/customization/components/datatypes/ezxmltext/custom_tags for more information.
Alex
Alex
[ bald_technologist on the IRC channel (irc.freenode.net): #eZpublish ]
Well, you could change all of your XML Text Fields to standard Text Fields which will accept your HTML for the most part. But in the long run that is limiting the power of the system. May I ask why you do not want to use custom tags?
Alex
Alex
[ bald_technologist on the IRC channel (irc.freenode.net): #eZpublish ]
I try to use no xml field. But no good will come of it. Ez is changing (&) and paste into derived html data (&), instead (<) insert (<).
I need input in form html tag which will be processed by brouser. I want use the rule of publication. For example telephone number or name and surname must be written together. <nobr>>(375)297-358-689</nobr>. Brouser show me (375)297-358-689 in line.
I use in output date {attribute_view_gui attribute=$node.object.data_map.body}. No result.When I insert <nobr> and I use {$node.name} all works normally. A problem with they remain as before.
When you use <i>{attribute_view_gui...}</i> the system automatically washes the output. Instead, try using something along the lines of:
{$node.object.data_map.body.content}
Again, this requires that your <i>body</i> field is not set up as an XML Text Field (which is the default) - it should be a Text Field. The reason it works when you use <i>{$node.name}</i> is the fact that the <i>Name</i> field is a Text line, so it is not subject to the XML filtering steps.
Alex
Alex
[ bald_technologist on the IRC channel (irc.freenode.net): #eZpublish ]
I use <literal class='html'>$content</literal> and remove operator wash in design/standard/templates/content/datatype/view/eztext.tpl. Then I something corrected literal tag \design\standard\templates\content\datatype\view\ezxmltags\
<div>{$content|(xhtml)}</div>
Thanks
You must be logged in to post messages in this topic!
