You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As the title says, penumbra completely fails to import mods that have non-ASCII characters in the name, such as chinese symbols, umlauts or the like. A workaround currently is to edit the .mpl file in the .ttmp2 archive before importing and removing any symbols that would result in a filepath with non-ASCII characters.
This works until you want to install something with Heliosphere; due to the automated nature of this plugin it's not possible to edit the .mpl beforehand, resulting in many mods simply being uninstallable.
Think a solution that doesn't cause problems down the line is to add a toggle into Penumbra settings called "Sanitize filenames to ASCII only" or similar. Easy way to handle the symbols would be simply to replace them with a ~ or - or some other simple symbol, or simply delete them from the filename.
Run your game with LC_ALL=C.UTF-8 (or another .UTF-8 locale, if you have any installed – note that the only one a Steam Deck has by default is C.UTF-8) or LC_CTYPE=C.UTF-8
Originally reported to the Penumbra repo, but was directed here.
pasting original report from xivdev/Penumbra#350:
Playing on linux.
As the title says, penumbra completely fails to import mods that have non-ASCII characters in the name, such as chinese symbols, umlauts or the like. A workaround currently is to edit the .mpl file in the .ttmp2 archive before importing and removing any symbols that would result in a filepath with non-ASCII characters.
This works until you want to install something with Heliosphere; due to the automated nature of this plugin it's not possible to edit the .mpl beforehand, resulting in many mods simply being uninstallable.
Think a solution that doesn't cause problems down the line is to add a toggle into Penumbra settings called "Sanitize filenames to ASCII only" or similar. Easy way to handle the symbols would be simply to replace them with a ~ or - or some other simple symbol, or simply delete them from the filename.
Could this also be related to #15 ?
The text was updated successfully, but these errors were encountered: