From: ng0 <ng0@infotropique.org>
To: Ricardo Wurmus <rekado@elephly.net>
Cc: guix-devel@gnu.org
Subject: Re: Building AbiWord without libwmf and removing libwmf from Guix
Date: Sat, 24 Jun 2017 08:02:08 +0000 [thread overview]
Message-ID: <20170624080208.ibacxwkzt2ndh7du@abyayala> (raw)
In-Reply-To: <87a85yf1fj.fsf@elephly.net>
Ricardo Wurmus transcribed 1.4K bytes:
>
> Mark H Weaver <mhw@netris.org> writes:
>
> > Leo Famulari <leo@famulari.name> writes:
> >
> >> The last update to libwmf was twelve years ago, in 2005. In the
> >> meantime, a large number of security issues have been discovered in this
> >> library. These bugs are fixed somewhat haphazardly by the distributions.
> >>
> >> While working on patching CVE-2016-9011 in libwmf, and backporting fixes
> >> for CVE-2016-{9317,10167,10168} in the ancient bundled libgd, I find
> >> myself wondering if we need this library at all. The patches from this
> >> 12 year span of 3rd party fixes begin to conflict with each other...
> >>
> >> Libwmf is only used as a "plugin" by AbiWord, and AbiWord can be
> >> configured to build without it.
> >
> > What functionality would be lost? I guess that AbiWord would lose the
> > ability to open some kinds of files, but it would be good to know
> > whether or not such files are still in common use.
>
> WMF is the native vector format for Microsoft Office applications,
> according to Wikipedia, so this would probably affect the rendering of
> some images in Word documents that are opened with Abiword.
>
> The format has continuously been developed, so it’s possible that libwmf
> (with a last release in 2005) isn’t even able to handle recent versions
> of WMF.
>
> I think it would be better to remove libwmf.
>
> --
> Ricardo
>
> GPG: BCA6 89B6 3655 3801 C3C6 2150 197A 5888 235F ACAC
> https://elephly.net
>
>
>
Libreoffice is able to do that aswell. It doesn't use libwmf, right?
--
ng0
OpenPG: A88C8ADD129828D7EAC02E52E22F9BBFEE348588
infotropique OS: https://www.infotropique.org
personal: https://ng-0.github.io https://krosos.org/~/ng0/
next prev parent reply other threads:[~2017-06-24 8:02 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-27 17:06 Building AbiWord without libwmf and removing libwmf from Guix Leo Famulari
2017-05-27 19:41 ` Mark H Weaver
2017-05-27 21:13 ` Ricardo Wurmus
2017-05-28 13:06 ` Hartmut Goebel
2017-05-28 18:44 ` Leo Famulari
2017-05-28 20:57 ` Ludovic Courtès
2017-06-23 22:30 ` Leo Famulari
2017-06-24 8:12 ` ng0
2017-06-24 8:02 ` ng0 [this message]
2017-06-24 16:21 ` Leo Famulari
2017-06-24 22:52 ` Mark H Weaver
2017-06-25 3:37 ` Leo Famulari
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20170624080208.ibacxwkzt2ndh7du@abyayala \
--to=ng0@infotropique.org \
--cc=guix-devel@gnu.org \
--cc=rekado@elephly.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).