not matching Catalog/Export macro names in playground/base
Burkhard Lück
lueck at hube-lueck.de
Tue Jul 14 06:49:04 CEST 2009
Am Dienstag 14 Juli 2009 00:20:46 schrieb Aaron J. Seigo:
> On Monday 13 July 2009, Burkhard Lück wrote:
> > Hi Plasma Devels,
> >
> > I checked playground/base/plasma for i18n bugs and found some of them
> > (unused catalogs, not matching catalog / EXPORT macro names and an
> > extraction to the wrong catalog), see attachment.
> >
> > How can we fix these i18n bugs?
>
> hm.. the catalogs should match if they do exist. the thing about playground
> is that the items there aren't guaranteed to ever leave and actually be
> released.
>
> would it make more sense to worry about i18n issues like catalog names only
> when they exit playground and make it into a release?
>
No for several reasons:
- who will remember to check that at that time for each single applet/engine
etc ? For example the weatherengine jumped with Revision 710826 magically from
playground into kdebase, there was no chance to check i18n in kdereview.
- in the current state in playground it is impossible to check for proper i18n
with x-test or with a translated message catalog.
- it's not that hard to fix this now (change EXPORT macro name -> one line
commit, move some translation catalogs a bit more.
- who knows all distros already packaging exceptions like networkmanager with
broken i18n (unused catalogs)?
> networkmanager is an exception there as it's already being packaged by
> distros.
Where should the unused the unused catalogs networkmanagement_openvpnui +
networkmanagement_vpncui be pulled in via insertCatalog()
So just decide in each reported case what is right, the macro name or the
catalog name. that's doable within minutes and takes less time writing these
emails.
--
Burkhard Lück
More information about the Plasma-devel
mailing list