Edit - Meta Stack Exchange

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

Rev

154

"I understand that stylistically, uppercase headers look better, and it serves to better signify that it's a header instead of just a normal cell." I don't even agree with that. Uppercase is more difficult to read. A bold weight and the shaded background are more than sufficient to indicate that the cell is a table header. Just make all the headers use normal case. If the author wants uppercase, they can type that.
– Cody Gray - on strike
Commented Nov 24, 2020 at 4:16
62

@CodyGray The purpose of that text was less "I agree with it" and more "I see where you're coming from, but please...".
– Sonic the Anonymous Hedgehog
Commented Nov 24, 2020 at 4:18
11

@CodyGray real problem with all uppercase is if a column header needs a case-sensitive title (like in a programming language) where the styling works against language rules. I visually like the choice from a design POV, but it takes away flexibility from a coding perspective.
– bad_coder
Commented Nov 24, 2020 at 17:25
2

Yeah. Even if it were implemented as having the current all-caps formatting as the default, but with some parameter or way to disable that in specific tables (other than inappropriately using code formatting for non-code), it'd be an improvement from always formatting it as all-caps, with no exceptions.
– V2Blast
Commented Nov 27, 2020 at 8:36
11

Worse, ﬂ is one character, but breaks into two when uppercased. Similarly, ﬃ breaks into three, plus more. ſßﬆﬂ → SSSSTFL (what?)
– iBug says Reinstate Monica
Commented Nov 28, 2020 at 19:14
3

@iBug: Unicode discourages the use of those ligature characters anyway: unicode.org/faq/ligature_digraph.html. However, the German eszett is a different matter, as it's a "real letter" rather than a purely presentational artifact. Fortunately, it does have an uppercase form (ẞ) which can be used in lieu of the lowercase form.
– Kevin
Commented Nov 29, 2020 at 22:36
1

@Kevin I knew that, and that's why that's the only character I edited into my post in response to their comment. Still, though, the fact that the lowercase eszett becomes "SS" instead of ẞ is unexpected. From the looks of it, this is a direct result of the CSS attribute, and thus would be extremely difficult to work around without drastically altering the code.
– Sonic the Anonymous Hedgehog
Commented Nov 29, 2020 at 22:41
7

@Sonic: I agree that the eszett is a problem. It is likely because, at the time the lowercase eszett was added to Unicode, capital eszett was not formally a thing in German. So far as I can tell, the new capital form is considered "optional," meaning that SS is still considered a valid alternative and Unicode has to pick one or the other. Since it previously picked SS, and has to contend with various stability policies, this is probably the path of least resistance.
– Kevin
Commented Nov 29, 2020 at 22:51
It's also impossible to type the German eszett symbol ß into a header, as that breaks apart into "SS" Actually, german has an uppercase ß, the ẞ. Capitalizing ß as SS is wrong.
– Polygnome
Commented Dec 4, 2020 at 14:48
3

@Polygnome See the above two comments.
– Sonic the Anonymous Hedgehog
Commented Dec 4, 2020 at 20:04
1

@Polygnome Capitalizing ß as SS is not wrong. See § 25 E3
– jazzpi
Commented Dec 7, 2020 at 13:03
2

There is a workaround using MathJax: meta.stackexchange.com/a/357525/391772. It's not ideal though.
– user1271772
Commented Dec 7, 2020 at 17:49
4

Aaron says that this will be in the next version of Stacks but he's having to work around some alignment issues.
– Catija
Commented Dec 7, 2020 at 20:46
6

@poke It was in the Stacks design, but was removed 7 days ago. Unfortunately, as Catija commented, they ran into some layout issues with that, so the latest version hasn't been deployed to the sites yet. They're still on the older version that has it.
– Sonic the Anonymous Hedgehog
Commented Dec 8, 2020 at 9:16
4

There can be lags in publishing to Stacks and getting Stacks into production. As you can imagine, there's quite a bit more testing that needs to happen on the production side before we can get our Stacks package updated everywhere. This is in production everywhere now and things are looking good across the app.
– Aaron Shekey
Commented Dec 14, 2020 at 18:54

| Show 4 more comments

Correct minor typos or mistakes
Clarify meaning without changing it
Add related resources or links
Always respect the author’s intent
Don’t use edits to reply to the author

create code fences with backticks ` or tildes ~
```
like so
```
add language identifier to highlight code
```python
def function(foo):
print(foo)
```
put returns between paragraphs
for linebreak add 2 spaces at end
_italic_ or **bold**
indent code by 4 spaces
backtick escapes `like _so_`
quote by placing > at start of line
to make links (use https whenever possible)
<https://example.com>
[example](https://example.com)
<a href="https://example.com">example</a>

formatting help »
answering help »