Please, all responses on the list.

When I Publish a document containing the lines

<ul>
<li>
<strong>strong</strong><em>em</em><cite>cite</cite><code>code</code>
</li>
</ul>

Which displays in BXE (except that, in BXE, "strong" would be bold, "em" in
italics, "cite" in italics, and "code", with my CSS, in monospaced courier 
new) as 

strongemcitecode

(that is, with no spaces between the elements). 

After saving the page in and exiting from BXE, Submit and Publish /change 
the file/ so that it looks like this:

<ul>
<li>
<strong>strong</strong>
<em>em</em>
<cite>cite</cite>
<code>code</code>
</li>
</ul>

and displays (again, "strong", "em", "cite" and "code" each has the proper
appearance) as

strong em cite code

(that is, with spaces between the elements).

I really have no idea what is going on. My best guess is that HTML converts 
the newline characters inserted by Publish into spaces. Given the general
disarray of HTML (or XHTML files: it does not matter if all the tags above 
are replaced with <xhtml:> or </xhtml:> equivalents) files, it makes sense 
that plain text would work this way: any number of spaces or other white 
space characters are replaced with a single space.

So, the problem appears to me to be that Lenya's Publish function is 
introducing an unwelcome and unwanted reformatting to my document. I 
know even less about how Lenya's Publish function works than I do 
about HTML or CSS. And I don't know much about HTML or CSS at all.

I would like, if possible, a simple, clear statement as to whether the 
problem can be corrected and, if so, how to do it. What I am looking 
for is something on the order of "open file MAGIC.XSLT and insert the 
line <xlst:insert-no-whitespace-of-any-kind-between-elements"> in the 
"sane behavior" section". What I don't want is a referral to a multipage
reference manual or an endless regress of Web pages which may, or may 
not, actually contain the answer to the question.


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

Reply via email to