Your last error reminds me of
viewtopic.php?f=18&t=27054&start=75#p273492 . Unfortunately, legoboy did not give the debug output while he had the error, and he suddenly said it all worked without explaining what he had changed to get rid of the error...
You might have success with:
- Code: Select all
LANG=en_US.UTF-8 ./ffgo-launcher.py
or even:
- Code: Select all
LANG=C ./ffgo-launcher.py
but if you did install correctly, I'd like to find out what is going wrong in your locale. Did you configure your locales properly? ('dpkg-reconfigure locales' to be run as root on Debian, maybe similar on your distro)
From FFGo-1.11.3.tar.gz:
- Code: Select all
/tmp/FFGo-1.11.3 % find FFGo-1.11.3 -name '*.mo'
FFGo-1.11.3/ffgo/data/locale/ja/LC_MESSAGES/FFGo.mo
FFGo-1.11.3/ffgo/data/locale/it/LC_MESSAGES/FFGo.mo
FFGo-1.11.3/ffgo/data/locale/en/LC_MESSAGES/FFGo.mo
FFGo-1.11.3/ffgo/data/locale/pl/LC_MESSAGES/FFGo.mo
FFGo-1.11.3/ffgo/data/locale/es/LC_MESSAGES/FFGo.mo
FFGo-1.11.3/ffgo/data/locale/de/LC_MESSAGES/FFGo.mo
FFGo-1.11.3/ffgo/data/locale/fr/LC_MESSAGES/FFGo.mo
FFGo-1.11.3/ffgo/data/locale/nl/LC_MESSAGES/FFGo.mo
so, clearly the .mo files are there, and other languages should fall back to English.
Edit: I had written .po instead of .mo. .po files are source files for translations, and .mo are binary files generated from the .po files. Those that matter at runtime are the .mo files. They are automatically included in FFGo's tarballs/zip files, but not in the Git repository, which I think explains the problem here if you just cloned the Git repo and hoped to be able to run FFGo directly from that clone. This is not a bug; there are special instructions in
docs/INSTALL/INSTALL_en for people installing from the Git repo, which take care of generating the .mo files, among others).
If initialization gets far enough, FFGo leaves a log file in ~/.ffgo/Logs (automatically rotated), otherwise you can always run ffgo or ffgo-launcher.py with the option --log-level=debug
- Code: Select all
% ffgo --help
usage: ffgo [OPTION ...]
Graphical launcher for the FlightGear flight simulator.
Start a graphical user interface to make it easy to launch fgfs, the
FlightGear executable, with suitable arguments.
optional arguments:
--log-level {debug,info,notice,warning,error,critical}
only messages with the same or a higher priority will
be printed to the terminal (default: notice)
--save-stats-in-pretty-form
When saving the files containing usage statistics, use
a human-readable form at the expense of, maybe, a
little slowdown next time FFGo is started. Useful for
power users who have changed their aircraft paths and
want to keep their aircraft counts in spite of the
change. Don't fear using this option: if you stop
using it, the very small possible slowdown will
disappear completely next time FFGo is started.
-t, --test-mode enable test mode (useful to test pieces of code from
the FFGo GUI)
-T, --test-only after startup, run the App.testStuff() method and exit
--help display this message and exit
--version show program's version number and exit
~ %
Finally, a more appropriate place for this would be
the FFGo forum thread.
Bonne soirée.