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

[Mauro Carvalho Chehab]

Em Mon, 21 Nov 2016 10:44:44 -0700
Jonathan Corbet <corbet@xxxxxxx> escreveu:

> On Sun, 20 Nov 2016 14:08:31 -0200
> Mauro Carvalho Chehab <mchehab@xxxxxxxxxxxxxxxx> 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?

If you are OK with them, please apply on your tree. IMHO, it is better
to keep those on your tree than on mine. It should not cause conflicts
with the stuff I have at the media tree.

> 
> > 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.

I'm not sure. The problem happens on strings like this one:

x="103.58983 109.09226 113.67899 118.26572 122.85246 127.43919 132.47964 134.77301 140.27545 144.86218 150.81833 155.40506 160.44553 166.86365 188.62184 194.12427 198.711 203.29774 207.88448 212.47121 217.51166 219.80502 225.30746 229.8942 235.85034 240.43707 245.9395 252.35764 257.3981 262.43854 268.85669 375.69293 381.19534 385.78207 390.3688 394.95554 399.54227 404.58273 406.8761 412.37854 416.96527 422.92142 427.50815 433.01059 439.42871 444.46918 449.50961 455.92776 1.551828 7.0542617 11.640993 16.227724 20.814463 25.401194 30.441652 32.735016 38.237442 42.824177 48.780331 53.367065 58.869492 65.287621 70.328079 75.368538 81.786659"

I've no idea if breaking lines inside strings on XML would cause
troubles for SVG handling, and, if all SVG libraries would do the
same thing.

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

I guess so. We can always get them via git pull requests, and at
least my e-mail servers are OK with long e-mails. I suspect we'll
have problems with ML servers, like vger, though.

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

That's interesting!

Thanks,
Mauro