pfprot("\n

    pfprot("\n"

warning: display: found %d-bit depth while optimized for %d-bit.

"warning: display: found %d-bit depth while optimized for %d-bit.\n"

  Recompile for better performance.\n", offimage->depth, IBYTES_PER_PIXEL*8);

"  Recompile for better performance.\n", offimage->depth, IBYTES_PER_PIXEL*8);

#endif;

#endif

     <i>/<m>          goto previous/next page 

char helpstr[]=

(NUM)<g>              goto page NUM w.r.t. TeX-counters

"LIST OF COMMANDS WITH TYPICAL ARGUMENTS ************ V 01.03\n"

     <u>/<n>/<h>/<j>  scroll the visible area

"\n"

     <f>/<c>          make scrolling finer/coarser

"     <i>/<m>          goto previous/next page \n"

     <z>              center visible area

"(NUM)<g>              goto page NUM w.r.t. TeX-counters\n"

     <+>/<->          zoom in/out

"     <u>/<n>/<h>/<j>  scroll the visible area\n"

(NUM)<v>              set zoom-factor to NUM

"     <f>/<c>          make scrolling finer/coarser\n"

"     <z>              center visible area\n"

     <b>              set a bookmark

"     <+>/<->          zoom in/out\n"

     <w>              move to a bookmark

"(NUM)<v>              set zoom-factor to NUM\n"

     <^>              move back

"\n"

"     <b>              set a bookmark\n"

     <o>              display options 

"     <w>              move to a bookmark\n"

     <x>              toggle statusline-information

"     <^>              move back\n"

     <t>              set unit of measurement

"\n"

"     <o>              display options \n"

     <l>              show/hide screenmark and pagemark

"     <x>              toggle statusline-information\n"

     <y>              set pagemark at screenmark position

"     <t>              set unit of measurement\n"

     <a>              show/hide marked rectangle

"\n"

     <p>              show/hide printable area

"     <l>              show/hide screenmark and pagemark\n"

     <e>              set page-offset and -size

"     <y>              set pagemark at screenmark position\n"

"     <a>              show/hide marked rectangle\n"

     <k>              show/hide half-hyper-tex-mark

"     <p>              show/hide printable area\n"

     <TAB>            move to next href

"     <e>              set page-offset and -size\n"

     <RET>            follow current href

"\n"

"     <k>              show/hide half-hyper-tex-mark\n"

     <s>              search for text

"     <TAB>            move to next href\n"

  <*><r>              re-read DVIfile, fonts, eps-figures

"     <RET>            follow current href\n"

     <d>              load/kill DVIfile

"\n"

     <q>              quit tmview

"     <s>              search for text\n"

"  <*><r>              re-read DVIfile, fonts, eps-figures\n"

"     <d>              load/kill DVIfile\n"

GENERAL USAGE *******************************************

"     <q>              quit tmview\n"

"\n"

When everything is setup right, visiting a DVIfile with

"\n"

tmview just means to navigate the visible area along that

"GENERAL USAGE *******************************************\n"

file, using the cursor-keys.  Some of the following

"\n"

commands obviously require an argument, f.e. <g>.

"When everything is setup right, visiting a DVIfile with\n"

Arguments are to be entered BEFORE executing a command.

"tmview just means to navigate the visible area along that\n"

When executed by hitting the corresponding uppercase key,

"file, using the cursor-keys.  Some of the following\n"

you will be asked for the argument.  While the

"commands obviously require an argument, f.e. <g>.\n"

user-interface of tmview is meant to save keystrokes, it

"Arguments are to be entered BEFORE executing a command.\n"

is not too intuitive. You may either read the following

"When executed by hitting the corresponding uppercase key,\n"

instructions, or just do <caps-lock>.

"you will be asked for the argument.  While the\n"

"user-interface of tmview is meant to save keystrokes, it\n"

The cursor-keys <page-up> and <page-down> are taken as <i>

"is not too intuitive. You may either read the following\n"

resp. <m>. The keys <pos1> and <end> select the first

"instructions, or just do <caps-lock>.\n"

resp. the last page. The cursor-keys <left> <right> <up>

"\n"

and <down> do <h> <j> <u> resp. <n>. All in all this

"The cursor-keys <page-up> and <page-down> are taken as <i>\n"

means, that the cursor-keys do what they are meant to.

"resp. <m>. The keys <pos1> and <end> select the first\n"

"resp. the last page. The cursor-keys <left> <right> <up>\n"

When a mouse is connected, it moves any visible mark. When

"and <down> do <h> <j> <u> resp. <n>. All in all this\n"

the right or left mousebutton is no good for anything

"means, that the cursor-keys do what they are meant to.\n"

else, moving the mouse while holding that button acts on

"\n"

the visible area instead. (That sounds bad, but works out

"When a mouse is connected, it moves any visible mark. When\n"

fine) When the screenmark is shown (see <l>), the left

"the right or left mousebutton is no good for anything\n"

mouse-button sets the pagemark (see <y>) and the right

"else, moving the mouse while holding that button acts on\n"

button marks a rectangle (see <a>). When the

"the visible area instead. (That sounds bad, but works out\n"

half-hyper-mark is shown, the left mouse-button follows

"fine) When the screenmark is shown (see <l>), the left\n"

the current href, if any.

"mouse-button sets the pagemark (see <y>) and the right\n"

"button marks a rectangle (see <a>). When the\n"

*********************************************************

"half-hyper-mark is shown, the left mouse-button follows\n"

NON-INTUITIVE USER-INTERFACE ****************************

"the current href, if any.\n"

*********************************************************

"\n"

"*********************************************************\n"

To explain the way tmview expects to receive commands, a

"NON-INTUITIVE USER-INTERFACE ****************************\n"

short nomenclature used in the sequel is given:

"*********************************************************\n"

"\n"

Any text within `<' and `>' represents a single keystroke,

"To explain the way tmview expects to receive commands, a\n"

while `(' and `)' mark the beginning resp. the end of a

"short nomenclature used in the sequel is given:\n"

string to enter.  So <h> is about to hit the key named `h'

" \n"

and (25.4) could stand for <2><5> <.><4>.  The carriage-

"Any text within `<' and `>' represents a single keystroke,\n"

return-key is referred by <ret>, the backspace-key or 

"while `(' and `)' mark the beginning resp. the end of a\n"

delete-key by <del> and the escape-key by <esc>. Almost 

"string to enter.  So <h> is about to hit the key named `h'\n"

whenever a string is expected by tmview, you may use <del>

"and (25.4) could stand for <2><5> <.><4>.  The carriage-\n"

to remove the last character you typed. So even

"return-key is referred by <ret>, the backspace-key or \n"

<2><5><6><del><.><4> results in (25.4). Note that a string

"delete-key by <del> and the escape-key by <esc>. Almost \n"

does not need to be terminated by <ret>.  To simplify a

"whenever a string is expected by tmview, you may use <del>\n"

reference to a string, in this text any uppercase letters

"to remove the last character you typed. So even\n"

within `(' and `)' are not meant as a string, but as the

"<2><5><6><del><.><4> results in (25.4). Note that a string\n"

name of some string. So we may read something like

"does not need to be terminated by <ret>.  To simplify a\n"

`(PP)<h> scrolls PP percent to the left' as `typing in any

"reference to a string, in this text any uppercase letters\n"

number just before <h> results in scrolling left according

"within `(' and `)' are not meant as a string, but as the\n"

to that number'.

"name of some string. So we may read something like\n"

"`(PP)<h> scrolls PP percent to the left' as `typing in any\n"

"number just before <h> results in scrolling left according\n"

COMMANDS AND ARGUMENTS***********************************

"to that number'.\n"

"\n"

A command is executed by typing its name, which consists

"\n"

of a single character. Some of the above listed commands

"COMMANDS AND ARGUMENTS***********************************\n"

take numerical arguments.  Arguments are always

"\n"

optional. They may be entered before executing the

"A command is executed by typing its name, which consists\n"

command. Multiple arguments are separated by <,> or

"of a single character. Some of the above listed commands\n"

<;>. If no argument is passed, a default is used. If an

"take numerical arguments.  Arguments are always\n"

argument is passed, it serves as the default for following

"optional. They may be entered before executing the\n"

commands. Commands doing similar things share the same

"command. Multiple arguments are separated by <,> or\n"

default arguments.

"<;>. If no argument is passed, a default is used. If an\n"

"argument is passed, it serves as the default for following\n"

Example: 

"commands. Commands doing similar things share the same\n"

Typing (10)<h> results in scrolling 10% to the left and

"default arguments.\n"

sets the default for any scrolling commands to 10%. Thus

"\n"

typing <j> afterwards results in scrolling 10% to the

"Example: \n"

right.

"Typing (10)<h> results in scrolling 10% to the left and\n"

"sets the default for any scrolling commands to 10%. Thus\n"

"typing <j> afterwards results in scrolling 10% to the\n"

MAGIC ARGUMENT*******************************************

"right.\n"

"\n"

As a special argument some commands accept the magic

"\n"

argument <*>. It is used either to vary the command in

"MAGIC ARGUMENT*******************************************\n"

some way or to get the arguments from another place. <#>

"\n"

is equivalent to <*> and saves you from holding down the

"As a special argument some commands accept the magic\n"

shift-key on some keyboards.

"argument <*>. It is used either to vary the command in\n"

"some way or to get the arguments from another place. <#>\n"

<z> for example centers the visible area. It excepts as

"is equivalent to <*> and saves you from holding down the\n"

argument the point which will be taken as origin. Since

"shift-key on some keyboards.\n"

this will become the default for a future <z>, you may

"\n"

measure out the origin only once. Even quicker it is to

"<z> for example centers the visible area. It excepts as\n"

position the visible area by scrolling and then to do a

"argument the point which will be taken as origin. Since\n"

<*><z>.  This results in taking the current position as

"this will become the default for a future <z>, you may\n"

centered and so as default for a coming <z>.

"measure out the origin only once. Even quicker it is to\n"

"position the visible area by scrolling and then to do a\n"

As another example look at the command <m>, which moves

"<*><z>.  This results in taking the current position as\n"

pages forward, according to a given argument resp. a

"centered and so as default for a coming <z>.\n"

default. By moving on the next page there are two modi

"\n"

available: 1. keep the visible area; 2. do center like

"As another example look at the command <m>, which moves\n"

<z><z>.  <*><m> toggles between these two modi. So in this

"pages forward, according to a given argument resp. a\n"

case <*> acts as a kind of flag argument.

"default. By moving on the next page there are two modi\n"

"available: 1. keep the visible area; 2. do center like\n"

"<z><z>.  <*><m> toggles between these two modi. So in this\n"

"case <*> acts as a kind of flag argument.\n"

SELECTING THE PAGE****************************************

"\n"

"\n"

<i>/<m> Select a page relative to the current page. 

"\n"

"SELECTING THE PAGE****************************************\n"

     <i> moves towards the beginning of the DVIfile, while

"\n"

     <m> moves towards the end. A single argument (N) may

"<i>/<m> Select a page relative to the current page. \n"

     specify the amount of movement in pages. However, (N)

"\n"

     will NOT become the default value. The argument is (*), 

"     <i> moves towards the beginning of the DVIfile, while\n"

     the page-moving-mode is toggled. See above.  

"     <m> moves towards the end. A single argument (N) may\n"

"     specify the amount of movement in pages. However, (N)\n"

     Example: 

"     will NOT become the default value. The argument is (*), \n"

     (1)<i> selects the previous page <m> selects the next

"     the page-moving-mode is toggled. See above.  \n"

     page

"\n"

"     Example: \n"

<g> Select a page with respect to TeX counters.  

"     (1)<i> selects the previous page <m> selects the next\n"

"     page\n"

     A list of ten arguments (COUNT0; COUNT1; ... COUNT9)

"\n"

     specifies the page to be selected. <*> may be used as

"<g> Select a page with respect to TeX counters.  \n"

     wildcard. If there are more than one but less than ten

"\n"

     arguments given, the others will be taken as <*>.

"     A list of ten arguments (COUNT0; COUNT1; ... COUNT9)\n"

"     specifies the page to be selected. <*> may be used as\n"

     Example: 

"     wildcard. If there are more than one but less than ten\n"

     (26)<g> selects the first page after the current page

"     arguments given, the others will be taken as <*>.\n"

     with a value of 26 in \\count0.

