 | |
[DOCS] Documentation and explanatory diagrams
mailing.database.pgsql-docs mailing.database.pgsql-docs
 |
| | Thread Tools | Display Modes |
#101
 
| |||
| |||
|
Re: [DOCS] Documentation and explanatory diagrams -
06-13-2011
, 07:34 PM
|
Bruce Momjian <bruce (AT) momjian (DOT) us> writes: I think the big question is whether we can afford to allow multiple SVG editor file formats to be checked in, and hence support git diff churn as we switch SVG editors for commits. This doesn't seem likely to improve anytime soon so we should just decide and move forward. Perhaps we should allow any SVG file to be imported, but only allow modifications by a single SVG editor. How is that sensible? The first change to the file will result in exactly the mass of cosmetic diffs that we wish to avoid. |
a single diff change once the file is modified. If we don't do that
then all image additions have to be done by someone with the proper
editor.
Quote:
|
I think we probably have to specify the One True Graphics Editor, and maybe even specific version(s) of it, if we want to avoid unreadable diffs. The reason we have not managed to come to a consensus yet is that people would prefer not to do that, but it's becoming obvious that there just isn't any way around it. |
--
Bruce Momjian <bruce (AT) momjian (DOT) us> http://momjian.us
EnterpriseDB http://enterprisedb.com
+ It's impossible for everything to be true. +
--
Sent via pgsql-docs mailing list (pgsql-docs (AT) postgresql (DOT) org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-docs
#102
| |||
| |||
|
|
Tom Lane wrote: Bruce Momjian <bruce (AT) momjian (DOT) us> writes: Perhaps we should allow any SVG file to be imported, but only allow modifications by a single SVG editor. How is that sensible? The first change to the file will result in exactly the mass of cosmetic diffs that we wish to avoid. I suggested this so we could get images into the docs and then only have a single diff change once the file is modified. If we don't do that then all image additions have to be done by someone with the proper editor. |
committing. As long as said editor can read SVG output from a
reasonable range of other tools, this doesn't seem that onerous.
regards, tom lane
--
Sent via pgsql-docs mailing list (pgsql-docs (AT) postgresql (DOT) org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-docs
#103
| |||
| |||
|
|
Bruce Momjian <bruce (AT) momjian (DOT) us> writes: Tom Lane wrote: Bruce Momjian <bruce (AT) momjian (DOT) us> writes: Perhaps we should allow any SVG file to be imported, but only allow modifications by a single SVG editor. How is that sensible? *The first change to the file will result in exactly the mass of cosmetic diffs that we wish to avoid. I suggested this so we could get images into the docs and then only have a single diff change once the file is modified. *If we don't do that then all image additions have to be done by someone with the proper editor. 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. |
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
--
Sent via pgsql-docs mailing list (pgsql-docs (AT) postgresql (DOT) org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-docs
#104
| |||
| |||
|
|
On Mon, Jun 13, 2011 at 8:46 PM, Tom Lane <tgl (AT) sss (DOT) pgh.pa.us> wrote: Bruce Momjian <bruce (AT) momjian (DOT) us> writes: Tom Lane wrote: Bruce Momjian <bruce (AT) momjian (DOT) us> writes: Perhaps we should allow any SVG file to be imported, but only allow modifications by a single SVG editor. How is that sensible? ?The first change to the file will result in exactly the mass of cosmetic diffs that we wish to avoid. I suggested this so we could get images into the docs and then only have a single diff change once the file is modified. ?If we don't do that then all image additions have to be done by someone with the proper editor. 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. Bad news, Bruce: you're going to have to learn a new tool. :-) |
Do we have any agreement on which tool will be the definitive one?
--
Bruce Momjian <bruce (AT) momjian (DOT) us> http://momjian.us
EnterpriseDB http://enterprisedb.com
+ It's impossible for everything to be true. +
--
Sent via pgsql-docs mailing list (pgsql-docs (AT) postgresql (DOT) org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-docs
#105
| |||
| |||
|
|
Robert Haas wrote: On Mon, Jun 13, 2011 at 8:46 PM, Tom Lane <tgl (AT) sss (DOT) pgh.pa.us> 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. |
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.
Quote:
|
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? |
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. reedstrm (AT) rice (DOT) edu
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
--
Sent via pgsql-docs mailing list (pgsql-docs (AT) postgresql (DOT) org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-docs
#106
| |||
| |||
|
|
On 27 September 2010 15:29, Thom Brown <thombrown (AT) gmail (DOT) com> wrote: On 18 July 2010 11:58, Rafael Martinez <r.m.guerrero (AT) usit (DOT) uio.no> wrote: -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Thom Brown wrote: Okay, I just edited an existing dia file: pgclient_server.dia. *All I did was change the font size of the text "client application" at the top of the diagram, and changed the properties of a line so the arrowhead was no longer on the end. *I used dia 0.97.1 to edit the file. The result when saving is attached in the diff file. *That's a lot of file changes for what I did. Thom Indeed. The only explanation I can find to this is that I used dia.0.96.1 to generate the file and you have used 0.97.1 to edit it. Almost all changes are to the attributes: *<dia:rectangle val=.... *<dia  oint val=....I suspect that these changes have been done because 'something' have changed between the two main versions in the way they deal with these attributes  Has anyone yet come up with a reliable and sensible format we can use? Obviously nothing for this happened in time to make it for 9.1. So are diagrams still something we plan to have? |
documentation. Do we at least have an agreed-up approach?
--
Bruce Momjian <bruce (AT) momjian (DOT) us> http://momjian.us
EnterpriseDB http://enterprisedb.com
+ It's impossible for everything to be true. +
--
Sent via pgsql-docs mailing list (pgsql-docs (AT) postgresql (DOT) org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-docs
|
« Previous Thread
|
Next Thread »
| Thread Tools | |
| Display Modes | |
Linear Mode
| |
Powered by vBulletin Version 3.5.3
Copyright ©2000 - 2013, Jelsoft Enterprises Ltd.
Copyright ©2000 - 2013, Jelsoft Enterprises Ltd.