A Diumenge, 28 de novembre de 2010, Albert Astals Cid va escriure:
A Diumenge, 28 de novembre de 2010, Ivan Cukic va escriure:
On Monday, 22. November 2010. 19.05.45 Albert Astals Cid wrote:
A Dilluns, 22 de novembre de 2010, David Faure va escriure:
On Sunday 21 November 2010, Oswald
On Monday, 22. November 2010. 19.05.45 Albert Astals Cid wrote:
A Dilluns, 22 de novembre de 2010, David Faure va escriure:
On Sunday 21 November 2010, Oswald Buddenhagen wrote:
On Sun, Nov 21, 2010 at 12:46:53AM +, Albert Astals Cid wrote:
It achieves that by creating a static that
A Diumenge, 28 de novembre de 2010, Ivan Cukic va escriure:
On Monday, 22. November 2010. 19.05.45 Albert Astals Cid wrote:
A Dilluns, 22 de novembre de 2010, David Faure va escriure:
On Sunday 21 November 2010, Oswald Buddenhagen wrote:
On Sun, Nov 21, 2010 at 12:46:53AM +, Albert
A Dilluns, 22 de novembre de 2010, David Faure va escriure:
On Sunday 21 November 2010, Oswald Buddenhagen wrote:
On Sun, Nov 21, 2010 at 12:46:53AM +, Albert Astals Cid wrote:
It achieves that by creating a static that instructs KGlobal to load a
given translation catalog on global
On Saturday 20 November 2010 7:46:53 pm you wrote:
What do you think about the patch?
Is there any way i can convince you it's safe enough for KDE 4.6 inclusion?
I'm convinced.
[: Albert Astals Cid :]
Which this patch, your library would just have somewhere
K_CATALOG_LOADER(libkdepim);
and then all the programs linking to your library would automagically get
the libkdepim catalog loaded.
I think that it is crazy that the client code has to add library's
On Sunday 21 November 2010 00:46:53 Albert Astals Cid wrote:
Is there any way i can convince you it's safe enough for KDE 4.6 inclusion?
Albert
+1 from me, if the release team are happy I'm happy, but I see it as more a
bug fix than a new feature anyway.
John.
Quoting Albert Astals Cid aa...@kde.org:
Here comes a patch that tries to fix that by moving the catalog loading
responsability to the library, that is in my opinion where it should live.
Great!
What do you think about the patch?
Is there any way i can convince you it's safe enough for KDE
On Sun, Nov 21, 2010 at 12:46:53AM +, Albert Astals Cid wrote:
It achieves that by creating a static that instructs KGlobal to load a
given translation catalog on global locale creation.
statics in shared libraries have always been like a red flag for us. i
don't know whether the reasons
