dia - a diagram drawing program
dia [-c] [--credits] [-e OUTPUT] [--export=OUTPUT] [-L LAYER,LAYER,...] [--show-layers=LAYER,LAYER,...] [-h] [--help] [-n] [--nosplash] [-s WxH] [--size=WxH] [-t FORMAT] [--filter=TYPE] [-v] [--version] [file ...]
Dia is used to create diagrams. Dia has a number of basic tools, like lines and boxes but can also dynamically load sheets. A sheet is a collection of tools that are used in a certain type of diagram.
Most diagram objects in Dia have connection points. Lines can be connected to these connection points and this way graph structures can be formed. When objects are moved or resized the connections will follow the objects.
Diagrams drawn in Dia can be exported to various formats.
Dia accepts the following options:
-e OUTPUT --export=OUTPUT
-s WxH --size=WxH
This option is currently only implemented for the PNG export filter.
-L LAYER,LAYER,... --show-layers=LAYER,LAYER,...
-t TYPE --filter=TYPE
The following export formats are supported by dia. Most formats are implemented by plug-ins so their availability depends on compile- and runtime-configuration.
The format specifications eps and eps-pango both use the font renderer of the Pango library, while eps-builtin uses a dia specific font renderer. If you have problems with Pango rendering, e.g. Unicode, try eps-builtin instead.
There are three different SVG exporters with Dia having different specializations. cairo-svg is turning text to shapes to become independent of font availability on the target system. dia-svg is based on Dia core code only. It's translating all Dia's rendering capabilities as closely as possible to SVG. svg-py - as SVG renderer implemented in Python - is producing plain SVG. It is the most hackable version to allow some user adaptions
dia creates a directory .dia in the user's home, which contains different files to store user preferences. To reset dia to it's default behaviour, just remove the respective file:
Copyright 1999 Alexander Larsson.
Permission to use, copy, modify, and distribute this software and its documentation for any purpose and without fee is hereby granted, provided that the above copyright notice appear in all copies and that both that copyright notice and this permission notice appear in supporting documentation.
This manual was written by Fredrik Hallenberg.
Fredrik Hallenberg <email@example.com>
W. Borgert <firstname.lastname@example.org>
Alan Horkan <email@example.com>
Copyright © 1999, 2004 Fredrik Hallenberg, W. Borgert, Alan Horkan