If you use load_textdomain instead of load_theme_textdomain, you can load as many translations as you wish.<br><br>The point I am trying to address is not that of an end-user benefit (that remains the same), but that of the contributor community. Basically the theme front-end might have a total of 200 translatable strings, but the back-end might go over 2000. In such a case, hoping that a person will translate the entire back-end and make it available is a bit of a stretch. This kind of an approach will let you modularize translations too, so if you have a modular framework, you only load the translation files for the activated modules of a framework.<br>
<br><div class="gmail_quote">On Fri, Oct 12, 2012 at 12:57 PM, Chip Bennett <span dir="ltr"><<a href="mailto:chip@chipbennett.net" target="_blank">chip@chipbennett.net</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Is it even possible for a Theme to register two separate translation textdomains? As far as I knew, it's not possible.<div><br></div><div>Nevertheless, I think this suggestion would only add unnecessary complexity to Theme translation, while providing little benefit in return.</div>
<span class="HOEnZb"><font color="#888888">
<div><br></div></font></span><div><span class="HOEnZb"><font color="#888888">Chip</font></span><br></div></blockquote></div><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>