{
    "mode": "info",
    "parameter": "xdvi",
    "section": "",
    "url": "https://www.chedong.com/phpMan.php/info/xdvi/json",
    "generated": "2026-08-02T06:59:12Z",
    "synopsis": "xdvi  [+[page]] [--help] [-allowshell] [-altfont font] [-anchorposition\nanchor] [-bg color] [-browser WWWbrowser] [-copy] [-cr  color]  [-debug\nbitmask|string[,string ...]]  [-display host:display] [-dvipspath path]\n[-editor command] [-expert] [-expertmode flag] [-fg color] [-findstring\nstring]  [-font  font]  [-fullscreen  ] [-gamma g] [-geometry geometry]\n[-gsalpha]  [-gspalette  palette]  [-h]  [-help]  [-hl  color]  [-hush]\n[-hushbell]  [-hushchars] [-hushchecksums] [-hushstdout] [-icongeometry\ngeometry]  [-iconic]  [-install]  [-interpreter  path]   [-keep]   [-l]\n[-license]  [-linkcolor  color]  [-linkstyle  0|1|2|3] [-margins dimen]\n[-mfmode mode-def[:dpi]] [-mgs[n] size] [-mousemode  0|1|2]  [-nocolor]\n[-nofork]    [-noghostscript]   [-nogrey]   [-nogssafer]   [-noinstall]\n[-nomakepk]  [-nomatchinverted]  [-noomega]   [-noscan]   [-notempfile]\n[-notype1fonts]  [-noxi2scrolling] [-offsets dimen] [-p pixels] [-paper\npapertype] [-pause] [-pausespecial special-string]  [-postscript  flag]\n[-rulecolor color] [-rv] [-S density] [-s shrink] [-safer] [-sidemargin\ndimen] [-sourceposition  line[:col][ ]filename]  [-statusline]  [-text-\nencoding  encoding] [-thorough] [-topmargin dimen] [-unique] [-version]\n[-visitedlinkcolor color] [-warnspecials] [-watchfile secs] [-wheelunit\npixels] [-xoffset dimen] [-yoffset dimen] [dvifile]",
    "sections": {
        "NAME": {
            "content": "xdvi - DVI Previewer for the X Window System\n",
            "subsections": []
        },
        "SYNOPSIS": {
            "content": "xdvi  [+[page]] [--help] [-allowshell] [-altfont font] [-anchorposition\nanchor] [-bg color] [-browser WWWbrowser] [-copy] [-cr  color]  [-debug\nbitmask|string[,string ...]]  [-display host:display] [-dvipspath path]\n[-editor command] [-expert] [-expertmode flag] [-fg color] [-findstring\nstring]  [-font  font]  [-fullscreen  ] [-gamma g] [-geometry geometry]\n[-gsalpha]  [-gspalette  palette]  [-h]  [-help]  [-hl  color]  [-hush]\n[-hushbell]  [-hushchars] [-hushchecksums] [-hushstdout] [-icongeometry\ngeometry]  [-iconic]  [-install]  [-interpreter  path]   [-keep]   [-l]\n[-license]  [-linkcolor  color]  [-linkstyle  0|1|2|3] [-margins dimen]\n[-mfmode mode-def[:dpi]] [-mgs[n] size] [-mousemode  0|1|2]  [-nocolor]\n[-nofork]    [-noghostscript]   [-nogrey]   [-nogssafer]   [-noinstall]\n[-nomakepk]  [-nomatchinverted]  [-noomega]   [-noscan]   [-notempfile]\n[-notype1fonts]  [-noxi2scrolling] [-offsets dimen] [-p pixels] [-paper\npapertype] [-pause] [-pausespecial special-string]  [-postscript  flag]\n[-rulecolor color] [-rv] [-S density] [-s shrink] [-safer] [-sidemargin\ndimen] [-sourceposition  line[:col][ ]filename]  [-statusline]  [-text-\nencoding  encoding] [-thorough] [-topmargin dimen] [-unique] [-version]\n[-visitedlinkcolor color] [-warnspecials] [-watchfile secs] [-wheelunit\npixels] [-xoffset dimen] [-yoffset dimen] [dvifile]\n",
            "subsections": []
        },
        "DESCRIPTION": {
            "content": "Xdvi  is  a  program  for previewing dvi files, as produced e.g. by the\ntex(1) program, under the X window system.\n\nXdvi can show the file shrunken by various integer factors, and it  has\na  ``magnifying glass'' for viewing parts of the page enlarged (see the\nsection MAGNIFIER below). This version of xdvi is also referred  to  as\nxdvik  since  it  uses the kpathsea library to locate and generate font\nfiles.  In addition to that, it supports the following features:\n\n- hyperlinks in DVI files (section HYPERLINKS),\n\n- direct rendering of PostScript<tm> Type 1  fonts  (section  TYPE  1\nFONTS),\n\n- source specials in the DVI file (section SOURCE SPECIALS),\n\n- string search in DVI files (section STRING SEARCH),\n\n- saving  or  printing (parts of) the DVI file (sections PRINT DIALOG\nand SAVE DIALOG).\n\nXdvi can be compiled with the Motif toolkit or the Xaw (Athena) toolkit\n(and  variants  of  it), and the Motif version has a slightly different\nGUI; these differences are noted below.\n\nBefore displaying a page of a DVI file, xdvi will check to see  if  the\nfile  has changed since the last time it was displayed.  If this is the\ncase, it will reload the file.  This feature allows you to preview many\nversions of the same file while running xdvi only once. Since it cannot\nread partial DVI files, xdvik versions starting from 22.74.3 will  cre-\nate  a  temporary copy of the DVI file being viewed, to ensure that the\nfile can be viewed without interruptions. (The -notempfile can be  used\nto turn off this feature).\n\nXdvi can show PostScript<tm> specials by any of three methods.  It will\ntry first to use Display PostScript<tm>, then NeWS, then it will try to\nuse  Ghostscript  to render the images.  All of these options depend on\nadditional software to work properly; moreover, some of them may not be\ncompiled into this copy of xdvi.\n\nFor  performance  reasons,  xdvi does not render PostScript specials in\nthe magnifying glass.\n\nIf no file name has been specified on the command line, xdvi  will  try\nto  open the most recently opened file; if the file history (accessible\nvia the File > Open Recent menu) is empty, or if none of the  files  in\nthe  history  are  valid  DVI files, it will pop up a file selector for\nchoosing a file name.  (In previous versions, which didn't have a  file\nhistory,  the file selector was always used; you can set the X resource\nnoFileArgUseHistory to false to get back the old behaviour.)\n",
            "subsections": []
        },
        "OPTIONS": {
            "content": "In addition to specifying the dvi file (with or without the .dvi exten-\nsion), xdvi supports the following command line options.  If the option\nbegins with a `+' instead of a `-', the option is restored to  its  de-\nfault  value.   By  default,  these options can be set via the resource\nnames given in parentheses in the description of each option.\n\n+page  Specifies the first page to show.  If + is given without a  num-\nber, the last page is assumed; the first page is the default.\n",
            "subsections": [
                {
                    "name": "-allowshell",
                    "content": "(.allowShell) This option enables the shell escape in PostScript\nspecials.  (For security reasons, shell escapes are disabled  by\ndefault.)   This  option should be rarely used; in particular it\nshould not be used just to uncompress files:  that  function  is\ndone  automatically  if  the file name ends in .Z, .gz, or .bz2.\nShell escapes are always turned off  if  the  -safer  option  is\nused.\n\n-altfont font\n(.altFont)  Declares  a default font to use when the font in the\ndvi file cannot be found.  This is  useful,  for  example,  with\nPostScript <tm> fonts.\n\n-anchorposition anchor\nJump  to  anchor after opening the DVI file. This is only useful\nwhen invoking xdvi from other applications.\n\n-background color\n(.background) Determines the color of the background.   Same  as\n-bg.\n\n-bg color\n(.background) Determines the color of the background.\n\n-browser browser\n(.wwwBrowser) Defines the web browser used for handling external\nURLs. The value of this option or resource has the  same  syntax\nas the BROWSER environment variable; see the explanation of that\nvariable in the section `ENVIRONMENT' below for a  detailed  de-\nscription.   If neither the option nor the X resource wwwBrowser\nis specified, the environment variables BROWSER  and  WWWBROWSER\n(in  that  order)  are used to determine the browser command. If\nthese are not set either, the following default value  is  used:\nxdg-open %s:htmlview %s:firefox -remote -remote \"openURL(%s,new-\nwindow)\":mozilla    -remote    \"openURL(%s,new-window)\":netscape\n-raise -remote \"openURL(%s,new-window)\":xterm -e w3m %s:xterm -e\nlynx %s:xterm -e wget %s\n\n-copy  (.copy) Always use the copy operation when writing characters to\nthe display.  This option may be necessary for correct operation\non a color display, but overstrike characters will be incorrect.\nIf  greyscale  anti-aliasing is in use, the -copy operation will\ndisable the use of colorplanes and make overstrikes come out in-\ncorrectly.  See also -thorough.\n\n-cr color\n(.cursorColor)  Determines  the  color of the mouse cursor.  The\ndefault is the same as the foreground color.\n\n-debug bitmask|string[,string ...]\n(.debugLevel) If nonzero, prints additional information on stan-\ndard  output.  The argument can be either a bitmask specified as\na decimal number, or comma-separated list of strings.\nFor the bitmask representation, multiple values can be specified\nby  adding  the numbers that represent the individual bits; e.g.\nto debug all file searching and opening commands,  use  4032  (=\n2048 + 1024 + 512 + 256 + 128 + 64). Use -1 to turn on debugging\nof everything (this will produce huge output).\nFor the string representation, use the  strings  listed  in  the\nfollowing  table,  with  a comma to separate the values; e.g. to\ndebug all file searching and opening  commands,  use  search,ex-\npand,paths,hash,stat,open.   (The  option `kpathsea' is provided\nas a shorthand for these.)  Note that such a list may need to be\nquoted  to  prevent the shell from interpreting commas or spaces\nin the list.\nThe individual numbers and strings have the following meanings:\n\n1       bitmap      Bitmap creation\n2       dvi         DVI translation\n4       pk          PK fonts\n8       batch       Batch mode: Exit after\nreading the DVI file\n16      event       Event handling\n32      ps          PostScript interpreter calls\n64      stat        Kpathsea stat(2) calls\n128     hash        Kpathsea hash table lookups\n256     open        Kpathsea file opening\n512     paths       Kpathsea path definitions\n1024    expand      Kpathsea path expansion\n2048    search      Kpathsea searching\n4032    kpathsea    All Kpathsea options\n4096    htex        Hypertex specials\n8192    src         Source specials\n16384   client      Client/server mode (see -unique\nand -sourceposition options)\n32768   ft          FreeType library messages (Type 1 fonts)\n65536   ftverbose  Verbose FreeType library messages (currently unused)\n131072  gui         GUI elements\n\nSome of the Kpathsea debugging options are actually provided  by\nKpathsea;  see  the Debugging section in the Kpathsea manual for\nmore information on these.\n\n-density density\n(.densityPercent) Determines the  density  used  when  shrinking\nbitmaps for fonts.  A higher value produces a lighter font.  The\ndefault value is 40.  If greyscaling is in  use,  this  argument\ndoes not apply; use -gamma instead.  See also the `S' keystroke.\nSame as -S.\n\n-display host:display\nSpecifies the host and screen to be used for displaying the  dvi\nfile.  By default this is obtained from the environment variable\nDISPLAY.\n\n-dvipspath path\n(.dvipsPath) Use path as the dvips program to use when printing.\nThe  default  for  this  is dvips.  The program or script should\nread the DVI file from standard input, and write the  PostScript\nfile to standard output.\n\n-editor editor\n(.editor)  Specifies  the  editor  that will be invoked when the\nsource-special() action is triggered to start a  reverse  search\n(by default via Ctrl-Mouse 1).  The argument to this option is a\nformat string in which occurrences of ``%f'' are replaced by the\nfile name, occurrences of ``%l'' are replaced by the line number\nwithin the file, and optional occurrences of ``%c'' are replaced\nby the column number within the line.\n\nIf  neither  the option nor the X resource .editor is specified,\nthe following environment variables are checked to determine the\neditor  command: XEDITOR, VISUAL, and EDITOR (in this sequence).\nIf the string is found as the value of the VISUAL or EDITOR  en-\nvironment  variables,  then  ``xterm  -e  '' is prepended to the\nstring; if the editor is specified by other means, then it  must\nbe  in the form of a shell command to pop up an X window with an\neditor in it. If none of these variables is set, a warning  mes-\nsage  is  displayed  and  the  command ``xterm -e vi +%l %f'' is\nused.\n\nIf no ``%f'' or ``%l'' occurs in the string, the missing  format\nstrings  are appended automatically.  (This is for compatibility\nwith other programs when using  one  of  the  environment  vari-\nables).\n\nA  new  instance of the editor is started each time this command\nis used; therefore it is preferable to use an editor that can be\ninvoked  in  `client'  mode  to load new files into the same in-\nstance. Example settings are:\n\nemacsclient --no-wait\n(older Emacsen)\n\ngnuclient -q\n(XEmacs and newer Emacsen)\n\ngvim --servername xdvi --remote\n(VIM v6.0+; the `--servername  xdvi'  option  will  cause\ngvim  to run a dedicated instance for the files opened by\nxdvi.)\n\nnc     (nedit)\n\nNote that those strings need to be enclosed into quotes when us-\ning  them  on  the  command-line to protect them from the shell;\nwhen using them as argument for the .editor resource in an X re-\nsource file, no quotes should be used.\n\nNOTE  ON SECURITY: The argument of this option isn't executed as\na shell command, but via exec() to prevent evil tricks with  the\ncontents of source specials.\n"
                },
                {
                    "name": "-expert",
                    "content": "This option is only supported for backwards compatibility; it is\nequivalent to -expertmode 0, which should be preferred.\n\n-expertmode flag\n(.expertMode) With an argument of 0, this  option  switches  off\nthe  display  of the buttons, scrollbars, the toolbar (Motif on-\nly), the statusline and the page list. These  GUI  elements  can\nalso  be  (de)activated separately, by combining the appropriate\nvalues in the flag argument. This acts similar to the -debug op-\ntion:  The  integer  flag  is treated as a bitmap where each bit\nrepresents one element. If the bit has the value 1, the  element\nis  switched  on, if it has the value 0, the element is switched\noff. The meaning of the bits is as follows:\n\n1       statusline\n2       scrollbars\n4       Motif: pagelist, Xaw: buttons and pagelist\n8       toolbar (Motif only)\n16      menubar (Motif only)\n\nFor example, to turn on only the statusline and the  scrollbars,\nuse 3 (= 1 + 2).  See also the `x' keystroke, where the bits are\naddressed by their positions, from 1 to 3 (Xaw)  or  5  (Motif),\nrespectively.\n\nIf  the  statusline  is not active, all messages that would normally be\nprinted to the statusline will be printed to stdout, unless the  -hush-\nstdout option is used.\n\n-fg color\n(.foreground) Determines the color of the text (foreground).\n\n-findstring string\nThis  option  triggers  a search for string in the DVI file men-\ntioned on the command-line, similar to forward search  (see  the\ndescription  of  the sourceposition option): If there is already\nanother instance of xdvi running  on  the  displaying  that  DVI\nfile, it will cause that instance to perform the search instead.\nThe search starts at the top of the  current  page  of  the  DVI\nfile.\n\n-font font\n(*font)  Sets the font used in menus, buttons etc., as described\nin the X(7x) man page. The font for child  windows  can  be  set\nseparately, e.g.:\n\nxdvi*statusline*font: \\\n-*-helvetica-medium-r-*-*-12-*-*-*-*-*-*-*\n\n-foreground color\nSame as -fg.\n"
                },
                {
                    "name": "-fullscreen",
                    "content": "When  this  option is used, xdvi will (try to) run in fullscreen\nmode, with no window decorations.  This option is not guaranteed\nto work with all windowmanagers/desktops; if you're experiencing\nproblems with it, please use the -geometry option instead, and a\nsuitable  window  manager  setting  to remove the window decora-\ntions.  When using this option for presentations, you might want\nto  get  rid  of all the control widgets as well, using the -ex-\npertmode option. This option can also be toggled at runtime  us-\ning the fullscreen action (by default bound to Ctrl-l).\n\n-gamma gamma\n(.gamma)  Controls  the interpolation of colors in the greyscale\nanti-aliasing color palette.  Default value is  1.0.   For  0  <\ngamma < 1, the fonts will be lighter (more like the background),\nand for gamma > 1, the fonts will be darker (more like the fore-\nground).  Negative values behave the same way, but use a slight-\nly different algorithm.  For color and grayscale  displays;  for\nmonochrome, see -density.  See also the `S' keystroke.\n\n-geometry geometry\n(.geometry)  Specifies  the initial geometry of the main window,\nas described in the X(7x) man page. The geometry of  child  win-\ndows can be set separately, e.g.:\nxdvi*helpwindow.geometry: 600x800\n"
                },
                {
                    "name": "-gsalpha",
                    "content": "(.gsAlpha)  Causes  Ghostscript  to  be called with the x11alpha\ndriver instead of the x11 driver.  The x11alpha  driver  enables\nanti-aliasing  in  PostScript  specials, for a nicer appearance.\nIt is available on newer versions of Ghostscript.   This  option\ncan also be toggled with the `V' keystroke.\n\n-gspalette palette\n(.palette)  Specifies  the  palette to be used when using Ghost-\nscript for rendering PostScript specials.  Possible  values  are\nColor, Greyscale, and Monochrome.  The default is Color.\n"
                },
                {
                    "name": "-h, -help, --help",
                    "content": "Prints  a  short  help text with an overview of the command-line\noptions to standard output.\n\n-hl color\n(.highlight) Determines the color of the  page  border,  of  the\nruler  in  `ruler mode', and of the highlighting markers in for-\nward search and string search.  The default  is  the  foreground\ncolor.\n\n-hush  (.Hush) Causes xdvi to suppress all suppressible warnings.\n",
                    "flag": "-h",
                    "long": "--help"
                },
                {
                    "name": "-hushbell",
                    "content": "(.hushBell) Don't sound the X bell when an error occurs.\n"
                },
                {
                    "name": "-hushchars",
                    "content": "(.hushLostChars)  Causes  xdvi to suppress warnings about refer-\nences to characters which are not defined in the font.\n"
                },
                {
                    "name": "-hushchecksums",
                    "content": "(.hushChecksums) Causes xdvi to suppress warnings about checksum\nmismatches between the dvi file and the font file.\n"
                },
                {
                    "name": "-hushstdout",
                    "content": "(.hushStdout)  Suppresses printing of status messages to stdout.\nNote that errors or warnings will still  be  printed  to  stderr\neven if this option is used.\n\n-icongeometry geometry\n(.iconGeometry) Specifies the initial position for the icon.\n"
                },
                {
                    "name": "-iconic",
                    "content": "(.iconic)  Causes  the xdvi window to start in the iconic state.\nThe default is to start with the window open.\n"
                },
                {
                    "name": "-install",
                    "content": "(.install) If xdvi is running under a PseudoColor  visual,  then\n(by  default) it will check for TrueColor visuals with more bits\nper pixel, and switch to such a visual if  one  exists.   If  no\nsuch visual exists, it will use the current visual and colormap.\nIf -install is selected, however, it will still use a  TrueColor\nvisual  with a greater depth, if one is available; otherwise, it\nwill install its own colormap on the  current  visual.   If  the\ncurrent visual is not PseudoColor, then xdvi will not switch the\nvisual or colormap, regardless of its options.  The default val-\nue  of  the install resource is the special value, maybe.  There\nis no +install option.  See also -noinstall, and the GREYSCALING\nAND COLORMAPS section.\n\n-interpreter filename\n(.interpreter)  Use filename as the Ghostscript interpreter.  By\ndefault it uses gs.\n\n-keep  (.keepPosition) Sets a flag to indicate  that  xdvi  should  not\nmove  to  the home position when moving to a new page.  See also\nthe `k' keystroke. This flag is honored by  all  page  switching\nactions  and  by up-or-previous() / down-or-next(), although the\nlatter only honor the horizontal position, not the vertical one.\nThis allows for a \"continuous\" scrolling back an forth through a\ndocument with a display window narrower than a page width.\n\n-l     (.listFonts) List the names of all fonts used.\n"
                },
                {
                    "name": "-license",
                    "content": "Prints licensing information.\n"
                },
                {
                    "name": "-linkcolor",
                    "content": "(.linkColor) Color used for unvisited hyperlinks (`Blue2' by de-\nfault).  Hyperlinks  are  unvisited before you click on them, or\nafter the DVI file has been reloaded.  The value should  be  ei-\nther a valid X color name (such as DarkGoldenrod4) or a hexadec-\nimal color string (such as #8b6508).  See also -visitedlinkcolor\nand -linkstyle.\n"
                },
                {
                    "name": "-linkstyle",
                    "content": "(.LinkStyle)  Determines  the style in which hyperlinks are dis-\nplayed. Possible values and their meanings are:\n\n0       No highlighting of links\n1       Underline links with link color\n2       No underlining, color text with link color\n3       Underline and display text colored with\nlink color\n\nThe values for link color are specified by the options/resources\n-linkcolor and -visitedlinkcolor (which see).\n\n-margins dimen\n(.Margin)  Specifies  the  size  of both the top margin and side\nmargin.  This determines the ``home'' position of the page with-\nin  the  window as follows.  If the entire page fits in the win-\ndow, then the margin settings are ignored.  If, even  after  re-\nmoving  the  margins  from the left, right, top, and bottom, the\npage still cannot fit in the window, then the page is put in the\nwindow  such  that the top and left margins are hidden, and pre-\nsumably the upper left-hand corner of the text on the page  will\nbe  in the upper left-hand corner of the window.  Otherwise, the\ntext is centered in the window.  The dimension should be a deci-\nmal number optionally followed by any of the two-letter abbrevi-\nations for units accepted by TeX (pt, pc, in, bp,  cm,  mm,  dd,\ncc, or sp).  By default, the unit will be cm (centimeters).  See\nalso -sidemargin, -topmargin, and the keystroke `M.'\n\n-mfmode mode-def\n(.mfMode) Specifies a mode-def string,  which  can  be  used  in\nsearching  for  fonts (see ENVIRONMENT, below).  Generally, when\nchanging the mode-def, it is also necessary to change  the  font\nsize  to  the  appropriate value for that mode.  This is done by\nadding a colon and the value in dots per inch; for example, -mf-\nmode  ljfour:600.   This method overrides any value given by the\npixelsPerInch resource or the  -p  command-line  argument.   The\nmetafont  mode  is also passed to metafont during automatic cre-\nation of fonts.  By default, it is unspecified.\n\n-mgs size\nSame as -mgs1.\n\n-mgs[n] size\n(.magnifierSize[n]) Specifies the size of the window to be  used\nfor the ``magnifying glass'' for Button n.  The size may be giv-\nen as an integer (indicating that the magnifying glass is to  be\nsquare),  or  it may be given in the form widthxheight.  See the\nMOUSE ACTIONS section.  Defaults are 200x150, 400x250,  700x500,\n1000x800, and 1200x1200.\n"
                },
                {
                    "name": "-mousemode [0|1|2]",
                    "content": "(.mouseMode) Specifies the default mode of xdvi at startup: Mag-\nnifier (0), Text Selection Mode (1) or Ruler Mode (2).  See  the\nsection MODES, below, for more information.\n"
                },
                {
                    "name": "-nocolor",
                    "content": "(.color)  Turns  off the use of color specials.  This option can\nbe toggled with the `C' keystroke.  (Note: -nocolor  corresponds\nto color:off; +nocolor to color:on.)\n"
                },
                {
                    "name": "-nofork",
                    "content": "(.fork)  With  the  -sourceposition and -unique options, the de-\nfault behavior is for xdvi to put  itself  into  the  background\n(like  a daemon) if there is no appropriate instance of xdvi al-\nready running.  This argument makes it run in the foreground in-\nstead.  This is useful for debugging, or if your client applica-\ntion cannot deal well with a program  self-backgrounding  itself\nin this way -- e.g. the IPC functions in emacs are known to have\nproblems with this.  If no -sourceposition or  -unique  argument\nis given, then this option has no effect.  (Note: -nofork corre-\nsponds to fork:off; +nofork to fork:on.)\n"
                },
                {
                    "name": "-noghostscript",
                    "content": "(.ghostscript) Inhibits the use of  Ghostscript  for  displaying\nPostScript<tm>  specials.   (Note: -noghostscript corresponds to\nghostscript:off; +noghostscript to ghostscript:on.)\n"
                },
                {
                    "name": "-nogrey",
                    "content": "(.grey) Turns off the use of greyscale anti-aliasing when print-\ning  shrunken  bitmaps.  (Note: -nogrey corresponds to grey:off;\n+nogrey to grey:on.)  See also the `G' keystroke.\n"
                },
                {
                    "name": "-nogssafer",
                    "content": "(.gsSafer) Normally, if Ghostscript is used to render PostScript\nspecials,  the  Ghostscript  interpreter  is run with the option\n-dSAFER.   The  -nogssafer  option  runs   Ghostscript   without\n-dSAFER.   The -dSAFER option in Ghostscript disables PostScript\noperators such as  deletefile,  to  prevent  possibly  malicious\nPostScript  programs  from having any effect.  If the -safer op-\ntion is specified, then this option has no effect; in that  case\nGhostscript  is always run with -dSAFER.  (Note: -nogssafer cor-\nresponds to gsSafer:off; +nogssafer to gsSafer:on.)\n"
                },
                {
                    "name": "-noinstall",
                    "content": "(.install) Inhibit the default behavior of switching to a  True-\nColor  visual  if one is available with more bits per pixel than\nthe current visual.  (Note: -noinstall corresponds  install:off;\nthere  is  no  +noinstall  option.)   See also -install, and the\nGREYSCALING AND COLORMAPS section.\n"
                },
                {
                    "name": "-nomakepk",
                    "content": "(.makePk) Turns off automatic generation of font files that can-\nnot  be  found  by other means.  (Note: -nomakepk corresponds to\nmakePk:off; +nomakepk to makePK:on.)\n"
                },
                {
                    "name": "-nomatchinverted",
                    "content": "(.matchInverted) Don't highlight string search  matches  in  in-\nverted  color; instead, draw a rectangle in highlight color (see\nthe -hl option) around the match. This option is activated auto-\nmatically  if  the  display  isn't running in TrueColor.  (Note:\n-nomatchinverted corresponds to  matchInverted:off;  +nomatchin-\nverted to matchInverted:on.)\n"
                },
                {
                    "name": "-noomega",
                    "content": "(.omega)  This will disable the use of Omega extensions when in-\nterpreting DVI files.  By default, the  additional  opcodes  129\nand  134  are  recognized by xdvi as Omega extensions and inter-\npreted as requests to set 2-byte characters. The  only  drawback\nis  that the virtual font array will require 65536 positions in-\nstead of the default 256 positions, i.e. the memory requirements\nof  xdvi  will be slightly larger. If you find this unacceptable\nor encounter another problem with the Omega extensions, you  can\nswitch  this extension off by using -noomega (but please do send\na bug report if you find such problems - see the bug address  in\nthe AUTHORS section below).\n(Note:  -noomega  corresponds  to omega: off; +noomega to omega:\non.)\n"
                },
                {
                    "name": "-noscan",
                    "content": "(.prescan) By default, xdvi does a preliminary scan of  the  dvi\nfile  to  process any papersize specials; this is especially im-\nportant at startup since the paper size may be needed to  deter-\nmine  the  window size.  If PostScript<tm> is in use, then pres-\ncanning is also necessary in order to  properly  process  header\nfiles.   In  addition, prescanning is needed to correctly deter-\nmine the background color of a page.  This option turns off such\nprescanning.   (Prescanning will be automatically be turned back\non if xdvi detects any of the specials mentioned above.)  (Note:\n-noscan corresponds to prescan:off; +noscan to prescan:on.)\n"
                },
                {
                    "name": "-notempfile",
                    "content": "(.tempFile)  As mentioned in the section DESCRIPTION above, xdvi\nwill create a temporary copy of the DVI file so that it  can  be\naccessed  without  interruptions  even  while  the file is being\nrewritten by TeX.  Since this introduces the overhead of copying\nthe  file  every time it has changed, the -notempfile allows you\nto turn off this behaviour. In this case, exposing parts of  the\nwindow while the DVI file is being written by TeX will erase the\ncurrent window contents until the DVI  file  can  be  completely\nreread.\n(Note:  -notempfile  corresponds to tempFile:off; +notempfile to\ntempFile:on.)\n"
                },
                {
                    "name": "-notype1fonts",
                    "content": "(.type1) This will disable the use of the  FreeType  library  to\ndisplay PostScript<tm> Type 1 fonts.  Use this option as a work-\naround when you encounter problems with the display  of  Type  1\nfonts  (but  please  don't  forget  to send a bug report in this\ncase, to the URL mentioned in the section AUTHORS below).\n(Note: -notype1fonts corresponds to type1:off; +notype1fonts  to\ntype1:on.)\n"
                },
                {
                    "name": "-noxi2scrolling",
                    "content": "(.xi2Scrolling)  This  will  disable  the use of high-resolution\nscrolling using the XInput 2.1 features of the X  Server.   When\nenabled,  horizontal  and  vertical scrolling is done in smaller\nincrements than would correspond to a single click  of  a  mouse\nwheel.   This  is  only available for hardware that supports the\nfeature, generally touchpads.  It is not  available  for  tradi-\ntional  wheel  mice.   If suitable hardware is not present or if\nthe X server does not support XInput 2.1  or  higher,  then  the\nhigh-resolution  scrolling  feature is turned off and has no ef-\nfect.\n(Note:   -noxi2scrolling   corresponds   to    xi2Scrolling:off;\n+noxi2scrolling, to xi2Scrolling:on.)\n\n-offsets dimen\n(.Offset) Specifies the size of both the horizontal and vertical\noffsets of the output on the page.  By decree  of  the  Stanford\nTeX  Project,  the default TeX page origin is always 1 inch over\nand down from the top-left page corner, even  when  non-American\npaper  sizes  are  used.  Therefore, the default offsets are 1.0\ninch.  The argument dimen should be a decimal number  optionally\nfollowed  by  any  of the two-letter abbreviations for units ac-\ncepted by TeX (pt, pc, in, bp, cm, mm, dd, cc, or sp).   By  de-\nfault, the unit will be cm (centimeters).  See also -xoffset and\n-yoffset.\n\n-p pixels\n(.pixelsPerInch) Defines the size of the fonts to use, in pixels\nper  inch.   The  default value is 600.  This option is provided\nonly for backwards compatibility; the preferred  way is  to  set\nboth the resolution and the Metafont mode via the -mfmode option\n(which see).\n\n-paper papertype\n(.paper) Specifies the size of the printed page.  Note  that  in\nmost  cases it's best to specify the paper size in the TeX input\nfile via the line\n\n\\usepackage[dvips]{geometry}\n\nwhich will be recognized by both dvips and xdvi;  in  that  case\nthe use of a `-paper' option should be unnecessary.\nThe paper size may be specified in the form widthxheight option-\nally followed by a unit, where width and height are decimal num-\nbers giving the width and height of the paper, respectively, and\nthe unit is any of the two-letter abbreviations  for  units  ac-\ncepted  by  TeX (pt, pc, in, bp, cm, mm, dd, cc, or sp).  By de-\nfault, the unit is cm (centimeters).\nThere are also synonyms which may be used: us (8.5x11in),  legal\n(8.5x14in),  foolscap  (13.5x17in),  as  well  as  the ISO sizes\na1-a7, b1-b7, c1-c7.  Each of these also has a landscape or `ro-\ntated'  variant: usr (11x8.5in), a1r-a7r, etc. For compatibility\nwith dvips, the formats letter (8.5x11in), ledger (17x11in)  and\ntabloid  (11x17in)  are also supported (these don't have rotated\nvariants).\nAny of the above sizes may be preceded by  a  plus  sign  (`+');\nthis causes the paper size given here to override any paper size\ngiven in the dvi file.  The default paper size is 21 x  29.7  cm\n(A4 size).\n\n-pause (.pause)  This option provides a simple implementation of incre-\nmental (stepwise) display, which can be used for  presentations.\nWhen  this  option  is  used, xdvi will pause the display of the\ncurrent page whenever it  encounters  a  special  special-string\n(xdvi:pause  by default; the string can be customized via -paus-\nespecial, see below), and the cursor will change its shape.  The\naction  unpause-or-next()  (by  default  bound to the Space key)\nwill display the next portion of the page up  to  the  following\nspecial-string,  or  until the end of the page is reached.  When\nthe option is not used, specials containing special-string  will\nbe ignored.\n\n-pausespecial special-string\n(.pauseSpecial)  Sets  the  special  string  that causes xdvi to\npause when the -pause option is active.  The  default  value  of\nspecial-string is xdvi:pause.\n\n-postscript flag\n(.postscript)  If flag = 0, rendering of PostScript<tm> specials\nis disabled; instead,  bounding  boxes  will  be  displayed  (if\navailable).  A  value of 1 (the default) switches PostScript<tm>\nspecials on. With a value of 2, the PostScript<tm> specials  are\ndisplayed  along  with  their bounding boxes; this allows you to\nvisually check the correctness of the bounding boxes. The values\ncan  also  be  toggled at runtime with the `v' keystroke and the\ncorresponding numerical prefix arguments 0, 1 and 2.\n\n-ps2pdfpath path\n(.ps2pdfPath) Use path as a conversion program  from  PostScript\nto PDF. The program or script should accept two command-line ar-\nguments: The PostScript file as first argument, and the PDF out-\nput file as second argument.\n\n-rulecolor color\n(.ruleColor) Determines the color of the rules used for the mag-\nnifier (default: foreground color).\n\n-q     (.noInitFile) Ignore the $HOME/.xdvirc startup file (i.e.  don't\nread it at startup, and don't write it at exit). This forces the\ndefaults defined in $HOME/.Xdefaults to be used. See  FILES  for\nmore information on $HOME/.xdvirc.\n\n-rv    (.reverseVideo) Causes the page to be displayed with white char-\nacters on a black background, instead of vice versa.\n\n-S density\n(.densityPercent) Same as -density (which see).\n\n-s shrink\n(.shrinkFactor) Defines the initial shrink factor.  The  default\nvalue  is  8.   If shrink is given as 0, then the initial shrink\nfactor is computed so that the page fits within the  window  (as\nif the `s' keystroke were given without a number).\n\n-safer (.safer) This option turns on all available security options; it\nis designed for use when xdvi is called by a  browser  that  ob-\ntains  a dvi or TeX file from another site.  This option selects\n+nogssafer and +allowshell.\n\n-sidemargin dimen\n(.sideMargin) Specifies the side margin (see -margins).\n\n-sourceposition line[:col][ ]filename\nThis option makes xdvi search in the dvi file for the place cor-\nresponding  to  the  indicated line (and, optionally, column) in\nthe .tex source file, and highlight the place found by drawing a\nrectangle in the highlight color (see the -hl option) around the\ncorresponding text.  In addition, when run  with  this  argument\n(and  the -nofork option is not given, which see), xdvi will al-\nways return immediately:  if it finds another instance  of  xdvi\nalready  showing  dvifile,  then it will cause that instance to\nraise its window and move to the given place in  the  dvi  file;\notherwise  it  will start up its own instance in the background.\nIf several instances of xdvi are displaying the  respective  dvi\nfile,  the instance which was last raised to the foreground will\nbe used.\n\nThe space before filename is only needed if the filename  starts\nwith  a digit.  When the space is used, the argument needs to be\nenclosed in quotes to prevent the shell from misinterpreting the\nspace as argument separator.\n\nThis  option requires that dvifile be prepared with source spe-\ncial information.  See the section on SOURCE  SPECIALS  for  de-\ntails on how to do this.\n\nHere  is  a more detailed description of how the filename in the\n-sourceposition argument is matched with  the  filename  in  the\nsource specials:\n\n1. If  neither  of the filenames contains a path name component,\nthe filenames are compared ignoring the `.tex' extensions  in\nboth filenames.\n\n2. Otherwise, if one of the filenames does contain a path compo-\nnent (e.g.: ./test.tex, ../test.tex, /my/homedir/tex/test.tex\nor  any combination of these), both filenames are expanded to\na full path, with any occurrences of ../ and ./ expanded, and\nmultiple slashes removed.\nThe  pathname  in the -sourceposition is expanded relative to\nthe current working directory of the xdvi -sourceposition in-\nvocation,  and  the  pathnames in the source specials are ex-\npanded relative to the path of the  current  DVI  file  being\nviewed.\nThe  path  names are then compared ignoring the `.tex' exten-\nsions in both path names.\n"
                },
                {
                    "name": "-statusline",
                    "content": "(.statusline) This option is obsolete; use -expertmode  flag in-\nstead (which see).\n\n-text-encoding encoding\n(.textEncoding)  Use encoding as the text encoding of the string\nin the \"Find\" window. Usually, this should not be  needed  since\nthe encoding is determined from the locale settings.\n"
                },
                {
                    "name": "-thorough",
                    "content": "(.thorough)  Xdvi  will  usually  try  to ensure that overstrike\ncharacters (e.g. \\notin) are printed correctly.   On  monochrome\ndisplays,  this  is  always possible with one logical operation,\neither and or or.  On color displays, however, this may take two\noperations,  one  to  set  the appropriate bits and one to clear\nother bits.  If this is the case, then by default xdvi will  in-\nstead use the copy operation, which does not handle overstriking\ncorrectly.  The -thorough option chooses  the  slower  but  more\ncorrect choice.  See also -copy.\n\n-topmargin dimen\n(.topMargin)  Specifies  the  top  and bottom margins (see -mar-\ngins).\n"
                },
                {
                    "name": "-unique",
                    "content": "(.unique) This option will make another instance of xdvi running\non the same display act as a `server'.  For example, the invoca-\ntion\n\nxdvi -unique +5 file.dvi\n\nwill cause this other instance to load file.dvi  on  page  5  in\nplace  of  the file that it is currently displaying. If there is\nalready another instance of xdvi  already  displaying  the  file\nfile.dvi,  then  it  will just jump to page 5.  If the other in-\nstance of xdvi is displaying a  different  file,  it  will  load\nfile.dvi  instead.  Otherwise,  if  no other instance of xdvi is\ncurrently running on the display, this option instead  starts  a\nnew  instance  of xdvi in the background (unless the -nofork op-\ntion is specified, which see) displaying page 5 of file.dvi.\nThe filename and the +n option for the page number are the  only\noptions available for controlling a remote instance of xdvi like\nthis; all other options are currently ignored.\n"
                },
                {
                    "name": "-useTeXpages",
                    "content": "Use logical TeX pages (the values of the \\count0  register)  in-\nstead of physical pages for the pagelist labels and when jumping\nto a page in a document with the `g'  keystroke  (or  the  goto-\npage()  action).   This  option  can be toggled via the `T' key-\nstroke.\n"
                },
                {
                    "name": "-version",
                    "content": "Print information on the version of xdvi.\n"
                },
                {
                    "name": "-visitedlinkcolor",
                    "content": "(.visitedLinkColor) Color used for visited hyperlinks (`Purple4'\nby  default).  Hyperlinks become visited once you click on them.\nAs for linkColor, the value should be either  a  valid  X  color\nname or a hexadecimal color string.\n"
                },
                {
                    "name": "-warnspecials",
                    "content": "(.warnSpecials)  Causes  xdvi  to  print warnings about \\special\nstrings that it cannot process to  stderr.  These  warnings  are\nsuppressed by default.\n\n-watchfile n\n(.watchFile) If this option is set to a value larger than 0, xd-\nvi will check the DVI file for changes every n seconds.  If  the\nDVI file has been completely written by TeX, it will be reloaded\nautomatically.  Fractional values (e.g. `2.5') are possible. The\ndefault for this option is 0, i.e. no watching.\nSince  xdvi  cannot  handle  partial  DVI files, it tries not to\nreload the file while it is being rewritten.   However,  use  of\nthe magnifier or switching of pages requires reading (a part of)\nthe DVI file, and if the tempfile option is switched  off,  this\nwill erase the current contents of the window until the DVI file\ncan be read entirely.\n\n-wheelunit pixels\n(.wheelUnit) Sets the number of pixels that a motion of a  wheel\nmouse  will  move  the  image up, down, left, or right. (See the\nwheel and hwheel actions, below, for more information on  this.)\nIf  set  to zero, the wheel mouse functionality is (essentially)\ndisabled.  The default value is 80.\n\n-xoffset dimen\n(.xOffset) Specifies the size of the horizontal  offset  of  the\noutput on the page.  See -offsets.\n\n-yoffset dimen\n(.yOffset) Specifies the size of the vertical offset of the out-\nput on the page.  See -offsets.\n"
                }
            ]
        },
        "KEYSTROKES": {
            "content": "Xdvi recognizes the following keystrokes  when  typed  in  its  window.\nEach  may  optionally be preceded by a (positive or negative) number, a\n`prefix argument', whose interpretation will depend on  the  particular\nkeystroke.  This prefix argument can be discarded by pressing the ``Es-\ncape'' key.  If present, the ``Help'', ``Prior'' and ``Next'' keys  are\nsynonyms for `?', `b', and `f' keys, respectively.\n\nThe  key  bindings  listed here are those that xdvi assigns by default.\nThe names appearing in brackets at the beginning  of  the  descriptions\nare  the  names  of  the actions associated with the keys; these can be\nused to customize the key bindings, as explained in more detail in  the\nsection  CUSTOMIZATION  below.  If  only a lowercase binding is listed,\nboth upper- and lowercase keys will work for that binding.\n\nESC key\n[discard-number()] The escape key discards the numerical  prefix\nfor all actions (useful when you mistyped a number).\n\nReturn key\n[forward-page()] Moves to the next page (or to the nth next page\nif a number is given).  Synonyms are `n', `f' and Line Feed.\n\nBackspace key\n[back-page()] Moves to the previous  page  (or  back  n  pages).\nSynonyms are `p', `b' and Ctrl-h.\n\nDelete key\n[up-or-previous()]  Moves  up two-thirds of a window-full, or to\nthe top of the previous page if already at the top of the  page.\nWith  a float argument, moves up the corresponding fraction of a\nwindow-full.\n\nSpace key\n[unpause-or-next()] Moves down two-thirds of a  window-full,  or\nto the next page if already at the bottom of the page.\nWhen the option -pause special-string is used and the display is\ncurrently paused, this key will instead display the next portion\nof the page until the next special-string or the end of the page\nis encountered.  See the description of the  -pause  option  for\ndetails.  The  action [down-or-next()] does a similar thing, but\nwithout pausing; it is not bound to a key by default.\n\nCtrl-Home (Xaw), Ctrl-osfBeginLine (Motif)\n[goto-page(1)] Moves to the first page of the document.\n\nCtrl-End (Xaw), Ctrl-osfEndLine (Motif)\n[goto-page()] Moves to the last page of the document.\n\nHome (Xaw), osfBeginLine (Motif)\n[home-or-top()] Move to the ``home'' position of the page, or to\nthe  top  of the page if the keep flag is set (in this case, the\npage doesn't scroll horizontally).\n\nEnd (Xaw), osfEndLine (Motif)\n[end-or-bottom()] Move to the ``end'' position of the page  (the\nlower  right-hand  corner),  or to the bottom of the page if the\nkeep flag is set (in this case, the page doesn't scroll horizon-\ntally).\n\nDown arrow\n[down(0.015)] Scrolls page down.\n\nUp arrow\n[up(0.015)] Scrolls page up.\n\nRight arrow\n[right(0.015)] Scrolls page right.\n\nLeft arrow\n[left(0.015)] Scrolls page left.\n\nAlt-Ctrl-+\n[change-density(25)]  Increase  the darkness of the fonts in the\nDVI window by adding to the gamma value (see also the  `S'  key-\nstroke).\n\nAlt-Ctrl--\n[change-density(-25)]  Decrease the darkness of the fonts in the\nDVI window by subtracting from the gamma value (see also the `S'\nkeystroke).\n\nCtrl-+ [set-shrink-factor(+)]  Increase the shrink factor (see also the\n`s' keystroke).\n\nCtrl-- [set-shrink-factor(-)] Decrease the shrink factor (see also  the\n`s' keystroke).\n\nCtr-[  [pagehistory-delete-backward()]  Delete  the current item in the\npage history and move to the history  item  before  the  deleted\none.  With a prefix argument n, delete n previous history items.\nSee PAGE HISTORY for details.\n\n[      [pagehistory-back()] Move back in the  page  history  (see  PAGE\nHISTORY for details). With a prefix argument n, move back n his-\ntory items.\n\nCtr-]  [pagehistory-delete-forward()] Delete the current  item  in  the\npage history and move to the history item after the deleted one.\nWith a prefix argument n, delete n next history items. See  PAGE\nHISTORY for details.\n\n]      [pagehistory-forward()]  Move  forward  in the page history (see\nPAGE HISTORY for details). With a prefix argument n,  move  for-\nward n history items.\n\n^      [home()]  Move  to  the  ``home'' position of the page.  This is\nnormally the upper left-hand corner of the  page,  depending  on\nthe margins as described in the -margins option, above.\n\n?      [help()] Same as the h key (which see).\n\nB      [htex-back()]  This key jumps back to the previous hyperlink an-\nchor. See the section HYPERLINKS for more information  on  navi-\ngating the links.\n\nb      [back-page()]  Moves  to  the  previous  page (or back n pages).\nSynonyms are `p', Ctrl-h and Backspace.\n\nC      [set-color()] This key toggles the use of color  specials.   The\nkey  sequences  `0C'  and `1C' turn interpretation of color spe-\ncials off and on, respectively.  See also the -nocolor option.\n\nc      [center()] Moves the page so that the  point  currently  beneath\nthe mouse cursor is moved to the middle of the window, and warps\nthe mouse cursor to the same place.\n\nD      [toggle-grid-mode()] This key toggles the use of a grid  on  the\ndisplayed  page.   If  no  number  is  given,  the  grid mode is\nswitched on or off.  By prepending a number from 1 to 3, 3  dif-\nferent grid levels can be set.  The units of the grid are inches\nor centimeters, depending on whether the paper format is  letter\n(in) or a4 (cm).\n\nd      [down()]  Moves  page  down  two thirds of a window-full. With a\nfloat argument to ``down'', moves down the  corresponding  frac-\ntion of a window-full.\n\nCtrl-f [find()] Pop up a window to search for a string in the DVI file.\nSee the section STRING SEARCH, below, for more details.\n\nf      [forward-page()] Moves to the next page (or to the nth next page\nif a number is given).  Synonyms are `n', Return, and Line Feed.\n\nG      [set-greyscaling()]  This key toggles the use of greyscale anti-\naliasing for displaying shrunken bitmaps.  In addition, the  key\nsequences  `0G'  and `1G' clear and set this flag, respectively.\nSee also the -nogrey option.\n\nIf given a numeric argument that is not 0 or 1, greyscale  anti-\naliasing is turned on, and the gamma resource is set to the val-\nue divided by 100. E.g. `150G' turns on greyscale and sets gamma\nto 1.5.\n\nCtrl-g [find-next()]  Find  the next match string in the DVI file; this\ncan be used instead of pressing the `Find' button in the  search\nwindow.\n\ng      [goto-page()]  Moves  to  the  page with the given number. If no\npage number is given, xdvi jumps to the last page.\nIf the option/resource useTeXpages is active, the numbers corre-\nspond to the actual page numbers in the TeX file; otherwise, ab-\nsolute page numbers (starting from 1) are used.  In  the  latter\ncase,  the  page  numbers can be changed with the `P' keystroke,\nbelow.  Note that with the useTeXpages  option  it  is  possible\nthat the same page number occurs multiple times; in such a case,\nxdvi will use the first page number that matches.\n\nh      Pops up a help window with a short explanation of the  most  im-\nportant key bindings and concepts.\n\nk      [set-keep-flag()] Normally when xdvi switches pages, it moves to\nthe home position as well.  The `k' keystroke toggles  a  `keep-\nposition' flag which, when set, will keep the same position when\nmoving between pages.  Also `0k' and `1k'  clear  and  set  this\nflag, respectively.  See also the -keep option.\n\nCtrl-l [fullscreen(toggle)]  Toggles  fullscreen mode (see the descrip-\ntion of the -fullscreen option for more  information  on  this).\nThis  is  even  more  flaky  than using the command-line option:\nThere is no universal standard how a window could change its own\ngeometry  or  window  decorations  at run-time, so this will not\nwork with most window managers or desktops. Generally, it's bet-\nter  to  use  the  window manager controls to change the size or\ndecorations of the xdvi window.\n\nl      [left()] Moves page left two thirds of a window-full.\n\nM      [set-margins()] Sets the margins so that the point currently un-\nder  the  mouse cursor defines the upper left-hand corner of the\ntext in the page.  Note that the command does not move  the  im-\nage, but only determines the margins for the page switching com-\nmands. For details on how the margins are used, see the -margins\noption.\n\nm      [toggle-mark()]  Toggles  the  mark  for the current page in the\npage list. When a page is marked, it is displayed with  a  small\nstar  `*' next to the page number.  The marked pages can then be\nprinted or saved to a file.  A page or several pages can also be\nmarked by clicking or dragging Mouse-2 in the page list.\n\nCtrl-n [toggle-mark()forward-page()]  Toggles  the mark for the current\npage in the page list, and moves to the next page. This lets you\nquickly mark a series of subsequent pages.\n\nn      [forward-page()] Moves to the next page (or to the nth next page\nif a number is given).  Synonyms are `f', Return, and Line Feed.\n\nCtrl-o [select-dvi-file()] Read a new dvi file. A file-selection widget\nis  popped  up  for you to choose the DVI file from. If a prefix\nargument n is given, the n th file  from  the  file  history  is\nopened instead.\n\nP      [declare-page-number()]  ``This is page number n.''  This can be\nused to make the `g' keystroke refer to a different page  number\nthan  the  physical  page.  (If you want to use `logical' or TeX\npage numbers instead of physical pages, consider using  the  op-\ntion  -useTeXpages  instead.)  The argument n should be given as\nprefix to this key.\n\nCtrl-p [print()] Opens a popup window for printing  the  DVI  file,  or\nparts of it.  See the section PRINT DIALOG for an explanation of\nthe options available, and the resources to  customize  the  de-\nfault behaviour.\n\np      [back-page()]  Moves  to  the  previous  page (or back n pages).\nSynonyms are `b', Ctrl-h and Backspace.\n\nq      [quit()] Quits the program.\n\nCtrl-r [forward-page(0)] Redisplays the current page.\n\nR      [reread-dvi-file()] Forces the dvi file to be reread.  This  al-\nlows you to preview many versions of the same file while running\nxdvi only once.\n\nr      [right()] Moves page right two thirds of a window-full.\n\nCtrl-s [save()] Opens a popup window for saving the DVI file, or  parts\nof it. See the section SAVE DIALOG below for more information on\nthis.\n\nS      [set-density()] Sets the density factor to be used when  shrink-\ning  bitmaps.  This should be a number between 0 and 100; higher\nnumbers produce lighter characters.  If greyscaling mode  is  in\neffect,  this changes the value of gamma instead.  The new value\nof gamma is the given number divided by 100; negative values are\nallowed.\n\ns      [set-shrink-factor()]  Changes  the  shrink  factor to the given\nnumber.  If no number is given, the smallest factor  that  makes\nthe  entire  page  fit in the window will be used.  (Margins are\nignored in this computation.)\n\nT      [use-tex-pages()] Use logical  TeX  pages  (the  values  of  the\n\\count0 register) instead of physical pages for the pagelist la-\nbels and when jumping to a page in a document  via  goto-page().\nSee also the -useTeXpages option.\n\nt      [switch-magnifier-units()]  Switches the units used for the mag-\nnifier tick marks, and for reporting the  distance  between  the\nmouse  pointer  and the ruler centre in ruler mode (see the sec-\ntion MODES).  The default value is specified by the  X  resource\ntickUnits  (`mm'  by default). The units toggle through the fol-\nlowing values; except for `px', they  all  correspond  to  TeX's\nunits: mm (millimeters) pt (TeX points), in (inches), sp (scaled\npoints, the unit used internally  by  TeX)  bp  (big  points  or\n`PostScript  points'), cc (cicero points), dd (didot points), pc\n(pica), and px (screen pixels).\n\nCtrl-u [back-page()toggle-mark()] Moves to the previous page, and  tog-\ngles the mark for that page. This is the dual action to Ctrl-n.\n\nu      [up()]  Moves  page up two thirds of a window-full. With a float\nargument to ``up'', moves up the  corresponding  fraction  of  a\nwindow-full.\n\nCtrl-v [show-source-specials()]  Show  bounding  boxes for every source\nspecial on the current page, and print the strings contained  in\nthese specials to stderr. With prefix 1, show every bounding box\non the page. This is for debugging purposes mainly.\n\nV      [set-gs-alpha()] This key toggles  the  anti-aliasing  of  Post-\nScript<tm>  specials  when  Ghostscript is used as renderer.  In\naddition the key sequences `0V' and  `1V'  clear  and  set  this\nflag, respectively.  See also the -gsalpha option.\n\nv      [set-ps()] This key toggles the rendering of PostScript<tm> spe-\ncials between 3 states:\n\n- specials (like EPS graphics) are displayed;\n\n- specials are displayed  along  with  their  bounding  box  (if\navailable);\n\n- only the bounding box is displayed.\n\nThe states can also be selected directly by using `1v', `2v' and\n`0v' respectively.  See also the -postscript option.\n\nCtrl-x [source-what-special()] Display  information  about  the  source\nspecial  next to the mouse cursor in the statusline. This is the\nsame special that would be found by source-special(), but  with-\nout invoking the editor. For debugging purposes.\n\nx      [set-expert-mode()]  Toggles  expert  mode,  in  which  the sta-\ntusline, the scrollbars, the menu buttons,  the  toolbar  (Motif\nonly)  and the page list are not shown.  Typing `1x' toggles the\ndisplay of the statusline at the bottom of  the  window.  Typing\n`2x'  toggles  the scrollbars (if available). For Xaw, `3x' tog-\ngles the menu buttons and the page list, for Motif,  it  toggles\nthe page list. In Motif, the additional bindings `4x' toggle the\ntoolbar, and `5x' the menu bar.\nWithout a prefix argument, all of the mentioned GUI elements are\neither switched on (if they had been invisible before) or off.\nToggling the scrollbars may behave erratically with the Xaw wid-\ngets; e.g. the scrollbars may reappear after resizing  the  win-\ndow,  and at certain window sizes one of the scrollbars may fail\nto disappear.\nSee also the option -expertmode (the numbers above correspond to\nthe bits in the argument to -expertmode).\n",
            "subsections": []
        },
        "MOUSE ACTIONS IN THE MAIN WINDOW": {
            "content": "The  mouse  actions  can be customized by setting the X resource mouse-\nTranslations.  Since there are three different  mouse  modes  (see  the\nsection MODES below), there is a special action mouse-modes which lists\nthe actions for each  of  the  three  modes:  mouse-modes(\"ACTIONS-FOR-\nMODE1\",  \"ACTIONS-FOR-MODE2\",  \"ACTIONS-FOR-MODE3\").  If only one argu-\nment is specified, this action is used  for  all  modes.   The  default\nbindings are as follows:\n\nxdvi.mouseTranslations: \\\nShift<Btn1Down>:mouse-modes(\"drag(+)\")\\n\\\nShift<Btn2Down>:mouse-modes(\"drag(|)\")\\n\\\nShift<Btn3Down>:mouse-modes(\"drag(-)\")\\n\\\nCtrl<Btn1Down>:mouse-modes(\"source-special()\")\\n\\\n<Btn1Down>: mouse-modes(\"do-href()magnifier(*2)\", \"text-selection()\", \"ruler()\")\\n\\\n<Btn2Down>: mouse-modes(\"do-href-newwindow()magnifier(*2)\", \"text-selection()\", \"ruler()\")\\n\\\n<Btn3Down>: mouse-modes(\"magnifier(*3)\")\\n\\\n<Btn4Down>: mouse-modes(\"wheel(-0.2)\")\\n\\\n<Btn5Down>: mouse-modes(\"wheel(0.2)\")\\n\\\n<Btn6Down>: mouse-modes(\"hwheel(-0.2)\")\\n\\\n<Btn7Down>: mouse-modes(\"hwheel(0.2)\")\\n\\\n\nAll  of these actions are described in more detail below.  Note the use\nof quote symbols around the action  strings,  which  are  necessary  to\ngroup  them  into  one argument.  Buttons 4, 5, 6, and 7 refer to wheel\nmovements (wheel up/down/left/right) on wheel mice.  Not all mice  sup-\nport horizontal scrolling.\n\nThe X Toolkit routines that implement translations do not support event\ntypes of Btn6Down or Btn7Down.  Because of this,  xdvi  implements  its\nown parser for translations given in mouseTranslations.  This parser is\nmore limited than the parser built in to the  X  Toolkit.   The  string\ngiven  in mouseTranslations should not begin with ``#replace'', ``#aug-\nment'', or ``#override''.  Modifiers of the form @keysym are  not  sup-\nported,  and  the  event  type must be of the form BtnDown or BtnnDown,\nwhere n is a positive integer without leading zeroes.  Also, some limi-\ntations apply to the action field.\n\ndo-href()\n\ndo-href-newwindow()\nUsually,  if  a  binding specifies more then one action, all ac-\ntions are executed in a sequence.  The  hyperlink  bindings  do-\nhref() and do-href-newwindow() are special in that they are used\nas an alternative to other actions that might follow them if the\nmouse  is  currently located on a hyperlink.  In this case, none\nof the other actions will be executed; otherwise, only the other\nactions are executed.\nThe action do-href() jumps to the link target in the current xd-\nvi window (eventually switching to another page),  and  do-href-\nnewwindow()  opens  a  new instance of xdvi for the link target.\nIn both cases, the location of the  target  is  indicated  by  a\nsmall  arrow  drawn  in  the same color as a visited link in the\nleft corner of the window.\n\nmagnifier(n x m)\n\nmagnifier(*n)\nThis action will pop up a ``magnifying glass'' which  shows  the\nunshrunk image of the region around the mouse pointer.  The mag-\nnifier disappears when the mouse button is released. Moving  the\nmouse  cursor while holding the button down will move the magni-\nfier.\nDifferent mouse buttons produce different sized windows, as  in-\ndicated  by the argument of the magnifier() action. Its argument\nis either a string of the form widthxheight,  as  in  the  -mgsn\ncommand-line option, or one of the strings *1 through *5, refer-\nring to the value specified by the corresponding -mgsn option.\n\ndrag(+)\n\ndrag(|)\n\ndrag(-)\nDrags the page with the mouse. This action should have  one  pa-\nrameter, the character ``|'', ``-'', or ``+'', indicating verti-\ncal dragging only, horizontal dragging only, or dragging in  all\ndirections.\n\nsource-special()\nThis  action  starts a ``reverse search'', opening the editor at\nthe location in the TeX file corresponding to the pointer  loca-\ntion  in  the DVI file.  See the section on SOURCE SPECIALS, be-\nlow, for more information on this.\n\nwheel()\nThis action can be used to scroll the image with a wheel  mouse,\nwhere  it  is  usually  bound  to mouse button 4 (wheel up) or 5\n(wheel down).  The action takes one parameter, giving  the  dis-\ntance  to scroll the image.  If the parameter contains a decimal\npoint, the distance is given in wheel units; otherwise,  pixels.\nA negative value scrolls up, a positive value scrolls down.\n\nhwheel()\nThis  action can be used to scroll the image horizontally with a\nwheel mouse, where it is usually bound to mouse button 6  (wheel\nleft)  or 7 (wheel right).  The action takes one parameter, giv-\ning the distance to scroll the image.  If the parameter contains\na  decimal  point,  the distance is given in wheel units; other-\nwise, pixels.  A negative value scrolls left, a  positive  value\nscrolls  right.  Not all mice support horizontal scrolling; this\nis mostly for touchpads, trackpads, etc.\n\ntext-selection()\nThis action allows you to mark a rectangular region of  text  in\nthe  DVI  file.  The text is put into the X selection buffer and\ncan be pasted into other applications (e.g. text editors).  This\nworks  similar  to the Plain text option in the Save dialog; see\nthe discussion there for more information on encoding issues.\n\nruler()\nThis action creates a cross-shaped ruler. Moving the  mouse  and\nholding  the  button  down  drags the ruler and lets you measure\ndistances on the page.  See the section Ruler Mode for more  in-\nformation on this.\n",
            "subsections": []
        },
        "UNBOUND ACTIONS": {
            "content": "The following actions are not bound to a key by default, but are avail-\nable for customization.\n\nquit-confirm()\nPops up a confirmation window to quit xdvi. To bind  it  to  the\n`q'  key instead of the default `quit()' action, put the follow-\ning into your ~/.Xdefaults file:\n\nxdvi.mainTranslations: #override\\\n<Key>q: quit-confirm()\\n\n\ndown-or-next()\nSimilar to unpause-or-next(): Moves down two-thirds of a window-\nfull, or to the next page if already at the bottom of the page.\n\nshrink-to-dpi()\nThis  action  takes one (required) argument.  It sets the shrink\nfactor to an integer so as to approximate the use of fonts  with\nthe  corresponding  number  of  dots per inch.  If xdvi is using\nfonts scaled for p dots per inch, and the argument to shrink-to-\ndpi is n, then the corresponding shrink factor is the ratio p/n,\nrounded to the nearest integer.\n\nuser-exec()\nThis action takes one (required) argument. Runs an external pro-\ngram  specified  by  the  argument, which is tokenized on white-\nspace. The XDVIFILE environment variable is set to the absolute\npathname  of the DVI file, so that the program can find the DVI.\nAs an example, to establish the key `m' as a keybinding that re-\ngenerates  the DVI file with `make', put the following into your\n~/.Xdefaults file:\n\nxdvi.mainTranslations: #override\\\n<Key>m: user-exec(xdvi-remake)\\n\n\nwhere `xdvi-remake' names a program in your  PATH  analogous  to\n`cd $(dirname $XDVIFILE) && make $(basename $XDVIFILE)'.  (See\nalso the section SIGNALS for a way to get xdvi to reload the DVI\nfile once it has been regenerated.)\n",
            "subsections": []
        },
        "CUSTOMIZATION": {
            "content": "Key  and  mouse  button assignments can be changed by setting the main-\nTranslations resource to a string of translations  as  defined  in  the\ndocumentation  for  the X toolkit.  The actions should take the form of\naction names listed in the KEYSTROKES and MOUSE ACTIONS sections.\n\nAn exception to this are the Motif keys osfPageUp  (PgUp),  osfPageDown\n(PgDown),  osfBeginLine (Home) and osfEndLine (End) which are currently\nnot customizable in the Motif version.\n\nKey actions will usually be without arguments; if they  are  passed  an\nargument,  it represents the optional number or `prefix argument' typed\nprior to the action.\n\nSome key actions may take special arguments, as follows:  The  argument\nof  goto-page  may be the letter `e', indicating the action of going to\nthe end of the document.  The argument of set-shrink-factor may be  the\nletter  `a',  indicating  that  the  shrink factor should be set to the\nsmallest value such that the page will fit in the window, or one of the\nsigns `+' or `-', indicating that the shrink factor should be increased\nor decreased, respectively.  Finally, actions that would perform a tog-\ngle,  such  as  set-keep-flag,  may receive an argument `t', indicating\nthat the action should toggle regardless of the  current  prefix  argu-\nment.\n\nMouse   actions   should   refer   only  to  ButtonPress  events  (e.g.\n<Btn1Down>:magnifier(*1)).  The corresponding motion and release events\nwill  be  handled  internally.   A  key  action may be bound to a mouse\nevent, but not vice versa.\n\nUsually the string of translations should begin with ``#override'', in-\ndicating  that  the default key and mouse button assignments should not\nbe discarded.\n\nWhen keys or mouse buttons involving modifiers (such as Ctrl or  Shift)\nare  customized together with their non-modified equivalents, the modi-\nfied keys should come first, for example:\n\nxdvi.mainTranslations: #override \\\nShift<Key>s: select-dvi-file()\\n\\\nCtrl<Key>s: save()\\n\\\n<Key>s: find()\\n\n\nBecause xdvi needs to capture pointer motion events, and because the  X\nToolkit  translations  mechanism  cannot accommodate both motion events\nand double-click events at the same time, it is not possible to specify\ndouble-click  actions  in xdvi customizations.  For information on this\nand other aspects of translations, see the X Toolkit  Intrinsics  docu-\nmentation.\n\nThere  is  no command-line option to set the mainTranslations resource,\nsince changing this resource on the command line would  be  cumbersome.\nTo set the resource for testing purposes, use the -xrm command-line op-\ntion provided by the X toolkit.  For  example,  xdvi  -xrm  'XDvi.main-\nTranslations:  #override \"z\":quit()' ...  or xdvi -xrm 'XDvi.mainTrans-\nlations: #override <Key>z:quit()' ...  will cause the key `z'  to  quit\nxdvi.\n\nSome  resources  are provided to allow customization of the geometry of\nthe Xaw command buttons.  Again, they are not changeable  via  command-\nline  options,  other than via the -xrm option.  All of these resources\ntake integer values.\n\nbuttonSideSpacing\nThe number of pixels to be placed on either side of the buttons.\nThe default value is 6.\n\nbuttonTopSpacing\nThe  number  of pixels between the top button and the top of the\nwindow.  The default value is 50.\n\nbuttonBetweenSpacing\nThe number of pixels between the buttons.  The default value  is\n20.\n\nbuttonBetweenExtra\nThe  number  of pixels of additional space to be inserted if the\nbuttonTranslations resource string  contains  an  extra  newline\ncharacter.  The default value is 50.\n\nbuttonBorderWidth\nThe border width of the button windows.  The default value is 1.\n",
            "subsections": []
        },
        "PAGE LIST": {
            "content": "The  scrollable page list on the right of the main window allows you to\njump directly to a page in the DVI file.\n\nMouse-1\nJumps to the page the mouse is located on.\n\nMouse-2\n[toggle-mark()] Toggle the mark of the current page.  The  marks\nare used by the `Print' and `Save to file' dialogs to select on-\nly marked pages from the DVI file.\n\nWhen the mouse pointer is inside the page list, the mouse wheel switch-\nes to the next or previous page.\n",
            "subsections": []
        },
        "SCROLLBARS": {
            "content": "The scrollbars (if present) behave in the standard way:  pushing Button\n2 in a scrollbar moves the top or left edge of the  scrollbar  to  that\npoint  and  optionally drags it; pushing Button 1 moves the image up or\nright by an amount equal to the distance from the button press  to  the\nupper  left-hand corner of the window; pushing Button 3 moves the image\ndown or left by the same amount.\n\nThe scrollbars can be removed via the -expertmode flag/keystroke (which\nsee).\n",
            "subsections": []
        },
        "MAGNIFIER": {
            "content": "By default, the mouse buttons 1 to 5 will pop up a ``magnifying glass''\nthat shows an unshrunken image of the page (i.e. an image at the  reso-\nlution determined by the option/X resource pixels or mfmode) at varying\nsizes. When the magnifier is moved, small  ruler-like  tick  marks  are\ndisplayed  at  the  edges  of  the magnifier (unless the X resource de-\nlayRulers is set to false, in which case the tick marks will always  be\ndisplayed).   The  unit  of  the  marks is determined by the X resource\ntickUnits (mm by default). This unit can be changed at runtime via  the\naction  switch-magnifier-units(), by default bound to the keystroke `t'\n(see the description of that key, and of  switch-magnifier-units()  for\nmore details on the units available).\nThe  length  of  the tick marks can be changed via the X resource tick-\nLength (4 by default). A zero or negative  value  suppresses  the  tick\nmarks.\n",
            "subsections": []
        },
        "PAGE HISTORY": {
            "content": "Xdvi keeps a history of viewed pages, and you can move through the his-\ntory and delete items using the keys [ (pagehistory-back()),  ]  (page-\nhistory-forward()),  Ctr-[  (pagehistory-delete-backward())  and  Ctr-]\n(pagehistory-delete-forward()).\n\nWhen one of the history commands is used, the page history is displayed\nin  the  status line at the bottom of the window, with the current list\nitem marked by square brackets `[', `]' and a left and right context of\nat most 10 items. File boundaries are marked by `#'.\n\nThe  size of the history can be customized with the X resource pageHis-\ntorySize (the default size is 1000 items). If the size is set to 0, the\nhistory commands are disabled.\n",
            "subsections": []
        },
        "HYPERLINKS": {
            "content": "The  actions  do-href()  and  do-href-newwindow()  (by default bound to\nMouse-1 and Mouse-2 if the pointer is currently located on a hyperlink)\ncan  be  used to open the link target in the same window (do-href()) or\nin a new window (do-href-newwindow()).\n\nIf the link target is not a file on  the  local  disk,  xdvi  tries  to\nlaunch a web browser (as specified by the -browser command line option,\nthe BROWSER environment variable or the wwwBrowser X resource, in  this\norder) to retrieve the document. See the description of the BROWSER en-\nvironment variable, below, for an example setting.\n\nIf the file is a local file, xdvi tries to determine if  it  is  a  DVI\nfile.  If  it  is, xdvi will try to display the file; otherwise it will\ntry to determine the MIME type of the file, and from that  an  applica-\ntion  suitable for opening the file.  This is done by parsing the files\nspecified by the environment variable EXTENSIONMAPS for  a  mapping  of\nfilename  extensions to MIME types, and the files determined by the en-\nvironment variable MAILCAPS for a mapping of MIME types to  application\nprograms.  See the descriptions of these variables in the section ENVI-\nRONMENT, below, for a more detailed description and the default  values\nof  these  variables. If no suitable files are found, a set of built-in\ndefault MIME types and applications is used.\n\nXdvi currently uses no heuristics apart from the filename suffix to de-\ntermine the mime type of a file. If a filename has no suffix, the value\nof the resource noMimeSuffix  is  used  (by  default  application/x-un-\nknown).  If the suffix doesn't match any of the suffixes in mime.types,\nthe value of the resource unknownMimeSuffix is used (by default  appli-\ncation/x-unknown).   If  the mailcap entries do not list a viewer for a\ngiven mime type, xdvi will show a warning popup. If you want  to  avoid\nthis  warning,  and for example want to always use the netscape browser\nfor unknown MIME types, you  could  add  the  following  line  to  your\n~/.mailcap file:\n\napplication/xdvi-unknown; \\\nnetscape -raise -remote 'openURL(%s,new-window)'\n",
            "subsections": []
        },
        "STRING SEARCH": {
            "content": "The keystroke Ctrl-f or the menu entry File > Find ...  (or the `Binoc-\nulars' symbol in the toolbar, for  Motif)  opens  a  dialog  window  to\nsearch  for a text string or a regular expression in the DVI file.  The\nkeystroke Ctrl-g jumps to the next match (like pressing the `Find' but-\nton in the search window).\n\nBy default, the matches are highlighted in inverted color.  If the dis-\nplay isn't running in TrueColor, or if the X resource matchHighlightIn-\nverted  is  set to false or the command-line option -nomatchinverted is\nused, xdvi will instead draw a rectangle in highlight  color  (see  the\n-hl option) around the match.\n\nIf  a match crosses a page boundary, only the part on the first page is\nhighlighted.  Xdvi will scan up to 2 adjacent pages  to  match  strings\ncrossing  page boundaries; but note that header or footer lines, or in-\ntervening float pages will be treated as parts  of  the  scanned  text.\nSuch text will usually cause multi-page matching to fail.\n\nThis  emphasizes the fact that searching in the formatted text (the DVI\noutput) works differently from searching in the source text:  Searching\nin  the  DVI  file makes it easier to skip formatting instructions, and\nmakes it possible to search for e.g. hyphenation and equation  numbers;\nbut  sometimes  the formatting results can also get in the way, e.g. in\nthe case of footnotes. In these cases it's better to search in the  TeX\nsource  instead. The use of source specials will make switching between\nthe xdvi display and the editor with the TeX  source  easier;  see  the\nsection SOURCE SPECIALS below for more information on this.\n\nThe  text  extracted  from the DVI file is in encoded in UTF-8 (you can\nview that text by saving the file in UTF-8 format via the File  >  Save\nas  ...  menu item).  If xdvi has been compiled with locale, nllangin-\nfo() and iconv support, the search term is converted from the character\nset  specified by the current locale into UTF-8. (See the output of lo-\ncale -a for a list of locale settings available on  your  system).   If\nnllanginfo() is not available, but iconv is, you can specify the input\nencoding for iconv via the X resource textEncoding (see the  output  of\niconv -l for a list of valid encodings). If iconv support is not avail-\nable, only the encodings ISO-8859-1  and  UTF-8  are  supported  (these\nnames are case-insensitive).\n\nIdeographic characters from CJKV fonts are treated specially: All white\nspace (spaces and newlines) before and after such characters is ignored\nin the search string and in the DVI file.\n\nTo match a newline character, use \\n in the search string; to match the\nstring \\n, use \\\\n.\n\nIf the checkbox Regular Expression is activated, the string is  treated\nas  a  regular  expression in extended POSIX syntax, with the following\nproperties:\n\n- a? matches a zero or one times.\n\n- a* matches a zero or more times.\n\n- a+ matches a one or more times.  Note that * and + are greedy, i.e.\nthey match the longest possible substring.\n\n- The  pattern  .  matches  any character except for newline. To also\nmatch a newline, use `(.|\\n)'.\n\n- a{n} matches a exactly n times.\n\n- a{n,m} matches a at least n and no more than m times.\n\n- a|b matches a or b.  Brackets  can  be  used  for  grouping,  e.g.:\n(a|b)|c.\n\n- The  string  matched by the nth group can be referenced by \\n, e.g.\n\\1 refers to the first match.\n\n- The characters ^ and $ match the beginning and the end of  a  line,\nrespectively.\n\n- [abc]  matches  any  of  the letters a, b, c, and [a-z] matches all\ncharacters from a to z.\n\n- Each item in a regular expression can also be one of the  following\nPOSIX character classes:\n[[:alnum:]] [[:alpha:]] [[:blank:]] [[:cntrl:]] [[:digit:]]\n[[:graph:]] [[:lower:]] [[:print:]] [[:space:]] [[:upper:]]\n\nThese can be negated by inserting a ^ symbol after the first brack-\net: [^[:alpha:]]\n\nFor more details on POSIX regular expressions, see  e.g.  the  IEEE\nStd 1003.1 standard definition available online from:\n\nhttp://www.opengroup.org/onlinepubs/007904975/basedefs/xbdchap09.html\n\n- As  a non-standard extension, the following Perl-like abbreviations\ncan be used instead of the POSIX classes:\n\nSymbol   Meaning                       POSIX Class\n\n\\w   an alphanumeric character     [[:alnum:]]\n\\W   a non-alphanumeric character  [^[:alnum:]]\n\\d   a digit character             [[:digit:]]\n\\D   a non-digit character         [^[:digit:]]\n\\s   a whitespace character        [[:space:]]\n\\S   a non-whitespace character    [^[:space:]]\n\n- The following characters are special symbols; they need to  be  es-\ncaped with \\ in order to match them literally:  ( ) [ ] . * ? + ^ $\n\\.\n\n- Matches of length zero are silently skipped.\n\nThe dialog also provides checkboxes to:\n\n- search backwards;\n\n- match in a case-sensitive manner (the default is  to  ignore  case,\ni.e. a search string Test will match both the strings test and TEST\nin the DVI file);\n\n- ignore line breaks and hyphens: This removes  all  hyphens  at  the\nends  of  lines  and the following newline characters, and replaces\nall remaining newline characters by  white  spaces.  So  hyphenated\nwords  will  appear as one word to the search, and a search for two\nwords with a space in between will also match the words if they are\nseparated by a linebreak.\nNote  that  the  hyphen removal may cause unwanted side effects for\ncompound words containing hyphens that are wrapped  after  the  hy-\nphen, and that replacing the newlines affects the interpretation of\nregular expressions as follows: The . pattern will also match  new-\nlines,  and  ^  and  $ won't match begin and end of lines any more.\n(Since currently there is no option for turning off the  greediness\nof  *  and +, turning on this option will usually result in matches\nthat are longer than desired.)\n\nThe current checkbox settings are saved in the ~/.xdvirc file.\n",
            "subsections": []
        },
        "PRINT DIALOG": {
            "content": "The print dialog window allows you to print  all  pages,  marked  pages\n(click  or  drag  Mouse-2 in the page list to mark them), or a range of\npages. Note that the page numbers always refer to physical pages, so if\nyou're  using the option `use TeX pages', you may want to disable it to\nmake it easier to determine the correct page  numbers  (or  avoid  this\nproblem altogether by marking the pages to be printed).\n\nThe  value  of  the  Printer  text filed is passed to dvips via the -o!\nmechanism, as a single argument after the `!'. Any arguments listed  in\nthe Dvips options field are segmented at whitespace and passed as sepa-\nrate arguments to dvips.  If you e.g. want to print the file 2-up,  you\nshould enter the following string into the Printer field:\n\npsnup -2 -q | lpr -Plp\n\nThere  are  several resources for customizing the behaviour and the de-\nfault entries of the print dialog:\n\ndvipsPrinterString\n\ndvipsOptionsString\nThese can be used to provide default entries for the Printer and\nthe Dvips options text fields, respectively. If no paper size is\nspecified in the DVI file (via e.g. \\usepackage[dvips]{geometry}\n-  this is the preferred method), the input field is initialized\nwith the current value of the command line option/X resource pa-\nper.   E.g.  the  option -paper a4r is translated into the dvips\noptions -t a4 -t landscape.  Note that  no  check  is  performed\nwhether dvips actually understands these options (it will ignore\nthem if it can't); currently not all options used  by  xdvi  are\nalso covered by dvips.\n\ndvipsHangTime\n\ndvipsFailHangTime\nThese  specify  the  time  (in  milliseconds)  that the printing\nprogress window will stay open after the dvips process has  ter-\nminated.  The value of dvipsHangTime is used if the process ter-\nminates successfully; dvipsFailHangTime is used if it terminates\nwith an error. The default values are 1.5 and 5 seconds, respec-\ntively.  If both values are negative, the window will stay  open\nuntil it is closed by the user.\n",
            "subsections": []
        },
        "SAVE DIALOG": {
            "content": "This dialog allows you to save all or selected/marked pages in the cur-\nrent DVI file. You can save in one of the following formats:\n\n- PostScript (uses dvips to convert the  DVI  file  to  a  PostScript\nfile, just like when printing to a PostScript file).\n\n- PDF (first uses dvips to convert the DVI file to a PostScript file,\nthen uses ps2pdf to convert the PostScript file to PDF).\n\n- Plain text in ISO-8859-1 or UTF-8 encoding. The  latter  will  pre-\nserve  more  of the special LaTeX characters e.g. from mathematical\nmode. Note however that e.g. only few of LaTeX's mathematical  sym-\nbols can be rendered correctly as text; so this functionality works\nbest for plain text documents.  If a character cannot be  displayed\nin  the  selected  charset,  it  is replaced by `\\' followed by the\nhexadecimal character code.  If a character is  not  recognized  at\nall, it is replaced by `?'.\n\nThe  programs  for  PostScript and PDF conversion can be customized via\nthe command line  options  or  X  resources  -dvipspath/.dvipsPath  and\n-ps2pdfpath/.ps2pdfPath, respectively; see the explanation of these op-\ntions above for more details.\n",
            "subsections": []
        },
        "MODES": {
            "content": "The keystroke Ctrl-m [switch-mode()] switches between  three  different\nmouse  bindings, which can also be activated via the Modes menu (in Mo-\ntif, this is a submenu of the Options menu called Mouse Mode).  The de-\nfault mode at startup can be customized via the X resource mouseMode or\nthe command-line option -mousemode.  The default startup mode is Magni-\nfier Mode.\n\nNote:  The  modes  are  implemented by changing the magnifier() action.\nSwitching the mode will not work if Mouse-1 has been customized  to  an\naction sequence that does not contain the magnifier() action.\n\nMagnifier Mode\nIn  this  mode,  the  mouse buttons 1 to 5 pop up a ``magnifying\nglass'' that shows an unshrunken image of the page (i.e. an  im-\nage at the resolution determined by the option/X resource pixels\nor mfmode) at varying sizes. When the magnifier is moved,  small\nruler-like tick marks are displayed at the edges of the magnifi-\ner (unless the X resource delayRulers is set to false, in  which\ncase  the  tick  marks  are  always displayed).  The unit of the\nmarks is determined by the X resource tickUnits (mm by default).\nThis unit can be changed at runtime via the action switch-magni-\nfier-units(), by default bound to the keystroke `t' (see the de-\nscription  of that key, and of switch-magnifier-units() for more\ndetails on the units available).\nThe length of the tick marks can be changed via the  X  resource\ntickLength  (4  by default). A zero or negative value suppresses\nthe tick marks.\n\nText Selection Mode\nThis mode allows you to select a rectangular region of  text  in\nthe  DVI  file by holding down Mouse-1 and moving the mouse. The\ntext is put into the X primary selection so that it can be past-\ned into other X applications with Mouse-2 as usual.\nIf  xdvi  has been compiled with locale, nllanginfo() and iconv\nsupport, the selected text is converted into the  character  set\nof the current locale (see the output of locale -a for a list of\nlocale settings available on your system).  If nllanginfo()  is\nnot  available, but iconv is, you can specify the input encoding\nfor iconv via the X resource textEncoding  (see  the  output  of\niconv -l for a list of valid encodings). If iconv support is not\navailable, only the encodings ISO-8859-1 and UTF-8 are supported\n(these names are case-insensitive).\nNote that UTF-8 is the only encoding that can render all charac-\nters (e.g. mathematical symbols) of a DVI file. If ISO-8859-1 is\nactive,  characters that cannot be displayed are replaced by `\\'\nfollowed by the hexadecimal character code.   For  other  encod-\nings,  such  characters  may trigger iconv error messages.  If a\ncharacter is not recognized at all, it is replaced by `?'.\nTo extract larger portions of text, you can  alternatively  save\nselected  pages or the entire file in text format via the File >\nSave as ...  menu.\n\nRuler Mode\nThis mode provides a simple way of measuring  distances  on  the\npage.\nWhen  this  mode  is  activated, the mouse cursor changes into a\nthin cross, and a larger, cross-shaped ruler  is  drawn  in  the\nhighlight  color  at  the mouse location. The ruler doesn't have\nunits attached to it; instead, the current distance between  the\nruler  and  the mouse cursor is continuously printed to the sta-\ntusline.\nWhen activating Ruler Mode, the ruler is at  first  attached  to\nthe  mouse and can be moved around. It can then be positioned at\na fixed place by clicking Mouse-1.  After that, the mouse cursor\ncan  be  moved to measure the horizontal (dx), vertical (dy) and\ndirect (shortest) (dr) distance between the ruler  center  point\nand the mouse.\nClicking  Mouse-1 again will move the ruler to the current mouse\nposition, and holding down Mouse-1 will drag the ruler around.\nIn Ruler Mode, the following special keybindings extend  or  re-\nplace the default bindings:\n\no      [ruler-snap-origin()]  Snap  the ruler back to the origin\ncoordinate (0,0).\n\nt      [overrides switch-magnifier-units()] Toggle between vari-\nous ruler units, which can be specified by the X resource\ntickUnits (`mm' by default).\n\nP      [overrides  declare-page-number()]  Print  the  distances\nshown in the statusline to standard output.\n\nTOOLBAR (Motif only)\nThe  Motif  toolbar  can  also be customized. The XPM file used for the\ntoolbar icons can be  specified  via  the  resource  toolbarPixmapFile,\nwhich  should  contain  a  filename  that can be found in one of XFILE-\nSEARCHPATH or XDVIINPUTS (see the section FILE SEARCHING below for more\ninformation  on  these  variables).  Xdvi will try to split this pixmap\nhorizontally into n pieces, where each piece is as wide as  the  pixmap\nis  high  and  is treated as an image for toolbar button n.  This means\nthat each icon should be a square, and that the  entire  pixmap  should\nhave width n x h if h is the height of the pixmap.\n\nThe  resource  toolbarTranslations  can be used to map icons/buttons to\nspecific actions.  The resource should contain a  string  separated  by\nnewline characters, similar to the resources mainTranslations and menu-\nTranslations.  Every line must contain either a spacer  definition,  or\nan icon definition:\n\nA  spacer  definition  is  a string SPACER(n), where n is the number of\npixels inserted as separator to the following button.\n\nAn icon definition is a colon-separated list containing  the  following\nelements:\n\n- the index of an icon in the pixmap file (starting from zero);\n\n- a long tooltip string, displayed in the status area;\n\n- a short tooltip string, displayed as popup;\n\n-  a sequence of actions to be performed when the corresponding tool-\nbar button is pushed.\n\nTo illustrate this, the default value of toolbarTranslations  looks  as\nfollows:\n\nxdvi.toolbarTranslations: \\\nSPACER(5)\\n\\\n0:Open a new document   (Key\\\\: Ctrl-f):\\\nOpen file:select-dvi-file()\\n\\\nSPACER(10)\\n\\\n1:Reread this document   (Key\\\\: R):\\\nReread file:reread-dvi-file()\\n\\\nSPACER(10)\\n\\\n2:Go to the first page of this document   (Key\\\\: 1g):\\\nGo to first page:goto-page(1)\\n\\\n3:Go to the previous page of this document   (Key\\\\: p):\\\nGo to previous page:back-page(1)\\n\\\n4:Go to the next page of this document   (Key\\\\: n):\\\nGo to next page:forward-page(1)\\n\\\n5:Go to the last page of this document   (Key\\\\: g):\\\nGo to last page:goto-page()\\n\\\nSPACER(10)\\n\\\n6:Enlarge the display   (Key\\\\: Ctrl-+):Zoom in:\\\nset-shrink-factor(+)\\n\\\n7:Shrink the display   (Key\\\\: Ctrl--):Zoom out:\\\nset-shrink-factor(-)\\n\\\nSPACER(10)\\n\\\n8:Jump back to the previous hyperlink   (Key\\\\: B):\\\nBack hyperlink:htex-back()\\n\\\nSPACER(10)\\n\\\n10:Print this document:Print:print()\\n\\\nSPACER(10)\\n\\\n11:Toggle marks for odd pages   (Key\\\\: 1m):\\\nToggle odd:toggle-mark(1)\\n\\\n12:Toggle marks for even pages   (Key\\\\: 2m):\\\nToggle even:toggle-mark(2)\\n\\\n13:Toggle mark for current page   (Key\\\\: 2m):\\\nToggle current:toggle-mark()\\n\\\n14:Unmark all pages   (Key\\\\: 0m):\\\nUnmark all:toggle-mark(0)\\n\\\nSPACER(10)\\n\\\n18:Display fonts darker   (Key\\\\: Alt-Ctrl-+):\\\nFonts darker:change-density(5)\\n\\\n19:Display fonts lighter   (Key\\\\: Alt-Ctrl--):\\\nFonts lighter:change-density(-5)\\n\n\nWhen  the  mouse  remains over a toolbar button for a certain period, a\n`tooltip' window is shown, describing what the button  does  using  the\nshort  tooltip  string  from  the above resource. At the same time, the\nlong tooltip string is displayed in the statusline.  The appearance and\nbehaviour  of  these  tooltips  can be customized via the following re-\nsources:\n\ntipShell.background\nBackground color of the tooltip window.\n\ntipShell.fontSet\nFont used for the tooltip.\n\ntipShell.waitPeriod\nThe time (in milliseconds) the mouse pointer needs  to  be  over\nthe  button  before  the  tooltip is shown. Set it to a negative\nvalue to suppress the tooltips altogether.\n",
            "subsections": []
        },
        "GREYSCALING AND COLORMAPS": {
            "content": "The greyscale anti-aliasing feature in xdvi will not work at  its  best\nif  the display does not have enough colors available.  This can happen\nif other applications are using most of the colormap (even if they  are\niconified).   If this occurs, then xdvi will print an error message and\nturn on the -copy option.  This will result  in  overstrike  characters\nappearing wrong; it may also result in poor display quality if the num-\nber of available colors is very small.\n\nTypically this problem occurs on displays that allocate eight  bits  of\nvideo  memory  per  pixel.  To see how many bits per pixel your display\nuses, type xwininfo in an xterm window, and then click the mouse on the\nroot  window  when  asked.  The ``Depth:'' entry will tell you how many\nbits are allocated per pixel.\n\nDisplays using at least 15 bits per pixel are typically TrueColor visu-\nals, which do not have this problem, since their colormap is permanent-\nly allocated and available to all applications.  (The visual  class  is\nalso  displayed  by  xwininfo.)  For more information on visual classes\nsee the documentation for the X Window System.\n\nTo alleviate this problem, therefore, one may (a) run  with  more  bits\nper  pixel  (this may require adding more video memory or replacing the\nvideo card), (b) shut down other applications that may be using much of\nthe  colormap  and then restart xdvi, or (c) run xdvi with the -install\noption.\n\nOne application which is often the cause of this problem  is  Netscape.\nIn  this  case  there are two more alternatives to remedying the situa-\ntion.  One can run ``netscape -install'' to cause Netscape to install a\nprivate colormap.  This can cause colors to change in bizarre ways when\nthe mouse is moved to a different window.  Or, one can  run  ``netscape\n-ncols 220'' to limit Netscape to a smaller number of colors.  A small-\ner number will ensure that other applications have more  colors  avail-\nable, but will degrade the color quality in the Netscape window.\n",
            "subsections": []
        },
        "HANDLING OF POSTSCRIPT FIGURES": {
            "content": "Xdvi  can  display  Encapsulated PostScript (EPS) files included in the\ndvi file.  Such files are first searched for in the directory where the\ndvi  file is, and then using normal Kpathsea rules.  There is an excep-\ntion to this, however:  if the file name begins with  a  backtick  (`),\nthen  the  remaining  characters  in the file name give a shell command\n(often zcat) which is executed; its standard output is then sent to  be\ninterpreted as PostScript.  Since the execution of arbitrary shell com-\nmands with the user's permissions is a huge security  risk,  evaluation\nof these backtick commands is disabled by default. It needs to be acti-\nvated via the -allowshell command-line option.  NOTE: You should  never\nuse  this  option  when viewing documents that you didn't compile your-\nself. The backtick specials are not needed  for  uncompressing  gzipped\nPostScript  files,  since  xdvi  can do that on the fly if the filename\nends with .eps.gz or .eps.Z (and if the first bytes of the  file  indi-\ncate  that the file is indeed compressed).  This is both safer and more\nflexible than the backtick approach, since the default  file  searching\nrules will apply to such filenames too.\n",
            "subsections": []
        },
        "TYPE 1 FONTS": {
            "content": "Using FreeType (version 2), xdvi can render PostScript<tm> Type 1 fonts\ndirectly, without the route via TeX pixel (pk) fonts. The advantage  of\nthis  is  that  only  one size of each font needs to be stored on disk.\nUnless the -notype1fonts option is used, xdvi will try to render  every\nfont using FreeType. Only as a fallback will it invoke an external pro-\ngram (like mktexpk, which in turn may invoke utilities  like  ps2pk  or\ngsftopk)  to  generate  a pixel font from the Type 1 source. The direct\nrendering of the Computer Modern  fonts  should  work  out-of-the  box,\nwhereas  other  Type  1  fonts such as the 35 `standard' PostScript<tm>\nfonts resident in printers may need to be made accessible for use  with\nxdvi,  unless your system administrator or TeX distribution has already\ndone so (which is the case e.g. for current TeX Live systems). For  the\n35  PostScript<tm>  resident fonts, xdvik will search using the Fontmap\nprovided with Ghostscript, if necessary.  Also, the xdvik  distribution\ncomes  with a utility called t1mapper to make these fonts available for\nxdvi; see the manual page for t1mapper(1) for usage details.  This pro-\ngram is likely to be dropped in the future, however, since it is proba-\nbly not needed anymore.\n\nSPECIALS (GENERALLY)\nAny of the specials used by xdvi may  be  preceded  by  the  characters\n``xdvi:''.   Doing so does not change the behavior of the special under\nxdvi, but it tells other dvi drivers (such as e.g. dvips) to ignore the\nspecial.\n",
            "subsections": []
        },
        "SOURCE SPECIALS": {
            "content": "Some  TeX implementations or macro packages provide the facility to au-\ntomatically include so-called `source specials' into a DVI file.  These\ncontain  the  line number, eventually a column number, and the filename\nof the .tex source. This makes it possible to jump from a .dvi file  to\nthe  corresponding place in the .tex source and vice versa (also called\n`inverse search' - jumping from the DVI file to the TeX  file  is  also\nknown  as  `reverse  search',  and jumping from the TeX file to the DVI\nfile as `forward search').\n\nTo be usable with xdvi, source specials in the dvi file must  have  one\nof the following formats:\n\nsrc:line[ ]filename\nsrc:line:col[ ]filename\nsrc:line\nsrc:line:col\nsrc::col\n\nIf  filename or line are omitted, the most recent values are used.  The\nfirst source special on each page must be  in  one  of  the  first  two\nforms, since defaults are not inherited across pages.\n\nYou  will need a TeX implementation that provides an appropriate switch\n(e.g. -src) or a macro  package  (such  as  srcltx.sty  or  srctex.sty,\navailable  from  CTAN:macros/latex/contrib/supported/srcltx/) to insert\nsuch source specials into the DVI file.\n\nFor reverse search, the combination Ctrl-Mouse 1 will make xdvi open an\neditor (the value of the -editor command line option) with the file and\nthe line number of the .tex source. See the description of the  -editor\noption for more information and example settings.\n\nFor  forward  search, xdvi has a -sourceposition option that makes xdvi\njump to the page in the DVI file corresponding to the  given  line  (or\nthe  closest  line  having  a source special) of the specified file and\nhighlight the found region. See the description of the  -sourceposition\noption for more details.\n\nMore information on setting up various editors for use with source spe-\ncials can be found at:\n\nhttp://xdvi.sourceforge.net/inverse-search.html\n",
            "subsections": []
        },
        "PAPERSIZE SPECIALS": {
            "content": "xdvi accepts specials to set the paper size for  the  document.   These\nspecials should be of the form\n\npapersize=[*]width,height\n\nwhere  width and height give the width and height of the paper, respec-\ntively.  Each of these should appear in the form of  a  decimal  number\nfollowed  by  any of the two-letter abbreviations for units accepted by\nTeX (pt, pc, in, bp, cm, mm, dd, cc, or sp).  If an  asterisk  (*)  ap-\npears  just  before the width, then the measurements refer to the docu-\nment dimensions (e.g. pt as opposed to truept).  This  allows  a  macro\npackage  to  vary  the page size according to elements of the document;\ne.g.\n\n\\special{xdvi: papersize=*\\number\\wd\\mybox sp,\n\\number\\ht\\mybox sp}\n\nExcept for the asterisk, this format is compatible with dvips.\n\nThe last papersize special on a page determines the size of that  page.\nIf  there is no such special on a given page, the most recent papersize\nis used, or, if there are no papersize specials on any preceding  page,\nthen  the  value of the paper resource (or -paper option on the command\nline) is used.  Thus the paper size may vary for different pages of the\ndvi file.\n\nIf  the  paper  resource  (or -paper command-line option) begins with a\nplus sign (`+'), then all papersize specials in the dvi  file  are  ig-\nnored.\n",
            "subsections": []
        },
        "COLOR SPECIALS": {
            "content": "The color specials supported by xdvi are the same as those supported by\ndvips, except that the literal PostScript color  specification  (as  in\nthe  AggiePattern example in the dvips documentation) is not supported.\nThere are also some restrictions due to the way xdvi's   drawing   rou-\ntines  are  implemented; e.g. the \\colorbox and \\fcolorbox macros don't\nwork with xdvi.  See the section LIMITATIONS below for more information\non  these restrictions.  Xdvi supports the same list of named colors as\ndvips does, namely:\n\nApricot, Aquamarine, Bittersweet, Black, Blue,  BlueGreen,  BlueViolet,\nBrickRed, Brown, BurntOrange, CadetBlue, CarnationPink, Cerulean, Corn-\nflowerBlue, Cyan, Dandelion, DarkOrchid, Emerald, ForestGreen, Fuchsia,\nGoldenrod,  Gray, Green, GreenYellow, JungleGreen, Lavender, LimeGreen,\nMagenta, Mahogany, Maroon,  Melon,  MidnightBlue,  Mulberry,  NavyBlue,\nOliveGreen,  Orange,  OrangeRed,  Orchid, Peach, Periwinkle, PineGreen,\nPlum, ProcessBlue, Purple, RawSienna, Red, RedOrange,  RedViolet,  Rho-\ndamine,  RoyalBlue,  RoyalPurple,  RubineRed,  Salmon, SeaGreen, Sepia,\nSkyBlue, SpringGreen, Tan, TealBlue, Thistle, Turquoise, Violet, Viole-\ntRed, White, WildStrawberry, Yellow, YellowGreen, YellowOrange.\n\nNote that these names are case sensitive.\n\nThe  documentation  of the LaTeX color package provides more details on\nhow to use such specials with LaTeX; see the dvips documentation for  a\ndetailed description of the syntax and semantics of the color specials.\n",
            "subsections": []
        },
        "SIGNALS": {
            "content": "When xdvi receives a SIGUSR1 signal, it rereads the dvi file.\n",
            "subsections": []
        },
        "ENVIRONMENT": {
            "content": "Xdvik  uses the same environment variables and algorithms for searching\nfor font files as TeX and  friends.   See  the  documentation  for  the\nKpathsea library, kpathsea.dvi, for a detailed description of these.\n\nIn addition, xdvik accepts the following variables:\n\nDISPLAY\nSpecifies which graphics display terminal to use.\n\nKPATHSEADEBUG\nTrace  Kpathsea  lookups;  set it to -1 (= all bits on) for com-\nplete tracing.\n\nEXTENSIONMAPS\nA list of files to be searched for mime types  entries  (as  for\nAcrobat Reader).  Earlier entries in one of these files override\nlater ones.  If this variable is not set, the following  default\npath is used:\n\n$HOME/.mime.types:/etc/mime.types:\\\n/usr/etc/mime.types:/usr/local/etc/mime.types\n\nMAILCAPS\nA  list  of files to be searched for mailcap entries, as defined\nby RFC 1343. See this RFC or the mailcap(4) manual  page  for  a\ndetailed description of the mailcap file format.  Currently, on-\nly the following mailcap features are supported:\n\ntest=command\nThe entry is only used if command can be executed via the\nsystem() call and if the system() call returns with value\n0 (success).  The command string may contain  the  format\nstring %s, which will be replaced by the file name.\n\nneedsterminal\nIf  this  flag is used, the command will be executed in a\nnew xterm window by prepending ``xterm -e '' to the  com-\nmand string.\n\nAll other fields in the mailcap entry are ignored by xdvi.  Ear-\nlier entries in one of these files override later ones.  If  the\nvariable is not defined, the following default path is used:\n\n$HOME/.mailcap:/etc/mailcap:/usr/etc/mailcap:\\\n/usr/local/etc/mailcap\n\nFor  security  reasons, some special characters (i.e. ( ) ` \\ ;)\nare escaped in the argument before passing it to system().\n\nBROWSER\nDetermines the web browser used to open external links (i.e. all\nURLs  that don't start with the `file:' scheme and are not rela-\ntive links in the local DVI file), and to open links  for  which\nno  viewer has been specified in the mailcap files. The value of\nthis variable is a colon-separated list of commands.  Xdvi  will\ntry  each  of  them in sequence until one succeeds (i.e. doesn't\nimmediately return with status 0). This allows  you  to  specify\nyour  favourite  browser at the beginning, and fallback browsers\nat the end. Every occurrence of %s in the string is replaced  by\nthe  target  URL; every occurrence of %% is replaced by a single\n%.  If no %s is present, the URL string is added as an extra ar-\ngument.\nAn example setting is:\n\nnetscape  -raise  -remote 'openURL(%s,new-window)':xterm -e lynx\n%s:xterm -e wget %s:lynx %s:wget %s\n\nSee\n\nhttp://www.catb.org/~esr/BROWSER/\n\nfor more details on the BROWSER environment variable.\n\nGSLIB A colon-separated list of  directories  to  search  for  Fontmap\nfiles,  etc.,  as used for Ghostscript.  It has the same meaning\nas it does when running Ghostscript.  In xdvik, it is used  when\nsearching  for font files when the map file does not give a file\nname for the font (this should be quite rare).  The  command  gs\n-h  will list the default value that Ghostscript uses.  See also\nthe XDVIGSLIB environment variable (below).\n\nXDVIGSLIB\nThis has the same effect as GSLIB but affects only  xdvi.   Use\nthis when you want to use a different value for GSLIB when run-\nning xdvi, but use either the compiled-in default value or  some\nother  value  when  running Ghostscript.  If both GSLIB and XD-\nVIGSLIB are set, then xdvi uses XDVIGSLIB.  To use  the  de-\nfault value compiled in to xdvi while still retaining the abili-\nty to set GSLIB for use  with  Ghostscript,  you  can  set  XD-\nVIGSLIB to the empty string.\n\nTMPDIR The  directory  to  use for storing temporary files created when\nuncompressing PostScript files.\n\nXEDITOR\nDetermines the editor command used for source  special  `reverse\nsearch', if neither the -editor command-line option nor the .ed-\nitor resource are  specified.   See  the description of the -ed-\nitor command line option for details on the format.\n\nVISUAL Determines  an editor to be opened in an xterm window if neither\nof -editor, .editor, or XEDITOR is specified.\n\nEDITOR Determines an editor to be opened in an xterm window if  neither\nof -editor, .editor, XEDITOR or VISUAL is specified.\n\nWWWBROWSER\nObsolete; use BROWSER instead.\n",
            "subsections": []
        },
        "LIMITATIONS": {
            "content": "xdvi  accepts many but not all types of PostScript specials accepted by\ndvips.  For example, it accepts most specials generated by epsf and ps-\nfig.   It  does not, however, support bop-hook or eop-hook, nor does it\nallow PostScript commands to affect the rendering of  things  that  are\nnot PostScript (for example, the ``NEAT'' and rotated ``A'' examples in\nthe dvips manual).  These restrictions are due to the design  of  xdvi;\nin all likelihood they will always remain.\n\nLaTeX2e rotation specials are currently not supported.\n\nMetaPost files containing included text are not supported.\n\nXdvi's  color  handling  doesn't  support  the \\colorbox and \\fcolorbox\nmacros;  this is not likely to change in the  near  future.  This  also\nmeans  that   e.g.  colored tables (as created by the colortbl package)\nmay render incorrectly: Text in colors different from the default fore-\nground color may not be displayed. When the page is redrawn (e.g. after\nusing the magnifier), the background color of the  cells  may  overdraw\nthe text.\n",
            "subsections": []
        },
        "FILES": {
            "content": "$HOME/.xdvirc\nA  file  that  holds  all settings that the user changed via the\nkeys, the `Options' and the Xaw `Modes' menu and the dialogs, as\nX   resources.   These   resources   override  the  settings  in\n$HOME/.Xdefaults.  This file is ignored if the -q option is used\nor the noInitFile X resource is set.\n\nconfig.xdvi\nAn  optional configuration file for the Type 1 font setup, which\nspecifies dvips-style map files specific to xdvik.  If used,  it\nshould  be  present in the directory determined by the TEXCONFIG\nenvironment variable.  Its format is  similar  to  configuration\nfiles for dvips, except that it is only scanned for the names of\nmap files (p and p+ directives).\n",
            "subsections": []
        },
        "SEE ALSO": {
            "content": "X(1), dvips(1), mktexpk(1), ps2pk(1),  gsftopk(1),  t1mapper(1),  mail-\ncap(4),  the  Kpathsea  documentation, https://ctan.org/pkg/xdvi/.  and\nthe Xdvik home page at http://xdvi.sourceforge.net/.\n",
            "subsections": []
        },
        "AUTHORS": {
            "content": "Eric Cooper, CMU, did a version for direct output to a  QVSS.  Modified\nfor  X  by Bob Scheifler, MIT Laboratory for Computer Science. Modified\nfor X11 by Mark Eichin, MIT SIPB. Additional enhancements by many  oth-\ners.\n\nThe  current maintainer of the original xdvi is Paul Vojta, U.C. Berke-\nley.\n\nCode for the xdvik variant has been contributed by many  people,  whose\nnames are scattered across the source files.\n\nFor the most up-to-date information, please visit:\n\nhttp://xdvi.sourceforge.net\n\nPlease report all bugs to the SourceForge bug tracker:\n\nhttp://sourceforge.net/tracker/?func=add&groupid=23164&atid=377580\n\nXdvik 22.87.04                    2020-02-29                           XDVI(1)",
            "subsections": []
        }
    },
    "summary": "xdvi - DVI Previewer for the X Window System",
    "flags": [
        {
            "flag": "",
            "long": null,
            "arg": null,
            "description": "(.allowShell) This option enables the shell escape in PostScript specials. (For security reasons, shell escapes are disabled by default.) This option should be rarely used; in particular it should not be used just to uncompress files: that function is done automatically if the file name ends in .Z, .gz, or .bz2. Shell escapes are always turned off if the -safer option is used. -altfont font (.altFont) Declares a default font to use when the font in the dvi file cannot be found. This is useful, for example, with PostScript <tm> fonts. -anchorposition anchor Jump to anchor after opening the DVI file. This is only useful when invoking xdvi from other applications. -background color (.background) Determines the color of the background. Same as -bg. -bg color (.background) Determines the color of the background. -browser browser (.wwwBrowser) Defines the web browser used for handling external URLs. The value of this option or resource has the same syntax as the BROWSER environment variable; see the explanation of that variable in the section `ENVIRONMENT' below for a detailed de- scription. If neither the option nor the X resource wwwBrowser is specified, the environment variables BROWSER and WWWBROWSER (in that order) are used to determine the browser command. If these are not set either, the following default value is used: xdg-open %s:htmlview %s:firefox -remote -remote \"openURL(%s,new- window)\":mozilla -remote \"openURL(%s,new-window)\":netscape -raise -remote \"openURL(%s,new-window)\":xterm -e w3m %s:xterm -e lynx %s:xterm -e wget %s -copy (.copy) Always use the copy operation when writing characters to the display. This option may be necessary for correct operation on a color display, but overstrike characters will be incorrect. If greyscale anti-aliasing is in use, the -copy operation will disable the use of colorplanes and make overstrikes come out in- correctly. See also -thorough. -cr color (.cursorColor) Determines the color of the mouse cursor. The default is the same as the foreground color. -debug bitmask|string[,string ...] (.debugLevel) If nonzero, prints additional information on stan- dard output. The argument can be either a bitmask specified as a decimal number, or comma-separated list of strings. For the bitmask representation, multiple values can be specified by adding the numbers that represent the individual bits; e.g. to debug all file searching and opening commands, use 4032 (= 2048 + 1024 + 512 + 256 + 128 + 64). Use -1 to turn on debugging of everything (this will produce huge output). For the string representation, use the strings listed in the following table, with a comma to separate the values; e.g. to debug all file searching and opening commands, use search,ex- pand,paths,hash,stat,open. (The option `kpathsea' is provided as a shorthand for these.) Note that such a list may need to be quoted to prevent the shell from interpreting commas or spaces in the list. The individual numbers and strings have the following meanings: 1 bitmap Bitmap creation 2 dvi DVI translation 4 pk PK fonts 8 batch Batch mode: Exit after reading the DVI file 16 event Event handling 32 ps PostScript interpreter calls 64 stat Kpathsea stat(2) calls 128 hash Kpathsea hash table lookups 256 open Kpathsea file opening 512 paths Kpathsea path definitions 1024 expand Kpathsea path expansion 2048 search Kpathsea searching 4032 kpathsea All Kpathsea options 4096 htex Hypertex specials 8192 src Source specials 16384 client Client/server mode (see -unique and -sourceposition options) 32768 ft FreeType library messages (Type 1 fonts) 65536 ftverbose Verbose FreeType library messages (currently unused) 131072 gui GUI elements Some of the Kpathsea debugging options are actually provided by Kpathsea; see the Debugging section in the Kpathsea manual for more information on these. -density density (.densityPercent) Determines the density used when shrinking bitmaps for fonts. A higher value produces a lighter font. The default value is 40. If greyscaling is in use, this argument does not apply; use -gamma instead. See also the `S' keystroke. Same as -S. -display host:display Specifies the host and screen to be used for displaying the dvi file. By default this is obtained from the environment variable DISPLAY. -dvipspath path (.dvipsPath) Use path as the dvips program to use when printing. The default for this is dvips. The program or script should read the DVI file from standard input, and write the PostScript file to standard output. -editor editor (.editor) Specifies the editor that will be invoked when the source-special() action is triggered to start a reverse search (by default via Ctrl-Mouse 1). The argument to this option is a format string in which occurrences of ``%f'' are replaced by the file name, occurrences of ``%l'' are replaced by the line number within the file, and optional occurrences of ``%c'' are replaced by the column number within the line. If neither the option nor the X resource .editor is specified, the following environment variables are checked to determine the editor command: XEDITOR, VISUAL, and EDITOR (in this sequence). If the string is found as the value of the VISUAL or EDITOR en- vironment variables, then ``xterm -e '' is prepended to the string; if the editor is specified by other means, then it must be in the form of a shell command to pop up an X window with an editor in it. If none of these variables is set, a warning mes- sage is displayed and the command ``xterm -e vi +%l %f'' is used. If no ``%f'' or ``%l'' occurs in the string, the missing format strings are appended automatically. (This is for compatibility with other programs when using one of the environment vari- ables). A new instance of the editor is started each time this command is used; therefore it is preferable to use an editor that can be invoked in `client' mode to load new files into the same in- stance. Example settings are: emacsclient --no-wait (older Emacsen) gnuclient -q (XEmacs and newer Emacsen) gvim --servername xdvi --remote (VIM v6.0+; the `--servername xdvi' option will cause gvim to run a dedicated instance for the files opened by xdvi.) nc (nedit) Note that those strings need to be enclosed into quotes when us- ing them on the command-line to protect them from the shell; when using them as argument for the .editor resource in an X re- source file, no quotes should be used. NOTE ON SECURITY: The argument of this option isn't executed as a shell command, but via exec() to prevent evil tricks with the contents of source specials."
        },
        {
            "flag": "",
            "long": null,
            "arg": null,
            "description": "This option is only supported for backwards compatibility; it is equivalent to -expertmode 0, which should be preferred. -expertmode flag (.expertMode) With an argument of 0, this option switches off the display of the buttons, scrollbars, the toolbar (Motif on- ly), the statusline and the page list. These GUI elements can also be (de)activated separately, by combining the appropriate values in the flag argument. This acts similar to the -debug op- tion: The integer flag is treated as a bitmap where each bit represents one element. If the bit has the value 1, the element is switched on, if it has the value 0, the element is switched off. The meaning of the bits is as follows: 1 statusline 2 scrollbars 4 Motif: pagelist, Xaw: buttons and pagelist 8 toolbar (Motif only) 16 menubar (Motif only) For example, to turn on only the statusline and the scrollbars, use 3 (= 1 + 2). See also the `x' keystroke, where the bits are addressed by their positions, from 1 to 3 (Xaw) or 5 (Motif), respectively. If the statusline is not active, all messages that would normally be printed to the statusline will be printed to stdout, unless the -hush- stdout option is used. -fg color (.foreground) Determines the color of the text (foreground). -findstring string This option triggers a search for string in the DVI file men- tioned on the command-line, similar to forward search (see the description of the sourceposition option): If there is already another instance of xdvi running on the displaying that DVI file, it will cause that instance to perform the search instead. The search starts at the top of the current page of the DVI file. -font font (*font) Sets the font used in menus, buttons etc., as described in the X(7x) man page. The font for child windows can be set separately, e.g.: xdvi*statusline*font: \\ -*-helvetica-medium-r-*-*-12-*-*-*-*-*-*-* -foreground color Same as -fg."
        },
        {
            "flag": "",
            "long": null,
            "arg": null,
            "description": "When this option is used, xdvi will (try to) run in fullscreen mode, with no window decorations. This option is not guaranteed to work with all windowmanagers/desktops; if you're experiencing problems with it, please use the -geometry option instead, and a suitable window manager setting to remove the window decora- tions. When using this option for presentations, you might want to get rid of all the control widgets as well, using the -ex- pertmode option. This option can also be toggled at runtime us- ing the fullscreen action (by default bound to Ctrl-l). -gamma gamma (.gamma) Controls the interpolation of colors in the greyscale anti-aliasing color palette. Default value is 1.0. For 0 < gamma < 1, the fonts will be lighter (more like the background), and for gamma > 1, the fonts will be darker (more like the fore- ground). Negative values behave the same way, but use a slight- ly different algorithm. For color and grayscale displays; for monochrome, see -density. See also the `S' keystroke. -geometry geometry (.geometry) Specifies the initial geometry of the main window, as described in the X(7x) man page. The geometry of child win- dows can be set separately, e.g.: xdvi*helpwindow.geometry: 600x800"
        },
        {
            "flag": "",
            "long": null,
            "arg": null,
            "description": "(.gsAlpha) Causes Ghostscript to be called with the x11alpha driver instead of the x11 driver. The x11alpha driver enables anti-aliasing in PostScript specials, for a nicer appearance. It is available on newer versions of Ghostscript. This option can also be toggled with the `V' keystroke. -gspalette palette (.palette) Specifies the palette to be used when using Ghost- script for rendering PostScript specials. Possible values are Color, Greyscale, and Monochrome. The default is Color."
        },
        {
            "flag": "-h",
            "long": "--help",
            "arg": null,
            "description": "Prints a short help text with an overview of the command-line options to standard output. -hl color (.highlight) Determines the color of the page border, of the ruler in `ruler mode', and of the highlighting markers in for- ward search and string search. The default is the foreground color. -hush (.Hush) Causes xdvi to suppress all suppressible warnings."
        },
        {
            "flag": "",
            "long": null,
            "arg": null,
            "description": "(.hushBell) Don't sound the X bell when an error occurs."
        },
        {
            "flag": "",
            "long": null,
            "arg": null,
            "description": "(.hushLostChars) Causes xdvi to suppress warnings about refer- ences to characters which are not defined in the font."
        },
        {
            "flag": "",
            "long": null,
            "arg": null,
            "description": "(.hushChecksums) Causes xdvi to suppress warnings about checksum mismatches between the dvi file and the font file."
        },
        {
            "flag": "",
            "long": null,
            "arg": null,
            "description": "(.hushStdout) Suppresses printing of status messages to stdout. Note that errors or warnings will still be printed to stderr even if this option is used. -icongeometry geometry (.iconGeometry) Specifies the initial position for the icon."
        },
        {
            "flag": "",
            "long": null,
            "arg": null,
            "description": "(.iconic) Causes the xdvi window to start in the iconic state. The default is to start with the window open."
        },
        {
            "flag": "",
            "long": null,
            "arg": null,
            "description": "(.install) If xdvi is running under a PseudoColor visual, then (by default) it will check for TrueColor visuals with more bits per pixel, and switch to such a visual if one exists. If no such visual exists, it will use the current visual and colormap. If -install is selected, however, it will still use a TrueColor visual with a greater depth, if one is available; otherwise, it will install its own colormap on the current visual. If the current visual is not PseudoColor, then xdvi will not switch the visual or colormap, regardless of its options. The default val- ue of the install resource is the special value, maybe. There is no +install option. See also -noinstall, and the GREYSCALING AND COLORMAPS section. -interpreter filename (.interpreter) Use filename as the Ghostscript interpreter. By default it uses gs. -keep (.keepPosition) Sets a flag to indicate that xdvi should not move to the home position when moving to a new page. See also the `k' keystroke. This flag is honored by all page switching actions and by up-or-previous() / down-or-next(), although the latter only honor the horizontal position, not the vertical one. This allows for a \"continuous\" scrolling back an forth through a document with a display window narrower than a page width. -l (.listFonts) List the names of all fonts used."
        },
        {
            "flag": "",
            "long": null,
            "arg": null,
            "description": "Prints licensing information."
        },
        {
            "flag": "",
            "long": null,
            "arg": null,
            "description": "(.linkColor) Color used for unvisited hyperlinks (`Blue2' by de- fault). Hyperlinks are unvisited before you click on them, or after the DVI file has been reloaded. The value should be ei- ther a valid X color name (such as DarkGoldenrod4) or a hexadec- imal color string (such as #8b6508). See also -visitedlinkcolor and -linkstyle."
        },
        {
            "flag": "",
            "long": null,
            "arg": null,
            "description": "(.LinkStyle) Determines the style in which hyperlinks are dis- played. Possible values and their meanings are: 0 No highlighting of links 1 Underline links with link color 2 No underlining, color text with link color 3 Underline and display text colored with link color The values for link color are specified by the options/resources -linkcolor and -visitedlinkcolor (which see). -margins dimen (.Margin) Specifies the size of both the top margin and side margin. This determines the ``home'' position of the page with- in the window as follows. If the entire page fits in the win- dow, then the margin settings are ignored. If, even after re- moving the margins from the left, right, top, and bottom, the page still cannot fit in the window, then the page is put in the window such that the top and left margins are hidden, and pre- sumably the upper left-hand corner of the text on the page will be in the upper left-hand corner of the window. Otherwise, the text is centered in the window. The dimension should be a deci- mal number optionally followed by any of the two-letter abbrevi- ations for units accepted by TeX (pt, pc, in, bp, cm, mm, dd, cc, or sp). By default, the unit will be cm (centimeters). See also -sidemargin, -topmargin, and the keystroke `M.' -mfmode mode-def (.mfMode) Specifies a mode-def string, which can be used in searching for fonts (see ENVIRONMENT, below). Generally, when changing the mode-def, it is also necessary to change the font size to the appropriate value for that mode. This is done by adding a colon and the value in dots per inch; for example, -mf- mode ljfour:600. This method overrides any value given by the pixelsPerInch resource or the -p command-line argument. The metafont mode is also passed to metafont during automatic cre- ation of fonts. By default, it is unspecified. -mgs size Same as -mgs1. -mgs[n] size (.magnifierSize[n]) Specifies the size of the window to be used for the ``magnifying glass'' for Button n. The size may be giv- en as an integer (indicating that the magnifying glass is to be square), or it may be given in the form widthxheight. See the MOUSE ACTIONS section. Defaults are 200x150, 400x250, 700x500, 1000x800, and 1200x1200."
        },
        {
            "flag": "",
            "long": null,
            "arg": null,
            "description": "(.mouseMode) Specifies the default mode of xdvi at startup: Mag- nifier (0), Text Selection Mode (1) or Ruler Mode (2). See the section MODES, below, for more information."
        },
        {
            "flag": "",
            "long": null,
            "arg": null,
            "description": "(.color) Turns off the use of color specials. This option can be toggled with the `C' keystroke. (Note: -nocolor corresponds to color:off; +nocolor to color:on.)"
        },
        {
            "flag": "",
            "long": null,
            "arg": null,
            "description": "(.fork) With the -sourceposition and -unique options, the de- fault behavior is for xdvi to put itself into the background (like a daemon) if there is no appropriate instance of xdvi al- ready running. This argument makes it run in the foreground in- stead. This is useful for debugging, or if your client applica- tion cannot deal well with a program self-backgrounding itself in this way -- e.g. the IPC functions in emacs are known to have problems with this. If no -sourceposition or -unique argument is given, then this option has no effect. (Note: -nofork corre- sponds to fork:off; +nofork to fork:on.)"
        },
        {
            "flag": "",
            "long": null,
            "arg": null,
            "description": "(.ghostscript) Inhibits the use of Ghostscript for displaying PostScript<tm> specials. (Note: -noghostscript corresponds to ghostscript:off; +noghostscript to ghostscript:on.)"
        },
        {
            "flag": "",
            "long": null,
            "arg": null,
            "description": "(.grey) Turns off the use of greyscale anti-aliasing when print- ing shrunken bitmaps. (Note: -nogrey corresponds to grey:off; +nogrey to grey:on.) See also the `G' keystroke."
        },
        {
            "flag": "",
            "long": null,
            "arg": null,
            "description": "(.gsSafer) Normally, if Ghostscript is used to render PostScript specials, the Ghostscript interpreter is run with the option -dSAFER. The -nogssafer option runs Ghostscript without -dSAFER. The -dSAFER option in Ghostscript disables PostScript operators such as deletefile, to prevent possibly malicious PostScript programs from having any effect. If the -safer op- tion is specified, then this option has no effect; in that case Ghostscript is always run with -dSAFER. (Note: -nogssafer cor- responds to gsSafer:off; +nogssafer to gsSafer:on.)"
        },
        {
            "flag": "",
            "long": null,
            "arg": null,
            "description": "(.install) Inhibit the default behavior of switching to a True- Color visual if one is available with more bits per pixel than the current visual. (Note: -noinstall corresponds install:off; there is no +noinstall option.) See also -install, and the GREYSCALING AND COLORMAPS section."
        },
        {
            "flag": "",
            "long": null,
            "arg": null,
            "description": "(.makePk) Turns off automatic generation of font files that can- not be found by other means. (Note: -nomakepk corresponds to makePk:off; +nomakepk to makePK:on.)"
        },
        {
            "flag": "",
            "long": null,
            "arg": null,
            "description": "(.matchInverted) Don't highlight string search matches in in- verted color; instead, draw a rectangle in highlight color (see the -hl option) around the match. This option is activated auto- matically if the display isn't running in TrueColor. (Note: -nomatchinverted corresponds to matchInverted:off; +nomatchin- verted to matchInverted:on.)"
        },
        {
            "flag": "",
            "long": null,
            "arg": null,
            "description": "(.omega) This will disable the use of Omega extensions when in- terpreting DVI files. By default, the additional opcodes 129 and 134 are recognized by xdvi as Omega extensions and inter- preted as requests to set 2-byte characters. The only drawback is that the virtual font array will require 65536 positions in- stead of the default 256 positions, i.e. the memory requirements of xdvi will be slightly larger. If you find this unacceptable or encounter another problem with the Omega extensions, you can switch this extension off by using -noomega (but please do send a bug report if you find such problems - see the bug address in the AUTHORS section below). (Note: -noomega corresponds to omega: off; +noomega to omega: on.)"
        },
        {
            "flag": "",
            "long": null,
            "arg": null,
            "description": "(.prescan) By default, xdvi does a preliminary scan of the dvi file to process any papersize specials; this is especially im- portant at startup since the paper size may be needed to deter- mine the window size. If PostScript<tm> is in use, then pres- canning is also necessary in order to properly process header files. In addition, prescanning is needed to correctly deter- mine the background color of a page. This option turns off such prescanning. (Prescanning will be automatically be turned back on if xdvi detects any of the specials mentioned above.) (Note: -noscan corresponds to prescan:off; +noscan to prescan:on.)"
        },
        {
            "flag": "",
            "long": null,
            "arg": null,
            "description": "(.tempFile) As mentioned in the section DESCRIPTION above, xdvi will create a temporary copy of the DVI file so that it can be accessed without interruptions even while the file is being rewritten by TeX. Since this introduces the overhead of copying the file every time it has changed, the -notempfile allows you to turn off this behaviour. In this case, exposing parts of the window while the DVI file is being written by TeX will erase the current window contents until the DVI file can be completely reread. (Note: -notempfile corresponds to tempFile:off; +notempfile to tempFile:on.)"
        },
        {
            "flag": "",
            "long": null,
            "arg": null,
            "description": "(.type1) This will disable the use of the FreeType library to display PostScript<tm> Type 1 fonts. Use this option as a work- around when you encounter problems with the display of Type 1 fonts (but please don't forget to send a bug report in this case, to the URL mentioned in the section AUTHORS below). (Note: -notype1fonts corresponds to type1:off; +notype1fonts to type1:on.)"
        },
        {
            "flag": "",
            "long": null,
            "arg": null,
            "description": "(.xi2Scrolling) This will disable the use of high-resolution scrolling using the XInput 2.1 features of the X Server. When enabled, horizontal and vertical scrolling is done in smaller increments than would correspond to a single click of a mouse wheel. This is only available for hardware that supports the feature, generally touchpads. It is not available for tradi- tional wheel mice. If suitable hardware is not present or if the X server does not support XInput 2.1 or higher, then the high-resolution scrolling feature is turned off and has no ef- fect. (Note: -noxi2scrolling corresponds to xi2Scrolling:off; +noxi2scrolling, to xi2Scrolling:on.) -offsets dimen (.Offset) Specifies the size of both the horizontal and vertical offsets of the output on the page. By decree of the Stanford TeX Project, the default TeX page origin is always 1 inch over and down from the top-left page corner, even when non-American paper sizes are used. Therefore, the default offsets are 1.0 inch. The argument dimen should be a decimal number optionally followed by any of the two-letter abbreviations for units ac- cepted by TeX (pt, pc, in, bp, cm, mm, dd, cc, or sp). By de- fault, the unit will be cm (centimeters). See also -xoffset and -yoffset. -p pixels (.pixelsPerInch) Defines the size of the fonts to use, in pixels per inch. The default value is 600. This option is provided only for backwards compatibility; the preferred way is to set both the resolution and the Metafont mode via the -mfmode option (which see). -paper papertype (.paper) Specifies the size of the printed page. Note that in most cases it's best to specify the paper size in the TeX input file via the line \\usepackage[dvips]{geometry} which will be recognized by both dvips and xdvi; in that case the use of a `-paper' option should be unnecessary. The paper size may be specified in the form widthxheight option- ally followed by a unit, where width and height are decimal num- bers giving the width and height of the paper, respectively, and the unit is any of the two-letter abbreviations for units ac- cepted by TeX (pt, pc, in, bp, cm, mm, dd, cc, or sp). By de- fault, the unit is cm (centimeters). There are also synonyms which may be used: us (8.5x11in), legal (8.5x14in), foolscap (13.5x17in), as well as the ISO sizes a1-a7, b1-b7, c1-c7. Each of these also has a landscape or `ro- tated' variant: usr (11x8.5in), a1r-a7r, etc. For compatibility with dvips, the formats letter (8.5x11in), ledger (17x11in) and tabloid (11x17in) are also supported (these don't have rotated variants). Any of the above sizes may be preceded by a plus sign (`+'); this causes the paper size given here to override any paper size given in the dvi file. The default paper size is 21 x 29.7 cm (A4 size). -pause (.pause) This option provides a simple implementation of incre- mental (stepwise) display, which can be used for presentations. When this option is used, xdvi will pause the display of the current page whenever it encounters a special special-string (xdvi:pause by default; the string can be customized via -paus- especial, see below), and the cursor will change its shape. The action unpause-or-next() (by default bound to the Space key) will display the next portion of the page up to the following special-string, or until the end of the page is reached. When the option is not used, specials containing special-string will be ignored. -pausespecial special-string (.pauseSpecial) Sets the special string that causes xdvi to pause when the -pause option is active. The default value of special-string is xdvi:pause. -postscript flag (.postscript) If flag = 0, rendering of PostScript<tm> specials is disabled; instead, bounding boxes will be displayed (if available). A value of 1 (the default) switches PostScript<tm> specials on. With a value of 2, the PostScript<tm> specials are displayed along with their bounding boxes; this allows you to visually check the correctness of the bounding boxes. The values can also be toggled at runtime with the `v' keystroke and the corresponding numerical prefix arguments 0, 1 and 2. -ps2pdfpath path (.ps2pdfPath) Use path as a conversion program from PostScript to PDF. The program or script should accept two command-line ar- guments: The PostScript file as first argument, and the PDF out- put file as second argument. -rulecolor color (.ruleColor) Determines the color of the rules used for the mag- nifier (default: foreground color). -q (.noInitFile) Ignore the $HOME/.xdvirc startup file (i.e. don't read it at startup, and don't write it at exit). This forces the defaults defined in $HOME/.Xdefaults to be used. See FILES for more information on $HOME/.xdvirc. -rv (.reverseVideo) Causes the page to be displayed with white char- acters on a black background, instead of vice versa. -S density (.densityPercent) Same as -density (which see). -s shrink (.shrinkFactor) Defines the initial shrink factor. The default value is 8. If shrink is given as 0, then the initial shrink factor is computed so that the page fits within the window (as if the `s' keystroke were given without a number). -safer (.safer) This option turns on all available security options; it is designed for use when xdvi is called by a browser that ob- tains a dvi or TeX file from another site. This option selects +nogssafer and +allowshell. -sidemargin dimen (.sideMargin) Specifies the side margin (see -margins). -sourceposition line[:col][ ]filename This option makes xdvi search in the dvi file for the place cor- responding to the indicated line (and, optionally, column) in the .tex source file, and highlight the place found by drawing a rectangle in the highlight color (see the -hl option) around the corresponding text. In addition, when run with this argument (and the -nofork option is not given, which see), xdvi will al- ways return immediately: if it finds another instance of xdvi already showing dvifile, then it will cause that instance to raise its window and move to the given place in the dvi file; otherwise it will start up its own instance in the background. If several instances of xdvi are displaying the respective dvi file, the instance which was last raised to the foreground will be used. The space before filename is only needed if the filename starts with a digit. When the space is used, the argument needs to be enclosed in quotes to prevent the shell from misinterpreting the space as argument separator. This option requires that dvifile be prepared with source spe- cial information. See the section on SOURCE SPECIALS for de- tails on how to do this. Here is a more detailed description of how the filename in the -sourceposition argument is matched with the filename in the source specials: 1. If neither of the filenames contains a path name component, the filenames are compared ignoring the `.tex' extensions in both filenames. 2. Otherwise, if one of the filenames does contain a path compo- nent (e.g.: ./test.tex, ../test.tex, /my/homedir/tex/test.tex or any combination of these), both filenames are expanded to a full path, with any occurrences of ../ and ./ expanded, and multiple slashes removed. The pathname in the -sourceposition is expanded relative to the current working directory of the xdvi -sourceposition in- vocation, and the pathnames in the source specials are ex- panded relative to the path of the current DVI file being viewed. The path names are then compared ignoring the `.tex' exten- sions in both path names."
        },
        {
            "flag": "",
            "long": null,
            "arg": null,
            "description": "(.statusline) This option is obsolete; use -expertmode flag in- stead (which see). -text-encoding encoding (.textEncoding) Use encoding as the text encoding of the string in the \"Find\" window. Usually, this should not be needed since the encoding is determined from the locale settings."
        },
        {
            "flag": "",
            "long": null,
            "arg": null,
            "description": "(.thorough) Xdvi will usually try to ensure that overstrike characters (e.g. \\notin) are printed correctly. On monochrome displays, this is always possible with one logical operation, either and or or. On color displays, however, this may take two operations, one to set the appropriate bits and one to clear other bits. If this is the case, then by default xdvi will in- stead use the copy operation, which does not handle overstriking correctly. The -thorough option chooses the slower but more correct choice. See also -copy. -topmargin dimen (.topMargin) Specifies the top and bottom margins (see -mar- gins)."
        },
        {
            "flag": "",
            "long": null,
            "arg": null,
            "description": "(.unique) This option will make another instance of xdvi running on the same display act as a `server'. For example, the invoca- tion xdvi -unique +5 file.dvi will cause this other instance to load file.dvi on page 5 in place of the file that it is currently displaying. If there is already another instance of xdvi already displaying the file file.dvi, then it will just jump to page 5. If the other in- stance of xdvi is displaying a different file, it will load file.dvi instead. Otherwise, if no other instance of xdvi is currently running on the display, this option instead starts a new instance of xdvi in the background (unless the -nofork op- tion is specified, which see) displaying page 5 of file.dvi. The filename and the +n option for the page number are the only options available for controlling a remote instance of xdvi like this; all other options are currently ignored."
        },
        {
            "flag": "",
            "long": null,
            "arg": null,
            "description": "Use logical TeX pages (the values of the \\count0 register) in- stead of physical pages for the pagelist labels and when jumping to a page in a document with the `g' keystroke (or the goto- page() action). This option can be toggled via the `T' key- stroke."
        },
        {
            "flag": "",
            "long": null,
            "arg": null,
            "description": "Print information on the version of xdvi."
        },
        {
            "flag": "",
            "long": null,
            "arg": null,
            "description": "(.visitedLinkColor) Color used for visited hyperlinks (`Purple4' by default). Hyperlinks become visited once you click on them. As for linkColor, the value should be either a valid X color name or a hexadecimal color string."
        },
        {
            "flag": "",
            "long": null,
            "arg": null,
            "description": "(.warnSpecials) Causes xdvi to print warnings about \\special strings that it cannot process to stderr. These warnings are suppressed by default. -watchfile n (.watchFile) If this option is set to a value larger than 0, xd- vi will check the DVI file for changes every n seconds. If the DVI file has been completely written by TeX, it will be reloaded automatically. Fractional values (e.g. `2.5') are possible. The default for this option is 0, i.e. no watching. Since xdvi cannot handle partial DVI files, it tries not to reload the file while it is being rewritten. However, use of the magnifier or switching of pages requires reading (a part of) the DVI file, and if the tempfile option is switched off, this will erase the current contents of the window until the DVI file can be read entirely. -wheelunit pixels (.wheelUnit) Sets the number of pixels that a motion of a wheel mouse will move the image up, down, left, or right. (See the wheel and hwheel actions, below, for more information on this.) If set to zero, the wheel mouse functionality is (essentially) disabled. The default value is 80. -xoffset dimen (.xOffset) Specifies the size of the horizontal offset of the output on the page. See -offsets. -yoffset dimen (.yOffset) Specifies the size of the vertical offset of the out- put on the page. See -offsets."
        }
    ],
    "examples": [],
    "see_also": [
        {
            "name": "X",
            "section": "1",
            "url": "https://www.chedong.com/phpMan.php/man/X/1/json"
        },
        {
            "name": "dvips",
            "section": "1",
            "url": "https://www.chedong.com/phpMan.php/man/dvips/1/json"
        },
        {
            "name": "mktexpk",
            "section": "1",
            "url": "https://www.chedong.com/phpMan.php/man/mktexpk/1/json"
        },
        {
            "name": "ps2pk",
            "section": "1",
            "url": "https://www.chedong.com/phpMan.php/man/ps2pk/1/json"
        },
        {
            "name": "gsftopk",
            "section": "1",
            "url": "https://www.chedong.com/phpMan.php/man/gsftopk/1/json"
        },
        {
            "name": "t1mapper",
            "section": "1",
            "url": "https://www.chedong.com/phpMan.php/man/t1mapper/1/json"
        },
        {
            "name": "cap",
            "section": "4",
            "url": "https://www.chedong.com/phpMan.php/man/cap/4/json"
        }
    ]
}