<div dir="ltr">My personal thought is that it's something so low down on the priority list that if the spelling/capitalization of "WordPress" in Theme text strings is something that we're investing very much time in, we might want to consider our focus.<div>
<br></div><div>*Takes off personal-thought hat*</div><div><br></div><div>I would think that this could be something easily tested/flagged by Theme Check. It's a text string. I'm sure some RegEx guru could come up with a rule to test for the major derivations of "WordPress". (There's probably already one in capital_P_dangit().)</div>
<div><br></div><div>On a related note: the whole "Proudly powered by WordPress" footer credit thing is another good argument for standard template hooks. If Themes implemented standard template hooks, including one for footer credit text, then core could just add a filter callback to add "Proudly powered by WordPress", and Themes wouldn't need to bother with it at all.</div>
<div><br></div><div>*Stops eating the pie in the sky; it's full of carbs anyway*</div></div><div class="gmail_extra"><br><br><div class="gmail_quote">On Thu, Dec 12, 2013 at 2:33 PM, Mario Peshev <span dir="ltr"><<a href="mailto:mario@peshev.net" target="_blank">mario@peshev.net</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">Thanks everyone.<div><br>These were all examples of reviews of already approved themes (by proven authors I would say, not pointing fingers), I was curious how many bad examples are there in the repository already.</div>
<div><br></div><div>If it's considered vital (eventually) a quick search could probably be ran and theme authors notified, as the security searches for plugins happen. I'm not sure how important it is really, is it possible (Otto's territory) and how many authors would update their themes, but just a shot in the dark.<span class="HOEnZb"><font color="#888888"><br>
</font></span><div class="gmail_extra"><span class="HOEnZb"><font color="#888888"><br clear="all"><div><br>Mario Peshev</div></font></span><div><div class="h5"><br><div class="gmail_quote">On Thu, Dec 12, 2013 at 9:14 PM, Emil Uzelac <span dir="ltr"><<a href="mailto:emil@uzelac.me" target="_blank">emil@uzelac.me</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">Direct link: <a href="http://codex.wordpress.org/Theme_Review#WordPress_Trademark" target="_blank">http://codex.wordpress.org/Theme_Review#WordPress_Trademark</a><br>
</div><div><div><div class="gmail_extra"><br><br><div class="gmail_quote">
On Thu, Dec 12, 2013 at 12:51 PM, Edward Caissie <span dir="ltr"><<a href="mailto:edward.caissie@gmail.com" target="_blank">edward.caissie@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div dir="ltr">_capital_P_dangit() really should be all you need (*grin*) ... although I may accept all lowercase in some rare user-case scenarios, just can't think of any.</div><div class="gmail_extra"><span><font color="#888888"><br clear="all">
<div>Edward Caissie<br>aka Cais.</div></font></span><div><div>
<br><br><div class="gmail_quote">On Thu, Dec 12, 2013 at 11:27 AM, Mario Peshev <span dir="ltr"><<a href="mailto:mario@peshev.net" target="_blank">mario@peshev.net</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div dir="ltr">Thanks Tobias, for some reason my search found nothing there - works for me. :)<span><font color="#888888"><br></font></span><div class="gmail_extra"><span><font color="#888888"><br clear="all">
<div><br>Mario Peshev<br><div><br></div></div></font></span><div><div>
<br><br><div class="gmail_quote">On Thu, Dec 12, 2013 at 5:48 PM, Tobias Kerst <span dir="ltr"><<a href="mailto:tobscore@tobscore.com" target="_blank">tobscore@tobscore.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div bgcolor="#FFFFFF" text="#000000">
Hello Mario,<br>
<br>
'Themes must spell "WordPress" correctly in all public facing text:
all one word, with both an uppercase W and P.'<br>
Quoted from this page <a href="http://codex.wordpress.org/Theme_Review" target="_blank">http://codex.wordpress.org/Theme_Review</a><br>
<br>
Sincerely,<br>
<br>
Tobias Kerst<div><div><br>
<br>
<div>On 12.12.2013 16:41, Mario Peshev
wrote:<br>
</div>
</div></div><blockquote type="cite"><div><div>
<div dir="ltr">Hello,
<div><br>
I didn't find any guidelines related to the proper spelling of
WordPress in texts.</div>
<div><br>
</div>
<div>Do we have a general rule of thumb for texts (header,
footer, theme options, theme description) that could lead to
rejection for (I'm so sorry for what I'm about to type)
"Wordpress" or "wordpress" words used and written this way?</div>
<div><br>
</div>
<div>It bothers me a lot, but I'm not sure if that's a
"recommended" or "required" fix.<br clear="all">
<div><br>
Mario Peshev<br>
<div><br>
</div>
</div>
</div>
</div>
<br>
<fieldset></fieldset>
<br>
</div></div><pre>_______________________________________________
theme-reviewers mailing list
<a href="mailto:theme-reviewers@lists.wordpress.org" target="_blank">theme-reviewers@lists.wordpress.org</a>
<a href="http://lists.wordpress.org/mailman/listinfo/theme-reviewers" target="_blank">http://lists.wordpress.org/mailman/listinfo/theme-reviewers</a>
</pre>
</blockquote>
<br>
</div>
<br>_______________________________________________<br>
theme-reviewers mailing list<br>
<a href="mailto:theme-reviewers@lists.wordpress.org" target="_blank">theme-reviewers@lists.wordpress.org</a><br>
<a href="http://lists.wordpress.org/mailman/listinfo/theme-reviewers" target="_blank">http://lists.wordpress.org/mailman/listinfo/theme-reviewers</a><br>
<br></blockquote></div><br></div></div></div></div>
<br>_______________________________________________<br>
theme-reviewers mailing list<br>
<a href="mailto:theme-reviewers@lists.wordpress.org" target="_blank">theme-reviewers@lists.wordpress.org</a><br>
<a href="http://lists.wordpress.org/mailman/listinfo/theme-reviewers" target="_blank">http://lists.wordpress.org/mailman/listinfo/theme-reviewers</a><br>
<br></blockquote></div><br></div></div></div>
<br>_______________________________________________<br>
theme-reviewers mailing list<br>
<a href="mailto:theme-reviewers@lists.wordpress.org" target="_blank">theme-reviewers@lists.wordpress.org</a><br>
<a href="http://lists.wordpress.org/mailman/listinfo/theme-reviewers" target="_blank">http://lists.wordpress.org/mailman/listinfo/theme-reviewers</a><br>
<br></blockquote></div><br></div>
</div></div><br>_______________________________________________<br>
theme-reviewers mailing list<br>
<a href="mailto:theme-reviewers@lists.wordpress.org" target="_blank">theme-reviewers@lists.wordpress.org</a><br>
<a href="http://lists.wordpress.org/mailman/listinfo/theme-reviewers" target="_blank">http://lists.wordpress.org/mailman/listinfo/theme-reviewers</a><br>
<br></blockquote></div><br></div></div></div></div></div>
<br>_______________________________________________<br>
theme-reviewers mailing list<br>
<a href="mailto:theme-reviewers@lists.wordpress.org">theme-reviewers@lists.wordpress.org</a><br>
<a href="http://lists.wordpress.org/mailman/listinfo/theme-reviewers" target="_blank">http://lists.wordpress.org/mailman/listinfo/theme-reviewers</a><br>
<br></blockquote></div><br></div>