Sv: Sv: Emacs as a word processor (ways to convert Word/RTF proprietary files)

[arthur miller <arthur.miller@live.com>]

[-- Attachment #1: Type: text/plain, Size: 1779 bytes --]

I didn't had to work with office documents for few years, so I can't tell how it looks like now,
but what parts of text formatting does not work? They use to convert it pretty decently
before. As I remember it was usually if forms and scripts and graphics were involved that
it didn't work well, but simple text formatting worked well. I never wanted to pay for MS
Office, so I used at home open/libre office and was rarely founding a troublesome file.

I have no opinion on what should be done first at all. I was just reflecting on "unpleasant to
work with". ODT might be easier to work with sure. Problem with ooxml is that MS is not
really sticking to the specification and is doing things differently themselves, so Libre has to
emulate parts that are different then the standard MS specified themselves.
________________________________
Från: Stefan Monnier <monnier@iro.umontreal.ca>
Skickat: den 25 december 2020 22:08
Till: arthur miller <arthur.miller@live.com>
Kopia: Tomas Hlavaty <tom@logand.com>; emacs-devel@gnu.org <emacs-devel@gnu.org>
Ämne: Re: Sv: Emacs as a word processor (ways to convert Word/RTF proprietary files)

> LibreOffice does quite good job of translating docx stuff you wrote about.

Last I checked, LibreOffice still wasn't able to edit a "docx" file
without losing significant formatting information in real-life cases.

And I don't mean it as a criticism of LibreOffice.
The "docx" format is not nearly as "documented" as you think it is.

As for the original problem: I'm pretty sure it'd be hard enough to
solve the problem for ODT documents, so I'd focus on that first (and
leave the compatibility with formats that are actively designed to be
hard to support (like docx) to other tools).


        Stefan


[-- Attachment #2: Type: text/html, Size: 3989 bytes --]