<div dir="ltr">Like Matteo suggested, I'm pretty sure most Code IDEs will have packages for rST linting (such as putting in the 80 chars of underlining so it shouldn't be that much of a problem.<div><br></div><div>If the goal is to have folks editing in GitHub, those little helpers are not available. So it does play a factor in the barrier to contribution.</div><div><br></div><div>Arguably a trivial one that you learn to work around over time.</div><div><br></div><div>There is no suggestion that we should move away from rST. My comments about AsciiDoc were more of an observation rather than a pitch to migrate. ;)</div><div><br clear="all"><div><div dir="ltr" class="gmail_signature" data-smartmail="gmail_signature"><div dir="ltr"><div><div dir="ltr">Jared Morgan<div>M: +61413005479</div><div><a href="https://plus.google.com/u/0/117309635670089895654/posts/p/pub" target="_blank">Google+</a> | <a href="http://twitter.com/!#/jaredmorgs" target="_blank">Twitter</a> | <a href="http://facebook.com/jaredmorgs" target="_blank">Facebook</a></div><div><br></div><div><br></div></div></div></div></div></div><br></div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Fri, 7 Jun 2019 at 06:17, Cameron Shorter <<a href="mailto:cameron.shorter@gmail.com">cameron.shorter@gmail.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<div bgcolor="#FFFFFF">
<p>Hi Jared,</p>
<p>Last time I checked, a few years back, most of our OSGeo projects
were using RST. So I'd suggest that we should stick with it (at
least for this round).</p>
<p>Long term I suspect/hope someone will write a WYSIWG tool which
allows you to save in whatever wiki or doc format your like (and
transform between formats).</p>
<p>Re heading style, I've seen people use 80 chars of underline for
each heading. It makes the RST format a bit easier to read:<font face="arial, sans-serif"><br>
</font></p>
<p><font face="arial, sans-serif">Chapter 1 Title</font><font face="arial, sans-serif"><br>
</font></p>
<p><font face="arial, sans-serif">========================================================</font></p>
<p><font face="arial, sans-serif">Chapter 1.1 Title</font></p>
<p><font face="arial, sans-serif">--------------------------------------------------------------------------------------------------</font></p>
<p><font face="arial, sans-serif"><br>
</font></p>
<div class="gmail-m_-8362387656489320261moz-cite-prefix">On 6/6/19 6:35 pm, matteo wrote:<br>
</div>
<blockquote type="cite">
<pre class="gmail-m_-8362387656489320261moz-quote-pre">Hi Jared,
</pre>
<blockquote type="cite">
<pre class="gmail-m_-8362387656489320261moz-quote-pre"><a class="gmail-m_-8362387656489320261moz-txt-link-freetext" href="http://docutils.sourceforge.net/docs/user/rst/quickstart.html" target="_blank">http://docutils.sourceforge.net/docs/user/rst/quickstart.html</a> is the
first one and takes the form of an abridged version
of <a class="gmail-m_-8362387656489320261moz-txt-link-freetext" href="http://docutils.sourceforge.net/docs/user/rst/quickref.html#section-structure" target="_blank">http://docutils.sourceforge.net/docs/user/rst/quickref.html#section-structure</a>
Both are recommended by writers who need a quick reminder of syntax.
</pre>
</blockquote>
<pre class="gmail-m_-8362387656489320261moz-quote-pre">thanks for the links.
</pre>
<blockquote type="cite">
<pre class="gmail-m_-8362387656489320261moz-quote-pre">The only thing that grinds my gears about that is that you seem to have
to stuff around with needless decoration to get the headings to display.
Those folks who use writing IDEs like Atom an MS Code, are there good
libraries that take away some of these rough edges?
</pre>
</blockquote>
<pre class="gmail-m_-8362387656489320261moz-quote-pre">I'm using Atom, but years ago I just used gedit to write rst text. One
thing that IMHO is really good in rst (and also markdown) is that the
syntax is quite linear. You just have to be aware of a few steps
(chapter, cross-references, code, links and images).
Having a small cheatsheet on the table solve almost all the problems :)
Matteo
_______________________________________________
SeasonOfDocs mailing list
<a class="gmail-m_-8362387656489320261moz-txt-link-abbreviated" href="mailto:SeasonOfDocs@lists.osgeo.org" target="_blank">SeasonOfDocs@lists.osgeo.org</a>
<a class="gmail-m_-8362387656489320261moz-txt-link-freetext" href="https://lists.osgeo.org/mailman/listinfo/seasonofdocs" target="_blank">https://lists.osgeo.org/mailman/listinfo/seasonofdocs</a>
</pre>
</blockquote>
<pre class="gmail-m_-8362387656489320261moz-signature" cols="72">--
Cameron Shorter
Technology Demystifier
Open Technologies and Geospatial Consultant
M +61 (0) 419 142 254</pre>
</div>
_______________________________________________<br>
SeasonOfDocs mailing list<br>
<a href="mailto:SeasonOfDocs@lists.osgeo.org" target="_blank">SeasonOfDocs@lists.osgeo.org</a><br>
<a href="https://lists.osgeo.org/mailman/listinfo/seasonofdocs" rel="noreferrer" target="_blank">https://lists.osgeo.org/mailman/listinfo/seasonofdocs</a><br>
</blockquote></div>