> From: [EMAIL PROTECTED] [mailto:kid-
> [EMAIL PROTECTED] On Behalf Of Florian
Ludwig
> Christoph Zwerschke wrote:
> 
> > Florian Ludwig wrote:
> >
> > > I tried <div>&nbsp;</div> to get the results i wanted...
> > > but it always ends with a <div /> ...
> >
> > I cannot reproduce this. I get <div>\xa0</div> with output encoding
> > utf-8 and <div>&#160;</div> with output encoding ascii.

If the template is getting processed first by an xhtml-aware processor,
it should replace "&nbsp;" with a unicode 160, i.e., a non-breaking
space.  A non-xhtml cml processor should cause an error, because it
would not understand the nbsp entity.  Also, a nonbreaking space as the
only content should not be causing the output of the empty-element short
form (<empty/>).

The python code might choose to output the unicode 160 character as \xa0
during serialization for printing purposes, because that is a legal
unicode python representation.  But it should not be putting it into the
(x)html output.

So you can see how these anomalies might happen, but it's not quite how
thing should work.

TomP



-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems?  Stop!  Download the new AJAX search engine that makes
searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid3432&bid#0486&dat1642
_______________________________________________
kid-template-discuss mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/kid-template-discuss

Reply via email to