Re: Google Summer of Code: Implement support for OASIS XLIFF 1.1 in KBabel

On Friday 01 July 2005 16:47, Nicolas Goutte wrote:
> On Friday 01 July 2005 15:56, Nicolas Goutte wrote:
> > On Thursday 30 June 2005 20:23, Stanislav Visnovsky wrote:
> > > Dňa St 29. Jún 2005 17:06 Asgeir Frimannsson napísal:
> > > > On 6/29/05, Stanislav Visnovsky <[email protected]> wrote:
> > > > > Dňa Wednesday 29 of June 2005 02:10 Asgeir Frimannsson napísal:
> > > > > > I would like, if feasible, to do the development in a QT4
> > > > > > environment, so I'll spend a few days now first trying to port it
> > > > > > to QT4. If that works, I'll branch it from there and start
> > > > > > working on implementing XLIFF support. If however the porting is
> > > > > > too complicated (I'm not *that* familiar with QT yet..) I'll go
> > > > > > with QT3..
> > > > > >
> > > > > > Any thoughts or help (KDE4 porting anyone?) on the above issues
> > > > > > would be greatly appreciated!
> > > > >
> > > > > Basically, QTextEdit API has changed completely again. That will be
> > > > > the biggest problem.
> > > > >
> > > > > IMO we should create a branch for KBabel for Qt4. I would like to
> > > > > help you with porting.
> > > >
> > > > Sounds good! So maybe we can do something like:
> > > >
> > > > 1) We create a kbabel4 branch under /branches/work/ (or import it
> > > > into /branches/work/kde4/kdesdk/kbabel?) - I'll leave this to you...
> > >
> > > IMO we should move to /branches/work/kde4/kdesdk/kbabel, where it
> > > belongs. Could you do that? I'm not sure, maybe whole kdesdk should be
> > > imported there first.
> >
> > The best would first to copy the whole kdesdk then to run the porting
> > tool on it ( (assuming that not any of those steps are already done),
>
> Please wait before making the copy!  It seems that there is a problem is
> KBabel trunk. (Somehow my copy to the kbabel_svn branch seems to have
> corrupted trunk too.)

Sorry, the problem was in my local copy. A "svn revert -R ." fixed the 
problem.

>
> Probably it is easier that I make the copy to kde4 too.

I have copied kdesdk to branches/work/kde4/kdesdk

>
> As for the porting tool, I meant only to use it on needed files.
>
> Have a nice day!
>
> > > > 2) After the initial port, I create a kbabel4-xliff branch under
> > > > /branches/work - and do the main part of my project here
> > > > 3) Depending on the success of the project we can then merge this
> > > > back into the kde4 branch.
> > > >
> > > > I did a quick test, and got libkbabelcommon compiling without very
> > > > much trouble (mostly QString/QStringList changes).
> > >
> > > I would expect that.
> > >
> > > Stano
> > > _______________________________________________
> > > kbabel mailing list
> > > [email protected]
> > > https://mail.kde.org/mailman/listinfo/kbabel
> >
> > _______________________________________________
> > kbabel mailing list
> > [email protected]
> > https://mail.kde.org/mailman/listinfo/kbabel
>
> _______________________________________________
> kbabel mailing list
> [email protected]
> https://mail.kde.org/mailman/listinfo/kbabel