When the file to import has non-latin characters in its path, we're not
handling the provided filename correctly. I tried decoding with
sys.getfilesystemencoding() with no luck, so this needs more looking into. In
the mean time, if we can't open the path name, tell the user to File>Import
the file instead.
- a file path provided on the command line now will now trigger the import
process
- if anki was already running on win/lin, send the import to that process
- if no profile was open, wait until profile opened before importing
- don't do that for password-protected profiles, as it could be used abusively
in a school environment
- drop the old pid-based instance check
Because Qt translations need to be initialized before any widgets are created,
and because the Qt language needs to match the gettext language in order for
translated shortcuts to work, per-profile language settings aren't possible.
So instead of storing the language in the profile, we use
pm.meta['defaultLang'] for all profiles and initialize language handling in
__init__.py
The language selection in the preferences has been removed, because in a
school setting a student fiddling with the language could potentially cause
other students to be unable to navigate the UI. Instead, Anki will accept
-l/--lang passed on the command line to override the original language chosen
at first program startup.