<div dir="ltr">Hi Kari,<div><br></div><div>First, thanks for helping us translate OSGeoLive !</div><div><br></div><div>I'll try to answer your questions but we will probably need to discuss it with the team, so feel free to join us, your feedback will be very important.</div><div><br></div><div>1. Can you provide an example of that ? It didn't bring to my attention. Usually, I tend to keep the link as it is so I'm sure it'll be working. Some translators adapted the urls some don't, there is no guideline on that subject.</div><div>In the case where there is a translated page, I think the user will be able to get there by himself. It is less maintenance in our side and if the project doesn't have translated pages, the link will send to the English version anyway.</div><div><br></div><div>2. You can possibly make your local documentation, there is some guidelines here: [1] In the past we didn't had Finnish translations so you will need to add it to the configuration. See section <span style="color:rgb(0,0,0);font-family:Arial,Verdana,"Bitstream Vera Sans",Helvetica,sans-serif;font-size:13px;letter-spacing:-0.018em">Adding / removing a language</span></div><div> For the moment, the doc is build separably then introduced in the liveDVD at its building. Unfortunately, I'm not the best person to explain it to you. Please see with Vicky Vergara or Angelos for that matter.</div><div><br></div><div>3. Regarding the licences, the projects included in OSGeoLive keeps their licence. But the documentation for those projects produced for OSGeoLive (aka overviews, quickstarts and notebooks) are required to be in CC BY SA 3.0</div><div>It was not discussed to change the licence yet but as said before, feel free to propose it for discussion.</div><div><br></div><div>4. Short answer is no. We don't have the workforce to do it for the moment, but it can be a great quality improvement if we find the volunteers to do it. Can you please fill an issue in our track instance [2] ?</div><div>I, personally, had troubles with very long strings and paragraphs, so guidelines and a taskforce to enforce it might help.</div><div><br></div><div>5. The meeting are logs in [3], so you can check it easily. You can see the actual state of the documentation here: <a href="https://cvvergara.github.io/OSGeoLive/en/index.html">https://cvvergara.github.io/OSGeoLive/en/index.html</a></div><div> </div><div>To conclude this, this is my personal opinion and we can discuss it, feel free to join us at our weekly meeting every monday at 20:00 UTC</div><div>Plus, if it is a real issue, we have a track instance for issues related to OSGeoLive [2]</div><div><br></div><div>I hope this answers some of your question.</div><div><br></div><div>Best regards,</div><div><br></div><div>Nicolas Roelandt</div><div>OSGeoLive PSC</div><div><br></div><div>[1] <a href="https://trac.osgeo.org/osgeolive/wiki/building_the_docs" target="_blank">https://trac.osgeo.org/osgeolive/wiki/building_the_docs</a></div><div>[2] <a href="https://trac.osgeo.org/osgeolive/" target="_blank">https://trac.osgeo.org/osgeolive/</a></div><div>[3] <a href="http://irclogs.geoapt.com/osgeolive/" target="_blank">http://irclogs.geoapt.com/osgeolive/</a></div><div><br></div></div><br><div class="gmail_quote"><div dir="ltr">Le mar. 21 août 2018 à 15:00, Kari Salovaara <<a href="mailto:kari.salovaara@pp1.inet.fi" target="_blank">kari.salovaara@pp1.inet.fi</a>> a écrit :<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hi folks,<br>
<br>
1. In text (2 be translated) there is also internal links and they, of <br>
course, are language based. As they are at the moment non-existent, <br>
these links be as scientifically best guess?<br>
2. And how and when they could be tested if no new languages are taken <br>
into package as announced earlier? And where are the guidelines if I <br>
want to make a version of the DVD/USB where national translation are <br>
included?<br>
3. Will the licensies of all projects and their documentation be based <br>
on CC 3.0 (from pre-historical time) or will there be a great evoluation <br>
process in near future?<br>
4. Is there any quality assurance for the original texts? Some strings <br>
are more or less in some local dialect which are really painful to <br>
translate.<br>
5. What was the output of OSGeoLive PSC from yesterday and what is the <br>
time line now (looked the doc but no changes)<br>
<br>
Cheers, Kari<br>
<br>
PS. Should OSGeoLive name to be changed to OSGeoLike or OSGeoLove?<br>
<br>
_______________________________________________<br>
osgeolive mailing list<br>
<a href="mailto:osgeolive@lists.osgeo.org" target="_blank">osgeolive@lists.osgeo.org</a><br>
<a href="https://lists.osgeo.org/mailman/listinfo/osgeolive" rel="noreferrer" target="_blank">https://lists.osgeo.org/mailman/listinfo/osgeolive</a><br>
</blockquote></div><br clear="all"><div><br></div>-- <br><div dir="ltr" class="m_-323746241811903819m_-7348750063399372171gmail_signature" data-smartmail="gmail_signature"><div dir="ltr"><div><div><div><div>Bien cordialement,<br><br></div>Nicolas Roelandt<br></div>mail: <a href="mailto:roelandtn.pro@gmail.com" target="_blank">roelandtn.pro@gmail.com</a><br></div>mobile: +33 (0)6 42 40 42 55<br></div>twitter: <span dir="ltr"><a href="https://twitter.com/RoelandtN42" rel="noopener" target="_blank"><span dir="ltr">@<b>RoelandtN42</b></span></a></span> </div></div>