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

List:       kde-i18n-doc
Subject:    Re: [RFC] Clean up the language docbooks
From:       Burkhard =?iso-8859-15?q?L=FCck?= <lueck () hube-lueck ! de>
Date:       2010-08-15 11:27:24
Message-ID: 201008151327.24747.lueck () hube-lueck ! de
[Download RAW message or body]

Am Sonntag, 15. August 2010, um 11:44:39 schrieb Chusslove Illich:
> > [: Burkhard Lück :]
> > So the language documentations have to be cleaned up and regenerated once
> > a week, otherwise it makes no sense to publish them on docs.kde.org.
> 
> Why is this? What makes publishing on docs.kde.org different from bundling
> with applications?
> 
Documentation and its translation on docs.kde.org is bundled with the 
associated applications and their versions in trunk and branch in the same way 
as in the svn archiv.

The only difference ist the update cycle for publishing the docs. From the svn 
archiv we have an update cycle for branch with every minor realease (4-6 
weeks), for trunk/kde main modules an update cycle with every major release 
(around 6 month) when trunk becomes branch, for trunk/extragear an update 
cycle with every release (different time frames for each application).

Updates for documentation and its translations on docs.kde.org are published 
once a week.

> I mean, effort should be made to keep translated docs in the repository as
> up to date as possible, but beyond that, I don't see why docs.kde.org
> should be treated in any special way. If there is some technical caveat
> about docs.kde.org, it should be fixed on its side.

It is just the other way round. If the translated docs in the repository are 
as up to date as possible (no obsolete translations, old translations from <= 
kde3 docs removed, docbook generation up to date), nothing needs to be "fixed" 
on docs.kde.org.

But in the case like a team with 100% translated docmessages, but around 50% 
old language docbooks, that needs to be "fixed" on docs.kde.org, cause it does 
not make any sense to publish a language documentation with 50% old docbooks.

Same applies to all obsolete docbook translation (english documentation was 
removed, moved, merged etc...). 
Currently they appear on docs.kde.org in the navigation tree, that is worth as 
in KHelpcenter.
And why should these docbooks handled twice, once on docs.kde.org and second 
time in svn?
Clean that once at one place in svn and everything is fine.

-- 
Burkhard Lück

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

Configure | About | News | Add a list | Sponsored by KoreLogic