<html>
<head>
<meta content="text/html; charset=utf-8" http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<p><font face="Linux Biolinum O">Hi Philippe,</font></p>
<p><font face="Linux Biolinum O">They are several distinct points in
the answer of Johan, that you are treating as a whole.</font></p>
<p><font face="Linux Biolinum O">My question here was focused on a
single page. While one might disagree with it's conclusion to
not translate this page, I think that the argument – for this
specific page – is reasonable. It's a page targeting translator
of the technews, not its general final readers. An other
argument in favor of such a translation, is that one might
translate not from directly from English, but from an other
already translated version: sure the less you have indirection,
the better, but we might have volunteers out there for who it
might be the only skills they have to offer. An other argument
in favor of such a translation, is that our movement praise
transparency and availability of knowledge in native languages,
this page is (admittedly very small part) of how we organize, so
translating it fall in the intersection of this two goals.<br>
</font></p>
<p><font face="Linux Biolinum O">Now, I think there are two others
important points:</font></p>
<ol>
<li><font face="Linux Biolinum O">Phabricator is in English: that
is clearly something that should be fixed, as it makes the
tool far more difficult to use maybe even unusable for
non-English speakers.<br>
</font></li>
<li><font face="Linux Biolinum O">Wikimedia technical development
is in English: well, that's also problematic, but here it's
more a general global problematic of poor inclusion of
internationalization problems in software development process
in general (that is the internationalization of developers
tools themselves, not the internationalization targeting end
users). It's something for which we might try to foster good
practice, but probably not easily resolve alone.<br>
</font></li>
</ol>
<p><font face="Linux Biolinum O">Cheers,</font></p>
<p><font face="Linux Biolinum O">Mathieu</font><br>
</p>
<br>
<div class="moz-cite-prefix">Le 28/01/2017 à 00:57, Philippe Verdy a
écrit :<br>
</div>
<blockquote
cite="mid:CAGa7JC1H2_+1jiDnYFow_+hgnamp6usMwPBo7D-VafWiYv5bxA@mail.gmail.com"
type="cite">
<div dir="ltr">The Tech News is intended to tech-capable users,
yes, but they are acting as relays/ambassads to explain to other
people, and they will create presentation documents and have a
didactiv activity.
<div>Being able to speak a common language but understandardable
one for everyone is a must for these news that in fract don't
enter in lot of tricky details (and that are in fact read by
more people than what you think, even if they are not
developers). Anyway even if you speak English on this list not
everyone on Meta speak it (otherwise these news would not need
to be transalted at all !)</div>
<div><br>
</div>
<div>And tech developers are not necessarily the best to speak
about how to spek non technical English that are more related
here to the organization itself (when we speak about the
"Board"). Don't be elitist: these news are intended to be read
by the world, including those not reading English. For that
reason we should avoid "jargon" as much as possible (and even
many technical terms have transaltions in MediaWiki because it
is also intended to be used by non-English communities, where
English is also undesirable and very unlikey to be understood
correctly: we are in the area of usability of the software).</div>
<div><br>
</div>
<div>So no, I don't support you too limited POV.</div>
</div>
<div class="gmail_extra"><br>
<div class="gmail_quote">2017-01-27 23:39 GMT+01:00 Johan
Jönsson <span dir="ltr"><<a moz-do-not-send="true"
href="mailto:jjonsson@wikimedia.org" target="_blank">jjonsson@wikimedia.org</a>></span>:<br>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">On Fri,
Jan 27, 2017 at 5:22 PM, mathieu stumpf guntz<br>
<<a moz-do-not-send="true"
href="mailto:psychoslave@culture-libre.org">psychoslave@culture-libre.org</a><wbr>>
wrote:<br>
> Thank you Johan for the notification.<br>
><br>
> By the way, should we make<br>
> <a moz-do-not-send="true"
href="https://meta.wikimedia.org/wiki/Tech/News/For_contributors"
rel="noreferrer" target="_blank">https://meta.wikimedia.org/<wbr>wiki/Tech/News/For_<wbr>contributors</a>
translatable?<br>
<br>
I ask myself that for every page I work on on Meta, but
unfortunately,<br>
if you don't understand that page in English, contributing
to Tech<br>
News will be difficult. Phabricator is in English, Wikimedia
technical<br>
development is in English, the newsletter is in English,
it's<br>
translated from English. Unlike most pages on Meta and
MediaWiki.org,<br>
I don't think the instructions for contributors to Tech News
has an<br>
audience that doesn't speak English.<br>
<br>
//Johan Jönsson<br>
--<br>
<br>
______________________________<wbr>_________________<br>
Translators-l mailing list<br>
<a moz-do-not-send="true"
href="mailto:Translators-l@lists.wikimedia.org">Translators-l@lists.wikimedia.<wbr>org</a><br>
<a moz-do-not-send="true"
href="https://lists.wikimedia.org/mailman/listinfo/translators-l"
rel="noreferrer" target="_blank">https://lists.wikimedia.org/<wbr>mailman/listinfo/translators-l</a><br>
</blockquote>
</div>
<br>
</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
Translators-l mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Translators-l@lists.wikimedia.org">Translators-l@lists.wikimedia.org</a>
<a class="moz-txt-link-freetext" href="https://lists.wikimedia.org/mailman/listinfo/translators-l">https://lists.wikimedia.org/mailman/listinfo/translators-l</a>
</pre>
</blockquote>
<br>
</body>
</html>