\documentclass[a4paper,10pt]{article}
\usepackage{graphicx}

\title{Xlog manual}
\author{Joop Stakenborg, PG4I}

\begin{document}

\maketitle

\begin{abstract}
This manual described the use of xlog, an open source logbook for amateur
radio operators. It is available as html from the menu
(Help $\rightarrow$ Manual or Ctrl + h).
\end{abstract}

\section{Description}
xlog is a logbook program for amateur radio operators, written with the
help of the GTK+ libraries. The main xlog window consists
of a button bar, QSO frame, and a browseable log. Logs will be saved to a flat
text file. You can create, open and close logs as you need them. There
is an optional scoring window available which keeps track of the most important
awards. A ``worked before'' window shows QSO's with the same station you
are logging. An optional keyer window interfaces to cwdaemon and is useful for
contesting.

\subsection{Options and arguments}
\begin{center}
\textbf{xlog} [option] \textless log1.xlog \textgreater \textless log2.xlog \textgreater
\end{center}

You can either open logs from the command line or,
if there are no logs entered, logs as set in the preferences dialog will be
opened.

\medskip 

List of options:
\begin{description}
 \item[-h]Show summary of options and exit
 \item[-v]Output version information and exit
\end{description}

\subsection{First Use}

\begin{figure}[h]
 \centering
 \includegraphics{../images/xlog-newlogdialog.png}
 \caption{New log dialog}
\end{figure}

When xlog is first started, an empty window is shown. You must select
"Log $\rightarrow$ New" from the menu (Ctrl+N) to create a new log.
QSO's are entered into the QSO frame on the left of the main window. Clicking
the Date button will update the date field, the UTC button will update the UTC
field.

\begin{figure}[h]
 \centering
 \includegraphics{../images/xlog-mainwindow.png}
 \caption{The main xlog window}
\end{figure}

After all the fields are entered, click on the \textbf{Write} in the button bar,
to write the
QSO to the log list on the right side of the main window. QSO's can be deleted
from the log by selecting a row in the log list and clicking on \textbf{Delete}.
Likewise, a log entry can be changed by selecting a row in the log, changing
the QSO in the QSO frame, and clicking on \textbf{Update}. Finally, selecting
"Edit $\rightarrow$ Clear All" from the menu will Clear all the fields in
the QSO frame.

\subsection{Keys}
All of the above commands are available as shortcuts.
For a list of keys used by xlog (in the English language)
see the "Keys" window from the help menu (Ctrl+z).
Most of the buttons in the QSO frame can be clicked using the Alt
key together with the associated underlined character in the button.
If any of the labels are underlined the entry next to it will get focus when
the Alt key is used, when a default is present it will be filled in.
You can access the menu with Ctrl-F10. You need to make sure that your
window manager does not use Ctrl-F10, e.g. it is used by xfce to access
the 10th desktop.

\pagebreak 

\section{Preferences}
xlog stores and recalls several settings in GKeyFile format in the file
\$HOME/.xlog/xlog.cfg. To change these, select
"Settings $\rightarrow$ Preferences"
from the menu. You will see 4 different pages.

\subsection{Info page}
In order to calculate the correct distance to your location, you have to enter
your longitude and latitude in the Info page. Changing it will automatically
update the QTH locator field. You can also choose
whether the distance should be displayed in Kilometers or
Nautical Miles.

\begin{figure}[h]
 \centering
 \includegraphics{../images/xlog-preferencesdialog-info.png}
 \caption{Preferences dialog - Info page}
\end{figure}

The QTH locator field is important when you intend to make VHF/UHF QSO's
and you have a locator field in the log.

\medskip
The main xlog window has a button next to the callsign entry. When clicked it will
lookup the callsign with your internet browser on your preferred server.
It takes the form http://www.qrz.com/<call>, where <call> will be replaced
with the callsign.

\medskip
The use of the tilde character is explained in the "Keyer window" section.

\pagebreak 

\subsection{General page}
This page allows you to choose an editbox to enter band and mode
instead of using the default optionmenu. This is especially useful
when using hamlib, so the extra digits of your frequency can
be filled in. When "use free fields to add
distance and azimuth to the log" is checked, distance and azimuth will
be calculated from the locator field (when present) and added to the log.

\begin{figure}[h]
 \centering
 \includegraphics{../images/xlog-preferencesdialog-general.png}
 \caption{Preferences dialog - General page}
\end{figure}

When 'Enable type and find' is checked, all the logs will be searched
for a callsign match and when found, fill in name, QTH, locator and remarks
like in the previous QSO.

\pagebreak 

\subsection{Logs page}
In the Logs page you can decide where to save your logs and which logs to load
at startup (in case there are no logs entered at the command line). Of course,
you have to restart xlog and be sure to move your logs there. You can use
wildcards or a list of logs separated by a comma. Extension .xlog will be
automatically added, e.g. when using wildcards, 'p*' will load all logs
starting with 'p' and ending with '.xlog'.

Logs can be loaded by alphabet or by last modification date. In case you use
the last option, log loading can be manipulated by using 'touch'.

\begin{figure}[h]
 \centering
 \includegraphics{../images/xlog-preferencesdialog-logs.png}
 \caption{Preferences dialog - Logs page}
\end{figure}

You can also set the automatic saving method in this page. When selecting
autosave, the interval between saving of the logs needs to be selected.
Selecting a value of zero will disable autosave: you will need to use 'Ctrl+s'
every time a log is changed.

\pagebreak

\section{Hamlib}
Xlog is compiled with hamlib support, so you can read your rig's frequency,
mode, power and S-meter over the serial port.

\subsection{Hamlib preferences}
You must select the model of your rig and the port used
from the list available in the hamlib page of the preferences dialog.
If you want to use RPC rig, you should select localhost as a port. The same
page allows you to display a dockable frequency meter and s-meter
on the statusbar.

\begin{figure}[h]
 \centering
 \includegraphics{../images/xlog-preferencesdialog-hamlib.png}
 \caption{Preferences dialog - Hamlib support}
\end{figure}

When hamlib is enabled, 3 clickable buttons are added to the QSO frame, so you
can easily fill in frequency, mode and signal strength in the appropriate
fields. If your log records power (required in some countries), there is also a
clickable power button in the QSO frame. You can either chose to poll your
rig continuously with a certain time interval or just retrieve rig data
when using "Edit $\rightarrow$ Click All" or Ctrl-k. Your hamlib port can be configured
in the hamlib page of the preferences dialog. You can enter things like: 
rts\_state=ON,timeout=600,serial\_speed=19200 here.

\subsection{Testing hamlib}
At his point you should probably read your rig's manual, to see how you
should hook up your rig to the serial port. For my kenwood rig, I need
a standard serial cable with two 9-pin connectors. You also need write
permission to the serial port. On my system, this means I need to add
myself to the dialout group, with a command like:

\begin{quote}
\$ adduser 'username' dialout
\end{quote} 
 
Next, you can test hamlib with rigctl, a binary distributed with hamlib.
See which rigs are supported:

\begin{quote}
\$ rigctl --list
\end{quote} 

Then start rigctl with your model number, e.g. '210' for a kenwood TS-870S,
hooked up to COM2:

\begin{quote}
\$ rigctl -r /dev/ttyS1 -m 210
\end{quote} 

Now you can check out if mode, PTT, frequency, signal strength and power
(all used by xlog) are retrieved. At the 'Rig command:' prompt, type:

\begin{quote}
\begin{description}
\item[f]: retrieve frequency
\item[m]: retrieve mode
\item[t]: retrieve PTT (TX/RX mode)
\item[l] and 'STRENGTH': retrieve signal strength (-54=S0 and 0=S9)
\item[l] and 'RFPOWER': retrieve rig power (0.39 = 100 Watts)
\end{description}
\end{quote} 

