Martin,<br><br>It seems to me that LaTeX can easily take care of these things. Regarding plain text, I'd prefer that format instead of XML so as to reduce the background expenditure of energies. Then again, LaTeX takes plain text files as input. I didn't mean to imply .txt files when I wrote plain text... sorry about the confusion.
<br><br>Andres.<br><br><div class="gmail_quote">On Nov 15, 2007 3:37 PM, Martin McClure <<a href="mailto:martin.mcclure@gemstone.com">martin.mcclure@gemstone.com</a>> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Bruce Badger wrote:<br><br>> It's looking like we'll be building the text of the standard in the<br>> project wiki which Paolo is providing. As the bits or work are carved<br>> up I would expect the people working on a topic to put together the
<br>> text for that topic. For example, John O'Keefe is leading the errata<br>> effort.<br>><br>> Of course we will need to make sure that the work is consistent in<br>> style as well as content, so having someone keep an overall eye on
<br>> things would be great! Is that the kind of thing you had in mind?<br><br>Basically, yes. Consistent style, final assembly, and such.<br><br><br>As far as the content goes, I don't think plain text is necessarily a
<br>good format for specifying the standard. The final standard will be in<br>styled text, but it may be better to mechanically generate this text.<br>The 1998 standard has a *lot* of repetitive structure that, if done by a
<br>human, is both a lot of work and quite prone to error.<br><br>If instead we had a way to generate the text from an annotated reference<br>implementation (written in itself, so any ANSI-compliant Smalltalk could<br>execute the specification), we could reason about the spec in a form I
<br>expect we all find more convenient than text: A browser.<br><br>We'd be able to write tests to check the spec for consistency, changing<br>descriptive text in one place in the executable spec would automatically<br>
change it all the places it needed to be changed in the standard, and so<br>on.<br><br>I haven't seen a system that does precisely this, but I'm sure there are<br>things like it out there, and it doesn't look too difficult to implement
<br>even if it had to be done from scratch.<br><br>Regards,<br><br>-Martin<br><br>_______________________________________________<br>ANSI-Smalltalk mailing list<br><a href="mailto:ANSI-Smalltalk@lists.openskills.org">ANSI-Smalltalk@lists.openskills.org
</a><br><a href="http://lists.openskills.org/cgi-bin/mailman/listinfo/ansi-smalltalk" target="_blank">http://lists.openskills.org/cgi-bin/mailman/listinfo/ansi-smalltalk</a><br></blockquote></div><br>