| Re: [AD] grabber ._txification |
[ Thread Index |
Date Index
| More lists.liballeg.org/allegro-developers Archives
]
- To: alleg-developers@xxxxxxxxxx
- Subject: Re: [AD] grabber ._txification
- From: Elias Pschernig <allefant@xxxxxxxxxx>
- Date: Sun, 24 Oct 2004 15:05:19 +0200
- Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:references; b=VlGIREoujGt6GyxBK2tbzLu/xjZDDj3gZg2PS/7tRVtqXDZ1P+JIbDkY7VNjPBI+hnVeA+UyIKjp216DYU6v1KpZkQ7zEMqbqBiipFqUywBxH7VGcblTMAIK7qPczjD4EpPA9HbRXsogn2AM5E+/ufl1QFAhQP2/AE2VZyWf63A=
>
> Commited with small cosmetical changes.
>
Thanks. I guess I'll start ._txifying all the remaining .txt files as
well - so all the documentation is handled in the same way, which is
quite nice somehow.
Btw., there is still no solution for problems like PDF not containing
external files, or the missing "back to contents" links. And adding it
to makedoc isn't trivial - if the internal format is changed, all the
output generators have to be adjusted.
I just looked again at the XML docs suggestion for Allegro 5 - and a
._tx to XML converter would be fairly easiy (i.e. just another makedoc
output target). But, what was the idea behind this? Wouldn't we still
need e.g. the maketexi.c?