My homework: MCE examples
Shawn Villaron
shawnv at microsoft.com
Fri May 17 01:10:24 CEST 2013
Regarding the round-trip point in red, that's just a suggestion, right? I thought that extLst handling was a behavior left to the implementation?
-----Original Message-----
From: Chris Rae [mailto:Chris.Rae at microsoft.com]
Sent: Thursday, May 16, 2013 4:05 PM
To: e-SC34-WG4 at ecma-international.org
Subject: RE: My homework: MCE examples
We discussed my draft and Murata-san's followup document on the WG4 call on Tuesday. As mentioned in the minutes, we agreed to build the example into the current MCE draft pending a couple of changes. Attached is the document with those changes applied. The changes are:
* I have renamed the 2011/2013 versions of ChrisOffice to "v1" and "v2"
* I have added a couple of paragraphs at the end integrating Murata-san's example of "before" and "after" document subsections, as though a preprocessor was applied
Many thanks to Murata-san for helping revise this.
Chris
-----Original Message-----
From: Chris Rae
Sent: 18 April 2013 15:53
To: e-SC34-WG4 at ecma-international.org
Subject: My homework: MCE examples
Hi all - I've done some reworking of my famous MCE example from 2011 which used markup for some future features of ChrisOffice (TM). I've attached it as both a PDF and a Word document.
I know Murata-san was keen to have "before" and "after" samples in there, but upon reflection I actually don't think they would be very valuable. There's no requirement to implement MCE as a preprocessor step so for many implementations, including ours, there simply aren't a "before" and an "after". There are only things which were paid attention to and things which weren't. Additionally, one of the important things this example imparts is the fact that non-understood extension lists can easily be round-tripped by consuming applications. Trying to represent this in "after" file samples will, I think, end up being rather confusing.
Any feedback appreciated - the markup is similar to my original sample but the text is almost all new.
Chris
More information about the sc34wg4
mailing list