fly/flightgear
1
0
Fork 0
Code Activity
14042 commits 1 branch 0 tags 41 MiB
Commit graph

8 commits

Author SHA1 Message Date
Florent Rougon
b2d6acdd4d CMake changes related to FGDATA_SRC_DIR and TRANSLATIONS_SRC_DIR 
- When FGDATA_SRC_DIR isn't explicitly set by the user, set it to
  ${PROJECT_SOURCE_DIR}/../fgdata if this is a directory.

- When TRANSLATIONS_SRC_DIR isn't explicitly set by the user, look for
  translations in ${FGDATA_SRC_DIR}/Translations instead of
  ${PROJECT_SOURCE_DIR}/../fgdata/Translations (i.e., honor the setting
  of FGDATA_SRC_DIR for the sake of translation lookup).

This fixes the problem explained in [1] and [2].

[1] https://sourceforge.net/p/flightgear/mailman/message/36645499/
[2] b2274fbbed/
 2019-04-25 19:11:01 +02:00
James Turner
2b1913e118 Add Russian to list of Qt translations to sync 2018-10-12 11:37:08 +01:00
James Turner
ca8b84dae0 Make translations detection more robust 
Thanks to Scott Giese for the suggestion, check for a full valid
path inside the Translation setup, in case FGData exists but is not
populated.
 2018-09-22 18:24:23 +01:00
Stuart Buchanan
c5840b1039 Fix translations variable where no translations data 2018-09-01 16:22:08 +01:00
James Turner
c537bbcfe7 Translations: detect missing lrelease explicitly. 
This gives a clearer message and behaviour when Qt is installed but
the translation tools have been omitted.
 2018-09-01 14:59:24 +01:00
James Turner
41687767b9 Translations looked up correctly 
Tweak both the launcher and main locale lookups, to tolerate the
different region suffixes encountered in reality.
 2018-08-28 23:34:44 +01:00
James Turner
2329654e3b Disabling translations is tricky. 2018-08-28 17:12:31 +01:00
James Turner
eaa2ed5cbb Launcher translations enabled 
Translations are build into the executable at compile time, providing
FGData is available during the build.
 2018-08-27 13:20:23 +01:00