On 07/14/2012 04:36 PM, Manuel Collado wrote:
> First of all, thank you for the improvements provided by XXE 5.3.0. In
> particular I find very convenient the support of the associated CSS of
> XHTML, both for browser emulation and for document conversion.
>
> Now my current problem. Some time ago I wrote a configuration for XSLT
> files, based on what you kindly sent to me at that time.

Very nice. However please note that XXE has not been designed to be good 
at editing this kind of documents. Personally, I use Emacs+nxml-mode 
(outstanding XML mode written by James Clark) when I write XSLT stylesheets.


>
> My main improvement has been a CSS stylesheet that renders a tree-like
> view of the XSLT code, using different colors for top-level elements,
> other XSLT elements, and user supplied literal elements.
>
> This stylesheet uses the attributes() extension to render the image of
> the attributes like a table. It works OK in XXE 5.0.0, but the result is
> quite unsatisfactory in XXE 5.3.0.
>
> In a recent post to this forum you explained the reason of the change of
> CSS behaviour, and provided a potential solution. But I'm unsure about
> how to implement your solution in this particular case, because
> fragments of the attribute rendering are specified separately, and not
> as a single cell that could be declared non-wrappable.
>
> ¿Is still be possible to rely on attributes() to properly render a
> tabular presentation of the element's attributes?

Sure. Suffice to specify content:attributes() in a display:block.



>
> Please find attached the CSS, a sample XSLT document, and screen capture
> images from XXE 5.0.0 and 5.3.0.
>

I don't see how you can emulate the behavior of XXE v5.0 using XXE v5.3. 
So for now, you'll have to find a workaround by yourself (i.e. using a 
alternate layout for your generated content:

xsl|*:before {
    color: #0a0;
    content: collapser() xpath("concat('xsl:',local-name(), ' ')") 
attributes();
}

)

We'll try to improve XXE behavior in that respect in next release by 
either by changing the policy of making inlines as narrow as possible or 
by supporting the "width" CSS property in more elements (currently 
"width" is supported only in images and in tables).
 
--
XMLmind XML Editor Support List
[email protected]
http://www.xmlmind.com/mailman/listinfo/xmleditor-support

Reply via email to