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 catch any translations”: > if it does what i suspect it does, it takes the translated versions of the > strings of whatever locale the user currently has set. so if someone using > german as their language, whenever they run desktoptojson they’ll get > german strings rather than the default english ones. > > has anyone tested this with non-’c’ locales?
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. It does indeed mean that the plugin info coming from the json info in these plugins is not translated, which is a problem indeed. Cheers, -- sebas http://www.kde.org | http://vizZzion.org | GPG Key ID: 9119 0EF9 _______________________________________________ Kde-frameworks-devel mailing list [email protected] https://mail.kde.org/mailman/listinfo/kde-frameworks-devel
