Florian Anderiasch wrote:

Hi Florian,
> Hello there,
> I've got a few things to say that bug me about building new versions of
> the localized manual. I can only speak about the German translation,
> because that's where I've done a bit of work lately.
>
> The online manual at http://de.php.net/<funcname> shows "Last updated:
> Tue, 20 Sep 2005" and as I follow the commit-messages quite a bit has
> been done in that time.
>
> Now I've heard that some days ago Derick started the build process, and
> http://doc.php.net/php/de/revcheck.php seems to be up to date, but the
> docs themselves haven't changed.
>   
Derick's on holiday so I have no idea when he will be back.  We used to
get build logs on some php.net URL but I can't remember which URL it
was.  Ideally what we need is to do weekly builds per language over a
weekend using multiple machines to make the builds take quicker :)
> I may have done something wrong with de/reference/pdo/reference.xml for
> example, but even the other changes didn't show up.
>   
The revcheck script runs on a daily basis, checking out from CVS and
updating sqlite databases on my one server.

> Now the question is: Why is the manual always several months behind,
> when the stuff already *is* available. I know that this DocBook stuff
> takes ages to process, but would it be too much to at least run it every
> 2 weeks? I count 11 commits to de/ in the last 10 days alone, that are
> certainly ~15 updated pages.
>   
There is a project called 'livedocs' in progress to make manual pages
available in a faster fashion without having to rebuild the doc book stuff.
> I'm sorry if I'm bugging the wrong people, but the doc-de list isn't
> really active and I doubt that anyone there can give me details or even
> check this update (that should've been completed after a few days..)
>   
We need people to help improve the way we build docs from the current
build the doc book stuff to almost real time with live docs!

Regards
--jm
> Greetings,
> Florian
- 
Jacques Marneweck
http://www.powertrip.co.za/blog/

Reply via email to