emacs-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Emacs as a word processor (ways to convert Word/RTF proprietary file


From: Tomas Hlavaty
Subject: Re: Emacs as a word processor (ways to convert Word/RTF proprietary files)
Date: Fri, 25 Dec 2020 15:44:55 +0100

On Fri 25 Dec 2020 at 14:19, Arthur Miller <arthur.miller@live.com> wrote:
> The problem with documents in MS office is not text extraction; it is
> just xml nowadays anyway, the problem is countless VBA scripts that
> business and organisations run in Excell/Access/Word that just can't
> be translate to Libre. Libre has VB, but the underlaying objects are
> not there and lots of tools out there that people use can't be just
> automatically translated.
>
> I have worked in big organisation and did lots of automation for MS
> office and databases.

So what?  I do not understand what are you trying to say.

I tried to get the point across that it is not all or nothing problem.
There are use-cases which bring lots of value and are achievable with
reasonable effort.

>> Dealing with office formats is not a pleasant experience so I am
>> skeptical that volunteers will devote so much time to the use-cases
>> with the highest complexity.
>
> What is not so pleasant? New formats (marked with x) at the end are
> all xml, so it is just dealing with xml, sinilar to odt. I see nothing
> hard there and it is not that I defend Microsoft, I just don't see
> what you are talking about. That is part that alternatives you mention
> do.

Just because something is a zip file with some xml files inside does not
make it "not hard", "just dealing with xml".  It is complex to do
non-trivial stuff.  If you do not see what I am talking about, try to
implement something non-trivial (for example merge many docx documents
into one).  You'll understand why it is not a pleasant experience and
why I do not think anybody will do that in their free time.

>>               there could be.
>
> You are correct about one thing: there could be free alternative.
> All that will probably change in next 20 ~ 30 years, but we are not
> there yet.

It is not clear to me about which use-case are you talking in this
prediction.

1) There are use-cases, for which there are solutions now, as I already
   shown.

2) There are use-cases, for which solutions could be implemented with
   reasonable effort.

3) There are use-cases, which will very likely never have an
   alternative.

For 1) I did my best.

For 2) we'll see what I will do;-)

For 3) I wish you good luck!



reply via email to

[Prev in Thread] Current Thread [Next in Thread]