What is the advantage of two different textdomains? How does it make contributions from others any easier from the developer's point of view?<br><br><div class="gmail_quote">On 12 October 2012 13:04, Sayontan Sinha <span dir="ltr"><<a href="mailto:sayontan@gmail.com" target="_blank">sayontan@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hi,<br>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.<br>
<br>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. <br>
<br>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.<br><br>
Cheers,<br>
Sayontan.<span class="HOEnZb"><font color="#888888"><br clear="all"><br>-- <br>Sayontan Sinha<br><a href="http://mynethome.net" target="_blank">http://mynethome.net</a> | <a href="http://mynethome.net/blog" target="_blank">http://mynethome.net/blog</a><br>
--<br><br>
<br>
</font></span><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>