I think the problem could perhaps be that someone committed directly to trunk and messed up the translation?<br><br>Gabriel<br><br><br><div class="gmail_quote">2011/11/17 Dalai Felinto <span dir="ltr"><<a href="mailto:dfelinto@gmail.com">dfelinto@gmail.com</a>></span><br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">Hi,<br>
<br>
The only problem I can think of is that you either have fuzzy words in<br>
your .po file, or you need to merge it (the .po, not the .mo) with<br>
trunk (and clean the fuzzy after).<br>
<br>
--<br>
Dalai<br>
<br>
2011/11/17 Yain Vieyra <<a href="mailto:yaintech@yahoo.com.ar">yaintech@yahoo.com.ar</a>>:<br>
<div><div class="h5">> Hi,<br>
><br>
> I've found some old and ambiguous stings from the spanish .mo in trunk. I<br>
> don't know exactly what's happening, but when I replace the blender.mo file<br>
> with my own from POEdit, not all changes take effect. I mean, some new<br>
> strings that are added to the po are now visible in the GUI, that's ok, but<br>
> others like "Render" remain the same. In my case, for that word I can see<br>
> "Renderizado" when in my original po that word is "Procesamiento". So, I<br>
> don't know how blender manages that, but in my po that word was never<br>
> "Renderizado". Months ago we had the word "Procesamiento" instead. And I can<br>
> see it in the official release from 2.60.<br>
><br>
> I am using the most neutral and translated file: /branches/es/es.po<br>
> currently at 61% (93% before the major update was done for all pos).<br>
> Reviewing closely the source files I can see that the problematic word comes<br>
> from the file es_MX.po, currently at 4% and apparently stopped. There are<br>
> other strings that comes from es_ES.po as well, currently at 27%, so this<br>
> suggests to me that the blender.mo file from trunk is made of parts of the<br>
> three translations: es.po, es_ES.po and es_MX.po or possibly a bug related<br>
> to how the merge is donde from the branches has caused this trouble. I don't<br>
> know, I am not a developer, but I know that this is not the way to get a<br>
> good quality translation, because some terms are getting ambiguos with time<br>
> and a translator can't fix the bad words because they don't take effect when<br>
> replacing the blender.mo from it's own compilation.<br>
><br>
> If you need to replace the blender.mo file from branches, use the file<br>
> /branches/es/es.po to compile the appropriate .mo. That's the most updated<br>
> one and is neutral, so you can understand it being in Spain, as Argentina or<br>
> Venezuela.<br>
> If there's something I am doing wrong, please tell me. Most translators we<br>
> agree to concentrate the effort in one file, so this has to be established<br>
> some way when merging in trunk.<br>
><br>
> Best Regards.<br>
><br>
</div></div>> _______________________________________________<br>
> Bf-translations-svn mailing list<br>
> <a href="mailto:Bf-translations-svn@blender.org">Bf-translations-svn@blender.org</a><br>
> <a href="http://lists.blender.org/mailman/listinfo/bf-translations-svn" target="_blank">http://lists.blender.org/mailman/listinfo/bf-translations-svn</a><br>
><br>
><br>
_______________________________________________<br>
Bf-translations-svn mailing list<br>
<a href="mailto:Bf-translations-svn@blender.org">Bf-translations-svn@blender.org</a><br>
<a href="http://lists.blender.org/mailman/listinfo/bf-translations-svn" target="_blank">http://lists.blender.org/mailman/listinfo/bf-translations-svn</a><br>
</blockquote></div><br>