* Joshua Slive wrote: > 1. There was one main reason I stopped developing the "wacky" style: > complexity. If felt it was over-complex both visually and > particularly the css and html code. The css code had the advantage > that it was externally developed and maintained at style.tigris.org, > but I still didn't like using something that seemed difficult to > maintain.
probably nice to hear :) I revised the css completey and hope that the ruleset is now more simple. > 2. Let's try to determine exactly what about the original style people > like better. Perhaps we can combine the two in a way that will work. > Some suggestions: > > a) Black-on-white. I tend to agree that this is preferred. hmm, really: black on white is too much contrast. After a while it hurts my eyes. But I can imagine, that for example japanese characters (symbols? could someone lead me to the right term, please? ;-) are better to read then, because they are much more complex. Of course, with xslt we are able to include a different style sheet for such case. But that's probably not a good idea. > b) Side-menu listing important stuff seperate from text rather than > having the menu integrated from the text. I like this, but I'm not > sure how much it is about the "cool" factor. It also leads to the > obvious disadvantage of having to put the whole darn page in a table, > which is annoying but very common for modern sites. I don't like the sidebar, because it wastes so much space. On the other hand on large pages, like mod/core.html it's useful and makes the page more clear. > c) Smaller font. As I mentioned in the original discussion, smaller > fonts tend to look more modern and professional, since almost all > major websites now use a less-than-default font size. Of course, it > is silly to contradict what the user set as their default font, but > since almost all sites do it, <small> can almost be considered the > default. -1 for font-size: small. If we want a small(er) font, I'd propose using px instead, because if someone set up his browser to use a smaller font by default, a font-size:small will lead to a non-readable document. > d) Other things ??? (I think the header and footer from the new > version are nicer, and I also prefer how the section titles are now > handled...) I've added a "> Modules" breadcrumb on modulesynopsis pages. And, more technical: added xml:lang and lang attribute to <html>. Also sourced out the menu items to the $lang.xml files. This results in the following changes (in $lang.xml) <messages lang="en"> <!-- attribute containing the language token. --> <!-- breadcrumb links --> <message name="apache">Apache</message> <message name="http-server">HTTP Server</message> <message name="documentation">Documentation</message> <message name="version">Version 2.0</message> <!-- super menu --> <message name="modules">Modules</message> <message name="faq">FAQ</message> <message name="glossary">Glossary</message> <message name="sitemap">Sitemap</message> <!-- footer line --> <message name="maintainedby">Maintained by the </message> I'm a bit unsure about the term "Apache HTTP Server Documentation Project" in the footer line. It's yet hardcoded in the common.xsl, because I think, it's the proper noun of the project and should not be translated. (?) you'll find my current work at: <http://test.perlig.de/apdoc/manual/> I set up several alternate style sheets (loose style, sidebar, color schemes), which you may try out using a browser that can handle them (e.g. mozilla). The whole stuff is rolled in: <http://test.perlig.de/apdoc/manual.zip> (1.3 MB, windows \n) and <http://test.perlig.de/apdoc/manual.tar.gz> (0.98 MB, unix \n) nd -- my @japh = (sub{q~Just~},sub{q~Another~},sub{q~Perl~},sub{q~Hacker~}); my $japh = q[sub japh { }]; print join ######################### [ $japh =~ /{(.)}/] -> [0] => map $_ -> () # André Malo # => @japh; # http://www.perlig.de/ # --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
