[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-i18n-doc
Subject:    Re: KGeography needs your help
From:       Nicolas Goutte <nicolasg () snafu ! de>
Date:       2005-08-10 17:14:01
Message-ID: 200508101837.03485.nicolasg () snafu ! de
[Download RAW message or body]

On Wednesday 10 August 2005 05:52, Chusslove Illich wrote:
> > [: Nicolas Goutte :]
(...)
>
> > The change really seem to have a huge impact, even if the change of the
> > interface is minimal. Therefore I doubt that it will enter kdelibs
> > directly.
>
> Currently basic i18n is like this:
(...)
> KI18n::KI18n(const char* text) : m_script(false), m_priv(0)
> {
>   register KLocale *instance = KGlobal::locale();

You can drop the "register" as modern compilers do not care about it anymore.

(...)

>
> > As for kde-core-devel, yes, it will be probably a needed discussion
> > too. The question is more if you should do the discussion with some
> > code in SVN or if you should do the discussion with just a "white
> > paper", like now in this thread.
>
> I very much would like to approach kde-core-devel with the code, but I need
> some help with SVN. I've been going again though chapter on branching in
> SVN Book, but there they just assume that whole directory tree is
> branched, and then periodically merged from trunk. In this case, this
> seems excessive, as I have modified only klocale.h and klocale.cpp and
> added one .h/.cpp pair (and mentioned them in Makefile.am) in
> kdelibs/kdecore. What should I do?

Then you can choose to only branch kdelibs/kdecore and use the normal kdelibs 
for the rest.

Have a nice day!

[prev in list] [next in list] [prev in thread] [next in thread]