linux-kernel - Re: [PATCH 0/9] Get rid of bitmap images

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20161121104444.28862d80@lwn.net>
Date:   Mon, 21 Nov 2016 10:44:44 -0700
From:   Jonathan Corbet <corbet@....net>
To:     Mauro Carvalho Chehab <mchehab@...pensource.com>
Cc:     Linux Doc Mailing List <linux-doc@...r.kernel.org>,
        Mauro Carvalho Chehab <mchehab@...radead.org>,
        Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
        ksummit-discuss@...ts.linuxfoundation.org,
        Sakari Ailus <sakari.ailus@...ux.intel.com>,
        Laurent Pinchart <laurent.pinchart@...asonboard.com>,
        Markus Heiser <markus.heiser@...marIT.de>,
        Mauro Carvalho Chehab <mchehab@...nel.org>
Subject: Re: [PATCH 0/9] Get rid of bitmap images

On Sun, 20 Nov 2016 14:08:31 -0200
Mauro Carvalho Chehab <mchehab@...pensource.com> wrote:

> The goal of this patch series is to get rid of PNG images, using either graphviz
> or SVG for images.
> 
> For old images generated with xfig, stored inside PDF, just convert them to SVG
> and cleanup the images using inkscape.
> 
> Other images need to be rewritten in SVG.
> 
> The pipeline image is actually a graphviz diagram. So, use dot to convert it
> to SVG.
> 
> For now, I'm keeping the image conversion rules inside the
> Documentation/media/Makefile. As we get other docs using images,
> the best would be to move those rules to Documentation/Makefile.sphinx,
> while we don't have a Sphinx extension or fixup that would handle them
> directly.

So this all seems good to me and makes sense to get in for 4.10.  Should I
apply these?

> NOTE: some images use more than 998 columns, causing troubles
> with some MTA and MUA that could refuse them, because of an IETF
> RFC 2821 violation:

Hard would it be to bash out a little tool that could break those long
lines?  It seems like the format should be able to support that?  I'm no
XML expert, but a quick experiment breaking the long lines in
fieldseq_bt.svg didn't create any problems; white space is white space.

Indeed, given the small number of images and the infrequency with which
they change, perhaps that could just be done by hand?

(In the process I learned that if you visit an SVG image in emacs, it
actually renders and displays the image!)

jon