Remove all absolute URLs from the info docs

diff --git a/doc/info/attrs.html b/doc/info/attrs.html
index 46df99ac8d2c26bee07b84d30ba699f0eb8b32f1..fd6538b149f8ec8ab5f2d44925e4848193a27203 100644 (file)
--- a/doc/info/attrs.html
+++ b/doc/info/attrs.html
@@ -29,7 +29,7 @@ one would use
 </TABLE>
 Further details concerning the setting of attributes can be found
 in the description of the
-<A HREF="http://www.graphviz.org/doc/info/lang.html">DOT language.</A>
+<A HREF="lang.html">DOT language.</A>
 <P>
 At present, most device-independent units are either inches or
 <A NAME="points"></A>
@@ -39,10 +39,10 @@ which we take as 72 points per inch.
 <A NAME=h:undir_note><STRONG>Note:</STRONG></A> Some attributes, such as
 <A HREF=#d:dir>dir</A> or <A HREF=#d:arrowtail>arrowtail</A>, are
 ambiguous when used in
-<A HREF="http://www.graphviz.org/doc/info/lang.html">DOT</A>
+<A HREF="lang.html">DOT</A>
 with an undirected graph since the head and tail of an edge are meaningless.
 As a convention, the first time an undirected edge appears, the
-<A HREF="http://www.graphviz.org/doc/info/lang.html">DOT</A>
+<A HREF="lang.html">DOT</A>
 parser will assign the left node as the tail node and the right node as
 the head. For example, the edge <TT>A -- B</TT> will have tail <TT>A</TT>
 and head <TT>B</TT>. It is the user's responsibility to handle such
@@ -2004,6 +2004,19 @@ enclosed in the parentheses,  <TT>(...)+</TT> indicates 1 or more, and
 <DT><A NAME=k:colorList><STRONG>colorList</STRONG></A>
 <DD>A colon-separated list of color values: <I>C</I>(:<I>C</I>)*
    where each <I>C</I> is a <A HREF=#k:color>color</A> value.
+  <P>
+  Depending on the related attribute and graph object, two colors may specify a gradient fill.
+  The following table shows some variations of the <TT>yellow:blue</TT> color list depending on the
+  <A HREF=#a:style>style</A> and <A HREF=#a:gradientangle>gradientangle</A> attributes.
+    <TABLE border=1>
+      <TR><TH>Gradient angle<TH>Linear<TH>Radial</TR>
+      <TR><TD align=center>0<TD><IMG SRC="g_lin0.png"><TD><IMG SRC="g_rad0.png"></TR>
+      <TR><TD align=center>45<TD><IMG SRC="g_lin45.png"><TD><IMG SRC="g_rad45.png"></TR>
+      <TR><TD align=center>90<TD><IMG SRC="g_lin90.png"><TD><IMG SRC="g_rad90.png"></TR>
+      <TR><TD align=center>180<TD><IMG SRC="g_lin180.png"><TD><IMG SRC="g_rad180.png"></TR>
+      <TR><TD align=center>270<TD><IMG SRC="g_lin270.png"><TD><IMG SRC="g_rad270.png"></TR>
+      <TR><TD align=center>360<TD><IMG SRC="g_lin360.png"><TD><IMG SRC="g_rad360.png"></TR>
+    </TABLE>
 
 <DT><A NAME=k:dirType><STRONG>dirType</STRONG></A>
 <DD>For an edge <CODE>T -> H;</CODE>

diff --git a/doc/info/command.html b/doc/info/command.html
index 9725bc6de79913d20486707b5dae5a21b5b735a0..1c376225f9f332fd0c439413d6905addf305b7ea 100644 (file)
--- a/doc/info/command.html
+++ b/doc/info/command.html
@@ -23,14 +23,14 @@ If no input files are supplied, the program reads from <STRONG>stdin</STRONG>.
 <DT><A NAME=minusK><STRONG>-K</STRONG></A><I>layout</I>
 <DD>Specifies which default layout algorithm to use, overriding the default from the command name. For example, running
 <TT>dot -Kneato</TT> is equivalent to running <TT>neato</TT>.
-<DT><A NAME=dT><STRONG>-T</STRONG></A><I>format</I>[:<I>renderer</I>[:<I>formatter</I>]]       
-<DD>Set output language to one of the <A HREF=/content/output-formats>supported formats</A>.
-By default, <A HREF=/content/output-formats#ddot>attributed dot</A> is produced.
+<DT><A NAME=d:T><STRONG>-T</STRONG></A><I>format</I>[:<I>renderer</I>[:<I>formatter</I>]]       
+<DD>Set output language to one of the <A HREF=output.html>supported formats</A>.
+By default, <A HREF=output.html#d:dot>attributed dot</A> is produced.
 <P>
 Depending on how Graphviz was built, there may be multiple renderers for
 generating a particular output format, and multiple formatters for 
 creating the final output. For example, a typical installation
-can produce <A HREF="http://www.graphviz.org/content/output-formats#dpng">PNG</A>
+can produce <A HREF="output.html#d:png">PNG</A>
 output using either the Cairo or GD library. The desired rendering engine
 can be specified after a colon. If there are multiple formatting engines
 available, the desired one can be specified in a similar fashion after
@@ -55,16 +55,16 @@ beginning of output.
 whose content will be included in the preamble after the standard preamble.
 If <I>library</I> is the empty string <TT>""</TT>, the standard preamble
 is not emitted.
-<DT><A NAME=dn><STRONG>-n</STRONG>[<I>num</I>]</A>      
+<DT><A NAME=d:n><STRONG>-n</STRONG>[<I>num</I>]</A>      
 <DD>Sets no-op flag in <STRONG>neato</STRONG>. 
 If set, <STRONG>neato</STRONG> assumes nodes have already been 
-positioned and all nodes have a <A HREF=/content/attrs#dpos>pos</A>
+positioned and all nodes have a <A HREF=attrs.html#d:pos>pos</A>
 attribute giving
 the positions. It then performs an optional adjustment to remove node-node
 overlap, depending on the value of the 
-<A HREF=/content/attrs#doverlap>overlap</A> attribute, computes the edge 
+<A HREF=attrs.html#d:overlap>overlap</A> attribute, computes the edge 
 layouts, depending on the value of the 
-<A HREF=/content/attrs#dsplines>splines</A> attribute, and
+<A HREF=attrs.html#d:splines>splines</A> attribute, and
 emits the graph in the appropriate format. If <I>num</I> is supplied,
 the following actions occur:
 <DL>
@@ -73,10 +73,10 @@ the following actions occur:
 <DT><I>num</I> > 1
 <DD>Use node positions as specified, with no adjustment to
 remove node-node overlaps, and use any edge layouts already specified
-by the <A HREF=/content/attrs#dpos>pos</A> attribute. <STRONG>neato</STRONG>
+by the <A HREF=attrs.html#d:pos>pos</A> attribute. <STRONG>neato</STRONG>
 computes an edge layout for any edge that does not have a <B>pos</B> attribute.
 As usual, edge layout is guided by the 
-<A HREF=/content/attrs#dsplines>splines</A> attribute.
+<A HREF=attrs.html#d:splines>splines</A> attribute.
 </DL>
 <DT><STRONG>-o</STRONG><I>outfile</I>    
 <DD>Write output to file <I>outfile</I>. By default, output goes to
@@ -90,10 +90,10 @@ flags.
 the current executable.   e.g.  <STRONG>dot -P -Tps | lpr</STRONG>
 <DT><STRONG>-q</STRONG>
 <DD>Suppress warning messages.
-<DT><A NAME=ds><STRONG>-s</STRONG></A>[<I>scale</I>]
+<DT><A NAME=d:s><STRONG>-s</STRONG></A>[<I>scale</I>]
 <DD>Set input scale to <I>scale</I>. If this value is omitted,
 72.0 is used. This number is used to convert the point coordinate
-units used in the <A HREF=/content/attrs#dpos>pos</A> attribute 
+units used in the <A HREF=attrs.html#d:pos>pos</A> attribute 
 into inches, which is what is expected by neato and fdp. 
 Thus, feeding the output of a graph laid out by one program into
 neato or fdp almost always requires this flag.
@@ -106,10 +106,10 @@ This removes uninteresting graph structure and produces a less cluttered
 drawing.
 <DT><STRONG>-y</STRONG>             
 <DD>By default, the coordinate system used in generic output formats, 
-such as <A HREF=/content/output-formats#ddot>attributed dot</A>,
-<A HREF=/content/output-formats#dxdot>extended dot</A>,
-<A HREF=/content/output-formats#dplain>plain</A> and
-<A HREF=/content/output-formats#dplain-ext>plain-ext</A>,
+such as <A HREF=output.html#d:dot>attributed dot</A>,
+<A HREF=output.html#d:xdot>extended dot</A>,
+<A HREF=output.html#d:plain>plain</A> and
+<A HREF=output.html#d:plain-ext>plain-ext</A>,
 is the standard cartesian system with the origin in the lower left corner, 
 and with increasing y coordinates as points move from bottom to top.
 If the <CODE>-y</CODE> flag is used, the coordinate system is inverted,
@@ -137,21 +137,21 @@ output, the graph will have these attributes.
 <DT><STRONG>GDFONTPATH</STRONG>
 <DD>
 List of pathnames giving directories which a program should search for fonts.
-Overridden by <A HREF=#dDOTFONTPATH>DOTFONTPATH</A>.
+Overridden by <A HREF=#d:DOTFONTPATH>DOTFONTPATH</A>.
 <IT>Used only if Graphviz is not built with the <TT>fontconfig</TT> library</IT>
-<DT><A NAME=dDOTFONTPATH><STRONG>DOTFONTPATH</STRONG></A>
+<DT><A NAME=d:DOTFONTPATH><STRONG>DOTFONTPATH</STRONG></A>
 <DD>
 List of pathnames giving directories which a program should search for fonts.
