to the publications that stylize headlines and other content in ALL CAPS, but who use `text-transform: uppercase` instead of actually typing the headline in caps: i see you, i appreciate you, i love you
to the publications that stylize headlines and other content in ALL CAPS, but who use `text-transform: uppercase` instead of actually typing the headline in caps: i see you, i appreciate you, i love you 15 comments
@maxfenton @molly0xfff To the ones that go to the trouble of writing a style guide that differentiates between initialisms and acronyms and has sensible rules for both, and then reliably picks the wrong one: Arrrgh! BBC News, I'm looking at you! @molly0xfff You use I use We are not the same. /s @molly0xfff Caught between a rock and a hard place: I usually do this, but then get pushback from localisers that that's not reliable across languages (I believe Turkish is an example where this goes wrong). @molly0xfff for my own learning, what's the reason for wanting that? Is it related to accessibility, reader modes, or something else I'm not considering? @motopascyyy @molly0xfff Separating semantics from formatting. @motopascyyy i personally appreciate it because when i copy/paste a title to use in a reference, i don’t have to go to the trouble of re-titlecasing it. it also can help screenreaders misreading titles as containing acronyms (although apparently some still do this with text-transform), and it also allows sighted people who have difficulty reading all-caps to more easily restore the titles to titlecase using custom stylesheets. |
@molly0xfff To the publications who lowercase all acronym-named organizations and terms, I see you and squint angrily