Hi Bastien,<br><br>I think this is sad news.<br>You are doing a fantastic and very supportive job Bastien! and I think it would be bad for all the international Blender community that this situation is not solved and we can't progress as fast as we could on our translation efforts.<br>
<br>Perhaps we can explain the importance of your job to the people causing you trouble? <br><br>Best regards,<br>Gabriel<br><br><br><br><div class="gmail_quote">2013/3/28 Bastien Montagne <span dir="ltr"><<a href="mailto:montagne29@wanadoo.fr" target="_blank">montagne29@wanadoo.fr</a>></span><br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hi fellow devs and translators,<br>
<br>
From now on (at least until the situation has be clarified in one way<br>
or the other), I won't be doing any i18n maintenance anymore, as I was<br>
clearly asked by bl_ui (python ui code) owner to not touch this code<br>
anymore for i18n topics. I do not understand this reaction, but this<br>
obviously makes all further work in this matter worthless (you can't<br>
keep enhancing something by being only able to work on half of the<br>
stuff), py ui code is a nest for ambiguous and problematic messages (as<br>
they are usually very short).<br>
<br>
I will obviously keep doing the weekly updates of translation files<br>
(po's), and finish the development of the new py tools, as this at least<br>
won't crush anyone's toes (and yes, I'm aware related docs are outdated,<br>
so have to dedicate some time to those as well).<br>
<br>
Now the core question behind this is: if I have to ask permission to<br>
module owners each time I have to touch their code to fix a translation<br>
issue, I clearly consider this not OK. Chasing those issues already<br>
takes time, if I additionally have to always explain why I do this, and<br>
wait for the answer… just not worth the effort. Put in other words, I<br>
consider i18n a module on its own, for which I think I can claim some<br>
experience after one year and a half and hundreds of hours spent on it.<br>
If it is rather considered as a subset of ui module, I would rather see<br>
its ownership taken back by ui owner, that's all.<br>
<br>
I hope I made my point of view clear, without offending anyone. I just<br>
want the status of i18n to be clarified, so that I can decide whether I<br>
keep working on it, or if I switch to some other, less frustrating and<br>
more funny area of code.<br>
<br>
With best regards,<br>
Bastien Montagne (aka mont29)<br>
_______________________________________________<br>
Remember to *NEVER* commit to our svn's /trunk, but *ALWAYS* to relevant language po file under /branches!<br>
<br>
Found a missing msgid? Edit this doc: <a href="http://goo.gl/XcWcr" target="_blank">http://goo.gl/XcWcr</a><br>
<br>
Have some disambiguation issue (i.e. same english word that should be translated in more than one way, depending on the context)? Edit this doc: <a href="http://goo.gl/VzppJ" target="_blank">http://goo.gl/VzppJ</a><br>
_______________________________________________<br>
Bf-translations-dev mailing list<br>
<a href="mailto:Bf-translations-dev@blender.org">Bf-translations-dev@blender.org</a><br>
<a href="http://lists.blender.org/mailman/listinfo/bf-translations-dev" target="_blank">http://lists.blender.org/mailman/listinfo/bf-translations-dev</a><br>
</blockquote></div><br>