-Overridden by <A HREF=/content/attrs#dfontpath><STRONG>fontpath</STRONG></A>.
+Overridden by <A HREF=attrs.html#d:fontpath><STRONG>fontpath</STRONG></A>.
 <IT>Used only if Graphviz is not built with the <TT>fontconfig</TT> library</IT>
-<DT><A NAME=dSERVER_NAME><STRONG>SERVER_NAME</STRONG></A>
+<DT><A NAME=d:SERVER_NAME><STRONG>SERVER_NAME</STRONG></A>
 <DD>
 If defined, this indicates that the software is running as a web application,
 which restricts access to image files. See 
-<A HREF=#dGV_FILE_PATH>GV_FILE_PATH</A>.
-<DT><A NAME=dGV_FILE_PATH><STRONG>GV_FILE_PATH</STRONG></A>
+<A HREF=#d:GV_FILE_PATH>GV_FILE_PATH</A>.
+<DT><A NAME=d:GV_FILE_PATH><STRONG>GV_FILE_PATH</STRONG></A>
 <DD>
-If <A HREF=#dSERVER_NAME>SERVER_NAME</A> is defined, image files are
+If <A HREF=#d:SERVER_NAME>SERVER_NAME</A> is defined, image files are
 restricted to exist in one of the directories specified by <TT>GV_FILE_PATH</TT>.
 This last is a list of directory pathnames, separated by semicolons in Windows or
 by colons otherwise.
@@ -159,13 +159,13 @@ Note that sometimes, when using one of the layout programs in a web
 script, it is not enough to use an export command but rather the
 variables should be set when the command is run, for example,<BR>
 <CODE>
-SERVER_NAME=xxx GV_FILE_PATH="images:etc/images:/usr/share/images" dot -Tpng -o x.png x.dot
+SERVER_NAME=xxx GV_FILE_PATH="images:etc/images:/usr/share/images" dot -Tpng -o x.png x.gv
 </CODE>
 <P>
 Note that the image files must really reside in one of the specified directories. If the
 image file is specified as an absolute or relative pathname, a warning is given and only
 the base name is used.
-<DT><A NAME=dGVBINDIR><STRONG>GVBINDIR</STRONG></A>
+<DT><A NAME=d:GVBINDIR><STRONG>GVBINDIR</STRONG></A>
 <DD>
 Indicates which directory contains the Graphviz config file and
 plug-in libraries. If it is defined, the value overrides any other

diff --git a/doc/infosrc/attrs.1 b/doc/infosrc/attrs.1
index b67bb00e3d46fbfa428e79c4a265826a8af23a40..6079e75d40b1bb34c36cbb1e1a623da093956f72 100644 (file)
--- a/doc/infosrc/attrs.1
+++ b/doc/infosrc/attrs.1
@@ -29,7 +29,7 @@ one would use
 </TABLE>
 Further details concerning the setting of attributes can be found
 in the description of the
-<A HREF="http://www.graphviz.org/doc/info/lang.html">DOT language.</A>
+<A HREF="lang.html">DOT language.</A>
 <P>
 At present, most device-independent units are either inches or
 <A NAME="points"></A>
@@ -39,10 +39,10 @@ which we take as 72 points per inch.
 <A NAME=h:undir_note><STRONG>Note:</STRONG></A> Some attributes, such as
 <A HREF=#d:dir>dir</A> or <A HREF=#d:arrowtail>arrowtail</A>, are
 ambiguous when used in
-<A HREF="http://www.graphviz.org/doc/info/lang.html">DOT</A>
+<A HREF="lang.html">DOT</A>
 with an undirected graph since the head and tail of an edge are meaningless.
 As a convention, the first time an undirected edge appears, the
-<A HREF="http://www.graphviz.org/doc/info/lang.html">DOT</A>
+<A HREF="lang.html">DOT</A>
 parser will assign the left node as the tail node and the right node as
 the head. For example, the edge <TT>A -- B</TT> will have tail <TT>A</TT>
 and head <TT>B</TT>. It is the user's responsibility to handle such

diff --git a/doc/infosrc/command.html b/doc/infosrc/command.html
index 11f99b618de26d2368ba04b8fe9cd45d0a87b7eb..1c376225f9f332fd0c439413d6905addf305b7ea 100644 (file)
--- a/doc/infosrc/command.html
+++ b/doc/infosrc/command.html
@@ -30,7 +30,7 @@ By default, <A HREF=output.html#d:dot>attributed dot</A> is produced.
 Depending on how Graphviz was built, there may be multiple renderers for
 generating a particular output format, and multiple formatters for 
 creating the final output. For example, a typical installation
-can produce <A HREF="http://www.graphviz.org/doc/info/output.html#d:png">PNG</A>
+can produce <A HREF="output.html#d:png">PNG</A>
 output using either the Cairo or GD library. The desired rendering engine
 can be specified after a colon. If there are multiple formatting engines
 available, the desired one can be specified in a similar fashion after