1OMEGA(1)                    General Commands Manual                   OMEGA(1)
2
3
4

NAME

6       omega, iniomega, viromega - extended unicode TeX
7

SYNOPSIS

9       omega [options] [& format ] [ file | \ commands ]
10

DESCRIPTION

12       Run  the  Omega  typesetter on file, usually creating file.dvi.  If the
13       file argument has no extension, ".tex" will be appended to it.  Instead
14       of a filename, a set of Omega commands can be given, the first of which
15       must start with a backslash.  With a &format argument Omega uses a dif‐
16       ferent set of precompiled commands, contained in format.fmt; it is usu‐
17       ally better to use the -fmt format option instead.
18
19       Omega is a version of the TeX program modified for  multilingual  type‐
20       setting.   It  uses  unicode,  and has additional primitives for (among
21       other things) bidirectional typesetting.
22
23       The iniomega and viromega commands are Omega's analogues to the  initex
24       and  virtex  commands.   In this installation, they are symlinks to the
25       omega executable.
26
27       Omega's command line options are similar to those of TeX.
28
29       Omega is experimental software.
30

OPTIONS

32       This version of Omega understands the following command line options.
33
34       --oft format
35              Use format as the name of the format to be used, instead of  the
36              name by which Omega was called or a %& line.
37
38       -halt-on-error
39              Exit with an error code when an error is encountered during pro‐
40              cessing.
41
42       --help Print help message and exit.
43
44       --ini  Be iniomega, for dumping formats; this is implicitly true if the
45              program is called as iniomega.
46
47       --interaction mode
48              Sets  the  interaction  mode.  The mode can be one of batchmode,
49              nonstopmode, scrollmode,  and  errorstopmode.   The  meaning  of
50              these modes is the same as that of the corresponding \commands.
51
52       --ipc  Send  DVI  output  to a socket as well as the usual output file.
53              Whether this option is available is the choice of the installer.
54
55       --ipc-start
56              As --ipc, and starts the  server  at  the  other  end  as  well.
57              Whether this option is available is the choice of the installer.
58
59       --kpathsea-debug bitmask
60              Sets  path  searching  debugging flags according to the bitmask.
61              See the Kpathsea manual for details.
62
63       --maketex fmt
64              Enable mktexfmt, where fmt must be one of tex or tfm.
65
66       --no-maketex fmt
67              Disable mktexfmt, where fmt must be one of tex or tfm.
68
69       --output-comment string
70              Use string for the DVI file comment instead of the date.
71
72       -output-directory directory
73              directory instead of the current directory.  Look up input files
74              in directory first, the along the normal search path.
75
76       --parse-first-line
77              If the first line of the main input file begins with %& parse it
78              to look for a dump name.
79
80       --progname name
81              Pretend to be program name.  This affects both the  format  used
82              and the search paths.
83
84       --recorder
85              Enable  the filename recorder.  This leaves a trace of the files
86              opened for input and output  in  a  file  with  extension  .ofl.
87              (This option is always on.)
88
89       --shell-escape
90              Enable  the \write18{command} construct.  The command can be any
91              Bourne shell command.  This construct is normally disallowed for
92              security reasons.
93
94       --version
95              Print version information and exit.
96

ENVIRONMENT

98       See  the  Kpathsearch  library documentation (the `Path specifications'
99       node) for precise details of how the environment  variables  are  used.
100       The kpsewhich utility can be used to query the values of the variables.
101
102       One  caveat:  In most Omega formats, you cannot use ~ in a filename you
103       give directly to Omega, because ~ is an active character, and hence  is
104       expanded,  not  taken as part of the filename.  Other programs, such as
105       Metafont, do not have this problem.
106
107       TEXMFOUTPUT
108              Normally, Omega puts its output files in the current  directory.
109              If  any  output file cannot be opened there, it tries to open it
110              in the directory specified in the environment variable TEXMFOUT‐
111              PUT.  There is no default value for that variable.  For example,
112              if you say tex paper and the current directory is not  writable,
113              if  TEXMFOUTPUT  has  the  value  /tmp, Omega attempts to create
114              /tmp/paper.log (and /tmp/paper.dvi, if any output is produced.)
115
116       TEXINPUTS
117              Search path for \input and \openin files.  This should  probably
118              start  with  ``.'',  so  that user files are found before system
119              files.  An empty path component will be replaced with the  paths
120              defined  in  the  texmf.cnf file.  For example, set TEXINPUTS to
121              ".:/home/usr/tex:"  to  prepend   the   current   direcory   and
122              ``/home/user/tex'' to the standard search path.
123
124       TEXEDIT
125              Command  template for switching to editor.  The default, usually
126              vi, is set when Omega is compiled.
127

FILES

129       The location of the files mentioned below varies from system to system.
130       Use the kpsewhich utility to find their locations.
131
132       omega.pool
133              Encoded text of Omega's messages.
134
135       *.oft  Predigested Omega format (.oft) files.
136

NOTES

138       This  manual page is not meant to be exhaustive.  The complete documen‐
139       tation for this version of Omega can be found in the info manual Web2C:
140       A TeX implementation.
141

BUGS

143       This  version  of Omega implements a number of optional extensions.  In
144       fact, many of these extensions conflict to a greater or  lesser  extent
145       with  the  definition  of Omega.  When such extensions are enabled, the
146       banner printed when Omega starts is changed to print Omegak instead  of
147       Omega.
148
149       This version of Omega fails to trap arithmetic overflow when dimensions
150       are added or subtracted.  Cases where this occurs are rare, but when it
151       does the generated DVI file will be invalid.
152
153       The  DVI  files  produced  by  Omega may use extensions which make them
154       incompatible with most software designed to handle DVI files.  In order
155       to  print  or  preview  them, you should use odvips to generate a Post‐
156       Script file.
157
158       Omega is experimental software, and if you are an  active  user  it  is
159       strongly  recommended  that  you  subscribe  to the Omega mailing list.
160       Visit the Omega website http://omega.cse.unsw.edu.au for information on
161       how to subscribe.
162

SEE ALSO

164       tex(1), mf(1), odvips(1),
165

AUTHORS

167       The primary authors of Omega are John Plaice and Yannis Haralambous.
168
169
170
171Web2C 7.5.6                    27 December 1997                       OMEGA(1)
Impressum