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

List:       kde-i18n-doc
Subject:    Re: KDevelop and KDevPlatform
From:       Andreas Pakulat <apaku () gmx ! de>
Date:       2008-11-25 7:59:06
Message-ID: 20081125075906.GB21750 () morpheus ! apaku ! dnsalias ! org
[Download RAW message or body]


On 24.11.08 00:32:48, Pino Toscano wrote:
> Hi,
> 
> > Pino approached me today asking what the plan is with those two modules as
> > it seemed that so far nobody took care of i18n related things
> > (message-extraction, how many catalog files and so on). And thats correct,
> > the kdevelop module in trunk/KDE simply had the same stuff applied that has
> > been applied in any other module and IIRC we just copied its Messages.sh
> > script into kdevplatform/
> 
> And furthermore: the kdevplatform is not handled at all by scripty.

Can you tell me where scripty is in svn, so I can fix it up?

> > I don't think having a separate pot for each plugin makes sense and neither
> > does it for the libs. The kdelibs module also has only one big pot. Is
> > there anything else?
> 
> Not entirely true, kdelibs has few as well, as you can see[1]; although, the 
> bigger distinction is kdelibs4.po and kio4.po.
> 
> I personally would suggest to create one .pot for each kdevelop plugin, and 
> one for the main application (the kdevelop shell).

So all strings from the libraries in kdevplatform should go into one .pot
(they can't be installed separately anyways), then there's one .pot for
each plugin and another one for the handful of messages from
kdevelop/src/main.cpp (IIRC the rest of the code in kdevelop/src can be
deleted)

Thats fine with me, I'll try to create the needed Messages.sh scripts
tonight.

Andreas

-- 
Don't kiss an elephant on the lips today.

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

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