RE: [office-collab] Suggestions for moving forward to resolveissues

[monkeyiq <monkeyiq@gmail.com>]

Hi,
  I created the below with OpenOffice 3.3.0 which comes with Fedora. The
interface to OpenOffice doesn't make it simple to change styles for the
caption, though if it is a text:p as the XML indicates then it should be
fully legal to do so? Indeed, if one directly pokes the XML and makes
part of the caption bold then OO will render it as such.

  The changes I am talking about are very much like the ones I made to
content.xml, sans adding the second paragraph to get OO to generate the
bold style I wanted to use in the caption.

pic-and-caption.odt is not molested in any way.

On Thu, 2011-04-21 at 22:02 -0700, Dennis E. Hamilton wrote:
> Ben, send me an ODT document that has the nested <text:p><draw:frame>
> business and let's see what a Native ODF application actually does
> with the change you are talking about.
> 
> Send it in its unaltered form and include in the text what changes
> you'd like to see made to it.
> 
> I've already posted two documents that show what some allowed
> deletions and insertions do (and that, it happens, fail in one way or
> other where I have tested them).  But you can see the related XML as
> well.  None of it is done by some sort of diffing process.  It is
> rather more interesting than that.
> 
>  - Dennis
> 
> -----Original Message-----
> From: monkeyiq [mailto:monkeyiq@gmail.com] 
> Sent: Thursday, April 21, 2011 21:38
> To: Robin LaFontaine
> Cc: office-collab@lists.oasis-open.org
> Subject: Re: [office-collab] Suggestions for moving forward to resolve issues
> 
> On Thu, 2011-04-21 at 17:36 +0100, Robin LaFontaine wrote:
> ...
> 
> 
> 
> 	Suggested Actions
> 	
> 	A1. To resolve the issue over implementation, please could those who currently feel that the GCT is impossible/difficult/expensive to implement talk to those who have already done implementations? Perhaps the question to answer is: what restrictions could be put in place to make it easier to implement the GCT?
> 	
> 	
> 
> 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.
> 	
> 	A3. Conference call, again perhaps chaired by Rob, possibly on Tues 17 May (not yet checked with Rob) at the usual time to check if we are converging on a solution.
> 	
> 
> 
>

pic-and-caption.odt

pic-and-caption2.odt