Hi all, just to let everybody know who is involved: Backporting of KDevelop docs has been stopped. Sorry for any inconveniences.
Bernd Am Mittwoch, 17. M?rz 2004 13:18 (UCT) schrieb Lauri Watts: > On Wednesday 17 March 2004 13.27, Erik K. Pedersen wrote: > > Onsdag 17 marts 2004 04:33 skrev Malcolm Hunter: > > > It looks like they are to me: > > > > Well I think it is more to the point that when the documentation > > writers backport something tothe branch, they should tell us. The > > system of translating docbook files as po-files works wonderfully, > > but it would be after releases I occasionally backport the docbooks > > to the branch, not the po-files. In this case translating in HEAD > > and backporting the docbooks is probably the best solution. > > The kmplot manual in HEAD and in BRANCH is the same revision, I > wonder if Rinse doesn't have a sticky tag set or something. > > I'm aware a couple of developers have backported docs (KDevelop > specifically) but since they do not coordinate with the docs team any > more than they do with i18n, there's not a whole lot I can do about > that. When I did find out, I asked them not to do that in future, > without at least asking first. > > If you are seeing backports in docs in the BRANCH, please tell me, so > I can do something about it. BRANCH is completely string frozen, and > docs, in the end, are nothing but a big bunch of strings. > > I know some of you translating, like Erik, backport your own > translations of docs, that is great. Nobody at all should be > backporting *English* docs at this point, without it having come > across this list (kde-i18n) for approval, and frankly, it's a bit > late in the cycle for approval to be given lightly. > > (CC'ed to kde-doc-english just to make the frozenness of the branch > clear all over.) > > Regards,
