| Jukka K. Korpela 2007-08-17, 6:19 pm |
| Scripsit Robert Latest:
> if HTML authoring includes HTML autogeneration, this request is
> on-topic. Otherwise please forgive me and point me in the right
> direction.
It's not about HTML but server-side operations, so c.i.w.a.tools or
c.i.w.a.misc would have been a better choice. This sounds mostly like a
tools question, so I'm sending this to c.i.w.a.tools too and setting
followups there.
> I'd like to make a bunch of dirs full of files available on a web
> server. Of course I could just leave them like they are and have the
> server take care of the listings. I don't like that because the
> listing is entirely server-dependent, if the server allows dir
> listings at all.
That's true, but the situation is server-dependent anyway (unless you do
preprocessing: generate the listing yourself and upload it whenever you make
a change to the collection of files). If you use, say, PHP to generate the
listing, then you would have to change something if you move the site to a
system where PHP is not allowed.
> On the server I'm using the listing is ugly to boot
> because the server doesn't display UTF-8 characters correctly; it
> also doesn't show file sizes and dates.
Well, that's a good enough reason to something about it. However, it's not
certain that existing software for your purposes will do UTF-8 either.
> So what I'm looking for is some little program which, when invoked in
> a directory, will produce an index.html file listing the files in
> that dir, including date and file size. With a link to the respective
> file itself of course.
You get more challenges (and, if successful, better results) if you use
short codes or icons that indicate the type of each file (like DOC, GIF
etc.), if there are different types.
> Finally, since I use makefiles to autogenerate my website, the program
> should work from the command-line without user intervention. And on
> Linux.
Oh, then you're doing preprocessing, and you have different options. I'm
pretty sure there are utilities for your purposes, but writing a suitable
one might be easier than finding a suitable one. :-) Sounds like a job for
Perl.
--
Jukka K. Korpela ("Yucca")
http://www.cs.tut.fi/~jkorpela/
|