Slashdot Mirror


ISO Approves OOXML

sTeF writes in, with the hope that this is an April Fools joke. Doesn't look like it though. An article up at Intellectual Property Watch claims they have obtained a document (PDF) enumerating the vote after Microsoft's OOXML won ISO standard status.

94 of 435 comments (clear)

  1. Support Needed. by gnutoo · · Score: 5, Insightful

    Microsofts statement hailed the appearance of extremely broad support for the standard at the end of the ISO voting process.

    Broad? I think they mispelled bold faced fraud.

    1. Re:Support Needed. by mrbluze · · Score: 2, Funny

      Broad? I think they mispelled bold faced fraud. Or maybe they won the support by supplying extremely broad broads, or something similarly corrupt.
      --
      Do it yourself, because no one else will do it yourself. [beta blockade 10-17 Feb]
    2. Re:Support Needed. by nuzak · · Score: 5, Funny

      > I think they mispelled bold faced fraud.

      Perhaps their OOXML formatters have problems with boldface, and that's just how it rendered.

      --
      Done with slashdot, done with nerds, getting a life.
    3. Re:Support Needed. by Anonymous Coward · · Score: 2, Funny

      No, they misspelled bribe.

    4. Re:Support Needed. by gnutoo · · Score: 2, Insightful

      Problems? That's what digital restrictions are for!

    5. Re:Support Needed. by ShieldW0lf · · Score: 5, Funny

      ISO... ISO... aren't they that defunct organization in Switzerland, the one that used to represent standards before they got into the advertising business and disappeared?

      --
      -1 Uncomfortable Truth
    6. Re:Support Needed. by Zymergy · · Score: 2, Insightful

      No, No, its not that random. They have an ISO standard for it!
      -They use the "ISO Standard" for the voting and selection procedures as implemented by the International Olympic Committee: http://www.google.com/search?num=50&hl=en&safe=off&q=International+Olympic+Committee+corruption&btnG=Search

    7. Re:Support Needed. by Xiph · · Score: 5, Interesting

      Lets wait for the announcement tomorrow, ISO is deliberately avoiding an Aprils Fool announcement, which could mean that it might be of a more serious nature.
      Of course if the serious nature of the announcement is approving OOXML, I'll be sending them some emails telling them what a disgrace the process has been.

      It might not change anything, but I encourage anyone with the ability to send email to do something similar.

      --
      Blah blah sig blah blah blah irony blah blah
    8. Re:Support Needed. by Ilgaz · · Score: 4, Insightful

      Investigation should have started right after they gathered ISO support for .NET. Sold out geeks kept claiming .NET is a standard and while they are stuck on version 1.0 of standard with their "mono", .NET 3.0 Apps are all over the place. .NET became Dolby Digital EX while they are stuck in Mono.

    9. Re:Support Needed. by Gravatron · · Score: 5, Insightful

      Given the nature of the corruption this process showed, I don't think sending email is going to do much good unless said email contains bank account numbers pointing to a few million dollars.

    10. Re:Support Needed. by sxeraverx · · Score: 3, Funny

      Yes, and people voted for Bush. The second time around.

    11. Re:Support Needed. by supernova_hq · · Score: 5, Funny

      Or perhaps bank account numbers they recognize that no longer point to a few million dollars, if you catch my drift.

    12. Re:Support Needed. by EvilNTUser · · Score: 3, Insightful

      Forget about the ISO. Send your emails to your antitrust authority instead. I doubt the US will do anything, but the EU might.

      Make sure you concisely explain why truly open document standards are important and what is wrong with Microsoft's offer.

      --
      My Sig: SEGV
    13. Re:Support Needed. by n3tcat · · Score: 2, Insightful

      It doesn't have to point to a few million dollars in gains, so long as you point out the millions of dollars in losses they will suffer with a lack of global support.

    14. Re:Support Needed. by Bert64 · · Score: 2, Informative

      I seem to remember there were no votes against it, and 1 abstention... The actual number of countries voting was much smaller too, as microsoft hadn't stuffed the system with easily bought countries by that point.

      --
      http://spamdecoy.net - free throwaway anonymous email - avoid spam!
    15. Re:Support Needed. by pablochacin · · Score: 2, Interesting

      I'm afraid that this hardly will hurt ISO too much. They have some of the most important and widely used certification standards like ISO1400 (environmental management ) and ISO900 (quality management systems). Sorry, but they will be up and running for a long time.

    16. Re:Support Needed. by ShieldW0lf · · Score: 2, Insightful

      I'm afraid that this hardly will hurt ISO too much. They have some of the most important and widely used certification standards like ISO1400 (environmental management ) and ISO900 (quality management systems). Sorry, but they will be up and running for a long time.

      Yeah, I know a lot of people would like to receive credibility because they met the ISO certifications. But I'm afraid that the ISO certifications doesn't really give you credibility like it used to.

      A lot of people like the prestige that a university degree brings, but when people find out that all you had to do was pay a bunch of money and you got your certification in the mail, they're not going to give you the job. This isn't any different.

      Welcome to the modern age, where the dollar value of a good name is in how long you can deliver substandard overpriced service before people stop coming back.

      --
      -1 Uncomfortable Truth
    17. Re:Support Needed. by chrish · · Score: 2, Funny

      The quality management systems one is ISO 9000.

      You need to review your process.

      --
      - chrish
    18. Re:Support Needed. by pablochacin · · Score: 2

      I Never said I hold one :-D

    19. Re:Support Needed. by Bogtha · · Score: 2, Interesting

      ISO is deliberately avoiding an Aprils Fool announcement

      Which in itself is an announcement. If they rejected OOXML, would anybody think it was a joke? No. If they rubber-stamped OOXML, would anybody think it was a joke? Yes. So, by admitting there is a danger of it being construed as a joke, what is ISO telling everybody?

      It's either that, or they aren't bothered about the joke aspect and are just using it as an excuse to stall while they figure stuff out.

      --
      Bogtha Bogtha Bogtha
  2. Do they not know their own rules? by Adaptux · · Score: 5, Informative
    While I still have some doubts regarding the genuineness of this document (for example, why does it purport to come from the ISO Central Secretariat rather than from the ISO/IEC "Information Technology Task Force" (ITTF) which has been managing the voting process?), the document seems to accurately reflect the previously available information regarding the voting decisions of the national standardization bodies.

    However, how valid are those votes? For example, the ISO/IEC JTC1 directives seem to pretty explicitly forbid changing the vote from "disapprove" to "abstain" like AFNOR (the French standardization organization) did (under the influence of heavy lobbying from Microsoft and HP).

    1. Re:Do they not know their own rules? by KwKSilver · · Score: 5, Funny

      The rules? Haven't you heard of the Golden Rule: "He who had the gold makes the rules!" This is the "new and improved" ISO, aptly described by someone at Groklaw:

      I = I
      S = Sold
      O = Out

      --
      If you want your life to be different, live it differently.
  3. Abandon All Hope by Anonymous Coward · · Score: 5, Funny

    Ye Who Code This Standard!

    1. Re:Abandon All Hope by I'm+Don+Giovanni · · Score: 3, Insightful
      "Cue persistent formal requests to MS for specification details regarding "auto space like Word 95" et al. It's obviously the first step on the road to litigation/anti-trust cases."

      --------------
      This shows your ignorance (and that of the general slashdot population). The "auto space like Word 95" issue has been addressed in the latest spec (the spec that's beeen approved). That "auto space like Word 95" behavior, and the others like it, are now marked as "deprecated" (i.e. should not use for new documents) AND are fully spec'ed.

      Compatibility Settings - AutoSpaceLikeWord95

      There has also been a lot of interest in the Compatibility Settings that include the famous "AutoSpaceLikeWord95" or "truncateFontHeightsLikeWP6". Ecma worked to provide in this batch the full information necessary to implement all compatibility settings without any dependency on any product. This documentation is provided for the completeness of the spec, but these features should not be used when creating new documents. I'll discuss the compatibility settings in more detail in my next post And here are further details.

      See, this is the problem: So many of you that are railing against OOXML and against the ISO process are completely ignorant of the facts on the ground. The technical issues that you claimed to be concerned with have been addressed. So there's no technical reason to reject OOXML (there may be *political* reasons, but such reasons should have no bearing on ISO).

      For example, the Czech Republic voted NO in September, but switched to YES. Why? Because nearly every one of their issues have been addressed now.
      http://xmlguru.cz/2008/01/ecma-response-to-czech-ooxml-comments
      Do you really expect the Czech Republic to continue to oppose OOXML when nearly all of its objections to the original spec have been fixed? Why would they do that? The problems were fixed, so they switched to YES, and this was the case with many countries (those without a political agenda).

      It's like you guys are impervious to the fact that the OOXML spec has been quite improved (and that you're ranting about some old issue like "auto space like Word 95", an issue that has been resolved, *proves* it). Maybe, just maybe, if you took some time to learn the facts, learn how the spec has been changed since Sept, you'd not be so against OOXML (unless, as I suspect, your opposition is due to *political* reasons, under the mere guise of technical reasons).
      --
      -- "I never gave these stories much credence." - HAL 9000
    2. Re:Abandon All Hope by profplump · · Score: 5, Insightful

      So apparently it's not valid to complain that the new standard shouldn't need to support "truncateFontHeightsLikeWP6" in the first place? Wouldn't it be technologically superior to require MS Word to emulate "truncateFontHeightsLikeWP6" using standard formatting directives, rather than forcing every other implementer to code for compatibility with some file format that isn't even part of the spec?

      Try this one one for size:
      "15 years ago we had a file format that stored text using EBCDIC encoding. While we no longer write any files using this encoding, we propose that the new standard file format include an EBCDIC mode. We realize that traditional arguments for "backward compatibility" don't apply -- obviously none of our 15-year-old products ever produced any output in the new file format being proposed -- and we concede that we could just convert to UTF-8 encoding when saving old documents into the new format. But such conversions would require more work on our part than simply adding another encoding mode to the new file format and reusing our existing code to render in that mode. We acknowledge that this formatting directive will only benefit our product, as no one else can read our 15-year-old, unpublished format, so we'll note that the EBCDIC mode is deprecated. In spite of that note however, we will generate new files using EBCDIC mode, and therefore competing implementations must implement it as well to be functionally compliant."

    3. Re:Abandon All Hope by profplump · · Score: 4, Insightful

      If you'd like to comment on how some people are not aware of recent changes to the specification, and how those specific arguments against the spec aren't technically sound, be my guest. In some cases, such as the specific comment you replied to, you'd be perfectly justified.

      But your language doesn't contest the validity of a particular comment -- even your most recent comment here accuses "most of [us]" of willful ignorance. And your prior comment likewise accuses the community at large of having only political objections to this new "standard". It's a bit hypocritical to make generalized accusations and then dismiss rebuttals as irrelevant because they didn't address the specific comment to which you general attack happens to be attached.

    4. Re:Abandon All Hope by seebs · · Score: 2, Insightful

      Nice flagrant lie.

      Not about the deprecation. About its impact.

      The impact of deprecation? ZERO.

      Everyone still has to implement it, or they are not correctly implementing the standard for existing documents. Failure to implement that means failure to comply with the standard.

      This is how we know OOXML is not a real standard. It's just a documentation of the state of MS software at a particular point. In a standard intended for actual use by more than one party, the historical things would not be a part of the standard at all; they would be extensions which most people wouldn't use.

      Seriously, I went over this document not that long ago. It's still a joke. It's still not a technically viable standard. The "addressing" you point to doesn't come close to the minimal requirements we'd have imposed on one of the real standards.

      I could be mistaken. I mean, hey, I only did about a decade of work on ISO C. Maybe nowadays we just slap any old thing together, and declare that it "fixes" a problem if we say that something is deprecated, and while everyone is absolutely required to implement it, we don't want people making it happen in new code anymore.

      But I don't think so.

      --
      My blog: http://www.seebs.net/log/ --- My iPhone/iPad app: http://www.seebs.net/seebsfrac/
    5. Re:Abandon All Hope by Anonymous Coward · · Score: 2, Interesting

      BTW, there's no requirement to handle deprecated features, just a there's no requirement for browsers to handle every piece of HTML.
      But Microsoft's promise not to sue you over violating their patents on parts of OOXML only applies to complete implementations. So, those deprecated features are just as optional as not getting sued is.
  4. Here come Barbra... by Naughty+Bob · · Score: 4, Interesting

    I think we all expected MSFT's chicanery to work in the short-term.

    But witness that recent brand-awareness survey- As understanding of the computer world seeps into mainstream conciousness, MSFT's rotten practices are coming back to haunt them.

    Let's hope that the mainstream media picks up on the insanely obvious corruption involved here, and the Streisand Effect kicks in.

    I don't think this is the best outcome for open/free standards, but it should still be viewed as a win, long-term.

    --
    "Be light, stinging, insolent and melancholy"
    1. Re:Here come Barbra... by v1 · · Score: 2, Insightful

      And they ask "why?" Because there's nothing to bolster your company like buying a standards committee or two. I wonder which one they'll shop for next? ISO is going to be a pretty tough bargain to beat.

      --
      I work for the Department of Redundancy Department.
  5. Thank God by Mateo_LeFou · · Score: 5, Funny

    I've had so many clients asking if I can scrape data from their legacy lockinware. Now I can confidently say "Yes" and bill them for the 1400 hours it takes to read this spec.

    Thank you MS!

    --
    My turnips listen for the soft cry of your love
  6. Good. Now at least we know where the filth is by unity100 · · Score: 5, Insightful

    and what to avoid. and no, im not a bigoted fanboi of any camp - im just reflecting upon the series of stunts ms pulled to get that format validated. judging from the level they lowered themselves in dirty work to get this through with bribing and manipulating, i'd say that their format has to be total crap. else it wouldnt need that level of filthy campaigning.

    1. Re:Good. Now at least we know where the filth is by loafula · · Score: 3, Funny

      so, basically microsoft is like hillary clinton?

      --
      FOXTROT UNIFORM CHARLIE KILO
  7. Basically, what they just did by Anonymous Coward · · Score: 5, Interesting

    was to retroactively standardize 20 years of legacy document formats. All MS-OOXML really is is a forwards-compatible XML serialization of the Microsoft Office 2003 formats.

    And yes, many at Microsoft do consider the whole standardization process to be a sham. (I know, because I work there.)

    1. Re:Basically, what they just did by eerok · · Score: 4, Interesting

      "All MS-OOXML really is is a forwards-compatible XML serialization of the Microsoft Office 2003 formats."

      In other words it's not an open document format due to all the legacy proprietary crap it embodies. Thanks, but we knew that already.

      Actually, all MS did was make a joke out of the process of establishing standards. That's okay, the world can take a joke. But it holds grudges.

      --
      "The happiness of credulity is a cheap and dangerous quality." -- George Bernard Shaw
    2. Re:Basically, what they just did by Chris+Burke · · Score: 4, Insightful

      explain to me why such a pragmatic decision should come as a surprise to anyone. or, to put the question another way, how many industrial standards simply rationalize practices of long standing?

      Ah, that's very common. There will be various competing versions of something, and they vie in the marketplace as much as before standards boards, and eventually one is chosen as the standard. Including using dirty tricks to influence the process, to gain the advantage of it being your version which all your products already use that becomes standard.

      Here's what's different:

      At the end of the day, after the politics ended, the intent and result of these proceedings was to standardize and thus increase interoperability. The standards themselves enabled that, allowing multiple implementations of the standard that would work together. Even if one company gains an advantage in the near term, that doesn't last long and then things just start working better together, and choice and opportunity are increased.

      This is the exact opposite. The intent and result of this process is to damage interoperability by creating a standard that nobody can duplicate, that not even Microsoft themselves have implemented. It's only purpose is to derail acceptance of a true open standard like ODF. There will be no market around OOXML tools and products, because the only one that will ever use it is MS Office, and they aren't even obligated to follow the standard they created. That doesn't matter. All they want to be able to do is shout "We're an ISO standard!" when the government rep starts talking about how they require "open" documents. That's all.

      --

      The enemies of Democracy are
  8. ISO death bell by mugnyte · · Score: 5, Insightful

    And with that - the "standards body" of ISO was effectively taken down. FUD shovelers everywhere will begin the slow, purposeful targeting of Government, school and corporations to use MS's products for long-term archival concepts.

      Perhaps with only gnashing of teeth from the geek side, initially. After some time, say 3 or 4 product cycles, MS's formats, content and programs will have slipped into breaking changes - with various patches, pieces, conversion tools and sunsets. Then and only then, will the true colors of MS's saletroopers, who overrule the tech side, be shown. But you know this - why else would you be trawling the /. comments down here?

      In other news, the business of writing code to munge data from old MS formats into new MS formats is alive and well. Programmers rejoice! There is an endless market of chagrined middle managers who are willing to port old crap to new crap for good $/hour.

    1. Re:ISO death bell by Anonymous Coward · · Score: 2, Informative

      LOL. You clearly have no understanding of the ISO. They're responsible for thousands of standards in a wide variety of industries. Even if people ignored their computer-related standards, few would notice. The ISO is mostly known for their manufacturing process and quality control standards.

    2. Re:ISO death bell by gregorio · · Score: 2, Insightful

      A standards body is non existent if people/governments and large corporations openly accuses them or suspects fraud.
      ISO was never accused of fraud by anyone relevant. The only time when "irregularities" were mentioned, it was related to Norway's own standard comitee, and not ISO's.

      They would gather and setup ISO 2.0. If you think about JPEG being an ISO standard, you can imagine how important ISO is. Wonder if they will approve "HD Photo" from Microsoft as a ISO standard too?
      So...? Lots of international standards, from ISO, DIN, JIS, ASTM and others are redundant. Those institutions aren't responsible for choosing "the format". Their job is to give a name to accepted technical specifications, to distribute them and also inspect how companies and products are being certified in relation to these standards.

      Almost every single OSS nerd, even the ones opening anti-ooxml websites and posing as experts, are spweing this crap around the interwebs. Repeat after me: standard bodies are not responsible for definitive and unique specifications, lots of standards fill the same void and specify things related to the same subjects.

      With that decision, they are open to every kind of accusation. A company can remind "OOXML" when a completely irrelevant standard passes which would be in favour of a large corporation.
      Standards are not laws. Companies will only follow standards only if they're useful for the process of making money. Standards are created to allow the participating parties of a project, including the open market, to speak the same language. And that's not because they want to play nice, but because that saves money. If a standard is not relevant to the company's profit margin, it will not be used weather it was defined by Microsoft or by friendly buddhist monks.

      Companies should ask themselves "What if Microsoft goes chapter 11 in matter of a decade" and decide their formats based on that. All computers I owned in 1980s were made by huge, untouchable large companies which nobody could even imagine their fall. It happened.
      They should only ask that if their documents are not stored in the format defined by the ISO standard. If their documents are OOXML-based, your suggestion is pointless.
  9. Weirdest April 1st Ever! by darkfnord23 · · Score: 4, Insightful

    Assuming it's not a joke... Anyone using this standard for anything deserves a punch in the face.

    1. Re:Weirdest April 1st Ever! by codemachine · · Score: 5, Interesting

      The fools are those at ISO who voted to approve this horrid "standard". It definitely wasn't good enough to be fast-tracked, let alone made into a standard.

      Should be interesting to see the next moves from IBM and Sun though. Could there be some sort of challenge or appeal coming? I don't think we've seen the end of this.

    2. Re:Weirdest April 1st Ever! by the_olo · · Score: 5, Informative

      Could there be some sort of challenge or appeal coming?

      According to ISO press release , "Subject to there being no formal appeals from ISO/IEC national bodies in the next two months, the International Standard will accordingly proceed to publication". So there's still 2 months for appeals from NB's.

  10. pyhrric by apodyopsis · · Score: 5, Interesting

    Its the Pyhrric victory to end all.

    (1) if they lost the ISO process then they lost

    (2) they won the ISO process then they lost as it forced a deep examination of the standard, and raised critical questions and caused them more problems then it solved.

    (3) if nobody else implements this flawed standard then they lose as some Goverments are now also specifying cross platform implementation as well as open standard (perhaps in response to this mess)

    (4) if (and this is real unlikely) there are other implementations of this standard (eg OO) then they lose as MS Office is no longer required to be ubiquitous on the desktop

    This is NOT really a win for MS the way that I see it. They can spin this how they want and surely get away with it for a large amount of the population - but big business and govermental contracts (where the real money is) are already looking for an escape from propietry formats and have been for a while.

    I'm really fucked off about the perversion of the ISO system, the bad practice, the lack of any "technology morals" in decisions that needed to be unbiased. But I am not that upset about OOXML being passed - I really do not think MS has won this one.

    The important thing to watch now is how MS spins this and where the important money goes (big contracts, goverment).

    1. Re:pyhrric by holloway · · Score: 5, Informative

      I agree. We're back to where we were a year ago only now with a lot more awareness of the office monopoly and how much money is wasted.

      Here are two reports on OOXML that I recently released, one (PDF, 0.9MB) and two (PDF, 0.8MB).

    2. Re:pyhrric by MightyMartian · · Score: 2, Interesting

      (3) if nobody else implements this flawed standard then they lose as some Goverments are now also specifying cross platform implementation as well as open standard (perhaps in response to this mess)


      Open source developers will likely shoot themselves in the foot there. OOXML support is already under way for OO.org, and you can be sure that KOffice will likely follow, along with a number of other open source office apps. These will be similar to the efforts to get the Office 97-2003 formats working, seeing as the specs, even once decrypted, will only get you so far. It won't be good enough for these apps to be drop-in replacements, and even if it is, Microsoft will be recreating OOXML with every new release, so it will be the same old game of catch up. Even worse, Microsoft might even all-but-abandon OOXML, leaving it in as a legacy format, but defaulting to some new document format.
      --
      The world's burning. Moped Jesus spotted on I50. Details at 11.
    3. Re:pyhrric by Anonymous Coward · · Score: 3, Funny

      It's part of Microsoft's master plan to force OpenOffice to become a big, bloated, unmaintainable blob of code.

    4. Re:pyhrric by Anonymous Coward · · Score: 2, Informative
      It's not really OOXML support, it's Microsoft Office 2007 support. The OpenOffice.org support includes things that MS didn't submit to Ecma or the ISO like OLE, VBScript Conversion, etc.

      So it's the same old story about reverse engineering Microsoft Office, not implementing a poorly defined inconsistent "standard".

    5. Re:pyhrric by Handover+Phist · · Score: 2, Insightful

      Perhaps because OO wants to keep as much MS Office compatibility as it can.

    6. Re:pyhrric by Adaptux · · Score: 3, Funny

      they won the ISO process then they lost as it forced a deep examination of the standard, and raised critical questions and caused them more problems then it solved.

      Microsoft has a legitimate business interest to be seen as the leader in office document formats, and this interest is best served by participating in the ISO/IEC processes for refining and improving OOXML in good faith and with an active desire to resolve the issues that are raised.

      While I am highly critical of all national standardization organization officials who have contributed to allowing Microsoft push OOXML through via the "fast track" which IMO has proved to be clearly inappropriate, I'm really getting the impression that there is a tendency of seeing Microsoft primarily as an enemy which is getting in the way of our abvility to see reality as it is. I can personally testify that at the BRM and since then, Microsoft has shown every indication of willingness for the known technical shortcomings of OOXML to be corrected, and since I believe that it is in Microsoft's best interest to continue in this direction, I currently see no reason not to believe the Microsoft people that I have been communicating with when they indicate that it is Microsoft's intention to continue with this bona-fide cooperative stance regarding OOXML.

    7. Re:pyhrric by Ambidisastrous · · Score: 2, Informative

      Presumably because they thought this might happen. OpenOffice already supports pretty much every format under the sun, so deliberately ignoring OOXML would be obvious, petty, and somewhat self-destructive.

      It would be a lock-in tactic, and open-source software isn't really capable of that: If there was demand for OOXML import/export, and Sun didn't implement it, someone else would write an extension for it anyway (or worse, fork the whole project). If organizations are going to ask for OOXML support (if only to handle the stray .docx file that comes from outside), then it's better to have OOo support it competently than require an extension that does it poorly.

    8. Re:pyhrric by the_olo · · Score: 2, Informative

      I don't mean to sound like format correctness Nazi, but your PDFs could be much, much smaller.

      You just need to substitute the Nimbus family of fonts (which are in Type 1 format) for some corresponding TTF fonts, like the FreeSans/FreeSerif families.

      The problem is that OpenOffice PDF exported currently cannot do subsetting for Type 1 fonts, only for TTF fonts. So it embeds the full Type 1 fonts (Nimbus in your case) in the file. All the characters, including unused ones, like Japanese, Hindi and Chinese glyphs!

      That's why your PDFs are almost 1 megabyte when in fact they could be twice as small.

      Look in the properties of your PDFs (or use pdffonts utility) - when your see font names like "DAAAAA+font_name" then it's good - they are subsetted.

      But font names that aren't prefixed with those "?AAAAA+" strings are embedded fully, without subsetting - they occupy lots of space!

      Eliminate those fonts from your document when exporting to PDF, until OpenOffice issue 46305 is resolved (not likely in the near future...).

  11. .doc attachments by csk_1975 · · Score: 2, Insightful

    The referenced comments from the NBs are .doc files. If ISO mandates the use of MS Word .doc files is its existing internal processes what hope that anything other this result?

    Is the tag part of the ISO approved spec?

  12. Why no April Fools Today. by Foobar+of+Borg · · Score: 4, Insightful

    There is no April Fools today since the real news is comical enough (though in a tragically funny sort of way).

    1. Re:Why no April Fools Today. by Dr.+Eggman · · Score: 4, Funny

      But, there is an April Fools joke today on Slashdot! It's just subtle. Check your 'Foes' list and you'll see every editor has been added to it.

      --
      Demented But Determined.
    2. Re:Why no April Fools Today. by artanis00 · · Score: 4, Funny

      I already had all the editors on my Foes list, you insensitive clod!

  13. From the box of Office 14 by Tatsh · · Score: 3, Insightful

    * Microsoft's own Open Office XML (OOXML) format is now an ISO standard. This means anyone with software capable of reading OOXML can can read your documents.

    Translation:
    * Whilst OOXML is an ISO standard now, we still own the patents and the right to sue anyone who implements it (even if we issued a covenant not to sue; covenants mean nothing to Microsoft, just to let you know). Lastly, OOXML is open however we are only ones who know how to read the blob (binary) parts of the standard perfectly and no one else can.

    Internal document at Microsoft:
    * Finally we have an ISO and ECMA standard, just so we can say to you that we care about the future of digital documents, when we really just want more money. Saying OOXML is an ISO standard is a great way to have businesses automatically approve of our standard. And now we can put ODF and its hopes and dreams in the dark.
    ---
    I am very disappointed in ISO, OSI, and ECMA. I held them with high regard, until they started approving standards and licences of a company that has been holding back the PC industry all to make a little more money. I will ignore the three bodies for now, until they withdraw their positions on these Microsoft entities.

    When will MIPS-based-CPU desktops running Linux at high speeds (much faster than any x86 at the same clocked speed) take over the home PC market? x86 and even x86-64 are dying faster than we can count in my opinion the way things are going.
    ---
    (Written on Gentoo Linux 2.6.24.3 AMD64, Mozilla Firefox 2.0.13, KDE 3.5.8)

  14. Good Luck. by inTheLoo · · Score: 5, Interesting

    You are right about the size of the market but wrong about how much money it will make you and what tools to use. Sun and IBM will give you PDF of ODF output and a handy database system to keep it all. So can anyone else with Open Office. Some people are going to be automating the process better than others but it's going to be a competitive market. That's the whole point of standards, to avoid the massive cost of reinventing what should be obvious and spend resources on things people actually want. MSXML is going nowhere in a market like that.

    --
    No calls now, I'm ...
  15. Does anybody else... by $RANDOMLUSER · · Score: 5, Interesting

    ...find it ironic that the document describing OOXML's ISO adoption is in PDF format?

    --
    No folly is more costly than the folly of intolerant idealism. - Winston Churchill
    1. Re:Does anybody else... by Creepy+Crawler · · Score: 4, Funny

      That is because Microsoft's implementation is not 100% OOXML compatible.

      --
    2. Re:Does anybody else... by Bert64 · · Score: 3, Insightful

      Intel would love to buy AMD, and VIA, and be the only source of x86 compatible chips...
      Intel, like any other company, don't want motivation to progress. They want to continue selling old products for as long as possible at the highest price point they can, not be forced to develop something new and reduce prices in order to compete. Lucky for us consumers Intel don't have that ability, thanks to AMD... The problem is that Microsoft do have that ability, and they abuse it as much as they can. In a competitive marketplace, ODF would be prevalent (supported by a majority of vendors) and OOXML would die a death (supported by only one) and microsoft would have been forced to implement ODF like everyone else.

      --
      http://spamdecoy.net - free throwaway anonymous email - avoid spam!
  16. Re:Finally by Bryansix · · Score: 4, Interesting

    Yikes. I like Office 2007 but it is a pain in the ass to teach people to use. Banners? Really? No File Menu? WTF MATE!!! Believe me, Open Office is going to get my vote when it comes time to upgrade here.

  17. Agree - easy solution too by cheros · · Score: 4, Interesting

    I think the best approach to this is to:

    (a) Require MS to be true to their own standard (or immediately fall foul of anti-monopoly rules - hello EU)
    (b) Ensure every procurement decision in favour of MS because of this to REQUIRE to implement MSOOXML as well. No point using it for criteria otherwise.

    That way I give it a month before reality hits. And less than that for the EU to collar the b*stards again, and this time it won't be a baby fine because that has proven not to have too much of an effect. A cute punishment would be making ODF compliance mandatory in the EU. Given that they haven't implemented a proper filter this may completely nuke the franchise. And without the Office franchise there isn't much left of MS because brute forcing people into an upgrade to something as bad as Vista hasn't exactly worked out too well. Couple that with sub prime problems and companies as well as end users may start to seek for more economic ways to spend their money.

    This story is FAR from over.

    --
    Insert .sig here. Send no money now. Owner may sue, contents will settle. Batteries not included.
    1. Re:Agree - easy solution too by earbenT · · Score: 3, Insightful

      And without the Office franchise there isn't much left of MS because brute forcing people into an upgrade to something as bad as Vista hasn't exactly worked out too well. Microsoft still has DirectX to lure the gaming market back to Windows.
  18. I don't like this idea by failedlogic · · Score: 2, Interesting

    Of all (or most) of the reasons for not liking the MS OOXL file, I oppose it the most because what if 5 or 10 years down the road with a new Office version, they decide to change the format. With this supposed "standard" we might all have to convert our documents. Locking your work in this format is also bad news if you want to retrieve it later. At least the folks at Wordperfect were kind enough to not have changed the format since the 5.x release.

    I've decided to use LaTeX to make a final copy of my documents in PDF format after writing up the document w/o markup in Text or RTF document. I'm new to using it, but the markup for most of my purposes is as easy as HTML (I don't use tables or math very much). Its too bad others don't know how easy it is (esp. with templates you can download).

    Some of my files are 10 years old and I've archived them all pretty well. But if I use a current version of Word to open it up, the formatting is all screwy. All the more reason to change.

    1. Re:I don't like this idea by failedlogic · · Score: 2

      There's lots of people that don't know and have used GUI tools to markup a webpage. Its not to say the code was good, but it obscures the use of HTML and learning the language. Nobody has to hard-code a MS Word document with whatever formatting language it uses. I think if TeX catches on (I hope it will) a good GUI would help adoption LyX is a nice step forward.

      That said, I hope TeX language is standardized. Its increasingly popular in academia - in many fields outside of math and science, and I think its catching on in other areas as well (writing in languages other than those with romanized alphabets. Its in the last use particularly I think would help push standardized / ISO approval.

  19. I need enlightenment... by v(*_*)vvvv · · Score: 2, Interesting

    Doesn't the old cliche of "the great thing about standards is there are so many to choose from" apply here? Or does this mean a ton of people will now be forced to use it and Microsoft will reap the benefits?

    Sorry, but every article I read about OOXML is about the voting and standardization irregularities, and nothing I've found reviews OOXML from the users standpoint, or implications of it being ISO-ed...

    1. Re:I need enlightenment... by WWWWolf · · Score: 5, Informative

      Sorry, but every article I read about OOXML is about the voting and standardization irregularities, and nothing I've found reviews OOXML from the users standpoint, or implications of it being ISO-ed...

      From user's point of view, this rushed standardisation means that the whole point of the standardisation has been defeated in OOXML's case. It also means that we now have two standards that solve the exact same problem, and thanks to the Marketing, the technically far worse format has a chance at winning: If OOXML becomes the dominant format, the promising future from OpenDocument may not be realised. It can be a major setback.

      And what was the point of the standardisation? What was the golden promise of OpenDocument? Interoperability, plain and simple.

      Simply put: In the current state of affairs, OpenDocument is implementable by third parties. OOXML is not. There can and will be many OpenDocument applications. If OOXML won't get fixed, there will be one and only one application with anywhere near compliant OOXML support.

      With OpenDocument, you can edit the documents in any ODF-compliant application - or process them with any external tool, or generate them from scratch programmatically - and there's no problems because the standards is complete, well specified, and not hopelessly tied to one application. OOXML, in comparison, has nothing of this: There's a bunch of nasty features that make writing completely compliant applications difficult, if not impossible. The end result will be that there's one application that processes OOXML "perfectly" (MSOffice) and the rest work when they work (and since consumers expect perfect behaviour, it means they aren't used very much, no?)...

      Sure, the interoperability dream is still very much there, because ODF is still out there. It's just that now we have a completely redundant standard that is a) technically inferior but b) Microsoft will make you either use it, or cry and use it.

    2. Re:I need enlightenment... by Neuticle · · Score: 4, Informative

      Sorry, but every article I read about OOXML is about the voting and standardization irregularities, and nothing I've found reviews OOXML from the users standpoint...

      That's pretty much because:
      a) the voting irregularities are IMMENSE
      and
      b) there is no review on OOXML from the user's standpoint, because there is NO implementation (ZIP, ZERO, NONE) of the ISO candidate version of OOXML to review. Not even from Microsoft, who are using a different version now, and (IIRC) have stated that they WILL NOT be using the ISO version in the future, if it is approved. AND it is likely that there will never be a complete 3rd party implementation of the ISO OOXML standard because it is so long, complex and dependent on patents and references to legacy closed source software. MS happens to own that source and those patents and aren't about to give them away. So basically it's a dead end mockery of the ISO process.

      If that's not enough to answer your questions AND piss you off, do some more reading on the topic.

      Try reading up on how and for what the Fast-track process has been used in the past: Mature, complete and currently implemented industry standards that are just being formalized; Not slap-dick, fly-by-night, throw-in-kitchen-sink 6000 page cluster-f*ks like OOXML.

      --
      "Cheeze it!" - Bender
    3. Re:I need enlightenment... by ekhben · · Score: 2, Insightful

      I think you're mistaken. There will be no applications that process OOXML perfectly. Would you, in all seriousness, prepare a slideshow for an important presentation using Office 2003 for Mac, when the presentation will be given by Office 2008 for Windows? Not twice, I'm sure. And of course, it's even worse if you do it the other way around. I'm sure glad I'm in a job where I have the luxury of simply deleting documents sent to me in MS formats and instructing the sender to try again.

  20. Fix the headline, please by Eggplant62 · · Score: 2, Informative
    Interesting headline you have there. I think it should read:

    Microsoft buys ISO certification; World looks on with drool on its face

  21. Re:good by rtb61 · · Score: 2, Insightful
    Me thinks you have very little under standing of fractions, I'm getting more like 9/10 of /. is opposed to the corruption of ISO by M$ and the creation of a totally pointless unusable unstandard. When you have read and memorised a 6000 page standard, then you can come back and comment on it's value.

    Standards should be as brief, accurate and stable as possible, in order to be able to cost effectively apply them. This is just a sickening M$=B$ marketing exercise.

    At least in Australia it looks like OOXML is dead http://www.standards.org.au/downloads/080331_Aust_maintains_abstain_position_on_OOXML.pdf as it has been rejected by the Australian Government.

    --
    Chaos - everything, everywhere, everywhen
  22. Re:good by prockcore · · Score: 2, Insightful

    Using "M$" instead of Microsoft makes you look like a seething idiot.

  23. Its true by javilon · · Score: 5, Funny

    Even the KDE foundation voted for it !!!

    --


    When his defense asked, "Which computer has Jon Johansen trespassed upon?" the answer was: "His own."
  24. Re:Possible Tags? by teh+moges · · Score: 2, Funny

    omgponieslikeinoffice97 ?

  25. End of ISO? by Ilgaz · · Score: 4, Interesting

    See the story:
      An article up at Intellectual Property Watch claims they have obtained a document (PDF)

    See the article linked is "PDF"? Why? It is supported on everything down to Symbian S60 handsets and any open source software can support it. People can even race with vendors "reader" software making better ones. That is a real standard which won its place without dirty tricks.

    I bet usual suspects like Novell and their mighty Mono/Silverlight innovator Icaza will come up with a thing that supports it to some extent, advertise it and MS will use it as a proof.

    Last question: Did gnome people openly critised this decision? On their website?

    April 1 could be the end of ISO. Once you lose credibility, you don't get it back. It is not a April 1 joke either. You can even feel that one of the biggest IT scandals is waiting and this time it is not poor open source geeks anymore, it is IBM/Sun and GNU/BSD and various World governments especially those very rich ones who can even say "no" to EU. Don't forget the militaries either.

  26. Re:Use the standard by Idiot+with+a+gun · · Score: 3, Insightful

    Well, that'd work if it weren't for tech specs that include "Wraplineslikeword95." As soon as you can tell me what the heck that means, then I'll make you a converter.

    Then there's the whole issue that nobody has implemented the standard the ISO passed, not even Microsoft. So we have no way of telling if it's even possible from them, let alone anyone who doesn't have access to the 18 or so patents they have covering OOXML.

  27. Approval was not won... by QuietLagoon · · Score: 3, Informative
    Microsoft's OOXML won ISO standard status.

    Approval was not won, approval was purchased.

  28. Microsoft v IBM by Whiteox · · Score: 2, Insightful

    It's a sad time when MS can lobby an international standards group on a closed, propriety format.
    IBM, who have been shackled by MS with this vote and now the US government banning them from tendering, must be feeling the pinch.
    The only way to fight back in my opinion is to keep using odf and proactively supporting the ODF standard.
    Frankly, I don't mind if there are 2 document standards as well as PDF, as long as they are either fully interchangeable.

    --
    Don't be apathetic. Procrastinate!
  29. Re:good by MrKaos · · Score: 2, Funny

    Using "M$" instead of Microsoft makes you look like a seething idiot.
    Get over it dood, it's an accepted standard moniker when refering to Microsoft, and we have to accept standards even when we don't like them.
    --
    My ism, it's full of beliefs.
  30. Nothing has changed by mlwmohawk · · Score: 2, Interesting

    The ISO standard, besides showing how corrupting Microsoft's monopoly money is, changes nothing.

    We have the same situation today as we did yesterday.

    (1) A "standard" which is only a standard because a monopoly uses it.
    (2) A "standard" which is independently implemented by (n>1) vendors.

    So, as long as *we* the technologically literate stay "on message" like the P.R. spinmasters, we can use this in our favor.

    The "April fools document standard" AFDS for short, should be as well known as the "halloween documents." And when they ask why it is called the "april fools document standard," tell them.

  31. To: central@iso.org by Tolkien · · Score: 5, Interesting
    Subject: Re: Result of voting on ISO/IEC DIS 29500

    Hello, I'm writing to voice my opinion on the approval of Microsoft's OOXML format. It amazes me that ISO allowed such a monstrosity to pass. Everyone is aware of Microsoft's unending history of corruption. They bought out as many representatives as they could, to get this vote. Even Norway had corrupt people within its circles, though their committee chairman wasn't one of them (http://tech.slashdot.org/article.pl?sid=08/03/31/200201) thankfully. It appears ISO completely ignored his protests however because this change of vote, according to the PDF file that I found here (http://slashdot.org/article.pl?sid=08/04/01/2229207), lists Norway as Yes without comments, regardless of the fact that it was originally No with comments.


    Shame on you ISO. You have successfully contributed to setting back innovation both directly and indirectly until you come to your senses and approve the ODF file format, or another format which will have been developed by a corporation that has nothing monetary to gain by standardization. How long will that be, 5 years? Maybe 10 years?


    As this file (http://www.noooxml.org/local--files/arguments/TheCaseAgainstOOXML.pdf) should illustrate, everyone with two brain cells worth rubbing together knows that those thousands of pages contain many instances of Microsoft intentionally leaving out important information necessary to implement functional OOXML files which look and act identically in all software implementations. This should have been a massive red flag for ISO to choose to not even consider OOXML as a standard, much less APPROVE it.


    I urge you to reconsider and reverse the decision to formally approve OOXML. OOXML should never have even been considered in the first place.


    After this mistake, I will never fully trust ISO's standards again, considering how Microsoft successfully undermined its voting process, and ISO made no effort to verify or rectify the corruption. I suppose the next question could be "how much money did ISO gain by approving this format?" but I dare not ask. I'm sure I'd be sadly disappointed regardless of the answer given.


    Sincerely,
    Tolkien

    1. Re:To: central@iso.org by KDR_11k · · Score: 2, Informative

      ODF is already approved as an ISO standard.

      --
      Justice is the sheep getting arrested while an impartial judge declares the vote void.
  32. Creditibility vs. Virginity by buss_error · · Score: 2, Insightful

    Like virginity, credibility is only something one can perserve or loose.

    Unlike Voltare, who regarded virginity as a corectable perversion, credibility is the coin of the technical trade. Lose it, and watch ALL your works fade away.

    If the ISO doen't move to retract OOXML as a "standard", their other standards will only be seen as gross manipulation of the technical industry, and be discarded and ignored.

    Pity. Aside from how much work has gone into other ISO standards, I can't quite see the the people who have loaned their reputation sticking by a body so obviously bribed, coorsed, and schivvied into "accepting" such a "standard" to continue to support it.

    I'd think that within a very short time, those who regard their honor as something more than coin to be traded to the corporation most likely to bid high, twist arms to breaking, and cheat at every turn will start to distance themselves from the ISO because of this.

    It would be one thing if the offered "standard" met some acceptable technical goal. In my estimation, what we're seeing isn't a technical goal, but a lock in to assure undeserved profit.

    --
    Necessity is the plea for every infringement of human freedom. It is the argument of tyrants; it is the creed of slaves.
  33. Re:Stop crying, people. Start being HONEST. by AlgorithMan · · Score: 3, Informative

    In the first ISO vote the members had 50 pages of complaints
    around 1.5% of them have been adressed in the meantime

    what non-bribed ISO member would say now "wow, they adressed so many complaints that I can go from a 'no' vote to a 'yes' vote"?

    --
    The MAFIAA is a bunch of mindless jerks who will be the first up against the wall when the revolution comes
  34. Re:Why is this bad? by Otmenych · · Score: 4, Informative

    Ok, someone explain to me why a standard for office documents based on XML is bad.
    XML is not a point, OOXML is inconsistent, extremely complex, extremely verbose documented. It also may contain blob elements with an ARBITRARY content. For example, you can place WHOLE .doc document into .docx and it will be OOXML compliant despite fact that .doc is not a part of standard.
  35. Re:Agree - My Proposed Solution by cyclomedia · · Score: 2, Insightful

    Here's how I envisiage fighting this

    first set up a web site with a simplish name that's anonymously funded and transparently run, indeed I am an MCP at a Microsoft only shop, i'd be happy to run the site but my priorities lie with feeding my children.

    It needs to be factual and neutral. Never yelling, or preaching. It needs to be the (webstandards.org) acid test of the document suite / format world.

    It needs to show clearly where each of several major office suites stand in relation to compatibility to both formats, and yes, it needs to highlight OO.os flaws neutrally and just as prominently as any other suite's.

    It needs to link directly and clearly to plugins for each suite for each format (where available). It needs to explain each suites compatibility issues and explain workarounds for maximum platform compatibility.

    It needs to show, clearly licencing against said office suites and support costs.

    It needs to show patent issues, again, factually and clearly.

    All of the above should be targetted not at the IT crowd but at the Pointy Haired Bosses of the world.

    Then the task will fall to us lot, the OSS advocates, to make OO.o and ODF the clear, statistical winner in the above site.

    captcha: infinity

    --
    If you don't risk failure you don't risk success.
  36. Unfortunately, it is true. by bitserf · · Score: 2, Informative

    Read it and weep.

    http://www.iso.org/iso/pressrelease.htm?refid=Ref1123

    Pathetic, if you ask me.

  37. Re:Stop crying, people. Start being HONEST. by mudshark · · Score: 4, Insightful

    Hey, if you can repost that same crap drivel, back atcha homes:

    You obviously have never had to implement anything that needed to conform to a defined, published standard. If you had, you would never in a million years defend a ragged mess which can't even deal with Julian dates without referencing a broken proprietary binary (Excel 97). And you wouldn't defend OOXML, in raving terms including liberal usage of boldface, all caps and ad hominem attacks, if you understood the difference between a properly written standard and one cobbled together in panic that large institutional customers would abandon a proprietary format over concerns of long-term data accessibility, bit rot and lock-in.

    Enjoy your new spec.

    --
    In other news, astrophysicists have announced that they now know what all that dark matter is: it's stupidity.
  38. Re:Stop crying, people. Start being HONEST. by AlgorithMan · · Score: 3, Informative
    I remembered some numbers incorrectly:
    • The ISO members (the JTC1 committee) found 3522 defects in the OOXML standard
    • The Ecma grouped these complaints and proposed 1027 changes on about 2300 pages
    • Microsoft said they had adressed 662 of the proposals
    • At the isos ballot resolution meeting (BRM) 900 of the 1027 proposals were not checked (they didn't check if MS had implemented the changes)
    • Rob Weir used a random sampling technique to estimate how many proposals were actually implemented: about 1.5%
    http://www.computerworld.com/action/article.do?command=viewArticleBasic&articleId=9065903&intsrc=news_list
    http://www.pro-linux.de/news/2008/12520.html (german)
    http://politics.slashdot.org/article.pl?sid=07/12/04/0310208
    http://www.robweir.com/blog/2008/03/how-many-defects-remain-in-ooxml.html
    --
    The MAFIAA is a bunch of mindless jerks who will be the first up against the wall when the revolution comes
  39. Re:Stop crying, people. Start being HONEST. by makomk · · Score: 2, Insightful

    Of course, the Czech Republic comments covered only a tiny fraction of what was wrong with the standard, so the actual improvement was, relatively speaking, fairly negligible - even when you take all the comments submitted by all the countries, there's still far more things left unfixed than there are things that have been fixed. (There just wasn't enough time to find everything.) It looks like several of the partially-resolved issues are still likely to break interoperability, too. To be honest, saying that "OK, we can approve it now" based on this seems a bit iffy...

  40. Post approval analysis by Ice+Tiger · · Score: 2, Insightful

    Will be interesting to see who voted for what and what made them change if they did. Potentially there could be a lot of fallout for those involved as the facts come to light.

    Personally I have lost faith in ISO because it seems the worlds largest computer software manufacturer can just buy their own standards from this organisation.

    --
    "Because we are not employing at entry level, offshoring will kill our industry stone dead."
  41. You are lying. Msft can use ODF. by walterbyrd · · Score: 3, Informative

    >>And by real motives I mean "Anti-Microsoft people dont want Microsoft to obtain a public international standard on documents, so Office sinks (and Microsoft gets screwed) when governments start pushing restrictions on formats for their documents".

    Absolute 100% pure unadulterated crap. Msft is entirely capable, and welcome, to use ODF. In fact, I think plug-ins already exist.

    I am sick to death of this brazen lie being propagated on slashdot, and elsewhere. It is not true, and it makes no sense. You statement is based on the assumption that ODF locks msft out - and that assumption is simply not true.

    1. Re:You are lying. Msft can use ODF. by MightyMartian · · Score: 2, Interesting

      The plugin is a horrible monster.

      I hope the EU forces, under pains of billion dollar fines, Microsoft to put ODF support directly into future versions of Office, and continues to threaten them if they try to break it.

      --
      The world's burning. Moped Jesus spotted on I50. Details at 11.
  42. Nice way to astoturf by marcosdumay · · Score: 2, Interesting

    For example, the Czech Republic voted NO in September, but switched to YES. Why? Because nearly every one of their issues have been addressed now. http://xmlguru.cz/2008/01/ecma-response-to-czech-ooxml-comments Do you really expect the Czech Republic to continue to oppose OOXML when nearly all of its objections to the original spec have been fixed? Why would they do that? The problems were fixed, so they switched to YES, and this was the case with many countries (those without a political agenda).

    Were they fixed? Really? Like the other 98% of the comments, that were "fixed" even nobody reading the "fix" due to lack of time?

    Did you know that they had to vote NO if any one of their issues weren't fixed? "Nearly every one" doesn't cut it. Also, they could vote NO even if all of their issues were solved just because they discovered a new one, or because they think some other problem that wasn't fixed is important.

    Now, how did the Czech Republic know that their issues were fixed if nobody readed the final document before voting?