Tags on this site will likely include:

...and others like this. Maybe it's just my eyes, but at the standard zoom level the diifference between lowercase T and lowercase F is hard to read. The following are much nicer:

enter image description here

(Edit: Have to submit as a picture, because capitalized tags only work in preview, before they're connected to the existing, broken ones. Curses!)

I understand that there's a war on uppercase letters on the SE platform, but I like to capitalize my acronyms. Many tags are acronyms. Therefore, I'd like my tags to be able to be capitalized.

  • $\begingroup$ @Jonas - Fixed. They're correct in the source, and in preview... $\endgroup$ Aug 18, 2011 at 0:38
  • $\begingroup$ Ok. Anyway, I +1'ed the question already, I think uppercase acronyms are better - DCT I understand immediately, dct makes me wonder about a typo initially. $\endgroup$
    – Jonas
    Aug 18, 2011 at 0:52
  • 1
    $\begingroup$ +1, it would definitely look more professional. $\endgroup$
    – user42
    Aug 18, 2011 at 7:19
  • $\begingroup$ Or you know, simply don't use a tag for every small variation of the same topic? $\endgroup$
    – Ivo Flipse
    Aug 18, 2011 at 10:28
  • 2
    $\begingroup$ @Ivo All of these tags have very different uses, I don't think it is at all the case that it is small variations of the same topic. The last DSP class that I took easily took 2+ weeks on each item on its own. $\endgroup$
    – Kellenjb
    Aug 18, 2011 at 12:57
  • $\begingroup$ Then wouldn't a better tagging scheme be the use-case, rather than every specific method to get there? $\endgroup$
    – Ivo Flipse
    Aug 18, 2011 at 13:14
  • $\begingroup$ meta.stackexchange.com/questions/83724/… $\endgroup$ Aug 22, 2011 at 16:49
  • $\begingroup$ @Robert - That answer solves the synonyms problem by mapping all capitalization schemes to all lowercase. I'm not suggesting we go completely case-sensitive, just that we map to the capitalization scheme given on the official page for the tag instead of all-lowercase. $\endgroup$ Aug 22, 2011 at 17:25

3 Answers 3


While I completely agree that upper case tags will make life easier for us here, I'm very certain that this will be . For example, , , etc., have existed on StackOverflow for 3 years now, although people would've preferred they be capitalized. Tags are made lowercase uniformly to standardize them. Else you'll end up with [DTFT], [dtFt], [dtft], etc.

In the end, at least in my opinion, this is a very minor issue. Just as how one uses functions named fft, dct etc., in lower case in MATLAB, and still know what they mean, we'll get used to the lower case tags. It's after all the content that matters.

However, a bigger problem that I see is that tags are restricted to 25 chars. I would much rather have than . However, the former is 26 chars and won't fit. It certainly can get confusing (and lead to mistagging due to typos) with all the ctft, dtft, dft, etc., being thrown around. Again, requests to increase tag length have been denied before, so we'll have to live with that too.

  • 2
    $\begingroup$ Regarding ending up with multiple versions, it wouldn't be necessary to make tags case-sensitive. Just specify how some tags are displayed, e.g. fft as all-uppercase. $\endgroup$
    – user42
    Aug 18, 2011 at 7:20
  • $\begingroup$ @yoda - Else you'll end up with what? They all look the same to me. You need to take a screenshot of the preview to show what I think you want to show. However, I doubt that we'll end up with the situation I think you're describing; we can use the tag synonyms feature to standardize the capitalization. $\endgroup$ Aug 18, 2011 at 13:14
  • $\begingroup$ Also, the first link says When naming a tag, think about how someone would google that subject. In most cases this means typing out the full name, but you may also want to use the abbreviation. For example, "css" is probably more appropriate than "cascading-style-sheets". which is a counterpoint to your last paragraph. $\endgroup$ Aug 18, 2011 at 13:16
  • $\begingroup$ @KevinVermeer Uh, I didn't notice that it didn't render as I wanted in the final, although it showed correctly in the preview (now I see why you used an image for the second one). As to your second point, css is probably an isolated case there. Here we have dft,cft,ctft,dtft, dct all of which only differ by a letter or two. So that CSS example is not applicable here. $\endgroup$ Aug 18, 2011 at 13:54
  • $\begingroup$ In any case, I've tried my luck at TL and have gotten a "very unlikely [to be implemented]". $\endgroup$ Aug 18, 2011 at 13:57
  • $\begingroup$ @Yoda - Along with a suggestion that we make tags ALL UPPERCASE ALL THE TIME. lol. Anyway, the discussion starts here if any other mods want to read it. $\endgroup$ Aug 18, 2011 at 14:27

I will point out part of what Yoda was saying. The solution is not using acronyms in my mind. Make a synonym for your acronym! The users can use the acronym they are used to and we can all see it typed out without the exhausting work of typing it out.

Now the not fitting part, I am not sure what to say there, we need to approach tags somehow for that and adjust the tag in a standard way.

  • $\begingroup$ Though I'm almost loathe to type it, changing transform to xform solves the fitting problem if nothing else presents itself. $\endgroup$
    – Stephen
    Aug 18, 2011 at 14:24
  • 2
    $\begingroup$ You are not the only one that loathes that solution. $\endgroup$
    – Kortuk
    Aug 18, 2011 at 14:25

You can always set the text-transform property in a personal stylesheet, for example

.post-tag {
    text-transform: uppercase; 

switches all those tags to nice uppercase. Beware: this switches all tags. It should be possible to limit the change to dsp.sx via @-moz-document.


You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .