Spartan, what are you doing?
-
@OffByOne said:
The word "case" in that context doesn't mean the same thing as is means in the context I used it in.
What definition are you using then? Because the only definition of "case" on characters I know if is the typographical one...
I confused myself. You're right, I was using the typographical definition in my 'medieval Roman numerals" example.
-
Actual question I hurt my brain answering today: "Does %2f vs %2F matter?"
I'm going to say "no", because an escape sequence isn't an actual character in a filesystem path. If you have put yourself in a situation where it does, its probably your own fault.
ETA: no because of the necro.
-
-
Because the only definition of "case" on characters I know if is the typographical one...
They're the same logical character (i.e., same Unicode codepoint) but different glyphs (i.e., they look different). Hence you're talking about a non-semantic case difference, something that was purely up to the font designer. That's very different to a semantic difference in case, which would be reflected in a different (logical) character being used, even if they were actually rendered using the same glyph (presumably with different affine scaling factors).
This stuff gets brain-bending when you drill down into the details. :)
-
That's just idiotic.
We could ask @wood if he could implement such a thing for links on Discourse.sigh
Fine. Consider it done.