--nextPart315144266.7hz6g0gHA8
Content-Type: Text/Plain;
  charset="iso-8859-15"
Content-Transfer-Encoding: quoted-printable

On Friday, 2009-12-11, Stephan Kulow wrote:
> On Friday 11 December 2009 16:48:38 Pino Toscano wrote:

> >  general for any XDG menu implementation. This is als why IMO having
> >  translations in .desktop files (not DE specific) is a good solution so
> >  far.
> > And if the application does not use gettext at all for its translations
> >  (for example with Qt-only or Java applications)?
>=20
> I don't see why they would want to parse the menu structure of the DE, but
> if they do I don't see a reason why they shouldn't be able to use gettext.

I don't think it is solely about the launcher menu.
An application could get the name of a desktop file as the result of a quer=
y=20
for the default handler application. Or it could implement an "open with"=20
application selection using .desktop files found in XDG specified locations.

All frameworks have native methods of reading text files, most even of pars=
ing=20
INI-style files. I am not sure Qt or Java have native support for gettext.=
=20
Probably not even through well tested extensions, e.g. Qt Solutions.

Cheers,
Kevin

=2D-=20
Kevin Krammer, KDE developer, xdg-utils developer
KDE user support, developer mentoring

--nextPart315144266.7hz6g0gHA8
Content-Type: application/pgp-signature; name=signature.asc 
Content-Description: This is a digitally signed message part.

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)

iD8DBQBLIpwPnKMhG6pzZJIRAtirAKCGY4eKWmntCO9GE1EQ/+ustkEKtgCeL6+b
VPqr10I1IYG7c1MBhzcCGP8=
=HCxa
-----END PGP SIGNATURE-----

--nextPart315144266.7hz6g0gHA8--