<div dir="ltr">+1 for the glossary sharing between projects. This is a very useful feature for translation coherence.<div><br></div><div>If I'm correct, QGIS GUI will be "owned" by Werner only until we are sure that everything works well for the GUI translation. After that it will be transfered for QGIS as well.</div>
<div><br></div><div>Alexandre Neto</div></div><div class="gmail_extra"><br><br><div class="gmail_quote">On Fri, May 30, 2014 at 9:30 AM, matteo <span dir="ltr"><<a href="mailto:matteo.ghetta@gmail.com" target="_blank">matteo.ghetta@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">-----BEGIN PGP SIGNED MESSAGE-----<br>
Hash: SHA1<br>
<br>
Hi guys,<br>
I have some questions about the glossary in trasifex. We already had<br>
this discussion here<br>
<br>
<a href="http://lists.osgeo.org/pipermail/qgis-community-team/2013-November/003361.html" target="_blank">http://lists.osgeo.org/pipermail/qgis-community-team/2013-November/003361.html</a><br>
<br>
but now I would like to explore and better understand this feature.<br>
IMHO, what we need in order to speed up and make more coherent the<br>
translations is the chance to share the glossary between all the<br>
resources.<br>
<br>
In this thread<br>
<br>
<a href="http://support.transifex.com/customer/portal/questions/4158045-import-glossary" target="_blank">http://support.transifex.com/customer/portal/questions/4158045-import-glossary</a><br>
<br>
it is explained that, if the resources belong to the same organization<br>
this **should** be easy. But the synchronization can be done only by<br>
admins.<br>
<br>
But what if the resources belongs to different organizations? I see<br>
that Werner is the owner of the GUI while QGIS is the owner of<br>
Documentation and Website.<br>
<br>
Any idea?<br>
<br>
Cheers<br>
<br>
Matteo<br>
<br>
<br>
<br>
-----BEGIN PGP SIGNATURE-----<br>
Version: GnuPG v1<br>
Comment: Using GnuPG with Icedove - <a href="http://www.enigmail.net/" target="_blank">http://www.enigmail.net/</a><br>
<br>
iQEcBAEBAgAGBQJTiEG0AAoJEBy7UYf0gaEO6zYH/jT6uDH9w0wVXtcZI/dAL2R6<br>
GxVwem3jy9RfavXNvoLdIF86GmKMDOJBgOBA8toHF8Xi5WCMloJlJiOmqFeNRHtW<br>
xVB0gdiGGOOb5jWboSKy6g7VVxdc93NFFNhkfZrQZnXl2dZsifLr5n6oE6912/8r<br>
hbvPxunrZxUZg5EPxhlOIZQ4OMDs+shPikkmzhmPPFMa+AT2T4ZPJD1Pio+MDPaC<br>
NLe+rwKeGu/wA1PK/hK6N0uuxTjU/jWMr3++uCMPVwUjSjsh46IdgDO6QirGXpND<br>
Hr0SFuCNJMJnY10DTs+Ce8q7gcCnv1Cqvxr+sUvw2ATW1DSXYNcrSE4PMvYfqHY=<br>
=Woo1<br>
-----END PGP SIGNATURE-----<br>
_______________________________________________<br>
Qgis-community-team mailing list for organizing community resources such as documentation, translation etc..<br>
<a href="mailto:Qgis-community-team@lists.osgeo.org">Qgis-community-team@lists.osgeo.org</a><br>
<a href="http://lists.osgeo.org/mailman/listinfo/qgis-community-team" target="_blank">http://lists.osgeo.org/mailman/listinfo/qgis-community-team</a><br>
</blockquote></div><br></div>