"\n"

"     Example: \n"

"     (26)<g> selects the first page after the current page\n"

"     with a value of 26 in \\count0.\n"

MOVING AROUND ON CURRENT PAGE ******************************

"\n"

"\n"

<u>/<n>/<h>/<j> Scrolling the visible area

"\n"

"MOVING AROUND ON CURRENT PAGE ******************************\n"

       A single argument (PP) may be used to specify the

"\n"

       amount of scrolling in percent of the

"<u>/<n>/<h>/<j> Scrolling the visible area\n"

       screen-width. <u>/<n> resp. <up>/down> both accept

"\n"

       the argument (*) to toggle between: 1. stay on the

"       A single argument (PP) may be used to specify the\n"

       current page; 2. scroll over pages. When scrolling

"       amount of scrolling in percent of the\n"

       over pages, you may view the whole document while

"       screen-width. <u>/<n> resp. <up>/down> both accept\n"

       using only the single key <n>.

"       the argument (*) to toggle between: 1. stay on the\n"

"       current page; 2. scroll over pages. When scrolling\n"

       Example:

"       over pages, you may view the whole document while\n"

       (20)<h> scrolls 1/5 to the left.  

"       using only the single key <n>.\n"

"\n"

<f>/<c> Make scrolling finer/coarser

"       Example:\n"

"       (20)<h> scrolls 1/5 to the left.  \n"

       These commands change the default argument for the

"\n"

       above scrolling- commands. So <f> and <c> don't move

"<f>/<c> Make scrolling finer/coarser\n"

       the visible area at all, but they change the way the

"\n"

       scrolling-commands act.

"       These commands change the default argument for the\n"

"       above scrolling- commands. So <f> and <c> don't move\n"

<z> Center the visible area

"       the visible area at all, but they change the way the\n"

"       scrolling-commands act.\n"

       Without any argument <z> centers horizontally only,

"\n"

       while <z><z> centers in both directions.

"<z> Center the visible area\n"

       When two arguments (X,Y) are given, they describe

"\n"

       the point on the page, which will become the middle

"       Without any argument <z> centers horizontally only,\n"

       of the visible area. When the argument (*) is given,

"       while <z><z> centers in both directions.\n"

       the current position is taken as centered.  When the

"       When two arguments (X,Y) are given, they describe\n"

       screenmark is shown (see below <l>), and the

"       the point on the page, which will become the middle\n"

       argument (*) is given, the position of the

"       of the visible area. When the argument (*) is given,\n"

       screenmark becomes the center. This does move the

"       the current position is taken as centered.  When the\n"

       visible area, but it does not move the screenmark.

"       screenmark is shown (see below <l>), and the\n"

"       argument (*) is given, the position of the\n"

"       screenmark becomes the center. This does move the\n"

ZOOMING ****************************************************

"       visible area, but it does not move the screenmark.\n"

"\n"

<v> Set the zoom-factor

"\n"

"ZOOMING ****************************************************\n"

       This command requires one argument (F) which must be

"\n"

       between 0.05 and 2.  F will become the zoom-factor

"<v> Set the zoom-factor\n"

       and the visible-area will be redrawn. Use (*)<v> to 

" \n"

       adjust the zoom-factor such that the page horizontaly 

"       This command requires one argument (F) which must be\n"

       fits the visible-area.

"       between 0.05 and 2.  F will become the zoom-factor\n"

"       and the visible-area will be redrawn. Use (*)<v> to \n"

       If the zoom-factor is 1, the pixels found in pk-files 

"       adjust the zoom-factor such that the page horizontaly \n"

       are just copied one by one to the screen. Since the

"       fits the visible-area.\n"

       resolution of our days screens seems to be less than

"\n"

       that of our days printers, and since you may still

"       If the zoom-factor is 1, the pixels found in pk-files \n"

       want to use the same pk-files for printing and

"       are just copied one by one to the screen. Since the\n"

       viewing, F=1 usually results in a magnification. So

"       resolution of our days screens seems to be less than\n"

       when you're just reading some text in some DVIfile

"       that of our days printers, and since you may still\n"

       you will set F to something like 0.3, depending on

"       want to use the same pk-files for printing and\n"

       the involved resolutions. When the screenmark is

"       viewing, F=1 usually results in a magnification. So\n"

       visible (see <l>) the position of the screenmark is

"       when you're just reading some text in some DVIfile\n"

       taken as the origin of zooming, i.e. it is fixed. 

"       you will set F to something like 0.3, depending on\n"

       When the screenmark is not visible, the middle of the 

"       the involved resolutions. When the screenmark is\n"

       screen is fixed. The current zoom-factor is displayed 

"       visible (see <l>) the position of the screenmark is\n"

       in the optional statusline, see <x>.

"       taken as the origin of zooming, i.e. it is fixed. \n"

"       When the screenmark is not visible, the middle of the \n"

       There are two zooming modi. The integer modus 

"       screen is fixed. The current zoom-factor is displayed \n"

       requieres 1/f to be an integer. This modus is quite 

"       in the optional statusline, see <x>.\n"

       fast, so good values are F=0.5, 0.333, 0.25, 0.2, 

"\n"

       0.167 etc. The good thing about the slow modus is, 

"       There are two zooming modi. The integer modus \n"

       that it allows you to choose the zoom-factor 

"       requieres 1/f to be an integer. This modus is quite \n"

       arbitrary (between 0.05 and 2). So poor students with 

"       fast, so good values are F=0.5, 0.333, 0.25, 0.2, \n"

       small screens might find some optimum to make the 

"       0.167 etc. The good thing about the slow modus is, \n"

       text fit and still be readable. The bad thing about 

"       that it allows you to choose the zoom-factor \n"

       the slow modus is that it is slow.  But since once 

"       arbitrary (between 0.05 and 2). So poor students with \n"

       zoomed glyphs are kept in memory, this slowness only 

"       small screens might find some optimum to make the \n"

       hurts the first few pages after changing the

"       text fit and still be readable. The bad thing about \n"

       zoom-factor. Modus selection is  done by the display 

"       the slow modus is that it is slow.  But since once \n"

       options <o>. 

"       zoomed glyphs are kept in memory, this slowness only \n"

"       hurts the first few pages after changing the\n"

<+>/<-> Zoom in/out

"       zoom-factor. Modus selection is  done by the display \n"

"       options <o>. \n"

       Increase/decrease the zoom-factor. When in the fast

"\n"

       modus, step through the fast values only (see

"<+>/<-> Zoom in/out\n"

       above). When an argument (PP) is given, it is taken

"\n"

       as the amount of increasing/decreasing in percent of

"       Increase/decrease the zoom-factor. When in the fast\n"

       the current zoom-factor. This is likely to result in

"       modus, step through the fast values only (see\n"

       the slow modus.

"       above). When an argument (PP) is given, it is taken\n"

"       as the amount of increasing/decreasing in percent of\n"

"       the current zoom-factor. This is likely to result in\n"

BOOKMARKS **************************************************

"       the slow modus.\n"

"\n"

A bookmark remembers what is seen on the screen. That is

"\n"

the DVIfile, the page within that file, the position of the

"BOOKMARKS **************************************************\n"

visable area and the zoom-factor. There are three kind of

"\n"

bookmarks ...

"A bookmark remembers what is seen on the screen. That is\n"

"the DVIfile, the page within that file, the position of the\n"

file-bookmarks:

"visable area and the zoom-factor. There are three kind of\n"

Each file visited has a file-bookmark, containing the above

"bookmarks ...\n"

information about what was seen on the screen when visited

"\n"

the last time, plus some information on the file, that is

"file-bookmarks:\n"

the paper-offset and -position, the location of the

"Each file visited has a file-bookmark, containing the above\n"

printable-area.  file-bookmarks are generated automaticly.

"information about what was seen on the screen when visited\n"

This results in easy re-visiting a DVIfile: you'll find it

"the last time, plus some information on the file, that is\n"

as left. A file-bookmark is removed by killing the DVIfile

"the paper-offset and -position, the location of the\n"

with <d><k>, see <d> below.

"printable-area.  file-bookmarks are generated automaticly.\n"

"This results in easy re-visiting a DVIfile: you'll find it\n"

back-bookmarks:

"as left. A file-bookmark is removed by killing the DVIfile\n"

When searching a text-string, following a href or moving to

"with <d><k>, see <d> below.\n"

a bookmark, the position within the DVIfile might be

"\n"

changed to somewhere far far away. To simplify recovering

"back-bookmarks:\n"

fromsuch excursions, a back-bookmark will be generated

"When searching a text-string, following a href or moving to\n"

automaticly.  To prevent getting fed up with thousands of

"a bookmark, the position within the DVIfile might be\n"

back-bookmarks, the total number of theese is limited. See

"changed to somewhere far far away. To simplify recovering\n"

<^> below.

"fromsuch excursions, a back-bookmark will be generated\n"

"automaticly.  To prevent getting fed up with thousands of\n"

manual-bookmarks:

"back-bookmarks, the total number of theese is limited. See\n"

After all you may install your own bookmarks, marking often

"<^> below.\n"

visited places, say in some manuals. manual-bookmarks are

"\n"

named by a number.  This number has to be unique whithin

"manual-bookmarks:\n"

the DVIfile they belong to.  To define a manual-bookmark

"After all you may install your own bookmarks, marking often\n"

use <b>. Since manual-bookmarks belong to the DVIfile they

"visited places, say in some manuals. manual-bookmarks are\n"

are defined on, they get lost, when that DVIfile is killed

"named by a number.  This number has to be unique whithin\n"

by <d><k>.

"the DVIfile they belong to.  To define a manual-bookmark\n"

"use <b>. Since manual-bookmarks belong to the DVIfile they\n"

All kind of bookmarks are kept in a ring-buffer. There is a

"are defined on, they get lost, when that DVIfile is killed\n"

so called current bookmark of each type. Visiting the

"by <d><k>.\n"

bookmarks along the ring-buffer is done by <w> for file-

"\n"

and manual-bookmarks, while <^> acts on back-bookmarks.

"All kind of bookmarks are kept in a ring-buffer. There is a\n"

"so called current bookmark of each type. Visiting the\n"

<b> Define/undefine manual-bookmark.  

"bookmarks along the ring-buffer is done by <w> for file-\n"

"and manual-bookmarks, while <^> acts on back-bookmarks.\n"

       When the current position is not already defined as

"\n"

       a manual-bookmark, <b> defines one. When an single

"<b> Define/undefine manual-bookmark.  \n"

       numeric argument (NUM) is given, NUM will be the

"\n"

       name of the newly defined bookmark. With no

"       When the current position is not already defined as\n"

       argument, a name will be generated automaticly. See

"       a manual-bookmark, <b> defines one. When an single\n"

       <w> below, for how to visit manual-bookmarks.  When

"       numeric argument (NUM) is given, NUM will be the\n"

       the current position is already defined as a

"       name of the newly defined bookmark. With no\n"

       manual-bookmark, <b> undefines that manual-bookmark.

"       argument, a name will be generated automaticly. See\n"

"       <w> below, for how to visit manual-bookmarks.  When\n"

<w> Move to bookmark.

"       the current position is already defined as a\n"

"       manual-bookmark, <b> undefines that manual-bookmark.\n"

       When a single numeric argument (NUM) is given, <w>

"\n"

       moves to the manual-bookmark named NUM, if

"<w> Move to bookmark.\n"

       any. Since manual bookmarks are bound to DVIfiles,

"\n"

       the current DVIfile will never change in that

"       When a single numeric argument (NUM) is given, <w>\n"

       case. If no argument is given, <w> goes moves the

"       moves to the manual-bookmark named NUM, if\n"

       postion either thrue the ring-buffer of

"       any. Since manual bookmarks are bound to DVIfiles,\n"

       file-bookmarks or thrue the one of

"       the current DVIfile will never change in that\n"

       manual-bookmarks. To toggle between theese two modi,

"       case. If no argument is given, <w> goes moves the\n"

       use the magic argument <*>.

"       postion either thrue the ring-buffer of\n"

"       file-bookmarks or thrue the one of\n"

<^> Move back

"       manual-bookmarks. To toggle between theese two modi,\n"

"       use the magic argument <*>.\n"

       Move to the latest back-bookmark, if any. When a

"\n"

       single numeric argument (TOTAL) is given, keep the

"<^> Move back\n"

       TOTAL latest back-bookmarks and discard all the

