-
Notifications
You must be signed in to change notification settings - Fork 895
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
Translations applied partially #2209
Comments
In addition to the issues reported above:
|
I want to ask when this translation bug will be fixed? At least for the problem described in Screenshot 3 this is still the case in February 2020. In case I'm pointed to the right direction I can offer some help to fix this. |
I looked into the script 'angular-gettext-cli_compiled_js_output.js' and saw that the English text that gets not translated contains See here the corrected German translation as an example. The translation is pulled from the translation script as it should: |
This issue has been mentioned on Duplicati. There might be relevant details there: https://forum.duplicati.com/t/solution-for-translation-problem-in-web-gui/9664/1 |
This issue has been mentioned on Duplicati. There might be relevant details there: https://forum.duplicati.com/t/language-aspects-in-commandline-exe/11275/2 |
This concerns the following comment in issue duplicati#2209: duplicati#2209 (comment)
@Sordon, pull request #4384 removes extra backslashes from the localization source. I'm not that familiar with how the translations work, but I think this should resolve the issue you described. |
I'm not either, but Localizations/webroot/localization_webroot.pot looks like a generated file from angular-gettext-cli:
however looking at its history, I'm not sure if it's sent to Transifex or received from them. Sending makes more sense.
but a question to someone who knows HTML is whether newlines even make sense in this context. Will browser wrap? |
Thanks @ts678. I had thought that the source text was extracted automatically, but also saw individual commits to Regardless, it doesn't seem like the |
I'm now convinced that duplicati/Duplicati/Server/webroot/ngax/templates/restore.html Lines 132 to 135 in 9b977b7
duplicati/Localizations/webroot/localization_webroot.pot Lines 259 to 262 in 9b977b7
but explicit
I think the best solution is to remove |
These don't get interpreted as line breaks, and the resulting characters get converted to \\n in the localization_webroot.pot translation source file, which prevents translation of these strings. This concerns the following comment in issue duplicati#2209: duplicati#2209 (comment)
Thanks, that finally someone had a look at this problem. Will the fix be part of the next beta? |
I can confirm that the retention options are translated correctly in the current version. Still untranslated are the management options for the local database. |
@Sordon, I expect this to be part of the next beta. However, the timing of the next beta release is unclear. We should start planning... Thanks @kees-z. I believe pull request #4384 should fix the translations on the local database page so I'll mark it as the fix. If we find additional translation problems, we can create new issues for them. |
I have:
Version info
Duplicati Version: 2.0.1.38 Canary
Operating System: Windows 10
Bug description
A lot of translations to Dutch are not applied to the web interface. Especially the Advanced Options section is still completely English (except a few lines, like "Core options" and "Choose an option"), despite they are all translated to Dutch in the .po file.
Also the text in the section "Manage database" is not translated. See screenshot 3 below.
Steps to reproduce
Actual result: Almost all advanced options (the list as well as the explanations) are still in English.
Expected result: All strings should be displayed in the translated language.
Screenshots
Screenshot 1:
Screenshot 2:
Screenshot 3:
--- Want to back this issue? **[Post a bounty on it!](https://www.bountysource.com/issues/40449701-translations-applied-partially?utm_campaign=plugin&utm_content=tracker%2F4870652&utm_medium=issues&utm_source=github)** We accept bounties via [Bountysource](https://www.bountysource.com/?utm_campaign=plugin&utm_content=tracker%2F4870652&utm_medium=issues&utm_source=github).The text was updated successfully, but these errors were encountered: