From: Mark Hansen Date: Sun, 28 Feb 2021 03:15:05 +0000 (+1100) Subject: Redirect more duplicate docs to graphviz site X-Git-Tag: 2.47.0~33^2 X-Git-Url: https://granicus.if.org/sourcecode?a=commitdiff_plain;h=33a0452c8129b73e402a739dbcd462e0ed4eff64;p=graphviz Redirect more duplicate docs to graphviz site I've deleted schema.html instead of redirecting because it's not intended to be shown as a top-level page on its own, but rather included in another page as a subtree. Towards https://gitlab.com/graphviz/graphviz.gitlab.io/-/issues/39 --- diff --git a/doc/info/arrows.html b/doc/info/arrows.html index 46cf57837..31ef15e4e 100644 --- a/doc/info/arrows.html +++ b/doc/info/arrows.html @@ -1,316 +1,2 @@ - - - - -Arrow Shapes - - - -

Arrow Shapes

-Arrow shapes can be specified and named using the following simple -grammar. -Terminals are shown in bold font and nonterminals in italics. -Literal characters are given in single quotes. -Square brackets [ and ] enclose optional items. -Vertical bars | separate alternatives. - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

arrowname	:	aname [ aname [ aname [ aname ] ] ]
aname	:	[ modifiers ] shape
modifiers	:	[ 'o' ] [ side ]
side	:	'l'
	\|	'r'
shape	:	box
	\|	crow
	\|	curve
	\|	icurve
	\|	diamond
	\|	dot
	\|	inv
	\|	none
	\|	normal
	\|	tee
	\|	vee

-The primitive shapes are: -

- - - - - - - - - - - -

"box"	-	"crow"	-	"curve"	-	"diamond"	-
"dot"	-	"icurve"	-	"inv"	-	"none"	-
"normal"	-	"tee"	-	"vee"	-

- -

-As for the modifiers: -

'l' -: Clip the shape, leaving only the part to the left of the edge. -
'r' -: Clip the shape, leaving only the part to the right of the edge. -
'o' -: Use an open (non-filled) version of the shape. -

-Left and right are defined as those directions determined by looking -from the edge towards the point where the arrow "touches" the node. -

-As an example, the arrow shape lteeoldiamond is parsed as -'l' 'tee' 'o' 'l' 'diamond' and corresponds to the shape -

- -Note that the first arrow shape specified occurs closest to the node. -Subsequent arrow shapes, if specified, occur further from the node. -Also, a shape of none uses space, so, for example, the arrowhead nonenormal -is not the same as normal. -

-Not all syntactically legal combinations of modifiers are meaningful -or semantically valid. -For example, none of the modifiers make any sense with none. -The following table indicates which modifiers are allowed with which shapes. -

- - - - - - -

Modifier	box -	crow -	curve -	diamond -	dot -	icurve -	inv -	none -	normal -	tee -	vee -
'l'/'r'	X	X	X	X		X		X	X	X
'o'	X			X	X	X		X

- -

-This yields 42 different arrow shapes. The optional second, third, fourth shapes -can independently be any of the 42, except the last cannot be none as -this would create a redundant shape. -Thus, there are 41 · 42³ + 41 · 42² + 41 · 42 + 42 = 3,111,696 different combinations. - -

-The following display contains the 42 combinations possible with a single -arrow shape. The node attached to the arrow is not drawn but would appear -on the right side of the edge. -

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

-	-	-	-	-	-
box -	lbox -	rbox -	obox -	olbox -	orbox -
-	-	-
crow -	lcrow -	rcrow -
-	-	-	-	-	-
diamond -	ldiamond -	rdiamond -	odiamond -	oldiamond -	ordiamond -
-	-
dot -	odot -
-	-	-	-	-	-
inv -	linv -	rinv -	oinv -	olinv -	orinv -
-
none -
-	-	-	-	-	-
normal -	lnormal -	rnormal -	onormal -	olnormal -	ornormal -
-	-	-
tee -	ltee -	rtee -
-	-	-
vee -	lvee -	rvee -
-	-	-	-	-	-
curve -	lcurve -	rcurve -	icurve -	licurve -	ricurve -

- - - + +Moved to https://graphviz.org/doc/info/arrows.html. Redirecting... diff --git a/doc/info/colors.html b/doc/info/colors.html index 07da5b7c2..ebbc70c49 100644 --- a/doc/info/colors.html +++ b/doc/info/colors.html @@ -1,3939 +1,2 @@ - - - - -Color Names - - - -

Color Names

-Color names are resolved in the context of a -color scheme. Graphviz currently -supports the X11 scheme, -the SVG scheme, and the Brewer schemes, -with X11 being the default. -

-Color names are case-insensitive. -

-The Brewer color schemes below are covered by this license. -

The X11 color scheme

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

aliceblue	antiquewhite	antiquewhite1	antiquewhite2	antiquewhite3
antiquewhite4	aquamarine	aquamarine1	aquamarine2	aquamarine3
aquamarine4	azure	azure1	azure2	azure3
azure4	beige	bisque	bisque1	bisque2
bisque3	bisque4	black	blanchedalmond	blue
blue1	blue2	blue3	blue4	blueviolet
brown	brown1	brown2	brown3	brown4
burlywood	burlywood1	burlywood2	burlywood3	burlywood4
cadetblue	cadetblue1	cadetblue2	cadetblue3	cadetblue4
chartreuse	chartreuse1	chartreuse2	chartreuse3	chartreuse4
chocolate	chocolate1	chocolate2	chocolate3	chocolate4
coral	coral1	coral2	coral3	coral4
cornflowerblue	cornsilk	cornsilk1	cornsilk2	cornsilk3
cornsilk4	crimson	cyan	cyan1	cyan2
cyan3	cyan4	darkgoldenrod	darkgoldenrod1	darkgoldenrod2
darkgoldenrod3	darkgoldenrod4	darkgreen	darkkhaki	darkolivegreen
darkolivegreen1	darkolivegreen2	darkolivegreen3	darkolivegreen4	darkorange
darkorange1	darkorange2	darkorange3	darkorange4	darkorchid
darkorchid1	darkorchid2	darkorchid3	darkorchid4	darksalmon
darkseagreen	darkseagreen1	darkseagreen2	darkseagreen3	darkseagreen4
darkslateblue	darkslategray	darkslategray1	darkslategray2	darkslategray3
darkslategray4	darkslategrey	darkturquoise	darkviolet	deeppink
deeppink1	deeppink2	deeppink3	deeppink4	deepskyblue
deepskyblue1	deepskyblue2	deepskyblue3	deepskyblue4	dimgray
dimgrey	dodgerblue	dodgerblue1	dodgerblue2	dodgerblue3
dodgerblue4	firebrick	firebrick1	firebrick2	firebrick3
firebrick4	floralwhite	forestgreen	gainsboro	ghostwhite
gold	gold1	gold2	gold3	gold4
goldenrod	goldenrod1	goldenrod2	goldenrod3	goldenrod4
gray	gray0	gray1	gray10	gray100
gray11	gray12	gray13	gray14	gray15
gray16	gray17	gray18	gray19	gray2
gray20	gray21	gray22	gray23	gray24
gray25	gray26	gray27	gray28	gray29
gray3	gray30	gray31	gray32	gray33
gray34	gray35	gray36	gray37	gray38
gray39	gray4	gray40	gray41	gray42
gray43	gray44	gray45	gray46	gray47
gray48	gray49	gray5	gray50	gray51
gray52	gray53	gray54	gray55	gray56
gray57	gray58	gray59	gray6	gray60
gray61	gray62	gray63	gray64	gray65
gray66	gray67	gray68	gray69	gray7
gray70	gray71	gray72	gray73	gray74
gray75	gray76	gray77	gray78	gray79
gray8	gray80	gray81	gray82	gray83
gray84	gray85	gray86	gray87	gray88
gray89	gray9	gray90	gray91	gray92
gray93	gray94	gray95	gray96	gray97
gray98	gray99	green	green1	green2
green3	green4	greenyellow	grey	grey0
grey1	grey10	grey100	grey11	grey12
grey13	grey14	grey15	grey16	grey17
grey18	grey19	grey2	grey20	grey21
grey22	grey23	grey24	grey25	grey26
grey27	grey28	grey29	grey3	grey30
grey31	grey32	grey33	grey34	grey35
grey36	grey37	grey38	grey39	grey4
grey40	grey41	grey42	grey43	grey44
grey45	grey46	grey47	grey48	grey49
grey5	grey50	grey51	grey52	grey53
grey54	grey55	grey56	grey57	grey58
grey59	grey6	grey60	grey61	grey62
grey63	grey64	grey65	grey66	grey67
grey68	grey69	grey7	grey70	grey71
grey72	grey73	grey74	grey75	grey76
grey77	grey78	grey79	grey8	grey80
grey81	grey82	grey83	grey84	grey85
grey86	grey87	grey88	grey89	grey9
grey90	grey91	grey92	grey93	grey94
grey95	grey96	grey97	grey98	grey99
honeydew	honeydew1	honeydew2	honeydew3	honeydew4
hotpink	hotpink1	hotpink2	hotpink3	hotpink4
indianred	indianred1	indianred2	indianred3	indianred4
indigo	invis	ivory	ivory1	ivory2
ivory3	ivory4	khaki	khaki1	khaki2
khaki3	khaki4	lavender	lavenderblush	lavenderblush1
lavenderblush2	lavenderblush3	lavenderblush4	lawngreen	lemonchiffon
lemonchiffon1	lemonchiffon2	lemonchiffon3	lemonchiffon4	lightblue
lightblue1	lightblue2	lightblue3	lightblue4	lightcoral
lightcyan	lightcyan1	lightcyan2	lightcyan3	lightcyan4
lightgoldenrod	lightgoldenrod1	lightgoldenrod2	lightgoldenrod3	lightgoldenrod4
lightgoldenrodyellow	lightgray	lightgrey	lightpink	lightpink1
lightpink2	lightpink3	lightpink4	lightsalmon	lightsalmon1
lightsalmon2	lightsalmon3	lightsalmon4	lightseagreen	lightskyblue
lightskyblue1	lightskyblue2	lightskyblue3	lightskyblue4	lightslateblue
lightslategray	lightslategrey	lightsteelblue	lightsteelblue1	lightsteelblue2
lightsteelblue3	lightsteelblue4	lightyellow	lightyellow1	lightyellow2
lightyellow3	lightyellow4	limegreen	linen	magenta
magenta1	magenta2	magenta3	magenta4	maroon
maroon1	maroon2	maroon3	maroon4	mediumaquamarine
mediumblue	mediumorchid	mediumorchid1	mediumorchid2	mediumorchid3
mediumorchid4	mediumpurple	mediumpurple1	mediumpurple2	mediumpurple3
mediumpurple4	mediumseagreen	mediumslateblue	mediumspringgreen	mediumturquoise
mediumvioletred	midnightblue	mintcream	mistyrose	mistyrose1
mistyrose2	mistyrose3	mistyrose4	moccasin	navajowhite
navajowhite1	navajowhite2	navajowhite3	navajowhite4	navy
navyblue	none	oldlace	olivedrab	olivedrab1
olivedrab2	olivedrab3	olivedrab4	orange	orange1
orange2	orange3	orange4	orangered	orangered1
orangered2	orangered3	orangered4	orchid	orchid1
orchid2	orchid3	orchid4	palegoldenrod	palegreen
palegreen1	palegreen2	palegreen3	palegreen4	paleturquoise
paleturquoise1	paleturquoise2	paleturquoise3	paleturquoise4	palevioletred
palevioletred1	palevioletred2	palevioletred3	palevioletred4	papayawhip
peachpuff	peachpuff1	peachpuff2	peachpuff3	peachpuff4
peru	pink	pink1	pink2	pink3
pink4	plum	plum1	plum2	plum3
plum4	powderblue	purple	purple1	purple2
purple3	purple4	red	red1	red2
red3	red4	rosybrown	rosybrown1	rosybrown2
rosybrown3	rosybrown4	royalblue	royalblue1	royalblue2
royalblue3	royalblue4	saddlebrown	salmon	salmon1
salmon2	salmon3	salmon4	sandybrown	seagreen
seagreen1	seagreen2	seagreen3	seagreen4	seashell
seashell1	seashell2	seashell3	seashell4	sienna
sienna1	sienna2	sienna3	sienna4	skyblue
skyblue1	skyblue2	skyblue3	skyblue4	slateblue
slateblue1	slateblue2	slateblue3	slateblue4	slategray
slategray1	slategray2	slategray3	slategray4	slategrey
snow	snow1	snow2	snow3	snow4
springgreen	springgreen1	springgreen2	springgreen3	springgreen4
steelblue	steelblue1	steelblue2	steelblue3	steelblue4
tan	tan1	tan2	tan3	tan4
thistle	thistle1	thistle2	thistle3	thistle4
tomato	tomato1	tomato2	tomato3	tomato4
transparent	turquoise	turquoise1	turquoise2	turquoise3
turquoise4	violet	violetred	violetred1	violetred2
violetred3	violetred4	wheat	wheat1	wheat2
wheat3	wheat4	white	whitesmoke	yellow
yellow1	yellow2	yellow3	yellow4	yellowgreen

