All,<div><br></div><div>Just a quick note: I've added a clarification to the <a href="http://codex.wordpress.org/Theme_Review#Theme_Namespacing">textdomain guideline</a>, as follows:</div><div><br></div><div><blockquote style="margin:0 0 0 40px;border:none;padding:0px">
<div><span style="font-family:sans-serif;font-size:13px;line-height:22px;text-align:left;background-color:rgb(255,255,255)">Themes are </span><b style="text-align:left;font-family:sans-serif;font-size:13px;line-height:22px;background-color:rgb(255,255,255)">required</b><span style="font-family:sans-serif;font-size:13px;line-height:22px;text-align:left;background-color:rgb(255,255,255)"> to use </span><tt style="text-align:left;font-size:13px;line-height:22px;background-color:rgb(255,255,255)">theme-slug</tt><span style="font-family:sans-serif;font-size:13px;line-height:22px;text-align:left;background-color:rgb(255,255,255)"> <font color="#ff0000">(or a reasonable facsimile)</font> as textdomain for translation</span></div>
</blockquote></div><div><br></div><div>The intent of this guideline is to ensure that the Theme textdomain has as little chance as possible to clash with another defined textdomain (i.e. from a Plugin). The idea is to avoid acronyms, abbreviations, or arbitrary terms as Theme textdomains, *not* to require an exact-match between theme-slug and textdomain.</div>
<div><br></div><div>If you have any questions or issues, please ask/discuss them here.</div><div><br></div><div>Thanks!</div><div><br></div><div>Chip</div>