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

My 4-pennyworth:
I have not used Microsoft for 20 years but the world does.  Almost no
academic publishers or conference organisers will accept .ODT etc.  So I
always have to test all my stuff out on malware!  And yes, I sometimes find
oddities in Microsoft documents which, I suspect are not safe (Chrome does
not like all these posts either- I have to retrieve some from spam).

My suggestion is that we try to build as large a community as we can,
whilst recognising that the majority will not join us.  It would help if we
could buy new PC's that were not already loaded with the Microxrap
operating system.  I went to at least 6 dealers here and could not persuade
any of them to sell me a blank system.  They all said that if I deleted W10
the warranty would be invalid.   The dirty tricks brigade are alive and

Over 20 years ago, my University could not afford Windose 2000 and were
ready to convert all their PC;s to Linux.  Then a helicopter landed,
unannounced and a gang of smarmy suited Americans decided to gatecrash the
ViceChancellors office.  (It is on video somewhere).  Magically, the Uni
then got a very good deal....   I believe Munich had similar issues.

On Mon, 13 Dec 2021 at 14:16, Italo Vignoli <> wrote:

Unfortunately, the situation is way more complex than it seems.

A few facts:

1. MS Office documents carry 80% of all malware worldwide

2. MS Office documents do not follow the OOXML pseudo-standard, as
approved by ISO

3. The OOXML pseudo-standard breaks several ISO standards, such as the
Gregorian calendar and the language codes

4. MS Office ODF implementation is poor, because the way MS Office
manages XML schemas is completely different from the XML standard, and
in some cases - such as comments - doesn't make it possible to support
the ODF standard

5. Microsoft C-Fonts, which have been emulated by Croscore fonts (my
blog post is mostly about Croscore fonts), have been deprecated for MS
Office 2021, and will be replaced by a new set of proprietary fonts
(which will break interoperability, again)

I would never affirm that Microsoft supports open standards, on the
contrary they develop the most sophisticated strategies to break open
standards (and they unfortunately succeed).

On 12/13/21 13:50, James Harking wrote:
Microsoft office is certainly not malware. It serves no purpose to spread
falsehoods. From previous messages in this thread Microsoft are doing
than most to support open standards with their participation in Oasis.

The interoperability issue for me is around Microsoft Office document
fidelity on non Microsoft platforms.

On Mon, 13 Dec 2021, 12:38 Ravi, <> wrote:

I think every time we receive a word document from someone, we should
make them aware about the interoperability issues and tell them
Microsoft Office is a nonfree software which is a malware.

If some people switch to LibreOffice, that would be a real change.
Whether people listen or not, I keep speaking about these issues and
some of them do switch to LibreOffice or free software in general.

Ravi Dwivedi
GPG Keys->

To unsubscribe e-mail to:
Posting guidelines + more:
List archive:
Privacy Policy:

Italo Vignoli -
mobile/signal +39.348.5653829
GPG Key ID - 0xAAB8D5C0
DB75 1534 3FD0 EA5F 56B5 FDA6 DE82 934C AAB8 D5C0

To unsubscribe e-mail to:
Posting guidelines + more:
List archive:
Privacy Policy:

To unsubscribe e-mail to:
Posting guidelines + more:
List archive:
Privacy Policy:


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.