This is the mail archive of the egcs@egcs.cygnus.com mailing list for the EGCS project. See the EGCS home page for more information.
On 5 Mar 1999 craig@jcb-sc.com wrote: > Jeff and others, before we get too closed-down on the 1.1.2 front, > could y'all make sure we'll ship it with good pointers to live > information on the web pages regarding bugs and news? Catching up this entire thread after the weekend and just having committed some additional wwwdocs fixes in preparation for the release... > I mean, I think there have been a lot of improvements made in just > the past week or two. Is there anything you'd still like to see in 1.1.2 resp. in general? > What I'm especially interested in seeing is the top-level egcs page > contain two items: > > We try to provide late-breaking information on *known bugs*, and > *news* about items already planned for upcoming releases. I have just committed a patch adding a link to bugs.html to the main page. With regard to a "forthcoming.html", well, that depends on someone providing such information. And later, Jeff wrote: > Another approach would be to reference the bug list in the FAQ. > Which would get the pointer into releases automatically. We actually already have not one, but two links to bugs.html in the FAQ. ;-) And Craig again: > I don't even see why we ship HTML pages with the distribution, unless > they're truly source files (i.e. not derived from other files)...and > even then I'd wonder why they are in HTML and not something > higher-level, like texinfo (or, for that matter, plain-text). We also ship plain-text versions (via `lynx -dump`) of those HTML files in the distribution. As to why HTML, this is the format most people can cope with easily (by means of lynx, Netscape or even vi), while very few would want to read plain *.texi files or use GNU info, at least according to my personal experience. Gerald -- Gerald "Jerry" pfeifer@dbai.tuwien.ac.at http://www.dbai.tuwien.ac.at/~pfeifer/