Re: [AD] Docs and set_gfx_mode

[ Thread Index | Date Index | More lists.liballeg.org/allegro-developers Archives ]


> > I happened to think of an acceptable way to fix those external
> > pages. When the external link is processed, a function can be called
> > to modify the external page.  This function would load the HTML
> > file as a binary block and perform a search for the standard "Back
> > to contents" text in the last 5KB. If not found, it would search
> > for the usual </body> tag and resave the file with the "Back to
> > contents" HTML chunk just before the </body> tag. Then we only need
> > to make sure allegro._tx is processed after all other ._tx files.
> > 
> > Hacky hacky. It could even work with the build/* files. Since
> > they are clearly external, we could write "Back to Allegro manual"
> > instead.
> > 
> 
> Couldn't it be added unconditionally (without scanning)?
> 

Hm, I misunderstood @externalfile. It doesn't actually include the file,
as I had expected. Maybe we should replace @externalfile by a new
command @include.. which would just parse the specified file as if it
was at that place in the main ._tx file. That would also solve the
problem of .pdf output missing some of the docs.

-- 
Elias Pschernig





Mail converted by MHonArc 2.6.19+ http://listengine.tuxfamily.org/