Browse Source

YFKlog 0.5.0 release

master
Fabian Kurz 4 years ago
parent
commit
1aeb260ca5
  1. 27
      README
  2. 5
      doc/index.html
  3. 1
      releases/md5sums.txt
  4. BIN
      releases/yfklog-0.5.0.tar.gz
  5. 4
      releases/yfklog-0.5.0/AUTHORS
  6. 243
      releases/yfklog-0.5.0/CHANGELOG
  7. 280
      releases/yfklog-0.5.0/COPYING
  8. 45
      releases/yfklog-0.5.0/INSTALL
  9. 22
      releases/yfklog-0.5.0/LB3651-1.lab
  10. 4
      releases/yfklog-0.5.0/MANUAL
  11. 61
      releases/yfklog-0.5.0/Makefile
  12. 37
      releases/yfklog-0.5.0/README
  13. 81
      releases/yfklog-0.5.0/RELEASENOTES
  14. 1
      releases/yfklog-0.5.0/clubs/README
  15. 226
      releases/yfklog-0.5.0/config
  16. 3138
      releases/yfklog-0.5.0/cty.dat
  17. 7
      releases/yfklog-0.5.0/db_calls.sql
  18. 5
      releases/yfklog-0.5.0/db_clubs.sql
  19. 5
      releases/yfklog-0.5.0/db_config.sql
  20. 31
      releases/yfklog-0.5.0/db_log.sql
  21. 28
      releases/yfklog-0.5.0/db_log.sqlite
  22. BIN
      releases/yfklog-0.5.0/doc/awards1.png
  23. BIN
      releases/yfklog-0.5.0/doc/bandmap.png
  24. BIN
      releases/yfklog-0.5.0/doc/edit1.png
  25. 941
      releases/yfklog-0.5.0/doc/index.html
  26. BIN
      releases/yfklog-0.5.0/doc/logmode1.png
  27. BIN
      releases/yfklog-0.5.0/doc/logmode2.png
  28. BIN
      releases/yfklog-0.5.0/doc/lotwimport.png
  29. BIN
      releases/yfklog-0.5.0/doc/menu.png
  30. BIN
      releases/yfklog-0.5.0/doc/qslin1.png
  31. BIN
      releases/yfklog-0.5.0/doc/screenlayout0.png
  32. BIN
      releases/yfklog-0.5.0/doc/screenlayout1.png
  33. BIN
      releases/yfklog-0.5.0/doc/xplanet.jpg
  34. 8
      releases/yfklog-0.5.0/onlinelog/README
  35. 41
      releases/yfklog-0.5.0/onlinelog/search.php
  36. 2
      releases/yfklog-0.5.0/onlinelog/test.txt
  37. BIN
      releases/yfklog-0.5.0/p.png
  38. 2427
      releases/yfklog-0.5.0/yfk
  39. 6121
      releases/yfklog-0.5.0/yfksubs.pl
  40. 21
      releases/yfklog-0.5.0/zweckform3421.lab
  41. 24
      releases/yfklog-0.5.0/zweckform3475.lab
  42. 21
      releases/yfklog-0.5.0/zweckform3657.lab

27
README

@ -1,10 +1,11 @@
YFKlog Version 0.5.0 - A general purpose Ham Radio Logbook
------------------------------------------------------------------------------
YFKlog Version 0.5.0 - A general purpose Ham Radio Logbook for Linux/Unix
-------------------------------------------------------------------------
1. Project Description
----------------------
Project Description
-------------------
YFKlog is a general purpose logbook to keep track of amateur
radio contacts. This is Version 0.5.0, released on August 3rd, 2019.
radio contacts. This is Version 0.5.0, released on August 2nd, 2019.
The key characteristics are:
- Console based, bloat-free text interface.
@ -18,9 +19,19 @@ The key characteristics are:
- LoTW import and export
- minimalistic DX cluster bandmap
2. Project Website, Documentation
----------------------------------
Project Website, Documentation
------------------------------
The latest version can be found at: https://fkurz.net/ham/yfklog.html
A manual describing the setup process and most functions of YFKlog is
located at: https://fkurz.net/ham/yfklog/doc/
located at: https://fkurz.net/ham/yfklog/doc/
(The same files are distributed with YFKlog in the "doc" directory.)
Author, Contact
---------------
YFKlog was written by Fabian Kurz, DJ1YFK <fabian@fkurz.net>.
It's free software and can be distributed under the terms
described in the COPYING document.

5
doc/index.html

@ -330,7 +330,10 @@ they are not important.</p>
<p>YFKlog will need a minimum terminal size of 80 x 25 characters to run. If
there's more vertical space, the logging window will use the additional space
to show more lines of the log. If there's additional horizontal space, you can
make use of the
make use of the <a href="#bandmap">DX cluster/band map feature</a>.</p>
<p>There's limited support for resizing the windows during program runtime.
If you resize your terminal, you may want to restart the program to avoid
display errors.</p>
<hr>
<figure>

1
releases/md5sums.txt

@ -13,3 +13,4 @@ a43a1fca16e741d55af004f70f907abf releases/yfklog-0.3.2.tar.gz
b9dcffbd77d262676ed108be0ab2db0d releases/yfklog-0.3.5.tar.gz
75d4c0901d360c2622a559e6c637c0b1 releases/yfklog-0.3.6.tar.gz
4128ea4b46a37692130755dd437104fc releases/yfklog-0.4.0.tar.gz
2c3fe7c0c3bc00918546e7df5ed1c18b releases/yfklog-0.5.0.tar.gz

BIN
releases/yfklog-0.5.0.tar.gz

Binary file not shown.

4
releases/yfklog-0.5.0/AUTHORS

@ -0,0 +1,4 @@
Fabian Kurz, DJ1YFK <fabian@fkurz.net>
Wes Hardaker, WS6Z <wes AT TA ws6z DOTTY com> for misc minor improvements
Cornell Gonschior, DF6FR <df6fr@darc.de> also for minor improvements
David Quental, CT1DRB contributed some fixes

243
releases/yfklog-0.5.0/CHANGELOG