The hamlib FAQ at \url{http://hamlib.sf.net/faq.html} gives some answers
to common problems. You could also ask around on the hamlib mailing list, see:
\url{http://lists.sourceforge.net/lists/listinfo/hamlib-developer}.

\pagebreak

\section{Printing}
Printing can be done in 2 styles: landscape with 30 QSO's per page and
portrait with 50 QSO's per page. These styles can be chosen from the
"Page Setup" dialog, selected from the Log menu. The default for printing
is portrait.

\begin{figure}[h]
 \centering
 \includegraphics{../images/xlog-pagesetupdialog.png}
 \caption{Page Setup dialog}
\end{figure}

A fixed 12 point lettertype is used for printing. You need to make sure the
log fits the paperwidth by either selecting the correct style or selecting
a magnification factor in the "Page Setup" page of the print dialog. You can
also select columns to print in the "Columns" page of the same dialog.

\begin{figure}[h]
 \centering
 \includegraphics{../images/xlog-printdialog.png}
 \caption{Print dialog}
\end{figure}

The print dialog allows you to choose a configured printer and change it's
settings, but you can also print to a postscript or pdf document in a selected
directory.

\pagebreak

\subsection{QSL labels}
glabels is a gnome application for printing business cards and labels, see
\url{http://snaught.com/glabels}. It is designed to work with various laser/ink-jet
peel-off label and business card sheets that you'll find at most office supply
stores. The following works with a glabels version higher than 0.4.

\medskip 

You can use the 'Export' dialog for exporting the log to a type called
'TSV'. This will save your log fields in a TAB separated file. The fields you
want to export can be set in the "Export" page of the
``Settings $\rightarrow$ Dialogs and Windows``
dialog.

\begin{figure}[h]
 \centering
 \includegraphics{../images/xlog-exportsettings.png}
 \caption{Settings for the export dialog}
\end{figure}

The exported file can be imported into glabels using the template
called qsllabels.glabels in /usr/[local/]share/doc/xlog/glabels.
In case you need to print multiple QSO's per label, enter a number into the
"Group by callsign" field.

\begin{itemize}
\item Start glabels
\item Open qsllabels.glabels
\item Select 'Merge properties' from the Tools menu
\item Point 'location' to the exported labels file
\item Don't change any of the Custom field keys, just click 'OK'
\item You are now ready to print
\end{itemize}

You should customize the label sheet by using "Edit $\rightarrow$ Select All" from the
menu, click on 'New', select the apropriate sheet from the pulldown menu,
use "Edit $\rightarrow$ Paste" to copy the fields into the new sheet and move them around
with your mouse until the fit on the label. Save this file to use as a
template for your QSL labels.

\pagebreak

\section{Log-editor}
The log-editor, when selected from the tools menu, can be used to display or
hide a number of columns in the log. 2 columns allow free entry, they can be
given any name. Changes to the log columns will be committed once you save the
log.

\begin{figure}[h]
 \centering
 \includegraphics{../images/xlog-logeditor.png}
 \caption{The log editor}
\end{figure}

Please note that it maybe desirable to select a common name for a free column
when using ADIF export as described in the ADIF specifications at
\url{http://www.hosenose.com/adif/adif.html}, section 3: Field Definitions.

\medskip 

The log-editor can also be used to set the columnwidth of the log. You should
enter a number higher than 20. Changes to the column width will apply to all
the logs that are currently open. Only the number column allows a zero width,
you can use it to hide this column.

\pagebreak

\section{Log searching}
"Edit$\rightarrow$Find" or ctrl+f will bring up a small dialog which you can
use to search the log. You can either search for a callsign or search all of
the logfields by checking "Search all fields". It is also possible to restrict
searching to the current log.

\begin{figure}[h]
 \centering
 \includegraphics{../images/xlog-searchdialog.png}
 \caption{Search dialog}
\end{figure}

This dialog will be kept open every time the enter key is used or the Find
button is clicked. You must use the Close button to close this dialog.

\section{Dupe checking}
A log can be checked for dupes from the tools menu. There are some restrictions
on the frequency field when used in dupe checking. It should either contain a
'dot' after the MHz number or contain 3, 6 or 9 numbers after the Mhz number.

\begin{figure}[h]
 \centering
 \includegraphics{../images/xlog-dupecheckdialog.png}
 \caption{Dupe check dialog}
\end{figure}

When using hamlib, the total amount of numbers in the frequency field can be
selected in the hamlib page of the preferences dialog.

\section{Log Sorting}
If you select "Tools$\rightarrow$Sort by Date", your log will be sorted by date and
time. Log sorting assumes that the whole log is created with the same locale.
Also, the log date should have the format "dd mmm yyyy" in your locale, e.g.
"01 May 2004" in English, "01 mai 2004" in French, etc. You can check the
correct month name for your language settings by using the command:

\begin{quote}
\$ date --date='01 May'
\end{quote}

The time should be formatted as "HHMM", e.g. "1423". The sorted log will be
marked as changed. It is recommended to save the log under some other name,
so the original log will be safe. You should check this log for correct dates
and times before overwriting the original log. If the log is not correctly
sorted, start xlog from a terminal to see if sorting produces any errors.

\pagebreak

\section{Defaults}
"Settings $\rightarrow$ Default" will show a dialog where you can fill in default values for
logging. These values will be used when selecting "Edit $\rightarrow$ Click All" from the
menu.

\begin{figure}[h]
 \centering
 \includegraphics{../images/xlog-defaultsdialog.png}
 \caption{Defaults dialog}
\end{figure}

\section{Worked before}
When you select Worked Before from the tools menu, a dialog will be displayed
which shows a sorted list of contacts while you are typing in the callsign
entry. This is especially useful in contests.

\begin{figure}[h]
 \centering
 \includegraphics{../images/xlog-workedwindow.png}
 \caption{Worked before window}
\end{figure}

The number of columns shown in this dialog can be adjusted from the
"Settings $\rightarrow$ Dialogs and Windows" menu (first page).

\pagebreak

\section{Scoring}
Xlog will keep track of your DXCC scoring and will display worked and confirmed
countries and DXCC information in a separate window, called the scoring window.
The top table of this window displays the number of times a country is worked
or "0" if confirmed. The bottom table shows the total number of DXCC countries.

\begin{figure}[h]
 \centering
 \includegraphics{../images/xlog-scorewindow.png}
 \caption{Scoring window}
\end{figure}

Xlog can also keep track of
WAC (Worked All Continents), 
WAS (Worked All States), 
WAZ (Worked All Zones)
and IOTA (Islands On The Air) 
scoring. You will
have to enable it in the Scoring page of the
"Settings $\rightarrow$ Dialogs and Windows" dialog. This will add an extra
page to the scoring window. The "Settings $\rightarrow$ Dialogs and Windows"
dialog can also be used to enable Grid Locator scoring. For this to work the
log will need to have the Locator field added.

Xlog will look up the prefix of a callsign and display DXCC information together
with calculated distance and beam heading in the left frame. In a log where a
QTH locator field is present, distance and azimuth to the locator is calculated
and displayed in a separate frame.

If DXCC lookup fails you can enter a valid country in the AWARDS
field of the log. The correct format for this string is 'DXCC-' followed
by the desired prefix (see ''Help $\rightarrow$ DXCC list`` from the menu).
Continent lookups can be corrected by adding a 'WAC-' string
followed by the continent to the AWARDS columns. Valid continent names are
AS, AF, OC, NA, SA and EU. The same goes for WAZ scoring, the correct format
for this is 'WAZ-' followed by a number from 0 to 50.

The AWARDS field can also be used to add WAS and IOTA scoring. The 'WAS-'
string needs a US state added, valid US states are:
AL, AK, AZ, AR, CA, CO, CT, DE, FL, GA, HI, ID, IL, IN, IA, KS, KY, LA, ME, MD,
MA, MI, MN, MS, MO, MT, NE, NV, NH, NJ, NM, NY, NC, ND, OH, OK, OR, PA, RI, SC,
SD, TN, TX, UT, VT, VA, WA, WV, WI and WY.
The "IOTA-" string needs a continent followed by a number, e.g. "IOTA-EU-038"
is the island of Ameland of the Dutch northern coast.


\pagebreak

\section{Keyer window}
The keyer window, available under the Tools Menu, is in fact a simple
(contesting) interface for cwdaemon. You can program all of your function keys
with CW messages and control your speed here. Clicking the stop button or
using the 'ESC' key will abort any messages. You can also see a counter for
serial numbers, a toggle box for short serial numbers and a menu for selecting
either CQ or "Search \& Pound" mode.

\begin{figure}[h]
 \centering
 \includegraphics{../images/xlog-keyerwindow.png}
 \caption{Keyer window}
\end{figure}

The bottom text entry can be used to typecharacters. The function key entries
can use the following macros:

\begin{description}
\item[\%] - my callsign
\item[@] - his callsign
\item[\#] - number counter
\item[\~] - last exchange message
\end{description}

The \~{} (tilde) macro is used for forwarding the last received message.
For example, if we make a contest QSO we send "599ABC" and receive "599XYZ".
The next QSO we will send "599XYZ" using the \~{} macro. This macro would
typically be used in the keyer window and defaults dialog. The initial message
can be set in page 2 of the preferences dialog.

The number counter will auto-increment. The defaults dialog can be used to fill
in default reports for a contest, the \# and \~{} macro can be used in the
TX(RST) field of this dialog.

\subsection{Running a contest in CQ mode}
\begin{description}
\item - cursor on the callsign field
\item - \textless enter\textgreater on an empty callsign field will call \textless F1 \textgreater: "CQ de PG4I PG4I test"
\item - enter the callsign you hear and hit \textless enter \textgreater
\item - \textless F3 \textgreater will be sent: "PA0R 5nntt1"
\item - exchange entries will be filled in from the defaults dialog
\item - xlog will jump to the end of the exchange field \textless RX(RST) \textgreater
\item - enter the exchange number you hear and hit \textless enter \textgreater
\item - xlog will complete the date, time and frequency entries
\item - the \textless CQTU \textgreater entry will now be sent: "tu PG4I test"
\item - the QSO will be added to the log
\item - the counter will be incremented
\item - all fields will be cleared and xlog will jump to the callsign field
\end{description}

\subsection{Running a contest in S\&P mode}
\begin{description}
\item - cursor on the callsign field
\item - enter the callsign you here and hit \textless enter \textgreater
\item - \textless F6 \textgreater will be sent: "PG4I"
\item - exchange entries will be filled in from the defaults dialog
\item - xlog will jump to the end of the exchange field \textless RX(RST) \textgreater
\item - fill in the exchange and hit \textless enter \textgreater
\item - \textless S\&PTU \textgreater will be sent: "TU 5nntt1"
\item - the QSO will be added to the log
\item - the counter will be incremented
\item - all fields will be cleared and xlog will jump to the callsign field
\end{description}

\pagebreak

\section{Data exchange}
xlog can exchange data with \textbf{twpsk} (version 2.0 and higher) by WA0EIR. When a
callsign is entered, it will show up in twpsk's send widget (where you type
your text) when hitting Shift+Alt+h. Shift+Alt+o will show 'hiscall de mycall'.

\medskip 

\textbf{gmfsk} by OH2BNS (starting at version 0.4) can send logging data to xlog, when
clicking on the 'Log entry' button.

\medskip 

\textbf{Marote} (version 2.3 or later), a rig control program for the elecraft K2
by AB6CV does the same when clicking on the 'Log QSO' button.

\medskip 

\textbf{gpsk31} (starting at version 0.3) can exchange log information
when the QSO details dialog is open.

\medskip 

\textbf{ktrack} by LX2GT (starting at version 0.2.1) can exchange satellite information
with xlog. In order to do so, you need to enable the 2 free fields with the
log-editor. Next, select 'add data to QSO frame' in the last page of the
preferences dialog.

\pagebreak

\section{Importing and exporting logs}
xlog supports ADIF, Cabrillo, EDI (VHF and higher contest format recommended
by IARU region 1), editest, OH1AA, Trlog (tlf) and twlog import. Logs can be
exported to ADIF, Cabrillo and EDI. The apropriate option menu should be
selected for the file type when importing or exporting a log.

Import uses the GtkAssistant widget which helps you when importing. It asks
for the log name and type. You can also decide if you want to import into
the current log or create a new log.

\begin{figure}[h]
 \centering
 \includegraphics{../images/xlog-importdialog.png}
 \caption{Import dialog}
\end{figure}

\medskip 

\textit{Please check your log before importing it and make sure it has the right
  log format. The "Log $\rightarrow$ Import" dialog adds a preview widget which reads the
  first 10 lines of your log, so you can check it.}

\subsection{EDI}

When using EDI export, you should have enabled the locator field in the log.
Xlog will automatically calculate the distance and add it to the log.

\subsection{ADIF}

When using ADIF export you can decide to convert frequency to band. Please use
the "Export" page of the "Settings $\rightarrow$ Dialogs and Windows"
dialog to set this.

\subsection{TSV}

The TSV (Tab Separated Value) export format is used by glabels (see the chapter
on QSL labels), but this can also be used as a way to import log data into
a spreadsheet. You can also use the "Export" page of the
"Settings $\rightarrow$ Dialogs and Windows"
dialog to define the fields to export.

\subsection{Cabrillo}

The Cabrillo log format is the defacto standard format for log submission in
many contests. It's aim is to be ``an interface between logging program
authors and contest sponsors.'' As such, the information in the file is 
generally limited with respect to day-to-day logging of contacts. 

Xlog will import from and export to Cabrillo 2.0 files using the QSO template 
for DARC Worked All Europe. This format is very similar to, and in most cases 
should work for the QSO template for other ARRL and CQ contests, Stew Perry 
contest, Oceania DX Contest and AP Sprint.

\begin{verbatim}
                              --------info sent------- -------info rcvd--------
QSO: freq  mo date       time call          rst exch   call          rst exch  
QSO: ***** ** yyyy-mm-dd nnnn ************* nnn ****** ************* nnn ******
QSO:  3799 PH 2003-03-23 0711 YB1AQS        59  700    DL8WPX        59  001   
0000000001111111111222222222233333333334444444444555555555566666666667777777777
1234567890123456789012345678901234567890123456789012345678901234567890123456789
\end{verbatim}

Xlog will additionally attempt to import QSOs from Cabrillo files claiming to
be for the Sweepstakes, NAQP and NA Sprint contests by matching the CONTEST
tag and adjusting it's input parsing accordingly. When the CONTEST tag
matches RSGB-IOTA or ARRL an attempt is done to add IOTA and WAS scoring to
the AWARDS field in the log.

Xlog does not have contest specific exchange fields, instead the exchange data
should go in the RST field. On export the data after the RS or RST 
is split out for the exchange field of the Cabrillo file. On import the extra
exchange data is joined with the RST into Xlog's TX and RX RST fields. 

See also:
\begin{description}
\item \url{http://www.kkn.net/~trey/cabrillo}
\item logfile/cabrillo.c
\end{description}

\section{Merging logs}
xlog allows merging of 2 logs by selecting Log $\rightarrow$ Merge from the menu. You
will need to select 2 log names. The new log will be called "log1+log2" after
merging.

\begin{figure}[h]
 \centering
 \includegraphics{../images/xlog-mergelogdialog.png}
 \caption{Merge dialog}
\end{figure}


Before you merge logs, you need to make sure they have the same number of
columns by using the log-editor to add or remove columns. After merging, you
can use "Tools $\rightarrow$ Sort by Date" to sort your log.

\section{Fonts and theming}
Xlog fonts are handled by the GTK theme engine. When you use the gnome2 desktop,
start up gnome-font-properties. Otherwise, edit ~/.gtkrc-2.0 and add a line
like:

\begin{quote}
\texttt{gtk-font-name = "Times New Roman 14"}
\end{quote}

Or whatever. GNOME 2 applies its own settings to GTK2 programs with the
gnome-settings-daemon. When the daemon is running, GTK2 programs will use the
GNOME settings instead of those present in .gtkrc-2.0. There is also an
application called gtk-theme-switch2, which you can use to
adjust both appearance and font, whether you use gnome or not.

\section{License}
The xlog source code is release under the GNU General Public License (GPL).
The following chapter includes the full text of this license.

\subsection{GPL}
                    GNU GENERAL PUBLIC LICENSE
                       Version 3, 29 June 2007

 Copyright (C) 2007 Free Software Foundation, Inc. <http://fsf.org/>
 Everyone is permitted to copy and distribute verbatim copies
 of this license document, but changing it is not allowed.

                            Preamble

  The GNU General Public License is a free, copyleft license for
software and other kinds of works.

  The licenses for most software and other practical works are designed
to take away your freedom to share and change the works.  By contrast,
the GNU General Public License is intended to guarantee your freedom to
share and change all versions of a program--to make sure it remains free
software for all its users.  We, the Free Software Foundation, use the
GNU General Public License for most of our software; it applies also to
any other work released this way by its authors.  You can apply it to
your programs, too.

  When we speak of free software, we are referring to freedom, not
price.  Our General Public Licenses are designed to make sure that you
have the freedom to distribute copies of free software (and charge for
them if you wish), that you receive source code or can get it if you
want it, that you can change the software or use pieces of it in new
free programs, and that you know you can do these things.

  To protect your rights, we need to prevent others from denying you
these rights or asking you to surrender the rights.  Therefore, you have
certain responsibilities if you distribute copies of the software, or if
you modify it: responsibilities to respect the freedom of others.

  For example, if you distribute copies of such a program, whether
gratis or for a fee, you must pass on to the recipients the same
freedoms that you received.  You must make sure that they, too, receive
or can get the source code.  And you must show them these terms so they
know their rights.

  Developers that use the GNU GPL protect your rights with two steps:
(1) assert copyright on the software, and (2) offer you this License
giving you legal permission to copy, distribute and/or modify it.

  For the developers' and authors' protection, the GPL clearly explains
that there is no warranty for this free software.  For both users' and
authors' sake, the GPL requires that modified versions be marked as
changed, so that their problems will not be attributed erroneously to
authors of previous versions.

  Some devices are designed to deny users access to install or run
modified versions of the software inside them, although the manufacturer
can do so.  This is fundamentally incompatible with the aim of
protecting users' freedom to change the software.  The systematic
pattern of such abuse occurs in the area of products for individuals to
use, which is precisely where it is most unacceptable.  Therefore, we
have designed this version of the GPL to prohibit the practice for those
products.  If such problems arise substantially in other domains, we
stand ready to extend this provision to those domains in future versions
of the GPL, as needed to protect the freedom of users.

  Finally, every program is threatened constantly by software patents.
States should not allow patents to restrict development and use of
software on general-purpose computers, but in those that do, we wish to
avoid the special danger that patents applied to a free program could
make it effectively proprietary.  To prevent this, the GPL assures that
patents cannot be used to render the program non-free.

  The precise terms and conditions for copying, distribution and
modification follow.

                       TERMS AND CONDITIONS

  0. Definitions.

  "This License" refers to version 3 of the GNU General Public License.

  "Copyright" also means copyright-like laws that apply to other kinds of
works, such as semiconductor masks.

  "The Program" refers to any copyrightable work licensed under this
License.  Each licensee is addressed as "you".  "Licensees" and
"recipients" may be individuals or organizations.

  To "modify" a work means to copy from or adapt all or part of the work
in a fashion requiring copyright permission, other than the making of an
exact copy.  The resulting work is called a "modified version" of the
earlier work or a work "based on" the earlier work.

  A "covered work" means either the unmodified Program or a work based
on the Program.

  To "propagate" a work means to do anything with it that, without
permission, would make you directly or secondarily liable for
infringement under applicable copyright law, except executing it on a
computer or modifying a private copy.  Propagation includes copying,
distribution (with or without modification), making available to the
public, and in some countries other activities as well.

  To "convey" a work means any kind of propagation that enables other
parties to make or receive copies.  Mere interaction with a user through
a computer network, with no transfer of a copy, is not conveying.

  An interactive user interface displays "Appropriate Legal Notices"
to the extent that it includes a convenient and prominently visible
feature that (1) displays an appropriate copyright notice, and (2)
tells the user that there is no warranty for the work (except to the
extent that warranties are provided), that licensees may convey the
work under this License, and how to view a copy of this License.  If
the interface presents a list of user commands or options, such as a
menu, a prominent item in the list meets this criterion.

  1. Source Code.

  The "source code" for a work means the preferred form of the work
for making modifications to it.  "Object code" means any non-source
form of a work.

  A "Standard Interface" means an interface that either is an official
standard defined by a recognized standards body, or, in the case of
interfaces specified for a particular programming language, one that
is widely used among developers working in that language.

  The "System Libraries" of an executable work include anything, other
than the work as a whole, that (a) is included in the normal form of
packaging a Major Component, but which is not part of that Major
Component, and (b) serves only to enable use of the work with that
Major Component, or to implement a Standard Interface for which an
implementation is available to the public in source code form.  A
"Major Component", in this context, means a major essential component
(kernel, window system, and so on) of the specific operating system
(if any) on which the executable work runs, or a compiler used to
produce the work, or an object code interpreter used to run it.

  The "Corresponding Source" for a work in object code form means all
the source code needed to generate, install, and (for an executable
work) run the object code and to modify the work, including scripts to
control those activities.  However, it does not include the work's
System Libraries, or general-purpose tools or generally available free
programs which are used unmodified in performing those activities but
which are not part of the work.  For example, Corresponding Source
includes interface definition files associated with source files for
the work, and the source code for shared libraries and dynamically
linked subprograms that the work is specifically designed to require,
such as by intimate data communication or control flow between those
subprograms and other parts of the work.

  The Corresponding Source need not include anything that users
can regenerate automatically from other parts of the Corresponding
Source.

  The Corresponding Source for a work in source code form is that
same work.

  2. Basic Permissions.

  All rights granted under this License are granted for the term of
copyright on the Program, and are irrevocable provided the stated
conditions are met.  This License explicitly affirms your unlimited
permission to run the unmodified Program.  The output from running a
covered work is covered by this License only if the output, given its
content, constitutes a covered work.  This License acknowledges your
rights of fair use or other equivalent, as provided by copyright law.

  You may make, run and propagate covered works that you do not
convey, without conditions so long as your license otherwise remains
in force.  You may convey covered works to others for the sole purpose
of having them make modifications exclusively for you, or provide you
with facilities for running those works, provided that you comply with
the terms of this License in conveying all material for which you do
not control copyright.  Those thus making or running the covered works
for you must do so exclusively on your behalf, under your direction
and control, on terms that prohibit them from making any copies of
your copyrighted material outside their relationship with you.

  Conveying under any other circumstances is permitted solely under
the conditions stated below.  Sublicensing is not allowed; section 10
makes it unnecessary.

  3. Protecting Users' Legal Rights From Anti-Circumvention Law.

  No covered work shall be deemed part of an effective technological
measure under any applicable law fulfilling obligations under article
11 of the WIPO copyright treaty adopted on 20 December 1996, or
similar laws prohibiting or restricting circumvention of such
measures.

  When you convey a covered work, you waive any legal power to forbid
circumvention of technological measures to the extent such circumvention
is effected by exercising rights under this License with respect to
the covered work, and you disclaim any intention to limit operation or
modification of the work as a means of enforcing, against the work's
users, your or third parties' legal rights to forbid circumvention of
technological measures.

  4. Conveying Verbatim Copies.

  You may convey verbatim copies of the Program's source code as you
receive it, in any medium, provided that you conspicuously and
appropriately publish on each copy an appropriate copyright notice;
keep intact all notices stating that this License and any
non-permissive terms added in accord with section 7 apply to the code;
keep intact all notices of the absence of any warranty; and give all
recipients a copy of this License along with the Program.

  You may charge any price or no price for each copy that you convey,
and you may offer support or warranty protection for a fee.

  5. Conveying Modified Source Versions.

  You may convey a work based on the Program, or the modifications to
produce it from the Program, in the form of source code under the
terms of section 4, provided that you also meet all of these conditions:

    a) The work must carry prominent notices stating that you modified
    it, and giving a relevant date.

    b) The work must carry prominent notices stating that it is
    released under this License and any conditions added under section
    7.  This requirement modifies the requirement in section 4 to
    "keep intact all notices".

    c) You must license the entire work, as a whole, under this
    License to anyone who comes into possession of a copy.  This
    License will therefore apply, along with any applicable section 7
    additional terms, to the whole of the work, and all its parts,
    regardless of how they are packaged.  This License gives no
    permission to license the work in any other way, but it does not
    invalidate such permission if you have separately received it.

    d) If the work has interactive user interfaces, each must display
    Appropriate Legal Notices; however, if the Program has interactive
    interfaces that do not display Appropriate Legal Notices, your
    work need not make them do so.

  A compilation of a covered work with other separate and independent
works, which are not by their nature extensions of the covered work,
and which are not combined with it such as to form a larger program,
in or on a volume of a storage or distribution medium, is called an
"aggregate" if the compilation and its resulting copyright are not
used to limit the access or legal rights of the compilation's users
beyond what the individual works permit.  Inclusion of a covered work
in an aggregate does not cause this License to apply to the other
parts of the aggregate.

  6. Conveying Non-Source Forms.

  You may convey a covered work in object code form under the terms
of sections 4 and 5, provided that you also convey the
machine-readable Corresponding Source under the terms of this License,
in one of these ways:

    a) Convey the object code in, or embodied in, a physical product
    (including a physical distribution medium), accompanied by the
    Corresponding Source fixed on a durable physical medium
    customarily used for software interchange.

    b) Convey the object code in, or embodied in, a physical product
    (including a physical distribution medium), accompanied by a
    written offer, valid for at least three years and valid for as
    long as you offer spare parts or customer support for that product
    model, to give anyone who possesses the object code either (1) a
    copy of the Corresponding Source for all the software in the
    product that is covered by this License, on a durable physical
    medium customarily used for software interchange, for a price no
    more than your reasonable cost of physically performing this
    conveying of source, or (2) access to copy the
    Corresponding Source from a network server at no charge.

    c) Convey individual copies of the object code with a copy of the
    written offer to provide the Corresponding Source.  This
    alternative is allowed only occasionally and noncommercially, and
    only if you received the object code with such an offer, in accord
    with subsection 6b.

    d) Convey the object code by offering access from a designated
    place (gratis or for a charge), and offer equivalent access to the
    Corresponding Source in the same way through the same place at no
    further charge.  You need not require recipients to copy the
    Corresponding Source along with the object code.  If the place to
    copy the object code is a network server, the Corresponding Source
    may be on a different server (operated by you or a third party)
    that supports equivalent copying facilities, provided you maintain
    clear directions next to the object code saying where to find the
    Corresponding Source.  Regardless of what server hosts the
    Corresponding Source, you remain obligated to ensure that it is
    available for as long as needed to satisfy these requirements.

    e) Convey the object code using peer-to-peer transmission, provided
    you inform other peers where the object code and Corresponding
    Source of the work are being offered to the general public at no
    charge under subsection 6d.

  A separable portion of the object code, whose source code is excluded
