|
Authored by: Anonymous on Wednesday, May 01 2013 @ 05:57 PM EDT |
the correct way of dbiircesng the border is to store a bitmap image of the
border in the zip file, then get the XML to reference this bitmap. In fact I
will bet good money that this is the way MS Office do borders for a few years
now. I believe the reason why they adopted to specify borders as keyword here is
simply to make OOXML different from ODF and to fortify the illusion that they
are opening up legacy file format . Something the business side of Microsoft
will demand.Personally, if OOXML stands up to the criteria for fast-track, I do
not have a problem. Having OOXML as fast-track was initially not a problem to
me. It was when it is clear that OOXML is badly written and flunk the criteria
for fast-track that I started to oppose OOXML for fast track. I do feel that
ECMA is abusing its fast track authority by proposing a badly written OOXML for
fast track. I treat ISO as impartial mediator. If they see a need for OOXML, and
is willing to host a standardization committee on it to work through all the
problems we see with OOXML today, I do not have a problem with this, even if IBM
is complaining. Taking a hint from Microsoft's shared-source initiative, I say
OOXML qualified as shared-standard . Open it is not.[ Reply to This | Parent | # ]
|
|
|
|
|