@ -0,0 +1,243 @@
2019-Jul-31: Version 0.5.0
-------------------------------------------------------------------------------
- LoTW download: Show list of confirmed contacts after import.
- Usability: Flush keyboard input buffer frequently during blocking operations
(e.g. scrolling) to avoid unexpected behaviour (such as further scrolling
after PgUp/Dwn was released)
- Include a minimal DX cluster / bandmap tool.
- Support for terminal window sizes beyond 80x25. Additional vertical size
allows to show more QSOs in the log, horizontal size will be used for the
bandmap / DX cluster (if configured)
- Include docs in the release tarball and install it to share/doc/yfklog
- Remove GNUisms from Makefile (tnx KC3NTG)
2019-Jun-30: Version 0.4.0
-------------------------------------------------------------------------------
- Many small improvements contributed over the years, mostly by DF6FR and CT1DRB
- Add support for LoTW upload and download directy from YFKlog (requires tqsl)
- Update dxcc algorithm to handle "new" style country files (with full calls
marked with a =).
2008-Jan-31: Version 0.3.5
-------------------------------------------------------------------------------
- Remote logging from fldigi; uses the same interface as Xlog.
- Custom award statistics. See manual for details.
- Sort order of the log- and the previous-QSO-field now customized by "logsort"
and "prevsort" values.
- Added an option "askme"; when set to nonzero value, you're warned/asked if
you leave the log mode or clear a QSO without saving it.
- An error message is displayed when a QSO cannot be saved, giving the reason
for the failure.
- F6 in the logging mode opens a $browser (as specified in the config file)
for a QRZ.com call lookup.
- Small improvements in the Edit mode.
- A little "hardening" of the ADIF import.
- Updated to the latest version of AD1C's cty.dat country file.
2007-Oct-23: Version 0.3.4
-------------------------------------------------------------------------------
- Removed bug that caused a crash during the Xplanet marker file generation.
- The entry field in the Setup for the SQL server didn't accept dots. Fixed.
- QSL-label PDF file now saved in the proper directory as set in the config
file, not in /tmp/.
2007-Oct-22: Version 0.3.3
-------------------------------------------------------------------------------
- Reading LOTW reports failed for QSOs on 70cm and higher, fixed.
- Major cleanup of key-handling functions. Saved 200 lines and made it faster
and more readable.
- Date, time, band, mode, rst, qsl fields in the main entry form are in
overwrite mode now.
- Cursor-Down now also goes to the following field (additional to Tab, Enter
and Space), Shift-Tab to the previous (additional to Cursor-Up).
2007-Oct-20: Version 0.3.2
-------------------------------------------------------------------------------
- Moved configuration file to ~/.yfklog/config
- Added a complete config menu, from which almost all settings in the config
file ~/.yfklog/config can be edited.
- Database (when using sqlite, recommended) now stored in ~/.yfklog/[DBname]
- Now comes with a Makefile, which installs YFKlog system wide if wanted.
- The (tab)order of the fields in the entry mask can now be freely defined,
see 'fieldorder' in ~/.yfklog/config
- Improved sanity checks for several values (Callsign) during ADIF import.
Callsigns like 'DJ 1 YFK' are now automatically corrected to 'DJ1YFK'.
- No more division by zero for stations with distance of 0 (tnx EA8BVP)
2007-Aug-27: Version 0.3.1
-------------------------------------------------------------------------------
- Bugfix: Logbook table upgrade failed under certain circumstances when using
MySQL. SQLite unaffected.
2007-Aug-07: Version 0.3.0
-------------------------------------------------------------------------------
- SQLite3 support! YFKlog can now run with a SQLite database instead of MySQL.
To use SQLite, set dbserver=sqlite in the config file '.yfklog'.
2007-Aug-06: Version 0.2.5
-------------------------------------------------------------------------------
- Added two database fields, GRID (to store a gridsquare in either 4- or
6-letter format) and OPERATOR (to save who made a QSO). For the latter, a new
variable (operator=DJ1YFK) can optionally be set in the config file.
While logging, enter gridsquares in the remarks field: GRID:JO61UA
Operator information is entered in the same manner: OPERATOR:DJ1YFK and will
be used for all following QSOs.
- Added VUCC/GRID to the award scorings.
- Querying the frequency and mode via hamlib can now be done
automatically for every new QSO, by setting autoqueryrig=1 in the config
file.
- Finally wrote some more detailled documentation. Under permanent
construction: http://fkurz.net/ham/yfklog/doc/
2007-Aug-02: Version 0.2.4
-------------------------------------------------------------------------------
- NEW FEATURE: Export of a marker-file to be used with 'xplanet'. Shows all
current DXCC entities in different colors: Red = not worked, Yellow = Worked
but not confirmed, Green = Confirmed.
Example: http://dl0tud.tu-dresden.de/~dj1yfk/xplanet.png
- Minor improvements and bugfixes
2007-Jul-20: Version 0.2.3
-------------------------------------------------------------------------------
- NEW FEATURE: LOTW Import and Export. See 'MANUAL' for details. LOTW QSLs are
considered for award purposes, with both a summary of paper-only and
LOTW-only confirmations and a combined score.
- NEW FEATURE: At startup, automatically check for the existance of the
neccessary database. If they do not exist, create them. If they are from a
previous version of YFKlog, update them to the latest. This makes the
installation a lot easier and more comfortable.
- IMPROVEMENT: Functions to determine DXCC from a callsign mostly rewritten and
significantly faster (x 20) now.
- IMPROVEMENT: New field added for label printing: QSLR. Says 'TNX' if QSL was
received, 'PSE' when QSL for this QSO is missing.
- IMPROVEMENT: Added 'hamlibparam' to the config file for additional
hamlib/rigctl parameters
- IMPROVEMENT: When working a station, show if the DXCC is worked/confirmed
already on all bands defined by 'awardbands' in the config file.
Output like: "10C 12W 15C 17W 20C 30W 40C 80W"
- IMPROVEMENT: When working a station, it's now also possible to check for this
callsign in any other logbooks, as set by the 'checklogs' variable in the
config file.
- IMPROVEMENT: Possibility to specify a date range for ADIF-export.
- BUG FIX: QSL printing doesn't start at label -1 anymore...
- BUG FIX: Problems with / in $mycall resolved for label printing.
2007-Apr-28: Version 0.2.2
-------------------------------------------------------------------------------
- NEW FEATURE: Hamlib support. See 'MANUAL' for details.
- IMPROVEMENT: Changed REGEX for callsign recognition, now calls like RV0AL/0/P
are not causing problems anymore.
- IMPROVEMENT: Cleaned up SQL syntax. No more problems with MySQL5.
- IMPROVEMENT: ADIF-Import works with files that have DOS-linebreaks now, also
uppercase file extensions (ADI) are now recognized.
- IMPROVEMENT: 47 GHz and up are now given in millimeters (instead of 0.x cm)
on the QSL labels
- IMPROVEMENT: Added a new 'QSO / Mode' statistics function.
- IMPROVEMENT: Another QSL label definition for 70x36 (dm7a.lab) as used for
thousands of contest cards at DM7A...
- BUGFIX: For some awards/statistics, the date range was ignored. Fixed.
- BUGFIX: When creating a new log, and the callsign contained a '/', the
$mycall variable was faulty and caused YFKlog to crash. Fixed.
- BUGFIX: HTML-Output for DXCC, WPX awards etc had a minor bug for 2m only.
2006-Apr-16: Version 0.2.1
-------------------------------------------------------------------------------
- NEW FEATURE: Band data now also allows the higher UHF bands like 70cm etc
(enter as 0.7, 0.23...). This required a change in the database structure.
************************************************************************
*** IMPORTANT: READ AND FOLLOW INSTRUCTIONS FROM FILE 'RELEASENOTES' ***
************************************************************************
- NEW FEATURE: Different screen layouts available for the main screen. See
variable "screenlayout" in .yfklog.
- ADIF-Import: Field 'gridsquare' added to remarks field, if it exists. (tnx
ES6CO)
- BUGFIX: ADIF-Import: Fields containing a ' produced errors. Fixed.
- BUGFIX: Callsigns like DJ1YFK/123 were not properly recognized.
- BUGFIX: Invalid callsigns (like QQ0XX) don't produce ugly warning messages
anymore.
- BUGFIX: When editing a previous QSO, with another QTH/Name than saved in the
database, the QTH/Name was overwritten in the edit-window. Fixed.
- IMPROVEMENT: Changed several REGEXP SQL statements to LIKE, which
increases the speed.
- IMPROVEMENT: ADIF import speed increased by the factor of 3..10.
- IMPROVEMENT: Bands for awards can be specified in the config file .yfklog
using "awardbands=....". (see sample config file)
- IMPROVEMENT: Several cosmetic changes to the award and statistic fuctions.
2005-Dec-28: Version 0.2.0
-------------------------------------------------------------------------------
- BUGFIX: ADIF export: the band fieldlength was one too short. eg. <band:2>20m
- BUGFIX: ADIF import: Fieldlength 0 didn't work.
- BUGFIX: ADIF import: <eoh>/<eor> was errornously case sensitive.
- BUGFIX: ADIF import: integer MHz frequencies didn't work, always required
decimal separator (e.g. "14.000").
- BUGFIX: CALL/A became Prefix A0 and no DXCC.
- BUGFIX: Different calls with the same QSL-Manager were printed on one card!
e.g.: 8Q7ZZ via G3SWH and 5R8GZ via G3SWH ended up on one card with
8Q7ZZ in the "To:" field. Fixed this temporarily, for the cost of
not sorting after the manager's call. Might be changed in future
versions... (tnx info DL3DTH)
- BUGFIX: Name/QTH database update for ADIF import added whole calls
(including /P etc) to the database instead of the basic call
(DJ1YFK, AD5UR..) only. Also it tried to add nonexisting fields
(name/qth) when only one of them was known.
- BUGFIX: cty.dat includes WAE countries (IG9, IT9, 4U1V, GM/s, IG9, IT9,
JW/b, TA1) which are *not* DXCCs. Those are now hardcoded into
yfklog (dxcc sub) to be changed to the proper DXCC. Since they are
not likely to change in the future, I decided to take this easy
approach.
Those DXCCs started with a "*" (*TA1 etc) and are easily filtered
out.
A similar problem occurs with DXCCs that have more than 4 letters,
for example VP8/h. The field for DXCC is only 4 chars long, and
somehow I forgot to remove the "/". This is now also fixed.
Unfortunately in an exisiting database from yfklog-0.1.0, the WAEs
are already counted as new DXCCs, and some DXCCs might be lost
because of the "/". There is a script "yfk-fixdxcc.pl"
distributed with yfklog-0.2.0 which fixes these problems.
- BUGFIX: Direction of the other station was wrong ("mirrored").
- NEW FEATURE: Statistics: DXCC, PFX, CQZ, IOTA, STATE, QSOs/Band
(more statistics can easily be added. Don't hesitate to ask me
for any additions!). See manual for details.
- NEW FEATURE: In the input form, CURSOR UP goes to the previous field. No
more need to cycle through all fields to get to the previous
one.
- NEW FEATURE: After entering a call in "Logging Mode", "New Bandpoint" or
"New DXCC" is displayed if appropriate.
- NEW FEATURE: In the "QSL-Receive" mode, pressing "s" toggles the "QSL-Sent"
flag of the QSO, which is useful when you are only replying
to incoming QSLs.
- NEW FEATURE: Simple editor for Name/QTH-Database.
2005-May-18: Initial release

