To Translators : merging DigikamImagePlugins to digiKam...

[Gilles Caulier-4]

Hi all,

If you have follow my recent commits to svn about next 0.9.2 release, i have started to merge some duplicate editor tools into one and moved it into digiKam. This is require about to solve some usability issues in editor.

The tools currently moved are :

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

About translations, this is want mean than blowup, refocus, unsharp mask plugins translations file are obsolete in svn.

Note than all i18n strings from these tools are unchanged. You can backport all strings translated from old plugins .po files to digikam.po.

I have planed to move all DigikamImagePlugins implementation to digiKam. The tools will be always available like a pliugins, but we will have only one .po file for all tools : digikam.po.

The advantages are listed below :

- One file to translate.
- Duplicate i18n will be merged to one reference in .po.
- One package to build for each release : digikam.
- Image Editor plugins will be always available by default. no need to install a separate package.

Also, when the plugins implementation will be moved to digiKam, i will polish the code to prepare QT4 port (for later of course)...

The disavantage to merge DigikamImagePlugins to digiKam is for translators : there are a lots of job to do about to manage/backport old translations to digiKam core.

Well my question is simple : what do you think about to process merging for 0.9.2 release ?

Fabien, Oliver, and others digiKam translators, please let's me hear your viewpoints... Thanks in advance.

Gilles





_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel

[Oliver Dörr]

Gilles Caulier schrieb:

> Hi all,
>
> If you have follow my recent commits to svn about next 0.9.2 release,
> i have started to merge some duplicate editor tools into one and moved
> it into digiKam. This is require about to solve some usability issues
> in editor.
>
> The tools currently moved are :
>
> - Blowup plugin merged with Image Editor Resize tool (digiKam core).
> - Refocus, Unsharp Mask merged with Image Editor Sharpen tool (core
> image plugin)
>
> About translations, this is want mean than blowup, refocus, unsharp
> mask plugins translations file are obsolete in svn.
>
> Note than all i18n strings from these tools are unchanged. You can
> backport all strings translated from old plugins .po files to digikam.po.
>
> I have planed to move all DigikamImagePlugins implementation to
> digiKam. The tools will be always available like a pliugins, but we
> will have only one .po file for all tools : digikam.po.
>
> The advantages are listed below :
>
> - One file to translate.
> - Duplicate i18n will be merged to one reference in .po.
> - One package to build for each release : digikam.
> - Image Editor plugins will be always available by default. no need to
> install a separate package.
>
> Also, when the plugins implementation will be moved to digiKam, i will
> polish the code to prepare QT4 port (for later of course)...
>
> The disavantage to merge DigikamImagePlugins to digiKam is for
> translators : there are a lots of job to do about to manage/backport
> old translations to digiKam core.
>
> Well my question is simple : what do you think about to process
> merging for 0.9.2 release ?
>
> Fabien, Oliver, and others digiKam translators, please let's me hear
> your viewpoints... Thanks in advance.

It sound like pure horror to me. From my experience i have to re-read
all fuzzies before accepting them. Just as an example the copying from
the docbook from trunk to stable and the confusion that started with
that gave me plenty of fuzzies and untranslated for a docbook there
every single string was translated. (Both, trunk and stable were
complete translated a  week after the 0.9.1 release).

http://l10n.kde.org/stats/gui/stable/de/extragear-graphics/index.php

So this merge will cost me hours and hours of my freetime. Due to the
new single file, nobody will be able to help me.

So from my point of view -> perhaps we will get a translated gui for
digikam, but there is only litlle chance that any of other projects like
exiv2 will be transalated for the next release. So if you must to do
this, do it now and give us a real extralong string freeze. Normally
string freezes for digikam are not real. Even in string freeze we get
one or two changes per day.

Sorry
Oliver

_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel

[Gilles Caulier-4]

2007/3/20, Oliver <[hidden email]>:

Gilles Caulier schrieb:

> Hi all,
>
> If you have follow my recent commits to svn about next 0.9.2 release,
> i have started to merge some duplicate editor tools into one and moved
> it into digiKam. This is require about to solve some usability issues
> in editor.
>
> The tools currently moved are :
>
> - Blowup plugin merged with Image Editor Resize tool (digiKam core).
> - Refocus, Unsharp Mask merged with Image Editor Sharpen tool (core
> image plugin)
>
> About translations, this is want mean than blowup, refocus, unsharp
> mask plugins translations file are obsolete in svn.
>
> Note than all i18n strings from these tools are unchanged. You can
> backport all strings translated from old plugins .po files to digikam.po.
>
> I have planed to move all DigikamImagePlugins implementation to
> digiKam. The tools will be always available like a pliugins, but we
> will have only one .po file for all tools : digikam.po.
>
> The advantages are listed below :
>
> - One file to translate.
> - Duplicate i18n will be merged to one reference in .po.

> - One package to build for each release : digikam.

> - Image Editor plugins will be always available by default. no need to
> install a separate package.
>
> Also, when the plugins implementation will be moved to digiKam, i will
> polish the code to prepare QT4 port (for later of course)...
>
> The disavantage to merge DigikamImagePlugins to digiKam is for
> translators : there are a lots of job to do about to manage/backport
> old translations to digiKam core.
>
> Well my question is simple : what do you think about to process
> merging for 0.9.2 release ?
>
> Fabien, Oliver, and others digiKam translators, please let's me hear
> your viewpoints... Thanks in advance.

It sound like pure horror to me. From my experience i have to re-read
all fuzzies before accepting them. Just as an example the copying from
the docbook from trunk to stable and the confusion that started with
that gave me plenty of fuzzies and untranslated for a docbook there
every single string was translated. (Both, trunk and stable were
complete translated a  week after the 0.9.1 release).

http://l10n.kde.org/stats/gui/stable/de/extragear-graphics/index.php

So this merge will cost me hours and hours of my freetime. Due to the
new single file, nobody will be able to help me.

So from my point of view -> perhaps we will get a translated gui for
digikam, but there is only litlle chance that any of other projects like
exiv2 will be transalated for the next release. So if you must to do
this, do it now and give us a real extralong string freeze. Normally
string freezes for digikam are not real. Even in string freeze we get
one or two changes per day.

Oliver,

Like an old French KDE GUI translator, i know your viewpoint. This is why i post this message here...

Note than only the GUI will be touched. The doc will be done later (and it's a separate package witch can be released later)

I have not yet taken a real decision when i will merge both package. I'm sure to do it before the QT4 port. But the question is when...

Merging source code now will take just few hours for me (:=)))

Note than for gui translations, you can ruse the already translated string from old .po files...

Gilles

_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel

[Fabien-5]

Hi,

Gilles Caulier wrote:
> If you have follow my recent commits to svn about next 0.9.2 release, i
> have started to merge some duplicate editor tools into one and moved it
> into digiKam. This is require about to solve some usability issues in
> editor.
>
> The tools currently moved are :
 >
 > [...]

>
> I have planed to move all DigikamImagePlugins implementation to digiKam.
> The tools will be always available like a pliugins, but we will have
> only one .po file for all tools : digikam.po.
>
> The advantages are listed below :
>
> - One file to translate.
> - Duplicate i18n will be merged to one reference in .po.
> - One package to build for each release : digikam.
> - Image Editor plugins will be always available by default. no need to
> install a separate package.

Ok, great !

> Also, when the plugins implementation will be moved to digiKam, i will
> polish the code to prepare QT4 port (for later of course)...
>
> The disavantage to merge DigikamImagePlugins to digiKam is for
> translators : there are a lots of job to do about to manage/backport old
> translations to digiKam core.
>
> Well my question is simple : what do you think about to process merging
> for 0.9.2 release ?

For me, it's ok, as long as the new release is not in less than one month :)

--
Fabien

_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel

[Gilles Caulier-4]

2007/3/20, Fabien <[hidden email]>:

Hi,

Gilles Caulier wrote:
> If you have follow my recent commits to svn about next 0.9.2 release, i
> have started to merge some duplicate editor tools into one and moved it
> into digiKam. This is require about to solve some usability issues in
> editor.
>
> The tools currently moved are :
>
> [...]

>
> I have planed to move all DigikamImagePlugins implementation to digiKam.
> The tools will be always available like a pliugins, but we will have
> only one .po file for all tools : digikam.po.
>
> The advantages are listed below :
>
> - One file to translate.
> - Duplicate i18n will be merged to one reference in .po.
> - One package to build for each release : digikam.
> - Image Editor plugins will be always available by default. no need to
> install a separate package.

Ok, great !

> Also, when the plugins implementation will be moved to digiKam, i will
> polish the code to prepare QT4 port (for later of course)...
>
> The disavantage to merge DigikamImagePlugins to digiKam is for
> translators : there are a lots of job to do about to manage/backport old
> translations to digiKam core.
>
> Well my question is simple : what do you think about to process merging
> for 0.9.2 release ?

For me, it's ok, as long as the new release is not in less than one month :)

yes, we can plan a final release around  last week of may, for example...

Gilles

_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel

Dnia wtorek 20 marzec 2007, Gilles Caulier napisał:
> The disavantage to merge DigikamImagePlugins to digiKam is for
> translators : there are a lots of job to do about to manage/backport old
> translations to digiKam core.

But less work for maintenance later. Also plethora of files to
translation was a real mess for managing.
>
> Well my question is simple : what do you think about to process merging
> for 0.9.2 release ?
>
> Fabien, Oliver, and others digiKam translators, please let's me hear
> your viewpoints... Thanks in advance.

Good decision :)

m.

_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel

[Gilles Caulier-4]

2007/3/20, Oliver <[hidden email]>:

Gilles Caulier schrieb:

> Hi all,
>
> If you have follow my recent commits to svn about next 0.9.2 release,
> i have started to merge some duplicate editor tools into one and moved
> it into digiKam. This is require about to solve some usability issues
> in editor.
>
> The tools currently moved are :
>
> - Blowup plugin merged with Image Editor Resize tool (digiKam core).
> - Refocus, Unsharp Mask merged with Image Editor Sharpen tool (core
> image plugin)
>
> About translations, this is want mean than blowup, refocus, unsharp
> mask plugins translations file are obsolete in svn.
>
> Note than all i18n strings from these tools are unchanged. You can
> backport all strings translated from old plugins .po files to digikam.po.
>
> I have planed to move all DigikamImagePlugins implementation to
> digiKam. The tools will be always available like a pliugins, but we
> will have only one .po file for all tools : digikam.po.
>
> The advantages are listed below :
>
> - One file to translate.
> - Duplicate i18n will be merged to one reference in .po.

> - One package to build for each release : digikam.

> - Image Editor plugins will be always available by default. no need to
> install a separate package.
>
> Also, when the plugins implementation will be moved to digiKam, i will
> polish the code to prepare QT4 port (for later of course)...
>
> The disavantage to merge DigikamImagePlugins to digiKam is for
> translators : there are a lots of job to do about to manage/backport
> old translations to digiKam core.
>
> Well my question is simple : what do you think about to process
> merging for 0.9.2 release ?
>
> Fabien, Oliver, and others digiKam translators, please let's me hear
> your viewpoints... Thanks in advance.

It sound like pure horror to me. From my experience i have to re-read
all fuzzies before accepting them. Just as an example the copying from
the docbook from trunk to stable and the confusion that started with
that gave me plenty of fuzzies and untranslated for a docbook there
every single string was translated. (Both, trunk and stable were
complete translated a  week after the 0.9.1 release).

http://l10n.kde.org/stats/gui/stable/de/extragear-graphics/index.php

So this merge will cost me hours and hours of my freetime. Due to the
new single file, nobody will be able to help me.

So from my point of view -> perhaps we will get a translated gui for
digikam, but there is only litlle chance that any of other projects like
exiv2 will be transalated for the next release. So if you must to do
this, do it now and give us a real extralong string freeze. Normally
string freezes for digikam are not real. Even in string freeze we get
one or two changes per day.

Sorry
Oliver

Oliver, this is my plan :

- moving DigikamImagePlugins to digiKam this week.
- give at least 5 weeks to translators to update digikam.po after to have fixed i18n. I promise to you to have a stable period for translations. I fact during this period, a new branch can be started in svn about Qt4 port.
- i think 0.9.2-final release can be planed in June.

Fine for you ?

Gilles

 

_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel

_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel

[Gerhard Kulzer]

/* Just a thought in the morning: The plugins were meant to be the moving
target so that the main application can be stable and the development happens
in the plugins. The situation is rather reversed since a long time: the
plugins are stable, the application changes 50% of code per week ;-) */

I propose to clear the IE menus as we are integrating the plugins. This is my
proposal (I beg your pardon if it has been suggested elsewhere before):

File (as is)

Edit (as is)

View (as is)

Color
 - Auto-Correction
 - White Balance
 - Brightness/Contrast/Gamma
 - Hue Saturation/Lightness
 - Color Effects
 - Color Balance

 - Curves Adjust
 - Level Adjust
 - Channel Mixer

 - Invert
 - Black and White
 - Color Management
 - Color Depth

Fix
 - Red Eye Reduction
 - Sharpen
 - Blur
 - Noise Reduction
 - Restoration
 - Inpainting
 - Hot Pixels
 - Anti-Vignetting
 - Lens Distortion

Transform
 - Flip ->
 - Rotate ->
 - Free Rotation
 - Change Size
 - Aspect Ration Crop
 - Shear
 - Perspective

Decoration
 - Apply texture
 - Add Border
 - Insert Text
 - Template Superimpose

Effects (or Filters)
 - Infrared Film
 - Filmgrain
 - Oilpaint
 - Charcoal Drawing
 - Emboss
 - Distortion effect
 - Blur Effects
 - Raindrops

Settings (as is)

Help (as is)


--
Hakuna matata
http://www.gerhard.fr

_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel

On Wednesday 21. of March 2007 07:21:21 Gerhard Kulzer wrote:
> I propose to clear the IE menus as we are integrating the plugins. This is
> my proposal (I beg your pardon if it has been suggested elsewhere before):

I wanted to do some simple changes (huge Colors menu to main menu...) before
0.9.1, but I thought it was better to wait for next release.
I like you proposal as menu items more follow the flow of editing and you have
put most used items (at least for beginners) more to the top of the menu.

> Fix
>  - Red Eye Reduction
>  - Sharpen
>  - Blur
>  - Noise Reduction
>  - Restoration
>  - Inpainting
>  - Hot Pixels
>  - Anti-Vignetting
>  - Lens Distortion

We might move Sharpen/Blur to the top, as it may be more used than Red Eye
Reduction, which would be then together with Noise Reduction. Having
separator after Sharpen/Blur would also be nice.
Maybe also separate Hot Pixels, Anti-Vignetting and Lens Distortion with
separator as they have more to do with fixing camera problems.

>
> Transform
>  - Flip ->
>  - Rotate ->
>  - Free Rotation
>  - Change Size
>  - Aspect Ration Crop
>  - Shear
>  - Perspective

I would put Rotate first (more used), but then it would not be together with
Free Rotation. But anyway, Free Rotation might better fit with Shear and
Perspective tool.
I am not sure if "Change Size" is better than "Resize". Therefore my
suggestion would be:
  - Resize
  - Aspect Ration Crop

  - Flip ->
  - Rotate ->
  - Free Rotation
  - Perspective
  - Shear

>
> Decoration
>  - Apply texture
>  - Add Border
>  - Insert Text
>  - Template Superimpose

Much better than Image - very good suggestion.

>
> Effects (or Filters)
>  - Infrared Film
>  - Filmgrain
>  - Oilpaint
>  - Charcoal Drawing
>  - Emboss
>  - Distortion effect
>  - Blur Effects
>  - Raindrops
>
> Settings (as is)
>
> Help (as is)

I think when we are done with this, we have to put attention to Albums GUI
menu, as that one in my opinion needs even more work (and it is harder to do
it right imho).

I think it would be good to get feedback from Celeste from KDE Usability, as
she will be doing some usability testing with digikam:
http://weblog.obso1337.org/2007/user-based-testing-expected-for-digikam-and-ubiquity/

Regards,
Luka
_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel

> Transform
>  - Flip ->
>  - Rotate ->
>  - Free Rotation
>  - Change Size
>  - Aspect Ration Crop
>  - Shear
>  - Perspective

Rotate is very, very often performed action, flip not so but to simplify
menu I would suggest inclusing *both* rotate actions into this menu
maybe with separator:

Transform
- Rotate left
- Rotate right
--------------
- Flip horizontally
- Flip vertically
--------------
- Free rotation
- Change Size
- Aspect Ration Crop
- Shear
- Perspective

Another try with flip in submenu:

Transform
- Flip ->
--------------
- Rotate left
- Rotate right
--------------
- Free rotation
- Change Size
- Aspect Ration Crop
- Shear
- Perspective

(Maybe include Free rotation in Rotate section delimited with separators)

With these inclusions this is still not the longest menu in IE but makes
life for users much, much easier.

m.

----------------------------------------------------
Przejmujący film. Poruszające, pełne emocji kino.
PLAC ZBAWICIELA - już na DVD!
http://klik.wp.pl/?adr=http%3A%2F%2Fadv.reklama.wp.pl%2Fas%2Fplaczbawiciela.html&sid=1067


_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel

[Gilles Caulier-4]

Gerhard, Luka, Mikolaj,

I'm agree to re-organize editor menus...

There is a file in B.K.O about this subject :

http://bugs.kde.org/show_bug.cgi?id=89365

Warning !  in this file, there are 3 sections : album gui, camera gui, image editor.

Album gui ==> forget.  ==> report is too old and must be refresh later in another file (if necessary), for example into #135931...
Camera gui ==> forget ==> i have planed to use KMainWindow instead KDialogBase... later. It will be obsolete
Image editor ==> to check...

Just share your experience in this file with others users. Luka, feel free to re-organize the menus in source code after than i have performed the merging. I will merge plugins as well, without change menu entries structure.

Take a care than the editor gui is common to digiKam image editor and Showfoto.

After to have changed menu structure in editor, please close #89365.

Thanks in advance

Gilles

2007/3/21, Mikołaj Machowski <[hidden email]>:

> Transform
>  - Flip ->
>  - Rotate ->
>  - Free Rotation
>  - Change Size
>  - Aspect Ration Crop
>  - Shear
>  - Perspective

Rotate is very, very often performed action, flip not so but to simplify
menu I would suggest inclusing *both* rotate actions into this menu
maybe with separator:

Transform
- Rotate left
- Rotate right
--------------
- Flip horizontally
- Flip vertically
--------------
- Free rotation
- Change Size
- Aspect Ration Crop
- Shear
- Perspective

Another try with flip in submenu:

Transform
- Flip ->
--------------
- Rotate left
- Rotate right
--------------
- Free rotation
- Change Size
- Aspect Ration Crop
- Shear
- Perspective

(Maybe include Free rotation in Rotate section delimited with separators)

With these inclusions this is still not the longest menu in IE but makes
life for users much, much easier.

m.

----------------------------------------------------
Przejmujący film. Poruszające, pełne emocji kino.
PLAC ZBAWICIELA - już na DVD!
http://klik.wp.pl/?adr=http%3A%2F%2Fadv.reklama.wp.pl%2Fas%2Fplaczbawiciela.html&sid=1067


_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel

_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel

[Celeste Lyn Paul]

> I propose to clear the IE menus as we are integrating the plugins. This is
> my proposal (I beg your pardon if it has been suggested elsewhere before):

What do you mean by clear?  Reorganizing or taking options out?

FYI, all functionality must be present in the menubar and no tools can be in
the toolbar without also being in the menubar.

> Color
>  - Auto-Correction

(BTW... Has there been any discussion on why the auto-[something] filters
popup a preview dialog?  Are your users more likely to want to preview the
change or see the change right away?)

>  - White Balance
>  - Brightness/Contrast/Gamma
>  - Hue Saturation/Lightness
>  - Color Effects
>  - Color Balance

(I assume the space is a separater bar?)

>
>  - Curves Adjust
>  - Level Adjust
>  - Channel Mixer
>
>  - Invert
>  - Black and White
>  - Color Management
>  - Color Depth
>
> Fix
>  - Red Eye Reduction
>  - Sharpen
>  - Blur
>  - Noise Reduction
>  - Restoration
>  - Inpainting
>  - Hot Pixels
>  - Anti-Vignetting
>  - Lens Distortion
>
> Transform
>  - Flip ->
>  - Rotate ->
>  - Free Rotation
>  - Change Size
>  - Aspect Ration Crop
>  - Shear
>  - Perspective
>
> Decoration
>  - Apply texture
>  - Add Border
>  - Insert Text
>  - Template Superimpose
>
> Effects (or Filters)
>  - Infrared Film
>  - Filmgrain
>  - Oilpaint
>  - Charcoal Drawing
>  - Emboss
>  - Distortion effect
>  - Blur Effects
>  - Raindrops
>
> Settings (as is)
>
> Help (as is)

Any of these actions which pop up a dialog require an ellipsis (...) after the
label.  Otherwise, the organization looks pretty good.

--
Celeste Lyn Paul
KDE Usability Project
usability.kde.org
_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel

[Gerhard Kulzer]

Am Wednesday 21 March 2007 schrieb Celeste Lyn Paul:
> > I propose to clear the IE menus as we are integrating the plugins. This
> > is my proposal (I beg your pardon if it has been suggested elsewhere
> > before):
>
> What do you mean by clear?  Reorganizing or taking options out?
Reorganizing mainly.
Gilles has already taken out a few days ago three plugins that went under one
hood:
sharpen= sharpen & refocus
Resize= resize & Blow-up
color effects= solarise & Velvia

> FYI, all functionality must be present in the menubar and no tools can be
> in the toolbar without also being in the menubar.
>
> > Color
> >  - Auto-Correction
> (BTW... Has there been any discussion on why the auto-[something] filters
> popup a preview dialog?  Are your users more likely to want to preview the
> change or see the change right away?)
Auto-Correction has 5 options, so it needs a dialog
>
> >  - White Balance
> >  - Brightness/Contrast/Gamma
> >  - Hue Saturation/Lightness
> >  - Color Effects
> >  - Color Balance
>
> (I assume the space is a separater bar?)
Yes, you assume rightly so

> >  - Curves Adjust
> >  - Level Adjust
> >  - Channel Mixer
> >
> >  - Invert
> >  - Black and White
> >  - Color Management
> >  - Color Depth
> >
> > Fix
> >  - Red Eye Reduction
> >  - Sharpen
> >  - Blur
> >  - Noise Reduction
> >  - Restoration
> >  - Inpainting
> >  - Hot Pixels
> >  - Anti-Vignetting
> >  - Lens Distortion
> >
> > Transform
> >  - Flip ->
> >  - Rotate ->
> >  - Free Rotation
> >  - Change Size
> >  - Aspect Ration Crop
> >  - Shear
> >  - Perspective
> >
> > Decoration
> >  - Apply texture
> >  - Add Border
> >  - Insert Text
> >  - Template Superimpose
> >
> > Effects (or Filters)
> >  - Infrared Film
> >  - Filmgrain
> >  - Oilpaint
> >  - Charcoal Drawing
> >  - Emboss
> >  - Distortion effect
> >  - Blur Effects
> >  - Raindrops
> >
> > Settings (as is)
> >
> > Help (as is)
>
> Any of these actions which pop up a dialog require an ellipsis (...) after
> the label.  Otherwise, the organization looks pretty good.

Will be added.

All will be carried over to B.K.O http://bugs.kde.org/show_bug.cgi?id=89365 

Gerhard
--
Hakuna matata
http://www.gerhard.fr

_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel

[Oliver Dörr]

Gilles Caulier schrieb:

> 2007/3/20, Oliver <[hidden email]
> <mailto:[hidden email]>>:
>
>     Gilles Caulier schrieb:
>     > Hi all,
>     >
>     > If you have follow my recent commits to svn about next 0.9.2
>     release,
>     > i have started to merge some duplicate editor tools into one and
>     moved
>     > it into digiKam. This is require about to solve some usability
>     issues
>     > in editor.
>     >
>     > The tools currently moved are :
>     >
>     > - Blowup plugin merged with Image Editor Resize tool (digiKam core).
>     > - Refocus, Unsharp Mask merged with Image Editor Sharpen tool (core
>     > image plugin)
>     >
>     > About translations, this is want mean than blowup, refocus, unsharp
>     > mask plugins translations file are obsolete in svn.
>     >
>     > Note than all i18n strings from these tools are unchanged. You can
>     > backport all strings translated from old plugins .po files to
>     digikam.po.
>     >
>     > I have planed to move all DigikamImagePlugins implementation to
>     > digiKam. The tools will be always available like a pliugins, but we
>     > will have only one .po file for all tools : digikam.po.
>     >
>     > The advantages are listed below :
>     >
>     > - One file to translate.
>     > - Duplicate i18n will be merged to one reference in .po.
>     > - One package to build for each release : digikam.
>     > - Image Editor plugins will be always available by default. no
>     need to
>     > install a separate package.
>     >
>     > Also, when the plugins implementation will be moved to digiKam,
>     i will
>     > polish the code to prepare QT4 port (for later of course)...
>     >
>     > The disavantage to merge DigikamImagePlugins to digiKam is for
>     > translators : there are a lots of job to do about to
>     manage/backport
>     > old translations to digiKam core.
>     >
>     > Well my question is simple : what do you think about to process
>     > merging for 0.9.2 release ?
>     >
>     > Fabien, Oliver, and others digiKam translators, please let's me
>     hear
>     > your viewpoints... Thanks in advance.
>     It sound like pure horror to me. From my experience i have to re-read
>     all fuzzies before accepting them. Just as an example the copying from
>     the docbook from trunk to stable and the confusion that started with
>     that gave me plenty of fuzzies and untranslated for a docbook there
>     every single string was translated. (Both, trunk and stable were
>     complete translated a  week after the 0.9.1 release).
>
>     http://l10n.kde.org/stats/gui/stable/de/extragear-graphics/index.php
>
>     So this merge will cost me hours and hours of my freetime. Due to the
>     new single file, nobody will be able to help me.
>
>     So from my point of view -> perhaps we will get a translated gui for
>     digikam, but there is only litlle chance that any of other
>     projects like
>     exiv2 will be transalated for the next release. So if you must to do
>     this, do it now and give us a real extralong string freeze. Normally
>     string freezes for digikam are not real. Even in string freeze we get
>     one or two changes per day.
>
>     Sorry
>     Oliver
>
>
> Oliver, this is my plan :
>
> - moving DigikamImagePlugins to digiKam this week.
> - give at least 5 weeks to translators to update digikam.po after to
> have fixed i18n. I promise to you to have a stable period for
> translations. I fact during this period, a new branch can be started
> in svn about Qt4 port.
> - i think 0.9.2-final release can be planed in June.
>
> Fine for you ?

Sounds ok for me. I will try my best.

Oliver

_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel

[Gilles Caulier-4]

Olivers,

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...

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...

If you want, we can talk about by IRC...

Gilles

2007/3/21, Oliver <[hidden email]>:

Gilles Caulier schrieb:

> 2007/3/20, Oliver <[hidden email]
> <mailto:[hidden email]>>:
>
>     Gilles Caulier schrieb:
>     > Hi all,
>     >
>     > If you have follow my recent commits to svn about next 0.9.2
>     release,
>     > i have started to merge some duplicate editor tools into one and
>     moved
>     > it into digiKam. This is require about to solve some usability
>     issues
>     > in editor.
>     >
>     > The tools currently moved are :
>     >
>     > - Blowup plugin merged with Image Editor Resize tool (digiKam core).
>     > - Refocus, Unsharp Mask merged with Image Editor Sharpen tool (core
>     > image plugin)
>     >

>     > About translations, this is want mean than blowup, refocus, unsharp

>     > mask plugins translations file are obsolete in svn.
>     >
>     > Note than all i18n strings from these tools are unchanged. You can
>     > backport all strings translated from old plugins .po files to
>     digikam.po.
>     >
>     > I have planed to move all DigikamImagePlugins implementation to
>     > digiKam. The tools will be always available like a pliugins, but we
>     > will have only one .po file for all tools : digikam.po.
>     >
>     > The advantages are listed below :
>     >
>     > - One file to translate.
>     > - Duplicate i18n will be merged to one reference in .po.
>     > - One package to build for each release : digikam.
>     > - Image Editor plugins will be always available by default. no
>     need to
>     > install a separate package.
>     >
>     > Also, when the plugins implementation will be moved to digiKam,
>     i will
>     > polish the code to prepare QT4 port (for later of course)...
>     >
>     > The disavantage to merge DigikamImagePlugins to digiKam is for
>     > translators : there are a lots of job to do about to
>     manage/backport
>     > old translations to digiKam core.
>     >
>     > Well my question is simple : what do you think about to process
>     > merging for 0.9.2 release ?
>     >
>     > Fabien, Oliver, and others digiKam translators, please let's me
>     hear
>     > your viewpoints... Thanks in advance.

