-
-
Notifications
You must be signed in to change notification settings - Fork 2.1k
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 for the release 3.12 wanted #2124
Comments
I will have a look at updating the German translation in the next days. |
I will make some time for this in the next 24 hours. |
I'll try to complete it at the beginning of next week.
|
Thanks for accepting my pull request. |
Hello,
I'll try to do it this week-end. I've to reinstall the software to do it.
Best regards
Michel
|
I'm planning to complete Turkish translations in the next 3-4 days. Do you have any tool suggestions to easily manage translations? |
Besides Qt Linguist? If that's the case, then no. I think most people translating are just using Linguist. |
Hi Manuel,
I just finish the job :)
Going to bed right now :)
Best regards
Michel
|
Here is the file... I don't know where to push it :( Please remove the .zip extension |
@SafaAlfulaij @hrwatahiki Same question as above... there were two spelling mistakes fixed in our source text a few hours ago. That will mean your translations aren't quite 100% any more. Any interest in fixing those as well? 😄 |
I just heard about the Qt Linguist. Qt Linguist looks fine, thank you. |
I Justin,
The updates are done.
Where I can left the file ? as early this morning ?)
Thanks
Michel
|
Hi Firat,
I use this :
https://www.softpedia.com/get/Others/Home-Education/Qt-Linguist.shtml
Best regards
|
Hi Justin (bis), Here is the file updated, as early this morning, please remove the .zip extension. |
@justinclift Thank you. Now I've download the new files and I'm updating them. |
Puzzle strings, and untranslatable string: |
@hrwatahiki Thanks. 😄 @SafaAlfulaij That's a bit confusing. What should that example be instead? 😄 |
Oops. Accidentally closed this. 😉 |
If I understood @SafaAlfulaij correctly, he pointed out that we need parameterized strings in 'AboutDialog.cpp' (which is referenced by Safa), because in some languages we use a different word order than English to make sentences. For example, in the following code block string concatenation is okay for English but not for Turkish:
English: "Built for X" In short, parameterized strings allow us to make a sentence in a valid order. P.S: I'm able to fix this problem by using another form of the sentence like "Derleme mimarisi: X", so it's not a huge problem for Turkish, at least for now. |
Some Portuguese translations could be made more "natural" if the source strings contained more context for the sentence. |
It seems that |
Oops. Ok, just merged it. 😄 |
Now the only problem of zh translation is the dialog buttons of qt, as I mentioned in #2124 (comment) |
Yeah. I don't know if there's any way we can fix that. 😦 |
Actually, maybe we could just add the zh translations to our own copy of the Qt translation files on our build server... |
can you try this? https://github.com/wisaly/qtbase_zh |
Ok, I've just added the .qm file from that repo to the 64-bit Qt translations folder, and just started our nightly build script. In about 40 minutes, an updated version of our Win64 build should be on the nightlies server. When that new build is ready, are you able to check if it improves things? |
Ahhh. That build pulled from the I was hoping those Qt buttons at the bottom would change though. 😦 |
Hi Justin,
Here is the new french translation file. I hope everything is correct :)
You'll find 2 files : the ts file and ts file zipped.
Best regards
Michel
|
@mvt91 Sorry, but that didn't work. GitHub ignores attachments in email reply messages. 😦 You'll probably need to use the web interface instead. 😄 |
I'll try it
|
Hi Justin, Here is the file (zipped, .ts files are not supported) |
@mercury233 can you try translating some dialog strings in Qt in the new file architecture (where qt.ts is just calling qtbase and others), perhaps that's the problem? If that is you can just migrate the translations from qt_zh to a new qtbase_zh and that's it. Other thing might be locale naming? zh zh_cn zh_tw? |
@mvt91 Awesome. 😄 Just to double check, that's based on the |
Hi Justin, I got the file here : |
Hi Justin, (double message sorry) |
I always have an error with qt linguist 5.13.2 on that sentence : |
@SafaAlfulaij I tried to set up a qt build env but failed. |
@mvt91 Not sure about that error. Looking at the .ts file, I think the error is mistaken. It seems to be thinking the source string has placeholders in it - which it doesn't. As you say, it probably doesn't matter. Hopefully. 😄 For the .zip files, I just applied the first one to the |
Hi Justin,
I tried to find a solution but it seems (stackoverflow) it's a little bug in the Qt linguist version I used.
For me it's Ok.
Best regards
Michel
|
@mvt91 No worries. 😄 |
No No... thanks
|
Closing this as version 3.12 is finally released 😄 |
Good point. 😄 Thanks heaps to everyone for the translations. The approach this time around (initial translations done, then a final "touch up" of the translations for the release candidate) seems to work out well. We should probably do the same thing again next time. 😄 |
Complete translation and some improvements: - Fix warnings raised by Linguist - Avoid Title Case in Spanish Issue #2124 Cherry-picked from v3.12.x branch. # Conflicts: # src/translations/sqlb_es_ES.ts
Complete translation and some improvements: - Fix warnings raised by Linguist - Avoid Title Case in Spanish Issue #2124
We are in the process of releasing our next stable version (3.12.0) of 'DB Browser for SQLite' with many new features and corrections.
Once again we kindly ask our users to help us in making DB4S better by translating it to their languages or updating the translation of the last release (when available).
The *.ts files are already updated on the master branch, and we are not going to modify the strings unless needed to include some correction.
You can read brief indications here about how to do it. I'll be happy to assist you in the process, in case you had any doubt.
I'll ping here all the translators who have helped us in the past, so they get a notification. Please, report back if you want to help again. When there are more than one volunteers, they can share out the work and/or review each other translations. Happy translation!
Source string changes after translation started:
When we're near the final release build, we should check this list of "source string changes ..." in case some languages need those done.
The text was updated successfully, but these errors were encountered: