Custom translated fields

Albert Astals Cid aacid at kde.org
Sun Jul 5 09:22:03 UTC 2015


El Diumenge, 5 de juliol de 2015, a les 08:48:20, Jaroslaw Staniek va 
escriure:
> On Sunday, 5 July 2015, Albert Astals Cid <aacid at kde.org> wrote:
> > El Dimecres, 10 de juny de 2015, a les 13:24:57, Jaroslaw Staniek va
> 
> escriure:
> >> On 10 June 2015 at 12:26, Alexander Potashev <aspotashev at gmail.com>
> 
> wrote:
> >> > (CCing kde-i18n-doc)
> >> > Hi Jaroslaw,
> >> > 
> >> > The list of fields to extract is hardcoded in [1].
> >> > 
> >> > How many fields do you want to add? Can they be useful in other
> 
> projects?
> 
> >> > [1]
> 
> http://websvn.kde.org/trunk/l10n-kf5/scripts/createdesktopcontext.pl?view
> 
> >> > =markup
> >> 
> >> Thanks so much for the info, Alexander.
> >> I need one field at the moment, it's a plural noun explaining a
> >> "folder" name, that is for example:
> >> for a Table plugin, the the folder could be called "Tables".
> > 
> > How does this work for languages with multiple plurals?
> 
> For the need I presented it's out of scope. The 'tables' here refers to a
> set, just that.

Why do you need this to be part of the .desktop file instead of being 
somethign your plugin api provides, is it because you don't want to load the 
plugin to access it?

Cheers,
  Albert

> 
> > Cheers,
> > 
> >   Albert
> >> 
> >> It's quite custom as you see. Perhaps we can have a hint for the
> >> createdesktopcontext.pl in a "# comment" line that some field is up
> >> for translation?
> >> 
> >> > --
> >> > Alexander Potashev
> >> > 
> >> > 2015-06-10 12:41 GMT+03:00 Jaroslaw Staniek <staniek at kde.org>:
> >> >> Hi,
> >> >> KPluginMetaData::readTranslatedValue() is cool as it supports custom
> >> >> translated fields, i.e. something more than Name[...] or Comment[...].
> >> >> A question: How is make our scripty infrastructure know that a custom
> >> >> field such as Foo[...] should be translated as well?
> >> > 
> >> > 2015-06-10 12:41 GMT+03:00 Jaroslaw Staniek <staniek at kde.org>:
> >> >> Hi,
> >> >> KPluginMetaData::readTranslatedValue() is cool as it supports custom
> >> >> translated fields, i.e. something more than Name[...] or Comment[...].
> >> >> A question: How is make our scripty infrastructure know that a custom
> >> >> field such as Foo[...] should be translated as well?
> >> >> 
> >> >> --
> >> >> regards, Jaroslaw Staniek
> >> >> 
> >> >> KDE:
> >> >> : A world-wide network of software engineers, artists, writers,
> >> >> : translators
> >> >> : and facilitators committed to Free Software development -
> >> >> : http://kde.org
> >> >> 
> >> >> Calligra Suite:
> >> >> : A graphic art and office suite - http://calligra.org
> >> >> 
> >> >> Kexi:
> >> >> : A visual database apps builder - http://calligra.org/kexi
> >> >> 
> >> >> Qt Certified Specialist:
> >> >> : http://www.linkedin.com/in/jstaniek
> >> >> 
> >> >> _______________________________________________
> >> >> Kde-frameworks-devel mailing list
> >> >> Kde-frameworks-devel at kde.org
> >> >> https://mail.kde.org/mailman/listinfo/kde-frameworks-devel
> >> > 
> >> > --
> >> > Alexander Potashev
> >> > _______________________________________________
> >> > Kde-frameworks-devel mailing list
> >> > Kde-frameworks-devel at kde.org
> >> > https://mail.kde.org/mailman/listinfo/kde-frameworks-devel



More information about the Kde-frameworks-devel mailing list