Bill Somerville 9501cdf271
Sorting out how to test translation files
Windows makes this more complex than necessary.

On  all  systems  the  packaged  translation  file  in  the  resources
:/Translations  directory wsjtx_<lang>.qm  will  be  loaded if  <lang>
matches the  current system locale. Otherwise  the native translatable
strings will be used (en_US is assumed for the native language).

On  all systems  a wsjtx_<lang>.qm  compiled translation  file in  the
current working directory will be loaded if <lang> matches the current
system locale  language and  country (wsjtx_en_GB.qm  for a  locale of
en-GB).

On non-Windows systems  the locale used above can be  set for just the
wsjtx instance being tested by  setting the LANG environment variable,
e.g.

LANG=ca-ES wsjtx

On  Windows  systems  the  current  locale  can  only  be  changed  by
installing  the  relevant  Windows  Language Pack,  selecting  the  UI
language     either      as     the      default     or      as     an
override (Set-WinUILanguageOverride  -Language ca-ES) and  the signing
out and back in.

The two translations file sources above  cam be overridden using a new
command line option:

[-l | -language] <language-code>[-<country-code>]

e.g. -language  ca-ES which will  load the first  readable translation
file as  found in the following  order: :/Translations/wsjtx_ca_ES.qm,
:/Translation/wsjtx_ca.qm,  :/Translations/wsjtx.qm. This  search will
be  preceded  by  the  normal translation  file  load  from  resources
described above. Following  that and the normal load  from the current
working directory described above, the first readable translation file
as    found    in    the   following    order:    $cwd/wsjtx_ca_ES.qm,
$cwd/wsjtx_ca.qm, $cwd/wsjtx.qm.

This allows Windows  testers to change the WSJT-X  UI language without
having to  change the system  UI language and installing  the relevant
language  pack.  Note  that using  this  method will  only change  the
translated  strings,  number  and  date formatting  will  not  change.
Because of this it should only be used for basic testing.
2020-05-19 00:14:10 +01:00
2020-05-07 02:56:57 +01:00
2019-07-02 12:45:05 -05:00
2019-07-01 21:10:43 -05:00
2020-05-07 02:56:57 +01:00
2020-03-17 16:30:05 -04:00
2014-11-28 23:34:23 +00:00
2014-11-28 23:34:23 +00:00
2015-11-18 22:53:37 +00:00
2014-11-28 23:34:23 +00:00
2020-05-10 01:48:46 +01:00
2016-01-02 22:30:12 +00:00
2020-05-07 02:56:57 +01:00
2012-10-21 19:24:54 +00:00
2013-08-10 15:29:55 +00:00
2020-05-09 22:19:52 +01:00
2020-05-09 22:19:52 +01:00
2020-05-14 15:23:06 -04:00
2014-11-28 23:34:23 +00:00
2016-12-19 02:54:43 +00:00
2020-05-13 01:23:17 +01:00
2015-07-27 18:11:06 +00:00

This file contains ambiguous Unicode characters

This file contains Unicode characters that might be confused with other characters. If you think that this is intentional, you can safely ignore this warning. Use the Escape button to reveal them.

 __       __   ______      _____  ________      __    __ 
|  \  _  |  \ /      \    |     \|        \    |  \  |  \
| $$ / \ | $$|  $$$$$$\    \$$$$$ \$$$$$$$$    | $$  | $$
| $$/  $\| $$| $$___\$$      | $$   | $$ ______ \$$\/  $$
| $$  $$$\ $$ \$$    \  __   | $$   | $$|      \ >$$  $$ 
| $$ $$\$$\$$ _\$$$$$$\|  \  | $$   | $$ \$$$$$$/  $$$$\ 
| $$$$  \$$$$|  \__| $$| $$__| $$   | $$       |  $$ \$$\
| $$$    \$$$ \$$    $$ \$$    $$   | $$       | $$  | $$
 \$$      \$$  \$$$$$$   \$$$$$$     \$$        \$$   \$$
                                                         
                                                         
                                                         
Copyright (C) 2001 - 2019 by Joe Taylor, K1JT.

