<br><br><div class="gmail_quote">On Tue, Apr 19, 2011 at 11:22 AM, Bert Freudenberg <span dir="ltr"><<a href="mailto:bert@freudenbergs.de" target="_blank">bert@freudenbergs.de</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div style="word-wrap:break-word"><div><div></div><div><div><div>On 19.04.2011, at 14:50, Ricardo Moran wrote:</div><br><blockquote type="cite">On Tue, Apr 19, 2011 at 1:20 AM, Korakurider <span dir="ltr"><<a href="mailto:korakurider@gmail.com" target="_blank">korakurider@gmail.com</a>></span> wrote:<br>
<div class="gmail_quote"><blockquote class="gmail_quote" style="margin-top:0px;margin-right:0px;margin-bottom:0px;margin-left:0.8ex;border-left-width:1px;border-left-color:rgb(204, 204, 204);border-left-style:solid;padding-left:1ex">
Hi.<br>
<div><br>
On Tue, Apr 19, 2011 at 12:22 PM, Ricardo Moran <<a href="mailto:richi.moran@gmail.com" target="_blank">richi.moran@gmail.com</a>> wrote:<br>
> I think it's still useful. I used it to export all translatable strings for<br>
> Physical Etoys (including the Etoys translations). But maybe there is a<br>
> better way that I ignore.<br>
</div> Ah, I see.<br>
<div><br>
> Also, I was thinking about the translation support and I came to the<br>
> conclusion that I really hate the String>>#translatedInAllDomains hack. The<br>
> problem is that I don't know how to fix it so it would find the right domain<br>
> in *all* cases.<br>
</div> I think translation support in Squeak/Etoys have introduced unique<br>
problems and<br>
the hack is reasonable workaround at this time.<br>
<div><br>
> So, here is my idea: what if instead of having a bunch of .mo files, we come<br>
> back to the big etoys.mo file but keeping the .po files divided in domains?<br>
> I mean, the translators would be happy because they'll have all the files<br>
> splitted by domain. And, at the time of compiling, we merge all the po files<br>
> into one huge etoys.po file and just compile that, thus simplifying the<br>
> #translated stuff a lot.<br>
</div> Once split domains, there could be the case that a phrase have<br>
multiple translations.<br>
(Note: ability to have multiple translations might be opportunity )<br>
So I suspect merging translations isn't good change.<br>
<font color="#888888"><br></font></blockquote><div><br></div><div>Yes, there might be multiple translations but they'll depend on the domain being detected properly. Currently, with the #translatedInAllDomains workaround we can't rely on the domain detection so it's kinda worthless, don't you think?</div>
</div></blockquote><br></div></div></div><div>It works pretty well, and we could fix it for the cases where it does not, if needed, me thinks. So I would not call it "worthless".</div><div><br></div><div>Having one .mo per .po seems most straight-forward for everyone to understand. The translatedInAllDomains "hack" is almost invisible. So we would need a very good reason to abandon that. </div>
<br></div></blockquote><div><br></div><div>Yes, it's true. It works and it's very easy to understand. I still think it's pretty ugly, though :)</div><div><br></div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div style="word-wrap:break-word"><font color="#888888"><div>
<span style="border-collapse:separate;border-spacing:0px 0px;color:rgb(0, 0, 0);font-family:Lucida Grande;font-size:12px;font-style:normal;font-variant:normal;font-weight:normal;letter-spacing:normal;line-height:normal;text-align:auto;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px"><div style="font-family:Helvetica">
<span style="font-family:Helvetica">- Bert -</span></div><br></span>
</div>
<br></font></div><br>_______________________________________________<br>
etoys-dev mailing list<br>
<a href="mailto:etoys-dev@squeakland.org" target="_blank">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>
<br></blockquote></div><br>