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

List:       koffice-devel
Subject:    Re: KOffice & CVS : Can't understand the logic
From:       David Faure <david () mandrakesoft ! com>
Date:       2002-12-11 9:30:51
[Download RAW message or body]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Tuesday 10 December 2002 22:03, Macolu wrote:
> But I noticed that the KOffice i18n contents (.pot, .po, etc) are present in 
> the KDE_3_1_BRANCH. Why ?

IIRC this is where we made koffice-1.2 from. Doesn't matter anymore.
The current branches for translation are KOFFICE_1_2_BRANCH (although
that's about to be released) and HEAD.

> When this branch was created, there was no planned KOffice release (except 
> 1.2.1, but it's not the same thing). So the koffice i18n contents present in 
> the 3.1 branch is a head snapshot which doesn't correspond to anything. So it 
> is useless : outdated for head, and doesn't correspond to any release.
Right. So ? The stuff in the KDE_1_0_BRANCH is outdated too, you know.

> If it is present in the 3.1 i18n tarballs (can't check, sorry), it just 
> enlarges them for nothing.

The scripts for packaging kde-i18n remove koffice stuff.

> This situation is confusing, since translators may want to translate koffice 
> in 3.1 branch, which is a waste of time.

If they read kde-i18n-doc, they won't do so.

> IMHO, there would be an easy way to fix that (and be more logical) : do not 
> include koffice i18n contents in kde 3.1 (and following) branch, and keep 
> including it in the koffice 1.2 (and following) branch.

In the future we'll branch kde-i18n like it was branched for KOFFICE_1_2_BRANCH
recently. This is quite new - previously the releases were more "coupled".

But you raise an interesting point. I suggested a separate koffice-i18n module,
on kde-i18n-doc, and coolo said "it's not worth it, branching achieves the same".
You're right about one thing: given that some branches don't apply to koffice,
it can be confusing.

Anyway, feel free to delete koffice stuff from kde branches in the future.
Please note that we developers don't take care of kde-i18n, that's not our job.

- -- 
David FAURE, david@mandrakesoft.com, faure@kde.org
http://people.mandrakesoft.com/~david/
Contributing to: http://www.konqueror.org/, http://www.koffice.org/
Get the latest KOffice - http://download.kde.org/stable/koffice-1.2/
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.7 (GNU/Linux)

iD8DBQE99wXL72KcVAmwbhARArxlAJ46RyJeu9jUmQhJDnBFSm8tCpsA7ACfaDCs
8T3OpnTLkjXMs8WrIjWJZgc=
=Ojw6
-----END PGP SIGNATURE-----

_______________________________________________
koffice-devel mailing list
koffice-devel@mail.kde.org
http://mail.kde.org/mailman/listinfo/koffice-devel
[prev in list] [next in list] [prev in thread] [next in thread]