First on the agenda today is a tiny CSS nit with workaround.  It would
seem that the text-decoration property does not properly display across
all boxes generated by that element.  For example (in DocBook):

    <ulink url="http://www.example.org/";>Hello, world,
    <emphasis>please see my homepage!</emphasis></ulink>

the text "Hello, world, " is underlined, but that underline does not
extend to the box for the emphasis element.  Note that this is not
strictly an inheritence issue; if my reading of the spec[0] is correct,
the underline should extend across all inline blocks within the ulink.
This also corresponds with what I (and perhaps others) would expect.
That being said, it can be worked around using inheritence:

    *
    {
        text-decoration: inherit;
    }

which is not exactly what you'd want, but which works in most
situations.  You can also tune it to be arbitrarily close to your
desired display in a given context.

Second up, I was wondering if there was any chance of getting
CSS-compliant procedural counters in XXE.  I'd like to be able to do
arbitrary nesting, amongst other things.

Finally, I wanted to ask for xml:base support in XXE.  Of course XXE
supports adding xml:base attributes, but I would like to use them to
evaluate URIs for resources (as they are intended).  For example, when
referencing graphics or document components (using XInclude), I believe
XXE should take into account the xml:base that may be in scope.  Also,
these URIs (taken against an in-scope base URI) should be resolved using
XML catalogs.  Interestingly, this raises the question of "classes" of
XML catalogs in XXE: it currently uses XML catalogs for application
processing, but this use of XML catalogs would be more along the lines
of user data resolution.

Take care,

    John L. Clark

[0] http://www.w3.org/TR/CSS21/text.html#lining-striking-props
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
Url : 
http://www.xmlmind.com/pipermail/xmleditor-support/attachments/20041001/dd8716f8/attachment.sig
 

Reply via email to