Gene Selkov wrote:
>
> I feel I am almost there; at least I think I am on the right track. The
> white space is now preserved in the file, and I can even see line breaks
> in the editor. But there is a difference between how the contents of the
> ALT element is displayed in the EQUATION and INLINEEQUATION elements. It
> is left-justified in INLINEEQUATION (which it should be), but the same
> content becomes centre-justified when placed inside EQUATION. Where
> should I look to find out about the styles affecting the rendering of
> these elements in the editor?
In your case, the CSS styles are found in:
/opt/xxe-perso-4_4_0/addon/config/docbook/css/*.css, *.imp
You need to remove "text-align:center;" (or better, override it with
"text-align:left;" in your CSS customization file) in:
---
alt {
display: block;
text-align: center;
margin: 1.33ex 0;
}
---
> By the way, the quick-and-dirty solution worked just as well as the more
> permanent one, although I am not sure whether I executed the permanent
> one correctly.
The answer is no.
>
> I have made the following steps:
>
> 1. created ~/.xxe4/addon/custom/
>
> 2. There, I symlinked all these includes except docbook1.imp:
>
> ln -s /opt/xxe-perso-4_4_0/addon/config/docbook/css/*imp .
> rm docbook1.imp
>
> 3. copied
>
> /opt/xxe-perso-4_4_0/addon/config/docbook/css/docbook1.imp
>
> /opt/xxe-perso-4_4_0/addon/config/docbook/css/docbook.css
>
> 4. added this to dockbook1.imp:
>
> <css name="Style sheet #1" location="docbook.css" alternate="true" />
> <windowLayout>
> <center css="Style sheet #1" />
> </windowLayout>
>
> <cfg:preserveSpace xmlns=""
> elements="address funcsynopsisinfo classsynopsisinfo
> literallayout programlisting screen synopsis
> equation/alt inlineequation/alt" />
>
>
> This proved to be equivalent to the quick-and-dirty solution, although I
> am left with the impression that I've performed a cargo cult act.
I don't know that expression. I would say that you performed a brilliant
improvisation when you were asked to play a score note for note.
> I understand that the reason for docbook.css to be there is to pull in my
> version of docbook1.imp. It does this with
>
> @import "docbook1.imp";
>
> and it also imports a bunch of other things, which it couldn't find
> until I symlinked them from the xxe installation directory. That almost
> defeats the purpose of customization, although if there is no easier way
> of cloning the global configuration, refreshing a bunch of links after
> an upgrade is admittedly easier than hunting down changes in config
> files. But maybe there is an even more straightforward way?
>
Creating a customization of an existing configuration takes 5 minutes
(when you understand how it works) and does *not* involve copying files
from and/or making symlinks to the stock configuration.
In a nutshell, it works by:
[1] Creating customizations files somewhere inside ~/.xxe4/addon/
because this directory is scanned by XXE during its startup.
[2] importing/including in your customization files, stock files
referenced using URLs starting with "xxe-config:".
(No magic here, the stock XML catalog of XXE, located in
XXE_install_dir/addon/config/, starts with:
---
<rewriteURI uriStartString="xxe-config:" rewritePrefix="." />
---)
All this is explained in great length in XMLmind XML Editor -
Configuration and Deployment,
http://jazz.localdomain/xmleditor/_distrib/doc/configure/index.html
I agree that this document is boring to read.
