desktoptojson and list properties / i18n of JSON files
lueck at hube-lueck.de
Fri Nov 21 15:34:04 GMT 2014
Am Freitag, 21. November 2014, 00:07:53 schrieb Milian Wolff:
> In general though, I'd say we should not blindly translate all *.json files
> in the repository. Rather, lets come up with a more specific extension
> filter. What about *.i18n.json? I fear that using *.json is too generic and
> will lead to manual work to exclude *.json files that are not supposed to
> be translated. We didn't have this issue before since all *.desktop files
> are supposed to be translated.
We will support only translation of specific fields e.g.'KPlugin'.'Name' or
'KPlugin'. 'Description' similar to desktop files.
Why do we need a more specific extension then?
What kind of "strange" future json files you want to introduce?
More information about the kde-core-devel