The SVG color scheme

aliceblue	antiquewhite	aqua	aquamarine	azure
beige	bisque	black	blanchedalmond	blue
blueviolet	brown	burlywood	cadetblue	chartreuse
chocolate	coral	cornflowerblue	cornsilk	crimson
cyan	darkblue	darkcyan	darkgoldenrod	darkgray
darkgreen	darkgrey	darkkhaki	darkmagenta	darkolivegreen
darkorange	darkorchid	darkred	darksalmon	darkseagreen
darkslateblue	darkslategray	darkslategrey	darkturquoise	darkviolet
deeppink	deepskyblue	dimgray	dimgrey	dodgerblue
firebrick	floralwhite	forestgreen	fuchsia	gainsboro
ghostwhite	gold	goldenrod	gray	grey
green	greenyellow	honeydew	hotpink	indianred
indigo	ivory	khaki	lavender	lavenderblush
lawngreen	lemonchiffon	lightblue	lightcoral	lightcyan
lightgoldenrodyellow	lightgray	lightgreen	lightgrey	lightpink
lightsalmon	lightseagreen	lightskyblue	lightslategray	lightslategrey
lightsteelblue	lightyellow	lime	limegreen	linen
magenta	maroon	mediumaquamarine	mediumblue	mediumorchid
mediumpurple	mediumseagreen	mediumslateblue	mediumspringgreen	mediumturquoise
mediumvioletred	midnightblue	mintcream	mistyrose	moccasin
navajowhite	navy	oldlace	olive	olivedrab
orange	orangered	orchid	palegoldenrod	palegreen
paleturquoise	palevioletred	papayawhip	peachpuff	peru
pink	plum	powderblue	purple	red
rosybrown	royalblue	saddlebrown	salmon	sandybrown
seagreen	seashell	sienna	silver	skyblue
slateblue	slategray	slategrey	snow	springgreen
steelblue	tan	teal	thistle	tomato
turquoise	violet	wheat	white	whitesmoke
yellow	yellowgreen

Brewer color schemes

-accent3 color scheme
- - - - - -

-accent4 color scheme
- - - - - - -

-accent5 color scheme
- - - - - - - -

-accent6 color scheme
- - - - - - - - -

-accent7 color scheme
- - - - - - - - - -

-accent8 color scheme
- - - - - - - - - - -

-blues3 color scheme
- - - - - -

-blues4 color scheme
- - - - - - -

-blues5 color scheme
- - - - - - - -

-blues6 color scheme
- - - - - - - - -

-blues7 color scheme
- - - - - - - - - -

-blues8 color scheme
- - - - - - - - - - -

-blues9 color scheme
- - - - - - - - - - - -

-brbg10 color scheme
- - - - - - - - - - - - -

-brbg11 color scheme
- - - - - - - - - - - - - -

-brbg3 color scheme
- - - - - -

-brbg4 color scheme
- - - - - - -

-brbg5 color scheme
- - - - - - - -

-brbg6 color scheme
- - - - - - - - -

-brbg7 color scheme
- - - - - - - - - -

-brbg8 color scheme
- - - - - - - - - - -

-brbg9 color scheme
- - - - - - - - - - - -

-bugn3 color scheme
- - - - - -

-bugn4 color scheme
- - - - - - -

-bugn5 color scheme
- - - - - - - -

-bugn6 color scheme
- - - - - - - - -

-bugn7 color scheme
- - - - - - - - - -

-bugn8 color scheme
- - - - - - - - - - -

-bugn9 color scheme
- - - - - - - - - - - -

-bupu3 color scheme
- - - - - -

-bupu4 color scheme
- - - - - - -

-bupu5 color scheme
- - - - - - - -

-bupu6 color scheme
- - - - - - - - -

-bupu7 color scheme
- - - - - - - - - -

-bupu8 color scheme
- - - - - - - - - - -

-bupu9 color scheme
- - - - - - - - - - - -

-dark23 color scheme
- - - - - -

-dark24 color scheme
- - - - - - -

-dark25 color scheme
- - - - - - - -

-dark26 color scheme
- - - - - - - - -

-dark27 color scheme
- - - - - - - - - -

-dark28 color scheme
- - - - - - - - - - -

-gnbu3 color scheme
- - - - - -

-gnbu4 color scheme
- - - - - - -

-gnbu5 color scheme
- - - - - - - -

-gnbu6 color scheme
- - - - - - - - -

-gnbu7 color scheme
- - - - - - - - - -

-gnbu8 color scheme
- - - - - - - - - - -

-gnbu9 color scheme
- - - - - - - - - - - -

-greens3 color scheme
- - - - - -

-greens4 color scheme
- - - - - - -

-greens5 color scheme
- - - - - - - -

-greens6 color scheme
- - - - - - - - -

-greens7 color scheme
- - - - - - - - - -

-greens8 color scheme
- - - - - - - - - - -

-greens9 color scheme
- - - - - - - - - - - -

-greys3 color scheme
- - - - - -

-greys4 color scheme
- - - - - - -

-greys5 color scheme
- - - - - - - -

-greys6 color scheme
- - - - - - - - -

-greys7 color scheme
- - - - - - - - - -

-greys8 color scheme
- - - - - - - - - - -

-greys9 color scheme
- - - - - - - - - - - -

-oranges3 color scheme
- - - - - -

-oranges4 color scheme
- - - - - - -

-oranges5 color scheme
- - - - - - - -

-oranges6 color scheme
- - - - - - - - -

-oranges7 color scheme
- - - - - - - - - -

-oranges8 color scheme
- - - - - - - - - - -

-oranges9 color scheme
- - - - - - - - - - - -

-orrd3 color scheme
- - - - - -

-orrd4 color scheme
- - - - - - -

-orrd5 color scheme
- - - - - - - -

-orrd6 color scheme
- - - - - - - - -

-orrd7 color scheme
- - - - - - - - - -

-orrd8 color scheme
- - - - - - - - - - -

-orrd9 color scheme
- - - - - - - - - - - -

-paired10 color scheme
- - - - - - - - - - - - -

-paired11 color scheme
- - - - - - - - - - - - - -

-paired12 color scheme
- - - - - - - - - - - - - - -

-paired3 color scheme
- - - - - -

-paired4 color scheme
- - - - - - -

-paired5 color scheme
- - - - - - - -

-paired6 color scheme
- - - - - - - - -

-paired7 color scheme
- - - - - - - - - -

-paired8 color scheme
- - - - - - - - - - -

-paired9 color scheme
- - - - - - - - - - - -

-pastel13 color scheme
- - - - - -

-pastel14 color scheme
- - - - - - -

-pastel15 color scheme
- - - - - - - -

-pastel16 color scheme
- - - - - - - - -

-pastel17 color scheme
- - - - - - - - - -

-pastel18 color scheme
- - - - - - - - - - -

-pastel19 color scheme
- - - - - - - - - - - -

-pastel23 color scheme
- - - - - -

-pastel24 color scheme
- - - - - - -

-pastel25 color scheme
- - - - - - - -

-pastel26 color scheme
- - - - - - - - -

-pastel27 color scheme
- - - - - - - - - -

-pastel28 color scheme
- - - - - - - - - - -

-piyg10 color scheme
- - - - - - - - - - - - -

-piyg11 color scheme
- - - - - - - - - - - - - -

-piyg3 color scheme
- - - - - -

-piyg4 color scheme
- - - - - - -

-piyg5 color scheme
- - - - - - - -

-piyg6 color scheme
- - - - - - - - -

-piyg7 color scheme
- - - - - - - - - -

-piyg8 color scheme
- - - - - - - - - - -

-piyg9 color scheme
- - - - - - - - - - - -

-prgn10 color scheme
- - - - - - - - - - - - -

-prgn11 color scheme
- - - - - - - - - - - - - -

-prgn3 color scheme
- - - - - -

-prgn4 color scheme
- - - - - - -

-prgn5 color scheme
- - - - - - - -

-prgn6 color scheme
- - - - - - - - -

-prgn7 color scheme
- - - - - - - - - -

-prgn8 color scheme
- - - - - - - - - - -

-prgn9 color scheme
- - - - - - - - - - - -

-pubu3 color scheme
- - - - - -

-pubu4 color scheme
- - - - - - -

-pubu5 color scheme
- - - - - - - -

-pubu6 color scheme
- - - - - - - - -

-pubu7 color scheme
- - - - - - - - - -

-pubu8 color scheme
- - - - - - - - - - -

-pubu9 color scheme
- - - - - - - - - - - -

-pubugn3 color scheme
- - - - - -

-pubugn4 color scheme
- - - - - - -

-pubugn5 color scheme
- - - - - - - -

-pubugn6 color scheme
- - - - - - - - -

-pubugn7 color scheme
- - - - - - - - - -

-pubugn8 color scheme
- - - - - - - - - - -

-pubugn9 color scheme
- - - - - - - - - - - -

-puor10 color scheme
- - - - - - - - - - - - -

-puor11 color scheme
- - - - - - - - - - - - - -

-puor3 color scheme
- - - - - -

-puor4 color scheme
- - - - - - -

-puor5 color scheme
- - - - - - - -

-puor6 color scheme
- - - - - - - - -

-puor7 color scheme
- - - - - - - - - -

-puor8 color scheme
- - - - - - - - - - -

-puor9 color scheme
- - - - - - - - - - - -

-purd3 color scheme
- - - - - -

-purd4 color scheme
- - - - - - -

-purd5 color scheme
- - - - - - - -

-purd6 color scheme
- - - - - - - - -

-purd7 color scheme
- - - - - - - - - -

-purd8 color scheme
- - - - - - - - - - -

-purd9 color scheme
- - - - - - - - - - - -

-purples3 color scheme
- - - - - -

-purples4 color scheme
- - - - - - -

-purples5 color scheme
- - - - - - - -

-purples6 color scheme
- - - - - - - - -

-purples7 color scheme
- - - - - - - - - -

-purples8 color scheme
- - - - - - - - - - -

-purples9 color scheme
- - - - - - - - - - - -

-rdbu10 color scheme
- - - - - - - - - - - - -

-rdbu11 color scheme
- - - - - - - - - - - - - -

-rdbu3 color scheme
- - - - - -

-rdbu4 color scheme
- - - - - - -

-rdbu5 color scheme
- - - - - - - -

-rdbu6 color scheme
- - - - - - - - -

-rdbu7 color scheme
- - - - - - - - - -

-rdbu8 color scheme
- - - - - - - - - - -

-rdbu9 color scheme
- - - - - - - - - - - -

-rdgy10 color scheme
- - - - - - - - - - - - -

-rdgy11 color scheme
- - - - - - - - - - - - - -

-rdgy3 color scheme
- - - - - -

-rdgy4 color scheme
- - - - - - -

-rdgy5 color scheme
- - - - - - - -

-rdgy6 color scheme
- - - - - - - - -

-rdgy7 color scheme
- - - - - - - - - -

-rdgy8 color scheme
- - - - - - - - - - -

-rdgy9 color scheme
- - - - - - - - - - - -

-rdpu3 color scheme
- - - - - -

-rdpu4 color scheme
- - - - - - -

-rdpu5 color scheme
- - - - - - - -

-rdpu6 color scheme
- - - - - - - - -

-rdpu7 color scheme
- - - - - - - - - -

-rdpu8 color scheme
- - - - - - - - - - -

-rdpu9 color scheme
- - - - - - - - - - - -

-rdylbu10 color scheme
- - - - - - - - - - - - -

-rdylbu11 color scheme
- - - - - - - - - - - - - -

-rdylbu3 color scheme
- - - - - -

-rdylbu4 color scheme
- - - - - - -

-rdylbu5 color scheme
- - - - - - - -

-rdylbu6 color scheme
- - - - - - - - -

-rdylbu7 color scheme
- - - - - - - - - -

-rdylbu8 color scheme
- - - - - - - - - - -

-rdylbu9 color scheme
- - - - - - - - - - - -

-rdylgn10 color scheme
- - - - - - - - - - - - -

-rdylgn11 color scheme
- - - - - - - - - - - - - -

-rdylgn3 color scheme
- - - - - -

-rdylgn4 color scheme
- - - - - - -

-rdylgn5 color scheme
- - - - - - - -

-rdylgn6 color scheme
- - - - - - - - -

