Forum:Site fonts: your opinion needed: Difference between revisions

From Tardis Wiki, the free Doctor Who reference
no edit summary
No edit summary
No edit summary
Line 13: Line 13:


:::I actually don't min the section headers, but if they ae changed to show upper and lowercase then please keep them blue and fairly large, unlike once when they were black and you could barely tell the distinction between headers. Can I also ask that the navboxes at the bottom of pages be collapsable again? [[User:Glimmer721|Glimmer721]] <sup>[[User talk:Glimmer721|talk to me]]</sup> 20:51, October 16, 2011 (UTC)
:::I actually don't min the section headers, but if they ae changed to show upper and lowercase then please keep them blue and fairly large, unlike once when they were black and you could barely tell the distinction between headers. Can I also ask that the navboxes at the bottom of pages be collapsable again? [[User:Glimmer721|Glimmer721]] <sup>[[User talk:Glimmer721|talk to me]]</sup> 20:51, October 16, 2011 (UTC)
== Responding to these suggestions ==
Thanks very much for these thoughts.  The big issue, then, seems to be the sectional headings.  I've now changed them to all lowercase.  The issue for me is that they have to be ''either'' '''all lower''' or '''all upper'''.  The reason for this is that editors over the year have been ''very'' inconsistent with capitalisation of header text.  Making them go all upper or all lower instantly provides a uniformity that simply can't be achieved by going with normal sentence case. 
Of course, I realise that the MOS says that we should be using sentence case in headers, and that ''still'' applies even with enforced cap styling.  It's important to have sentence case so that people can know how to perform sectional links. (Linking to [[Companion#Species and gender]] works, while [[Companion#Species and Gender]] doesn't, even though both provide apparent blue-links.)
However, I can't think of a quick way to make the bot enforce sentence case.  There's probably a way, but it would involve writing a specialised regular expression for it, and I'm just not that regex-savvy yet.  So the quickest, easiest way to make everything ''appear'' to be uniform is just to enforce cap styling.
We've had it all upper case for a while, so now let's give lowercase a shot.  I'd appreciate your comments on whether you think this is an improvement.
{{user:CzechOut/Sig}}&nbsp;<span style="{{User:CzechOut/TimeFormat}}">02:40: Wed&nbsp;30 Nov 2011&nbsp;</span>
85,404

edits

Cookies help us deliver our services. By using our services, you agree to our use of cookies.