<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
<font face="Helvetica, Arial, sans-serif">+1</font><br>
<br>
<font face="Helvetica, Arial, sans-serif">Thanks,</font><br>
<font face="Helvetica, Arial, sans-serif">Aurelio Pires</font>
<p><font face="Helvetica, Arial, sans-serif"></font><br>
</p>
<div class="moz-cite-prefix">On 2021-05-05 01:47, Alexandre Neto
wrote:<br>
</div>
<blockquote type="cite"
cite="mid:CA+H0G_GOAxjBGxPHTY_dyzyabL9zRp0wOJgna8KqPweWi8FiCA@mail.gmail.com">
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
<div dir="ltr">
<div>Hello all,</div>
<div><br>
</div>
<div>The glossary feature in Transifex can be a great help for
adding consistency and speed our translations. Nevertheless,
it can also be a curse, when the same term has different
meanings in the destination language, as having a translation
that does not match a glossary term throws a warning message
in the resources list.</div>
<div><br>
</div>
<div>Currently, all translators can change the glossary, which
may end up by losing the consistency, if someone just
disagrees with a translation and decides to change it.<br>
</div>
<div><br>
</div>
<div>For this reason, I would like to propose that we remove the
glossary editing permissions from regular translators, keeping
it editable only by reviewers and administrators. Members of
the translation teams can discuss amongst them the best
translations for each term and decide which term should be in
the glossary. Later an administrator or reviewer can add those
to the glossary without the risk that a newcomer change it
back.</div>
<div><br>
</div>
<div>This goes in line with reviewed strings, which are blocked
for further changes by regular translators.</div>
<div><br>
</div>
<div>Thanks,</div>
<div><br>
</div>
<div>Alexandre Neto<br>
</div>
</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<pre class="moz-quote-pre" wrap="">_______________________________________________
Qgis-community-team mailing list for organizing community resources such as documentation, translation etc..
<a class="moz-txt-link-abbreviated" href="mailto:Qgis-community-team@lists.osgeo.org">Qgis-community-team@lists.osgeo.org</a>
<a class="moz-txt-link-freetext" href="https://lists.osgeo.org/mailman/listinfo/qgis-community-team">https://lists.osgeo.org/mailman/listinfo/qgis-community-team</a>
</pre>
</blockquote>
</body>
</html>