From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from smtp1.linuxfoundation.org (smtp1.linux-foundation.org [172.17.192.35]) by mail.linuxfoundation.org (Postfix) with ESMTPS id 5C3E5483 for ; Sat, 19 Nov 2016 22:59:12 +0000 (UTC) Received: from twosheds.infradead.org (twosheds.infradead.org [90.155.92.209]) by smtp1.linuxfoundation.org (Postfix) with ESMTPS id 9AE64108 for ; Sat, 19 Nov 2016 22:59:11 +0000 (UTC) Message-ID: <1c179b5da49382970d7bf5171550d600.squirrel@twosheds.infradead.org> In-Reply-To: References: <20161107075524.49d83697@vento.lan> <11020459.EheIgy38UF@wuerfel> <20161116182633.74559ffd@vento.lan> <2923918.nyphv1Ma7d@wuerfel> <20161119101543.12b89563@lwn.net> <1479578112.4382.15.camel@infradead.org> Date: Sat, 19 Nov 2016 22:59:01 -0000 From: "David Woodhouse" To: "Linus Torvalds" MIME-Version: 1.0 Content-Type: text/plain;charset=utf-8 Content-Transfer-Encoding: 8bit Cc: ksummit-discuss@lists.linuxfoundation.org, "open list:DOCUMENTATION" , Linux Kernel Mailing List , Linux Media Mailing List Subject: Re: [Ksummit-discuss] Including images on Sphinx documents List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , > On Sat, Nov 19, 2016 at 9:55 AM, David Woodhouse > wrote: >> >> I know it's unfashionable these days, but TeX always used to be bloody >> good at that kind of thing. > > You must have used a different TeX than I did. > > TeX is a horrible example. The moment you needed to insert anything > that TeX didn't know about, you were screwed. > > I think my go-to for TeX was LaTeX, the "epsfig" thing, and then xfig > and eps files (using fig2dev). Christ, I get flashbacks just thinking > about it. You're right. You included Epson, which was generated from fig. Now I'm having flashbacks too, and I actually remember. > I thought one of the points of Sphinx was to not have to play those games. > > I think that graphviz and svg are the reasonable modern formats. Let's > try to avoid bitmaps in today's world, except perhaps as intermediate > generated things for what we can't avoid. Sure, SVG makes sense. It's a text-based format (albeit XML) and it *can* be edited with a text editor and reasonably kept in version control, at least if the common tools store it in a diff-friendly way (with some line breaks occasionally, and maybe no indenting). Do they? -- dwmw2