Translations for KDevelop 3.5

Hi,

lately we branched KDevelop 3 again from branches/KDE/3.5/
into
branches/kdevelop/3.5 so we can add a few features we had
lying on our
disks (KDevelop3 will stay probably until KDE 4.1, as
KDevelop4 is not
reay earlier). 

Now we've got the same problem as earlier this year when
KDevelop3.4 was
in its own branch under branches/kdevelop/3.4 and thus a
mess in
distribution shipped kdevelops was created as they packaged
KDevelop3.4.
Back then I already asked how we could make sure kdevelop's
translations
get fetched from branches/kdevelop/3.4 instead of
KDE/3.5/kdevelop and
the answer was simply adding a path to scripts/get_paths.

So I'd like to ask now wether I can commit the attached
patch doing this
change and fetching kdevelop messages from
branches/kdevelop/3.5 instead
of branches/KDE/3.5. This would allow us to let kdevelop3.5
live in the
branch and still get translations for it (the other option
would be to
merge back, though that would basically break the feature
freeze which
we'd rather not do).

Please include the kdevelop-devel list in replies as I'm not
reading
kde-i18n-doc.

Andreas

-- 
You'd like to do it instantaneously, but that's too slow.

_______________________________________________
KDevelop-devel mailing list
KDevelop-develkdevelop.org
https://barney.cs.uni-potsdam.de/mailman/listinf
o/kdevelop-devel

Tuesday 11 September 2007 14:19:35 kirjutas Stephan Johach:
> Am Samstag 08 September 2007, 21:43:07 schrieb Andreas
Pakulat:
> > Now we've got the same problem as earlier this
year when KDevelop3.4 was
> > in its own branch under branches/kdevelop/3.4 and
thus a mess in
> > distribution shipped kdevelops was created as they
packaged KDevelop3.4.
> > Back then I already asked how we could make sure
kdevelop's translations
> > get fetched from branches/kdevelop/3.4 instead of
KDE/3.5/kdevelop and
> > the answer was simply adding a path to
scripts/get_paths.
> >
> > So I'd like to ask now wether I can commit the
attached patch doing this
> > change and fetching kdevelop messages from
branches/kdevelop/3.5 instead
> > of branches/KDE/3.5. This would allow us to let
kdevelop3.5 live in the
> > branch and still get translations for it (the
other option would be to
> > merge back, though that would basically break the
feature freeze which
> > we'd rather not do).
>
> I am puzzled. Will the changes be merged to the stable
branch
> kdevelop.po then or to a separate branch for
kdevelop.po in
> branches/kdevelop/3.5?
>
> Stephan


If I remember correctly last time new strings were merged to
the stable 
branch, so creating new and fuzzy strings in existing
kdevelop.po.

Marek Laane

_______________________________________________
KDevelop-devel mailing list
KDevelop-develkdevelop.org
https://barney.cs.uni-potsdam.de/mailman/listinf
o/kdevelop-devel

Am Samstag 08 September 2007, 21:43:07 schrieb Andreas
Pakulat:
> Now we've got the same problem as earlier this year
when KDevelop3.4 was
> in its own branch under branches/kdevelop/3.4 and thus
a mess in
> distribution shipped kdevelops was created as they
packaged KDevelop3.4.
> Back then I already asked how we could make sure
kdevelop's translations
> get fetched from branches/kdevelop/3.4 instead of
KDE/3.5/kdevelop and
> the answer was simply adding a path to
scripts/get_paths.
>
> So I'd like to ask now wether I can commit the attached
patch doing this
> change and fetching kdevelop messages from
branches/kdevelop/3.5 instead
> of branches/KDE/3.5. This would allow us to let
kdevelop3.5 live in the
> branch and still get translations for it (the other
option would be to
> merge back, though that would basically break the
feature freeze which
> we'd rather not do).

I am puzzled. Will the changes be merged to the stable
branch
kdevelop.po then or to a separate branch for kdevelop.po in

branches/kdevelop/3.5?

Stephan


_______________________________________________
KDevelop-devel mailing list
KDevelop-develkdevelop.org
https://barney.cs.uni-potsdam.de/mailman/listinf
o/kdevelop-devel