<html>
<head>
<meta content="text/html; charset=utf-8" http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<p>Hi Richard,</p>
<p>Further to Niko's comments.</p>
<p>Re chatting:</p>
<p>Our IRC contact details, and weekly meeting time is linked from:
<a class="moz-txt-link-freetext" href="https://wiki.osgeo.org/wiki/Live_GIS_Disc#Contact_Us">https://wiki.osgeo.org/wiki/Live_GIS_Disc#Contact_Us</a> . I am on IRC
now if you are around. Where in the world do you live?<br>
</p>
<br>
Re goals:<br>
We have quite targeted goals for the packages installed on
OSGeo-Live, as outlined here:<br>
<a class="moz-txt-link-freetext" href="https://wiki.osgeo.org/wiki/Live_GIS_Add_Project#What_gets_into_OSGeoLive.3F">https://wiki.osgeo.org/wiki/Live_GIS_Add_Project#What_gets_into_OSGeoLive.3F</a><br>
Basically, we look for stable, established open source geospatial
projects with an active and engaged community, which is small enough
to fit.<br>
We have also specified the content format of Project Overviews and
Quickstarts to be created for OSGeo-Live:<br>
<a class="moz-txt-link-freetext" href="https://wiki.osgeo.org/wiki/Live_GIS_Add_Project#Documentation">https://wiki.osgeo.org/wiki/Live_GIS_Add_Project#Documentation</a><br>
Currently we are using RST format, but would be open to using
something else if there is a good reason to move, and volunteer
support.<br>
<br>
Re sources of documentation:<br>
See <a class="moz-txt-link-freetext" href="https://wiki.osgeo.org/wiki/Live_GIS_Add_Project#Documentation">https://wiki.osgeo.org/wiki/Live_GIS_Add_Project#Documentation</a><br>
<br>
<div class="moz-cite-prefix">On 26/01/2017 7:00 AM, Baka Niko wrote:<br>
</div>
<blockquote
cite="mid:CAMrBSoeVtOwJ5vu0M+wJi200+gvJ53R8=ZoMzBxdWa=-cEARLQ@mail.gmail.com"
type="cite">
<div dir="ltr">
<div>
<div>
<div>
<div>
<div>
<div>
<div>
<div>
<div>
<div>
<div>
<div>
<div>
<div>Hi Richard and the QGIS team,<br>
<br>
</div>
Thank you for holding your hand to us.<br>
<br>
</div>
As you said, the online version is the
latest version. We work on github as
well. [1]<br>
<br>
</div>
The main output is to generate translated
documentation in html pages, and if we
used subervsion and git, we would like to
use transifex.<br>
</div>
The html pages are generated by sphinx from
rst files. Then those pages ar uploaded
online and embedded in the isos we produce.<br>
<br>
</div>
We tried to generate pdf without good result,
but it can be a nice side issue.<br>
<br>
</div>
For the moment, from the folder we were able to
push the files in the "en" folder into
transifex. [2]<br>
</div>
By this, the files get an "en-" prefix, and we
don't know if it is normal.<br>
<br>
</div>
I tried to pull translations in order to produce the
html pages with strange result:<br>
</div>
- first, i get all the translation but, for each
translation images are duplicated, and it is a major
issue, if we want to stay under 4GB (DVD size).<br>
</div>
- then, i wasn't able to pull any translation from
transifex.<br>
<br>
</div>
We suspect that our current folder structure does not fit
well for Transifex but we are not sure. By this, I mean
with the conf.py [3] in the main folder and not in the
"en" folder.<br>
</div>
We don't know where place the "_build" folder either. If
you can look at the structure and give us some advice, we
will be very grateful.<br>
<br>
<br>
</div>
Best regards,<br>
<br>
</div>
Nicolas<br>
<br>
[1] <a moz-do-not-send="true"
href="https://github.com/OSGeo/OSGeoLive-doc">https://github.com/OSGeo/OSGeoLive-doc</a><br>
<br>
[2] <a moz-do-not-send="true"
href="https://www.transifex.com/osgeo/osgeolive/">https://www.transifex.com/osgeo/osgeolive/</a><br>
<br>
[3] <a moz-do-not-send="true"
href="https://github.com/OSGeo/OSGeoLive-doc/blob/master/conf.py">https://github.com/OSGeo/OSGeoLive-doc/blob/master/conf.py</a><br>
<div>
<div>
<div>
<div>
<div>
<div>
<div>
<div>
<div><br>
<br>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
<div class="gmail_extra"><br>
<div class="gmail_quote">2017-01-25 10:00 GMT+01:00 Richard
Duivenvoorde <span dir="ltr"><<a moz-do-not-send="true"
href="mailto:rdmailings@duif.net" target="_blank">rdmailings@duif.net</a>></span>:<br>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">On
24-01-17 10:54, Cameron Shorter wrote:<br>
> Transifex Webtranslation page for QGIS is on<br>
> <a moz-do-not-send="true"
href="https://www.transifex.com/qgis/" rel="noreferrer"
target="_blank">https://www.transifex.com/<wbr>qgis/</a><br>
<span class="">><br>
> Hello qgis translation team,<br>
><br>
> We, the OSGeo-Live [1] team, are blessed to have
scores of active<br>
> translators, who have been translating OSGeo-Live
docs into over 10<br>
> languages. To date, this has been done using
subversion and git, but<br>
> we'd like to do better and move to transifex.<br>
><br>
> Jakob and Niko have been trying hard to set this up
for us but have been<br>
> getting stuck and during our weekly meeting today we
were hopeful that<br>
> some people in the QGIS translation team might have
sufficient<br>
> experience and time to be able to help point us in
the right direction.<br>
><br>
> I'd provide more context, but I'm not sure what
questions to ask. I'm<br>
> hoping someone with Transifex experience can prompt
us by asking us the<br>
> right questions.<br>
<br>
</span>Hi Cameron,<br>
<br>
I'm happy to give a hand with this. Jakob and I already
emailed in<br>
private about this. Maybe it is easier to have a chat about
this?<br>
<br>
Some things I would want to know is the goals you want to
achieve. For<br>
example for qgis-docs we wanted:<br>
<br>
- site to be responsive (to be able to show it on phone or
small help<br>
widget on desktop)<br>
- docs also be able to create as pdf's for printing<br>
- one source (rst)<br>
- ability for a language to have localized images (by having
a separate<br>
resources/images tree directory)<br>
- translation via transifex<br>
- buildable on several OS's (easiest via docker)<br>
- custom template + css/less (shared with/looking as
website)<br>
- automatic pulling of translations and daily building of
docs (and sync<br>
to webserver)<br>
- ...<br>
<br>
Nowadays I would add:<br>
- add md also as source ability (so easy editing in Github,
but to be<br>
able to have indexes you end up with mixed rst/md sources
then)<br>
- images relative (so they are visible in Github, like you
now have)<br>
- stay as close as possible to vanilla Sphinx scripts and
templates<br>
<br>
So: please let me know what it is that osgeo-live wants, and
off course:<br>
every item makes stuff complexer :-)<br>
<br>
This is current build yes? <a moz-do-not-send="true"
href="http://live.osgeo.org/en/index.html"
rel="noreferrer" target="_blank">http://live.osgeo.org/en/<wbr>index.html</a><br>
<br>
Regards,<br>
<br>
Richard Duivenvoorde<br>
<br>
<br>
</blockquote>
</div>
<br>
</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
Live-demo mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Live-demo@lists.osgeo.org">Live-demo@lists.osgeo.org</a>
<a class="moz-txt-link-freetext" href="https://lists.osgeo.org/mailman/listinfo/live-demo">https://lists.osgeo.org/mailman/listinfo/live-demo</a>
<a class="moz-txt-link-freetext" href="http://live.osgeo.org">http://live.osgeo.org</a>
<a class="moz-txt-link-freetext" href="http://wiki.osgeo.org/wiki/Live_GIS_Disc">http://wiki.osgeo.org/wiki/Live_GIS_Disc</a></pre>
</blockquote>
<br>
<pre class="moz-signature" cols="72">--
Cameron Shorter
M +61 419 142 254</pre>
</body>
</html>