[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: Re: [office-collab] Suggestions for moving forward to resolveissues
On Thu, 2011-04-21 at 17:36 +0100, Robin LaFontaine wrote: ... Hopefully there has been a little jump start on this. Like the exchange on handing text:style-name; http://lists.oasis-open.org/archives/office-collab/201104/msg00042.html As a follow on to that, it might be interesting to consider preferring this form of serialization where XML elements can be nested (like text:span). In such a situation the serialization can insert the XML elements needed by revisions with citation to the ctid where ac:change can be used to collapse nested trees where many changes occurred at a point. As mentioned previously, the downside here is that applications not supporting CT would have to process these older revision XML elements too on loading. FWIW I've tried loading some of these GCT ODF files in OpenOffice 3.3.0 and they display the final version OK. The upside of this serialization is the avoidance of the markup for sliding windows over revisions. Does anyone know of a nice resource to how OO handles the existing CT stuff? It would be nice to expand the collective knowledge of how apps model these things. I'm happy to put more info up about abiword, in addition to the past comments and abw file segments. If folks do not find it appropriate for such implementation oriented stuff on list, we can put it up some place else. A2. To see if we can combine the best aspects or the two proposals, please would anyone who has ideas on this propose them for discussion. |
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]