Hi everyone,
-
Hi everyone,
If you are using hastags with multiple words, please use camel case.
Not #likethisexample
Why?
A) Screen readers will see a bunch of letters that doesn't make one word and read out each individual letter. Which makes it hard to understand.
B) For us sighted people, it is also easier to read.
Thanks you
@print ah, sorry, I had been originally misinformed that #'s worked best all in lower case.. I will try rewire my behaviour!
-
@print and it avoids issues like #lovescats or #susanalbumparty
-
J jwcph@helvede.net shared this topic
-
Hi everyone,
If you are using hastags with multiple words, please use camel case.
Not #likethisexample
Why?
A) Screen readers will see a bunch of letters that doesn't make one word and read out each individual letter. Which makes it hard to understand.
B) For us sighted people, it is also easier to read.
Thanks you
@print good for instance moderators also to keep in mind, when you're moderating trending hashtags
-
B for me. Camel case pleases my #ConanTheGrammarian instincts as opposed to the #horriblesplurgeoflowercase abominations.
-
medial capitals:
Pascal case = upper camel case
There is also dormadary or lower camel case.
-
@crabby
Wikipedia calls the example as Pascal case or upper camel case.Your example with initial lower case is a example of lower camel case or dromedary case.
I guess we are both correct and I have learnt something.
Either way is better than all lowercase.
Technically it is camelCase and PascalCase, yeah, but:
- CamelCase is pretty self-evident, where PascalCase relies on obscure programming language trivia to even begin making sense.
- It'll require WAY more explanation to understand the difference between camelCase and PascalCase, and even that there is a difference, than getting the point of CamelCase.
- For this CamelCase is actually preferred to camelCase.
- We're discussing ACCESSIBILITY, not programming conventions and history. And making that distinction is about as inaccessible as it gets. 🥴
·
Take this for somebody with quite a pedant vein as well: just say/use CamelCase and forget the mess, being "correct" here is of no use.
Or consider camelCase and CamelCase different words, if it helps.
-
Hi everyone,
If you are using hastags with multiple words, please use camel case.
Not #likethisexample
Why?
A) Screen readers will see a bunch of letters that doesn't make one word and read out each individual letter. Which makes it hard to understand.
B) For us sighted people, it is also easier to read.
Thanks you
@print Thank you, I didn't know that it would make it easier for screenreaders.
-
Technically it is camelCase and PascalCase, yeah, but:
- CamelCase is pretty self-evident, where PascalCase relies on obscure programming language trivia to even begin making sense.
- It'll require WAY more explanation to understand the difference between camelCase and PascalCase, and even that there is a difference, than getting the point of CamelCase.
- For this CamelCase is actually preferred to camelCase.
- We're discussing ACCESSIBILITY, not programming conventions and history. And making that distinction is about as inaccessible as it gets. 🥴
·
Take this for somebody with quite a pedant vein as well: just say/use CamelCase and forget the mess, being "correct" here is of no use.
Or consider camelCase and CamelCase different words, if it helps.
@yenndc @crabby
"The earliest use of the name "Camel Case" occurs in 1995, in a post by Newton Love. "With the advent of programming languages having these sorts of constructs, the humpiness of the style made me call it HumpyCase at first, before I settled on CamelCase. I had been calling it CamelCase for years. ... The citation above was just the first time I had used the name on USENET."[
The term "Pascal Case" was coined in design discussions for the .NET Framework, first released in 2002 -
I've always been a fan of #UpperCamelCase and #lowerCamelCase (with camel case just meaning either one depending on context) since those are way more self evident terms
-
@yenndc @crabby
"The earliest use of the name "Camel Case" occurs in 1995, in a post by Newton Love. "With the advent of programming languages having these sorts of constructs, the humpiness of the style made me call it HumpyCase at first, before I settled on CamelCase. I had been calling it CamelCase for years. ... The citation above was just the first time I had used the name on USENET."[
The term "Pascal Case" was coined in design discussions for the .NET Framework, first released in 2002 -
Hi everyone,
If you are using hastags with multiple words, please use camel case.
Not #likethisexample
Why?
A) Screen readers will see a bunch of letters that doesn't make one word and read out each individual letter. Which makes it hard to understand.
B) For us sighted people, it is also easier to read.
Thanks you
@print Do the tags get listed as different if using caps?
-
Hi everyone,
If you are using hastags with multiple words, please use camel case.
Not #likethisexample
Why?
A) Screen readers will see a bunch of letters that doesn't make one word and read out each individual letter. Which makes it hard to understand.
B) For us sighted people, it is also easier to read.
Thanks you
TIL, thanks for the tip
-
@print but camel case would actually be #likeThisExample
No caps on first letter.
According to Wikipedia,, and the person who invented the term. it is correct.
-
@libewa @print @d1 please don't @ me if I'm wrong, but are these all keyboard issues? #gboardalternative #gboard
-
Hi everyone,
If you are using hastags with multiple words, please use camel case.
Not #likethisexample
Why?
A) Screen readers will see a bunch of letters that doesn't make one word and read out each individual letter. Which makes it hard to understand.
B) For us sighted people, it is also easier to read.
Thanks you
@print@theforkiverse.com Actually I can’t think of anyone who wouldn’t benefit from writing hashtags this way.
-
Hi everyone,
If you are using hastags with multiple words, please use camel case.
Not #likethisexample
Why?
A) Screen readers will see a bunch of letters that doesn't make one word and read out each individual letter. Which makes it hard to understand.
B) For us sighted people, it is also easier to read.
Thanks you
@print Check - I'll (do my best to) remember it.
But gotta admit - I was mostly clicking to see how many Pascal vs. Camel mentions
-
Hi everyone,
If you are using hastags with multiple words, please use camel case.
Not #likethisexample
Why?
A) Screen readers will see a bunch of letters that doesn't make one word and read out each individual letter. Which makes it hard to understand.
B) For us sighted people, it is also easier to read.
Thanks you
@print ... as anyone who remembers getting their software development tips from a site about experts doing sex changes will remember from the Olde Webbe.
-
According to Wikipedia,, and the person who invented the term. it is correct.
@print the case you are using is called PascalCase. True camelCase has the first letter as a lower.
-
@print the case you are using is called PascalCase. True camelCase has the first letter as a lower.
Incorrect.
It is camel case.
In particular upper camel case.
There is upper and lower canel case.
While aome people might call it PascalCase. That term did not enter usage until about 5 years later with .NET documentation.
-
Incorrect.
It is camel case.
In particular upper camel case.
There is upper and lower canel case.
While aome people might call it PascalCase. That term did not enter usage until about 5 years later with .NET documentation.
"The earliest use of the name "Camel Case" occurs in 1995, in a post by Newton Love. "With the advent of programming languages having these sorts of constructs, the humpiness of the style made me call it HumpyCase at first, before I settled on CamelCase. I had been calling it CamelCase for years. ... The citation above was just the first time I had used the name on USENET."[
The term "Pascal Case" was coined in design discussions for the .NET Framework, first released in 2002"
