digiKam translations in l10n-kf5
Locked
digiKam translations in l10n-kf5
 
|
Hi Luigi (and everyone),
digiKam Software Compilation is getting close to releasing its 5.0.0-beta1 version. We are now ready to start translations in the trunk/l10n-kf5 branch. I suggest the following scheme for initial import of existing translations from l10n-kde4 to reuse them as much as possible: 1. These files are to be copied from trunk/l10n-kde4/messages/$LANG/ to trunk/l10n-kf5/.../ kdegraphics/libkipi.po kdegraphics/desktop_kdegraphics_libkipi.po kdegraphics/libkexiv2.po kdegraphics/libkdcraw.po kdegraphics/libksane.po kdegraphics/libkface.po extragear-libs/libkvkontakte.po extragear-graphics/showfoto.appdata.po extragear-graphics/desktop_extragear-graphics_digikam.po extragear-graphics/digikam.po extragear-graphics/desktop_extragear-graphics_kipi-plugins.po extragear-graphics/kipiplugins.po extragear-graphics/kipiplugin_advancedslideshow.po extragear-graphics/kipiplugin_calendar.po extragear-graphics/kipiplugin_dropbox.po extragear-graphics/kipiplugin_expoblending.po extragear-graphics/kipiplugin_facebook.po extragear-graphics/kipiplugin_flashexport.po extragear-graphics/kipiplugin_googledrive.po extragear-graphics/kipiplugin_imageviewer.po extragear-graphics/kipiplugin_kmlexport.po extragear-graphics/kipiplugin_panorama.po extragear-graphics/kipiplugin_printimages.po extragear-graphics/kipiplugin_sendimages.po extragear-graphics/kipiplugin_smug.po extragear-graphics/kipiplugin_vkontakte.po extragear-graphics/kipiplugin_yandexfotki.po 2. Each of these files should be copied in the same way, but under a different name: extragear-graphics/kipiplugin_flickrexport.po -> extragear-graphics/kipiplugin_flickr.po extragear-graphics/kipiplugin_imageshackexport.po -> extragear-graphics/kipiplugin_imageshack.po extragear-graphics/kipiplugin_imgurexport.po -> extragear-graphics/kipiplugin_imgur.po extragear-graphics/kipiplugin_piwigoexport.po -> extragear-graphics/kipiplugin_piwigo.po extragear-graphics/kipiplugin_rajceexport.po -> extragear-graphics/kipiplugin_rajce.po extragear-graphics/kipiplugin_kioexportimport.po -> extragear-graphics/kipiplugin_remotestorage.po extragear-graphics/kipiplugin_wikimedia.pot -> extragear-graphics/kipiplugin_mediawiki.po 3. These files from l10n-kde4/messages should be merged into l10n-kf5/.../extragear-graphics/digikam.po: kdegraphics/libkgeomap.po extragear-graphics/kipiplugin_acquireimages.po extragear-graphics/kipiplugin_dngconverter.po extragear-graphics/kipiplugin_metadataedit.po extragear-graphics/kipiplugin_gpssync.po kdegraphics/libkexiv2.po (this file should also be kept standalone as mentioned above) As you may notice some KIPI plugins have been dropped, some other merged into digiKam core. kipiplugin_timeadjust.po will _soon_ be merged into digiKam core too, please wait for the update from us. Documentation is not updated yet, may docbook are obsolete. But it's in separate repos (digikam-doc.git and kipi-plugins-doc.git), so we can start doc. translations later. -- Alexander Potashev _______________________________________________ Digikam-devel mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-devel |
Re: digiKam translations in l10n-kf5
|
|
Hi,
many thanks for the detailed list, really helpful. I have one question: On Tuesday 22 of September 2015 18:57:58 Alexander Potashev wrote: > 3. These files from l10n-kde4/messages should be merged into > l10n-kf5/.../extragear-graphics/digikam.po: > > kdegraphics/libkgeomap.po > extragear-graphics/kipiplugin_acquireimages.po > extragear-graphics/kipiplugin_dngconverter.po > extragear-graphics/kipiplugin_metadataedit.po > extragear-graphics/kipiplugin_gpssync.po > kdegraphics/libkexiv2.po (this file should also be kept > standalone as mentioned above) libkgeomap is released as a separate library; why are the same messages needed inside digikam? Also, libkexiv2, why should it be keep separate for now? Is it temporary? Or will the copy inside digikam be removed? (I hope the latter). Ciao -- Luigi _______________________________________________ Digikam-devel mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-devel |
Re: digiKam translations in l10n-kf5
|
|
2015-09-22 19:06 GMT+03:00 Luigi Toscano <[hidden email]>:
> Hi, > many thanks for the detailed list, really helpful. I have one question: > > On Tuesday 22 of September 2015 18:57:58 Alexander Potashev wrote: >> 3. These files from l10n-kde4/messages should be merged into >> l10n-kf5/.../extragear-graphics/digikam.po: >> >> kdegraphics/libkgeomap.po >> extragear-graphics/kipiplugin_acquireimages.po >> extragear-graphics/kipiplugin_dngconverter.po >> extragear-graphics/kipiplugin_metadataedit.po >> extragear-graphics/kipiplugin_gpssync.po >> kdegraphics/libkexiv2.po (this file should also be kept >> standalone as mentioned above) > > libkgeomap is released as a separate library; why are the same messages needed > inside digikam? > > Also, libkexiv2, why should it be keep separate for now? Is it temporary? Or > will the copy inside digikam be removed? (I hope the latter). Luigi, We decided not to release libkgeomap, but instead incorporate its source code into digiKam core (digikam.git). That is why there will be no libkgeomap.po in l10n-kf5. As for libkexiv2, its UI part (widget classes) has been moved into digikam.git too, thus the merge of libkexiv2.po into digikam.po. I've just checked the source code and it turns out that libkexiv2 has no more translatable strings left, so libkexiv2.po should _not_ exist in l10n-kf5. Sorry for my mistake. -- Alexander Potashev _______________________________________________ Digikam-devel mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-devel |
Re: digiKam translations in l10n-kf5
|
|
2015-09-22 19:29 GMT+03:00 Alexander Potashev <[hidden email]>:
> We decided not to release libkgeomap, but instead incorporate its > source code into digiKam core (digikam.git). That is why there will be > no libkgeomap.po in l10n-kf5. Because of the unclear situation with libkgeomap code in digikam we decided to copy the above listed translations tomorrow, we the i18n strings in digikam.po are more or less stable. -- Alexander Potashev _______________________________________________ Digikam-devel mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-devel |
Re: digiKam translations in l10n-kf5
|
|
In reply to this post by Alexander Potashev
El Dimarts, 22 de setembre de 2015, a les 19:29:44, Alexander Potashev va
escriure: > 2015-09-22 19:06 GMT+03:00 Luigi Toscano <[hidden email]>: > > Hi, > > many thanks for the detailed list, really helpful. I have one question: > > > > On Tuesday 22 of September 2015 18:57:58 Alexander Potashev wrote: > >> 3. These files from l10n-kde4/messages should be merged into > >> > >> l10n-kf5/.../extragear-graphics/digikam.po: > >> kdegraphics/libkgeomap.po > >> extragear-graphics/kipiplugin_acquireimages.po > >> extragear-graphics/kipiplugin_dngconverter.po > >> extragear-graphics/kipiplugin_metadataedit.po > >> extragear-graphics/kipiplugin_gpssync.po > >> kdegraphics/libkexiv2.po (this file should also be kept > >> > >> standalone as mentioned above) > > > > libkgeomap is released as a separate library; why are the same messages > > needed inside digikam? > > > > Also, libkexiv2, why should it be keep separate for now? Is it temporary? > > Or will the copy inside digikam be removed? (I hope the latter). > > Luigi, > > We decided not to release libkgeomap, but instead incorporate its > source code into digiKam core (digikam.git). That is why there will be > no libkgeomap.po in l10n-kf5. > > As for libkexiv2, its UI part (widget classes) has been moved into > digikam.git too, thus the merge of libkexiv2.po into digikam.po. I've > just checked the source code and it turns out that libkexiv2 has no > more translatable strings left, so libkexiv2.po should _not_ exist in > l10n-kf5. Sorry for my mistake. No, no and 153 times no. You can not say "We decided not to release libkgeomap". libkgeomap is already released as part of KDE Applications http://download.kde.org/stable/applications/15.08.1/src/libkgeomap-15.08.1.tar.xz.mirrorlist and so is http://download.kde.org/stable/applications/15.08.1/src/libkexiv2-15.08.1.tar.xz.mirrorlist Who has decided that they are never ever going to be released again and just part of digikam source code? In coordination with who else? I really hope this is just a bad joke. Albert _______________________________________________ Digikam-devel mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-devel |
Re: digiKam translations in l10n-kf5
|
|
2015-09-22 23:24 GMT+03:00 Albert Astals Cid <[hidden email]>:
> El Dimarts, 22 de setembre de 2015, a les 19:29:44, Alexander Potashev va > escriure: >> We decided not to release libkgeomap, but instead incorporate its >> source code into digiKam core (digikam.git). That is why there will be >> no libkgeomap.po in l10n-kf5. >> >> As for libkexiv2, its UI part (widget classes) has been moved into >> digikam.git too, thus the merge of libkexiv2.po into digikam.po. I've >> just checked the source code and it turns out that libkexiv2 has no >> more translatable strings left, so libkexiv2.po should _not_ exist in >> l10n-kf5. Sorry for my mistake. > > No, no and 153 times no. > > You can not say "We decided not to release libkgeomap". > > libkgeomap is already released as part of KDE Applications > > http://download.kde.org/stable/applications/15.08.1/src/libkgeomap-15.08.1.tar.xz.mirrorlist Albert, I meant that releasing _KF5-based_ version of libkgeomap was questionable. libkgeomap-15.08.x are KDELibs4-based, and these are not going away. We are in the process of discussing if libkgeomap/KF5 should be released soon. I guess it should be OK to the release-team if libkgeomap stays KDE4-only for some more months/years/forever? -- Alexander Potashev _______________________________________________ Digikam-devel mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-devel |
Re: digiKam translations in l10n-kf5
|
|
El Dimarts, 22 de setembre de 2015, a les 23:36:04, Alexander Potashev va
escriure: > 2015-09-22 23:24 GMT+03:00 Albert Astals Cid <[hidden email]>: > > El Dimarts, 22 de setembre de 2015, a les 19:29:44, Alexander Potashev va > > > > escriure: > >> We decided not to release libkgeomap, but instead incorporate its > >> source code into digiKam core (digikam.git). That is why there will be > >> no libkgeomap.po in l10n-kf5. > >> > >> As for libkexiv2, its UI part (widget classes) has been moved into > >> digikam.git too, thus the merge of libkexiv2.po into digikam.po. I've > >> just checked the source code and it turns out that libkexiv2 has no > >> more translatable strings left, so libkexiv2.po should _not_ exist in > >> l10n-kf5. Sorry for my mistake. > > > > No, no and 153 times no. > > > > You can not say "We decided not to release libkgeomap". > > > > libkgeomap is already released as part of KDE Applications > > > > http://download.kde.org/stable/applications/15.08.1/src/libkgeomap-15.08.1 > > .tar.xz.mirrorlist > Albert, > > I meant that releasing _KF5-based_ version of libkgeomap was > questionable. libkgeomap-15.08.x are KDELibs4-based, and these are not > going away. > > We are in the process of discussing if libkgeomap/KF5 should be > released soon. I guess it should be OK to the release-team if > libkgeomap stays KDE4-only for some more months/years/forever? releasing the same code forever makes no sense if people is supposed to be using some other code. I'd like that you guys do some coordination with the rest of non digikam people because otherwise packagers and developers get a mixed message of what things are they supposed to use/package. Cheers, Albert _______________________________________________ Digikam-devel mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-devel |
Re: digiKam translations in l10n-kf5
|
|
In reply to this post by Alexander Potashev
Do you mean that there are libraries bundled to the digiKam? That sounds terrible. Dne út 22. 9. 2015 22:36 uživatel Alexander Potashev <[hidden email]> napsal: 2015-09-22 23:24 GMT+03:00 Albert Astals Cid <[hidden email]>: _______________________________________________ Digikam-devel mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-devel |
Re: digiKam translations in l10n-kf5
|
|
2015-09-23 8:10 GMT+03:00 Vít Pelčák <[hidden email]>:
> Do you mean that there are libraries bundled to the digiKam? That sounds > terrible. Hi Vit, Not exactly "bundled libraries". The worst thing that may happen is we have two versions of libkgeomap/KF5: one compiled into digiKam/KF5 (not even as a shared), another one later released as a shared library. This is not bad for the release team, it is only bad in terms of maintainability for developers of digiKam, KPhotoAlbum and others who might want to use libkgeomap. I will try to convince Gilles that libkgeomap should stay a public shared library and be used by digiKam externally. -- Alexander Potashev > Dne út 22. 9. 2015 22:36 uživatel Alexander Potashev <[hidden email]> > napsal: >> >> 2015-09-22 23:24 GMT+03:00 Albert Astals Cid <[hidden email]>: >> > El Dimarts, 22 de setembre de 2015, a les 19:29:44, Alexander Potashev >> > va >> > escriure: >> >> We decided not to release libkgeomap, but instead incorporate its >> >> source code into digiKam core (digikam.git). That is why there will be >> >> no libkgeomap.po in l10n-kf5. >> >> >> >> As for libkexiv2, its UI part (widget classes) has been moved into >> >> digikam.git too, thus the merge of libkexiv2.po into digikam.po. I've >> >> just checked the source code and it turns out that libkexiv2 has no >> >> more translatable strings left, so libkexiv2.po should _not_ exist in >> >> l10n-kf5. Sorry for my mistake. >> > >> > No, no and 153 times no. >> > >> > You can not say "We decided not to release libkgeomap". >> > >> > libkgeomap is already released as part of KDE Applications >> > >> > >> > http://download.kde.org/stable/applications/15.08.1/src/libkgeomap-15.08.1.tar.xz.mirrorlist >> >> Albert, >> >> I meant that releasing _KF5-based_ version of libkgeomap was >> questionable. libkgeomap-15.08.x are KDELibs4-based, and these are not >> going away. >> >> We are in the process of discussing if libkgeomap/KF5 should be >> released soon. I guess it should be OK to the release-team if >> libkgeomap stays KDE4-only for some more months/years/forever? Digikam-devel mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-devel |
Re: digiKam translations in l10n-kf5
|
|
2015-09-23 12:42 GMT+03:00 Luca Beltrame <[hidden email]>:
> Il Wed, 23 Sep 2015 12:36:07 +0300, Alexander Potashev ha scritto: > > >> release team, it is only bad in terms of maintainability for developers >> of digiKam, KPhotoAlbum and others who might want to use libkgeomap. > > ... and let's not forget about packagers. I needed to say: release team _and_ _packagers_ may not care. -- Alexander Potashev _______________________________________________ Digikam-devel mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-devel |
Re: digiKam translations in l10n-kf5
|
|
In reply to this post by Alexander Potashev
2015-09-22 19:29 GMT+03:00 Alexander Potashev <[hidden email]>:
> 2015-09-22 19:06 GMT+03:00 Luigi Toscano <[hidden email]>: >> Hi, >> many thanks for the detailed list, really helpful. I have one question: >> >> On Tuesday 22 of September 2015 18:57:58 Alexander Potashev wrote: >>> 3. These files from l10n-kde4/messages should be merged into >>> l10n-kf5/.../extragear-graphics/digikam.po: >>> >>> kdegraphics/libkgeomap.po >>> extragear-graphics/kipiplugin_acquireimages.po >>> extragear-graphics/kipiplugin_dngconverter.po >>> extragear-graphics/kipiplugin_metadataedit.po >>> extragear-graphics/kipiplugin_gpssync.po >>> kdegraphics/libkexiv2.po (this file should also be kept >>> standalone as mentioned above) >> >> libkgeomap is released as a separate library; why are the same messages needed >> inside digikam? >> >> Also, libkexiv2, why should it be keep separate for now? Is it temporary? Or >> will the copy inside digikam be removed? (I hope the latter). > > Luigi, > > We decided not to release libkgeomap, but instead incorporate its > source code into digiKam core (digikam.git). That is why there will be > no libkgeomap.po in l10n-kf5. > > As for libkexiv2, its UI part (widget classes) has been moved into > digikam.git too, thus the merge of libkexiv2.po into digikam.po. I've > just checked the source code and it turns out that libkexiv2 has no > more translatable strings left, so libkexiv2.po should _not_ exist in > l10n-kf5. Sorry for my mistake. Hi Luigi, You asked me on IRC if libkgeomap.po can still be a separate translation file (digikam_geoiface.po?). I talked to Gilles and we came to the decision: this would be too complex to maintain, with regard to the possible advantages. Thus we extract the whole digikam.git repo into a single file digikam.pot as usual. The existing translations (from KDE4) can be filled into kf5/digikam.po from the six files listed above. -- Alexander Potashev _______________________________________________ Digikam-devel mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-devel |
«
Return to digikam-devel
|
1 view|%1 views
| Free forum by Nabble | Edit this page |