desktoptojson and list properties / i18n of JSON files

[Albert Astals Cid]

El Dimarts, 18 de novembre de 2014, a les 23:35:48, Milian Wolff va escriure:
> On Tuesday 18 November 2014 22:31:08 Albert Astals Cid wrote:
> > El Dimarts, 18 de novembre de 2014, a les 14:09:00, Milian Wolff va
> 
> escriure:
> > > On Tuesday 18 November 2014 12:48:42 Sebastian Kügler wrote:
> > > > On Monday, November 17, 2014 18:50:04 Milian Wolff wrote:
> > > > > > > > Or can we nowadays write the .json files directly, i.e. can
> > > > > > > > scripty/ki18n
> > > > > > > > cope with them nowadays?
> > > > > > > 
> > > > > > > So, any chance we can use .json directly here?
> > > > > > 
> > > > > > That should be possible, you can just drop the json file in there,
> > > > > > and
> > > > > > reference that in the K_PLUGIN_FACTORY_WITH_JSON macro.
> > > > > 
> > > > > So scripty and the ki18n crew can cope with .json files nowadays? No
> > > > > reason
> > > > > to  use .desktop at all anymore?
> > > > > 
> > > > > That would be an acceptable solution for me. Though I guess
> > > > > desktoptojson
> > > > > should get a big fat warning that this it is deprecated and one
> > > > > should
> > > > > better  write .json directly to prevent such issues from occurring
> > > > > randomly
> > > > > in other projects.
> > > > 
> > > > Had I read your email, I'd have said no. I don't think scripty is
> > > > ready
> > > > for
> > > > that yet, and desktoptojson isn't deprecated (and I doubt it will be
> > > > for
> > > > some time).
> > > 
> > > Criss-cross! So back to the start. What can we do about this? Since this
> > > is
> > > a serious blocker for KDevelop, I'm open for suggestions and would be
> > > willing to spent time on improving the situation.
> > > 
> > > What blocks i18n from working on JSON files, does anyone know more about
> > > this? I think fixing that would be time well spent, contrary to
> > > improving
> > > desktoptojson.
> > 
> > Why do we need i18n support in json files?
> 
> Same reason we have i18n support for .desktop files. KPluginMetaData or what
> its called uses that e.g. to show the localized names of plugins etc., no?

I didn't even know we were using json now. Why did we change from .desktop 
file to .json ones? What's the benefit? Seems like .desktop files did their 
job good enough and we have all the tooling available already.

Sorry to ask old-man questions :D

Cheers,
  Albert

> 
> Bye