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

List:       kde-i18n-doc
Subject:    Re: KDE/kdevplatform
From:       Albert Astals Cid <aacid () kde ! org>
Date:       2008-11-26 21:01:11
Message-ID: 200811262201.40470.aacid () kde ! org
[Download RAW message or body]

A Dimecres 26 Novembre 2008, Andreas Pakulat va escriure:
> On 25.11.08 22:42:01, Burkhard Lück wrote:
> > Am Dienstag 25 November 2008 21:58:30 schrieben Sie:
> > > SVN commit 889037 by apaku:
> > >
> > > Add Messages.sh files to extract the messages for translation.
> > > kde-i18n team said its good to have the messages for each plugin
> > > separately.
> > > CCMAIL:kde-i18n-doc@kde.org
> >
> > [snip ]
> >
> > > +subdirs="interfaces kross language outputview project shell sublime
> > > util
> >
> > There are some more plugins in these subdirs above:
> > kross/krossplugin.cpp:46:K_EXPORT_PLUGIN(KrossSupportFactory("kdevkrossma
> >nager"))
>
> Hmm, thats basically the only i18n using code in the kross subdirectory. So
> I could just special-case the kross subdir to use kdevkrossmanager.
>
> > shell/settings/runpreferences/runpreferences.cpp:56:K_EXPORT_PLUGIN(RunPr
> >eferencesFactory("kcm_kdev_runsettings"))
> > shell/settings/ccpreferences.cpp:50:K_EXPORT_PLUGIN(CCPreferencesFactory(
> >"kcm_kdev_ccsettings"))
> > shell/settings/uipreferences.cpp:37:K_EXPORT_PLUGIN(UiPreferencesFactory(
> >"kcm_kdev_uisettings"))
> > shell/settings/bgpreferences.cpp:38:K_EXPORT_PLUGIN(BGPreferencesFactory(
> >"kcm_kdev_bgsettings"))
> > shell/settings/environmentpreferences.cpp:44:K_EXPORT_PLUGIN(PreferencesF
> >actory("kcm_kdev_envsettings"))
> > shell/settings/projectpreferences.cpp:36:K_EXPORT_PLUGIN(ProjectPreferenc
> >esFactory("kcm_kdev_projectsettings"))
>
> Those are all "part" of the shell. You can't use them without and they're
> just configuration modules too - thats why they don't have extensive
> aboutdata as the "normal" plugins.
>
> > shell/tests/nonguiinterfaceplugin.cpp:30:K_EXPORT_PLUGIN(..."kdevnonguiin
> >terfaceplugin"...
>
> Thats purely for unit-tests and doesn't/shouldn't have anything to i18n.
>
> > Seems illogical to me to export the code via K_EXPORT_PLUGIN, which also
> > exports the translations via the proper catalog name; and then extract
> > the translations into an other catalog, which has to be inserted
> > explicitely via insertCatalog()
>
> Does this mean that the .pot files should be named after the catalog used
> for the KAboutData constructor?
>
> And I'm fine to use insertCatalog for the ones in shell/settings as they're
> a core part of the shell and cannot be split off from it anyway.

Inserting catalogs is ok, yes.

Albert

>
> Andreas



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