-
-
Notifications
You must be signed in to change notification settings - Fork 1.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
The file tree view in FileBrowserWindow is not fully localized #1305
Comments
see the \translations folder i added all the original qt translations, i see that thay only provide zh_TW and not _zh_CN so that might be the issue here |
It seems that the locale names for Simplified Chinese and Traditional Chinese used inside Sandboxie have been changed from And I found the reason why Qt's translations wouldn't apply. My "UiLanguage" is To localize the two dialog boxes mentioned in this issue, the only group of translation files required is the However, after loading the Qt translation file correctly, those two dialogs are more, but still partially, localized. The translations are contributed by the Qt community, so there are missing translations and even incorrect ones. For example,
It's Qt's issue, not Sandboxie's issue, though. P.S. Just found that Qt 6 has more complete translations. There's no plan to upgrade Sandboxie to Qt 6, but maybe we can just use Qt 6's translation files. |
Describe the bug
FileBrowserWindow is the window that shows the specified sandbox's content after you right click a sandbox then select Browse Content.
It contains a tree view that shows all files and subdirectories in the sandbox's directory. However, the column names and each item's "type" is always shown in English, as shown in the screenshot below.
My system language and the language set in Sandboxie are all Chinese Simplified.
From the code I can know that the tree view's content is provided by
QFileSystemModel
, but it's part of Qt library, so its strings won't appear in sandman's .ts files.Sandboxie-Plus v0.9.8b
The text was updated successfully, but these errors were encountered: