Translations for digikam

[Duncan Hill-5]

With Gilles mentioning that Exiv2 is getting NLS support, I started looking at
doing some of the work needed to correct the digiKam interface for British
English (things like color being spelt colour).  I've worked out how to get
the .pot file, and how to use kbabel or a text editor to turn that into a .po
file.  What I can't work out is how to recompile digikam so that it knows
about the po files and converts them appropriately for use.

What have I missed? :)
_______________________________________________
Digikam-users mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-users

[Gilles Caulier-2]

Le Lundi 4 Décembre 2006 14:48, Duncan Hill a écrit :
> With Gilles mentioning that Exiv2 is getting NLS support, I started looking
> at doing some of the work needed to correct the digiKam interface for
> British English (things like color being spelt colour).
> I've worked out
> how to get the .pot file, and how to use kbabel or a text editor to turn
> that into a .po file.  What I can't work out is how to recompile digikam so
> that it knows about the po files and converts them appropriately for use.
>
> What have I missed? :)

I'm happy to see somebody witch improve the English words used by digiKam.
Like you know certainly, Me, Marcel, and Paco we are'nt native English spoken
(:=)))

I think than you missunderstand something. All strings in English witch must
be translated are in the source code. It easy to find it. Just grep the
string to correct in all *.cpp source code, and fix it with your favorite
editor.

In kde repository, all days a script parse source code to extract strings
witch must be i18n. All strings are strored in .po files witch will be
translated by i18n team.

If you want to fix English words, you need to fix source code. Forget Kbabel
and po files, it's for translators.

All internationalized strings in digiKam source code are wrapped with the
i18n() enclosure. For example we have in Comments & tags side bar :

QVGroupBox* tagsBox = new QVGroupBox(i18n("&Tags"), settingsArea);

or

popmenu.insertItem(SmallIcon("pencil"), i18n("Edit Tag Properties..."), 11);

There is some coding style to respect. For example, with i18n("&Tags"), '&' is
to introduce a keyboard shortcut. There is a guide for developpers about to
implemente internationalization :

http://developer.kde.org/documentation/library/kdeqt/kde3arch/kde-i18n-howto.html

If you provide a patch against svn implementation, i can commit you fix in
repository.

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

[Duncan Hill-2]

Caulier Gilles wrote:

> Le Lundi 4 Décembre 2006 14:48, Duncan Hill a écrit :
>> With Gilles mentioning that Exiv2 is getting NLS support, I started looking
>> at doing some of the work needed to correct the digiKam interface for
>> British English (things like color being spelt colour).
>> I've worked out
>> how to get the .pot file, and how to use kbabel or a text editor to turn
>> that into a .po file.  What I can't work out is how to recompile digikam so
>> that it knows about the po files and converts them appropriately for use.
>>
>> What have I missed? :)
>
> I'm happy to see somebody witch improve the English words used by digiKam.
> Like you know certainly, Me, Marcel, and Paco we are'nt native English spoken
> (:=)))
>
> I think than you missunderstand something. All strings in English witch must
> be translated are in the source code. It easy to find it. Just grep the
> string to correct in all *.cpp source code, and fix it with your favorite
> editor.
>
> In kde repository, all days a script parse source code to extract strings
> witch must be i18n. All strings are strored in .po files witch will be
> translated by i18n team.
>
> If you want to fix English words, you need to fix source code. Forget Kbabel
> and po files, it's for translators.

The issue is that colour is spelt in two different ways in English
(American vs British) - so even if I fix the language usage in the C++
files to be British English, someone in North America is going to
complain that the interface spells words incorrectly and demand a patch :p

I guess I'll trust in the i18n team to fix the rest of it for the
appropriate variants of English.  I'll submit patches for the source in
American English for now - I can use both equally well. :)

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

[Gilles Caulier-2]

Le Lundi 4 Décembre 2006 18:32, Duncan Hill a écrit :

> Caulier Gilles wrote:
> > Le Lundi 4 Décembre 2006 14:48, Duncan Hill a écrit :
> >> With Gilles mentioning that Exiv2 is getting NLS support, I started
> >> looking at doing some of the work needed to correct the digiKam
> >> interface for British English (things like color being spelt colour).
> >> I've worked out
> >> how to get the .pot file, and how to use kbabel or a text editor to turn
> >> that into a .po file.  What I can't work out is how to recompile digikam
> >> so that it knows about the po files and converts them appropriately for
> >> use.
> >>
> >> What have I missed? :)
> >
> > I'm happy to see somebody witch improve the English words used by
> > digiKam. Like you know certainly, Me, Marcel, and Paco we are'nt native
> > English spoken (:=)))
> >
> > I think than you missunderstand something. All strings in English witch
> > must be translated are in the source code. It easy to find it. Just grep
> > the string to correct in all *.cpp source code, and fix it with your
> > favorite editor.
> >
> > In kde repository, all days a script parse source code to extract strings
> > witch must be i18n. All strings are strored in .po files witch will be
> > translated by i18n team.
> >
> > If you want to fix English words, you need to fix source code. Forget
> > Kbabel and po files, it's for translators.
>
> The issue is that colour is spelt in two different ways in English
> (American vs British) - so even if I fix the language usage in the C++
> files to be British English, someone in North America is going to
> complain that the interface spells words incorrectly and demand a patch :p
>
> I guess I'll trust in the i18n team to fix the rest of it for the
> appropriate variants of English.  I'll submit patches for the source in
> American English for now - I can use both equally well. :)
>

Ducan,

If you check the .po file available on KDE repository, you can see a en_gb
folder dedicaced to british styles.

http://websvn.kde.org/trunk/l10n/en_GB/messages/extragear-graphics/

so, i think that all messages need to be wrapped around English US style.

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

[Gilles Caulier-2]

Le Lundi 4 Décembre 2006 18:32, Duncan Hill a écrit :

> Caulier Gilles wrote:
> > Le Lundi 4 Décembre 2006 14:48, Duncan Hill a écrit :
> >> With Gilles mentioning that Exiv2 is getting NLS support, I started
> >> looking at doing some of the work needed to correct the digiKam
> >> interface for British English (things like color being spelt colour).
> >> I've worked out
> >> how to get the .pot file, and how to use kbabel or a text editor to turn
> >> that into a .po file.  What I can't work out is how to recompile digikam
> >> so that it knows about the po files and converts them appropriately for
> >> use.
> >>
> >> What have I missed? :)
> >
> > I'm happy to see somebody witch improve the English words used by
> > digiKam. Like you know certainly, Me, Marcel, and Paco we are'nt native
> > English spoken (:=)))
> >
> > I think than you missunderstand something. All strings in English witch
> > must be translated are in the source code. It easy to find it. Just grep
> > the string to correct in all *.cpp source code, and fix it with your
> > favorite editor.
> >
> > In kde repository, all days a script parse source code to extract strings
> > witch must be i18n. All strings are strored in .po files witch will be
> > translated by i18n team.
> >
> > If you want to fix English words, you need to fix source code. Forget
> > Kbabel and po files, it's for translators.
>
> The issue is that colour is spelt in two different ways in English
> (American vs British) - so even if I fix the language usage in the C++
> files to be British English, someone in North America is going to
> complain that the interface spells words incorrectly and demand a patch :p
>
> I guess I'll trust in the i18n team to fix the rest of it for the
> appropriate variants of English.  I'll submit patches for the source in
> American English for now - I can use both equally well. :)

Ducan,

In B.K.O, there is a file reported by i18n team about wrong English typo :

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

This file is a priority. I will very happy if we can fix it before final
release. If you can take a look...

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

[Gilles Caulier-2]

Le Lundi 4 Décembre 2006 18:32, Duncan Hill a écrit :

> Caulier Gilles wrote:
> > Le Lundi 4 Décembre 2006 14:48, Duncan Hill a écrit :
> >> With Gilles mentioning that Exiv2 is getting NLS support, I started
> >> looking at doing some of the work needed to correct the digiKam
> >> interface for British English (things like color being spelt colour).
> >> I've worked out
> >> how to get the .pot file, and how to use kbabel or a text editor to turn
> >> that into a .po file.  What I can't work out is how to recompile digikam
> >> so that it knows about the po files and converts them appropriately for
> >> use.
> >>
> >> What have I missed? :)
> >
> > I'm happy to see somebody witch improve the English words used by
> > digiKam. Like you know certainly, Me, Marcel, and Paco we are'nt native
> > English spoken (:=)))
> >
> > I think than you missunderstand something. All strings in English witch
> > must be translated are in the source code. It easy to find it. Just grep
> > the string to correct in all *.cpp source code, and fix it with your
> > favorite editor.
> >
> > In kde repository, all days a script parse source code to extract strings
> > witch must be i18n. All strings are strored in .po files witch will be
> > translated by i18n team.
> >
> > If you want to fix English words, you need to fix source code. Forget
> > Kbabel and po files, it's for translators.
>
> The issue is that colour is spelt in two different ways in English
> (American vs British) - so even if I fix the language usage in the C++
> files to be British English, someone in North America is going to
> complain that the interface spells words incorrectly and demand a patch :p
>
> I guess I'll trust in the i18n team to fix the rest of it for the
> appropriate variants of English.  I'll submit patches for the source in
> American English for now - I can use both equally well. :)
>

To create a patch against svn, it explained on digiKam web site :

http://www.digikam.org/?q=contrib

The _most_ important is to always work with the current svn implementation
before to change something in source code. Just update implementation using
'svn up'.

Gilles

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

[Duncan Hill-5]

Caulier Gilles wrote:

> http://bugs.kde.org/show_bug.cgi?id=130176
>
> This file is a priority. I will very happy if we can fix it before final
> release. If you can take a look...

Patch attached to that ticket.  Fixes a fair number of the reported
strings, and some that weren't.

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

[Gilles Caulier-2]

Le lundi 4 décembre 2006 22:37, Duncan Hill a écrit :
> Caulier Gilles wrote:
> > http://bugs.kde.org/show_bug.cgi?id=130176
> >
> > This file is a priority. I will very happy if we can fix it before final
> > release. If you can take a look...
>
> Patch attached to that ticket.  Fixes a fair number of the reported
> strings, and some that weren't.
>

Great job. thanks you.

I hope tahn Marcel will include it before to release 0.9.0-RC2

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