[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-i18n-doc
Subject:    digiKam and DigikamImagePlugins projects merged in svn...
From:       "Gilles Caulier" <caulier.gilles () gmail ! com>
Date:       2007-03-23 9:29:03
Message-ID: b4b1230e0703230229p7c18f09ax8147fde76d856 () mail ! gmail ! com
[Download RAW message or body]

Hi all,

I'm the lead digiKam and DigikamImagePlugins developer and coordinator.

I would just ping translators team than digiKam and DigikamImagePlugins
project are now merged in svn.

I have waiting to do it since a long time. After a discussion with digiKam
team members (including some translators), we have decided to perform
merging now. The reasons are listed below :

- To solve some usability issues in digiKam image editor.  Some tools
provided by  DigikamImagePlugins are  duplicate with core editor tool and
bloat menu entries. Especially, these tools have been fusioned :

 * Blowup plugin merged with Image Editor Resize tool (digiKam core
implementation).
 * Refocus, Unsharp Mask merged with Image Editor Sharpen tool (from core
image plugin)

- One package to build for each digiKam release. We lost a lots of time to
release both package at the same time : digiKam + DigikamImagePlugins.
- Some users do not understand why all DigikamImagePlugins are not available
by default like others photo tools done (photoshop, krita, gimp, etc).
Like this all tools will be always available by default.
- The merged code is now prepared to QT4/KDE4 port planed after
0.9.2release. It's not a port. it's just a code polishing.

This is want mean than DigikamImagePlugins 0.9.2 will never exist...

This merge will change a lots of thing about translations :

- We have now just one file to translate : digikam.po.
- All Duplicate i18n will be merged to one reference in .po. Before all
plugins have a dedicated .po file and this way is the hell to translate.
- All digikamimageplugins_*.po GUI files are obsolete in svn.
- All digikamimageplugins_*.po desktop files are obsolete in svn.  all is
merged into main digikam desktop file.

Note :

- all i18n strings from these tools are unchanged. The merge have been done
as well. You can backport certainly all strings translated from old
digikamimageplugins_*.po files to the new digikam.po. If yes, let's me hear
the way to do it.
- the handbook are not yet merged. But it planed later. It's not really a
big problem because documentation is released like a separate tarball.

I hope than all my explanations have been clear... (:=)))

Regards

Gilles Caulier

[Attachment #3 (text/html)]

Hi all,<br><br>I&#39;m the lead digiKam and DigikamImagePlugins developer and \
coordinator.<br><br>I would just ping translators team than digiKam and \
DigikamImagePlugins project are now merged in svn. <br><br>I have waiting to do it \
since a long time. After a discussion with digiKam team members (including some \
translators), we have decided to perform merging now. The reasons are listed below :
<br><br>- To solve some usability issues in
digiKam image editor.&nbsp; Some tools&nbsp; provided by&nbsp; DigikamImagePlugins
are&nbsp; duplicate with core editor tool and bloat menu entries.
Especially, these tools have been fusioned :<br><br>&nbsp;* Blowup plugin merged with \
Image Editor Resize tool (digiKam core implementation). <br>&nbsp;* Refocus, Unsharp \
Mask merged with Image Editor Sharpen tool (from core image plugin)<br><br>- One \
package to build for each digiKam release. We lost a lots of time to release both \
package at the same time : digiKam + DigikamImagePlugins.
<br>- Some users do not understand why all DigikamImagePlugins are not
available by default like others photo tools done (photoshop, krita,
gimp, etc).
<br>Like this all tools will be always available by default.<br>- The merged code is \
now prepared to QT4/KDE4 port planed after 0.9.2 release. It&#39;s not a port. \
it&#39;s just a code polishing.<br><br>This is want mean than DigikamImagePlugins  \
0.9.2 will never exist...<br><br>This merge will change a lots of thing about \
translations :<br><br>- We have now just one file to translate : digikam.po.<br>- All \
Duplicate i18n will be merged to one reference in .po. Before all plugins have a \
dedicated .po file and this way is the hell to translate.
<br>


- All digikamimageplugins_*.po GUI files are obsolete in svn. <br>
- All digikamimageplugins_*.po desktop files are obsolete in svn.&nbsp; all is merged \
into main digikam desktop file. <br>

<br>Note :<br><br>- all i18n strings from these tools are unchanged. The merge have \
been done as well. You can backport certainly all strings translated from old \
digikamimageplugins_*.po files to the new digikam.po. If yes, let&#39;s me hear the \
way to do it. <br>- the handbook are not yet merged. But it planed later. It&#39;s \
not really a big problem because documentation is released like a separate \
tarball.<br> <br>I hope than all my explanations have been clear... \
(:=)))<br><br>Regards<br><span class="sg"><span><br>Gilles </span>Caulier</span>



[prev in list] [next in list] [prev in thread] [next in thread]