from the Corresponding Source as a System Library, need not be
included in conveying the object code work.

  A "User Product" is either (1) a "consumer product", which means any
tangible personal property which is normally used for personal, family,
or household purposes, or (2) anything designed or sold for incorporation
into a dwelling.  In determining whether a product is a consumer product,
doubtful cases shall be resolved in favor of coverage.  For a particular
product received by a particular user, "normally used" refers to a
typical or common use of that class of product, regardless of the status
of the particular user or of the way in which the particular user
actually uses, or expects or is expected to use, the product.  A product
is a consumer product regardless of whether the product has substantial
commercial, industrial or non-consumer uses, unless such uses represent
the only significant mode of use of the product.

  "Installation Information" for a User Product means any methods,
procedures, authorization keys, or other information required to install
and execute modified versions of a covered work in that User Product from
a modified version of its Corresponding Source.  The information must
suffice to ensure that the continued functioning of the modified object
code is in no case prevented or interfered with solely because
modification has been made.

  If you convey an object code work under this section in, or with, or
specifically for use in, a User Product, and the conveying occurs as
part of a transaction in which the right of possession and use of the
User Product is transferred to the recipient in perpetuity or for a
fixed term (regardless of how the transaction is characterized), the
Corresponding Source conveyed under this section must be accompanied
by the Installation Information.  But this requirement does not apply
if neither you nor any third party retains the ability to install
modified object code on the User Product (for example, the work has
been installed in ROM).

  The requirement to provide Installation Information does not include a
requirement to continue to provide support service, warranty, or updates
for a work that has been modified or installed by the recipient, or for
the User Product in which it has been modified or installed.  Access to a
network may be denied when the modification itself materially and
adversely affects the operation of the network or violates the rules and
protocols for communication across the network.

  Corresponding Source conveyed, and Installation Information provided,
in accord with this section must be in a format that is publicly
documented (and with an implementation available to the public in
source code form), and must require no special password or key for
unpacking, reading or copying.

  7. Additional Terms.

  "Additional permissions" are terms that supplement the terms of this
License by making exceptions from one or more of its conditions.
Additional permissions that are applicable to the entire Program shall
be treated as though they were included in this License, to the extent
that they are valid under applicable law.  If additional permissions
apply only to part of the Program, that part may be used separately
under those permissions, but the entire Program remains governed by
this License without regard to the additional permissions.

  When you convey a copy of a covered work, you may at your option
remove any additional permissions from that copy, or from any part of
it.  (Additional permissions may be written to require their own
removal in certain cases when you modify the work.)  You may place
additional permissions on material, added by you to a covered work,
for which you have or can give appropriate copyright permission.

  Notwithstanding any other provision of this License, for material you
add to a covered work, you may (if authorized by the copyright holders of
that material) supplement the terms of this License with terms:

    a) Disclaiming warranty or limiting liability differently from the
    terms of sections 15 and 16 of this License; or

    b) Requiring preservation of specified reasonable legal notices or
    author attributions in that material or in the Appropriate Legal
    Notices displayed by works containing it; or

    c) Prohibiting misrepresentation of the origin of that material, or
    requiring that modified versions of such material be marked in
    reasonable ways as different from the original version; or

    d) Limiting the use for publicity purposes of names of licensors or
    authors of the material; or

    e) Declining to grant rights under trademark law for use of some
    trade names, trademarks, or service marks; or

    f) Requiring indemnification of licensors and authors of that
    material by anyone who conveys the material (or modified versions of
    it) with contractual assumptions of liability to the recipient, for
    any liability that these contractual assumptions directly impose on
    those licensors and authors.

  All other non-permissive additional terms are considered "further
