<div dir="ltr">Not an easy choice... I'm not very fond of duplicating substitutions images as I believe it will lead to pages with different icons because someone just update one place. Maybe it would be possible to have a common place with all images and some kind of script to copy the icons to a child forder near the rst?<div><br></div><div>Is a third option valid? Since we (you) are making some experiments, how about put all rst files in the same folder? For document I mean. What is the impact on the documents? This would made possible to have a single place for the substitutions?<div><br></div><div>Alexandre</div></div></div><br><div class="gmail_quote"><div dir="ltr">Richard Duivenvoorde <<a href="mailto:richard@duif.net">richard@duif.net</a>> escreveu no dia domingo, 24/01/2016 às 20:59:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hi, as promised I started to move around images in our docs source (only<br>
ONE rst file for now)<br>
<br>
Eg, the dialog screendumps from<br>
<br>
<a href="https://github.com/qgis/QGIS-Documentation/blob/master/source/docs/user_manual/working_with_vector/vector_properties.rst" rel="noreferrer" target="_blank">https://github.com/qgis/QGIS-Documentation/blob/master/source/docs/user_manual/working_with_vector/vector_properties.rst</a><br>
<br>
are now in a local 'images'-directory next to rest. So the :figure:<br>
directives have a relative path to the image in the 'images'-dir.<br>
Meaning that in the link above the screendumps are shown in Github.<br>
<br>
I also removed all little |nix| icon substitutions.<br>
And I removed the :menuselection: and :guilabel: thingies.<br>
<br>
One thing I want to discuss is what to do with the (little) inline<br>
images we have, like the button-images showing up in text.<br>
In rst you can ONLY do inline images apparently by creating<br>
substitutions for them. So there is no other way then to create a<br>
substitution part for these.<br>
<br>
BUT there are two options here:<br>
-1- define them in a central place (like now: conf.py): nice because you<br>
define them only once (theoretically) and no doublures in images, but...<br>
NOT nice: Github is not able to resolve those in conf.py defined<br>
substitutions<br>
-2- define them locally in the rst file where you use them. This has as<br>
drawback that very often used inline images (like the checkbox) are<br>
defined + image copied very often.<br>
BUT the nice thing about it is that IF you define them in the rst file,<br>
Github is able to resolve those SO they show up as inline images their.<br>
<br>
To see the difference, compare:<br>
<br>
<a href="https://github.com/qgis/QGIS-Documentation/blob/master/source/docs/user_manual/working_with_vector/vector_properties.rst#labels-menu" rel="noreferrer" target="_blank">https://github.com/qgis/QGIS-Documentation/blob/master/source/docs/user_manual/working_with_vector/vector_properties.rst#labels-menu</a><br>
<br>
with<br>
<br>
<a href="https://github.com/qgis/QGIS-Documentation/blob/master_github_e/source/docs/user_manual/working_with_vector/vector_properties.rst#labels-menu" rel="noreferrer" target="_blank">https://github.com/qgis/QGIS-Documentation/blob/master_github_e/source/docs/user_manual/working_with_vector/vector_properties.rst#labels-menu</a><br>
<br>
as you can see in the last one I moved (only) the checkbox substitutions<br>
to the rst file and those little checkbox images show up nicely in the<br>
text (compared to the other link where you see |checkbox| everywhere in<br>
the text. IF we move all substitutions in a rst file from the conf.py to<br>
the rst file itself, all the |xxxx| will show nice inline images.<br>
<br>
I also tried a compromise between those two: I move the images to the<br>
static/common folder before build already, and tried to use relative(!)<br>
url's in , but that fails, because apparently the root for those path's<br>
is NOT the position of conf.py, but the place where you USE the<br>
substitution. Meaning we cannot reuse a substitution anymore, and the<br>
whole re-use arguement is useless. NOTE that currently we used non<br>
relative path like /static/common/... !<br>
<br>
If anybody has better insight, please let us know.<br>
<br>
Else: what your preference from the two options above?<br>
I tend to want to see those images in github, making it easier to<br>
read/edit directly there (so option 2). The drawback of duplicates of<br>
subs and images I take for grantage.<br>
<br>
So doc-writers, please raise your hand for one of the options (well.. I<br>
hope it is clear enough to make a choice ....)<br>
<br>
Regards,<br>
<br>
Richard Duivenvoorde<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" target="_blank">Qgis-community-team@lists.osgeo.org</a><br>
<a href="http://lists.osgeo.org/mailman/listinfo/qgis-community-team" rel="noreferrer" target="_blank">http://lists.osgeo.org/mailman/listinfo/qgis-community-team</a></blockquote></div><div dir="ltr">-- <br></div><div dir="ltr"><div>Alexandre Neto</div><div>---------------------</div><div>@AlexNetoGeo</div><div><a href="http://sigsemgrilhetaswordpress.com">http://sigsemgrilhetaswordpress.com</a></div><a href="http://gisunchained.wordpress.com">http://gisunchained.wordpress.com</a><br></div>