What is or is not a legacy feature?

Francis Cave francis at franciscave.com
Tue Feb 21 16:07:51 CET 2012

While I think of it, the same issue arises with two run properties in
WordprocessingML: w:highlight and w:shd. Although section does
document the interaction between these two elements, as far as I can see
anything that be expressed using w:highlight (which only controls background
colour, and only uses colour names) can be expressed using w:shd. This
suggests that any new producer implementation of WML Strict would probably
not implement both ways, and would probably choose to implement w:shd as the
more powerful of the two. This in turn suggests that w:highlight could be
considered to be a legacy feature.






From: Francis Cave [mailto:francis at franciscave.com] 
Sent: 21 February 2012 14:58
To: 'e-SC34-WG4 at ecma-international.org'
Subject: What is or is not a legacy feature?


I have recently needed to review the way that form controls can be
represented in OOXML. It seems that there are two approaches, and both of
these are documented in Part 1. The first approach is to use fields as
documented in section 17.16. The second approach is to use structured
document tags as documented in section 17.5.


There seems to be a fair amount of overlap in functionality between these
two approaches, and this has caused me to wonder whether one of these
(probably the use of fields) should be considered a "legacy" approach and
moved to Part 4.


There appears to be some support for doing just that in an unlikely place:
in the Microsoft Word 2007 / 2010 user interface. The tools for inserting
form fields into a document are grouped together in a box labelled "Legacy


I'd be interested to hear expert opinions on this.





-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.vse.cz/pipermail/sc34wg4/attachments/20120221/de0d1149/attachment.htm>

More information about the sc34wg4 mailing list