I have three problems with using CSS. First, and most fundamental, if you want to turn page numbers and line numbers on and off, and offer a choice of 5 different background colors, you need 20 different CSS options. Another feature will at least double the number of files.

Not quite... unless you're not using CSS properly. With the proper use of CSS selectors, hidden and visible properties, and other attributes and classes, you can make this very small and tight. It just takes a bit of up-front planning to get it all working right. Most people don't use CSS in any sort of optimized format.

Secondly, it doesn't work on many web browsers, and I don't think that lynx and friends have any intent of ever supporting CSS.

Hence the "C" part of the CSS spec. It should always degrade properly to continue to work with the lesser capabilities of older browsers or browsers that don't support the full rich CSS styles. This includes PDAs, cellphones, WAP devices, screen scrapers, syndicated feeds, text-based browsers, text-to-speech devices, and so on.

Lastly, it's never struck me as particularly user-friendly. If you can point me to a place where it's actually used and it's easy to change without being a computer science major, I'd appreciate it.

Why should you want to "change" the CSS? Maybe I'm missing your goals here. Can you try to explain this a bit further, perhaps by providing some examples you've done that solve/show these problems? David A. Desrosiers desrod@gnu-designs.com http://gnu-designs.com