> [: Albert Astals Cid :] > Chusslove, now that we're discussing this, the current kde4 code allows > .mo files to be under ~/.kde/ (thanks to the multiple possible paths of > kstandarddirs) while the new one only finds them on > QStandardPaths::GenericDataLocation, I know some teams (and even lokalize > i think) use this feature of installing in ~/.kde/ so that you don't need > to have root to "install" the translation. > > Are we fine with losing that feature?
I never liked this as feature as such: why should it be possible to shift one particular application's internal resource (i.e. non-config) to another path, and not any other resources? I always looked at this as a pure debugging facility for translators, somewhere in between using root and building from source. So, how about providing now something more strongly debugging oriented? Like an environment variable where the translator (or a translation tool like Lokalize) can set the search paths for compiled catalogs. Maybe it could be taken as current ~/.kde/... if the environment variable is not set, to preserve behavioral compatibility, though I'd rather have it only explicitly. -- Chusslove Illich (Часлав Илић)
signature.asc
Description: This is a digitally signed message part.
_______________________________________________ Kde-frameworks-devel mailing list Kde-frameworks-devel@kde.org https://mail.kde.org/mailman/listinfo/kde-frameworks-devel
