File: pdfedit.xml

package info (click to toggle)
pdfedit 0.4.1-2
  • links: PTS, VCS
  • area: main
  • in suites: lenny
  • size: 15,032 kB
  • ctags: 21,708
  • sloc: cpp: 185,471; xml: 8,824; yacc: 1,178; ansic: 666; perl: 664; makefile: 636; sh: 371; lisp: 51
file content (126 lines) | stat: -rw-r--r-- 5,059 bytes parent folder | download
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
<part id="cmdline_part">
  <title>Command line</title>
  <para>
  </para>
 <chapter id="cmdline_description">
  <title>PDF Editor Commandline parameters</title>
  <para>
   You can specify any number of filenames as parameters on commandline.
   One window will be opened for each file specified.
   If no file is specified on commandline, editor will be loaded initially empty.
  </para>
  <para>
   Name of files can be mixed with options (parameter that begin with a dash).
   Invalid option on commandline will cause editor to abort with error message.
   Names of options are case sensitive.
  </para>
  <para>
   Options which require a parameter can be specified in "short form", like <parameter>-d1</parameter>
   or "long form", like <parameter>-d 1</parameter>, both of these mean option <option>-d</option> with
   parameter <parameter>1</parameter>.
  </para>
  <para>
   Use <option>-script</option>, <option>-eval</option> and <option>-run</option>
   options to run any script besides the init script.
   These parameters are run/evaluated in the order they are specified on commandline
   and may be specified multiple times.
   If these parameters are specified in GUI mode,
   they are used in each window opened on program start, in commandline mode (console mode)
   they are used after commandline init script.
   After these scripts finish execution, the editor terminates.
  </para>
  <sect1 id="opt__help">
   <title>Option <option>--help</option></title>
   <para>
    Print brief help about commandline options to STDOUT and exit
   </para>
  </sect1>
  <sect1 id="opt__version">
   <title>Option <option>--version</option></title>
   <para>
    Print version of editor to STDOUT and exit
   </para>
  </sect1>
  <sect1 id="opt_d">
   <title>Option <option>-d (n)</option></title>
   <para>
    Set verbosity of debugging messages reported by editor.
    Only messages below or equal level specified in parameter will be shown, default is debugging level 1.
    Also, any of symbolic constants defined below (case insensitive), or starting part of them may be given instead of
    corresponding number.
   <table frame="none" id="table_debug_levels">
    <title>Explanation of debugging levels</title>
    <tgroup cols="3"><tbody>
     <row><entry>0</entry><entry>PANIC</entry><entry>Critical errors</entry></row>
     <row><entry>1</entry><entry>CRITICAL</entry><entry>Critical errors, but at least the program can exit somewhat gracefully</entry></row>
     <row><entry>2</entry><entry>ERROR</entry><entry>Usual errors</entry></row>
     <row><entry>3</entry><entry>WARNING</entry><entry>Comments about some unusual behavior</entry></row>
     <row><entry>4</entry><entry>INFO</entry><entry>Information about some internal behavior</entry></row>
     <row><entry>5</entry><entry>DEBUG</entry><entry>Debugging messages</entry></row>
    </tbody></tgroup>
   </table>
    Setting this to -1 mean no debug messages will be shown at all, not even the most critical ones.
    Debugging messages are sent to STDERR.
   </para>
  </sect1>
  <sect1 id="opt_console">
   <title>Option <option>-console</option></title>
   <para>
    Run in commandline mode.
    No editor windows are opened and commandline init script is executed.
   </para>
  </sect1>
  <sect1 id="opt_script">
   <title>Option <option>-script (filename)</option></title>
   <para>
    Run script with given filename.
    Look for the script in script path.
    If not found, look for the script in current directory.
   </para>
  </sect1>
  <sect1 id="opt_run">
   <title>Option <option>-run (filename)</option></title>
   <para>
    Run script with given filename, but unlike <option>-script</option> option, script path is not searched.
   </para>
  </sect1>
  <sect1 id="opt_eval">
   <title>Option <option>-eval (code)</option></title>
   <para>
    Evaluate given script code
   </para>
  </sect1>
  <sect1 id="opt_s">
   <title>Option <option>-s (filename)</option></title>
   <para>
    This is just shortcut for <option>-console -script (filename)</option>
   </para>
  </sect1>
  <sect1 id="opt__">
   <title>Option <option>--</option></title>
   <para>
    Stop processing options. Any further parameters after this one are treated as filenames.
    This can be useful if you want to open file, that have name beginning with a dash.
   </para>
  </sect1>
 </chapter>

 <chapter id="cmdline_localization">
  <title>Localization</title>
  <para>
   PDF Editor is run in english language by default, but by setting environment variable <envar>LANG</envar> before launching
   the program, you can tell PDF Editor to look for specific language file. If the localization you requested is
   not available, english will be used instead.
  </para>
  <para>
   Aside default english, these localizations are available:
   <informaltable frame="none">
    <tgroup cols="2"><tbody>
     <row><entry>cs</entry><entry> - Czech</entry></row>
     <row><entry>sk</entry><entry> - Slovak</entry></row>
    </tbody></tgroup>
   </informaltable>
  </para>
 </chapter>

</part>