El Dimecres, 31 de juliol de 2013, a les 10:44:41, Chusslove Illich va
escriure:
> > [: Albert Astals Cid :]
> > After reading qt5 code it seems you can use XDG_DATA_DIRS to inject
> > directories in GenericDataLocation, well, it's not that bad i guess
>
> I've just used this fact in a unit test
> [: Albert Astals Cid :]
> After reading qt5 code it seems you can use XDG_DATA_DIRS to inject
> directories in GenericDataLocation, well, it's not that bad i guess
I've just used this fact in a unit test initialization (via qputenv), to
point to the location of test-specific catalogs. So it work
> [: 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 loka
On Saturday 20 July 2013 00:23:30 Albert Astals Cid wrote:
> El Divendres, 19 de juliol de 2013, a les 16:27:39, Chusslove Illich va
>
> escriure:
> > > [: David Faure :]
> > > I.e. the question is whether the search path should apply to all
> > > catalogs
> > > in the current process (loaded afte
El Dissabte, 20 de juliol de 2013, a les 09:59:52, Chusslove Illich va
escriure:
> > [: 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
El Divendres, 19 de juliol de 2013, a les 16:27:39, Chusslove Illich va
escriure:
> > [: David Faure :]
> > I.e. the question is whether the search path should apply to all catalogs
> > in the current process (loaded after the call), or should apply to an
> > individual catalog. In your example co
> [: David Faure :]
> I.e. the question is whether the search path should apply to all catalogs
> in the current process (loaded after the call), or should apply to an
> individual catalog. In your example code above, I presume the latter would
> be better.
If the search path would apply to all ca
El Divendres, 19 de juliol de 2013, a les 00:32:03, David Faure va escriure:
> On Wednesday 10 July 2013 04:14:19 Sebastian Kügler wrote:
> > Hi,
> >
> > Example code:
> >
> > const QString translationsPath = package->filePath("translations");
> > KGlobal::dirs()->addResourceDir("locale", transla
On Wednesday 10 July 2013 04:14:19 Sebastian Kügler wrote:
> Hi,
>
> Example code:
>
> const QString translationsPath = package->filePath("translations");
> KGlobal::dirs()->addResourceDir("locale", translationsPath);
> KLocalizedString::insertCatalog(dataEngineDescription.pluginName());
>
> Que
El Dimecres, 10 de juliol de 2013, a les 04:14:19, Sebastian Kügler va
escriure:
> Hi,
Hi
> Example code:
>
> const QString translationsPath = package->filePath("translations");
> KGlobal::dirs()->addResourceDir("locale", translationsPath);
> KLocalizedString::insertCatalog(dataEngineDescriptio
Hi,
Example code:
const QString translationsPath = package->filePath("translations");
KGlobal::dirs()->addResourceDir("locale", translationsPath);
KLocalizedString::insertCatalog(dataEngineDescription.pluginName());
Question:
How to port to QStandardPaths, i.e. where to insert the translations
11 matches
Mail list logo