Date: prev next · Thread: first prev next last
2019 Archives by date, by thread · List index


On 06/07/19 10:27, Tor Lillqvist wrote:


    The issue is, what if you force to deal with docx and you run into
    problems? 


The data structure inside a .docx has very little relationship to the
internal data structures inside LO, so it would be extremely hard to
display "codes" from the .docx in the LibreOffice UI.

Like wise between Word and WordPerfect. But personally, I don't care
about that. The structure in Reveal Codes is a perfect match for a
WordPerfect document. I would like a Reveal-Codes-like window in Writer
that is a perfect match for Writer documents. It just makes working in
your word processor of choice *SO* much easier.

What you can do is unzip the .docx, edit the .xml files inside, update
them into the .docx? For some specific mechanical mass changes, or
trivial detail changes, that you can't do in LO, might work.

My biggest uses for reveal codes were (a) it was my editing window of
choice, (b) when somebody comes to you for help you *can* *see* *WHY*
their document wasn't doing what they expected, and (c) it gave me
*complete* control of whatever I was doing.

When the company I worked for moved to Word, it was forever doing all
sorts of weird things, and especially when trying to provide support to
other users, it was an ABSOLUTE NIGHTMARE because you had no way of
finding out WHY (and hence stopping) Word from doing all those stupid
things you didn't want.

Oh - and when you were helping another user "fix" their document, you
didn't need to know where in the menus / on the keypad all these
functions were that they were using that you didn't know where they'd
came from. You just double-clicked on the code, and it opened up the
configuration window. Or you just deleted the code and the formatting
went away. etc etc.

Cheers,
Wol

Context


Privacy Policy | Impressum (Legal Info) | Copyright information: Unless otherwise specified, all text and images on this website are licensed under the Creative Commons Attribution-Share Alike 3.0 License. This does not include the source code of LibreOffice, which is licensed under the Mozilla Public License (MPLv2). "LibreOffice" and "The Document Foundation" are registered trademarks of their corresponding registered owners or are in actual use as trademarks in one or more countries. Their respective logos and icons are also subject to international copyright laws. Use thereof is explained in our trademark policy.