On Friday, February 21, 2014 15:45:25 Sebastian Kügler wrote:
> Including the translations would mean that all translations have to be there
> at compile-time, which would mean that runtime changes to translations
> aren't picked up.
... are there such things as “runtime changes to translations”?
On Friday, February 21, 2014 13:51:47 Aaron J. Seigo wrote:
> Aaron J. SeigoOn Friday, February 21, 2014 13:41:29 wrote:
> > What are the plans for i18n in desktoptojson? It currently does not catch
> > any translations in the .desktop file.
>
> actually, i think it might be worse than “does not
On Friday, February 21, 2014 13:57:07 Kevin Krammer wrote:
> If we want to be able to parse .desktop files without KConfig, we need a
> desktop file parser.
valuable to know, indeed. thanks for sharing your experience, saves me some
effort.
> The Razor-Qt and LxQt people might have one already.
On Friday, 2014-02-21, 13:41:29, Aaron J. Seigo wrote:
> While there are shortcomings in QSettings for parsing random INI files, I
> don’t think any of these apply to the .desktop files we use. Would there be
> any objection / reason against dropping the use of KConfig in desktop and
> moving to Q
Aaron J. SeigoOn Friday, February 21, 2014 13:41:29 wrote:
> What are the plans for i18n in desktoptojson? It currently does not catch
> any translations in the .desktop file.
actually, i think it might be worse than “does not catch any translations”: if
it does what i suspect it does, it takes
Hi ...
So, the next fun thing I’ve run into is desktoptojson. Currently in Sprinter
I’m just hand writing the json files for the plugins. However, in its TODO file
is this:
* Metadata
* localization/i18n in plugin metadata (name, description)
* license
* author information (name, email
