Garland: Accessibility/improvements and bugfixes

Stefan: I'm curious -- why not remove the Drupal version from the comment header, rather than updating it with each new version? Does the Drupal version NEED to be in there, for ease in distinguishing changes from previous versions? The $Id$ tag is there, and it seems that would be sufficient.

One reason I ask is that I'm uncertain about the purpose of the header. IMO, it doesn't assert a specific copyright claim, nor a design credit, nor anything specific -- its just the two names, and apparently occurs only in the CSS files? The other core themes don't have a similar header in their .css files; if this is about noting the well-deserved design credit, then why not have just a single header in style.css or template.php (or some other file integral to the theme).

(Please note that I ask because I don't know the answer, not because I'm suggesting that you and Steven don't deserve tremendous credit for a fantastic theme.)

@Stefan - I don't see the latest patch (#4). Thanks.

The patch induce some minor(!) changes in the display on Firefox (namely the rendering of lists), but doesn't otherwise appear to change anything. I haven't tested the IE related stuff, as I don't have IE available. :)

Edit: It should probably be noted that the list rendering is intended, according to the issues this patch is out to fix/enhance, so the fact that their rendering changed, is due to the CSS-fu working.

Edit 2: For good measure, my Firefox == Mozilla/5.0 (X11; U; Linux i686 (x86_64); da; rv:1.8.1.12) Gecko/20080201 Firefox/2.0.0.12. I only have geckos available here, so I haven't bothered to test in another browser.

Stefan, I committed this patch to CVS HEAD but found it somewhat silly to include the 'for Drupal 7' as well as the copyright headers. We don't do this for other code either. I would accept a patch that removes those for sake of consistency, and that adds you to the MAINTAINERS.txt.

"a copyright notice that it may only be used in combination with drupal"

This seems like a bad precedent and counter to the spirit of open source. If we start locking out others from using Drupal resources, they will surely do the same to us. Imagine no more Wordpress theme ports, for example. We need to maintain open sharing with other projects, otherwise we are no better than, say, Microsoft.

Thanks for the hard work,
But how do you actually make use of this patch? How do you implement it? Any dummy step-by-step please :(
Please note that one major issue with this Theme is the Slogan of the site which appear oddly in the same size as the title and in front of it. It could be nice to have the Slogan beneath the title and much smaller/italic text instead

I use Durpal 6.x, is the patch for 6.x version
http://drupal.org/node/226943

koyauni: See http://drupal.org/patch/apply for more information about applying patches.

thank you, but I host web site on a Hosting server, I am not sure how to use the patch file on the server side. Why do not they create a new Theme package so users can replace the whole theme?

Committed to CVS HEAD. Thanks.

koyauni - This issue is for fixes to a core theme for Drupal 7.x. If you want to patch your copy, you were given instructions. There won't be a separate release of the theme as this theme is part of Drupal core, not contrib.

Michelle