<div dir="ltr"><div>Hi all,</div><div><br></div><div>During the past years, I've reported so many bugs, thanks to all passionate devs, most of them are finally resolved. But when we talked about **i18n bugs**, it always was so awkward for some reason, for years... Last time when we mentioned "i18n project maintanance is on hold", it was really a shock to me, because definitely it was born for a very good reason at the beginning. I know devs got different standpoints on this issue. I can well understand that, just want to share my opinion here:</div><div><br></div><div><div>Language diversity is something about culture, and we cannot force one to totally understand or accept another, and definitely we shouldn't, vise versa. But I believe we could at least try to respect that fact, and realize that English is NOT the one that is spoken by the largest population around the world. True, it is the most popular one, but not the only popular one I should say. And, there are countless people out there, students, designers, artists, FOSS fans, who really want to get involved with Blender (they really should :-)), but a sad thing is, to do that, they will have to learn a second language (English) first! In that case, learning curve becomes horrible. Or, they don't have to, just with the help of a **USEABLE** UI translation. Yeah, the word "useable" should really be stressed, because for them it is either useable or useless. To be truely honest, things now are getting worse, and there's nothing that all passionate translators can do to help their compatriots further, to help propagating Blender further.</div></div><div><br></div><div>As one of the active translation contributors, IMHO, I believe no one touched i18n more than Bastien. So, if he says there is a valid way to fix the horrible ambiguity/polyseme issue (yeah, horrible, because now it causes the UI translation silly enough), I'll totally vote for that idea. I have one faith: If i18n project gets better, then there will be chances for more people to get involved, in their appropriate ways, peer to peer for sure. Finally, vast contributions and donations will go towards Blender Foundation! It is a typical virtuous cycle, a win-win thing benefiting everyone, isn't it?</div><div><br></div><div>An indefinite on-hold doesn't actually help anything to anyone here. As I said, UI translation plays such an important role to Blender that it is either useable or useless. Please, make it useable. :)</div><div><br></div><div>Blenderheads, translators and devs, two years have passed, it's time to face it, share your thoughts on this point.</div><div><br></div></div><div class="gmail_extra"><br><div class="gmail_quote">On Sun, Feb 15, 2015 at 7:27 PM, Bastien Montagne <span dir="ltr"><<a href="mailto:montagne29@wanadoo.fr" target="_blank">montagne29@wanadoo.fr</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hey,<br>
<br>
So, almost two years ago, the 'disambiguation' process of our i18n<br>
messages was freezed<br>
(see<br>
<a href="http://lists.blender.org/pipermail/bf-translations-dev/2013-March/000424.html" target="_blank">http://lists.blender.org/pipermail/bf-translations-dev/2013-March/000424.html</a><br>
for details).<br>
<br>
Since then, people who are translating Blender have been quite<br>
frustrated, because you sometimes<br>
cannot make a valid translation (polysemy, a same english word meaning<br>
different things depending<br>
on contexts).<br>
<br>
We do have a valid way to fix that, called gettext contexts. It’s not<br>
ideal, it’s not perfect, but:<br>
* it is simple<br>
* it works<br>
* it does not need to redesign our whole UI message system!<br>
<br>
One month ago, a TODO task (<a href="https://developer.blender.org/T43295" target="_blank">https://developer.blender.org/T43295</a>) was<br>
created on this subject,<br>
with not much attention from people from UI team so far, so I’m inclined<br>
to just resume adding<br>
needed contexts in code. We cannot wait years for someone to redesign<br>
from scratch our<br>
UI messages system.<br>
<br>
Cheers,<br>
Bastien<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><br clear="all"><div><br></div>-- <br><div class="gmail_signature"><div dir="ltr">Leon Cheung<div>a.k.a. Zhang Yu | 老猫</div></div></div>
</div>