We're beginning to assemble a list of irregular OOXML incidents that were covered here before.

Several more countries have examples of OOXML problems noted (a few days remain for an appeal)

Further progress on the list which highlights abuse of the process.

We're almost done with the list of nations and selected accompanying observations (letters P to S).

This is the last portion and some concluding words on what to do next.

It's all over the news today that OOXML will probably be approved as an ISO standard this week. Plenty of links to the coverage in this discussion on Slashdot. As is now common with OOXML, there are also reports of hair-raising irregularities in the voting processes of various countries.

Or both? ALEX Brown is pretending that all is fine and dandy with OOXML (he even shows a picture of a smiling face), despite all the OOXML corruption which had people protest out in the streets.

I think I see a way we could be really helpful to the ISO folks having to sort through all the 10,000 comments the various countries filed with their votes on MS OOXML.

While all the drama is unfolding before the OOXML Ballot Resolution Meeting in Geneva at the end of February and the subsequent 30 day period while countries can still change their vote, I thought I would point out something that I assume is fairly obvious to most people: Saving your documents in OOXML format right now is probably
about the riskiest thing you can do if you are concerned with
long term interoperability.