Re: instream-foreign-object SVG?

Hi,
  A couple questions I'm coming up with as I look at the "border" and border
side shorthands:

   Right now dump-info.xml has <property> tags (with only "name" attributes)
for shorthand
properties for seven of the eight absolute/relative sides - "border-bottom" is
missing.  The XSL spec only seems to mention shorthands for the absolute
sides - border-bottom, border-top, border-left, border-right.  Should the other
four exist?  There seems to be code talking about border-after's and such in
some of the area code, and the spec seems to talk about it in those terms,
but not for actual element attributes.  Also, right now spec-dump doesn't seem
to include any of these properties in the files it dumps; I didn't see right
off what suppresses them.

  There are already fo-property-border.[ch] files which seem to have some
general border-oriented enums and such - will I want to merge these with the
same-named files that spec-dump will produce, or rename these existing files,
...?

  A semantic question for which I didn't notice an answer in the spec right
off - the spec clearly says that the border-<side> shorthands are of higher
priority than border-{style,color,width}, and "border" is lowest priority.
You're allowed to omit any or all of the style, color, and width components
from the border{,-<side>} shorthands, right (I don't know the XSL spec regex
vocabulary particularly - ||, etc.)?  e.g., border-top="1px solid" is valid,
no?  In the case that components are omitted, it would seem intuitive that
any values already assigned by a lower-priority shorthand which correspond
to an omitted component on the current one would remain as the value, rather
than, say, a default value for that omitted component overriding the actually
specified value from a lower-priority shorthand.  If that is the desired
semantics, how will that be represented in xmlroff?  In particular, what will,
say, fo_wsc_get_color() return if that component was omitted from the
shorthand attribute corresponding to the FoWsc?  I want to say NULL, but that
seems to indicate other error conditions - would we need some other enum value
meaning "omitted" or something?  I guess that's somewhere
between a question and a suggestion.

  If 'inherit' is specified on one of these shorthands, will that be resolved
in the expr-eval code?  From my perspective, that will already be resolved
before the fo-context-util code gets ahold of the FoWsc's, right?

 All I have for now..  Thanks,
   Julian


-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click