The use of the theme slug as the textdomain name has been recently discussed in another thread.<br><br>Also to note, the use of an incorrect textdomain may be "minor", but I also consider it to be a significant indicator the theme requires additional review by the theme author before it will be accepted into the Theme repository ... so essentially the theme would be resolved as "not-approved" in these cases. Note, this is generally due to other issues of more relevance than a textdomain oversight as well.<br>
<br>Of course, there may be other issues related to I18n that can be discussed, but I would suggest that be a separate thread to keep all of those points in one place.<br><br><br>Cais.<br><br><div class="gmail_quote">On Fri, Oct 22, 2010 at 4:00 AM, Safirul Alredha <span dir="ltr"><zeo@zeo.my></span> wrote:<br>
<blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">Shouldn't there be a section for i18n in the Theme Review codex page. <div><br></div><div>
I've noticed few theme that's based on x theme didn't bother to change the original x theme textdomain, POT filename and also doesn't generate new POT file. </div>
<div><br></div><div>While this is a minor issue and will not get a theme rejected, but at least theme developer should be aware of it. I think this is part of theme quality.</div><div><br></div><div>zeo</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>