Skip to main content

Home/ Document Wars/ Group items tagged tc

Rss Feed Group items tagged

Gary Edwards

ongoing · Life Is Complicated - 0 views

  • Fortunately for Microsoft, the DaVinci plugin is coming, which will enable Microsoft office applications to comply with ISO 26300. We all understand the financial issues that prompted the push to make OOXML a standard (see Tim's comment above and http://lnxwalt.wordpress.com/2007/01/21/whose-finances-are-on-the-line/ for more on this) and ensure continued vendor lock-in. However, OOXML is not the answer.
  • ODF can handle everything and anything Microsoft Office can throw at it. Including the legacy billions of binary documents, years of MSOffice bound business processes, and even tricky low level reaching add-ons represented by assistive technologies.
  •  
    Yes!  It's Da Vinci time.  I wonder if W^ has downloaded ACME 376 and taken the Da Vinci conversion engine out for a test run?  Belgium and Adobe took a look, and have expressed an interest in getting their hands on the ODF 1.2 version of Da Vinci.  California and Massachusetts have yet to comment about ACME 376, but of course they are also waiting for Da Vinci.

    I'll thank W^ for his kind comments, and make sure he knows about the ACME 376 proof of concept.  If DaVinci can hit perfect conversion fidelity with those billions of binary documents using XML encoded RTF, there is no reason why Da Vinci can't do the same with ODF.  We do however need ODF 1.2 to insure that perfect interoperability with other ODF ready applications.
  • ...1 more comment...
  •  
    Yes!  It's Da Vinci time.  I wonder if W^ has downloaded ACME 376 and taken the Da Vinci conversion engine out for a test run?  Belgium and Adobe took a look, and have expressed an interest in getting their hands on the ODF 1.2 version of Da Vinci.  California and Massachusetts have yet to comment about ACME 376, but of course they are also waiting for Da Vinci.

    I'll thank W^ for his kind comments, and make sure he knows about the ACME 376 proof of concept.  If DaVinci can hit perfect conversion fidelity with those billions of binary documents using XML encoded RTF, there is no reason why Da Vinci can't do the same with ODF.  We do however need ODF 1.2 to insure that perfect interoperability with other ODF ready applications.
  •  
    Yes!  It's Da Vinci time.  I wonder if W^ has downloaded ACME 376 and taken the Da Vinci conversion engine out for a test run?  Belgium and Adobe took a look, and have expressed an interest in getting their hands on the ODF 1.2 version of Da Vinci.  California and Massachusetts have yet to comment about ACME 376, but of course they are also waiting for Da Vinci.

    I'll thank W^ for his kind comments, and make sure he knows about the ACME 376 proof of concept.  If DaVinci can hit perfect conversion fidelity with those billions of binary documents using XML encoded RTF, there is no reason why Da Vinci can't do the same with ODF.  We do however need ODF 1.2 to insure that perfect interoperability with other ODF ready applications.
  •  
    Hi guys,

    There is an interesting discussion triggered by Tim Bray's "ongoing · Life Is Complicated" blog piece.  Our good friend Mike Champion has some interesting comments defending ISO/IEC approval of MS Ecma 376 based on many arguments.  But this one seems to be the bottom line;

    <mike> "there is not an official standard for one that (in the opinion of the people who actually dug deeply into the question, and I have not) represents all the features supported in the MS Office binary formats and can be efficiently loaded and processed without major redesign of MS Office.

    ..... So, if you want a clean XML format that represents mainstream office document use cases, use ODF. If you want a usable XML foormat that handles existing Word documents with full fidelity and optimal performance in MS Office, use OOXML. If you think this fidelity/performance argument is all FUD, try it with your documents in Open Office / ODF and MS Office 2007 / OOXML and tell the world what you learn." </mike>

    Mike's not alone in this.  This seems to be the company line for Microsoft's justification that ISO/IEC should have two conflicting file formats each pomising to do the same thing, becaus eonly one of those formats can handle the bilions of binary documents conversion to XML with an acceptable fidelity. 

    This is not true, and we can prove it.  And if we're right  that you can convert the billions of binaries to ODF without loss of fidelity, then there was no "technology" argument for Microsoft not implementing ODF natively and becoming active in the OASIS ODF TC process to improve application interoperability.

    <diigo_
Gary Edwards

Microsoft Closer on &#0092;'Office Open&#0092;' Blessing - 0 views

  • Opponents to OOXML, which include IBM (Quote)&nbsp;and the Open Document Foundation, have argued that Microsoft's specifications are unwieldy and that the standard application is redundant with the Open Document Format (ODF), which already exists. Microsoft has countered that the OOXML format is valuable because it is closer to Office 2007 and is backwards-compatible with older versions of Office. "Although both ODF and Open XML are document formats, they are designed to address different needs in the marketplace," the company wrote in an open letter published earlier this month.
  •  
    Internet News is reporting that Ecma has submitted to the ISO/IEC JTC1 their repsonsess to the 20 "fast track" for Ecma 376 (OOXML) objections.  Nothing but blue skies and steady breeze at their back for our friends at Redmond, according to Ecma's rubber stamper in chief, Jan van den Beld.

    Once again there is that ever present drum beat from Microsoft that ODF can't handle MSOffice and legacy MSOffice features - including but not mentioned the conversion to XML of those infamous billions of binary documents:
    "Microsoft has countered that the OOXML format is valuable because it is closer to Office 2007 and is backwards-compatible with older versions of Office. "Although both ODF and Open XML are document formats, they are designed to address diffe
Gary Edwards

Brian Jones: Open XML Formats : Office Open XML final draft!!! - 0 views

  • # re: Office Open XML final draft!!! @ Wednesday, October 11, 2006 1:46 PM The past incarnations of DrawingML have been chaotic. It would be interesting, out of curiosity, to get an accurate history of what changed over time, perhaps to better understand what is supported in what. Here is my take, I am pretty sure I got at least 50% of it wrong :-) - pre-Windows 95 era, Word, Excel and Powerpoint use their own vector drawing layer used to draw shapes, pictures, diagrams, art and charts. Powerpoint, acquired by Microsoft in 1987, has by far the advanced drawing layer (bi-linear gradients, opacity, ...), codenamed Escher (in reference of the famous mathematician). - In Office 95, it is decided to reuse the Powerpoint vector graphics layer in Word and Excel. Migration begins. - Migration ends with Office 97 where both Word, Excel and Powerpoint use the same vector graphics layer, publicly known as MSO (mso97.dll) - In Office 2000, it's all craze about internet and Word tries to export WYSIWYG html. For that end, mark up extensions must be added to account for the MSO drawing layer. Hence the VML (Vector Markup language). Excel and Powerpoint don't support it. Internet Explorer natively supports VML (Internet Explorer's Direct animation vector drawing layer dismissed for performance reasons). - In Office XP, VML migration ends and both Word, Excel and Powerpoint support VML whenever a document is saved as a "Single web page archive" (.mhtml extension). - In Office 2003, nothing changes. - In Office 12, MSO gets rewritten with backwards compatibility in mind. The vector drawing layer uses more sophisticated drawing functionalities which makes it easier to draw themed, 3D realistic &nbsp;objects. Technically, the differences are akin to the differences between GDI and GDI+. This new shared library is known as E2O and the corresponding mark up language is known as Drawing ML (Ecma TC45 specs). - In Office 14, ??? perhaps the drawing layer is rewritten, again, to 1) use WPF 2) to allow plugins, hence enabling much more sophisticated do-it-yourself scenarios. Use cases : custom charts ; BI analysis tools. Stephane Rodriguez
  •  
    Stephen Rodriguez gives a quick history of the MSO <> VML <> DrawingML transition in the Microsoft Product line. Note that MSOffice produces two versions of EOOXML file formats. On import os a legacy document, MSOffice will convert the doc and produce a
  •  
    Stephen Rodriguez gives a quick history of the MSO <> VML <> DrawingML transition in the Microsoft Product line. Note that MSOffice produces two versions of EOOXML file formats. On import os a legacy document, MSOffice will convert the doc and produce a
  •  
    Stephen Rodriguez gives a quick history of the MSO <> VML <> DrawingML transition in the Microsoft Product line. Note that MSOffice produces two versions of EOOXML file formats. On import os a legacy document, MSOffice will convert the doc and produce a
Gary Edwards

The big winner from Apache OpenOffice.org | ITworld - Brian Proffitt - 1 views

  •  
    Brian is once again writing about OpenOffice and ODF, this time in the aftermath of Oracle's decision to cut OOo loose and turn it over to Apache instead of The Document Foundation.  Good discussion - features a lengthy comment from the mighty Marbux where he vigorusly corrects the river of spin coming out of IBM.  Worth a careful read! excerpt: IBM seems to maneuver itself to any open source project that suits its needs, and for whatever reason they have decided to hitch their wagon to Oracle's star (or vice versa). With this historical context, there is really little surprise in Oracle's decision to go with the Apache Software Foundation, because IBM was probably influencing the decision. My second question doesn't have a definitive answer--yet. But it needs to be answered. It is simply this: how will OpenOffice.org remain relevant to end users?
  •  
    I should have added to that comment a stronger warning for the Apache Foundation Board and developers considering joining the IBM-backed Apache OpenOffice.org incubator project in regard to the danger posed by IBM and Oracle's control of the OpenDocument Formats Technical Committee at OASIS, aptly characterized by IBM's Rob Weir: "Those who control the exchange format, can control interoperability and turn it on or off like a water faucet to meet their business objectives." Rob Weir, Those Who Forget Santayana, An Antic Disposition (20 December 2007), http://www.robweir.com/blog/2007/12/those-who-forget-santayana.html What IBM, Oracle, and others can do by manipulating the ODF specification that Apache OOo depends upon is something entirely outside the control of the Apache Foundation. And as history has taught us so well, IBM and Sun exercised that control mercilessly via their co-chairmanship of the ODF TC to block all real interoperability initiatives. That is the very reason that only ODF implementations that share the same code base can interoperate. And if one were tempted to think that IBM and Sun/Oracle would not even consider manipulating the ODF specification to their own commercial advantage, consider the fact that in writing the quoted statement above, Rob Weir was speaking from deep personal experience in in such activities. So beware, both Apache Foundation and LibreOffice developers.
Jesper Lund Stocholm

Groklaw - Digging for Truth - 6 views

  • You harmed us and our families. You harmed the public, and you will have to live with that judgment from us.
    • Jesper Lund Stocholm
       
      Legendary comment ... :o) "You harmed our families. You harmed the public and you will have to live with that judgement from us"
  •  
    What an amazing conversation. It's true that ODF was NOT designed to be compatible with MSOffice and the legacy binary format. That's not to say there were not considerable efforts within the OASIS Open Office XML TC (ODF) pushing for compatibility. But Sun successfully held off these efforts, insisting that ODF was not designed to be compatible with MSOffice or the MSOffice binaries. Many asked the obvious question, "How are end users supposed to convert their information (billions of legacy "in-process" binary documents) to ODF if ODF is not designed for that conversion?" Stellent, represented by Phil Boutros, and Corel, represented by Paul Langille and Tom Magliery, were particularly obsessed with this problem. Without "compatibility", how were end users supposed to convert their documents? Needless to say, Sun prevailed. ODF is 100% perfectly compatible with OpenOffice/StarOffice, by design. It is not compatible with the billions of "in-process" compound business documents essential to world trade, commerce and information exchange. What a shame, ~ge~
Alex Brown

[office] OpenDocument TC coordination call minutes 2009-10-19 - 2 views

    • Alex Brown
       
      The strange lack of fanfare about this is deafening.
« First ‹ Previous 61 - 66 of 66
Showing 20 items per page