>     It sound like pure horror to me. From my experience i have to re-read

>     all fuzzies before accepting them. Just as an example the copying from
>     the docbook from trunk to stable and the confusion that started with
>     that gave me plenty of fuzzies and untranslated for a docbook there
>     every single string was translated. (Both, trunk and stable were
>     complete translated a  week after the 0.9.1 release).
>
>     http://l10n.kde.org/stats/gui/stable/de/extragear-graphics/index.php
>
>     So this merge will cost me hours and hours of my freetime. Due to the
>     new single file, nobody will be able to help me.
>
>     So from my point of view -> perhaps we will get a translated gui for
>     digikam, but there is only litlle chance that any of other
>     projects like
>     exiv2 will be transalated for the next release. So if you must to do
>     this, do it now and give us a real extralong string freeze. Normally
>     string freezes for digikam are not real. Even in string freeze we get
>     one or two changes per day.
>
>     Sorry
>     Oliver
>
>
> Oliver, this is my plan :
>
> - moving DigikamImagePlugins to digiKam this week.
> - give at least 5 weeks to translators to update digikam.po after to
> have fixed i18n. I promise to you to have a stable period for
> translations. I fact during this period, a new branch can be started
> in svn about Qt4 port.
> - i think 0.9.2-final release can be planed in June.
>
> Fine for you ?

Sounds ok for me. I will try my best.

Oliver

_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel

_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel

[Gilles Caulier-4]

Olivers

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

Gilles

2007/3/21, Gilles Caulier <[hidden email]>:

Olivers,

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...

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...

If you want, we can talk about by IRC...

Gilles

2007/3/21, Oliver <[hidden email]>:

Gilles Caulier schrieb:

> 2007/3/20, Oliver <[hidden email]
> <mailto:[hidden email]>>:
>
>     Gilles Caulier schrieb:
>     > Hi all,
>     >
>     > If you have follow my recent commits to svn about next 0.9.2
>     release,
>     > i have started to merge some duplicate editor tools into one and
>     moved
>     > it into digiKam. This is require about to solve some usability
>     issues
>     > in editor.
>     >
>     > The tools currently moved are :
>     >
>     > - Blowup plugin merged with Image Editor Resize tool (digiKam core).
>     > - Refocus, Unsharp Mask merged with Image Editor Sharpen tool (core
>     > image plugin)
>     >

>     > About translations, this is want mean than blowup, refocus, unsharp

>     > mask plugins translations file are obsolete in svn.
>     >
>     > Note than all i18n strings from these tools are unchanged. You can
>     > backport all strings translated from old plugins .po files to
>     digikam.po.
>     >
>     > I have planed to move all DigikamImagePlugins implementation to
>     > digiKam. The tools will be always available like a pliugins, but we
>     > will have only one .po file for all tools : digikam.po.
>     >
>     > The advantages are listed below :
>     >
>     > - One file to translate.
>     > - Duplicate i18n will be merged to one reference in .po.
>     > - One package to build for each release : digikam.
>     > - Image Editor plugins will be always available by default. no
>     need to
>     > install a separate package.
>     >
>     > Also, when the plugins implementation will be moved to digiKam,
>     i will
>     > polish the code to prepare QT4 port (for later of course)...
>     >
>     > The disavantage to merge DigikamImagePlugins to digiKam is for
>     > translators : there are a lots of job to do about to
>     manage/backport
>     > old translations to digiKam core.
>     >
>     > Well my question is simple : what do you think about to process
>     > merging for 0.9.2 release ?
>     >
>     > Fabien, Oliver, and others digiKam translators, please let's me
>     hear
>     > your viewpoints... Thanks in advance.

>     It sound like pure horror to me. From my experience i have to re-read

>     all fuzzies before accepting them. Just as an example the copying from
>     the docbook from trunk to stable and the confusion that started with
>     that gave me plenty of fuzzies and untranslated for a docbook there
>     every single string was translated. (Both, trunk and stable were
>     complete translated a  week after the 0.9.1 release).
>
>     <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
>
>     So this merge will cost me hours and hours of my freetime. Due to the
>     new single file, nobody will be able to help me.
>
>     So from my point of view -> perhaps we will get a translated gui for
>     digikam, but there is only litlle chance that any of other
>     projects like
>     exiv2 will be transalated for the next release. So if you must to do
>     this, do it now and give us a real extralong string freeze. Normally
>     string freezes for digikam are not real. Even in string freeze we get
>     one or two changes per day.
>
>     Sorry
>     Oliver
>
>
> Oliver, this is my plan :
>
> - moving DigikamImagePlugins to digiKam this week.
> - give at least 5 weeks to translators to update digikam.po after to
> have fixed i18n. I promise to you to have a stable period for
> translations. I fact during this period, a new branch can be started
> in svn about Qt4 port.
> - i think 0.9.2-final release can be planed in June.
>
> Fine for you ?

Sounds ok for me. I will try my best.

Oliver

_______________________________________________
Digikam-devel mailing list
[hidden email]
<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

_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel

[Gilles Caulier-4]

Merging is done in svn. DigikamImagePlugins is despears now...

Gilles

2007/3/20, Gilles Caulier <[hidden email]>:

Hi all,

If you have follow my recent commits to svn about next 0.9.2 release, i have started to merge some duplicate editor tools into one and moved it into digiKam. This is require about to solve some usability issues in editor.

The tools currently moved are :

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

About translations, this is want mean than blowup, refocus, unsharp mask plugins translations file are obsolete in svn.

Note than all i18n strings from these tools are unchanged. You can backport all strings translated from old plugins .po files to digikam.po.

I have planed to move all DigikamImagePlugins implementation to digiKam. The tools will be always available like a pliugins, but we will have only one .po file for all tools : digikam.po.

The advantages are listed below :

- One file to translate.
- Duplicate i18n will be merged to one reference in .po.
- One package to build for each release : digikam.
- Image Editor plugins will be always available by default. no need to install a separate package.

Also, when the plugins implementation will be moved to digiKam, i will polish the code to prepare QT4 port (for later of course)...

The disavantage to merge DigikamImagePlugins to digiKam is for translators : there are a lots of job to do about to manage/backport old translations to digiKam core.

Well my question is simple : what do you think about to process merging for 0.9.2 release ?

Fabien, Oliver, and others digiKam translators, please let's me hear your viewpoints... Thanks in advance.

Gilles

_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel

[Gilles Caulier-4]

Fabien,

DigikamImagePlugins and digiKam are merged now into svn. Can you update your script on the web project page ?

Gilles

2007/3/20, Fabien <[hidden email]>:

Hi,

Gilles Caulier wrote:
> If you have follow my recent commits to svn about next 0.9.2 release, i
> have started to merge some duplicate editor tools into one and moved it
> into digiKam. This is require about to solve some usability issues in
> editor.
>
> The tools currently moved are :
>
> [...]

>
> I have planed to move all DigikamImagePlugins implementation to digiKam.
> The tools will be always available like a pliugins, but we will have
> only one .po file for all tools : digikam.po.
>
> The advantages are listed below :
>
> - One file to translate.
> - Duplicate i18n will be merged to one reference in .po.
> - One package to build for each release : digikam.
> - Image Editor plugins will be always available by default. no need to
> install a separate package.

Ok, great !

> Also, when the plugins implementation will be moved to digiKam, i will
> polish the code to prepare QT4 port (for later of course)...
>
> The disavantage to merge DigikamImagePlugins to digiKam is for
> translators : there are a lots of job to do about to manage/backport old
> translations to digiKam core.
>
> Well my question is simple : what do you think about to process merging
> for 0.9.2 release ?

For me, it's ok, as long as the new release is not in less than one month :)

--
Fabien

_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel

_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel

[Fabien-5]

Gilles Caulier wrote:
> Fabien,
>
> DigikamImagePlugins and digiKam are merged now into svn. Can you update
> your script on the web project page ?
>

In fact, they still work :)
I will remove the svn update digikamimageplugins that is not useful
anymore, but even with that, it's ok (no error, no warning)...


Could you resume the changes about po files ?

If I'm not wrong, there's only digikam.pot and nothing else ?
Will other digikamimageplugins*.pot be removed soon ?
http://websvn.kde.org/trunk/l10n/templates/messages/extragear-graphics/

--
Fabien

_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel

[Gilles Caulier-4]

2007/3/22, Fabien <[hidden email]>:

Gilles Caulier wrote:
> Fabien,
>
> DigikamImagePlugins and digiKam are merged now into svn. Can you update
> your script on the web project page ?
>

In fact, they still work :)
I will remove the svn update digikamimageplugins that is not useful
anymore, but even with that, it's ok (no error, no warning)...

fine...

Could you resume the changes about po files ?

If I'm not wrong, there's only digikam.pot and nothing else ?

exactly... Normally, the digikam.po will be size up.

Nota : i'm sure to 90% that we can merge all old digikamimageplugins po files to digikam.po to not re-translate all....

Will other digikamimageplugins*.pot be removed soon ?

yes, by i18n teams, not me. I'm trying to contact i18n team today by IRC about this subject.

Gilles

_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel