extensions not translated on Windows if profile path contains no-ASCII characters

Summary:

If you start Inkscape on Windows and the profile path contains non-ASCII characters like german umlauts (external) extensions will not be translated.

Steps to reproduce:

• use a Windows PC

• install an external Inkscape extension like Ink/Stitch (https://inkstitch.org)

• create directory with non-ASCII chars like "C:\Users\Kai Schröder\AppData\Roaming\inkscape"

• copy the content of your profile dir (normally %APPDATA%\inkscape) to the new created folder

• set environment variable INKSCAPE_PROFILE_DIR to "C:\Users\Kai Schröder\AppData\Roaming\inkscape"

• start Inkscape (maybe you have to change the language to a non-english one)

• repeat the same with a profile path that contains only ASCII characters like C:\inkscape-profile to confirm that the extension is translated

What happened?

• extension is not translated

What should have happened?

• extension should be translated

Version info

Inkscape 1.1.2 (b8e25be833, 2022-02-05)

    GLib version:     2.70.3
    GTK version:      3.24.31
    glibmm version:   2.66.2
    gtkmm version:    3.24.5
    libxml2 version:  2.9.12
    libxslt version:  1.1.34
    Cairo version:    1.17.4
    Pango version:    1.50.3
    HarfBuzz version: 3.3.2
    Poppler version:  22.01.0

    OS version:       Windows 7 SP17Vista SP2Vista SP1VistaXP SP3XP SP2XP SP1XP