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

List:       koffice-devel
Subject:    Re: i18n errors in koffice
From:       Thomas Zander <zander () kde ! org>
Date:       2007-11-01 8:15:53
Message-ID: 200711010915.53967.zander () kde ! org
[Download RAW message or body]

[Attachment #2 (multipart/signed)]


On Wednesday 31 October 2007 21:58:24 Burkhard Lück wrote:
> On Wednesday 31 October 2007 18:35:52 Thomas Zander wrote:
> > On Wednesday 31 October 2007 18:02:16 Burkhard Lück wrote:
> > > plugins/dockers/Messages.sh:2:$XGETTEXT *.cpp shapeselector/*.cpp -o
> > > $podir/koffice-dockers.pot
> > > This is a message catalog with only one msgid, which is nonsense from a
> > > translators point of view.
> >
> > Less work is bad?
>
> Translations for an application spread over a lot of small catalogs means
> more work to keep the translations consistent and fix bugs.
>
> Developers (translators) avoid having duplicate code (translations of the
> same string), they use libraries (kdelibs4, koffice, one catalog for one
> app).

Fair enough :)

Unfortunately with plugins the dynamic changes a little.  We *can* have one 
catalog per plugin which IMO is a good thing so people get context a lot 
easier.
On the other hand its more work if you have strings that had to be translated 
the same in different contexts. I understand that.

I'm thinking the argument that we can now release a plugin 2 months after the 
KOffice-wide release with only the translations for that plugin is a good 
thing.  And the context it gives by having a 'koffice-dockers' instead of a 
big 'koffice-general' catalog is also a big plus.

But please do suggest alternate ways of working. I'm not sure what 
possibilities we have here.

> > The plugin is pretty empty, we are focussing on other functionality
> > first, but i'm pretty sure it will eventually have more messages.
>
> With plugin you mean
> plugins/dockers/Plugin.cpp:26:K_EXPORT_COMPONENT_FACTORY(kofficedockers,
> KGenericFactory<Plugin>( "Plugin" ) )?
> Then this is untranslatable because "Plugin" != "koffice-dockers"

Ah! Thats what the string is for.

You learn something new every day ;)

Fix committed.

> Nonmatching catalog name or misssing extraction to catalog ->
> untranslatable messages.

Yes, I start to understand this process a big better now. I hope lots of 
KOffice devs read this thread with as much interrest as I have, and will 
spent 10 minutes checking if their stuff is actually translatable. :)

-- 
Thomas Zander

["signature.asc" (application/pgp-signature)]

_______________________________________________
koffice-devel mailing list
koffice-devel@kde.org
https://mail.kde.org/mailman/listinfo/koffice-devel


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