-rdylgn7 color scheme
- - - - - - - - - -

-rdylgn8 color scheme
- - - - - - - - - - -

-rdylgn9 color scheme
- - - - - - - - - - - -

-reds3 color scheme
- - - - - -

-reds4 color scheme
- - - - - - -

-reds5 color scheme
- - - - - - - -

-reds6 color scheme
- - - - - - - - -

-reds7 color scheme
- - - - - - - - - -

-reds8 color scheme
- - - - - - - - - - -

-reds9 color scheme
- - - - - - - - - - - -

-set13 color scheme
- - - - - -

-set14 color scheme
- - - - - - -

-set15 color scheme
- - - - - - - -

-set16 color scheme
- - - - - - - - -

-set17 color scheme
- - - - - - - - - -

-set18 color scheme
- - - - - - - - - - -

-set19 color scheme
- - - - - - - - - - - -

-set23 color scheme
- - - - - -

-set24 color scheme
- - - - - - -

-set25 color scheme
- - - - - - - -

-set26 color scheme
- - - - - - - - -

-set27 color scheme
- - - - - - - - - -

-set28 color scheme
- - - - - - - - - - -

-set310 color scheme
- - - - - - - - - - - - -

-set311 color scheme
- - - - - - - - - - - - - -

-set312 color scheme
- - - - - - - - - - - - - - -

-set33 color scheme
- - - - - -

-set34 color scheme
- - - - - - -

-set35 color scheme
- - - - - - - -

-set36 color scheme
- - - - - - - - -

-set37 color scheme
- - - - - - - - - -

-set38 color scheme
- - - - - - - - - - -

-set39 color scheme
- - - - - - - - - - - -

-spectral10 color scheme
- - - - - - - - - - - - -

-spectral11 color scheme
- - - - - - - - - - - - - -

-spectral3 color scheme
- - - - - -

-spectral4 color scheme
- - - - - - -

-spectral5 color scheme
- - - - - - - -

-spectral6 color scheme
- - - - - - - - -

-spectral7 color scheme
- - - - - - - - - -

-spectral8 color scheme
- - - - - - - - - - -

-spectral9 color scheme
- - - - - - - - - - - -

-ylgn3 color scheme
- - - - - -

-ylgn4 color scheme
- - - - - - -

-ylgn5 color scheme
- - - - - - - -

-ylgn6 color scheme
- - - - - - - - -

-ylgn7 color scheme
- - - - - - - - - -

-ylgn8 color scheme
- - - - - - - - - - -

-ylgn9 color scheme
- - - - - - - - - - - -

-ylgnbu3 color scheme
- - - - - -

-ylgnbu4 color scheme
- - - - - - -

-ylgnbu5 color scheme
- - - - - - - -

-ylgnbu6 color scheme
- - - - - - - - -

-ylgnbu7 color scheme
- - - - - - - - - -

-ylgnbu8 color scheme
- - - - - - - - - - -

-ylgnbu9 color scheme
- - - - - - - - - - - -

-ylorbr3 color scheme
- - - - - -

-ylorbr4 color scheme
- - - - - - -

-ylorbr5 color scheme
- - - - - - - -

-ylorbr6 color scheme
- - - - - - - - -

-ylorbr7 color scheme
- - - - - - - - - -

-ylorbr8 color scheme
- - - - - - - - - - -

-ylorbr9 color scheme
- - - - - - - - - - - -

-ylorrd3 color scheme
- - - - - -

-ylorrd4 color scheme
- - - - - - -

-ylorrd5 color scheme
- - - - - - - -

-ylorrd6 color scheme
- - - - - - - - -

-ylorrd7 color scheme
- - - - - - - - - -

-ylorrd8 color scheme
- - - - - - - - - - -

-ylorrd9 color scheme
- - - - - - - - - - - -

-
-Apache-Style Software License for ColorBrewer software and ColorBrewer -Color Schemes, Version 1.1 -

-Redistribution and use in source and binary forms, with or without -modification, are permitted provided that the following conditions are met: -

