[theme-reviewers] Theme Review Codex Page

[Edward Caissie]

The use of the theme slug as the textdomain name has been recently discussed
in another thread.

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.

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.


Cais.

On Fri, Oct 22, 2010 at 4:00 AM, Safirul Alredha <zeo at zeo.my> wrote:

> Shouldn't there be a section for i18n in the Theme Review codex page.
>
> 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.
>
> 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.
>
> zeo
>
> _______________________________________________
> theme-reviewers mailing list
> theme-reviewers at lists.wordpress.org
> http://lists.wordpress.org/mailman/listinfo/theme-reviewers
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.wordpress.org/pipermail/theme-reviewers/attachments/20101022/a1bed5ca/attachment.htm>