The thing is... all entities in HTML are actually real entities as in XML... and   is just another one... I forget which Unicode character number it is and can't seem to find it but using jEdit's entities to characters does print me a space... looking at W3C's HTML 4 specs (and certainly XHTML) should probably provide it to you...

The only trick remaining is encoding... Although I've seen some errors some time ago the maven b9 seem to be happy with an all-UTF-8 solution and generates the appropriate HTML heading.

It is pretty nifty, I find it, to be able to see a non-breaking-space as a space instead of these ugly editing-oriented entity. What's needed is just a good editor. This was one of my main reason to use jEdit, even on Mac where it was pretty slow.

Paul


Kai Runte wrote:
Hi,

I had a look again: If I place   in the JSL script, it actually gets printed out, but not as entity. What Mozilla and Camino actually disliked in the HTML was that it was written as XML. When I changed the outputmode to HTML in the plugin.jelly of the xdoc plugin, everything turned out fine. Sorry about the fuss.

Thanks
    Kai

On Thursday, June 26, 2003, at 11:16 PM, Rafal Krzewski wrote:

Kai Runte wrote:

Hi,
maybe this is the wrong list to ask, apologies if yes.
Currently I working on a site.jsl script for creating webpages in the look-and-feel of our internal website. For some obscure layout reasons I need to have a   entity in the target HTML document, but utterly failed in getting Jelly/JSL to do so.
If I try the following:
<td width="100%" height="51" background="images/bann_mid.gif">
&nbsp;
</td>
Maven bails out with:
BUILD FAILED
null:-1:-1: <null> Could not parse Jelly script


Did you try escaping the & charcter as &amp; entity in the jelly source?
I think it will get written as & in the target document:

<td width="100%" height="51" background="images/bann_mid.gif">
&amp;nbsp;
</td>



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



Reply via email to