On 5-4-2024 19:48, Niels Dossche wrote:
On 05/04/2024 19:00, Tim Düsterhus wrote:
I've just written up the follow-up RFC to my previous “Casing of acronyms in
class and method names” thread and I'm officially opening up the discussion
period for it.
Please find the following links for your convenience:
RFC: https://wiki.php.net/rfc/class-naming-acronyms
Previous ML discussion: https://externals.io/message/120959#120959
Related discussion in PHP-FIG:
https://github.com/php-fig/per-coding-style/issues/83
Tim,
In the "It decreases readability" section you make a sweeping statement
about accessibility, but don't back that up with research. Please back
your statement up as based on my understanding, the opposite is true.
Case in point: if written in all caps, screenreaders will spell the
characters out - think HTML -. If written in Mixed case, screenreaders
will try to pronounce the word, making acronyms and other abbreviations
very hard to understand for anyone using a screenreader.
This is something which has repeatedly been pointed out, for instance at
conferences regarding conference acronym hashtags, like #DPC.
So, I'd be very interested to see your statement backed up by actual
research and invite you to look into this a little deeper.
I support this proposal.
If accepted, I'll make the necessary changes to ext-dom and ext-xsl to comply
with the new policy.
Niels: just wondering what changes you are referring to ? The RFC
explicitly states "Existing class and method names in released versions
are not affected"... ?
Smile,
Juliette
