Re: [Bug-gnupedia] Design proposal

[Tom Chance]

The thing is that

1) XML isn't as well supported as HTML files created
on the fly by a perl script.

2) A database (like mySQL) would be far, far easier to
convert.

3) Say an article is removed, as previously suggested,
and other article link to that removed article. It
would be very easy to remove all links to it in a
database like mySQL, but far harder and more
time-consuming to do it with a large collection of XML
files!

Maybe in the future the perl script could create an
XML document on the fly if we saw advantages in it,
but for now I don't see any on the frontend or the
backend over HTML+Perl and mySQL+Perl

Tom Chance


--- Imran Ghory <address@hidden> wrote: > On 23
Jan 2001, at 9:46, Tom Chance wrote:
> 
> > Plus of course if we swapped systems, they'd have
> to
> > be compatible or easily interchangeable. I've been
> > talking to RMS who agrees that it would be best to
> > keep it simple with HTML (not XML or other text
> > display technologies), not only because it will
> work
> > with any browser (even lynx!) but also because it
> will
> > be easy to change into other formats should we
> wish
> > to. 
> 
> XML to HTML could be provided, also converting from
> XML into 
> other formats would probably be easier then
> converting from HTML.
> 
> XML would also allows us to give a more "uniform"
> style overall.
> 
> Imran
> 
> _______________________________________________
> Bug-gnupedia mailing list
> address@hidden
> http://mail.gnu.org/mailman/listinfo/bug-gnupedia


__________________________________________________
Do You Yahoo!?
Yahoo! Auctions - Buy the things you want at great prices. 
http://auctions.yahoo.com/