restrictions" within the meaning of section 10.  If the Program as you
received it, or any part of it, contains a notice stating that it is
governed by this License along with a term that is a further
restriction, you may remove that term.  If a license document contains
a further restriction but permits relicensing or conveying under this
License, you may add to a covered work material governed by the terms
of that license document, provided that the further restriction does
not survive such relicensing or conveying.

  If you add terms to a covered work in accord with this section, you
must place, in the relevant source files, a statement of the
additional terms that apply to those files, or a notice indicating
where to find the applicable terms.

  Additional terms, permissive or non-permissive, may be stated in the
form of a separately written license, or stated as exceptions;
the above requirements apply either way.

  8. Termination.

  You may not propagate or modify a covered work except as expressly
provided under this License.  Any attempt otherwise to propagate or
modify it is void, and will automatically terminate your rights under
this License (including any patent licenses granted under the third
paragraph of section 11).

  However, if you cease all violation of this License, then your
license from a particular copyright holder is reinstated (a)
provisionally, unless and until the copyright holder explicitly and
finally terminates your license, and (b) permanently, if the copyright
holder fails to notify you of the violation by some reasonable means
prior to 60 days after the cessation.

  Moreover, your license from a particular copyright holder is
reinstated permanently if the copyright holder notifies you of the
violation by some reasonable means, this is the first time you have
received notice of violation of this License (for any work) from that
copyright holder, and you cure the violation prior to 30 days after
your receipt of the notice.

  Termination of your rights under this section does not terminate the