280
releases/yfklog-0.5.0/COPYING

@ -0,0 +1,280 @@
GNU GENERAL PUBLIC LICENSE
Version 2, June 1991
Copyright (C) 1989, 1991 Free Software Foundation, Inc.
59 Temple Place, Suite 330, Boston, MA 02111-1307 USA
Everyone is permitted to copy and distribute verbatim copies
of this license document, but changing it is not allowed.
Preamble
The licenses for most software are designed to take away your
freedom to share and change it. By contrast, the GNU General Public
License is intended to guarantee your freedom to share and change free
software--to make sure the software is free for all its users. This
General Public License applies to most of the Free Software
Foundation's software and to any other program whose authors commit to
using it. (Some other Free Software Foundation software is covered by
the GNU Library General Public License instead.) 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
this service 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 make restrictions that forbid
anyone to deny you these rights or to ask you to surrender the rights.
These restrictions translate to certain responsibilities for you if you
distribute copies of the software, or if you modify it.
For example, if you distribute copies of such a program, whether
gratis or for a fee, you must give the recipients all the rights that
you have. 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.
We protect your rights with two steps: (1) copyright the software, and
(2) offer you this license which gives you legal permission to copy,
distribute and/or modify the software.
Also, for each author's protection and ours, we want to make certain
that everyone understands that there is no warranty for this free
software. If the software is modified by someone else and passed on, we
want its recipients to know that what they have is not the original, so
that any problems introduced by others will not reflect on the original
authors' reputations.
Finally, any free program is threatened constantly by software
patents. We wish to avoid the danger that redistributors of a free
program will individually obtain patent licenses, in effect making the
program proprietary. To prevent this, we have made it clear that any
patent must be licensed for everyone's free use or not licensed at all.
The precise terms and conditions for copying, distribution and
modification follow.
GNU GENERAL PUBLIC LICENSE
TERMS AND CONDITIONS FOR COPYING, DISTRIBUTION AND MODIFICATION
0. This License applies to any program or other work which contains
a notice placed by the copyright holder saying it may be distributed
under the terms of this General Public License. The "Program", below,
refers to any such program or work, and a "work based on the Program"
means either the Program or any derivative work under copyright law:
that is to say, a work containing the Program or a portion of it,
either verbatim or with modifications and/or translated into another
language. (Hereinafter, translation is included without limitation in
the term "modification".) Each licensee is addressed as "you".
Activities other than copying, distribution and modification are not
covered by this License; they are outside its scope. The act of
running the Program is not restricted, and the output from the Program
is covered only if its contents constitute a work based on the
Program (independent of having been made by running the Program).
Whether that is true depends on what the Program does.
1. You may copy and distribute 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 and disclaimer of warranty; keep intact all the
notices that refer to this License and to the absence of any warranty;
and give any other recipients of the Program a copy of this License
along with the Program.
You may charge a fee for the physical act of transferring a copy, and
you may at your option offer warranty protection in exchange for a fee.
2. You may modify your copy or copies of the Program or any portion
of it, thus forming a work based on the Program, and copy and
distribute such modifications or work under the terms of Section 1
above, provided that you also meet all of these conditions:
a) You must cause the modified files to carry prominent notices
stating that you changed the files and the date of any change.
b) You must cause any work that you distribute or publish, that in
whole or in part contains or is derived from the Program or any
part thereof, to be licensed as a whole at no charge to all third
parties under the terms of this License.
c) If the modified program normally reads commands interactively
when run, you must cause it, when started running for such
interactive use in the most ordinary way, to print or display an
announcement including an appropriate copyright notice and a
notice that there is no warranty (or else, saying that you provide
a warranty) and that users may redistribute the program under
these conditions, and telling the user how to view a copy of this
License. (Exception: if the Program itself is interactive but
does not normally print such an announcement, your work based on
the Program is not required to print an announcement.)
These requirements apply to the modified work as a whole. If
identifiable sections of that work are not derived from the Program,
and can be reasonably considered independent and separate works in
themselves, then this License, and its terms, do not apply to those
sections when you distribute them as separate works. But when you
distribute the same sections as part of a whole which is a work based
on the Program, the distribution of the whole must be on the terms of
this License, whose permissions for other licensees extend to the
entire whole, and thus to each and every part regardless of who wrote it.
Thus, it is not the intent of this section to claim rights or contest
your rights to work written entirely by you; rather, the intent is to
exercise the right to control the distribution of derivative or
collective works based on the Program.
In addition, mere aggregation of another work not based on the Program
with the Program (or with a work based on the Program) on a volume of
a storage or distribution medium does not bring the other work under
the scope of this License.
3. You may copy and distribute the Program (or a work based on it,
under Section 2) in object code or executable form under the terms of
Sections 1 and 2 above provided that you also do one of the following:
a) Accompany it with the complete corresponding machine-readable
source code, which must be distributed under the terms of Sections
1 and 2 above on a medium customarily used for software interchange; or,
b) Accompany it with a written offer, valid for at least three
years, to give any third party, for a charge no more than your
cost of physically performing source distribution, a complete
machine-readable copy of the corresponding source code, to be
distributed under the terms of Sections 1 and 2 above on a medium
customarily used for software interchange; or,
c) Accompany it with the information you received as to the offer
to distribute corresponding source code. (This alternative is
allowed only for noncommercial distribution and only if you
received the program in object code or executable form with such
an offer, in accord with Subsection b above.)
The source code for a work means the preferred form of the work for
making modifications to it. For an executable work, complete source
code means all the source code for all modules it contains, plus any
associated interface definition files, plus the scripts used to
control compilation and installation of the executable. However, as a
special exception, the source code distributed need not include
anything that is normally distributed (in either source or binary
form) with the major components (compiler, kernel, and so on) of the
operating system on which the executable runs, unless that component
itself accompanies the executable.
If distribution of executable or object code is made by offering
access to copy from a designated place, then offering equivalent
access to copy the source code from the same place counts as
distribution of the source code, even though third parties are not
compelled to copy the source along with the object code.
4. You may not copy, modify, sublicense, or distribute the Program
except as expressly provided under this License. Any attempt
otherwise to copy, modify, sublicense or distribute the Program is
void, and will automatically terminate your rights under this License.
However, parties who have received copies, or rights, from you under
this License will not have their licenses terminated so long as such
parties remain in full compliance.
5. You are not required to accept this License, since you have not
signed it. However, nothing else grants you permission to modify or
distribute the Program or its derivative works. These actions are
prohibited by law if you do not accept this License. Therefore, by
modifying or distributing the Program (or any work based on the
Program), you indicate your acceptance of this License to do so, and
all its terms and conditions for copying, distributing or modifying
the Program or works based on it.
6. Each time you redistribute the Program (or any work based on the
Program), the recipient automatically receives a license from the
original licensor to copy, distribute or modify the Program subject to
these terms and conditions. You may not impose any further
restrictions on the recipients' exercise of the rights granted herein.
You are not responsible for enforcing compliance by third parties to
this License.
7. If, as a consequence of a court judgment or allegation of patent
infringement or for any other reason (not limited to patent issues),
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
distribute so as to satisfy simultaneously your obligations under this
License and any other pertinent obligations, then as a consequence you
may not distribute the Program at all. For example, if a patent
license would not permit royalty-free redistribution of the Program by
all those who receive copies directly or indirectly through you, then
the only way you could satisfy both it and this License would be to
refrain entirely from distribution of the Program.
If any portion of this section is held invalid or unenforceable under
any particular circumstance, the balance of the section is intended to
apply and the section as a whole is intended to apply in other
circumstances.
It is not the purpose of this section to induce you to infringe any
patents or other property right claims or to contest validity of any
such claims; this section has the sole purpose of protecting the
integrity of the free software distribution system, which is
implemented by public license practices. Many people have made
generous contributions to the wide range of software distributed
through that system in reliance on consistent application of that
system; it is up to the author/donor to decide if he or she is willing
to distribute software through any other system and a licensee cannot
impose that choice.
This section is intended to make thoroughly clear what is believed to
be a consequence of the rest of this License.
8. If the distribution and/or use of the Program is restricted in
certain countries either by patents or by copyrighted interfaces, the
original copyright holder who places the Program under this License
may add an explicit geographical distribution limitation excluding
those countries, so that distribution is permitted only in or among
countries not thus excluded. In such case, this License incorporates
the limitation as if written in the body of this License.
9. The Free Software Foundation may publish revised and/or new versions
of the 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 a version number of this License which applies to it and "any
later version", you have the option of following the terms and conditions
either of that version or of any later version published by the Free
Software Foundation. If the Program does not specify a version number of
this License, you may choose any version ever published by the Free Software
Foundation.
10. If you wish to incorporate parts of the Program into other free
programs whose distribution conditions are different, write to the author
to ask for permission. For software which is copyrighted by the Free
Software Foundation, write to the Free Software Foundation; we sometimes
make exceptions for this. Our decision will be guided by the two goals
of preserving the free status of all derivatives of our free software and
of promoting the sharing and reuse of software generally.
NO WARRANTY
11. BECAUSE THE PROGRAM IS LICENSED FREE OF CHARGE, 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.
12. IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING
WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MAY MODIFY AND/OR
REDISTRIBUTE 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.
END OF TERMS AND CONDITIONS

45
releases/yfklog-0.5.0/INSTALL

@ -0,0 +1,45 @@
YFKlog 0.4.0 INSTALLATION GUIDE
--------------------------------
More detailled instructions at http://fkurz.net/ham/yfklog/doc/
--------------------------------
YFKlog 0.4.0 comes with a Makefile
$ (sudo) make install [PREFIX=/usr/local]
will install it into PREFIX (default /usr/[bin|share/yfklog/]).
That's all, you can then start 'yfk'. On the first run, you'll be taken to a
configuration menu, where you can set up YFKlog according to your needs.
By default, YFKlog uses a SQLite database, and you don't need to set up
anything manually.
For MySQL-Users only
--------------------
If you want to use MySQL instead of SQLite (I recommend not to use MySQL unless
you *really* know why you want to!) follow these steps:
1 Create a Database (this example uses 'YFKlog' as dbname) and
give the user the needed permissions for it (replace "username" with your
login-name and chose a password for 'passwd').
$ mysqladmin -u root -p create YFKlog
$ mysql -u root -p
mysql> GRANT ALL ON YFKlog.* TO username@localhost IDENTIFIED BY 'passwd';
mysql> quit
2 Start YFKlog.
$ yfk
On the first run, you'll be taken to a configuration menu, where you have
to set the database server, port, db-name, username and password.
Enter these values and you're ready to go.

22
releases/yfklog-0.5.0/LB3651-1.lab

@ -0,0 +1,22 @@
% LB3651-1 52,5 x 29,7mm
% QSOS=3
% WIDTH=52.5
% HEIGHT=29.7
% TOPMARGIN=0
% LEFTMARGIN=0
% ROWS=9
% COLS=4
\put(3.3,25){\makebox(0,0)[lt]{To Radio:}}
\put(48,25){\makebox(0,0)[rt]{\large\bf HISCALL}}
\put(3.3,20){\makebox(0,0)[lt]{Via:}}
\put(48,20){\makebox(0,0)[rt]{\large\bf MANAGER}}
\put(3.3,14){\makebox(0,0)[l]{\footnotesize MYCALL is glad to confirm 2xQSOs:}}
\put(2.4,3){
\footnotesize
\begin{tabular}{@{}p{16mm}@{}p{8.5mm}@{}p{8mm}@{}p{8mm}@{}p{6.5mm}@{}}
\bf Date&\bf Time&\bf Band&\bf 2way&\bf RST\\
\hline
DATE1&TIME1&BAND1&MODE1&RST1\\
DATE2&TIME2&BAND2&MODE2&RST2\\
DATE3&TIME3&BAND3&MODE3&RST3
\end{tabular}}

4
releases/yfklog-0.5.0/MANUAL

@ -0,0 +1,4 @@
Note: This document is now obsolete. A (more or less) current (and much more
detailled and frequently updated version) of the manual can be found at:
http://fkurz.net/ham/yfklog/doc/

61
releases/yfklog-0.5.0/Makefile

