Cyriaque Dupoirieux wrote:
le 05/05/2006 17:13 Ross Gardler a écrit :
Web Maestro Clay wrote:
On May 5, 2006, at 3:01 AM, Ross Gardler wrote:
...
In this case if the class="T1" attribute were allowed to pass
through, suppose I could just create a style for it in skinconf.xml.
Then, I don't think it would be invalid code (unless the DTD doesn't
allow that). We could 'pick and choose' styles that way... Any
styles which are not in skinconf.xml would be ignored. If we could
modify the pipeline to only allow styles from skinconf.xml it would
be all the better.
Your approach makes two assumptions, both of which are, in my opinion,
flawed:
1) we know what T1 is used for by the user
2) we can force a predefined style on T1 and the document will still
look right
My approach allows us to pull the style information from the OOo
document and therefore respect the users wishes within the confines of
the web designers rules.
It doesn't require that much more work since it will (hopefully) only
be a case of copying over the code from the OOo plugin.
The fact that it creates invalid XDocs is not a huge problem as it
only affects things on the internal side of Forrest and so validation
checks are not an issue (in fact the internal format is not valid in
many other ways too). We can return and address this at a later date.
Ross, I fully agree with you, but I have search in one of my odt files
with bold characters (style="T1") and I can't find the style definition
in the T1 style ?
This highlights a third incorrect assumption about styles in ODT docs:
- there is consistency in the style names used across different ODT
editing environemnts
It seems to be a predefined style ?
I just loooked in an ODT file for the first time and was pleasently
suprised to find sensible style names and not codes like "T1" as was
used in SXW. Perhaps the document Web Maestro Clay is referring to
started life as an SXW?
In SXW, if I remember rifhtly, T1 was the predefined style called "Title
1" in the drop down styles list.
Ross