licenses of parties who have received copies or rights from you under
this License.  If your rights have been terminated and not permanently
reinstated, you do not qualify to receive new licenses for the same
material under section 10.

  9. Acceptance Not Required for Having Copies.

  You are not required to accept this License in order to receive or
run a copy of the Program.  Ancillary propagation of a covered work
occurring solely as a consequence of using peer-to-peer transmission
to receive a copy likewise does not require acceptance.  However,
nothing other than this License grants you permission to propagate or
modify any covered work.  These actions infringe copyright if you do
not accept this License.  Therefore, by modifying or propagating a
covered work, you indicate your acceptance of this License to do so.

  10. Automatic Licensing of Downstream Recipients.

  Each time you convey a covered work, the recipient automatically
receives a license from the original licensors, to run, modify and
propagate that work, subject to this License.  You are not responsible
for enforcing compliance by third parties with this License.

  An "entity transaction" is a transaction transferring control of an
organization, or substantially all assets of one, or subdividing an
organization, or merging organizations.  If propagation of a covered
work results from an entity transaction, each party to that
transaction who receives a copy of the work also receives whatever
licenses to the work the party's predecessor in interest had or could
give under the previous paragraph, plus a right to possession of the
Corresponding Source of the work from the predecessor in interest, if
the predecessor has it or can get it with reasonable efforts.

  You may not impose any further restrictions on the exercise of the
rights granted or affirmed under this License.  For example, you may
not impose a license fee, royalty, or other charge for exercise of
rights granted under this License, and you may not initiate litigation
(including a cross-claim or counterclaim in a lawsuit) alleging that
any patent claim is infringed by making, using, selling, offering for
sale, or importing the Program or any portion of it.

  11. Patents.

  A "contributor" is a copyright holder who authorizes use under this
License of the Program or a work on which the Program is based.  The
work thus licensed is called the contributor's "contributor version".

  A contributor's "essential patent claims" are all patent claims
owned or controlled by the contributor, whether already acquired or
hereafter acquired, that would be infringed by some manner, permitted
by this License, of making, using, or selling its contributor version,
but do not include claims that would be infringed only as a
consequence of further modification of the contributor version.  For
purposes of this definition, "control" includes the right to grant
patent sublicenses in a manner consistent with the requirements of
this License.

  Each contributor grants you a non-exclusive, worldwide, royalty-free
