Yes, but the English translations are almost empty. So all strings will fall into that. Not matter how much we optimize it, it doesn&#39;t make sense. <div>I think we should avoid this case as much as we can because ideally #translatedInAllDomains shouldn&#39;t even exist. <div>

IMHO we need to guess the text domain correctly (which doesn&#39;t happen in a lot of cases) and try to complete all the translations.</div><div><br></div><div>Richo<br><br><div class="gmail_quote">On Sun, May 30, 2010 at 6:42 PM, Bert Freudenberg <span dir="ltr">&lt;<a href="mailto:bert@freudenbergs.de">bert@freudenbergs.de</a>&gt;</span> wrote:<br>

<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;"><div class="im">On 30.05.2010, at 21:22, Ricardo Moran wrote:<br>
<br>
&gt; Hi,<br>
&gt;<br>
&gt; I made new versions of po/mo files. These ones have all the english files 100% filled (in almost all the cases the msgstr is the same as the msgid, though). This fixes the problem of sending #translatedInAllDomains for the english locale.<br>


<br>
</div>Not a good idea, IMHO. We have many more incomplete translations than just English. We need to optimize that case, not avoid it.<br>
<br>
- Bert -<br>
<br>
_______________________________________________<br>
etoys-dev mailing list<br>
<a href="mailto:etoys-dev@squeakland.org">etoys-dev@squeakland.org</a><br>
<a href="http://lists.squeakland.org/mailman/listinfo/etoys-dev" target="_blank">http://lists.squeakland.org/mailman/listinfo/etoys-dev</a><br>
</blockquote></div><br></div></div>