Log message:
Update 2.0.3 to 2.1RC3  (it is said beta-3 at following text, but we call it as RC)
(Following text is note from 2.1 beta-1 to 2.1-beta-3)
------------------------------
I'm happy to announce availability of a test release of TQSL, which is the third \ 
beta test
release for TQSL 2.1.

The two major goals for TQSL 2.1 are to make TQSL accessible and to make it \ 
localizable.

Changes since beta-2:

1. Several cases where errors could either be ignored or lost have been \ 
corrected. For
example, trying to create a callsign certificate request when the user does not have
permission to save the request file would result in "NO ERROR" being \ 
reported. Trying to
import a .TQ6 file when the user did not have permission to store the callsign \ 
certificate
would cause TQSL to crash.

2. The certificate upload messages from LoTW are now cleaned up prior to \ 
display. When an
error occurs during certificate processing for an uploaded certificate request, \ 
TQSL now
displays that error more prominently and deletes the pending callsign \ 
certificate request.

3. Recovery from errors in the Duplicates database have been made more robust. \ 
The common
case where TQSL would report "Invalid Argument" (trying to use a \ 
database from a newer
version of TQSL on an old version of TQSL) is now handled.

(These are also available from the Sourceforge repository.)

As always, feedback on any suggestions for improvements or reports of any issues is
appreciated. Send directly to me, or on the list

[The TQSL 2.1 beta-2 release notes follow.]

For accessibility, several changes in the TQSL user interface were made to help \ 
the user
interface to interact better with screen readers and other accessibility \ 
interfaces. While
many of these changes aren't apparent to the typical user, there are some minor \ 
changes in
work flow that you may notice. However, it is much more usable with assistive \ 
technologies.

For localization, much of the TQSL GUI and messages can now be translated into local
languages. For this beta, there are machine translations included that came from \ 
Google
Translate. They're probably of very poor quality, but serve as a proof of \ 
concept. Just use
the "Language" selection on the "File" pulldown menu. Note \ 
that you may need extra fonts
installed to use some languages.

Other major changes:

1. If a user has only one station location, then there's no prompt to ask them \ 
to select what
location to use when signing a log.

2. Station locations can be set up with callsign "[None]". When a user \ 
uses that station
location to sign a log, they're prompted for the appropriate callsign. This \ 
allows people who
have had multiple callsigns for a given QTH to enter the data for the location \ 
once and
re-use it for a specific callsign.

3. TQSL now recognizes the ADIF <SUBMODE> tag and attempts to map that to \ 
modes recognized by
LoTW. Fully supporting <SUBMODE> will require changes in the LoTW \ 
configuration file.

4. TQSL now detects when another instance is busy signing a log (waiting on a \ 
user to respond
to a prompt, for example) and a command line logger is requesting TQSL to sign a \ 
different
log. The command line invocation of TQSL no longer "hangs" the command \ 
line signing operation
and instead returns an error.

5. TQSL now properly handles non-ASCII characters in folder names. Previous \ 
versions of TQSL
relied upon the DOS compatibility "short" file names, which are not \ 
enabled by default on
Windows 8.

There's also startup performance improvements, particularly for stations with \ 
large numbers
of callsign certificates. Other minor updates include allowing callsign \ 
certificates to be
requested with dates one year in the future (for special event stations, for \ 
example), and
verifying that the end date for valid QSOs for a callsign certificate is after \ 
the start
date.

Log message:
Add information of FreeBSD way of patches

Log message:
COMMIT_MSG Removed. TODO updated to include clang issue.

Log message:
Bump version 2.0.2 to 2.0.3
(tqslilb: 2.4)
Fix defect that doesn't allow adding station locations if only a single
callsign certificate is installed.
 
(following diff is manually editted, tabs are deleted)
 diff -urp tqsl-2.0.2/src/location.cpp tqsl-2.0.3/src/location.cpp
--- tqsl-2.0.2/src/location.cpp	2014-07-13 05:18:13.000000000 +0900
+++ tqsl-2.0.3/src/location.cpp	2014-07-17 10:22:16.000000000 +0900
@@ -1152,6 +1152,9 @@ update_page(int page, TQSL_LOCATION *loc
 			field.idx = static_cast<int>(field.items.size());
 		field.items.push_back(item);
 	}
+	if (field.idx == -1 && field.items.size() == 1) {
+		field.idx = 0;
+	}
 	if (field.idx >= 0) {
 		field.cdata = field.items[field.idx].text;
 	}

Log message:
Candidate of commit log pkgsrc proper. But too long for now (238lines).

Log message:
(Authors note):
As I've had no comments on the 2.0.2-rc5 beta, I've decided that it's time to \ 
release it.

The kits on sourceforge have been updated to the final v2.0.2 release.

https://sourceforge.net/projects/trustedqsl/files/TrustedQSL/v2.0.2/

The README there is the preliminary release notes.
Thanks to everyone for the help with testing and reporting issues.

(pkgsrc)
README (as is) doesn't look for regular release notes, but usage of
the software. (So it is not included yet as a binary or commit log.)

Log message:
tqsl-2.0.2RC4 to 2.0.2RC5 change:
----------
This release fixes a pair of related defects that have been there
since TQSL 1.x

When you create a station location, you associate it with a callsign
certificate. When you sign a log, you select a location for signing,
which then uses the callsign to select the right callsign certificate.

The problems happen when you do unexpected things with those
certificates.

If you create a station location for K1MU, then delete all of the
certificates for K1MU, then signing a log would cause an "Invalid
Argument" error. TQSL has been corrected to now display an error that
there are no valid callsign certificates.

Similarly, if you create a station location and then let the
associated callsign certificate to expire, trying to sign using that
location would also give an unhelpful "Invalid Argument" message.

When there were no matching certificates, displaying the properties of
a station location would display an incorrect callsign.

These defects have been corrected in RC5 so that useful error messages
are displayed for these cases.

Log message:
Committed to pkgsrc proper. Make it empty now.