[theme-reviewers] Multiple Translation Domains

[Kirk Wight]

What is the advantage of two different textdomains? How does it make
contributions from others any easier from the developer's point of view?

On 12 October 2012 13:04, Sayontan Sinha <sayontan at gmail.com> wrote:

> Hi,
> There was a recent discussion on the forum regarding the translation-ready
> tag and whether or not back-end translation was needed for the
> translation-ready tag.
>
> In this context I would like to ask if it is okay to include 2 translation
> domains for text. E.g. "my-theme" for texts visible on the front-end and
> "my-theme-admin" for texts visible on the back-end. Obviously, "my-theme"
> is a theme-specific unique slug. The purpose of this split would be to
> account for themes with many options in the back-end. My understanding is
> that a lot of folks rely on volunteers for translation, and from a
> developer's point of view this might help getting the work split up amongst
> contributors. From an end user's point of view this is still transparent
> since only the text domain is being changed.
>
> Only if a theme translates everything (i.e. both "my-theme" and
> "my-theme-admin" are fully translated) that the translation-ready tag gets
> included. That way the review requirement stands.
>
> Cheers,
> Sayontan.
>
> --
> Sayontan Sinha
> http://mynethome.net | http://mynethome.net/blog
> --
>
>
>
> _______________________________________________
> 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/20121012/f568bdf4/attachment.htm>