"   \n"

       others.

"       Move to the latest back-bookmark, if any. When a\n"

"       single numeric argument (TOTAL) is given, keep the\n"

"       TOTAL latest back-bookmarks and discard all the\n"

CHOOSING WHAT'S ON THE DISPLAY *****************************

"       others.\n"

"\n"

<o> Display options

"\n"

"CHOOSING WHAT'S ON THE DISPLAY *****************************\n"

       This command collects a number of general options 

"\n"

       on how the things get on the screen. Use the cursor

"<o> Display options\n"

       keys (or <u>/<n>/<h>/<h>) to navigate.

"\n"

"       This command collects a number of general options \n"

       > Greyscales. When the zoom-factor is less than 1, 

"       on how the things get on the screen. Use the cursor\n"

       the glyphs may be displayed using grey-levels, making 

"       keys (or <u>/<n>/<h>/<h>) to navigate.\n"

       them more smooth. This takes some memory, so you are 

"\n"

       allowed to switch it off. On high-res displays there 

"       > Greyscales. When the zoom-factor is less than 1, \n"

       is no need for greyscaling anyway.

"       the glyphs may be displayed using grey-levels, making \n"

"       them more smooth. This takes some memory, so you are \n"

       > Eps-rendering. There is limited support for 

"       allowed to switch it off. On high-res displays there \n"

       rendering eps-files by running ghostscript. However, 

"       is no need for greyscaling anyway.\n"

       this sometimes is quite slow and memory intensive, so 

"\n"

       you may turn it off. If rendering is enabled the 

"       > Eps-rendering. There is limited support for \n"

       results are buffered. Hence, if the eps-files are 

"       rendering eps-files by running ghostscript. However, \n"

       updated by some graphics program, you need to do a 

"       this sometimes is quite slow and memory intensive, so \n"

       <*><r> to force rerendering. To disable certain 

"       you may turn it off. If rendering is enabled the \n"

       eps-files individually, abort the rendering process 

"       results are buffered. Hence, if the eps-files are \n"

       by <esc>.

"       updated by some graphics program, you need to do a \n"

"       <*><r> to force rerendering. To disable certain \n"

       > Double-page. There is also limited support for 

"       eps-files individually, abort the rendering process \n"

       viewing two pages beside each other. Again their

"       by <esc>.\n"

       is some memory required to keep it all buffered.

"\n"

       You may disable double paged viewing entirely. You

"       > Double-page. There is also limited support for \n"

       may let tmview deceide on basis of the zoom-factor.

"       viewing two pages beside each other. Again their\n"

       Or you may permanently enable this feature.

"       is some memory required to keep it all buffered.\n"

"       You may disable double paged viewing entirely. You\n"

       > Zooming. There is a fast zooming mode allowing

"       may let tmview deceide on basis of the zoom-factor.\n"

       only zomming by 1/f where f is required to be an

"       Or you may permanently enable this feature.\n"

       integer. And there is an arbitrary mode to be

"\n"

       selected.

"       > Zooming. There is a fast zooming mode allowing\n"

"       only zomming by 1/f where f is required to be an\n"

<x> Toggle statusline-information

"       integer. And there is an arbitrary mode to be\n"

"       selected.\n"

       While the standard statusline shows you the

"\n"

       page-number of the current page and the arguments

"<x> Toggle statusline-information\n"

       you are about to enter, you may select optional

"\n"

       information for measuring out distances and so. See

"       While the standard statusline shows you the\n"

       below.

"       page-number of the current page and the arguments\n"

"       you are about to enter, you may select optional\n"

<t> Set unit of measurement

"       information for measuring out distances and so. See\n"

"       below.\n"

       Whenever you specify arguments which are to describe

"\n"

       a point on the page, this is done w.r.t. a unit of

"<t> Set unit of measurement\n"

       measurement, i.e. cm, mm, a.s.o.. This unit is also

"\n"

       used, when the position of a mark is displayed in

"       Whenever you specify arguments which are to describe\n"

       the statusline.

"       a point on the page, this is done w.r.t. a unit of\n"

"       measurement, i.e. cm, mm, a.s.o.. This unit is also\n"

"       used, when the position of a mark is displayed in\n"

MEASURING **************************************************

"       the statusline.\n"

"\n"

To allow you to measure distances on the page, there are

"\n"

two marks, the screenmark, which is fixed on the physical

"MEASURING **************************************************\n"

screen you're looking at, and the pagemark, which is fixed

"\n"

on the DVIfiles page. When you move the visible-area, the

"To allow you to measure distances on the page, there are\n"

screenmark acts as drawn with edding on your monitor. The

"two marks, the screenmark, which is fixed on the physical\n"

pagemark acts as drawn on the page. The optional statusline

"screen you're looking at, and the pagemark, which is fixed\n"

tells the position of the pagemark relative to the corner

"on the DVIfiles page. When you move the visible-area, the\n"

of the sheet of paper you're viewing. It also tells the

"screenmark acts as drawn with edding on your monitor. The\n"

position of the screenmark relative to the pagemark. To

"pagemark acts as drawn on the page. The optional statusline\n"

measure distances you first may switch this marks on, using

"tells the position of the pagemark relative to the corner\n"

<l>. When the marks are shown, the scrolling commands don't

"of the sheet of paper you're viewing. It also tells the\n"

act on the visible area anymore, but move the screenmark. 

"position of the screenmark relative to the pagemark. To\n"

For that case only moving the screenmark at the boarder of

"measure distances you first may switch this marks on, using\n"

the screen results in scrolling. To move the pagemark just

"<l>. When the marks are shown, the scrolling commands don't\n"

move the screenmark at the desired position and use <y> to

"act on the visible area anymore, but move the screenmark. \n"

make the pagemark follow.

"For that case only moving the screenmark at the boarder of\n"

"the screen results in scrolling. To move the pagemark just\n"

<l> Show/hide screenmark and pagemark

"move the screenmark at the desired position and use <y> to\n"

"make the pagemark follow.\n"

       This commands takes the two arguments

" \n"

       (PM_X;PM_Y). The pagemark is put at position PM_X

"<l> Show/hide screenmark and pagemark\n"

       PM_Y w.r.t. the upper left corner of the page. The