patent license under the contributor's essential patent claims, to
make, use, sell, offer for sale, import and otherwise run, modify and
propagate the contents of its contributor version.

  In the following three paragraphs, a "patent license" is any express
agreement or commitment, however denominated, not to enforce a patent
(such as an express permission to practice a patent or covenant not to
sue for patent infringement).  To "grant" such a patent license to a
party means to make such an agreement or commitment not to enforce a
patent against the party.

  If you convey a covered work, knowingly relying on a patent license,
and the Corresponding Source of the work is not available for anyone
to copy, free of charge and under the terms of this License, through a
publicly available network server or other readily accessible means,
then you must either (1) cause the Corresponding Source to be so
available, or (2) arrange to deprive yourself of the benefit of the
patent license for this particular work, or (3) arrange, in a manner
consistent with the requirements of this License, to extend the patent
license to downstream recipients.  "Knowingly relying" means you have
actual knowledge that, but for the patent license, your conveying the
covered work in a country, or your recipient's use of the covered work
in a country, would infringe one or more identifiable patents in that
country that you have reason to believe are valid.

  If, pursuant to or in connection with a single transaction or
arrangement, you convey, or propagate by procuring conveyance of, a
covered work, and grant a patent license to some of the parties
receiving the covered work authorizing them to use, propagate, modify
or convey a specific copy of the covered work, then the patent license
you grant is automatically extended to all recipients of the covered
work and works based on it.

  A patent license is "discriminatory" if it does not include within
the scope of its coverage, prohibits the exercise of, or is
conditioned on the non-exercise of one or more of the rights that are
specifically granted under this License.  You may not convey a covered
work if you are a party to an arrangement with a third party that is
in the business of distributing software, under which you make payment
to the third party based on the extent of your activity of conveying
the work, and under which the third party grants, to any of the
parties who would receive the covered work from you, a discriminatory
patent license (a) in connection with copies of the covered work
conveyed by you (or copies made from those copies), or (b) primarily
for and in connection with specific products or compilations that
contain the covered work, unless you entered into that arrangement,
or that patent license was granted, prior to 28 March 2007.

  Nothing in this License shall be construed as excluding or limiting
any implied license or other defenses to infringement that may
otherwise be available to you under applicable patent law.

  12. No Surrender of Others' Freedom.

  If conditions are imposed on you (whether by court order, agreement or
otherwise) that contradict the conditions of this License, they do not
excuse you from the conditions of this License.  If you cannot convey a
covered work so as to satisfy simultaneously your obligations under this
License and any other pertinent obligations, then as a consequence you may
not convey it at all.  For example, if you agree to terms that obligate you
to collect a royalty for further conveying from those to whom you convey
the Program, the only way you could satisfy both those terms and this
License would be to refrain entirely from conveying the Program.

  13. Use with the GNU Affero General Public License.

  Notwithstanding any other provision of this License, you have
permission to link or combine any covered work with a work licensed
under version 3 of the GNU Affero General Public License into a single
combined work, and to convey the resulting work.  The terms of this
License will continue to apply to the part which is the covered work,
but the special requirements of the GNU Affero General Public License,
section 13, concerning interaction through a network will apply to the
combination as such.

  14. Revised Versions of this License.

  The Free Software Foundation may publish revised and/or new versions of
the GNU General Public License from time to time.  Such new versions will
be similar in spirit to the present version, but may differ in detail to
address new problems or concerns.

  Each version is given a distinguishing version number.  If the
Program specifies that a certain numbered version of the GNU General
Public License "or any later version" applies to it, you have the
option of following the terms and conditions either of that numbered
version or of any later version published by the Free Software
Foundation.  If the Program does not specify a version number of the
GNU General Public License, you may choose any version ever published
by the Free Software Foundation.

  If the Program specifies that a proxy can decide which future
versions of the GNU General Public License can be used, that proxy's
public statement of acceptance of a version permanently authorizes you
to choose that version for the Program.

  Later license versions may give you additional or different
permissions.  However, no additional obligations are imposed on any
author or copyright holder as a result of your choosing to follow a
later version.

  15. Disclaimer of Warranty.

  THERE IS NO WARRANTY FOR THE PROGRAM, TO THE EXTENT PERMITTED BY
APPLICABLE LAW.  EXCEPT WHEN OTHERWISE STATED IN WRITING THE COPYRIGHT
HOLDERS AND/OR OTHER PARTIES PROVIDE THE PROGRAM "AS IS" WITHOUT WARRANTY
OF ANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING, BUT NOT LIMITED TO,
THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR
PURPOSE.  THE ENTIRE RISK AS TO THE QUALITY AND PERFORMANCE OF THE PROGRAM
IS WITH YOU.  SHOULD THE PROGRAM PROVE DEFECTIVE, YOU ASSUME THE COST OF
ALL NECESSARY SERVICING, REPAIR OR CORRECTION.

  16. Limitation of Liability.

  IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING
WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MODIFIES AND/OR CONVEYS
THE PROGRAM AS PERMITTED ABOVE, BE LIABLE TO YOU FOR DAMAGES, INCLUDING ANY
GENERAL, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING OUT OF THE
USE OR INABILITY TO USE THE PROGRAM (INCLUDING BUT NOT LIMITED TO LOSS OF
DATA OR DATA BEING RENDERED INACCURATE OR LOSSES SUSTAINED BY YOU OR THIRD
PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE WITH ANY OTHER PROGRAMS),
EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE POSSIBILITY OF
SUCH DAMAGES.

  17. Interpretation of Sections 15 and 16.

  If the disclaimer of warranty and limitation of liability provided
above cannot be given local legal effect according to their terms,
reviewing courts shall apply local law that most closely approximates
an absolute waiver of all civil liability in connection with the
Program, unless a warranty or assumption of liability accompanies a
copy of the Program in return for a fee.

                     END OF TERMS AND CONDITIONS

\section{Authors}
xlog was written by Joop Stakenborg \textless pg4i at amsat.org \textgreater.
The low level log format was designed by Stephane Fillod
\textless f8cfe at free.fr \textgreater. There were contributions by many people.

\end{document}