Reveal code, old macros convert them to LO

[Dan Lewis]

On 7/7/19 4:35 PM, Wols Lists wrote:
> On 07/07/19 17:06, Tor Lillqvist wrote:
>>      For the reference: we have a bug report since 2011
>>      https://bugs.documentfoundation.org/show_bug.cgi?id=34002
>>      and the corresponding openoffice bug report from 2002 is linked in the
>>      ticket...
>>
>>
>> Which should be a good indication that the request is unreasonable.
>>
> I think you mean "impractical" :-(
>
> How is it unreasonable for support guys to want to be able to debug
> their lusers' documents?
>
> How is it unreasonable for people like me to want to use a modern word
> processor, but be able to use it in a manner that we are comfortable,
> rather than be forced into a "one size fits all" extremely uncomfortable
> fairy tale bed ...
>
> I was serious when I suggested that Uwe's best case for fixing his
> documents was to "save as plain text" and start again. Bit tricky if the
> document is full of graphics and other stuff ...
>
> Cheers,
> Wol

I now possess a copy of the offending .docx document and the PDF version 
of it. (It contains 1.6MB, so it will take some time.) Tomorrow, I will 
be determining what is necessary to fix it. Rather than guess as to what 
would be required, I will find out. I think this would be much more 
useful for others.  I will report back when I am finished.

Additional observation as in a personal opinion: this discussion has 
grown to a great length without really solving the problem. Such was the 
case for similar discussions before. (I seem to remember that one time 
it involved OOo prior to 3.0.)

One thing I do know: an .odt file is based on styles. The only codes 
that are used are styles. This is obvious when looking at the 
Content.xml file in the .odt zipped file. Word Perfect has a different 
set of codes which it uses. I do not see any correlation between the 
two. Without this, how can a do more than pretend to convert LO's 
styles  from WP's "reveal codes"?

Dan