Re: [AD] Re: [AL] allegro DTD |
[ Thread Index |
Date Index
| More lists.liballeg.org/allegro-developers Archives
]
- To: alleg-developers@xxxxxxxxxx
- Subject: Re: [AD] Re: [AL] allegro DTD
- From: Elias Pschernig <allefant@xxxxxxxxxx>
- Date: Tue, 30 Nov 2004 12:10:02 +0100
- 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=AJwhu1KdY8p5yxqBloVgr9L4WR5aJGPZnx54im0h6YUbiUyvtJts/douqxx3LkWSOMgyxqTJ2B0mga/CkYJxh/FXG0iRu5JcpEMsIvucJIyt8h+F3f+zsjF+AYK/FMNOeKa39A5eqDaMiM3mjZagoKSlaucX9hBy+HIFL/bCO6A=
>
> Some of the _tx formating is getting to me >:E
> o unterminated <li>s (makes it more difficult to properly parse)
> o those funky <endblock> tags should go. whos idea was that anyway? Just use
> the opener tag name ::)
>
Well, keep the last parsed element somewhere. Close it when you
encounter <endblock>. But I agree, <endblock> isn't pretty, also when
having to write new docs.
> the <b> dt lists... going to be interesting to know what to do there. Maybe
> just edit the docs to use deffinition lists instead? something.
>
Yep. For now, I'd say, just ignore <b>. The XML doesn't have to be
perfect, we will need to improve/fix the _tx format in any case.
> Why are the @chapter and @section commands multi line? Should probably be
> changed to work like the @hnode command. easier to parse as well.
>
Hm, I think that should be possible by the parser. Use something
similiar to <codeblock>...<endblock>, just the start tag is
@section<EOL>, and the end-tag is <EOL>. I think you need to add
state-awareness to the parser (even if that is almost too complicated
for such a simple format, it is just almost. I spent enough time
trying to improve makedoc to figure out how evil the current _tx is
:P)