El Viernes, 6 de Mayo de 2005 17:34, Jeremy Huntwork escribió:
> Proposed setup:
>
> multi-arch
>
> |_Common
> |
> | |_Entire Book (defaults)
> |
> |_Arch1
> |
> | |_Symlinks to ../Common if nothing arch specific
> | |_Arch-specific pages
> |
> |_Arch2 (You get the idea, same as above)
>
> Hopefully the above comes through ok. Manuel, any thoughts?
That is the ideal setup for XHTML output (but not for PDF output) IF the
number of common pages is significant and IF we can find or develop and
XML/XSL framework that could generate that hierarchy without break the PDF
output.
For the first "IF" we don't know yet what will be the real number of common
pages and where will be they located.
If, for example, the common pages are all together at the beginning of the
book, then maybe with to change the master {book} to {set}, to create a
{book} for that common pages, and to add the required {book arch="XX"} for
the rest could be enougth.
But if the common pages are missed along the book, then there is two problems
to be solved:
First, to create a profiling engine that, instead to remove from the output
the undesired marked blocks like it do now, will generate a separate page for
each arch into their own dirs containing only the related text for each arch.
And second, to generate the TOCs and navigational links properly to can read
each arch book linearly based in that new pages locations.
Nothing impossible, I think, but very difficult to implement.
--
Manuel Canales Esparcia
Usuario de LFS nº2886: http://www.linuxfromscratch.org
LFS en castellano: http://www.escomposlinux.org/lfs-es http://www.lfs-es.com
TLDP-ES: http://es.tldp.org
--
http://linuxfromscratch.org/mailman/listinfo/lfs-dev
FAQ: http://www.linuxfromscratch.org/faq/
Unsubscribe: See the above information page
