| Summary: | Question to translation of digiKam 7.7.0 | ||
|---|---|---|---|
| Product: | [Applications] digikam | Reporter: | herb <herb.k> |
| Component: | Usability-i18n | Assignee: | Digikam Developers <digikam-bugs-null> |
| Status: | RESOLVED FIXED | ||
| Severity: | normal | CC: | caulier.gilles, metzpinguin, tysontanx |
| Priority: | NOR | ||
| Version First Reported In: | 7.7.0 | ||
| Target Milestone: | --- | ||
| Platform: | Microsoft Windows | ||
| OS: | Microsoft Windows | ||
| Latest Commit: | Version Fixed/Implemented In: | 8.1.0 | |
| Sentry Crash Report: | |||
| Attachments: |
Screenshot Image-Loaders
Screenshot Batch-Queue Manager |
||
|
Description
herb
2022-05-28 18:54:36 UTC
Created attachment 149297 [details]
Screenshot Batch-Queue Manager
Attached please find another screenshot.
The problem seems to be that the translation is parsed from git/master. But the git/master branch is digiKam-8.0.0. However, the translation no longer fits 100% to the branch of qt5-maintenance that contains the future stable digiKam-7.7.0. Of course we are making some changes to the digiKam-8.0.0 version at the moment, so the translation no longer fits to digiKam-7.7.0. I think you should wait until we release first test versions of digiKam-8.0.0. Because doing 2 translations is unnecessary work. Maik Hello Maik, thanks for your quick reply. Of course will branches 7.7.0 and 8.0.0. differ. You wrote: The problem seems to be that the translation is parsed from git/master. Could you really do a test, that digiKam 8.0.0 with a digikam.mo file, built with all "fuzzy" removed, shows all translated strings - especially at the places I mentioned. I think that there will not be so much changes, that translation will not work. For me it looks like a Windows specific problem. Sorry, but I can do tests only on Windows. On the other hand: what is the goal - from translation point of view - for digiKam 7.7.0? Best regards herb Hi, We will release 7.7.0 as well. No specific translations rules will be done with 7.7.0, as we will switch quickly to 8.0.0 (master). The plan to release 7.7.0 is ASAP, when Windows build will be fixed and ready for production. Best Gilles Caulier One more note, I am using the digiKam-7.7.0 translation for digiKam-8.0.0 and can confirm your missing translations as there were changes in digiKam-8.0.0 to these strings. So it's not a Windows specific problem. Maik @Gilles, libxslt fails to build a current MXE at the moment. Can you confirm it? libtool: Version mismatch error. This is libtool 2.4.6, but the libtool: definition of this LT_INIT comes from libtool 2.4.7. libtool: You should recreate aclocal.m4 with macros from libtool 2.4.6 libtool: and run autoconf again. make[3]: *** [Makefile:595: attrvt.lo] Fehler 63 make[3]: *** [Makefile:595: xslt.lo] Fehler 63 Maik Hi Maik, no libxslt compile fine here using current MXE. Gilles *** Bug 456266 has been marked as a duplicate of this bug. *** Hi herb, There is a nightly build of digiKam-8.0.0, it is compiled with the MSVC compiler and signed. HEIF support is currently missing, otherwise things are going well. It would be nice if you continued to work on the German translation ((:-)) Back up the database if you want to use an older digiKam version again later. https://binary-factory.kde.org/view/Windows%2064-bit/job/Digikam_Nightly_win64/ (file with .exe) Maik Hi, As 8.0.0 is released, all translations must match with the source code. I close this file now. Gilles Caulier |