@ -0,0 +1,61 @@
VERSION=0.5.0
DESTDIR ?= /usr
all:
@echo "Nothing to do. make install|uninstall|clean|dist [DESTDIR=/usr]"
install:
sed 's^prefix="/usr"^prefix="$(DESTDIR)"^g' yfksubs.pl > yfksubs2.pl
sed 's^prefix="/usr"^prefix="$(DESTDIR)"^g' yfk > yfk2
chmod 0755 yfk
install -d $(DESTDIR)/share/yfklog/
install -d $(DESTDIR)/share/doc/yfklog/doc/
install -d $(DESTDIR)/share/yfklog/labels/
install -d $(DESTDIR)/bin/
install -m 0755 yfk2 $(DESTDIR)/bin/yfk
install -m 0444 yfksubs2.pl $(DESTDIR)/share/yfklog/yfksubs.pl
install -m 0444 db_* $(DESTDIR)/share/yfklog/
install -m 0444 cty.dat $(DESTDIR)/share/yfklog/
install -m 0444 config $(DESTDIR)/share/yfklog/
install -m 0444 p.png $(DESTDIR)/share/yfklog/
install -m 0444 *.lab $(DESTDIR)/share/yfklog/labels/
install -m 0444 doc/* $(DESTDIR)/share/doc/yfklog/doc/
rm -f yfksubs2.pl
rm -f yfk2
uninstall:
rm -f $(DESTDIR)/bin/yfk
rm -rf $(DESTDIR)/share/yfklog/
clean:
rm -f *~
dist:
sed 's/Version [0-9].[0-9].[0-9]/Version $(VERSION)/g' README > README2
rm -f README
mv README2 README
sed 's/Version [0-9].[0-9].[0-9]/Version $(VERSION)/g' MANUAL > MANUAL2
rm -f MANUAL
mv MANUAL2 MANUAL
rm -f releases/yfklog-$(VERSION).tar.gz
rm -rf releases/yfklog-$(VERSION)
mkdir yfklog-$(VERSION)
mkdir yfklog-$(VERSION)/clubs/
mkdir yfklog-$(VERSION)/doc/
mkdir yfklog-$(VERSION)/onlinelog/
cp yfk yfksubs.pl config cty.dat AUTHORS CHANGELOG db_*.sql *.sqlite \
COPYING Makefile\
INSTALL MANUAL README p.png RELEASENOTES *.lab yfklog-$(VERSION)
cp clubs/README yfklog-$(VERSION)/clubs
cp onlinelog/README yfklog-$(VERSION)/onlinelog
cp onlinelog/search.php yfklog-$(VERSION)/onlinelog
cp onlinelog/test.txt yfklog-$(VERSION)/onlinelog
cp doc/*.html yfklog-$(VERSION)/doc
cp doc/*.png yfklog-$(VERSION)/doc
cp doc/*.jpg yfklog-$(VERSION)/doc
tar -zcf yfklog-$(VERSION).tar.gz yfklog-$(VERSION)
mv yfklog-$(VERSION) releases/
mv yfklog-$(VERSION).tar.gz releases/
md5sum releases/*.tar.gz > releases/md5sums.txt
chmod a+r releases/*

37
releases/yfklog-0.5.0/README

@ -0,0 +1,37 @@
YFKlog Version 0.5.0 - A general purpose Ham Radio Logbook for Linux/Unix
-------------------------------------------------------------------------
Project Description
-------------------
YFKlog is a general purpose logbook to keep track of amateur
radio contacts. This is Version 0.5.0, released on August 2nd, 2019.
The key characteristics are:
- Console based, bloat-free text interface.
- Database backend: MySQL or SQLite3 (recommended)
- Unlimited number of logs manageable
- ADIF Import/Export
- High Quality QSL label printing with LaTeX
- Basic award functions plus statistics (DXCC, WAZ, WPX etc).
- Uses "cty.dat" country files
- Hamlib support to query frequency and mode from a transceiver
- LoTW import and export
- minimalistic DX cluster bandmap
Project Website, Documentation
------------------------------
The latest version can be found at: https://fkurz.net/ham/yfklog.html
A manual describing the setup process and most functions of YFKlog is
located at: https://fkurz.net/ham/yfklog/doc/
(The same files are distributed with YFKlog in the "doc" directory.)
Author, Contact
---------------
YFKlog was written by Fabian Kurz, DJ1YFK <fabian@fkurz.net>.
It's free software and can be distributed under the terms
described in the COPYING document.

81
releases/yfklog-0.5.0/RELEASENOTES

@ -0,0 +1,81 @@
RELEASENOTES for YFKlog
=======================
(This file was last updated for version 0.3.2)
To update from an older version, just replace all files of the old
YFKlog-version with the new ones and follow these instructions:
Update from YFKlog 0.1.0
------------------------
If you are updating from YFKlog 0.1.0, following additional changes are needed:
1. Copy yfk-fixdxcc.pl into your yfklog-directory and run it. It fixes some
minor problems of DXCC-handling in 0.1.0.
2. The config-file .yfklog had some changes in the "csadditions" and
"lidadditions"-lines. You might want to copy these lines to your old config
file.
3. Follow steps for update from 0.2.0
Update from YFKlog 0.2.0 (!!! Instructions obsolete, see below !!!)
------------------------
1. Some new lines were added to the config file .yfklog, in particular
"awardbands" and "screenlayout". Also changes in "lidadditions" and
"csadditions". Copy these lines into your old config-file.
2. The database logging-table structure has changed: In order to allow logging
on VHF-UHF, the "band" field was changed from INT to FLOAT. If you create new
logbooks, you don't need to bother with it; existing logbooks can be converted
by the following procedure: (replace YFKlog with your database name, if
different. Repeat the ALTER TABLE statement for every logbook you want to
change, note that the name of the logbook table [for example log_dj1yfk] is
case sensitive, and internally all callsigns are lowercase. So if your call is
DL1ABC, the line has to be "ALTER TABLE log_dl1abc MODIFY BAND FLOAT;".)
.---[ Example ]---------------------------------------------------------------
| $ mysql -p
| Enter password: **********
| Welcome to the MySQL monitor. Commands end with ; or \g.
| Your MySQL connection id is 1324 to server version: 4.1.5-gamma
|
| Type 'help;' or '\h' for help. Type '\c' to clear the buffer.
|
| mysql> use YFKlog;
| Reading table information for completion of table and column names
| You can turn off this feature to get a quicker startup with -A
|
| Database changed
| mysql> ALTER TABLE log_dj1yfk MODIFY BAND FLOAT;
| Query OK, 41861 rows affected (3.36 sec)
| Records: 41861 Duplicates: 0 Warnings: 0
|
| mysql>
`-----------------------------------------------------------------------------
Although nothing critical *should* happen, please make a backup of your
logbooks (ADIF export) before you do this modification.
Update from YFKlog 0.2.1
------------------------
Everything should work after simply replacing the old files. If you are
running into trouble, let me know!
Update from YFKlog 0.2.2 or higher
-----------------------------------
YFKlog as of 0.2.4 automatically tries to update the database structure etc
from any previous version. Any problems with the update should be reported to
the author.
As of 0.3.2, YFKlog doesn't have all its files in one single directory anymore,
rather is searches for the needed files in ~/.yfklog/ and $DESTDIR (by default
/usr[/bin|/share/yfklog/]...). The old .yfklog config file is now
~/.yfklog/config. You can copy your old .yfklog file to ~/.yfklog/config, but
note that several options have been added in the meantime. I'd recommend to
start with a fresh config file. It'll automatically be created on the first
run.
The SQLite database file will also be searched for in ~/.yfklog/, so move/copy
it there if you used SQLite.

1
releases/yfklog-0.5.0/clubs/README

@ -0,0 +1 @@
Under construction.

226
releases/yfklog-0.5.0/config

@ -0,0 +1,226 @@
##############################################################################
# Config file for YFKlog. See https://fkurz.net/ham/yfklog/doc/ or
# /usr/[local/]share/doc/yfklog/doc/index.html for details.
#
# There are two different kinds of settings, MANDATORY settings without which
# the program will NOT WORK and OPTIONAL settings which you might want to
# change, but they have internal defaults if they are not specified.
# Mandatory settings are marked with a "(M)", optional settings with a "(O)"
# in the first description line.
##############################################################################
# (M) mycall: YFKlog can handle several logs parallell, but this one
# is the one YFKlog starts with. As the name suggests, you should use your
# callsign for it. Use lowercase letters.
mycall=dl1test
# (M) dbuser: Database username of your MySQL DB access
dbuser=fabian
# (M) dbname: name of the MySQL Database OR SQLite3 database file.
dbname=YFKlog
# (M) dbpass: ONLY for MySQL.
# Database password. U should make this file only readable to
# yourself (chmod 600 .yfklog) unless you want everyone to be able to read
# your password.
dbpass=notmypassword
# (M) dbserver:
#
# If you use SQLite, set it to 'sqlite'
#
# For MySQL:
# Depending on the configuration of your server,
# only 'localhost' (via a socket) or only '127.0.0.1' (tcp) might work.
dbserver=sqlite
# (M) dbport: database server port (ONLY for MySQL)
dbport=3306
# (O) directory: This is the default directory used for example for ADIF
# import/export, PDF-label output etc. By default it's /tmp.
directory=/tmp
# (O) fieldorder: The order of the fields in the main entry mask.
# Available fields (also default order is:)
# CALL DATE TON TOFF BAND MODE QTH NAME QSLS QSLR RSTS RSTR REM PWR
# You may omit fields you don't need.
# Separate fields with whitespaces.
fieldorder=CALL DATE TON TOFF BAND MODE QTH NAME QSLS QSLR RSTS RSTR REM PWR
# (O) dband: The default band. At the moment YFKlog stores the band in m,
# since I only work from 2190m (136 kHz) - 2m (144 MHz). If there is popular
# demand for it, I could change it to kHz or MHz, so also VHF-EHF can properly
# log their QSOs. Default is my "home band" 80 (m).
dband=80
# (O) dmode: The default mode. You can enter any string here up to 6 letters.
dmode=CW
# (O) dmode: The default power. Only 4 digits for power, some OMs might want to
# regard the number as kW instead of W, some as mW :-)
dpwr=100
# (O) dqsls: Default value for QSL Sent. If not specifield it's "Q" for
# "Queue", meaning that the QSO will be put into the QSL writing-Queue.
dqsls=Q
# (O) dqslr: Default value for QSL received. Usually the QSL has not arrived
# when the QSO happens, so it is N by default
dqslr=N
# (O) dqslsi: Default value for QSL Sent for IMPORTED QSOs, if there is no such
# info in the ADIF. This might be useful because for contest QSOs there is
# usually no such info in the adif, and for those who do not send QSLs for
# every contest QSO this is an easy way to make sure that they don't end up in
# the QSL queue when dqsls=Q. Default: N
dqslsi=N
# (O) lat and lon: Latitude and longitude of the own station in decimal format.
# Needed to calculate the distance and beam heading.
lat=52
lon=-8
# (O) onlinedata: Specifies the columns of the logbook which will be added to
# the online logbook. Possible columns: NR, CALL, DATE, T_ON, T_OFF, BAND, MODE
# QTH, NAME, QSLS, QSLR, RSTS, RSTR, REM, PWR, DXCC, PFX, CONT, QSLINFO.
# Separate fields with commas
onlinedata=`CALL`, DATE, BAND, MODE, RSTS, RSTR, T_ON, QSLS, QSLR, PWR, QSLINFO, STATE
# (O) ftp-information: If you want to use the upload function for a online
# searchable log, some ftp-settings have to be specified. The names are
# self-explaining.
ftpserver=127.0.0.1
ftpport=21
ftpuser=dj1yfk
ftppass=test
ftpdir=/logs
# (O) Liddish callsign addidions which have to be removed, so the DXCC and
# Prefix can be properly determined. If you log stations with their proper
# calls (/QRP is not a part of the call), don't bother anyway.
lidadditions=^QRP$|^LGT$|^\d{2,99}$
# (O) Additions to the callsign which do not change the DXCC or Prefix; default:
# /P, /M, /MM, /AM. Add your own following the same schema if needed.
csadditions=(^P$)|(^M{1,2}$)|(^AM$)|(^A$)
# (O) Bands for award/statistic calculations. Default: all bands from 160 to
# 2m. Format: Bands, separated by whitespaces.
awardbands=160 80 40 30 20 17 15 12 10 6 2
# (O) Modes for award/statistic calculations. Default: CW and SSB
# Format: Modes, separated by whitespaces.
awardmodes=CW SSB
# (O) Screenlayout: YFKlog supports (at the moment) two different layouts of
# the main logging screen. You can toggle between them by setting screenlayout
# to either 0 or 1.
screenlayout=1
# (O) Checklogs: By default, when logging a new callsign, only the previous
# contacts in the current log are checked. It's now possible also to specify
# additional logs that will be checked for QSOs. If a QSO exists, it will be
# shown in the same line where club-membership information is usually shown, in
# a very short form: e.g: In logs: 9A/DJ1YFK/p PA/DJ1YFK/p
#
# Format: checklogs=LOG1 LOG2 LOG3...
#
# Example: checklog=DJ1YFK DM7A DG9YFK PA/DJ1YFK/P
#
# NB: The current active log can be included in the list; it'll be ignored.
checklogs=
# (O) hamlib rig model. 0 for no hamlib.
rigmodel=0
# (O) hamlib path to the device. For example /dev/ttyS0 etc.
rigpath=/dev/ttyS0
# (O) autoqueryrig: If set to 1, YFKlog queries the frequency from the
# transceiver via hamlib at every new QSO automatically.
autoqueryrig=0
# (O) operator: As of version 0.2.5, YFKlog can save an operator information
# for every QSO. This is the default value. When logging, QSOs, the OP can also
# be specified in the remarks-field by OPERATOR:DJ1YFK
operator=
# (O) lotwdetails: If set to 1, include all details (like CQ-Zone, ITU-Zone
# etc) from lotw-reports into the log. If 0, only change the QSLrL flag to Y.
lotwdetails=0
# (O) askme: Ask for confirmation when leaving the logging mode (to the menu)
# without saving the QSO, or deleting a QSO.
askme=1
# (O) logsort: How to sort the QSOs in the log display: Chronological or by the
# QSO-number (how they were entered or imported).
# Possible values: "C" = chronological, "N" = Number (default).
logsort=C
# (O) prevsort: How to sort the display of previous QSOs for a certain call
# D = By date, descending (default)
# A = By date, ascending
prevsort=D
# (O) browser: A browser to do QRZ.com call lookups.
browser=firefox
# (O) colors: Use terminal colors (1, default) or not (0).
colors=1
# (O) Whether we should use the Ham::Callsign::DB class to look up data to
# fill in QSO information with FCC and/or QRZ lookup information
usehamdb=0
# (O) lotwlocation: List of station locations for LoTW, in the format
# CALLSIGN:location. Has to match your definitions in the tqsl program.
#lotwlocation=
# (O) lotwuser: LoTW web user name to download reports
#lotwuser=
# (O) lotwpass: LoTW web password
#lotwpass=
# (O) dxchost: DX cluster hostname (e.g. foc.dj1yfk.de)
# (O) dxcport: DX cluster port (e.g. 7300)
# (O) dxccall: DX cluster login call (e.g. DJ1YFK-9)

3138
releases/yfklog-0.5.0/cty.dat

File diff suppressed because it is too large Load Diff

7
releases/yfklog-0.5.0/db_calls.sql

@ -0,0 +1,7 @@
CREATE TABLE `calls` (
`CALL` varchar(12) NOT NULL default '',
`NAME` varchar(12) default '',
`QTH` varchar(15) default '',
PRIMARY KEY (`CALL`)
);

5
releases/yfklog-0.5.0/db_clubs.sql

@ -0,0 +1,5 @@
CREATE TABLE clubs (
`club` varchar(30) NOT NULL default '',
`nr` varchar(6) NOT NULL default '',
`call` varchar(6) NOT NULL default ''
);

5
releases/yfklog-0.5.0/db_config.sql

@ -0,0 +1,5 @@
CREATE TABLE YFKconfig (
`Name` varchar(50) NOT NULL default '',
`Value` varchar(50) NOT NULL default ''
) TYPE=MyISAM;

31
releases/yfklog-0.5.0/db_log.sql

@ -0,0 +1,31 @@
CREATE TABLE `log_MYCALL` (
`NR` bigint(20) NOT NULL auto_increment,
`CALL` varchar(15) NOT NULL default '',
`DATE` date NOT NULL default '0000-00-00',
`T_ON` time NOT NULL default '00:00:00',
`T_OFF` time NOT NULL default '00:00:00',
`BAND` float unsigned NOT NULL default '0',
`MODE` varchar(6) NOT NULL default '',
`QTH` varchar(15) default '',
`NAME` varchar(15) default '',
`QSLS` char(1) NOT NULL default '',
`QSLR` char(1) NOT NULL default 'N',
`QSLRL` char(1) NOT NULL default 'N',
`RSTS` int(10) unsigned NOT NULL default '599',
`RSTR` int(10) unsigned NOT NULL default '599',
`REM` varchar(60) default '',
`PWR` int(10) unsigned default '0',
`DXCC` varchar(4) NOT NULL default '',
`PFX` varchar(8) NOT NULL default '',
`CONT` char(3) NOT NULL default '',
`ITUZ` int(2) unsigned NOT NULL default '0',
`CQZ` int(2) unsigned NOT NULL default '0',
`QSLINFO` varchar(15) default '',
`IOTA` varchar(6) default '',
`STATE` varchar(2) default '',
`GRID` varchar(6) NOT NULL default '',
`OPERATOR` varchar(6) NOT NULL default '',
PRIMARY KEY (`NR`),
KEY `CALL` (`CALL`),
KEY `DXCC` (`DXCC`)
) AUTO_INCREMENT=1 ;

28
releases/yfklog-0.5.0/db_log.sqlite

@ -0,0 +1,28 @@
CREATE TABLE `log_MYCALL` (
`NR` INTEGER PRIMARY KEY AUTOINCREMENT,
`CALL` varchar(15) NOT NULL default '',
`DATE` date NOT NULL default '0000-00-00',
`T_ON` time NOT NULL default '00:00:00',
`T_OFF` time NOT NULL default '00:00:00',
`BAND` float NOT NULL default '0',
`MODE` varchar(6) NOT NULL default '',
`QTH` varchar(15) default '',
`NAME` varchar(15) default '',
`QSLS` char(1) NOT NULL default '',
`QSLR` char(1) NOT NULL default 'N',
`QSLRL` char(1) NOT NULL default 'N',
`RSTS` int(10) NOT NULL default '599',
`RSTR` int(10) NOT NULL default '599',
`REM` varchar(60) default '',
`PWR` int(10) default '0',
`DXCC` varchar(4) NOT NULL default '',
`PFX` varchar(8) NOT NULL default '',
`CONT` char(3) NOT NULL default '',
`ITUZ` int(2) NOT NULL default '0',
`CQZ` int(2) NOT NULL default '0',
`QSLINFO` varchar(15) default '',
`IOTA` varchar(6) default '',
`STATE` varchar(2) default '',
`GRID` varchar(6) NOT NULL default '',
`OPERATOR` varchar(6) NOT NULL default ''
);

BIN
releases/yfklog-0.5.0/doc/awards1.png

Binary file not shown.

After

Width:  |  Height:  |  Size: 6.0 KiB

BIN
releases/yfklog-0.5.0/doc/bandmap.png

Binary file not shown.

After

Width:  |  Height:  |  Size: 16 KiB

BIN
releases/yfklog-0.5.0/doc/edit1.png

Binary file not shown.

After

Width:  |  Height:  |  Size: 13 KiB

941
releases/yfklog-0.5.0/doc/index.html

@ -0,0 +1,941 @@
<html>
<head>
<title>YFKlog v0.5.0 Manual</title>
</head>
<style>
body,td,a,p{font-family:arial,sans-serif}
figure {
padding: 5px;
float: right;
border: 1px solid #cccccc;
border-radius: 5px;
width: 484px;
}
figure img {
border-radius: 3px 3px 0 0;
}
figure figcaption {
padding: 2px 4px 2px 4px;
background-color: #636363;
color: #eeeeee;
font-style: italic;
border-radius: 0 0 3px 3px;
}
</style>
<body>
<h1>YFKlog v0.5.0 Manual</h1>
<p><code>Copyright (c) 2008-2019 Fabian Kurz, DJ1YFK &lt;<a href="fabianto:&#64;fkurz.net">fabian&#64;fkurz.net</a>&gt;<br>
Permission is granted to copy, distribute and/or modify this document<br>
under the terms of the GNU Free Documentation License, Version 1.2<br>
or any later version published by the Free Software Foundation;<br>
with no Invariant Sections, no Front-Cover Texts, and no Back-Cover<br>
Texts. A copy of the license is included in the section entitled "GNU<br>
Free Documentation License".
</code></p>
<hr noshade>
<p>YFKlog is a general purpose ham radio logbook program designed to run on
Linux and Unix systems. This manual tries to give a detailed description of all features
and functions of YFKlog.</p>
<p>The main website of YFKlog is located at:
<a href="https://fkurz.net/ham/yfklog.html">https://fkurz.net/ham/yfklog.html</a>
</p>
<hr>
<h2>Contents</h2>
<ol>
<li><a href="#install">Installation</a>
<ol>
<li>SQLite</li>
<li>MySQL</li>
</ol>
</li>
<li><a href="#setup">Setup</a>
<ol>
<li>Mandatory settings</li>
<li>Optional settings</li>
</ol>
</li>
<li><a href="#menu">Main Menu</a></li>
<li><a href="#logging">Logging QSOs</a></li>
<li><a href="#search">Searching and editing QSOs</a></li>
<li><a href="#qsl">Handling QSL-cards</a>
<ol>
<li>Incoming cards</li>
<li>Outgoing cards</li>
</ol>
</li>
<li><a href="#adif">ADIF import and export</a></li>
<li><a href="#online">Online log</a></li>
<li><a href="#config">Select Logbook, create new Logbook</a></li>
<li><a href="#awards">Awards/Statistics</a>
<ol>
<li>Standings for awards</li>
<li>Statistics, Xplanet markers</li>
</ol>
</li>
<li><a href="#name">Name/QTH database</a></li>
<li><a href="#lotw">LoTW functions</a>
<ol>
<li>LoTW export (and optional upload)</li>
<li>LoTW import</li>
</ol>
</li>
<li><a href="#hamlib">Transceiver control, hamlib</a></li>
<li><a href="#remote">Remote logging (for fldigi)</a></li>
<li><a href="#bandmap">DX cluster / bandmap</a></li>
<li><a href="#appendix">Appendix</a></li>
<li><a href="#GNUFDL">GNU Free Documentation License</a></li>
</ol>
<hr>
<h2><a id="install" name="install">1. Installation</a></h2>
<p>Install the required packages:</p>
<ul>
<li>Perl</li>
<li>DBI</li>
<li>SQLite</li>
<li>Curses</li>
<li>Make</li>
<li>libwww-perl</li>
</ul>
<p>On Ubuntu or Debian Linux, you can satisfy all requirements simply by
running:</p>
<code>sudo apt-get install perl libdbd-sqlite3-perl libclass-dbi-sqlite-perl make libsqlite3-0 libcurses-perl libwww-perl libnet-telnet-perl</code>
<p>For the LoTW integration, you will also need the packages <code>trustedqsl</code> and <code>xvfb</code>.</p>
<p>Download the <a href="http://fkurz.net/ham/yfklog/">latest version</a> of
YFKlog (or clone the latest version from git) and unpack the tarball to a directory of your choice, then run
<code>make install</code>.</p>
<h3>Install from distribution archive</h3>
<code><pre>
$ wget http://fkurz.net/ham/yfklog/yfklog-0.5.0.tar.gz
$ tar zxfv yfklog-0.5.0.tar.gz
$ cd yfklog-0.5.0
$ sudo make install
</pre></code>
<h3>Install from git</h3>
<code><pre>
$ git clone https://git.fkurz.net/dj1yfk/yfklog.git
$ cd yfklog
$ sudo make install
</pre></code>
<p>By default, YFKlog will be installed to <code>/usr</code>, but you can specify
another directory by adding the option
<code>DESTDIR=/your/favorite/directory</code>. If you have no root privileges on
the machine, a path within your home-directory would be suitable.</p>
<p>Now you are ready to run YFKlog, the executable is simply called
<code>yfk</code> and should be in your <code>PATH</code>.</p>
<p>On your first run, YFKlog will create a directory, <code>~/.yfklog/</code>,
where it stores your configuration and (in case of SQLite) your logbook. A
setup screen appears, where you can edit the most important settings (see <a
href="#setup">Setup</a> below).
You can chose between two databases,
<a href="http://sqlite.org/">SQLite</a> or
<a href="http://www.mysql.com/">MySQL</a>.</p>
<p>SQLite is a lightweight,
self-contained, zero-configuration SQL database engine and probably the right
choice for most users of YFKlog. Using MySQL may be a good idea if you have
the MySQL daemon running on your computer anyway.</p>
<h3>1.1 SQLite</h3>
<p>There is nothing really to set up, this is the default setting.
SQLite will autmatically create a SQLite database file
of the name as set in <code>dbname=...</code>. This single file contains the
whole database. It's trivial to back up and (if needed) accessible via the
<code>sqlite3</code> command line utility.</p>
<h3>1.2 MySQL</h3>
<p>Create a database (in this example it's called <code>YFKlog</code>, the user
is <code>dj1yfk</code> and the password is <code>notmypassword</code>) and
grant the user the neccessary permissions:
<code><pre>
$ mysqladmin -u root -p create YFKlog
$ mysql -u root -p
mysql&gt; GRANT ALL ON YFKlog.* TO dj1yfk@localhost IDENTIFIED BY 'notmypassword';
mysql&gt; FLUSH PRIVILEGES;
mysql&gt; quit
</pre></code>
<p>Now start YFKlog and change at least the
mandatory settings (see below) according to your database setup. If YFKlog can
properly connect the database, it will automatically create its database tables
after the first start. When updating from an older version, all upgrades of
the database structure are performed automatically as of version 0.2.3.</p>
<hr>
<h2><a id="setup" name="setup">2. Setup</a></h2>
<p>Most of the permanent settings of YFKlog are stored in a file, called
<code>~/.yfklog/config</code>. This file will automatically be created on your
first run of YFKlog, and can be changed either from YFKlog itself (accessible
from the main menu) or edited
manually with your favourite text editor.</p>
<p><strong>Have a careful look at the possible settings!</strong>
</p>
<p>If you're editing the file manually, note that the file-format allows an
arbitrary placement of the variables in the file. If a variable is set more
than once, the last occurrence is used. The format <code>name=value</code> must
be used, no spaces/tabs between <code>name=</code> and <code>value</code> are
allowed.</p>
<p>Some settings in this file are <em>mandatory</em>. YFKlog won't run properly
without setting these. Other settings are <em>optional</em>, which doesn't mean
they are not important.</p>
<h3>2.1 Mandatory Settings</h3>
<ul>
<li><strong>mycall</strong> - Should be set to the callsign used. Any
callsign, including portable designators (like PA/DJ1YFK/P) is accepted
here. A logbook-table with this callsign will automatically be created
on first startup, unless it already exists.</li>
<li><strong>dbuser</strong> - The username for the database access for
MySQL. In
most cases this will be the same as your login name, but it could be
anything. For SQLite, set anything here.</li>
<li><strong>dbname</strong> - The name of the database in which YFKlog
stores its logbook tables.</li>
<li><strong>dbpass</strong> - The database password. Only for MySQL.</li>
<li><strong>dbserver</strong> - For SQLite, set to <code>sqlite</code>.
For MySQL: The database server. In most cases this
is the same machine as YFKlog is running on. In that case, either
<em>localhost</em> (for a connection through a socket) or
<em>127.0.0.1</em>
(for a TCP/IP connection) should be used here. Note that (depending on
the server settings), either of these might not work.</li>
<li><strong>dbport</strong> - MySQL only: The database server port. Default
3306</li>
</ul>
<h3>2.2 Optional Settings</h3>
<ul>
<li><strong>dband</strong> - Default band for logging after startup, in
meters.</li>
<li><strong>dmode</strong> - Default mode for logging after startup.
</li>
<li><strong>dpower</strong> - Default output power. </li>
<li><strong>dqsls</strong> - Default value for the 'QSL-sent' field.
This could be Q (Queued), Y (Yes), N (No).</li>
<li><strong>dqslr</strong> - Default value for the 'QSL-received' field.
In most cases it should make sense to default this to N.</li>
<li><strong>dqslsi</strong> - Default value for the 'QSL-sent' field
for QSOs that were imported from an ADIF file that doesn't have any
information about sent QSLs. This is useful for importing contest logs,
for which one may not wish to send cards for every QSO.</li>
<li><strong>operator</strong> - Default value for the operator field.</li>
<li><strong>lat/lon</strong> - Latitude and longitude for distance and
beam heading calculations. North and West are positive.</li>
<li><strong>onlinedata</strong> - Information (log table fields) to be
included in the online-log.</li>
<li><strong>ftp-information</strong> - FTP setup for the online log.
Self explanatory, see config file.</li>
<li><strong>awardbands</strong> - Default bands considered for awards
and statistics functions. Can be changed at runtime if needed.</li>
<li><strong>screenlayout</strong> - YFKlog offers two different screen
layouts for the main logging screen. The <a
href="screenlayout0.png">classic version</a> (0) and a
<a href="screenlayout1.png">version proposed by CT1DRB</a> (1).</li>
<li><strong>checklogs</strong> - Additional logbooks to be searched for
previous QSOs when entering a new callsign in the main logging
mode.</li>
<li><strong>rigmodel</strong> - Rig model for Hamlib.pm cat support.</li>
<li><strong>rigpath</strong> - Path to the device used by Hamlib, e.g.
<code>/dev/ttyS0</code></li>
<li><strong>autoqueryrig</strong> - When 1, the frequency and mode is
automatically queried from the radio.</li>
<li><strong>lotwdetails</strong> - Whether or not to use QSO details
from LoTW to update the log.</li>
<li><strong>directory</strong> - The default directory for every file
to be written or read by YFKlog (like ADIF logs, QSL labels etc). By
default: <code>/tmp</code></li>
<li><strong>fieldorder</strong> - The (tab)order of the entry fields in
the main log form. You cannot only change their order, but also omit
fields you don't need.
All possible fields are listed in <code>~/.yfklog/config</code>.
</li>
<li><strong>askme</strong> - If set to non-zero value, YFKlog asks for
confirmation if you press F3 (clear QSO) or F1 (back to menu) in the
logging mode.
</li>
<li><strong>logsort</strong> - Specified the sort order of the logbook
display. Possible values: <strong>N</strong> for Number; QSOs displayed
in the order they were entered or imported. <strong>C</strong> for
chronologic order. (Default is N).</li>
<li><strong>prevsort</strong> - The sort order of the display of the
previous QSOs with a certain station. By date, either
<strong>A</strong> for ascending or <strong>D</strong> for descending.
Default: Descending.
</li>
<li><strong>browser</strong> - Browser for QRZ.com lookups. (Default: dillo) </li>
<li><strong>lotwlocation</strong> - List of station locations for LoTW
(see section on LoTW below for details!)</li>
<li><strong>lotwuser</strong> - LoTW web user name to download reports</li>
<li><strong>lotwpass</strong> - LoTW web password</li>
<li><strong>dxchost</strong> - DX cluster hostname (e.g. foc.dj1yfk.de)</li>
<li><strong>dxcport</strong> - DX cluster port (e.g. 7300)</li>
<li><strong>dxccall</strong> - DX cluster login call (e.g. DJ1YFK-9)</li>