ksummit.lists.linux.dev archive mirror
 help / color / mirror / Atom feed
From: Jonathan Corbet <corbet@lwn.net>
To: Mauro Carvalho Chehab <mchehab@s-opensource.com>
Cc: Markus Heiser <markus.heiser@darmarIT.de>,
	ksummit-discuss@lists.linuxfoundation.org,
	Linux Doc Mailing List <linux-doc@vger.kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Sakari Ailus <sakari.ailus@linux.intel.com>,
	Mauro Carvalho Chehab <mchehab@kernel.org>
Subject: Re: [Ksummit-discuss] [PATCH 0/9] Get rid of bitmap images
Date: Mon, 21 Nov 2016 10:44:44 -0700	[thread overview]
Message-ID: <20161121104444.28862d80@lwn.net> (raw)
In-Reply-To: <cover.1479656706.git.mchehab@s-opensource.com>

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

  parent reply	other threads:[~2016-11-21 17:44 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-11-20 16:08 Mauro Carvalho Chehab
2016-11-20 16:08 ` [Ksummit-discuss] [PATCH 1/9] [media] convert more media images to SVG Mauro Carvalho Chehab
2016-11-20 16:08 ` [Ksummit-discuss] [PATCH 2/9] [media] svg files: cleanup them Mauro Carvalho Chehab
2016-11-20 16:08 ` [Ksummit-discuss] [PATCH 3/9] [media] docs-rst: nv12mt zigzag images: replace by SVG images Mauro Carvalho Chehab
2016-11-20 16:08 ` [Ksummit-discuss] [PATCH 4/9] [media] docs-rst: convert pipeline to SVG format Mauro Carvalho Chehab
2016-11-20 16:08 ` [Ksummit-discuss] [PATCH 5/9] [media] docs-rst: replace the selection.png by a SVG image Mauro Carvalho Chehab
2016-11-20 16:08 ` [Ksummit-discuss] [PATCH 6/9] [media] docs-rst: replace bayer.png " Mauro Carvalho Chehab
2016-11-20 16:08 ` [Ksummit-discuss] [PATCH 7/9] docs-rst: media: build SVG from graphviz files Mauro Carvalho Chehab
2016-11-20 16:08 ` [Ksummit-discuss] [PATCH 8/9] doc-rst: media/Makefile: reorganize the rules Mauro Carvalho Chehab
2016-11-20 16:08 ` [Ksummit-discuss] [PATCH 9/9] docs-rst: fix media cleandocs target Mauro Carvalho Chehab
2016-11-21 17:44 ` Jonathan Corbet [this message]
2016-11-21 19:15   ` [Ksummit-discuss] [PATCH 0/9] Get rid of bitmap images Mauro Carvalho Chehab
2016-11-22 13:49     ` Jani Nikula
2016-11-22 15:15       ` Mauro Carvalho Chehab
2016-11-22 15:40         ` Jani Nikula
2016-11-22 16:38           ` Mauro Carvalho Chehab
2016-11-29  1:09 ` Jonathan Corbet
2016-11-30  9:29   ` Mauro Carvalho Chehab

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20161121104444.28862d80@lwn.net \
    --to=corbet@lwn.net \
    --cc=ksummit-discuss@lists.linuxfoundation.org \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=markus.heiser@darmarIT.de \
    --cc=mchehab@kernel.org \
    --cc=mchehab@s-opensource.com \
    --cc=sakari.ailus@linux.intel.com \
    /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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox