On Fri, Jan 13, 2012 at 4:14 PM, Simon Phipps <[email protected]> wrote:
> Hi Dan,
>
> Your easy conclusion that LibreOffice is at fault is wrong. Please see
> https://bugs.freedesktop.org/show_bug.cgi?id=44498
> and
> https://issues.apache.org/ooo/show_bug.cgi?id=115789
>
> You'll see that this is indeed a reflection of a bug in MS Word that is 
> avoided in OOo because of a bug in OOo 3.3 ("Files from OpenOffice.org Writer 
> fail the validation at the OpenOffice validation site allegedly because the 
> manifest:manifest (root) tag in the META-INF/manifest.xml file lacks a 
> version attribute.")
>
> Given this is a bug in MS Word, it is best avoided both in LibreOffice and in 
> a future AOO release by using a format that MS Word handles correctly >such 
> as .DOC or ODF 1.1, unless Microsoft issues a patch.

If a program does not meet user expectations then it is a bug.  If you
want to be compatible with Microsoft Office then you need to play by
their rules.  The existence of standards like ODF and OOXML does not
change the basic fact that interoperability is hard work.  It requires
testing.  It does not happen overnight. It is not merely the result of
an incantation that begins with the sacred syllables "ISO".

In any case Seeing responses like this from LibreOffice makes be very
optimistic about the future of Apache OpenOffice.  Whatever the cause,
the fact that LibreOffice ships with this problem shows either a
woefully inadequate QA program, or total indifference to real world
requirements.  Even testing a single LibreOffice document in Office
2007 would have shown this bug.  Is that too much to expect?

And if you prefer written specifications to testing, there is always
Microsoft's Implementation Notes on Office 2007, where they spell out
in great details what  they do and do not support in ODF 1,1:

http://msdn.microsoft.com/en-us/library/ee908651%28v=office.12%29.aspx

LibreOffice could have prevented this bug by checking there as well.

-Rob

> S.
>
> On 13 Jan 2012, at 12:42, Dan Lewis wrote:
>
>>     From what you wrote, there is no bug in OOo. OOo clearly creates
>> documents that Word 2007 can read. The problem is with LibreOffice: it
>> is the one with the bug. OOo and LibreOffice are not the same.
>> LibreOffice is a fork of OOo meaning it has the same basic computer
>> code, but it also has some computer code that differs from OOo. The bug
>> seems to be located in the computer code that differs from OOo.
>>     If you want to use LibreOffice when sending documents to people
>> having Word 2007, you will need to wait until LibreOffice fixes the bug.
>> However, as you pointed out, you can use OOo 3.3.3 now. Why not continue
>> using OOo?
>>
>> --Dan
>>
>> On Fri, 2012-01-13 at 13:14 +0100, Jacek wrote:
>>> Word 2007 has no issue to open OOo created ODF 1.2 extended file. As I was 
>>> told that it's because of a bug of OOo, I fear that in the future the bug 
>>> will be fixed and the possibility of opening the OOo file when default 
>>> format is used will be lost (as it is the case with LibOffice, today).
>>>
>>> I would like to recommend to some Association members I work with, to use 
>>> Open Office, but they are not the ones who can change OOo settings or play 
>>> with output file format. For me, it is a mean to introduce in their 
>>> environment some "libre" software. But, it will work only and only, if they 
>>> have no issue when exchanging the files with external world.
>>> For the time being they use Word, but as they have to upgrade their 
>>> computers, I planned to recommend, at first LibOffice. As I found the 
>>> LibOffice issue with word, I tried OOo.
>>> I was happy that there were no issue with word to open OOo 3.3.3 created 
>>> file till the moment I was told that this is a bug in OOo and that this bug 
>>> will be fixed...
>>>
>>> Bregs
>>>
>>> Jacek
>>>
>>>
>>> -----Message d'origine-----
>>> De : Dan Lewis [mailto:[email protected]]
>>> Envoyé : vendredi 13 janvier 2012 12:56
>>> À : [email protected]
>>> Objet : Re: OOo, ODF 1.2 extended format and Word: is the possibility to 
>>> open OOo generated file by word ed as bug?
>>>
>>> On Fri, 2012-01-13 at 09:14 +0100, Jacek wrote:
>>>> Hello,
>>>>
>>>>
>>>>
>>>> I tried to open ODF 1.2 extended format file generated by LibOffice
>>>> using Word 2007 and this didn't work properly.
>>>>
>>>> I tried OOo 3.3.3 and I had no issue to open ODF 1.2 extended  file
>>>> generated by it using word.
>>>>
>>>> Someone told me that I was successful in opening OOo created file in
>>>> word because of a bug in OOo. And he added that this bug would be
>>>> fixed in the future.
>>>>
>>>> Is this statement correct? Am I able to open OOo created file because
>>>> of bug? If so, is this "bug", which allows Word 2007 to open OOo
>>>> generated file, going to be fix, i.e. is OOo going to generate the
>>>> files, which will be difficult to open with Word or other Microsoft Office 
>>>> modules?
>>>>
>>>>
>>>>
>>>> Is this the right forum to ask this question? If not, please let me
>>>> know where it should be asked.
>>>
>>>> Best regards
>>>
>>>> Jacek
>>>>
>>>
>>>
>>>     The problem may be with Word 2007. ODF 1.2 extended was created after 
>>> Word 2007 so Word 2007 does not know how to handle the changes made when 
>>> the open document format went from ODF 1.1 to ODF 1.2 extended. There has 
>>> been some comments on this mailing list earlier about MS Office not 
>>> handling ODF 1.2 extended.
>>>     Work around: open the document in OOo. Change the ODF setting.
>>> (Tools > Options > Load/Save > General ) Then use save As to save the 
>>> document as ODF 1.0/1.1.
>>>
>>> --Dan
>>>
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: [email protected]
>>> For additional commands, e-mail: [email protected]
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: [email protected]
>>> For additional commands, e-mail: [email protected]
>>>
>>
>>
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: [email protected]
>> For additional commands, e-mail: [email protected]
>>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [email protected]
> For additional commands, e-mail: [email protected]
>

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to