Redistributions as source code must retain the above copyright notice, -this list of conditions and the following disclaimer. -
The end-user documentation included with the redistribution, if any, -must include the following acknowledgment: -
-This product includes color specifications and designs developed -by Cynthia Brewer (http://colorbrewer.org/). -
-Alternately, this acknowledgment may appear in the software itself, if and -wherever such third-party acknowledgments normally appear. -
The name "ColorBrewer" must not be used to endorse or promote products -derived from this software without prior written permission. For written -permission, please contact Cynthia Brewer at cbrewer@psu.edu. -
Products derived from this software may not be called "ColorBrewer", nor -may "ColorBrewer" appear in their name, without prior written permission -of Cynthia Brewer. -

-THIS SOFTWARE IS PROVIDED "AS IS" AND ANY EXPRESSED OR IMPLIED WARRANTIES, -INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND -FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL CYNTHIA -BREWER, MARK HARROWER, OR THE PENNSYLVANIA STATE UNIVERSITY BE LIABLE FOR -ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL -DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR -SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER -CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, -OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE -OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. - - + +Moved to https://graphviz.org/doc/info/colors.html. Redirecting... diff --git a/doc/info/command.html b/doc/info/command.html index 7a5d613d5..2dbb6b815 100644 --- a/doc/info/command.html +++ b/doc/info/command.html @@ -1,177 +1,2 @@ - - - -Command-line Usage - - - -

Command-line Invocation

-All Graphviz programs have a similar invocation:
-

cmd [ flags ] [ input files ]
-

-If no input files are supplied, the program reads from stdin. -

Flags

-Gname[=value] -

Set a graph attribute, with default value = true. -

-Nname[=value] -

Set a default node attribute, with default value = true. -

-Ename[=value] -

Set a default edge attribute, with default value = true. -

-Klayout -

Specifies which default layout algorithm to use, overriding the default from the command name. For example, running -dot -Kneato is equivalent to running neato. -

-Tformat[:renderer[:formatter]] -

Set output language to one of the supported formats. -By default, attributed dot 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 PNG -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 -the rendering engine. Thus, -Tpng:cairo specifies PNG -output produced by Cairo (using the Cairo's default formatter), and --Tpng:cairo:gd specifies PNG -output produced by Cairo formatted using the GD library. -

-If no renderer is specified, or a renderer but no formatter, the default one -is invoked. The flag -Tformat: produces a list of all -of the renderers available for the specified format, the first one -listed with a prefix matching format being the default. -Using the -v flag, described below, will print which format, -renderer, and formatter are actually used. -

-V -

Emit version information and exit. -

-llibrary -

User-supplied, device-dependent library text. Multiple flags may -be given. These strings are passed to the code generator at the -beginning of output. -

For PostScript output, they are treated as file names -whose content will be included in the preamble after the standard preamble. -If library is the empty string "", the standard preamble -is not emitted. -

-n[num] -

Sets no-op flag in neato. -If set, neato assumes nodes have already been -positioned and all nodes have a pos -attribute giving -the positions. It then performs an optional adjustment to remove node-node -overlap, depending on the value of the -overlap attribute, computes the edge -layouts, depending on the value of the -splines attribute, and -emits the graph in the appropriate format. If num is supplied, -the following actions occur: -

num = 1 -: Equivalent to -n. -
num > 1 -: Use node positions as specified, with no adjustment to -remove node-node overlaps, and use any edge layouts already specified -by the pos attribute. neato -computes an edge layout for any edge that does not have a pos attribute. -As usual, edge layout is guided by the -splines attribute. -

-ooutfile -

Write output to file outfile. By default, output goes to -stdout. -

-O -

Automatically generate output file names based on the input -file name and the various output formats specified by the -T -flags. -

-P -

Automatically generate a graph that shows the plugin configuration of -the current executable. e.g. dot -P -Tps | lpr -

-q -

Suppress warning messages. -

-s[scale] -

Set input scale to scale. If this value is omitted, -72.0 is used. This number is used to convert the point coordinate -units used in the pos 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. -Ignored if the -n flag is used. -

-v -

Verbose mode -

-x -

In neato, on input, prune isolated nodes and peninsulas. -This removes uninteresting graph structure and produces a less cluttered -drawing. -

-y -

By default, the coordinate system used in generic output formats, -such as attributed dot, -extended dot, -plain and -plain-ext, -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 -y flag is used, the coordinate system is inverted, -so that increasing values of y correspond to movement from top to bottom. -

-? -

Print usage information, then exit. -

-If multiple -T flags are given, drawings of the graph -are emitted in each of the specified formats. Multiple -o -flags can be used to specify the output file for each format. If there -are more formats than files, the remaining formats are written to -stdout. -

-Note that the -G, --N and --E flags override any initial attribute declarations -in the input graph, -i.e., those attribute statements appearing before any node, edge or -subgraph definitions. -In addition, these flags cause the related attributes to be permanently -attached to the graph. Thus, if attributed dot is used for -output, the graph will have these attributes. -

Environment Variables

GDFONTPATH -: -List of pathnames giving directories which a program should search for fonts. -Overridden by DOTFONTPATH. -Used only if Graphviz is not built with the fontconfig library -
DOTFONTPATH -: -List of pathnames giving directories which a program should search for fonts. -Overridden by fontpath. -Used only if Graphviz is not built with the fontconfig library -
SERVER_NAME -: -If defined, this indicates that the software is running as a web application, -which restricts access to image files. See -GV_FILE_PATH. -
GV_FILE_PATH -: -If SERVER_NAME is defined, image files are -restricted to exist in one of the directories specified by GV_FILE_PATH. -This last is a list of directory pathnames, separated by semicolons in Windows or -by colons otherwise. -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,
--SERVER_NAME=xxx GV_FILE_PATH="images:etc/images:/usr/share/images" dot -Tpng -o x.png x.gv - -
-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. -
GVBINDIR -: -Indicates which directory contains the Graphviz config file and -plug-in libraries. If it is defined, the value overrides any other -mechanism for finding this directory. If Graphviz is properly installed, -it should not be needed, though it can be useful for relocation on -platforms not running Linux or Windows. -

- - + +Moved to https://graphviz.org/doc/info/command.html. Redirecting... diff --git a/doc/info/index.html b/doc/info/index.html index 338c23004..a6720d27d 100644 --- a/doc/info/index.html +++ b/doc/info/index.html @@ -1,17 +1,2 @@ - - - -GraphViz Reference - - - -

GraphViz Reference

-The DOT Language
-Command-line Usage
-Output Formats
-Graph Attributes
-Node Shapes
-Colors
- - + +Moved to https://graphviz.org/doc/info/index.html. Redirecting... diff --git a/doc/info/lang.html b/doc/info/lang.html index 518705575..b2fd73f11 100644 --- a/doc/info/lang.html +++ b/doc/info/lang.html @@ -1,296 +1,2 @@ - - - - -The DOT Language - - - -

The DOT Language

-The following is an abstract grammar defining the DOT language. -Terminals are shown in bold font and nonterminals in italics. -Literal characters are given in single quotes. -Parentheses ( and ) indicate grouping when needed. -Square brackets [ and ] enclose optional items. -Vertical bars | separate alternatives. - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

graph	:	[ strict ] (graph \| digraph) [ ID ] '{' stmt_list '}'
stmt_list	:	[ stmt [ ';' ] stmt_list ]
stmt	:	node_stmt
	\|	edge_stmt
	\|	attr_stmt
	\|	ID '=' ID
	\|	subgraph
attr_stmt	:	(graph \| node \| edge) attr_list
attr_list	:	'[' [ a_list ] ']' [ attr_list ]
a_list	:	ID '=' ID [ (';' \| ',') ] [ a_list ]
edge_stmt	:	(node_id \| subgraph) edgeRHS [ attr_list ]
edgeRHS	:	edgeop (node_id \| subgraph) [ edgeRHS ]
node_stmt	:	node_id [ attr_list ]
node_id	:	ID [ port ]
port	:	':' ID [ ':' compass_pt ]
	\|	':' compass_pt
subgraph	:	[ subgraph [ ID ] ] '{' stmt_list '}'
compass_pt	:	(n \| ne \| e \| se \| s \| sw \| w \| nw \| c \| _)

-The keywords node, edge, graph, digraph, -subgraph, and strict are case-independent. -Note also that the allowed compass point values are not keywords, so -these strings can be used elsewhere as ordinary identifiers and, conversely, -the parser will actually accept any identifier. -

-An ID is one of the following: -

Any string of alphabetic ([a-zA-Z\200-\377]) characters, underscores ('_') or -digits ([0-9]), not beginning with a digit; -

a numeral [-]^?(.[0-9]⁺ | [0-9]⁺(.[0-9]^*)^? ); -

any double-quoted string ("...") possibly containing escaped -quotes (\")¹; -

an HTML string (<...>). -

-An ID is just a string; the lack of quote characters in the first two -forms is just for simplicity. There is no semantic difference between -abc_2 and "abc_2", or between 2.34 and -"2.34". Obviously, to use a keyword as an ID, it must be quoted. -Note that, in HTML strings, angle -brackets must occur in matched pairs, and newlines and other formatting whitespace -characters are allowed. -In addition, the content must be legal XML, so that the special XML -escape sequences for ", &, <, and > may be necessary -in order to embed these characters in attribute values or raw text. -As an ID, an HTML string can be any legal XML string. However, if used -as a label attribute, it is interpreted specially and must follow the syntax -for HTML-like labels. -

-Both quoted strings and HTML strings are scanned as a unit, so -any embedded comments will be treated as part of the strings. -

-An edgeop is -> in directed graphs and -- in -undirected graphs. -

-The language supports C++-style comments: /* */ and //. -In addition, a line beginning with a '#' character is considered a line -output from a C preprocessor (e.g., # 34 to indicate line 34 ) and discarded. -

-Semicolons and commas aid readability but are not required. -Also, any amount of whitespace may be inserted between terminals. -

-As another aid for readability, dot allows double-quoted strings to -span multiple physical lines using the standard C convention of a -backslash immediately preceding a newline character². In addition, -double-quoted strings can be concatenated using a '+' operator. -As HTML strings can contain newline characters, which are used solely for -formatting, the language does not allow escaped newlines or -concatenation operators to be used within them. -

Subgraphs and Clusters

-Subgraphs play three roles in Graphviz. First, a subgraph can be used to -represent graph structure, indicating that certain nodes and edges should -be grouped together. This is the usual role for subgraphs -and typically specifies semantic information about the graph components. -It can also provide a convenient shorthand for edges. An edge statement allows -a subgraph on both the left and right sides of the edge operator. -When this occurs, an edge is created from every node on the left to every node -on the right. For example, the specification -

-  A -> {B C}
-

-is equivalent to -

-  A -> B
-  A -> C
-

-In the second role, a subgraph can provide a context for setting attributes. -For example, a subgraph could specify that blue -is the default color for all nodes defined in it. -In the context of -graph drawing, a more interesting example is: -

-subgraph { 
-rank = same; A; B; C; 
-} 
-

-This (anonymous) subgraph specifies that the nodes A, B and C -should all be placed on the same rank if drawn using dot. -

-The third role for subgraphs directly involves how the graph -will be laid out by certain layout engines. If the name of -the subgraph begins with cluster, Graphviz notes the subgraph as -a special cluster subgraph. If supported, the layout engine will -do the layout so that the nodes belonging to the cluster are drawn together, -with the entire drawing of the cluster contained within a bounding rectangle. -Note that, for good and bad, cluster subgraphs are not part of the -DOT language, but solely a syntactic convention adhered to by -certain of the layout engines. -

Lexical and Semantic Notes

-A graph must be specified as either a digraph or a graph. -Semantically, this indicates whether or not there is a natural direction from -one of the edge's nodes to the other. -Lexically, a digraph must specify an edge using the edge operator -> -while a undirected graph must use --. -Operationally, the distinction is used to define different default rendering -attributes. For example, edges in a digraph will be drawn, by default, with -an arrowhead pointing to the head node. For ordinary graphs, edges are drawn -without any arrowheads by default. -

-A graph may also be described as strict. -This forbids the creation of multi-edges, i.e., there can be at most one -edge with a given tail node and head node in the directed case. For undirected -graphs, there can be at most one -edge connected to the same two nodes. Subsequent edge statements using -the same two nodes will identify the edge with the previously defined one -and apply any attributes given in the edge statement. -For example, the graph -

-strict graph { 
-  a -- b
-  a -- b
-  b -- a [color=blue]
-} 
-

-will have a single edge connecting nodes a and b, -whose color is blue. -

-If a default attribute is -defined using a node, edge, or graph statement, -or by an attribute assignment not attached to a node or edge, any object of the -appropriate type defined afterwards will inherit this attribute value. -This holds until the default attribute is set to a new value, from which -point the new value is used. Objects defined before a default attribute -is set will have an empty string value attached to the attribute once -the default attribute definition is made. -

-Note, in particular, that a subgraph receives the attribute settings of -its parent graph at the time of its definition. This can be useful; for -example, one can assign a font to the root graph and all subgraphs will -also use the font. For some attributes, however, this property is -undesirable. If one attaches a label to the root graph, it is probably -not the desired effect to have the label used by all subgraphs. Rather -than listing the graph attribute at the top of the graph, and the -resetting the attribute as needed in the subgraphs, one can simply defer -the attribute definition in the graph until the appropriate subgraphs -have been defined. -

-If an edge belongs to a cluster, its endpoints belong to that cluster. -Thus, where you put an edge can effect a layout, as clusters are sometimes -laid out recursively. -

-There are certain restrictions on subgraphs and clusters. First, at -present, the names of a graph and it subgraphs share the same namespace. -Thus, each subgraph must have a unique name. Second, although nodes -can belong to any number of subgraphs, it is assumed clusters form -a strict hierarchy when viewed as subsets of nodes and edges. -

Character encodings

-The DOT language assumes at least the ascii character set. -Quoted strings, both ordinary and HTML-like, may contain non-ascii characters. -In most cases, these strings are uninterpreted: they simply serve as -unique identifiers or values passed through untouched. Labels, however, -are meant to be displayed, which requires that the software be able to -compute the size of the text and determine the appropriate glyphs. -For this, it needs to know what character encoding is used. -

-By default, DOT assumes the UTF-8 character encoding. It also accepts -the Latin1 (ISO-8859-1) character set, assuming the input graph uses -the charset attribute to -specify this. For graphs using other -character sets, there are usually programs, such as iconv, which -will translate from one character set to another. -

-Another way to avoid non-ascii characters in labels is to use HTML entities -for special characters. During label evaluation, these entities are -translated into the underlying character. This - -table shows the supported entities, with their Unicode value, a typical -glyph, and the HTML entity name. Thus, to include a lower-case Greek beta -into a string, one can use the ascii sequence β. -In general, one should only use entities that are allowed in the output -character set, and for which there is a glyph in the font. -

In quoted strings in DOT, the only escaped character is double-quote -("). That is, in quoted strings, the dyad \" is converted to "; all other -characters are left unchanged. In particular, \\ remains \\. Layout -engines may apply additional escape sequences. -
Previous to 2.30, the language allowed escaped newlines to be used anywhere outside -of HTML strings. The new lex-based scanner makes this difficult to implement. Given the -perceived lack of usefulness of this generality, we have restricted this feature to -double-quoted strings, where it can actually be helpful. -

- - + +Moved to https://graphviz.org/doc/info/lang.html. Redirecting... diff --git a/doc/info/output.html b/doc/info/output.html index 47b46fd3a..2a1d98046 100644 --- a/doc/info/output.html +++ b/doc/info/output.html @@ -1,708 +1,2 @@ - - - - -Output Formats - - - - - -

Output Formats

-The output format is specified with the -Tlang -flag on the command line, where lang -is one of the parameters listed below. -

-The formats actually available in a given Graphviz system depend on -how the system was built and the presence of additional libraries. -To see what formats dot supports, run dot -T?. -See the description of the -T -flag for additional information. -

-Note that the internal coordinate system has the origin -in the lower left corner. -Thus, positions in the -canon, -dot, -xdot, -plain, and -plain-ext -formats need to be interpreted in this manner. -

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Command-line
parameter Format
bmp - Windows Bitmap Format
canon -
dot -
gv -
xdot -
xdot1.2 -
xdot1.4 - DOT
cgimage - CGImage bitmap format
cmap - Client-side imagemap (deprecated)
eps - Encapsulated PostScript
exr - OpenEXR
fig - FIG
gd -
gd2 - GD/GD2 formats
gif - GIF
gtk - GTK canvas
ico - Icon Image File Format
imap -
cmapx - Server-side and client-side imagemaps
imap_np -
cmapx_np - Server-side and client-side imagemaps
ismap - Server-side imagemap (deprecated)
jp2 - JPEG 2000
jpg -
jpeg -
jpe - JPEG
json -
json0 -
dot_json -
xdot_json - Dot graph represented in JSON format
pct -
pict - PICT
pdf - Portable Document Format (PDF)
pic - Kernighan's PIC graphics language
plain -
plain-ext - Simple text format
png - Portable Network Graphics format
pov - POV-Ray markup language (prototype)
ps - PostScript
ps2 - PostScript for PDF
psd - PSD
sgi - SGI
svg -
svgz - Scalable Vector Graphics
tga - Truevision TGA
tif -
tiff - TIFF (Tag Image File Format)
tk - TK graphics
vml -
vmlz - Vector Markup Language (VML)
vrml - VRML
wbmp - Wireless BitMap format
webp - Image format for the Web
xlib -
x11 - Xlib canvas
-

Format Descriptions

bmp -

Outputs images in the Windows BMP format. - -

canon -,

dot -,

gv -,

xdot -,

xdot1.2 -,

xdot1.4 -

These formats produce output in the -dot language. -Using canon produces a prettyprinted version of the input, -with no layout performed. -

-The dot option corresponds to attributed dot output, -and is the default output format. -It reproduces the input, along with layout information for the graph. -In particular, a bb attribute is -attached to the graph, specifying the bounding box of the drawing. -If the graph has a label, its position is specified by the -lp attribute. -

-Each node gets pos, -width and -height attributes. If the node is a record, -the record rectangles are given in the -rects attribute. -If the node is a polygon and the -vertices attribute is defined, this -attribute contains the vertices of the node. -

-Every edge is -assigned a pos attribute, -and if the edge has a label, the label position -is given in lp. -

-The xdot format extends the -dot format by providing much more detailed information about -how graph components are drawn. It relies on additional attributes -for nodes, edges and graphs. -

-The format is fluid; comments and -suggestions for better representations are welcome. -To allow for changes in the format, Graphviz attaches the attribute -xdotversion to the graph. -If the xdotversion attribute is set in the input graph, the renderer -will only output features supported by that version. Note that the formats xdot1.2 -and xdot1.4 are equivalent to setting xdotversion=1.2 and xdotversion=1.4, -respectively. -

-Additional drawing attributes can appear on nodes, edges, clusters and -on the graph itself. There are six new attributes: - -
_draw_ General drawing without labels -
_ldraw_ Label drawing -
_hdraw_ Head arrowhead Edge only -
_tdraw_ Tail arrowhead Edge only -
_hldraw_ Head label Edge only -
_tldraw_ Tail label Edge only -
-

-For a given graph object, one will typically a draw directive before the -label directive. For example, for a node, one would first use the commands -in _draw_ followed by the commands in _ldraw_. -

-The value of these attributes consists of the concatenation of some -(multi-)set of the following 13 rendering or attribute operations. -(The number is parentheses gives the xdot version when the operation -was added to the format. If no version number is given, the operation -was in the original specification.) - -
E x₀ y₀ w h - Filled ellipse ((x-x₀)/w)² + ((y-y₀)/h)² = 1 -
e x₀ y₀ w h - Unfilled ellipse ((x-x₀)/w)² + ((y-y₀)/h)² = 1 -
P n x₁ y₁ ... x_n y_n - Filled polygon using the given n points -
p n x₁ y₁ ... x_n y_n - Unfilled polygon using the given n points -
L n x₁ y₁ ... x_n y_n - Polyline using the given n points -
B n x₁ y₁ ... x_n y_n - B-spline using the given n control points -
b n x₁ y₁ ... x_n y_n - Filled B-spline using the given n control points (1.1) -
T x y j w n -b₁b₂...b_n - Text drawn using the baseline point (x,y). The text consists of the -n bytes following '-'. The text should be left-aligned (centered, -right-aligned) on the point if j is -1 (0, 1), respectively. The value -w gives the width of the text as computed by the library. -
t f - Set font characteristics. The integer f is the OR of BOLD=1, ITALIC=2, UNDERLINE=4, SUPERSCRIPT=8, SUBSCRIPT=16, (1.5) STRIKE-THROUGH=32 (1.6), -and OVERLINE=64 (1.7). -
C n -b₁b₂...b_n - Set fill color. The color value consists of the -n bytes following '-'. (1.1) -
c n -b₁b₂...b_n - Set pen color. The color value consists of the -n bytes following '-'. (1.1) -
F s n -b₁b₂...b_n - Set font. The font size is s points. The font name consists of the -n bytes following '-'. (1.1) -
S n -b₁b₂...b_n - Set style attribute. The style value consists of the -n bytes following '-'. The syntax of the value is the same as -specified for a styleItem in style. (1.1) -
I x y w h n -b₁b₂...b_n - Externally-specified image drawn in the box with lower left -corner (x,y) and upper right corner (x+w,y+h). The name of the image -consists of the n bytes following '-'. This is usually a bitmap -image. Note that the image size, even when converted from pixels to -points, might be different from the required size (w,h). It is -assumed the renderer will perform the necessary scaling. (1.2) -
-

-Note that the filled figures (ellipses, polygons and B-Splines) -imply two operations: first, drawing the filled figure with the -current fill color; second, drawing an unfilled figure with the -current pen color, pen width and pen style. -

-Within the context of a single drawing attribute, e.g., _draw_, there is -an implicit state for the graphical attributes. That is, once a color, style, font, or -font characteristic is set, it remains valid for all relevant drawing operations -until the value is reset by another xdot cmd. -

-Style values which can be incorporated in the graphics model do not -appear in xdot output. In particular, the style values -filled, rounded, diagonals, and invis -will not appear. Indeed, if style contains invis, -there will not be any xdot output at all. -

-With version 1.4 of xdot, color strings may now encode linear and radial gradients. Linear -gradients have the form
- '[' x₀ y₀ x₁ y₁ n [color-stop]⁺ ']'
-where (x₀,y₀) and (x₁,y₁) define the starting and -ending points of the gradient line segment, and n gives the number of color-stops. Each -color-stop has the form
- v m -b₁b₂...b_m
-where v is a number in the range [0,1] defining a position on the gradient line segment, with -color specified by the m byte string b₁b₂...b_m, -the same format as used for colors in the 'c' and 'C' operations. -

-Radial gradients have the form
- '(' x₀ y₀ r₀ x₁ y₁ r₁ n [color-stop]⁺ ')'
-where x_j y_j r_j, for j=0,1, specify -the center and radius of the start and ending circle, and n gives the number of color-stops. -A color-stop has the same format as defined for linear gradients, again given the fractional -offset and its associated color. -

-In handling text alignment, the application may want to recompute the -string width using its own rendering primitives. -

-The text operation is only used in the label attributes. Normally, -the non-text operations are only used in the non-label attributes. -If, however, the decorate -attribute is set on an edge, its label -attribute will also contain a polyline operation. -In addition, if a label is a complex, HTML-like label, it will also -contain non-text operations. -

-All coordinates and sizes are in points. -Note though that if -an edge or node is invisible, no drawing operations are attached to it. -

-Version info: - - - - - - - - - - -
Xdot version Graphviz version Modification
1.0 1.9
1.1 2.8 First plug-in version
1.2 2.13 Support image operator I
1.3 2.31 Add numerical precision
1.4 2.32 Add gradient colors
1.5 2.34 Fix text layout problem; fix inverted vector in gradient; support version-specific output; new t op for text characteristics
1.6 2.35 Add STRIKE-THROUGH bit for t
1.7 2.37 Add OVERLINE for t
- -

cgimage -

Output using the CGImage format. - -

cmap -

Produces map files for client-side image maps. The cmap format is -mostly identical to cmapx, but the latter is well-formed XML amenable -to processing by XML tools. In particular, the cmapx output is wrapped in -<map></map>. -

-See Note. - -

eps -

Produces Encapsulated PostScript output. -At present, this is only guaranteed to be correct for a single -input graph since the Bounding Box information has to appear -at the beginning of the output, and this will be based on the first graph. - -

exr -

Output in the OpenEXR format - -

fig -

Outputs graphs in the FIG graphics language. - -

gd -,

gd2 -

Output images in the GD and GD2 format. These are the internal -formats used by the gd library. The latter is compressed. - -

gif -

Outputs GIF bitmap images. - -

gtk -

Creates a GTK window and displays the output there. - -

ico -

Outputs images in the Windows ICO format. - -

imap -,

cmapx -

Produces map files for server-side and client-side image maps. -These can be used in a web page with -a graphical form of the output, e.g. in JPEG, GIF or PNG format, to attach -links to nodes and edges. -Graphviz generates an object's map information only if the object has a non-trival -URL or href -attribute, or if it has an explicit tooltip attribute. -

-For example, to create a server-side map -given the dot file -

-/* x.gv */
-digraph mainmap {
-  URL="http://www.research.att.com/base.html";
-  command [URL="http://www.research.att.com/command.html"];
-  command -> output [URL="colors.html"];
-}
-

-one would process the graph and generate two output files: -

-dot -Timap -ox.map -Tgif -ox.gif x.gv
-

-and then refer to it in a web page: -

-<A HREF="x.map"><IMG SRC="x.gif" ismap="ismap" /></A>
-

-For client-side maps, one again generates two output files: -

-dot -Tcmapx -ox.map -Tgif -ox.gif x.gv
-

-and uses the HTML -

-<IMG SRC="x.gif" USEMAP="#mainmap" />
-... [content of x.map] ...
-

-Note that the name given in the USEMAP attribute must be the same -as the ID attribute of the MAP element. The Graphviz renderer -uses the name of the graph as the ID. Thus, in the example above, -where the graph's name is mainmap, we have USEMAP="#mainmap" -in the IMG attribute, and x.map will look like -

-<map id="mainmap" name="mainmap">
-... 
-</map>
-

-URLs can be attached to the root -graph, nodes and edges. If a node has a URL, clicking in the node -will activate the link. -If an edge has a URL, various -points along the edge (but not necessarily the head or tail) -will link to it. In addition, if the edge has a -label, that will link -to the URL. -As for the head of the edge, this is linked to the -headURL, if set. -Otherwise, it is linked to the edge's URL if that is defined. -The analogous description holds for the tail and the -tailURL. -A URL associated with the graph is used as a default link. -

-If the URL -of a node contains the escape sequence "\N", it will be replaced by -the node's name. -If the headURL is defined and contains the escape sequence "\N", -it will be replaced by -the headlabel, if defined. -The analogous result holds for the tailURL and the -taillabel. -

-See Note. - -

imap_np -,

cmapx_np -

These are identical to the imap and cmapx formats, except they -rely solely on rectangles as active areas. - -

ismap -

Produces HTML image map files. This is a predecessor (circa 1994) -of the IMAP format. Most servers now use the latter. -URLs can be attached to the root graph, -nodes and edges. Since edge -links are attached to edge labels, an edge must -have a label for its -URL to be used. For both nodes and edges, if the URL has the escape -sequence "\N" embedded in its string, this will be replaced with the -node or edge name. - -

jp2 -

Output using the JPEG 2000 format. - -

jpg -,

jpeg -,

jpe -

Output JPEG compressed image files. - -

json -,

json0 -,

dot_json -,

xdot_json -

These formats produce a JSON output encoding the DOT language. -Using json0 produces output in JSON format that contains the -same information produced by -Tdot. -Using json produces output in JSON format that contains the -same information produced by -Txdot. -Both of these assume the graph has been processed by one of the layout -algorithms. -The dot_json and xdot_json also produce JSON output similar to -to json0 and json, respectively, except they only use the -content of the graph on input. In particular, they do not assume that the -graph has been processed by any layout algorithm, and the only xdot information -appearing in the output was in the original input file. -

-The output produced by these follows the json schema shown below. -Note that the objects array has all of the subgraphs first, -followed by all of the nodes. The _gvid value is the index of -the subgraph or node in the objects array. This also holds -true for the edges in the objects array. Note that this format -allows clustered graphs, where edges can connect clusters as well as nodes. -

- - - -

pct -,

pict -

Output in the Apple PICT file format. - -

pdf -

Produces PDF output. -(This option assumes Graphviz includes the Cairo renderer.) -Alternatively, one can use the ps2 option to -produce PDF-compatible PostScript, and then use a ps-to-pdf converter. - -

pic -

Output is given in the text-based PIC language developed for troff. -See Pic language. - -

plain -,

plain-ext -

The plain and plain-ext formats produce output using -a simple, line-based language. -The latter format differs in that, on edges, it provides port names -on head and tail nodes when applicable. -

-There are four types of statements. -

- graph scale width height
- node name x y width height label style shape color fillcolor
- edge tail head n x₁ y₁ .. x_n y_n [label xl yl] style color
- stop
-

graph -

The width and height values give the width and height -of the drawing. The lower left corner of the drawing is at the origin. -The scale value indicates how the drawing should be scaled -if a size attribute was given and the drawing -needs to be scaled to conform to that size. If no scaling is necessary, -it will be set to 1.0. Note that all graph, node and edge -coordinates and lengths are given unscaled. -

node -

The name value is the name of the node, and x and y -give the node's position. The width and height are the -width and height of the node. -The label, -style, shape, color and fillcolor give the -node's label, -style, shape, -color and -fillcolor, -respectively, using attribute default values where necessary. If the -node does not have a style attribute, "solid" is used. -

edge -

The tail and head values give the names of the head and -tail nodes. In plain-ext format, the head or tail name will be appended -with a colon and a portname if the edge connects to the node at a port. -n is the number of control points defining the -B-spline forming the edge. This is followed by 2*n numbers giving -the x and y coordinates of the control points in order from tail to head. -If the edge has a label, this comes next -followed by the x and y coordinates of the label's position. -The edge description is completed by the edge's -style and color. -As with nodes, if a style is not defined, "solid" is used. -

-Note: The control points given in an edge statement define the -body of the edge. In particular, if the edge has an arrowhead to the -head or tail node, -there will be a gap between the last or first control points and the -boundary of the associated node. There are at least 3 possible ways -of handling this gap: -

Arrange that the input graph uses dir=none, -arrowhead=none, or arrowtail=none for all edges. -In this case, the terminating control points will always touch the node. -
Consider the line segment joining the control point and the center -of the node, and determine the point where the segment intersects the -node's boundary. Then use the control point and the intersection point -as the main axis of an arrowhead. The problem with this approach is -that, if the edge has a port, the edge will not be pointing to the -center of the node. In this case, rather than use the control point -and center point, one can use the control point and its tangent. -
Arrange that the input graph uses headclip=false or -tailclip=false. In this case, the edge will terminate at -the node's center rather than its boundary. If arrowheads are used, -there will still be a gap, but normally this will occur within the -node. The application will still need to clip the spline to the node -boundary. Also, as with the previous item, if the edge points to -a node port, this technique will fail. -

-The output consists of one graph line, a sequence of -node lines, one per node, a sequence of -edge lines, one per edge, and a final stop -line. All units are in inches, represented by a floating point number. -

-Note that the plain formats provide minimal information, really giving not -much more than node positions and sizes, and edge spline control points. -These formats are usually most useful to applications wanting just this -geometric information, and willing to fill in all of the graphical details. -The only real advantages to these formats is their terseness and their -ease of parsing. In general, the dot and -xdot are preferable in terms of the quantity of -information provided. - -

png -

Produces output in the PNG (Portable Network Graphics) format. -

-(25 November 2014) A standard Graphviz installation will render using both -the Cairo and GD library. -By mixing the rendering and formatting of these -libraries, one can achieve different variations in the output. -

-Tpng:gd (or -Tpng:gd:gd) -: Indexed color, no antialiasing -
-Tpng:cairo:gd -: Indexed color, with antialiasing -
-Tpng (or -Tpng:cairo) -: True color, with antialiasing -

-These options are listed in increasing order of image quality and output size. - -

pov -

Scene-description language for 3D modelling for the -Persistence of Vision Raytracer. - -

ps -

Produces PostScript output. -

-Note: The default PostScript renderer can only handle the Latin-1 -character set. To get non-Latin-1 characters into PostScript output, -use -Tps:cairo, assuming your version was built with the -Cairo renderer. - -

ps2 -

Produces PostScript output with PDF notations. It is assumed the output -will be directly converted into PDF format. The notations include PDF -bounding box information, so that the resulting PDF file can be correctly -used with pdf tools, such as pdflatex. -In addition, if a node has a URL -attribute, this gets translated into PDF code such that the node, -when viewed in a PDF-viewer, e.g., -acroread, -is a link to the given URL. If a URL is attached to the graph, this serves -as a base, such that relative URLs on nodes are derived from it. - -

psd -

Output in the Adobe PhotoShop PSD file format. - -

sgi -

Output in the SGI image file format. - -

svg -,

svgz -

Produce SVG output, -the latter in compressed format. -

-See Note. - -

tga -

Output in the Truevision TGA or TARGA format. - -

tif -,

tiff -

Produces TIFF output. - -

tk -

Output using the text-based TK graphics primitives. - -

vml -,

vmlz -

Produces VML output, -the latter in compressed format. -

-See Note. - -

vrml -

Outputs graphs in the VRML format. -To get a 3D embedding, nodes must have a z -attribute. These can either be supplied as part of the input graph, or -be generated by neato provided dim=3 -and at least one node has a z value. -

-Line segments are drawn as cylinders. -In general, VRML output relies on having the PNG library to produce images -used to texture-fill the node shapes. However, if -shape=point, -a node is drawn as a 3D sphere. - -

wbmp -

Produces output in the Wireless BitMap (WBMP) format, optimized for -mobile computing. - -

webp -

Produces output in the image format for the Web (WEBP) format, optimized for -web devices such as tablets. -See Wikipedia's WebP -or Google's webp pages. - -

xlib -,

x11 -

Creates an Xlib window and displays the output there. - -

Image Formats

-The image and shapefile attributes specify an image file to be included -as part of the final diagram. Not all image formats can be read. In addition, -even if read, not all image formats can necessarily be used in a given -output format. -

-The graph below shows what image formats can be used in which output formats, -and the required plugins. On the left are the supported image formats. -On the right are the supported output formats. -In the middle are the plugins: image loaders, renderers, drivers, arranged by -plugin library. -This presents the most general case. A given installation may not provide -one of the plugins, in which case, that transformation is not possible. -
- -

Notes

-In the formats: -Tcmap, -Tcmapx, -Tsvg, -Tvml, the output generates -'id="node#"' properties for nodes, 'id="edge#"' properties for edges, and 'id="cluster#"' properties for clusters, with the '#' replaced by an internally assigned integer. These strings can be provided instead by an externally provided "id=xxx" attribute on the object. -Normal "\N" "\E" "\G" substitutions are applied. -Externally provided id values are not used internally, and it is the use's reponsibilty to ensure -that they are sufficiently unique for their intended downstream use. -Note, in particular, that "\E" is not a unique id for multiedges. -

- - + +Moved to https://graphviz.org/doc/info/output.html. Redirecting... diff --git a/doc/info/schema.html b/doc/info/schema.html deleted file mode 100644 index 251c44365..000000000 --- a/doc/info/schema.html +++ /dev/null @@ -1 +0,0 @@ -

description

JSON representation of a graph encoding xdot attributes

title

Graphviz JSON

required

name
directed
strict
_subgraph_cnt

definitions

drawops

items

oneOf

$ref
#/definitions/ellipse
#/definitions/polygon
#/definitions/polyline
#/definitions/bspline
#/definitions/text
#/definitions/font_style
#/definitions/drawcolor
#/definitions/font
#/definitions/style

type

array

style

required

op
style

type

object

properties

style

type	string

pattern	S
type	string

font_style

required

op
fontchar

type

object

properties

pattern	t
type	string

fontchar

minimum	0
type	integer
maximum	127

polygon

required

op
points

type

object

properties

points

$ref	#/definitions/pointlist

pattern	[pP]
type	string

metanode

required

_gvid
name

type

object

properties

_draw_

$ref	#/definitions/drawops

name

type	string
description	The node or subgraph name

_ldraw_

$ref	#/definitions/drawops

_gvid

type	integer

subgraphs

items

type	integer

type

array

description

index of a child subgraph

edges

items

type	integer

type

array

description

index of an edge in this subgraph

additionalProperties

type	string

nodes

items

type	integer

type

array

description

index of a node in this subgraph

title

node or subgraph

color

pattern	(#[0-9a-f]*)\|(#[0-9a-f]{8})
type	string

text

required

op
pt
align
text
width

type

object

properties

text

type	string

align

pattern	[lcr]
type	string

pattern	T
type	string

$ref	#/definitions/point

width

type	number

point

minItems

items

type	number

type

array

maxItems

stop

required

frac
color

type

object

properties

color

$ref	#/definitions/color

frac

type	number

drawcolor

required

op
grad

type

object

properties

oneOf

$ref
#/definitions/point
#/definitions/point3

oneOf

$ref
#/definitions/point
#/definitions/point3

color

$ref	#/definitions/color

stops

items

$ref	#/definitions/stop

type

array

grad

enum	none linear radial
type	string

pattern	[cC]
type	string

ellipse

required

op
rect

type

object

properties

rect

$ref	#/definitions/rectangle

pattern	[eE]
type	string

bspline

required

op
points

type

object

properties

points

$ref	#/definitions/pointlist

pattern	[bB]
type	string

edge

required

_gvid
tail
head

type

object

properties

_hldraw_

$ref	#/definitions/drawops

_tdraw_

$ref	#/definitions/drawops

_draw_

$ref	#/definitions/drawops

_ldraw_

$ref	#/definitions/drawops

_gvid

type	integer

tail

type	integer
description	_gvid of tail node

_tldraw_

$ref	#/definitions/drawops

_hdraw_

$ref	#/definitions/drawops

additionalProperties

type	string

head

type	integer
description	_gvid of tail head

title

edge

polyline

required

op
points

type

object

properties

points

$ref	#/definitions/pointlist

pattern	L
type	string

font

required

op
size
face

type

object

properties

size

minimum	0
type	number

pattern	F
type	string

face

type	string

point3

minItems

items

type	number

type

array

maxItems

rectangle

minItems

items

type	number

type

array

maxItems

pointlist

items

$ref	#/definitions/point

type

array

type

object

properties

directed

type	boolean
description	True if the graph is directed

_draw_

$ref	#/definitions/drawops

name

type	string
description	The graph name

objects

items

$ref	#/definitions/metanode

type

array

description

The graph's subgraphs followed by the graph's nodes

_ldraw_

$ref	#/definitions/drawops

strict

type	boolean
description	True if the graph is strict

edges

items

$ref	#/definitions/edge

type

array

additionalProperties

type	string

_subgraph_cnt

type	integer
description	Number of subgraphs in the graph

\ No newline at end of file diff --git a/doc/info/shapes.html b/doc/info/shapes.html index 5cc45f3f8..ccd09ead5 100644 --- a/doc/info/shapes.html +++ b/doc/info/shapes.html @@ -1,1268 +1,2 @@ - - - - -Node Shapes - - - -

Node Shapes

-There are three main types of shapes : -polygon-based, -record-based and -user-defined. -The record-based shape has largely been superseded and greatly generalized -by HTML-like labels. -That is, instead of using shape=record, one might -consider using shape=none, margin=0 and an HTML-like label. -

-The geometry and style of all node shapes are affected by -the node attributes -fixedsize, -fontname, -fontsize, -height, -label, -style and -width. - -

Polygon-based Nodes

-The possible polygon-based shapes are displayed below. - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

-	-	-	-
box -	polygon -	ellipse -	oval -
-	-	-	-
circle -	point -	egg -	triangle -
-	-	-	-
plaintext -	plain -	diamond -	trapezium -
-	-	-	-
parallelogram -	house -	pentagon -	hexagon -
-	-	-	-
septagon -	octagon -	doublecircle -	doubleoctagon -
-	-	-	-
tripleoctagon -	invtriangle -	invtrapezium -	invhouse -
-	-	-	-
Mdiamond -	Msquare -	Mcircle -	rect -
-	-	-	-
rectangle -	square -	star -	none -
-	-	-	-
underline -	cylinder -	note -	tab -
-	-	-	-
folder -	box3d -	component -	promoter -
-	-	-	-
cds -	terminator -	utr -	primersite -
-	-	-	-
restrictionsite -	fivepoverhang -	threepoverhang -	noverhang -
-	-	-	-
assembly -	signature -	insulator -	ribosite -
-	-	-	-
rnastab -	proteasesite -	proteinstab -	rpromoter -
-	-	-
rarrow -	larrow -	lpromoter -

-As the figures suggest, the shapes rect and rectangle are synonyms for box, and none is a synonym for plaintext. -The shape plain is similar to these two, except that it also enforces -width=0 height=0 margin=0, which guarantees that the actual size of the node is entirely determined by the label. -This is useful, for example, when using HTML-like labels. -Also, unlike the rest, we have shown these three, as well as underline, -without style=filled -to indicate the normal use. If fill were turned on, the label text would -appear in a filled rectangle. -

-The geometries of polygon-based shapes are also affected -by the node attributes -regular, -peripheries and -orientation. -If shape="polygon", the attributes -sides, -skew and -distortion are also used. -If unset, they default to 4, 0.0 and 0.0, respectively. -The point shape is special in that it is -only affected by the peripheries, -width and -height attributes. -

-Normally, the size of a node is determined by smallest width and height -needed to contain its label and image, if any, with a margin specified by -the margin attribute. The width -and height must also be at least as large as the sizes specified by the -width and -height attributes, which specify -the minimum values for these parameters. -See the fixedsize attribute -for ways of restricting the node size. -In particular, if fixedsize=shape, the node's shape will be fixed -by the width and -height attributes, and the shape -is used for edge termination, but both the shape and label sizes are used -preventing node overlap. For example, the following graph -

-digraph G {
-  { 
-    node [margin=0 fontcolor=blue fontsize=32 width=0.5 shape=circle style=filled]
-    b [fillcolor=yellow fixedsize=true label="a very long label"]
-    d [fixedsize=shape label="an even longer label"]
-  }
-  a -> {c d}
-  b -> {c d}
-}
-

-yields the figure
-

-Note that the label of the yellow node, with fixedsize=true, overlaps -the other node, where there is sufficient space for the gray node with -fixedsize=shape. -

-The shapes: note, tab, folder, -box3d and component were provided by Pander. -The synthetic biology shapes: -promoter, -cds, -terminator, -utr, -primersite, -restrictionsite, -fivepoverhang, -threepoverhang, -noverhang, -assembly, -signature, -insulator, -ribosite, -rnastab, -proteasesite, -proteinstab, -rpromoter, -rarrow, -larrow and -lpromoter -were contributed by Jenny Cheng. - -

Record-based Nodes

-NOTE: Please see the note about record-based nodes at the -top of this page. Also note that there are problems using -non-trivial edges (edges with ports or labels) between adjacent -nodes on the same rank if one or both nodes has a record shape. -

-These are specified by shape values of "record" and "Mrecord". -The structure of a record-based node is determined by -its label, -which has the following schema: - - - - -
rlabel = field ( '|' field )*
where field = fieldId or '{' rlabel '}'
and fieldId = [ '<' string '>'] [ string ]
-Braces, vertical bars and angle brackets must be escaped with -a backslash character if you wish them to appear as a literal character. -Spaces are interpreted as separators between tokens, -so they must be escaped if you want spaces in the text. -

-The first string in fieldId assigns a portname to the field and can -be combined with the node name to indicate where to attach an edge -to the node. (See portPos.) -The second string is used as the text for the field; it supports the usual -escape sequences \n, \l and \r. -

-Visually, a record is a box, with fields represented by alternating -rows of horizontal or vertical subboxes. The Mrecord shape is identical -to a record shape, except that the outermost box has rounded corners. -Flipping between horizontal and vertical layouts is done by nesting -fields in braces "{...}". The top-level orientation in a record is -horizontal. Thus, a record with label "A | B | C | D" will have 4 fields -oriented left to right, while "{A | B | C | D}" will have them -from top to bottom and "A | { B | C } | D" will have "B" over "C", with -"A" to the left and "D" to the right of "B" and "C". -

-The initial orientation of a record node depends on the -rankdir attribute. If this attribute -is TB (the default) or BT, corresponding to vertical -layouts, the top-level fields in a record are displayed horizontally. -If, however, this attribute is LR or RL, -corresponding to horizontal layouts, the top-level fields are -displayed vertically. -

-As an example of a record node, the dot input -

-digraph structs {
-    node [shape=record];
-    struct1 [label="<f0> left|<f1> mid&#92; dle|<f2> right"];
-    struct2 [label="<f0> one|<f1> two"];
-    struct3 [label="hello&#92;nworld |{ b |{c|<here> d|e}| f}| g | h"];
-    struct1:f1 -> struct2:f0;
-    struct1:f2 -> struct3:here;
-}
-

- -yields the figure
-

-If we add the line -

-    rankdir=LR
-

-we get the layout
-

-If we change node struct1 to have shape Mrecord, -it then looks like:
- - -

Styles for Nodes

-The style -attribute can be used to modify the appearance of a node. -At present, there are 8 style values recognized: -filled, invisible, diagonals, rounded. -dashed, dotted, solid and bold. -As usual, the value of the style -attribute can be a comma-separated list of any of these. If the -style contains conflicts (e.g, style="dotted, solid"), the last -attribute wins. -

filled -

This value indicates that the node's interior should be filled. -The color used is the node's fillcolor or, if that's not defined, its -color. For unfilled nodes, the interior of the node is transparent to -whatever color is the current graph or cluster background color. -Note that point shapes are always filled. -

-Thus, the code -

-digraph G {
-  rankdir=LR
-  node [shape=box, color=blue]
-  node1 [style=filled] 
-  node2 [style=filled, fillcolor=red] 
-  node0 -> node1 -> node2
-}
-

-yields the figure
-

- -

invisible -

Setting this style causes the node not to be displayed at all. -Note that the node is still used in laying out the graph. - -

diagonals -

The diagonals style causes small chords to be drawn near the vertices -of the node's polygon or, in case of circles and ellipses, two chords near -the top and the bottom of the shape. The special node shapes -Msquare, -Mcircle, and -Mdiamond -are simply an ordinary square, circle and -diamond with the diagonals style set. - -

rounded -

The rounded style causes the polygonal corners to be smoothed. -Note that this style also applies to record-based nodes. Indeed, -the Mrecord shape is simply shorthand for setting this style. -Also, prior to 26 April 2005, the rounded and filled styles were -mutually exclusive. -

-As an example of rounding, dot uses the graph -

-digraph R {
-  rankdir=LR
-  node [style=rounded]
-  node1 [shape=box]
-  node2 [fillcolor=yellow, style="rounded,filled", shape=diamond]
-  node3 [shape=record, label="{ a | b | c }"]
-
-  node1 -> node2 -> node3
-}
-

-to produce the figure
-

dashed -

This style causes the node's border to be drawn as a dashed line. -

dotted -

This style causes the node's border to be drawn as a dotted line. -

solid -

This style causes the node's border to be drawn as a solid line, -which is the default. -

bold -

This style causes the node's border to be drawn as a bold line. -See also penwidth. - -

- -

-Additional styles may be available with a specific code generator. -

HTML-Like Labels

- -NOTE:This feature is only available on versions of Graphviz -that are newer than mid-November 2003. In particular, it is not part -of release 1.10. -

-NOTE:The font markups for bold, italic, underlining, subscript and -superscript (, , ,  and ) -are only available in versions after 14 October 2011, and -the markup for strike-through (<S>) requires versions later than 15 September 2013. -In addition, all of these markups are -currently only available via the cairo and svg renderers. -The horizontal and vertical rules (<HR> and <VR>) -are only available in versions later than 8 July 2011. -

-NOTE:For releases later than 9 September 2014, one can use shape=plain so that the size -of the node is totally determined by the label. Otherwise, the node's margin, width and height values may cause the -node to be larger, so that edges are clipped away from the label. In effect, shape=plain is shorthand -for shape=none width=0 height=0 margin=0. -

-If the value of a label attribute -(label for nodes, edges, clusters, and -graphs, and the -headlabel and -taillabel -attributes of an edge) is given as an -HTML string, -that is, delimited by <...> -rather than "...", -the label is interpreted as -an HTML description. At their simplest, such labels -can describe multiple lines of variously aligned text as provided by ordinary -string labels. More generally, the -label can specify a table similar to those provided by HTML, -with different graphical attributes at each level. -

-As HTML strings are processed like HTML input, any use of -the ", &, <, and > characters in literal text or in attribute values -need to be replaced by the corresponding escape sequence. For example, if you want to -use & in an href value, this should be represented as &. -

-NOTE: The features and syntax supported by these labels are -modeled on HTML. However, there are many aspects that are relevant -to Graphviz labels that are not in HTML and, conversely, HTML allows -various constructs which are meaningless in Graphviz. We will generally -refer to these labels as "HTML labels" rather than the cumbersome -"HTML-like labels" but the reader is warned that these are not really -HTML. The grammar below describes precisely what Graphviz will accept. -

-Although HTML labels are not, strictly speaking, a shape, they can be -viewed as a generalization of the record shapes described above. -In particular, if a node has set its -shape -attribute to none or plaintext, the HTML label will be the node's -shape. On the other hand, if the node has any other shape (except -point), the HTML label will be embedded within the node the -same way an ordinary label would be. Adding HTML labels to record-based shapes (record and Mrecord) is discouraged and may lead to unexpected behavior because of their conflicting label schemas and overlapping functionality. -

-The following is an abstract grammar for HTML labels. -Terminals, corresponding to elements, are shown in bold font, -and nonterminals in italics. -Square brackets [ and ] enclose optional items. -Vertical bars | separate alternatives. -Note that, as in HTML, element and attribute names are case-insensitive. -(cf. sections 3.2.1 and 3.2.2 of the -HTML 4.01 specification). - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
label : text
| fonttable
text : textitem
| text textitem
textitem : string
|  
|  text 
|  text 
|  text 
|  text 
| <O> text </O>
|  text 
|  text 
| <S> text </S>
fonttable : table
|  table 
|  table 
|  table 
|  table 
| <O> table </O>
table : <TABLE> rows </TABLE>
rows : row
| rows row
| rows <HR/> row
row : <TR> cells </TR>
cells : cell
| cells cell
| cells <VR/> cell
cell : <TD> label </TD>
| <TD> <IMG/> </TD>
-

-All non-printing characters such as tabs or newlines are ignored. -Above, a string is any collection of printable characters, including -spaces. For tables, outside of the body of a <TD> element, -whitespace characters are ignored, including spaces; within a <TD> element, spaces -are preserved but all other white space characters are discarded. -N.B. For technical reasons, if a table is wrapped in a font element such as -or , any space immediately before or after this will cause a syntax error. For example, -the label -

-< <U><TABLE><TR><TD>a</TD></TR></U>>
-

-is not legal. Removing either the space or the ... will fix this. -

-HTML comments are allowed within an HTML string. They can occur anywhere -provided that, if they contain part of an HTML element, they must contain -the entire element. -

-As is obvious from the above description, the interpretation of white space -characters is one place where HTML-like labels is very different from -standard HTML. In HTML, any sequence of white space characters is -collapsed to a single space, If the user does not want this to happen, the -input must use non-breaking spaces " ". This makes sense in -HTML, where text layout depends dynamically on the space available. In -Graphviz, the layout is statically determined by the input, so it is -reasonable to treat ordinary space characters as non-breaking. In addition, -ignoring tabs and newlines allows the input text to be formatted for -easier reading. -

-Each of the HTML elements has a set of optional attributes. -Attribute values must appear in double quotes. -

-  -

-<TABLE
-  ALIGN="CENTER|LEFT|RIGHT"
-  BGCOLOR="color"
-  BORDER="value"
-  CELLBORDER="value"
-  CELLPADDING="value"
-  CELLSPACING="value"
-  COLOR="color"
-  COLUMNS="value"
-  FIXEDSIZE="FALSE|TRUE"
-  GRADIENTANGLE="value"
-  HEIGHT="value"
-  HREF="value"
-  ID="value"
-  PORT="portName"
-  ROWS="value"
-  SIDES="value"
-  STYLE="value"
-  TARGET="value"
-  TITLE="value"
-  TOOLTIP="value"
-  VALIGN="MIDDLE|BOTTOM|TOP"
-  WIDTH="value"
->
-

-  -

<TR
-  <!-- No attributes -->
->
-

-  -

<TD
-  ALIGN="CENTER|LEFT|RIGHT|TEXT"
-  BALIGN="CENTER|LEFT|RIGHT"
-  BGCOLOR="color"
-  BORDER="value"
-  CELLPADDING="value"
-  CELLSPACING="value"
-  COLOR="color"
-  COLSPAN="value"
-  FIXEDSIZE="FALSE|TRUE"
-  GRADIENTANGLE="value"
-  HEIGHT="value"
-  HREF="value"
-  ID="value"
-  PORT="portName"
-  ROWSPAN="value"
-  SIDES="value"
-  STYLE="value"
-  TARGET="value"
-  TITLE="value"
-  TOOLTIP="value"
-  VALIGN="MIDDLE|BOTTOM|TOP"
-  WIDTH="value"
->
-

- -

-  -

<FONT
-  COLOR="color"
-  FACE="fontname"
-  POINT-SIZE="value"
->
-

- -

-  -

<BR
-  ALIGN="CENTER|LEFT|RIGHT"
-/>
-

- -

-  -

<IMG
-  SCALE="FALSE|TRUE|WIDTH|HEIGHT|BOTH"
-  SRC="value"
-/>
-

-  -

<I
-  <!-- No attributes -->
->
-

-  -

<B
-  <!-- No attributes -->
->
-

-  -

<U
-  <!-- No attributes -->
->
-

-  -

<O
-  <!-- No attributes -->
->
-

-  -

<SUB
-  <!-- No attributes -->
->
-

-  -

<SUP
-  <!-- No attributes -->
->
-

-  -

<S
-  <!-- No attributes -->
->
-

-  -

<HR
-  <!-- No attributes -->
-/>
-

-  -

<VR
-  <!-- No attributes -->
-/>
-

- -

-ALIGN -

-specifies horizontal placement. When an object is allocated -more space than required, this value determines where the extra space -is placed left and right of the object. -
-
-
CENTER aligns the object in the center. (Default)
-
LEFT aligns the object on the left.
-
RIGHT aligns the object on the right.
-
(<TD> only) TEXT aligns lines of text using the full -cell width. The alignment of a line is determined by its (possibly -implicit) associated   element.
-
-
-The contents of a cell are normally aligned as a block. In particular, -lines of text are first aligned as a text block based on the width of -the widest line and the corresponding   elements. Then, -the entire text block is aligned within a cell. If, however, the -cell's ALIGN value is "TEXT", and the cell contains -lines of text, then the lines are justified using the entire available -width of the cell. If the cell does not contain text, then the contained -image or table is centered. -

- -BALIGN -

-specifies the default alignment of   elements contained -in the cell. That is, if a   element has no -explicit ALIGN attribute, the attribute value is specified -by the value of BALIGN. -

- -BGCOLOR="color" -

-sets the color of the background. This color can be -overridden by a BGCOLOR attribute in descendents. -The value can be a single color or two colors separated by a colon, the -latter indicating a gradient fill. -

- -BORDER="value" -

-specifies the width of the border around the object in points. -A value of zero indicates no border. The default is 1. -The maximum value is 255. -If set in a table, and CELLBORDER is not set, -this value is also used for all cells in the table. -It can be overridden by a BORDER tag in a cell. -

- -CELLBORDER="value" -

-specifies the width of the border for all cells in a table. -It can be overridden by a BORDER tag in a cell. -The maximum value is 255. -

- -CELLPADDING="value" -

-specifies the space, in points, between a cell's border and its content. -The default is 2. -The maximum value is 255. -

- -CELLSPACING="value" -

-specifies the space, in points, between cells in a table and between -a cell and the table's border. The default is 2. -The maximum value is 127. -

- -COLOR="color" -

-sets the color of the font within the scope of -..., or the border color -of the table or cell within the scope of -<TABLE>...</TABLE>, -or <TD>...</TD>. -This color can be -overridden by a COLOR attribute in descendents. -By default, the font color is determined by the -fontcolor attribute of -the corresponding node, edge or graph, and the border color -is determined by the -color attribute of -the corresponding node, edge or graph. -

- -COLSPAN="value" -

-specifies the number of columns spanned by the cell. The default is 1. -The maximum value is 65535. -

- -COLUMNS="value" -

-provides general formatting information concerning the columns. -At present, the only legal value is "*", which causes a vertical rule to -appear between every cell in every row. -

- -FACE="fontname" -

-specifies the font to use within the scope of -.... -This can be -overridden by a FACE attribute in descendents. -By default, the font name is determined by the -fontname attribute of the corresponding -node, edge or graph. -

- -FIXEDSIZE -

-specifies whether the values given by the WIDTH -and HEIGHT attributes are enforced. -
-
-
FALSE allows the object to grow so that all its contents will fit. (Default)
-
TRUE fixes the object size to its given WIDTH -and HEIGHT. -Both of these attributes must be supplied.
-
-

- -GRADIENTANGLE="value" -

-gives the angle used in a gradient fill if the -BGCOLOR is a color list. For the default linear gradient, -this specifies -the angle of a line through the center along which the colors transform. -Thus, an angle of 0 will cause a left-to-right progression. -For radial gradients (see STYLE), the angle specifies the position -of the center of the coloring. An angle of 0 places the center at the center of the -table or cell; an non-zero angle places the fill center along that angle near the -boundary. -

- -HEIGHT="value" -

-specifies the mininum height, in points, of the object. The height -includes the contents, any spacing and the border. Unless -FIXEDSIZE is true, the height will be expanded to allow -the contents to fit. -The maximum value is 65535. -

- -HREF="value" -

-attaches a URL to the object. -Note that the "value" is treated as an -escString similarly to the -URL attribute. -

- -ID="value" -

-allows the user to specify a unique ID for a table or cell. See -the id attribute for more information. -Note that the "value" is treated as an -escString similarly to the -id attribute. -

- -POINT-SIZE="value" -

-sets the size of the font, in points, used within the scope of -.... -This can be -overridden by a POINT-SIZE attribute in descendents. -By default, the font size is determined by the -fontsize attribute of the corresponding -node, edge or graph. -

- -PORT="value" -

-attaches a portname to the object. -(See portPos.) -This can be used to modify the head -or tail of an edge, so that the end attaches directly to the object. -

- -ROWS="value" -

-provides general formatting information concerning the rows. -At present, the only legal value is "*", which causes a horizontal rule to -appear between every row. -

- -ROWSPAN="value" -

-specifies the number of rows spanned by the cell. The default is 1. -The maximum value is 65535. -

- -SCALE -

-specifies how an image will use any extra space available in its cell. -Allowed values are -
-
FALSE : keep image its natural size. (Default)
-
TRUE : scale image uniformly to fit.
-
WIDTH : expand image width to fill
-
HEIGHT : expand image height to fill
-
BOTH : expand both image width height to fill
-
-If this attribute is undefined, -the image inherits the imagescale -attribute of the graph object being drawn. -As with the imagescale -attribute, if the cell has a fixed size and the image is too large, -any offending dimension will be shrunk to fit the space, the -scaling being uniform in width and height if SCALE="true". -Note that the containing cell's ALIGN -and VALIGN attributes override -an image's SCALE attribute. -

- -SIDES="value" -

-specifies which sides of a border in a cell or table should be drawn, if -a border is drawn. By default, all sides are drawn. The "value" -string can contain any collection of the (case-insensitive) -characters 'L', 'T', 'R', or 'B', -corresponding to the left, top, right and, bottom sides of the border, -respectively. For example, SIDES="LB" would indicate only the -left and bottom segments of the border should be drawn. -

- -SRC="value" -

-specifies the image file to be displayed in the cell. -Note that if the software is used as a web server, file system access -to images is more restricted. See GV_FILE_PATH -and SERVER_NAME. -

- -

-STYLE -

-specifies style characteristics of the table or cell. Style characteristics are -given as a comma or space separated list of style attributes. At present, the only -legal attributes are "ROUNDED" and "RADIAL" for tables, and "RADIAL" for cells. -If "ROUNDED" is specified, the table will have rounded corners. -This probably works best if the outmost cells have no borders, or their CELLSPACING -is sufficiently large. -If it is desirable to have borders around the cells, use HR -and VR elements, or the COLUMNS and ROWS attributes of TABLE. -
-The "RADIAL" attribute indicates a radial gradient fill. See the BGCOLOR and -GRADIENTANGLE attributes. -

- -TARGET="value" -

-determines which window of the browser is used for the URL if the object -has one. -See W3C documentation. -Note that the "value" is treated as an -escString similarly to the -target attribute. -

- -TITLE="value" -

-sets the tooltip annotation attached to the element. -This is used only if the element has a HREF attribute. -Note that the "value" is treated as an -escString similarly to the -tooltip attribute. -

- -TOOLTIP="value" -

-is an alias for TITLE. -

- -

-VALIGN -

-specifies vertical placement. When an object is allocated -more space than required, this value determines where the extra space -is placed above and below the object. -
-
-
MIDDLE aligns the object in the center. (Default)
-
BOTTOM aligns the object on the bottom.
-
TOP aligns the object on the top.
-
-

- -WIDTH="value" -

-specifies the mininum width, in points, of the object. The width -includes the contents, any spacing and the border. Unless -FIXEDSIZE is true, the width will be expanded to allow -the contents to fit. -The maximum value is 65535. -

- -

-There is some inheritance among the attributes. If a table specifies -a CELLPADDING, CELLBORDER or BORDER -value, this value is used by the table's -cells unless overridden. If a cell or table specifies a BGCOLOR, -this will be the background color for all of its descendents. -Of course, if a background or fill color is specified for the -graph object owning the label, this will be the original -background for the label. -The object's fontname, fontcolor and fontsize attributes -are the default for drawing text. These can be overridden by using -FONT to set new values. The new font values will hold -until overridden by an enclosed FONT element. -Finally, the pencolor or color of the graph object will be used as -the border color. -

-If you want horizontal or vertical rules used uniformly within a table, consider -using the COLUMNS or ROWS attributes -rather than using many -HR and VR elements. -

-Because of certain limitations in handling tables in a device-independent -manner, when BORDER is 1 and both table and cell borders -are on and CELLSPACING is less than 2, anomalies can arise -in the output, such as gaps between sides of borders which should be -abutting or even collinear. The user can usual get around this by increasing -the border size or the spacing, or turning off the table border. -

-As an example of HTML labels, the dot input -

-digraph structs {
-    node [shape=plaintext]
-    struct1 [label=<
-<TABLE BORDER="0" CELLBORDER="1" CELLSPACING="0">
-  <TR><TD>left</TD><TD PORT="f1">mid dle</TD><TD PORT="f2">right</TD></TR>
-</TABLE>>];
-    struct2 [label=<
-<TABLE BORDER="0" CELLBORDER="1" CELLSPACING="0">
-  <TR><TD PORT="f0">one</TD><TD>two</TD></TR>
-</TABLE>>];
-    struct3 [label=<
-<TABLE BORDER="0" CELLBORDER="1" CELLSPACING="0" CELLPADDING="4">
-  <TR>
-    <TD ROWSPAN="3">hello<BR/>world</TD>
-    <TD COLSPAN="3">b</TD>
-    <TD ROWSPAN="3">g</TD>
-    <TD ROWSPAN="3">h</TD>
-  </TR>
-  <TR>
-    <TD>c</TD><TD PORT="here">d</TD><TD>e</TD>
-  </TR>
-  <TR>
-    <TD COLSPAN="3">f</TD>
-  </TR>
-</TABLE>>];
-    struct1:f1 -> struct2:f0;
-    struct1:f2 -> struct3:here;
-}
-

-produces the HTML analogue of the record example above
-

-As usual, an HTML specification is more verbose. On the other hand, -HTML labels are much more general, as the following example shows: -

- -

-The source for this graph can be found here. -

-Here is an example using elements -

- -

-with the input graph. -

-Here is an example using an <IMG> element -

- -

-with the input graph. -

-The sides attribute (version 2.37 and later) allows one to combine cells to form -various non-convex shapes. For example, a tee-shaped node -

- -

-can be produced using -

-  tee [shape=none margin=0 label=
-    <<table border="0" cellspacing="0" cellborder="1">
-     <tr>
-      <td width="9" height="9" fixedsize="true" style="invis"></td>
-      <td width="9" height="9" fixedsize="true" sides="ltr"></td>
-      <td width="9" height="9" fixedsize="true" style="invis"></td>
-     </tr>
-     <tr>
-      <td width="9" height="9" fixedsize="true" sides="tlb"></td>
-      <td width="9" height="9" fixedsize="true" sides="b"></td>
-      <td width="9" height="9" fixedsize="true" sides="brt"></td>
-     </tr>
-    </table>>]
-

User-defined Nodes

- -There is a third type of node shape which is specified by the user. -Typically, these shapes rely on the details of a concrete graphics -format. At present, shapes can be described using PostScript, via a -file or add-on library, for use in PostScript output, or shapes can -be specified by a bitmap-image file for use with SVG or bitmap (jpeg, -gif, etc.) output. More information can be found on the page - -How to create custom shapes. - -

SDL Shapes for PostScript

-One example of user-defined node shapes is provided by Mark Rison of CSR. -These are the SDL shapes. -These are available as PostScript functions whose use is described in - External PostScript procedures. -The necessary PostScript library file and sample use can be found in the -contrib/sdlshapes directory in the release. Please note the -COPYRIGHT AND PERMISSION NOTICE contained in the library file sdl.ps. -

-The table below -gives the shape names and the corresponding node shapes. -

- - - + +Moved to https://graphviz.org/doc/info/shapes.html. Redirecting...

Command-line parameter	Format
bmp -	Windows Bitmap Format
canon - dot - gv - xdot - xdot1.2 - xdot1.4 -	DOT
cgimage -	CGImage bitmap format
cmap -	Client-side imagemap (deprecated)
eps -	Encapsulated PostScript
exr -	OpenEXR
fig -	FIG
gd - gd2 -	GD/GD2 formats
gif -	GIF
gtk -	GTK canvas
ico -	Icon Image File Format
imap - cmapx -	Server-side and client-side imagemaps
imap_np - cmapx_np -	Server-side and client-side imagemaps
ismap -	Server-side imagemap (deprecated)
jp2 -	JPEG 2000
jpg - jpeg - jpe -	JPEG
json - json0 - dot_json - xdot_json -	Dot graph represented in JSON format
pct - pict -	PICT
pdf -	Portable Document Format (PDF)
pic -	Kernighan's PIC graphics language
plain - plain-ext -	Simple text format
png -	Portable Network Graphics format
pov -	POV-Ray markup language (prototype)
ps -	PostScript
ps2 -	PostScript for PDF
psd -	PSD
sgi -	SGI
svg - svgz -	Scalable Vector Graphics
tga -	Truevision TGA
tif - tiff -	TIFF (Tag Image File Format)
tk -	TK graphics
vml - vmlz -	Vector Markup Language (VML)
vrml -	VRML
wbmp -	Wireless BitMap format
webp -	Image format for the Web
xlib - x11 -	Xlib canvas

_draw_	General drawing without labels -
_ldraw_	Label drawing -
_hdraw_	Head arrowhead	Edge only -
_tdraw_	Tail arrowhead	Edge only -
_hldraw_	Head label	Edge only -
_tldraw_	Tail label	Edge only -

E x₀ y₀ w h -	Filled ellipse ((x-x₀)/w)² + ((y-y₀)/h)² = 1 -
e x₀ y₀ w h -	Unfilled ellipse ((x-x₀)/w)² + ((y-y₀)/h)² = 1 -
P n x₁ y₁ ... x_n y_n -	Filled polygon using the given n points -
p n x₁ y₁ ... x_n y_n -	Unfilled polygon using the given n points -
L n x₁ y₁ ... x_n y_n -	Polyline using the given n points -
B n x₁ y₁ ... x_n y_n -	B-spline using the given n control points -
b n x₁ y₁ ... x_n y_n -	Filled B-spline using the given n control points (1.1) -
T x y j w n -b₁b₂...b_n -	Text drawn using the baseline point (x,y). The text consists of the -n bytes following '-'. The text should be left-aligned (centered, -right-aligned) on the point if j is -1 (0, 1), respectively. The value -w gives the width of the text as computed by the library. -
t f -	Set font characteristics. The integer f is the OR of BOLD=1, ITALIC=2, UNDERLINE=4, SUPERSCRIPT=8, SUBSCRIPT=16, (1.5) STRIKE-THROUGH=32 (1.6), -and OVERLINE=64 (1.7). -
C n -b₁b₂...b_n -	Set fill color. The color value consists of the -n bytes following '-'. (1.1) -
c n -b₁b₂...b_n -	Set pen color. The color value consists of the -n bytes following '-'. (1.1) -
F s n -b₁b₂...b_n -	Set font. The font size is s points. The font name consists of the -n bytes following '-'. (1.1) -
S n -b₁b₂...b_n -	Set style attribute. The style value consists of the -n bytes following '-'. The syntax of the value is the same as -specified for a styleItem in style. (1.1) -
I x y w h n -b₁b₂...b_n -	Externally-specified image drawn in the box with lower left -corner (x,y) and upper right corner (x+w,y+h). The name of the image -consists of the n bytes following '-'. This is usually a bitmap -image. Note that the image size, even when converted from pixels to -points, might be different from the required size (w,h). It is -assumed the renderer will perform the necessary scaling. (1.2) -

Xdot version	Graphviz version	Modification
1.0	1.9
1.1	2.8	First plug-in version
1.2	2.13	Support image operator I
1.3	2.31	Add numerical precision
1.4	2.32	Add gradient colors
1.5	2.34	Fix text layout problem; fix inverted vector in gradient; support version-specific output; new t op for text characteristics
1.6	2.35	Add STRIKE-THROUGH bit for `t`
1.7	2.37	Add OVERLINE for `t`

rlabel	=	field ( '\|' field )*
where field	=	fieldId or '{' rlabel '}'
and fieldId	=	[ '<' string '>'] [ string ]

label	:	text
	\|	fonttable
text	:	textitem
	\|	text textitem
textitem	:	string
	\|	<BR/>
	\|	<FONT> text </FONT>
	\|	<I> text </I>
	\|	<B> text </B>
	\|	<U> text </U>
	\|	<O> text </O>
	\|	<SUB> text </SUB>
	\|	<SUP> text </SUP>
	\|	<S> text </S>
fonttable	:	table
	\|	<FONT> table </FONT>
	\|	<I> table </I>
	\|	<B> table </B>
	\|	<U> table </U>
	\|	<O> table </O>
table	:	<TABLE> rows </TABLE>
rows	:	row
	\|	rows row
	\|	rows <HR/> row
row	:	<TR> cells </TR>
cells	:	cell
	\|	cells cell
	\|	cells <VR/> cell
cell	:	<TD> label </TD>
	\|	<TD> <IMG/> </TD>