[ Thread Index |
Date Index
| More lists.liballeg.org/allegro-developers Archives
]
On 2008-02-06, allefant <allefant@xxxxxxxxxx> wrote:
> On Feb 6, 2008 1:42 PM, Peter Wang <novalazy@xxxxxxxxxx> wrote:
> >
> > - Cross reference support isn't so great, although good enough. See
> > inside the zip file for details.
>
> Hm..
>
> [al_map_rgb]: #al_map_rgb
>
> I wonder if we could ask them to auto-create reference points for all
> headings, like e.g. mediawiki markup does. But then, it would not be a
> real problem, as long as small awkward things like this aren't adding
> up and we end up with makedoc-like markup in the end.
Yeah. I'm sure cross references will be fixed though.
> > - It doesn't yet output Texinfo. I've mostly written an output driver
> > which does. It will be available in time.
> >
> > - It doesn't output split HTML files. We can add that support, or
> > process each section as a separate document and combine them somehow.
>
> You mean something like:
>
> manual.md:
> ...
> @include graphics.md
> @include sound.md
>
> graphics.md:
> ...
> @include al_map_rgb.md
>
> In which case I think, it should work nicely. We'd have to fix
> cross-references if they are processed separately, but shouldn't be
> too hard.
Yes, exactly.
> > Maybe we can convince the author to fix the first two as well.
> >
>
> That would be nice, especially if done in a way so also split HTML can
> be done easily :)
>
> > A few days ago I added an output driver into my Haskell makedoc program
> > that can convert allegro._tx into a format readable by Pandoc, so we can
> > easily do a once-off conversion.
>
> Will be useful especially for changelog and thanks files I guess - the
> old API docs on the other hand can stay in the 4.4 branch, except if
> we want to have a big test case for pandoc, or want to also get rid of
> makedoc for 4.4.
Neither of those files will parse though, either due to bitrot or because I
hadn't got around to supporting them yet. But they are easily converted
with a few regular expressions and editor macros, no parsing required.
Peter