RE: [PHP-DOC] RE: [DOC-HU] PHP DOC BUILDS -- PLEASE READ

>
> Some criteria was establised for this. AFAIK it was said that it
> checks for
> language-snippets.ent precense, when deciding whether a
> translation should be
> built. BTW this file is the on translations are started with, so
> it may not
> be the best to check for... Maybe a sum translated size check?
>
perhaps... i was going to go for a human aspect here... if xyz 'experienced'
phpdoc'ers were to agree a translation was ready for build, they could add
it to a file, or something.

> > Also, as a consideration: how does translated languages get
> built? I have a
> > sneaky suspicion that they get built fully. Can't we just start
> work in an
> > en tree and just rebuild the files that got translated?
>
> There were two things popping up about this:
>
>  - build only what's translated for translations
>  - build only what's changed for languages (assuming generated output
>    from a previous build is available)

Yes...
>
> Both of these would enourmously speed up the generation, so all languages
> would be built in one day. Problems with this include inconsitencies
> appearing in:
>
>  - TOC parts
>  - Prev/next links
>  - Any type of <xref> crosslinks

Right, my idea would be to try and build in a sandbox with existing content,
and then simply update what has changed. Hmm, this might be possible if we
were able to use cvs in a smart way (ie, checkout files changed since a
certain date/time)... we could get an idea of what changed. Working in a
sandbox of already built en... and just updating what needs updating, rather
than starting from the beginning. If all the links are the same (and
theoretically, they should be, they are after all just translations) then
everything should dovetail into place...


> There is also no way I know to start the transformation on
> indicidual levels
> (transform chapters in sequence programatically instead of transform one
> book). So we probably would need to generate a temporary <book> for the
> translated content with only the translated file, and then try to
> replace the
> files in the EN build with the translated ones.
>
> Then again, the above three problems appear, as well as that there may be
> files with generated IDs (ie. aen334423.html), which are also a
> problem if
> linked from the toc, but then translated. As the translated file will
> probably have a different generated ID. This is a rare case,
> AFAIK all files
> are generated after their ID (installation.apache.html) or tag names
> (copyright.html).
>
> Hope that this shed some light on the issues involved...
> Goba
>
>