</TABLE>
Further details concerning the setting of attributes can be found
in the description of the
-<A HREF="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>
<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="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="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
</TABLE>
Further details concerning the setting of attributes can be found
in the description of the
-<A HREF="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>
<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="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="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