Open bobbingwide opened 5 years ago
Note: If you want to write Wordpress with a lower case p in a WordPress blog and you want it to stay as Wordpress on round robin editing then you can’t use the p
technique.
It works once, then on re-editing gets converted back to a lower case p and Wordpress gets filtered to WordPress.
Solution: type Word<span>p</span>ress
Have you noticed that if you run the
capital_p_dangit
filter function against its own short description it rather changes the meaning of the message?I was writing a post on LinkedIn and noticed this little faut pas in the content embedded for https://core.wp-a2z.org/oik_api/capital_p_dangit/
While it looks OK when you view the page in the browser, it's not OK when embedded by some systems, such as LinkedIn. And it's not OK in the website's search results either.
Explanation
When the
capital_P_dangit
filter function is being run against the post's title the badly spelledWordpress
is corrected. But it rather changes the meaning of the message doesn't it?I don't think we want to eliminate WordPress from the planet, just the misspelling as Wordpress, with a lower case p.
Exceptions?
It's a problem with LinkedIn and WordPress core embed. It seems OK when embedding content into Facebook and Slack.
Local fix
For wp-a2z, the fix is to change the
genesis_a2z_the_title
filter function to detectWordpress
and convert it toWordpress
.Longer term
Should the WordPress core source code be changed to use the HTML representation for lower case p as well? Shall I raise a TRAC?