Uppercase
The current implementation is using uppercase for Locale, Default Country ect. I am wondering if this is the right implementation. I am not much of a fan for using uppercase in interfaces, since it implies to much emphasis - where instead the emphasis should be on the option, not the given label.
I think the complications are minor, but worth mentionable.
1. It will make translations more difficult, where capitalization is used in the language in dutch for example this evening is s'Avonds. And I know in german there are many more cases, even in normal labeling. Do they all need to change to lowercase?
2. Contribs will need to take over this pattren, and I am not sure if thats a right direction. There are quite some contribs, which have forms within forms and complex interfaces - they might not want to adapt this pattren. But this will mean the overall Drupal interface will become inconsistent.
3. The choice has been made before to go for lowercase, and it seemed to have rolled out quite nicely. I don't think going for Uppercase, gives us an major advantage over lowercase.
http://drupal.org/files/issues/Uppercase.png
Conversation with Mark Boulton
Caps: Should be used sparingly. In the form, I'd suggested usage for Fieldset titles only. Elsewhere, caps is used to draw attention for the user, but they should be used sparingly.
Discussion
So we should discuss how we wish to use this uppercase. The biggest worry, by using it sparingly that we might cause inconsistency in the interface.
| Comment | File | Size | Author |
|---|---|---|---|
| #9 | uppercasification.patch | 454 bytes | gábor hojtsy |
| #6 | noupper.patch | 352 bytes | jacine |
| #3 | uppercasification.patch | 454 bytes | yoroy |
Comments
Comment #1
Stefan Nagtegaal commentedIMO it's even better to get rid of the whole CAPS-thing entirely.
It doesn't look good, and the way it currently is, is way to overwhelming and miss' the purpose completely.
Just my $0,02...
Comment #2
yoroy commentedAgreed the use of all caps is too much right now, as the screenshot shows.
I would go for using all caps on fieldset titles only, as Mark suggests, it then acts as a header and helps seperate multiple fieldsets from eachother:
Comment #3
yoroy commentedThis patch should style things as in the screenshot above.
Comment #4
yoroy commentedComment #5
moshe weitzman commentedAgreed that uppercase is really uncool. fieldset titles i can live with but really there is no dire need there either. better to be consistent with sentence case as we have always been.
Comment #6
jacine+1 for removing uppercase entirely from legends and labels.
Here's a patch for that just in case ;)
Comment #7
gábor hojtsyRecomponentize.
Comment #8
markboulton commentedFor clarification. CAPS should be used for Fieldset titles only. All other form elements should be lc. The caps is there to provide typographic hierarchy.
Comment #9
gábor hojtsyhttp://www.d7ux.org/content/ used caps for TITLE, CATEGORY and TAGS, which were not fieldsets. Looks like we either inferred this caps treatment wrong from that form or the state of things changed. This makes #3 RTBC. Reuploading here, so core committers are not mistaken for #6 :) I certainly don't deserve credit for this one.
Comment #10
webchickCommitted to HEAD. Thanks! :)
Comment #11
xmacinfoThank you so much. :-)