WSJT-X Version 2.1 offers ten different protocols or modes: FT4, FT8,
JT4, JT9, JT65, QRA64, ISCAT, MSK144, WSPR, and Echo. The first six
are designed for making reliable QSOs under weak-signal
conditions. They use nearly identical message structure and source
encoding. JT65 and QRA64 were designed for EME (“moonbounce”) on the
VHF/UHF bands and have also proven very effective for worldwide QRP
communication on the HF bands. QRA64 has a number of advantages over
JT65, including better performance on the very weakest signals. We
imagine that over time it may replace JT65 for EME use. JT9 was
originally designed for the LF, MF, and lower HF bands. Its submode
JT9A is 2 dB more sensitive than JT65 while using less than 10% of the
bandwidth. JT4 offers a wide variety of tone spacings and has proven
highly effective for EME on microwave bands up to 24 GHz. These four
“slow” modes use one-minute timed sequences of alternating
transmission and reception, so a minimal QSO takes four to six minutes
— two or three transmissions by each station, one sending in odd UTC
minutes and the other even. FT8 is operationally similar but four
times faster (15-second T/R sequences) and less sensitive by a few
dB. FT4 is faster still (7.5 s T/R sequences) and especially well
suited for radio contesting. On the HF bands, world-wide QSOs are
possible with any of these modes using power levels of a few watts (or
even milliwatts) and compromise antennas. QSOs are possible at signal
levels 10 to 15 dB below those required for CW.

Note that even though their T/R sequences are short, FT4 and FT8 are
classified as slow modes because their message frames are sent only
once per transmission. All fast modes in WSJT-X send their message
frames repeatedly, as many times as will fit into the Tx sequence
length.

ISCAT, MSK144, and optionally submodes JT9E-H are “fast” protocols
designed to take advantage of brief signal enhancements from ionized
meteor trails, aircraft scatter, and other types of scatter
propagation. These modes use timed sequences of 5, 10, 15, or 30 s
duration. User messages are transmitted repeatedly at high rate (up to
250 characters per second, for MSK144) to make good use of the
shortest meteor-trail reflections or “pings”. ISCAT uses free-form
messages up to 28 characters long, while MSK144 uses the same
structured messages as the slow modes and optionally an abbreviated
format with hashed callsigns.

WSPR (pronounced “whisper”) stands for Weak Signal Propagation
Reporter. The WSPR protocol was designed for probing potential
propagation paths using low-power transmissions. WSPR messages
normally carry the transmitting stations callsign, grid locator, and
transmitter power in dBm, and they can be decoded at signal-to-noise
ratios as low as -31 dB in a 2500 Hz bandwidth. WSPR users with
internet access can automatically upload reception reports to a
central database called WSPRnet that provides a mapping facility,
archival storage, and many other features.

Echo mode allows you to detect and measure your own stations echoes
from the moon, even if they are far below the audible threshold.

WSJT-X provides spectral displays for receiver passbands as wide as 5
kHz, flexible rig control for nearly all modern radios used by
amateurs, and a wide variety of special aids such as automatic Doppler
tracking for EME QSOs and Echo testing. The program runs equally well
on Windows, Macintosh, and Linux systems, and installation packages
are available for all three platforms.

WSJT-X is an open-source project released under the GPLv3 license (See
COPYING). If you have programming or documentation skills or would
like to contribute to the project in other ways, please make your
interests known to the development team.  The projects source-code
repository can be found at https://sourceforge.net/projects/wsjt, and
communication among the developers takes place on the email reflector
https://sourceforge.net/p/wsjt/mailman.  User-level questions and
answers, and general communication among users is found on the
https://groups.yahoo.com/neo/groups/wsjtgroup/info email reflector.


Project web site:

https://www.physics.princeton.edu/pulsar/K1JT/wsjtx.html

Project mailing list (shared with other applications from the same
team):

https://groups.yahoo.com/neo/groups/wsjtgroup
Description
This a mirror of WSJT-X and will be updated every 6 hours. PR will be ignored, head to the SF link. Repo will be updated at 06:00:00 UTC 12:00:00 UTC 18:00:00 UTC 00:00:00 UTC Now fixed.
Readme 216 MiB
Languages
C++ 52.4%
Fortran 19.5%
Python 18.8%
C 7.6%
CMake 1.3%
Other 0.1%