DII ODF workshop catch-up

by jlundstocholm 2. August 2008 00:26

Wow - it seems the entire cast of Microsoft bloggers are laying the grounds for a whole bunch of blog-entries after the DII-workshop in Redmond the day before yesterday (Wednesday July 30th).

So OK - I'll bite.

I am again back in Denmark after a Hell-ish evening after the workshop where jet-lag almost had the end of me. If the cap-driver had actually known the way to my hotel (he didn't so I ended up giving directions in a town I had only been in for about 36 hours in a country I was only visiting for the second time) I am sure I would have been catching Z's big time on my way home in the cap ... at 20.15 in the evening.

All in all it was very interesting to attend the workshop in Redmond. The day started up with an introduction by Peter Amstein about the approaches and decisions Microsoft had done when working on their ODF-implementation. One of the more interesting discussions here was what Microsoft had done where there was differences between ODF and OOXML - should they be conservative or creative? An example of this was numbering/bulleted lists (it is one of the key parts with differences between ODF and OOXML).OOXML has the possibility of having each bullet in a list a seperate colour where ODF does not. Microsoft had chosen the conservative approach and simply removed all colours from the bullets, but Patrick Durusau noted that he thought it was possible to use styling to do it in ODF - only downside was, that to his knowledge, this particular way of doing it was not supported by any ODF-implementation. I guess some times you are screwed regardless of what you do.

After this followed various project managers that demonstrated how their part of Microsoft Office supported ODF and talked about the remaining work. They each had complex documents that they showed us their work on and the result of saving them (OOXML-files) to ODF. I remember working with conversion using the SourceForge translator in Fall 2007, and I was really impressed by the fidelity of the conversions we saw.

Key points from this part was

  • Shapes are converted without much loss of fidelity
  • Metadata is converted (Dublin Core)
  • Fields are converted
  • Headers/footers are converted
  • TOC etc are converted
  • Shapes are converted
  • SmartArt is converted to shapes
  • Images are converted including cropping etc
  • New 3D-shapes are reduced to the closest possible OpenDocument Drawing shape
  • Old 3D-shapes are converted
  • Formulas in spreadsheets are implemented by the ECMA-376 specwith Microsoft's namespace
  • Mathematical content is converted from/to OMML and MathML
  • When loading an ODF-spreadsheet
  • Tables in OOXML-presentations are converted to shapes thereby making a "virtual table" since ODF does not support tables in presentations
  • Conversion of embedded objects is not fully supported
  • CustomXML is converted to "flat Xml" with content controls being discarded.
  • When loading a spreadsheet from ODF with formula-namespace other than Microsoft's, just the values are being converted and the formulas are disgarded
  • Animations are converted in presentations
  • The concept of "master pages" is not converted to ODF
The rest of the day consisted of hands-on labs (stay tuned for the tech-stuff from this part of the day) and a round-table discussion in the afternoon. I will talk about these part in a couple of posts in the beginning of next week.

I saw that Doug Mahugh will post the material presented to us - so watch his blog for these data.

Comments

8/2/2008 2:39:19 AM #

pingback

Pingback from osrin.net

Oliver Bell’s weblog  » Blog Archive   » DII Workshop on ODF and SP2 - complete

osrin.net | Reply

8/2/2008 11:30:15 AM #

hAl

That makes support for OOo spreadsheet as good as worthless however I don't think many serieus spreadsheet users ever considered openoffice a serieus spreadsheet. Untill the onset of openformula any effort put in spreadsheet formula's can be considered a writeoff.

It think it is probably right to focus mostly on ODF textprocessing files because that has been the main focus of ODF standard development as well and spreadsheet and presentations have largily been left behind in ODF standard en implementations.

hAl | Reply

8/6/2008 4:48:48 PM #

pingback

Pingback from blogs.technet.com

Gray Matter : Redmond ODF workshop feels pretty good

blogs.technet.com | Reply

Add comment


(Will show your Gravatar icon)

  Country flag

biuquote
  • Comment
  • Preview
Loading



Powered by BlogEngine.NET 1.5.0.7
Theme by Mads Kristensen

about ...

Image of Jesper Lund Stocholm

Name: Jesper
Nationality: Danish
Civil status: Married
Kids: a girl
Home town: CPH
iPhone-owner: Yes
ubuntu-edition: 9.04
Spam-impact: Moderate

(when spam-impact is anything but low, this blog is sadly moderated.)

Update 2009-07-11: I am experiencing really, really high spam influx these days, so I appologize if your legitimate comment is lost in the flood of crap.

OOXML ISO

Country adoption

Country ODF1.0
ODF1.1 OOXML
Ecuador x    
Norway
x  
UK x    
US x    
Vietnam x    

If you know of other countries that have decided on an approved document format, please let me know. I'll need a reference before it is added to the list.

Smile

Badges of honor

Burst A J
Microsoft Lackey  I I,
Microsoft booster   I,
Microsoft drone   I
ODF basher   I,
ODF Offender
I
I
Microsoft mole I  
IBM Drone   I
MS Provocateur   I
Pro-ms saboteur   I
Crony  I I
Microsoft's special friend I  
Micro$oft nazi I  
Microsoft minion   I
Nattering nabob O  


From Dec 16th 2009, new additions are marked with "O"

Quote

You have it backwards, OpenOffie should switch to OOXML so they are interoprable woth the worlds largest installed base.

Sorry, but the tail does not wag the dog.

From ZDNet (No_Ax_to_Grind)

License

The content of this blog is licensed under the Creative Commons "Attribution license"

Creative Commons Attribution license

This basically means, that you can do just about anything with the content I provide, but not in any way that suggests that I endorse you or your use of the content on my blog.