"\n"

       Screenmark may be moved with the scrolling-commands.

"       This commands takes the two arguments\n"

"       (PM_X;PM_Y). The pagemark is put at position PM_X\n"

<y> Set pagemark at the position of the screenmark

"       PM_Y w.r.t. the upper left corner of the page. The\n"

"       Screenmark may be moved with the scrolling-commands.\n"

Beside of these marks there are three rectangles for

"\n"

measurement. First there is the boarder of the paper setup

"<y> Set pagemark at the position of the screenmark\n"

by the command-line options -h,-v and -p.  Then there is

"       \n"

the printable area, setup with the -k command-line option.

"Beside of these marks there are three rectangles for\n"

Third the so called marked rectangle used.

"measurement. First there is the boarder of the paper setup\n"

"by the command-line options -h,-v and -p.  Then there is\n"

<a> Show/hide marked rectangle

"the printable area, setup with the -k command-line option.\n"

"Third the so called marked rectangle used.\n"

       The four arguments (LEFT,TOP,WIDTH,HIGHT) specify

"\n"

       the position on page an the size of the marked

"<a> Show/hide marked rectangle\n"

       rectangle. When pagemark and screenmark are shown,

"\n"

       their positions are used as default. When they are

"       The four arguments (LEFT,TOP,WIDTH,HIGHT) specify\n"

       hidden, the last position of the marked rectangle is

"       the position on page an the size of the marked\n"

       used as default.

"       rectangle. When pagemark and screenmark are shown,\n"

"       their positions are used as default. When they are\n"

<p> Show/hide printable area 

"       hidden, the last position of the marked rectangle is\n"

"       used as default.\n"

       The four arguments (LEFT,RIGHT,TOP,BOTTOM) specify

"\n"

       the margins of the printable area, w.r.t. the

"<p> Show/hide printable area \n"

       boarder of the page. When pagemark and screenmark

"       \n"

       are shown, the argument (*) sets the printable area

"       The four arguments (LEFT,RIGHT,TOP,BOTTOM) specify\n"

       to the rectangle described by screenmark and

"       the margins of the printable area, w.r.t. the\n"

       pagemark.  When they are hidden, (*) takes the

"       boarder of the page. When pagemark and screenmark\n"

       command-line-options resp. defaults -k of the

"       are shown, the argument (*) sets the printable area\n"

       printable area.

"       to the rectangle described by screenmark and\n"

"       pagemark.  When they are hidden, (*) takes the\n"

<e> Set paper-offset and -size  

"       command-line-options resp. defaults -k of the\n"

"       printable area.\n"

       The four arguments (HOFF;VOFF;WIDTH;HEIGHT) specify

"\n"

       the boarder of the page. Have the top-left corner of

"<e> Set paper-offset and -size  \n"

       a sheet of paper in mind. Then (HOFF,VOFF) is the

"\n"

       offset of the DVIfile's origin to the left boarder

"       The four arguments (HOFF;VOFF;WIDTH;HEIGHT) specify\n"

       of the paper.  Standard values are

"       the boarder of the page. Have the top-left corner of\n"

       HOFF=VOFF=2.54cm. WIDTH and HEIGHT are the width and

"       a sheet of paper in mind. Then (HOFF,VOFF) is the\n"

       the height of the sheet of paper. The sheet of paper

"       offset of the DVIfile's origin to the left boarder\n"

       is represented only by a frame on the screen. It

"       of the paper.  Standard values are\n"

       does not affect the drawing of the DVIfile.

"       HOFF=VOFF=2.54cm. WIDTH and HEIGHT are the width and\n"

"       the height of the sheet of paper. The sheet of paper\n"

       When pagemark and screenmark are shown, the argument

"       is represented only by a frame on the screen. It\n"

       (*) sets the boarder of the page to the rectangle

"       does not affect the drawing of the DVIfile.\n"

       described by screenmark and pagemark.  When they are

"\n"

       hidden, (*) takes the command-line-options

"       When pagemark and screenmark are shown, the argument\n"

       resp. defaults -h,-v and -p.

"       (*) sets the boarder of the page to the rectangle\n"

"       described by screenmark and pagemark.  When they are\n"

"       hidden, (*) takes the command-line-options\n"

HALF-HYPER *************************************************

"       resp. defaults -h,-v and -p.\n"

"\n"

tmview does some of the fancy hyper-tex things. I talk

"\n"

about HALF-hyper-tex, because tmview follows only links

"HALF-HYPER *************************************************\n"

which point to somewhere within the currently visited

"\n"

dvi-file. So there is no connection to the net or so. But

"tmview does some of the fancy hyper-tex things. I talk\n"

you might find it usefull (when editing a major project) to

"about HALF-hyper-tex, because tmview follows only links\n"

view an equation number this-and-that by clicking on

"which point to somewhere within the currently visited\n"

this-and-that whereever the text refers to that equation.

"dvi-file. So there is no connection to the net or so. But\n"

For information about hyper-tex, related macropackages and

"you might find it usefull (when editing a major project) to\n"

fully compatible viewer scan the net ...

"view an equation number this-and-that by clicking on\n"

"this-and-that whereever the text refers to that equation.\n"

<k> Show/hide half-hyper-mark

"For information about hyper-tex, related macropackages and\n"

<TAB> Goto next href

"fully compatible viewer scan the net ...\n"

<RET> Follow current href, if any 

"\n"

"<k> Show/hide half-hyper-mark\n"

"<TAB> Goto next href\n"

MISC *******************************************************

"<RET> Follow current href, if any \n"

"\n"

<s> Search for text

"\n"

"MISC *******************************************************\n"

      You will be asked for the text-string to be searched.

"\n"

      You may enter a regular expression describing that

"<s> Search for text\n"

      string, that includes especially just to enter the

"\n"

      string as it is.

"      You will be asked for the text-string to be searched.\n"

"      You may enter a regular expression describing that\n"

      tmview will take the entire DVIfile as one huge

"      string, that includes especially just to enter the\n"

      text-string and then search for the next substring,

"      string as it is.\n"

      fitting the regular expression you've enterd. Thereby

"\n"

      \"next\" is ment with respect to the current page.

"      tmview will take the entire DVIfile as one huge\n"

"      text-string and then search for the next substring,\n"

      So far this sounds quite easy, but there are some ugly

"      fitting the regular expression you've enterd. Thereby\n"

      details, based on the fact, that a DVIfile contains

"      \"next\" is ment with respect to the current page.\n"

      information on how to draw a bitmap representing your

"\n"

      text. It does not contain information about from what

"      So far this sounds quite easy, but there are some ugly\n"

      characters in which order your text is made up. Even

"      details, based on the fact, that a DVIfile contains\n"

      the PKfiles used to draw your text consist only of

"      information on how to draw a bitmap representing your\n"

      lots of glyphs but no character-codes, like ASCII or

"      text. It does not contain information about from what\n"

      so. Building a huge text-string from a DVIfile is some

"      characters in which order your text is made up. Even\n"

      kind of guessing.

"      the PKfiles used to draw your text consist only of\n"

"      lots of glyphs but no character-codes, like ASCII or\n"

      Fisrt: What kind of huge-string is build from the DVIfile?

"      so. Building a huge text-string from a DVIfile is some\n"

"      kind of guessing.\n"

      This string will consists of the letters <A> ... <Z>,

"\n"

      <a> ... <z>, the accent <\"> and the digits <0>

"      Fisrt: What kind of huge-string is build from the DVIfile?\n"

      ... <9>. It does NOT contain anything else, like

"\n"

      <space>, <ret> or <->:

"      This string will consists of the letters <A> ... <Z>,\n"

      Whenbeingprinteditwouldlooklikethisnotreadableatall.  

"      <a> ... <z>, the accent <\"> and the digits <0>\n"

      Taking the DVIfile as huge string allows you to find

"      ... <9>. It does NOT contain anything else, like\n"

      all locations of a sub-string, say

"      <space>, <ret> or <->:\n"

      \"commandlineoptions\", even those that are seperarted

"      Whenbeingprinteditwouldlooklikethisnotreadableatall.  \n"

      by linebreaks (and hyphens) or pagebreaks. In turn,

"      Taking the DVIfile as huge string allows you to find\n"

      there is no chance to find all those locations, where

"      all locations of a sub-string, say\n"

      \"commandlineoptions\" is seperated by a hypenation.  To

"      \"commandlineoptions\", even those that are seperarted\n"

      keep tmview from being confused by headings, there is

"      by linebreaks (and hyphens) or pagebreaks. In turn,\n"

      another rule for building up the huge text-string: any

"      there is no chance to find all those locations, where\n"

      glyph outside the printable area (see <p>) is

"      \"commandlineoptions\" is seperated by a hypenation.  To\n"

      ignored. So you may setup the printable area to ignore

"      keep tmview from being confused by headings, there is\n"

      headings when searching.

"      another rule for building up the huge text-string: any\n"

"      glyph outside the printable area (see <p>) is\n"

      Second: How is the huge-string build up?

"      ignored. So you may setup the printable area to ignore\n"

"      headings when searching.\n"

      To translate the list of glyphs found in the DVIfile

"\n"

      to a text-string, the tfm-files are asked for the

"      Second: How is the huge-string build up?\n"

      encoding-scheme. This does work with dc-fonts and

"\n"

      cm-fonts, since the following encoding-scheme names

"      To translate the list of glyphs found in the DVIfile\n"

      are accepted: \"ASCII\", \"TeX text\", \"TeX math italic\",

"      to a text-string, the tfm-files are asked for the\n"

      \"TeX math symbols\", \"TeX typewriter text\", \"Extended

"      encoding-scheme. This does work with dc-fonts and\n"

      TeX Font Encoding - Latin\", \"Adobe StandardEncoding\".

"      cm-fonts, since the following encoding-scheme names\n"

      The alphanumerics <A>...<Z>, <a>...<z>, <0> ... <9>

"      are accepted: \"ASCII\", \"TeX text\", \"TeX math italic\",\n"

      are copied one by one to the huge text-string. Glyphs

"      \"TeX math symbols\", \"TeX typewriter text\", \"Extended\n"

      that \"look like\" a simple alphanumeric will be taken

"      TeX Font Encoding - Latin\", \"Adobe StandardEncoding\".\n"

      as that one it looks like.  So the Tex input '\\c o',

"      The alphanumerics <A>...<Z>, <a>...<z>, <0> ... <9>\n"

      producing an 'o'-with-an-cedilla-accent, will be

"      are copied one by one to the huge text-string. Glyphs\n"

      represented as a simple (o) in the text-string. This

"      that \"look like\" a simple alphanumeric will be taken\n"

      rule also works for all kind of ligatures. The TeX

"      as that one it looks like.  So the Tex input '\\c o',\n"

      input 'ffl\\AE' will be represented by (fflAE).  Any

"      producing an 'o'-with-an-cedilla-accent, will be\n"

      accent ON TOP of a glyph will be translated to a (\"),

"      represented as a simple (o) in the text-string. This\n"

      preceding whatever the glyph without that accent would

"      rule also works for all kind of ligatures. The TeX\n"

      be translated to.  The TeX input '\\\"a' producing the

"      input 'ffl\\AE' will be represented by (fflAE).  Any\n"

      german umlaut 'a'-with-two-dots-on-top, will be found

"      accent ON TOP of a glyph will be translated to a (\"),\n"

      as (\"a) in the generated text-string.  The TeX input

"      preceding whatever the glyph without that accent would\n"

      '\\aa' producing the scandinavian

"      be translated to.  The TeX input '\\\"a' producing the\n"

      'a'-with-circle-on-top will be found as (\"a) too. Any

"      german umlaut 'a'-with-two-dots-on-top, will be found\n"

      other glyphs are ignored.

"      as (\"a) in the generated text-string.  The TeX input\n"

"      '\\aa' producing the scandinavian\n"

      Third: In what does the above result?

"      'a'-with-circle-on-top will be found as (\"a) too. Any\n"

"      other glyphs are ignored.\n"

      Visiting english documents, say manuals to some

"\n"

      computer related stuff like elisp.dvi, searching for

"      Third: In what does the above result?\n"

      keywords works fine. Searching in documents in which

"\n"

      extensive use of accents and funny characters is made

"      Visiting english documents, say manuals to some\n"

      works too, but requires some luck or/and experiance in

"      computer related stuff like elisp.dvi, searching for\n"

      how TeX acts on such things.

"      keywords works fine. Searching in documents in which\n"

"      extensive use of accents and funny characters is made\n"

"      works too, but requires some luck or/and experiance in\n"

      Example: 

"      how TeX acts on such things.\n"

"\n"

      Take the file story.tex from the TeXbook, chapter 6, 

"\n"

      page 24.  It contains the line

"      Example: \n"

              galaxy called \\\"O\\\"o\\c c,

"\n"

      The text-string build from the corresponding story.dvi

"      Take the file story.tex from the TeXbook, chapter 6, \n"

      will therfore contain

"      page 24.  It contains the line\n"

              galaxycalled\"O\"oc

"              galaxy called \\\"O\\\"o\\c c,\n"

      You may search for ...    getting as result ...

"      The text-string build from the corresponding story.dvi\n"

      galaxy                    found

"      will therfore contain\n"

      galaxycalled              found

"              galaxycalled\"O\"oc\n"

      galaxy called             not found

"      You may search for ...    getting as result ...\n"

      d\"                        found

"      galaxy                    found\n"

      galaxy.*\"O\"oc             found

"      galaxycalled              found\n"

      Ooc                       not found

"      galaxy called             not found\n"

"      d\"                        found\n"

"      galaxy.*\"O\"oc             found\n"

<r> Re-read current DVIfile and re-draw screen.

"      Ooc                       not found\n"

"      \n"

      Note: <r> will not  re-initialize the fontdatabase,

"  \n"

      nor the buffer for rendered eps-figures. To force

"<r> Re-read current DVIfile and re-draw screen.\n"

      everything beeing re-read, use (*)<r>.

"\n"

"      Note: <r> will not  re-initialize the fontdatabase,\n"

"      nor the buffer for rendered eps-figures. To force\n"

<d> Load/kill DVIfile

"      everything beeing re-read, use (*)<r>.\n"

"\n"

      After typing <d> you may select between <l> to load a 

"\n"

      DVIfile and <k> to kill a DVIfile. 

"<d> Load/kill DVIfile\n"

"\n"

      Loading a DVIFile: 

"      After typing <d> you may select between <l> to load a \n"

"      DVIfile and <k> to kill a DVIfile. \n"

      tmview will look for a file-bookmark belonging to that

"      \n"

      file. If there is one, it becomes the current

"      Loading a DVIFile: \n"

      file-bookmark. The DVIfile will be shown as left, and

"\n"

      any defined manual-bookmarks are accessable by

"      tmview will look for a file-bookmark belonging to that\n"

      <w>. When loading a DVIfile for the first time, a new

"      file. If there is one, it becomes the current\n"

      file-bookmark will be generated.  This will be setup

"      file-bookmark. The DVIfile will be shown as left, and\n"

      with default values from the command-line options and

"      any defined manual-bookmarks are accessable by\n"

      won't contain any manual-bookmarks.

"      <w>. When loading a DVIfile for the first time, a new\n"

"      file-bookmark will be generated.  This will be setup\n"

      Killing a DVIfile:

"      with default values from the command-line options and\n"

      To kill a DVIfile means to kill its file-bookmark and

"      won't contain any manual-bookmarks.\n"

      any related manual-bookmark. Killing a DVIfile won't

"\n"

      hurt the file itself.  You don't have to kill a

"      Killing a DVIfile:\n"

      DVIfile just to load another one.

"      To kill a DVIfile means to kill its file-bookmark and\n"

"      any related manual-bookmark. Killing a DVIfile won't\n"

<q> Quit tmview 

"      hurt the file itself.  You don't have to kill a\n"

"      DVIfile just to load another one.\n"

      When quitting, a startup-file will be written. When

"\n"

      running tmview next time, you will find almost

"<q> Quit tmview \n"

      everything as you left it.

"    \n"

"      When quitting, a startup-file will be written. When\n"

"      running tmview next time, you will find almost\n"

**********************************************************

"      everything as you left it.\n"

End of help***********************************************

"\n"

\n\n\n"

"\n"

"**********************************************************\n"

char helpstr[]=HELPSTR;

"End of help***********************************************\n"

"\n\n\n";

     pfprot("IMPORTANT DEBUGINFORMATION 

     pfprot("IMPORTANT DEBUGINFORMATION \n"

break with fro %d fco %d

"break with fro %d fco %d\n"

fshr %f hof %d vof %d hof2 %d vof2 %d\n",firstrows,firstcols,

"fshr %f hof %d vof %d hof2 %d vof2 %d\n",firstrows,firstcols,

     pfprot("IMPORTANT DEBUGINFORMATION 

     pfprot("IMPORTANT DEBUGINFORMATION \n"

break with fro %d fco %d

"break with fro %d fco %d\n"

fshr %f hof %d vof %d hof2 %d vof2 %d\n",firstrows,firstcols,

"fshr %f hof %d vof %d hof2 %d vof2 %d\n",firstrows,firstcols,

  pfprot("\n\

  pfprot("\n"

warning: display: use polling when rendering eps-figures due to 

"warning: display: use polling when rendering eps-figures due to \n"

  a compiletime-option. If your svgalib is above version 1.2.10,

"  a compiletime-option. If your svgalib is above version 1.2.10,\n"

  recompiling with \"VGAHASWAITIO\" defined may speed up rendering.\n\n"); 

"  recompiling with \"VGAHASWAITIO\" defined may speed up rendering.\n\n"); 

      pfprot("\n\

      pfprot("\n"

warning: display: mode not supported on this machine. Now try -d640x480.

"warning: display: mode not supported on this machine. Now try -d640x480.\n"

  Check your svgalib configuration.\n");

"  Check your svgalib configuration.\n");

    pfprot("\n\

    pfprot("\n"

warning: display: mode -d640x480 not supported at 256 colors. Now try at 

"warning: display: mode -d640x480 not supported at 256 colors. Now try at \n"

  16 colors. This will reduce display quality and speed. Check your

"  16 colors. This will reduce display quality and speed. Check your\n"

  svgalib configuration.\n\n");

"  svgalib configuration.\n\n");

      pfprot("\n\

      pfprot("\n"

warning: display: mode -d640x480 not even supported at 16 colors.\n"); 

"warning: display: mode -d640x480 not even supported at 16 colors.\n");