1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
|
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
"DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml">
<!-- XML file produced from file: manual.tex
using Hyperlatex v 2.6 (c) Otfried Cheong
on Emacs 21.3.1, Tue Sep 26 20:03:45 2006 -->
<head>
<title>Ipe Manual -- 3 Command line options, auxiliary programs, and environment variables</title>
<style type="text/css">
.maketitle { align : center }
div.abstract { margin-left: 20%; margin-right: 10%; }
h3.abstract { align : center }
div.verse, div.quote, div.quotation {
margin-left : 10%;
margin-right : 10%;
}
</style>
<meta http-equiv="Content-Type"
content="text/html; charset=UTF-8">
</head>
<body bgcolor="#ffffe6">
<table width="100%" cellpadding=0 cellspacing=2><tr><td bgcolor="#99ccff"><a href="manual_4.html"><img border="0" alt="4 General Concepts" src="next.png"></a></td><td bgcolor="#99ccff"><a href="manual.html"><img border="0" alt="Top" src="up.png"></a></td><td bgcolor="#99ccff"><a href="manual_2.html"><img border="0" alt="2 About Ipe files" src="previous.png"></a></td><td align="center" bgcolor="#99ccff" width="100%"><b>3 Command line options, auxiliary programs, and environment variables</b></td></tr></table>
<h1>3 Command line options, auxiliary programs, and environment variables</h1>
<h4><a name="id1">Ipe command line options</a></h4>
<p>Ipe supports the following two options:
<dl><dt><b><code>-sheet</code> <em>style sheet name</em></b><dd>
Adds the designated style sheet to any newly created documents.
<dt><b><code>-geom</code> <em>WxH+X+Y</em></b><dd>
Places the Ipe main windows at the desired position and size.
(Note the slight difference with the standard Unix option
<code>-geometry</code>).
</dl>
In addition, you can specify the name of an Ipe file to open on the
command line. Finally, Ipe also understands some standard X11 options
on Unix (this is support built into the Qt library, see there for
details).
<h4><a name="id2">ipetoipe: converting Ipe file formats</a></h4>
<p>The auxiliary program <em>ipetoipe</em> converts between the different
Ipe file formats:
<pre>
ipetoipe ( -xml | -pdf | -eps | -ps ) [ -export ] [ -noshading ] [-lastview ] infile outfile
</pre>
For example, the command line syntax
<pre>
ipetoipe -pdf figure1.eps figure1.pdf
</pre>
converts <code>figure1.eps</code> to PDF format.
<p>When you use the <code>-export</code> flag, no Ipe markup is included in the
resulting output file. Ipe will not be able to open a file created
that way, so make sure you keep your original!
<p>With the <code>-noshading</code> flag, the background of generated PDF pages
will not be shaded.
<p>With the <code>-lastview</code> flag, only the last view of each Ipe page
will be created in PDF or Postscript format. This is often convenient
to make handouts for slides.
<h4><a name="id3">ipetopng: converting to a bitmap</a></h4>
<p>The auxiliary program <em>ipetopng</em> converts a page of the document
to a bitmap in PNG format. (Of course the result contains no Ipe
markup, so make sure you keep your original.) For instance, the
following command line
<pre>
ipetopng 3 150.0 presentation.pdf pres3.png
</pre>
converts page 3 of the Ipe document <code>presentation.pdf</code> to a
bitmap, with resolution <i>150.0</i> pixels per inch.
<h4><a name="id4">figtoipe: Importing FIG figures</a></h4>
<p>The auxiliary program <em>figtoipe</em> converts a figure in FIG format
into an Ipe XML-file. This is useful if you used to make figures with
Xfig before discovering Ipe, of if your co-authors made figures for
your article with Xfig (converting them will have the added benefit of
forcing your co-authors to learn to use Ipe). Finally, there are
quite a number of programs that can export to FIG format, and
<em>figtoipe</em> effectively turns that into the possibility of
exporting to Ipe.
<p>However, <em>figtoipe</em> is not quite complete. Most seriously, no
attempt is made to represent FIG splines, FIG arc-boxes, and embedded
images in FIG files. The drawing models of FIG and Ipe are also
somewhat different, which makes it impossible to properly render some
FIG files in Ipe. Ipe does not support depth ordering independent of
grouping, pattern fill, and Postscript fonts. You may therefore have
to edit the file after conversion.
<h4><a name="id5">pdftoipe: Importing Postscript and PDF</a></h4>
<p>You can convert arbitrary Postscript or PDF files into Ipe documents,
making them editable. The auxiliary program <em>pdftoipe</em> converts
(pages from) a PDF file into an Ipe XML-file. (If your source is
Postscript, you have to first convert it to PDF using Acrobat
Distiller or <i>ps2pdf</i>.) Once converted to XML, the file can be
opened from Ipe as usual.
<p>The conversion process should handle any graphics in the PDF file
fine, but doesn't do very well on text--Ipe's text model is just too
different.
<p>Note that <em>pdftoipe</em> is not part of the Ipe source
distribution. You can download and build it separately.
<h4><a name="id6">environment variables</a></h4>
<p>Ipe, <em>ipetoipe</em>, and <em>ipetopng</em> respect the following
environment variables:
<dl><dt><b>IPELATEXDIR</b><dd> the directory where Ipe runs Pdflatex.
<dt><b>IPEPDFLATEX</b><dd> the name of the Pdflatex executable. If Pdflatex
is on your path, the value <em>pdflatex</em> is sufficient.
<dt><b>IPEDOCDIR</b><dd> the directory containing the Ipe documentation.
<dt><b>IPELANGDIR</b><dd> the directory containing user interface localization
for Ipe. (No such localization exists yet.)
<dt><b>IPEFONTMAP</b><dd> the complete path of the font map, describing where
Ipe can find the 14 standard PDF fonts.
<dt><b>IPEKEYSFILE</b><dd> the complete path of the XML file specifying the
standard Ipe key assignment. You don't normally need to set this
variable, as you can override the standard assignment using a file
in your home directory.
<dt><b>IPEBROWSER</b><dd> the name of the HTML browser to be used to
display the Ipe on-line manual.
<dt><b>IPELETPATH</b><dd> a list of directories where Ipe looks for
ipelets. Directories are separated by `:' on Unix, and by `;' on
Windows.
<dt><b>TEXINPUTS</b><dd> when running Pdflatex, Ipe prepends both the current
directory (where Ipe was started) as the directory containing the
current document to the <b>TEXINPUTS</b> environment variable.
</dl>
<hr />
<table width="100%" cellpadding=0 cellspacing=2><tr><td bgcolor="#99ccff"><a href="manual_4.html"><img border="0" alt="4 General Concepts" src="next.png"></a></td><td bgcolor="#99ccff"><a href="manual.html"><img border="0" alt="Top" src="up.png"></a></td><td bgcolor="#99ccff"><a href="manual_2.html"><img border="0" alt="2 About Ipe files" src="previous.png"></a></td><td align="center" bgcolor="#99ccff" width="100%"><b>3 Command line options, auxiliary programs, and environment variables</b></td></tr></table></body></html>
|
