Skip to content
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

German buttons translation missing (and some others). #9022

Closed
sfadschm opened this issue Sep 14, 2021 · 7 comments
Closed

German buttons translation missing (and some others). #9022

sfadschm opened this issue Sep 14, 2021 · 7 comments
Labels
p2-high Escalation, on top of current planning, release blocker
Milestone

Comments

@sfadschm
Copy link

Expected behaviour

Everything should be translated.

Actual behaviour

The Local folder string and e.g., buttons in the add sync dialog are not translated (see screenshots).
I checked transiflex but everything seems to be translated there (and was working before 2.9).
Tested with both the use default language setting and specifically selecting Deutsch.

Client configuration

Client version: 2.9.0

Operating system: Windows 10 (up-to-date)

OS language: German

Screenshots

Local Folder
Local Folder2

@TheOneRing TheOneRing added this to the 2.9.1 milestone Sep 15, 2021
@michaelstingl michaelstingl added the p2-high Escalation, on top of current planning, release blocker label Sep 15, 2021
@fmoc
Copy link
Contributor

fmoc commented Sep 16, 2021

Such buttons are standard within Qt. You won't be able to find them on Transifex, because the translations should be provided by Qt as well.

What's really strange is that the "Auswählen..." button is translated, because it's also a standard button. ll check the dialog's definition.

@fmoc
Copy link
Contributor

fmoc commented Sep 16, 2021

I've checked how that dialog is set up. We use QWizard as a "frame" widget, the pages are four widgets we define in src/gui/wizard.

I don't see why there should be an inconsistency between the buttons on the bottom and the buttons on the wizard page.

@TheOneRing
Copy link
Contributor

@fmoc do we successfully load the qtbase translations?

@fmoc
Copy link
Contributor

fmoc commented Sep 17, 2021

I can't tell, really. We try a couple of different locations, but there is no logging in place that could tell us if the last call in the chain fails:

const QString qtBaseTrFile = QLatin1String("qtbase_") + lang;
if (!qtTranslator->load(qtTrFile, qtTrPath)) {
if (!qtTranslator->load(qtTrFile, trPath)) {
if (!qtTranslator->load(qtBaseTrFile, qtTrPath)) {
qtTranslator->load(qtBaseTrFile, trPath);
}
}
}

Edit: also, both strings "Auswählen" and "Next" should be part of qtbase. Why in the world should one half work while the other wouldn't?

@fmoc
Copy link
Contributor

fmoc commented Sep 17, 2021

Can be reproduced in a Windows 10 VM.

@TheOneRing
Copy link
Contributor

#9062

@gabi18 gabi18 mentioned this issue Sep 29, 2021
46 tasks
@gabi18
Copy link
Contributor

gabi18 commented Sep 30, 2021

Confirmed on Windows 10 20H2, client 2.9.1rc1 (build 5270) that the buttons are translated:

local_folder

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
p2-high Escalation, on top of current planning, release blocker
Projects
None yet
Development

No branches or pull requests

5 participants