Custom translated fields
Burkhard Lück
lueck at hube-lueck.de
Wed Jun 10 20:18:24 UTC 2015
Am Mittwoch, 10. Juni 2015, 16:19:28 schrieb Alexander Potashev:
> 2015-06-10 14:24 GMT+03:00 Jaroslaw Staniek <staniek at kde.org>:
> > 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].
> >>
and also in
http://websvn.kde.org/trunk/l10n-kf5/scripts/applycontext.cpp?view=markup
kpluginmetadata supports only translations for fields "Name" + "Description",
that is hardcoded in frameworks/kcoreaddons as well.
> >> 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?vie
> >> w=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".
> >
> > 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?
>
That is not sufficient, you need this "hint" for translated fields in
applycontext.cpp, createdesktopcontext.pl and kpluginmetadata
>
> Nice idea, I like it! Let's see if someone else in kde-i18n-doc comes
> up with a better strategy.
Use a json file and define the translation fields inside the json file, see
Milians proposal in https://svn.reviewboard.kde.org/r/7126/
--
Burkhard Lück
More information about the Kde-frameworks-devel
mailing list