public inbox for [email protected]  

help / color / mirror / Atom feed

From: Ross J. Reedstrom <[email protected]>
To: Bruce Momjian <[email protected]>
Cc: Robert Haas <[email protected]>
Cc: Tom Lane <[email protected]>
Cc: Thom Brown <[email protected]>
Cc: Greg Smith <[email protected]>
Cc: [email protected]
Subject: Re: Documentation and explanatory diagrams
Date: Tue, 14 Jun 2011 16:44:37 -0500
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>
References: <[email protected]>
	<[email protected]>

On Tue, Jun 14, 2011 at 08:59:41AM -0400, Bruce Momjian wrote:
> Robert Haas wrote:
> > On Mon, Jun 13, 2011 at 8:46 PM, Tom Lane <[email protected]> wrote:
> > >
> > > Or at least, somebody passes it through the "proper editor" before
> > > committing. ?As long as said editor can read SVG output from a
> > > reasonable range of other tools, this doesn't seem that onerous.

This scenario depends on the idea that the tool in question will serve
as an SVG normalizer. From what I can gather, none of the tools seem to
manage to do that. Or at least, do it in such a way as not to make
hamburger of the output SVG.

> > Bad news, Bruce: you're going to have to learn a new tool.  :-)
> 
> Yes, I am sensing that.  ;-)
> 
> Do we have any agreement on which tool will be the definitive one?

For my money, Inkscape seems to be the leader in this space (open source
generic SVG editor),  and is portable across all three major platforms:
Unixes, Windows, and MacOS. I think it's even in the BSD ports collections, 
Bruce. :-)

I would dearly love to have an SVG normalizer, but it seems no one has
done the deed.

Ross
-- 
Ross Reedstrom, Ph.D.                                 [email protected]
Systems Engineer & Admin, Research Scientist        phone: 713-348-6166
Connexions                  http://cnx.org            fax: 713-348-3665
Rice University MS-375, Houston, TX 77005
GPG Key fingerprint = F023 82C8 9B0E 2CC6 0D8E  F888 D3AE 810E 88F0 BEDE

view thread (114+ messages)  latest in thread

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: [email protected]
  Cc: [email protected], [email protected], [email protected], [email protected], [email protected], [email protected]
  Subject: Re: Documentation and explanatory diagrams
  In-Reply-To: <[email protected]>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox