
%   > if you are not using PostScript <
% use these options for the
%                       dvidrv.exe dvi{scr|hplj|dot}
% command of the emTeX system
% (the %% lines are just for printing, the %%% ones are real comments):
%
% The following options are contained in the configuiration files for dvidrv:
%   b_a5_r.cnf  (viewing) and
%   b_a5_p.cnf  (hplj printing: should be run first with /d:e, then with /d:o)
% (contained in the subdirertory tex_ware).

%What I had to do, to get a good html version as well:

%% ( this is done already, so just to log it:
% - change the original \verb delimiter from " to anything (I choosed ')
% - supertabular change to tabular for html
% - enclose fonts commands in table into { } as well (l2h does not limit their
%  scope by &)
%  )

%% eventually, for latex2html,
% - convert the input files from tex to an il2 encoding

%% run latex2html -split 5 use.ltx
%% edit the resulting html file:
% - shift the metacomment regarding charset before the title
%  (not here, this is needed just for czech titles)
% - copy the main file a directory higher, and changing "node to "use/node
%  in the links from
%  there, to keep the mess of child links out of directory listing;
%  also the style sheet reference is to be changed there (to use/use.css), and

%   bgcolor=white attribute of the body element added, to have

%   a nice observatory logo on white background

%% what is no more needed, when table (and perhaps math) extension in
%%  -html_version is not demanded (I put them there before, not knowing why):
% - adding a first line on the html version
% - clearing the cols attribute in the <table>

%%+landscape-mode  % but then the file should be processed with response L
%+columns:2 +rows:1
%+page-width:148.5mm
%+page-height:210mm
%%% booklet:
%%+section-count:1
%%+page-shift:0.17mm
%%% (Print first with /d:e and then
%%%  the back sides of the papers with /d:o)

%%% now for preview:

% not to be affected by lj.cnf /l a /t:
%+left-margin:0mm
%+top-margin:0mm

%+height:210mm
%+width:297mm
                 %------------------------------------%

% For printing the text as an A5 brochure from folded A4 sheets
%   > using PostScript <
% apply dvips to the dvi-file. From the resulting file pas_intc.ps,
% create then two files by pstops programme (ps2boo.bat will do that
% with needed layout, you shoud just supply the name of input file and
% perhaps two names of output files).
% The first file should contain the outer side,
% the second one the inner side of the sheets. (The ps-utilities are
% contained in the tex-ware subdirectory of this package.)


% cslatex or pdfcslatex are needed, to handle the IL2 encoding

% Otherwise, comment out inputec and encodingdefault,
% and change latin2 to tex notation for Czech letters (by cs_conv or cstocs)
% Eventually, this last change may have been already done for this file.

\documentclass[a5paper]{article}
\clubpenalty=10000
\widowpenalty=10000
\usepackage{longtable}

%begin{latexonly}
\ifx\pdfoutput\undefined
 \input pic_form.lt
\else
\fi
%end{latexonly}

\input symb_jh.lt
\input myhtml.lt
\hyphenation{Post-Script Ghost-Script}
\oddsidemargin 0mm
\topmargin 0mm
\headheight 0mm
\headsep 0mm
% these values can be used for an A5 brochure:
 \textwidth 128mm
 \textheight 184mm
 \hoffset -15.55mm
 \voffset -12.55mm
 \footskip 6mm

%\usepackage[latin2]{inputenc}
\renewcommand{\encodingdefault}{IL2} %% To use CS fonts
%\renewcommand{\encodingdefault}{T1}  %% To use EC (DC) fonts

\ifx\pdfoutput\undefined
\else
 \RequirePackage[latin2]{inputenc}
 \usepackage
  [pdftex,bookmarks,bookmarksopen,%backref, %backref did not work me
   pdfview=fitb,
   pdfauthor = {Jan\ Hollan},
   pdftitle  = {Package\ of\ programmes},
   pdfsubject= {Advice\ to\ users},
   pdfkeywords={Pascal, Astronomy, Ephemerides, Charts}
   ]
  {hyperref}
 %\pdfpagewidth=148mm \pdfpageheight=210mm  % a5 paper % is in preamble
\fi

\begin{document}
\english

\begingroup
\title{\bfseries Astronomic and other programmes \\
                     (written in Pascal) }

\begin{htmlonly}
% \begin{center}
       \section*{Astronomic and other programmes \\
                     (written in Pascal) }

\end{htmlonly}

\input titl_jhe.lt
\endgroup

\renewcommand{\thesubsection}{\arabic{subsection}}
\thispagestyle{empty}
\renewcommand{\contentsname}{\large\bf Contents}
\renewcommand{\refname}{\large\bf References}

\vspace*{\fill}
\tableofcontents
\newpage


\setcounter{page}{1}

\subsection{Introduction}

 The set of programmes has been made at the \emph{Nicholas Copernicus
 Observatory and Planetarium in Brno}
 (\http{www.sci.muni.cz/obsbrno}).
 It contains mostly work of members
 of the \emph{Amat\'ersk\'a prohl\'{\i}dka oblohy} (\emph{Amateur Sky
 Survey} \cite{APO}),
 whose professional member I am. The programmes solve a lot of various
 tasks I have encountered, astronomical and another ones.
% See their short overview in \verb'Programs.lst' or process the file
% you read now (\verb'use.ltx').

 All programmes and their parts are \emph{free software}, and to ensure the
 freedom further on, their use is regulated by the GNU General Public License
 as published by the Free Software Foundation, either version 2 of the
 License, or (at your option) any later version. If you do not have the
 text of the license (it should accompany the programmes as
 \verb'gpl.txt'), you will find it at
 \http{www.gnu.org/copyleft/gpl.html}.
 The same directory
 (\http{www.gnu.org/copyleft/})
 gives also the reasons, why is such specification needed and what
 \emph{free software} in general is. GNU license demands, e.g., that
 anyone, who gets some of the programmes in an executable form, would
 obtain its original text or an information, where it is available.

 The programmes can be best used by those people, who have access to the
 Borland Turbo Pascal compiler, or who will download a very good Free
 Pascal Compiler \cite{fpk}. The last one works on many platforms
 (under Linux as well). Source texts of all programmes are available
 as a packed file \verb'pas_jh.zip' at
 \httpc{astro.sci.muni.cz/pub/hollan/programmes}.

 The same address hosts also translated executable files for a PC-XT
 with numeric coprocessor (as a package \verb'exe87_jh'), for a PC
 without it (\verb'exe_jh') and for Linux PC's. The disadvantage of
 executable files is they cannot be adapted to your environment, which
 can differ in directory structure, time zone, etc.

 Some programmes need astronomical data, and these are available as
 further packages (or archives, \verb'*.zip' files). The packages are
 packed by programme \verb'pkzip' (or by programme \verb'zip', on
 UNIX platforms). They can be ``unzipped'' by e.g.\\
 \verb'pkunzip /d pas_jh.zip' \ or by \ \verb'unzip pas_jh.zip'.


\subsection{Using computers with MS-DOS}

 To make a computer serve you well, you need to configure it properly.
 Start with the file \verb'AutoExec.bat' in the root directory of
 MS-DOS\footnotemark[1]. I recommend you very much to define the
 beginning of ``environmental variable'' \verb'Path' (list of
 directories, where executable files are sought) as \\
 \verb'Path=C:\bat;C:\DOS;C:\s\exetpu;' \\
 --- the very beginning is the directory with batch files (programmes in
 the operating system language), which you use to start programmes
 contained in many different directories. There is no need to include
 these many directories into the \verb'Path' variable.

 \footnotetext[1]{
 This simple operating system (or its analogues \hbox{$\ast$-DOS})
 used to be the only one for ``personal computers''. It can be run on
 these computers (at least simulated) from more sophisticated systems
 as well, and so most of the programmes written for this old system
 can be used further on.}

 For example, you can start the Windows system by \verb'win.bat' or
 just \verb'w.bat', which read probably \verb'C:\Windows\win.com' ---
 no other programmes in the \verb'\Windows' directory are run by MS-DOS,
 and so it is dull to include that huge directory in the \verb'Path'.
 (Why it is so common? MS-DOS makes no \verb'\bat' directory during
 its installation, and so no programmes are relying on it during their
 own installation.)

 Batch files enable to define starting values for various programmes.
 For example, I have a batch \verb't.bat', which reads
 \verb'C:\s\t602\t602.exe /EGAm %1 %2', and by which I can easily open
 up to two files in that popular Czech editing program, and use a bit
 higher letters. Another batch
 you will surely need is \verb'tpc.bat', running a command-line
 compiler of Turbo Pascal (you can place a \verb'/m' parameter there,
 which makes sure that changed units will be compiled as well, or
 parameter \verb'/l', to overcome insufficient free memory). The
 Borland system for developing programmes is started by a batch
 \verb'tp' on my computers, Free Pascal Compiler by \verb'fp'.

 You would do well to copy the batch files contained in directories
 \verb'Astro' and \verb'Util' of the archive \verb'pas_jh' into the
 \verb'\bat' directory. From the root directory of the archive, copy
 two batch files there, \verb'tpc.bat' and \verb'tpc_all.bat'. The
 first one compiles one file, the other one compiles all files in a
 current directory by the fist one. Failing compilations are logged in
 \verb'fail_tra.lst'.

 The \verb'ExeTPU' directory, as I call it, has to appear in the
 \verb'tpc.cfg' file in the \verb'/E' parameter --- there the compiled
 units and programmes should be placed, and there the compiler tries to
 find the units compiled before. The \verb'tpc.cfg' file should reside
 in the same directory as the compiler \verb'tpc.exe' itself (which I
 call by \verb'tpc.bat').

 The \verb'Path' variable should continue (or end) with a directory
 containing various viewing and packing programmes, in my case
 \verb'C:\s\nc'. There I have the programmes for creating and expanding
 archives. To expand an archive, make a directory for it (it may have
 the same name), copy the archive there, and issue a command
 \verb'pkunzip -d' \emph{name of archive} (suffix \verb'.zip' can be
 omitted)\footnote{When using unzip, the -d switch is default --- it
 may be a good idea, having a batch file doing that for pkunzip as
 well, i.e., creating always the needed subdirectories.}. The
 \verb'-d' switch ensures restoring the needed subdirectory structure.
 The archive file itself can be then deleted.

 In case of archive \verb'BSC5_cd' with a part of \emph{The Bright
 Stars Catalogue} (\cite{BSC}) there is a batch of the same name (i.e.,
 \verb'BSC5_cd.bat'), which makes that task, and then it runs a
 database programme which changes the files into a working form. To be
 able to run a database program, it needs a \verb'd.bat' file with one
 parameter (in my case it reads \verb'C:\s\db3\dbaza.exe %1'), which
 starts that program. If the programme is \verb'dBaseIII+',
 \verb'Append.exe' (MS-DOS resident program) should run with a
 directory containing that program. In my case it is accomplished by
 \verb'ApdB.bat' reading: \\
 \verb'LH Append /e' \\
 \verb'Append c:\s\db3;c:\s\tp\bgi;'

 If your \verb'Autoexec.bat' does not execute the above command, then
 (for programmes using a graphic mode) it should contain a line like \\
 \verb'Set BGI=C:\s\tp\bgi'\\
 which informs the programmes where the graphic drivers (Borland Graphic
 Interface) reside. The same directory contains usually the Borland
 unit \verb'Graph.tpu', and so it is to be included in the \verb'/U'
 parameter of \verb'tpc.cfg', as well as the directory with the source
 files of units (\verb'C:\s\Pas\Units' in my case).

 The above examples say, that I have most of software I use in the
 \verb'\S' directory. It is hidden there, as I do not need to see it
 very often, and I do not want to be bored by its long list in the
 root directory \verb'C:\'. When I am looking at the programmes at all,
 it's just into their source texts (I have them in the \verb'c:\s\PAS'
 directory, where I get any time by \verb'Pas.bat').

 If your computers access more than one disk, you should avoid
 starting file names by a disk letter in the batch files. Instead,
 make a line in
 \verb'Autoexec.bat' reading like
 \verb'Set SWDir=C:\s'
  and just then
 \verb'Set BGI=%SWDir%\tp\bgi'.
 Similarly, explicit \verb'c:\s' should be replaced by \verb'%swdir%'
 in all batch files. If the software will then shift to a disk
 \verb'D' (you will shift it, or the disk will have such letter when
 accessed from another computer), it is sufficient to change the
 letter in the definition of environmental variable \verb'SWDir', and
 the rest will work as previously. If the space for environmental
 variables does not suffice, you can enlarge it by a line in the
 \verb'Config.sys' reading like
 \verb'Shell=c:\command.com /p /e:1024'.
 Then, 1024 bytes of environmental space will be available instead of
 default 256 B.


\subsection{Development of programmes
                \textmd{(remarks for Pascal users)}}
 The programmes are used on PCs, and are written in the Borland Turbo
 Pascal language. We use version 6.0 of the language, but no its new
 features with respect to some previous versions. Thanks to the
 existence of \www{Free Pascal Compiler}
 {http://www.freepascal.org},
 they can now be developed not only in MS-DOS, but also in Linux or
 even in some still popular commercial systems.

 The programmes have been developed gradually, according to my needs and
 possibilities. Included are also similarly developed programmes of my
 colleagues, who agree with their spreading under the same GNU General
 Public License \cite{GPL}. We have used mostly algorithms from a
 booklet by Zden\v{e}k Pokorn\'y \cite{Pok} (who himself used the book
 by Jan Meeus \cite{Meeus}) and from text by Jana Vondr\'ak in
 \cite{AstrPrir}.

 As the programmes became more complicated, or as the author could not
 remember algorithms of old programmes, a need for some documentation
 emerged, at least in the form of comments in the source
 codes. In spite of that, the comments remained mostly quite
 insufficient, and the programmes are very far from the ideal of
 \emph{literate programming}, as formulated and made true by Donald
 Knuth (author of programmes like \verb'WEB' and \TeX \cite{TeX}).
 Further, the programmes have been supplemented to behave well, like
 (e.g.) programmes of MS-DOS which explain their meaning and use when
 being started a suitable way. These instructions how to use the
 programme are contained at the beginning of its text.

 Some time ago, I have noticed two problems of Borland Turbo Pascal
 when run with or without numeric co-processor. The first one concerns
 different ways of rounding. Pascal itself rounds real numbers ending
 .5 to a greater absolute value, whereas numeric co-processor to an
 even number. I have changed in some programmes the rounding procedure
 to a third possibility, namely always to a greater value (by a
 function RoundUp). The second problem concerns formatting. With
 co-processor, all unformatted real numbers are output as extended,
 with e.g. four digits in exponent. Some formatting procedures at the
 beginning of \verb'str_num' unit overcome different behaviour of
 different hardware.

 The programmes are English-written, with few exceptions. Why is that
 so, when most of the users are speaking Czech? The main reason is,
 that the author hates disabled Czech without diacritics, and that
 Czech diacritics has not just one possibility how to be implemented
 in the computers. The problem of two main MS-DOS-based ``code pages''
 can be solved by the programme \verb'CS_Conv'. But the English programmes
 are easier to read, when names of variables, subroutines and comments
 are English as well as the programming language. And each potential
 user of these programmes surely reads English, with some effort at
 least.

 If you make some programme better, and you suppose, that your
 adaptation may suit another people as well, please give them whole
 this package including your addition. I welcome you sending the
 modified programme me as well. I will gladly discard the original work
 and replace it by the same-named version by you in our set.

 As follows from the License \cite{GPL}, everybody can modify the
 programmes and use their parts in her/his own programmes. If such
 programmes are spread further, they are obliged to remain \www{free
 software}
 {http://www.gnu.org/copyleft}
 subject to the same Public License.

 If the change of a programme concerns only
\bi
\item the list of directories where the data files are sought for, or
\item the five default constants concerning the observing site (these are at the
  beginning of the \verb'solar_ut' unit),
\ei
 the programme can keep
 its name and no notice on the change is needed. The same holds
 in case, when just explanations are supplemented (it may be
 needed in some cases, to make the use of the programme
 understandable to another people than to author himself).


\subsection{Handling the programmes}
 Some programmes explain how to use them, whenever they are run
 without parameters (this applies for those ones, which always need
 some parameters). Another ones offer instructions to users, if at
 least one of parameters is \verb'?' (or \verb'/?' or \verb'-?').
 Programs with long explanation should give a possibility to write it
 into a file instead to a screen. Mostly the standard redirecting of
 the output can be used, as \verb'fGCVS >> fGCVS.hlp'. Some
 programmes, which have to react on each key during their work, make
 redirecting impossible, however (the \verb'crt' tool of Borland Turbo
 Pascal language is guilty). These programmes create a file
 \verb'*.hlp', when asked to do that by \verb'/h' (or \verb'-h')
 parameter. For example, \verb'graph_d -h'.

 All of the programmes are controlled by the parameters on the command
 line. Saying \emph{parameter}, we understand a ``word'', single
 parameters are (as usual with real words) separated by spaces.
 Controlling programmes by parameters is comfortable thanks to the
 fact, that the command can be repeated many times with just small
 changes of parameters (directly from MS-DOS you can do it easily,
 when the \verb'DOSKey /insert' runs). Even greater advantage is a
 possibility to make batch files (i.e. \verb'*.bat'), where some
 parameters are defined already (e.g., your geographical coordinates).

 The above-mentioned programme \verb'graph_d' is one of few
 exceptions. If you use it for polynomial (usually linear) regression
 of data, or if you try to find their axis of symmetry, then the
 programme asks you some questions also in the course of the work.
 This conversation is implemented in a rather simple way (it is an old
 programme already, what appears also through an unusual shape of its
 command-line parameters), but it suffices its task.

 Most programmes in our set, which produce a graphic output on the screen,
 can simultaneously create a corresponding file with a picture in \LaTeX or
 PostScript language (file \verb'*.eps'). Using them, you can produce
 prints with unlimited resolution, and modify them before the print by any
 text editor. This is a notable advantage over those commercial programmes
 which offer a mere possibility to copy a screen on the paper. As far as
 PostScript \cite{PostScript} is concerned, it is language of all
 advanced printers and photo-setting machines. If you have none, install
 GhostScript (\http{www.cs.wisc.edu/~ghost})
 into your computer. Its supplement PSView can be then used for
 comfortable viewing of PostScript outputs on the screen.

 As the graphic screen may pose problems in some cases (e.g., on Linux
 text console), the graphic programmes may be converted to text
 versions, which produce just the PostScript output (there are
 conversion batch files available).

\subsection{Remarks on selected programmes}
 I have mentioned the programme \verb'Graph_d' already. It produces
 graphs and histograms, preferably from files of \verb'*.dbf' type. It
 can handle also text files, which have some columns of numbers inside
 of them. Its another special feature is, that it can stack the data
 according to the given period, or even find their symmetry axis (this
 is a common task in astronomy).

 The same directory \verb'Util' contains a couple of another
 programmes I often use. One of them is a programme \verb'CutBE',
 which can copy a part of any (large) file, and by running several
 times, divide the file to several parts (see batch file
 \verb'cut10'). The copied parts of reasonable size can be then edited
 by common editing programmes and by a MS-DOS command \verb'copy'
 glued together to a single file again (see \verb'copy10.bat'). The
 \verb'CutTrBla' programme cuts away obsolete spaces at ends of lines
 of a text file (most editing programmes make it as well, but just for
 small files).

 From the \verb'Astro' directory I use many programmes quite often. The
 most complicated one is contained in a separate directory \verb'Map_BSC'
 and described in the last section of this booklet. Another mapping
 programme is \verb'Map_mGSC'. It uses the famous \emph{Guide Stars
 Catalogue}, in the version of the MegaStar atlas \cite{MegaStar}. To be
 able to use it, you have to buy a CD with that marvelous computer star
 atlas. As a facility not contained in the MegaStar itself (at least not in
 version 3), my programme offers a possibility to create maps according to
 command-line parameters or according to parameters in some of the
 configuration files. Both \verb'Map_*' programmes can be run by means of
 batch files \verb'm*.bat', which, e.g., make a map centered on a given
 object (a comet or Moon). The new versions of MegaStar can do it as well,
 but it takes more time to make them do so. I used to write just
 \verb'mb_hb' to have an actual map of the surroundings of the Hale-Bopp
 comet.
\footnote
 {In April 2000 I have added a possibility to use the standard
 files with description of
 trajectories \cite{elements} in the MPC and xpehem formats.}

 As said above, these graphic programmes can produce also true PostScript
 \cite{PostScript} (or \LaTeX \cite{TeX}) file, easy to edit. However, even
 the screen is nicer than for most star-mapping programmes, as grayscale is
 employed to get smooth stars, with faintest ones visible only using the
 full luminance. If you like to save the screen to a file, use, e.g., the
 Screen Thief programme by Villa Software \cite{ScreenThief}. Some examples
 I offer have been saved this way \cite{Examples}.

 Then there is a group of programmes giving tables of positions of
 celestial bodies and sky events, namely \verb'Sun', \verb'Moon' and
 \verb'Planet' programmes. Various small programmes deal with
 transformations of coordinates and of photometric quantities ---
 these may be quite instructive. A large programme \verb'SunDial'
 offers a proposal and accurate construction of sundials and computes
 insolation of absorbers in solar collectors.

 In the \verb'Screen' directory the most useful programme is
 \verb'VMod'. I employ it mainly through \verb'v.bat', which reads
 \verb'Vmod 3'. When a screen is due to some conflict of software and
 hardware entirely confused, entering this only letter is sufficient
 to see again what you write.

\subsection{Final remarks}
 For further information on the programmes please see their overview
 on the following pages.
% (Or read \verb'programmes.lis' file or process this \verb'pas_int.ltx'
% file. The files have been edited from a file made by \verb'describe.bat'.
 Some programmes of \verb'Screen' and \verb'Tisk' directories, useful
 for few people, are not contained there; if you would be interested
 in them, you would to look directly their source codes (rather then
 just to translate and try them).

 I will be grateful for information on errors in the programmes. I
 will even enrich the programmes according to your wishes, with
 respect to my time possibilities, mood and your insisting on me. But
 I prefer the programmes being supplemented by you; just blame me for
 insufficient comments in the source codes. By the way, the first
 changes in the programme should be your comments on your assumptions
 on the inquired algorithm, whenever you get an idea, what a given
 part serves for.

 I hope that at least some programmes will prove useful to you, as
 they have already for my colleagues. I thank them for their
 development (in an alphabetic order the involved people are David
 Motl, Rudolf Nov\'ak, Leo\v{s} Ondra, Tom\'a\v{s} Rezek and Martin
 \v{S}kutek, what is always mentioned in the comments inside the
 programmes) and for their suggestions.


% \vfill
%\newpage

\subsection{List of programmes}
\input programs.lt

%\vfill
%\newpage

\normalsize
\input map_bsc.lt

\vfill

\begin{thebibliography}{99}
\ifx\pdfoutput\undefined
 \addcontentsline{toc}{subsection}{References}
 % there is definitely a possibility to make this section a target in pdftex
 % even befor this hyperref ability will be functional
\fi
\raggedright

\bibitem{pas}
 The source texts and executable files are at \\
 \http{astro.sci.muni.cz/pub/hollan/programmes},
 which is the same as \\
 \wwws{ftp://astro.sci.muni.cz/hollan/programmes}
\bibitem{GPL} GNU General Public License, see
 \http{www.gnu.org/copyleft/gnu.html}.
 The same directory
 (\http{www.gnu.org/copyleft/})
 gives reasons for this license.
\bibitem{APO}
 See \http{www.ian.cz/apo} (mostly in Czech only)
\bibitem{fpk}
 Free Pascal Compiler, see
 \http{www.freepascal.org}
\bibitem{Pok}
 Pokorn\'y, Z.: Astronomick\'e algoritmy pro kalkul\'atory. Hv\v ezd\'arna a
 planet\'arium hl. m. Prahy, 1984.
\bibitem{Meeus}
 Meeus, J.: Astronomical Formulae for Calculators. Willmann-Bell,
 Richmond, Va, 1982.
\bibitem{AstrPrir}
 Wolf, M. et al: Astronomick\'a p\v r\'\i{}ru\v cka. Academia, Praha 1992.
 ISBN~80-200-0467-X
\bibitem{BSC}
 The Bright Star Catalogue,  5th Revised Ed. (Preliminary Version);
     Hoffleit D., Warren Jr W.H.;
    \verb'<'Astronomical Data Center, NSSDC/ADC (1991)\verb'>'.
 Original form available as
 \wwws{ftp://cdsweb.u-strasbg.fr/pub/cats/V/50},
 a dBaseIII+ format version as
 \wwws{ftp://astro.sci.muni.cz/hollan/data/bsc5dbf.zip}
\bibitem{Hipparcos}
 ESA, 1997, The Hipparcos and Tycho Catalogues, ESA SP-1200. See
 \http{astro.estec.esa.nl/Hipparcos} or
 \http{cdsweb.u-strasbg.fr/hipparcos.html}.
 The catalogues can be downloaded from
 \wwws{ftp://cdsweb.u-strasbg.fr/pub/cats/I/239} even in the FITS format,
 which can be readily converted (by \verb'fit2dbf') to the dbf format.
\bibitem{LittAtl}    { \catcode`\_=13\def_{\_{}}
 Little Star Atlas, see
 \http{astro.sci.muni.cz/pub/hollan/data/litt_atl}
 }
\bibitem{BSH}
 Du\v sek, J., Hollan, J., Gabzdyl, P.: B\'aje\v cn\'y sv\v et hv\v ezd. Hv\v ezd\'arna a
 planet\'arium Mikul\'a\v se Kopern\'\i{}ka v~Brn\v e, 1996. ISBN 80-85882-03-5
\bibitem{MegaStar}
 MegaStar, version 1.5 CD, a computer star atlas by E.L.B. Software (by Emil
 Bonanno).
 Information on the current version (having a different format)
 is available on
 \http{www.willbell.com/software/megastar/index.htm}
\bibitem{elements}
 Files with elements of tractories of icy and stone minor planets
 are available at
 \http{cfa-www.harvard.edu/iau/Ephemerides/index.html}
\bibitem{PostScript}
 PostScript, a language by and trademark of the Adobe Corporation, see
 \http{www.adobe.com/print/postscript/main.html}
\bibitem{ScreenThief}
 ScreenThief, a program by Villa Software, available, e.g., at
 \http{www.simtel.net/simtel.net/msdos/graphics-pre.html}
 as st201f.zip. A local copy is
 \wwws{ftp://astro.sci.muni.cz/hollan/programmes/st201f.zip}
\bibitem{TeX}
 See pages of \TeX{} Users Group,
 \http{www.tug.org}
\bibitem{CSTUG}
 \v Ceskoslovensk\'e sdru\v zen\'\i{} u\v zivatel\accent23u
 \TeX{}u, see \http{www.cstug.cz}
\bibitem{Examples}
 Examples of screens captured from star-mapping programmes \verb'map_bsc'
 and \verb'map_mgsc' can be seen at
 \http{astro.sci.muni.cz/pub/hollan/programmes/images}.
\bibitem{rainbow}
 Twocolor glasses for viweing anaglyphs (as well asl polarization
 and diffraction ones) sells, e.g.,
 \http{www.rainbowsymphony.com}


\end{thebibliography}

\vfill
 %\enlargethispage{3mm}

\ifx\pdfoutput\undefined

\newpage

~\vfill \newpage

~\vfill

\else
\fi

\thispagestyle{empty}
 \noindent
 Jan Hollan              \hfill
 \www{Hollan@Ped.MUni.cz}{mailto:hollan@ped.muni.cz} \\
 Hv\v{e}zd\'arna a planet\'arium Mikul\'a\v{s}e Kopern\'{\i}ka v~Brn\v{e}, \\
 (N. Copernicus Observatory and Planetarium in Brno) \\
 Krav\'{\i} hora 2, CZ -- 616 00  Brno \hfill +420 (5) 41 32 12 87 \\
  \httpc{astro.sci.muni.cz/pub/hollan}
  \centerline{\wwws{ftp://astro.sci.muni.cz/hollan}}

\bigskip
\centerline
{(last modification of the text: April 2000)}

\end{document}

