Commit Graph

79 Commits

Author SHA1 Message Date
Bill Somerville
905085ab36
Japanese UI translation, thanks to Oba san, JA7UDE 2020-05-31 13:38:38 +01:00
Bill Somerville
b30cb2d040
Updated Catalan and Spanish UI translations, tnx Xavi, EA3W 2020-05-31 13:37:58 +01:00
Bill Somerville
2ba29f4932
Remove unpopulated translation files 2020-05-30 23:06:34 +01:00
Bill Somerville
5d82eac14a
Updated translation files, thanks to Xavi, EA3W 2020-05-30 22:53:13 +01:00
Bill Somerville
68310ec561
Updated translation files, thanks to Xavi, EA3W 2020-05-30 22:46:50 +01:00
Bill Somerville
1da87fe904
Empty wsjtx_en.qm so that macOS doesn't load a secondary l10n 2020-05-30 22:01:47 +01:00
Bill Somerville
241abdb10e
Empty wsjtx_en.qm so that macOS doesn't load a secondary l10n 2020-05-29 22:11:41 +01:00
Bill Somerville
a57dcd4a6f
Merge branch 'master' into develop 2020-05-29 00:53:36 +01:00
Bill Somerville
3a1b42a3fd
Enable UI translations to Japanese 2020-05-26 12:57:38 +01:00
Bill Somerville
9ed7e5b903
Enable UI translations to Japanese 2020-05-26 12:42:13 +01:00
Bill Somerville
9ba4657309
Catalan UI translation updates, thanks to Xavi, EA3W 2020-05-26 12:29:23 +01:00
Bill Somerville
fc76966720
Use language only to identify Spanish translation files
This  allows the  Spanish UI  translation to  work, for  now, for  all
Spanish speaking locales.  If necessary we  can make it es-ES if other
translators feel it is not a good base for their Spanish variant. OTOH
if they just need to l10n a  few strings then, say for Argentina, then
they can do  that in an wsjtx_es_AR.ts and  untranslated strings there
will fall back to the  ones in wsjtx_es.ts automatically. This happens
because of teh way the application loads multiple translation files in
an order suitable for that to happen.
2020-05-26 12:29:23 +01:00
Bill Somerville
546550e97a
Updated UI translation, inc. Spanish, Tnx to Xavi, EA3W 2020-05-26 12:29:23 +01:00
Bill Somerville
80d16bcc91
Catalan UI translation updates, thanks to Xavi, EA3W 2020-05-26 11:12:14 +01:00
Bill Somerville
0856c4298a
Use language only to identify Spanish translation files
This  allows the  Spanish UI  translation to  work, for  now, for  all
Spanish speaking locales.  If necessary we  can make it es-ES if other
translators feel it is not a good base for their Spanish variant. OTOH
if they just need to l10n a  few strings then, say for Argentina, then
they can do  that in an wsjtx_es_AR.ts and  untranslated strings there
will fall back to the  ones in wsjtx_es.ts automatically. This happens
because of teh way the application loads multiple translation files in
an order suitable for that to happen.
2020-05-26 00:01:43 +01:00
Bill Somerville
0b0f29dc64
Updated UI translation, inc. Spanish, Tnx to Xavi, EA3W 2020-05-25 23:52:28 +01:00
Bill Somerville
0ff781e26f
Updated translation files 2020-05-19 12:38:16 +01:00
Bill Somerville
75c4dca87c
Switch to a single common Catalan language translation file
Xavi,  EA3W, assures  me that  all Catalan  dialects and  variants are
essentially  the same,  so there's  no  need to  have country  variant
specific Catalan translation files.
2020-05-19 12:28:50 +01:00
Bill Somerville
4f08363d68
Updated Catalan UI string translations, thanks to Xavi, EA3W 2020-05-19 12:26:51 +01:00
Bill Somerville
6be6fc3269
Initial Catalan UI translation by Xavi, EA3W 2020-05-19 12:26:42 +01:00
Bill Somerville
f90205ce7f
Updated translation files 2020-05-19 12:23:11 +01:00
Bill Somerville
735cdc11f5
Switch to a single common Catalan language translation file
Xavi,  EA3W, assures  me that  all Catalan  dialects and  variants are
essentially  the same,  so there's  no  need to  have country  variant
specific Catalan translation files.
2020-05-19 12:13:43 +01:00
Bill Somerville
b5eb070ce8
Updated Catalan UI string translations, thanks to Xavi, EA3W 2020-05-19 11:25:08 +01:00
Bill Somerville
35fdbf9fee
Initial Catalan UI translation by Xavi, EA3W 2020-05-19 02:20:11 +01:00
Bill Somerville
cfeb2dda3f
Cosmetic punctuation for translation 2020-05-19 01:45:39 +01:00
Bill Somerville
e322de24d3
Cosmetic punctuation for translation 2020-05-19 01:14:18 +01:00
Bill Somerville
4a9b518513
Updated translation files
Spanish and Catalan added in preparation for Xavi, EA3W, to start work
on translations.
2020-05-14 12:54:22 +01:00
Bill Somerville
3c4825a5e7
Fix typos carried through to language files 2019-12-29 12:40:47 +00:00
Bill Somerville
45b12e6028
Preparation for UI i18n
Re-enabling the WSJT-X i18n  facilities. This allows translation files
to  be created  for languages  that are  automatically used  to lookup
translatable strings. To enable a  new language the language name must
be added to the CMakeLists.txt LANGUAGES list variable in BCP47 format
(i.e. en_US,  en_GB, pt_PT, ...). Do  one build with the  CMake option
UPDATE_TRANSLATIONS enabled  (do not  leave it enabled  as there  is a
danger of loosing existing translated texts), that will create a fresh
translations/wsjtx_<lang>.ts file which  should be immediately checked
in with the  CMakeLists.txt change. The .ts should then  be updated by
the translator using  the Qt Linguist tool to  add translations. Check
in the  updated .ts file  to complete the initial  translation process
for that language.

To  aid translators  their WIP  .ts file  may be  tested by  releasing
(using the  lrelease tool or  from the Linguist  menu) a .qm  file and
placing  that  .qm  file  in the  current  directory  before  starting
WSJT-X. The translations will be used if the system locale matches the
file name.   If the system  locale does not  match the file  name; the
language may be  overridden by setting the  LANG environment variable.
For  example if  a wsjtx_pt_PT.qm  file  is in  the current  directory
WSJT-X will use it for  translation lookups, regardless of the current
system locale setting, if the LANG variable is set to pt_PT or pt-PT.

On MS Windows from a command prompt:

 set LANG=pt_PT
 C:\WSJT\wsjtx\bin\wsjtx

elsewhere:

 LANG=pt_PT wsjtx
2019-06-06 12:56:25 +01:00