Jeff Hooker wrote:
> Hmmm. Bringing me closer.
>
> The white space was never being "lost". That is, even though it was not being
> displayed in XMLmind, it was still present in the XML and published correctly
> (the main application of this element within PMC is as a container for
> content that is programatically stripped from .c files imported into our CMS
> and from there, automatically imported into programmer reference guides, and
> that's been working swimmingly).
>
> The CSS change was already in place in my custom CSS, and adding the
> reference to my .xxe changed the display within XMLmind so that now
> whitespace is displayed correctly. Users still cannot enter new line
> feeds/carriage returns, however. Tapping the "Enter" key is simply not
> acknowledged. Nothing shows up on the console either, so at this point I'm
> just reconstructing my .xxe file one step at a time and waiting to see what
> breaks.
>
> Any other thoughts?
--> Can you type characters other than a newline in such
programlistings? I mean, may be your programlisting contains an xinclude
with parse="text" (I would do it this way to import .c files from a CMS)
or may be the CMS has added a read-only property without styling it.
Please try to add a programlisting ``by hand'' using the Edit tool and
then type a few lines separated by newline characters in it.
--> If this is not the case, please note that the answer below is both
*accurate* and *complete* and that we are almost sure that we have no
bugs related to this.
No offense intended, but you should really double-check that you have
both <preserveSpace...> and "white-space:pre;" somewhere in your
configuration files.
>
>> Jeff Hooker wrote:
>>
>> I've got something odd happening in the
>> programlisting element of my docbook5 modification. Users cannot break
>> lines, so
>> the contents of the whole element must be one single line.
>>
>>
>> Your stock docbook5 config is not like this; users can add new lines, etc.,
>> and
>> I'm groping for what I've changed. I know it nothing to do with the CSS or
>> the
>> .rnc files. It's something buried in my custom .xxe file. Got any clues for
>> me
>> to narrow down my search?
>>
>
> For elements like programlisting to
>> work as expected, you need:
>
> [1] This configuration
>> element
>
> ---
> <!-- This is needed because xml:space is declared as
>> follows in
> ``verbatim environments'':
> ...
>> & attribute xml:space {"preserve"}? & ...
> That is, it
>> is possible to add attribute xml:space but always
> with fixed
>> value "preserve".
> This is very different from:
>
>> [ a:defaultValue = "preserve" ]
> which would have
>> specified that "preserve" is the *default* value
> of attribute
>> xml:space. -->
>
> <preserveSpace elements="db:programlisting
>> db:literallayout db:screen
>
>> db:synopsis db:funcsynopsisinfo
>
>>
>> db:classsynopsisinfo db:address db:modifier" />
>
> ---
>
> in your
>> .xxe configuration file.
>
> More info:
>> href="http://www.xmlmind.com/xmleditor/_distrib/doc/configure/preserveSpace.html";
>>
>> target=_blank
>>> http://www.xmlmind.com/xmleditor/_distrib/doc/configure/preserveSpace.html
>
> [2]
>> Property
>> white-space:pre;
>
> ---
> programlisting,
> screen,
> literallayout,
> synopsis
>> {
> display: block;
> white-space: pre;
>
>> font-family: monospace;
> margin: 1.33ex
>> 0;
> }
> ---
>
> in your custom .css files.
>
> More info: > href="http://www.w3.org/TR/CSS2/text.html#white-space-prop";
> target=_blank
>>> http://www.w3.org/TR/CSS2/text.html#white-space-prop
--
XMLmind XML Editor Support List
[email protected]
http://www.xmlmind.com/mailman/listinfo/xmleditor-support
