El Dijous, 31 de juliol de 2014, a les 21:06:21, Alexander Potashev va escriure: > 2014-07-31 15:27 GMT+04:00 Aleix Pol <aleix...@kde.org>: > > On Thu, Jul 31, 2014 at 8:32 AM, Alexander Potashev <aspotas...@gmail.com> > > > > wrote: > >> Correct - Albert's final idea was to let the downstream decide. I'm > >> almost sure that won't work well, specifically most distros will > >> probably include all translations we ship, even very incomplete ones > >> because > >> > >> 1. Packagers won't find out soon they need to do this filtering (i.e. > >> > >> they won't notice that we've turned off filtering on our side), > >> because they didn't need to with KDE SC 4.x, > >> > >> 2. Packagers won't spent their time to write scripts for filtering > >> > >> translations in some smart way. > > > > Well, then we need to offer proper tooling. > > Aleix, > > How about shipping all available translation files in tarballs and > some filtering at build time? This way packagers will have an option > to easily modify the filtering approach. And for those packagers who > don't care there will be some kind of default filter applied at build > time, the easiest being per package threshold at 70%. > > The only downside is larger tarballs, because there will be much more > languages shipped, compared to filtering at tarball creation stage.
So you have an application, let's say VLC that is using some KDE framework, now VLC itself is in catalan at 100%, but that KDE framework is in catalan only at 25%. Why would ever someone want not to have those 25% of strings? I.e. when would someone decide not to get as many translations as possible, taking into account the framework is most probably the smallest part of visible messages? Cheers, Albert _______________________________________________ Kde-frameworks-devel mailing list Kde-frameworks-devel@kde.org https://mail.kde.org/mailman/listinfo/kde-frameworks-devel
