On 8/23/07, M. Sokolewicz <[EMAIL PROTECTED]> wrote:
> Philip Olson wrote:
> >
> >> We have been kicking around the idea, on IRC, of making each extension
> >> "a book", i.e. having tutorial, faq, best practices and lot of other
> >> info for each and every extension. Its kinda unrealistic goal, but I
> >> think it is worth the consideration at least.
> >
> > It's well worth a consideration even knowing how much work such a move
> > would entail. Once we finalize our dream structure we will then compare
> > it to our current and then decide where to go (if anywhere) next. We'd
> > allow a lot more flexibility by designating each extension as a book,
> > but is it worth it (I think so) or do we need it? How painless of a
> > transition could we make it while keeping the translations in mind? Not
> > sure, yet.
> >
> > Regards,
> > Philip
> along with its content. However, if we make sure to implement this new
> structure alongside the current structure we should be able to keep the
> translations as-is and working, and have the english version as the most

Docbook5 supports 'sets of books' which is where the whole idea span out from.
The problem with the translations are the ones who use the "magic
english includes". Translations like Japanese and French are not an
issue as they already have the whole thing translated so they would
continue to work as-is until their structure upgraded.

The rest of the translations (which I consider 'dead/harmful
translations') are a gigantic problem, in any way you look at it.
As long as the "container pages" (chapter/reference/section) are
translated it "could" work, but if the translation only has the
refentry translated it becomes a problem when it tries to
magic-include-the-reference-page.

In theory this could work "out-of-the-box", but the translations with
missing "containers" would be unbelievable inconsistent with the rest.

I don't think its a good idea to only switch the English version and
leave the rest of the translations as-is since that would cause
massive problems for people who switch between translation (i.e. the
"view this page in ...").

-Hannes

Reply via email to