Olivers<br><br>Others tips : in svn, i have renamed the plugin "despeckle" like noise reduction. Just use the despeckle.po file message to translate noise reduction tool mesages in digikam.po<br><br>Gilles<br><br>
<div><span class="gmail_quote">2007/3/21, Gilles Caulier <<a href="mailto:caulier.gilles@gmail.com">caulier.gilles@gmail.com</a>>:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Olivers, <br><br>Note than all the old DigikamImagePlugins translations file will can be used to translation all plugins moved to digiKam core until than i remove 2 lines in showfoto and digiKam to use the i18n catalogues...
<br><br>Also, i'm sure than you can merge all DigikamImagePlugins .po to digikam.po using a simple text editor. Like this you will lost nothing and it will simplify your work...<br><br>If you want, we can talk about by IRC...
<br><br>Gilles<br><br><div><span class="gmail_quote">2007/3/21, Oliver <<a href="mailto:oliver@doerr-privat.de" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">oliver@doerr-privat.de</a>>:</span>
<div><span class="e" id="q_1117589d7a8d1414_1"><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Gilles Caulier schrieb:<br>> 2007/3/20, Oliver <<a href="mailto:oliver@doerr-privat.de" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">oliver@doerr-privat.de</a><br>> <mailto:<a href="mailto:oliver@doerr-privat.de" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">
oliver@doerr-privat.de</a>>>:<br>>
<br>> Gilles Caulier schrieb:<br>> > Hi all,<br>> ><br>> > If you have follow my recent commits to svn about next 0.9.2<br>> release,<br>> > i have started to merge some duplicate editor tools into one and
<br>> moved<br>> > it into digiKam. This is require about to solve some usability<br>> issues<br>> > in editor.<br>> ><br>> > The tools currently moved are :<br>> >
<br>> > - Blowup plugin merged with Image Editor Resize tool (digiKam core).<br>> > - Refocus, Unsharp Mask merged with Image Editor Sharpen tool (core<br>> > image plugin)<br>> ><br>
> > About translations, this is want mean than blowup, refocus, unsharp<br>> > mask plugins translations file are obsolete in svn.<br>> ><br>> > Note than all i18n strings from these tools are unchanged. You can
<br>> > backport all strings translated from old plugins .po files to<br>> digikam.po.<br>> ><br>> > I have planed to move all DigikamImagePlugins implementation to<br>> > digiKam. The tools will be always available like a pliugins, but we
<br>> > will have only one .po file for all tools : digikam.po.<br>> ><br>> > The advantages are listed below :<br>> ><br>> > - One file to translate.<br>> > - Duplicate i18n will be merged to one reference in .po.
<br>> > - One package to build for each release : digikam.<br>> > - Image Editor plugins will be always available by default. no<br>> need to<br>> > install a separate package.<br>> >
<br>> > Also, when the plugins implementation will be moved to digiKam,<br>> i will<br>> > polish the code to prepare QT4 port (for later of course)...<br>> ><br>> > The disavantage to merge DigikamImagePlugins to digiKam is for
<br>> > translators : there are a lots of job to do about to<br>> manage/backport<br>> > old translations to digiKam core.<br>> ><br>> > Well my question is simple : what do you think about to process
<br>> > merging for 0.9.2 release ?<br>> ><br>> > Fabien, Oliver, and others digiKam translators, please let's me<br>> hear<br>> > your viewpoints... Thanks in advance.<br>
> It sound like pure horror to me. From my experience i have to re-read<br>> all fuzzies before accepting them. Just as an example the copying from<br>> the docbook from trunk to stable and the confusion that started with
<br>> that gave me plenty of fuzzies and untranslated for a docbook there<br>> every single string was translated. (Both, trunk and stable were<br>> complete translated a week after the 0.9.1 release).
<br>><br>> <a href="http://l10n.kde.org/stats/gui/stable/de/extragear-graphics/index.php" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">http://l10n.kde.org/stats/gui/stable/de/extragear-graphics/index.php
</a><br>><br>> So this merge will cost me hours and hours of my freetime. Due to the
<br>> new single file, nobody will be able to help me.<br>><br>> So from my point of view -> perhaps we will get a translated gui for<br>> digikam, but there is only litlle chance that any of other
<br>> projects like<br>> exiv2 will be transalated for the next release. So if you must to do<br>> this, do it now and give us a real extralong string freeze. Normally<br>> string freezes for digikam are not real. Even in string freeze we get
<br>> one or two changes per day.<br>><br>> Sorry<br>> Oliver<br>><br>><br>> Oliver, this is my plan :<br>><br>> - moving DigikamImagePlugins to digiKam this week.<br>> - give at least 5 weeks to translators to update
digikam.po after to<br>> have fixed i18n. I promise to you to have a stable period for<br>> translations. I fact during this period, a new branch can be started<br>> in svn about Qt4 port.<br>> - i think 0.9.2-final
release can be planed in June.<br>><br>> Fine for you ?<br>Sounds ok for me. I will try my best.<br><br>Oliver<br><br>_______________________________________________<br>Digikam-devel mailing list<br><a href="mailto:Digikam-devel@kde.org" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">
Digikam-devel@kde.org</a><br><a href="https://mail.kde.org/mailman/listinfo/digikam-devel" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">https://mail.kde.org/mailman/listinfo/digikam-devel</a><br>
</blockquote></span></div></div><br>
</blockquote></div><br>