Move to kdereview: solid-actions-kcm
Kevin Ottens
ervin at kde.org
Mon Feb 23 07:31:30 GMT 2009
On Monday 23 February 2009 07:44:00 Ben Cooksley wrote:
> Further investigation into QMetaObject introspection reveals that it
> cannot be translated, since the information would be extracted at
> runtime. Is it permissible for them to not be translated in the User
> Interface of Solid Actions?
As it's more of a power user thing perhaps it's fine to not translate them.
I'm not fully sure though.
Anyway, in my mind it was to use mainly as a fallback system if no translation
is found so that you don't get screwed up by a library upgrade for instance,
you're still able to access the new feature even if not translated.
> I can create a utility to automatically generate all the desktop files
> from the Classes if needed, So that they can be translated.
That's an idea too. And in any case a good way to reduce the risks of a gap
between the kcm and the library.
As for the .desktop files themselves, you probably should probably be more
strict in how you locate them and how you deal with dups. As I pointed in my
previous mail I get all the entries twice. Granted, it looks like a bug
somewhere in KStandardDirs, but it shows that the kcm is not prepared to
handle correctly the case where the desktop file is found twice (once in the
system install, once in the user settings) which could happen.
Regards.
--
Kévin 'ervin' Ottens, http://ervin.ipsquad.net
"Ni le maître sans disciple, Ni le disciple sans maître,
Ne font reculer l'ignorance."
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 197 bytes
Desc: This is a digitally signed message part.
URL: <http://mail.kde.org/pipermail/kde-core-devel/attachments/20090223/658ebb57/attachment.sig>
More information about the kde-core-devel
mailing list