Where did my line go?

by jlundstocholm 30. November 2007 12:07

When we started doing our tests in the lab and started thinking about what we thought we would be seeing, we had a very clear understanding that it would not all be blue-sky conversions and that we would identify problems - some more severe than others. We were also pretty aware, that there would be areas, where conversion was just not possible.

But - I am pretty sure I speak for the rest of the group - we were quite surprised to see which areas this concerned.

On area where absolutely nothing could be converted was ... lines. Not only line art, not only complex line drawings ... but simply - lines.

Lines are done in OOXML as either VML or DrawingML and in ODF it is done using a SVG-derivative. The puzzling thing is, that this area is apparently simply left out in either of the converters. We made some simple documents (line.docx 10,47 kb) and (line.odt 6,60 kb)  [I have re-made these for this article]. When converting these files using CleverAge 1.0 on Microsoft Office 2003 and 2007, Novell OOXML Translator (on Windows and SLED) or IBM Lotus Notes 8 (on SLED), the lines are simply removed. They are not altered, they are not just hidden, they are not moved to a different location in the document ... they are just removed.

This is another example of the overall observation from our tests ... the quality of the converters are simply not good enough today. If you look at the XML in either of the files above, you will see, that even though they look different, they basically specify the same thing (start and end-point for the line drawn), so technically it should pose no problem to be able to do a better conversion.

It is often said, that the main problem with converting from ODF to OOXML (and vice versa) is incompatibilities between the formats. This example is by first glance suporting this argument, but if you dig a bit deeper into the technicality of it, is simply boils down to a problem with bad converters.

Conclusion: The world is seldom black/white ... even if people are trying to convince you so. More often, the world is grey and depressing as a rainy day. 

Comments

12/26/2007 12:18:39 AM #

Jasper

There was a new CleverAge/SourceForge converter released December 4th. http://odf-converter.sourceforge.net/

Jasper Denmark | Reply

12/27/2007 2:09:21 PM #

jlundstocholm

Hi Jasper,

I just tried the new version of the command line converter (snapshot R4259 from odf-converter.sourceforge.net/.../) and interestingly the line is converted when going from OOXML (VML) to ODF (SVG) but not the other way around. I'll post a follow-up article as soon as I can find the time.

Thanks, for your input.

Smile

jlundstocholm Denmark | 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.