<div dir="ltr"><br><div class="gmail_extra"><br><br><div class="gmail_quote">On Thu, Apr 11, 2013 at 11:39 PM, Kalpa Welivitigoda <span dir="ltr"><<a href="mailto:callkalpa@gmail.com" target="_blank">callkalpa@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr"><br><div class="gmail_extra"><br><br><div class="gmail_quote">On Fri, Apr 12, 2013 at 1:53 AM, Gonzalo Odiard <span dir="ltr"><<a href="mailto:gonzalo@laptop.org" target="_blank">gonzalo@laptop.org</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr">+10</div></blockquote><div><br></div><div>
Many thanks to Bastein for focusing us all on the topic again.</div><div class="im"><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<div dir="ltr"><div><br></div><div>We need use the easier possible way to write (and translate) the docs.</div><div>I don't know if there are wysiwyg tools to write the XML files for Mallard,</div><div>
if not, is a big step backward.</div><span><font color="#888888"><div><br></div></font></span></div></blockquote><div><br></div></div><div>There is FoieGras [1] which wa also a GSoC project from GNOME in 2008. I have mailed Buddhika [2] who was the GSoC student for that project and he is also from the same university as mine, University of Moratuwa. I'll update with the status of FoieGras once Buddhika replies.</div>
<div><br></div><div>If I may summaries up to now,</div><div><br></div><div>Although the project idea says to implement a help system using Mallard, we can extend it, write help files in plain text and convert them to desired forms (Mallard, html etc) so that we can present them in several possible ways.</div>
<div><br></div><div>Should we output only in Mallard format? I don't see any advantage right now, since we have the capability to expand.</div><div><br></div><div>Since it is plain text, I think it's better to use MarkDown as the markup language. Anyway once I hear from Buddhika, I'll drop a mail to sugar-devel asking developers for their preference in markup language to be used.</div>
<div><br></div><div>[1] <a href="https://live.gnome.org/ProjectMallard/FoieGras" target="_blank">https://live.gnome.org/ProjectMallard/FoieGras</a></div><div>[2] <a href="http://mytechgossips.com/2007/08/24/end-of-a-great-three-months/" target="_blank">http://mytechgossips.com/2007/08/24/end-of-a-great-three-months/</a></div>
<div class="im">
<div><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 dir="ltr"><span><font color="#888888"><div>
</div><div>Gonzalo</div></font></span></div><div class="gmail_extra"><br><br><div class="gmail_quote"><div><div>On Thu, Apr 11, 2013 at 5:19 PM, Bastien <span dir="ltr"><<a href="mailto:bzg@laptop.org" target="_blank">bzg@laptop.org</a>></span> wrote:<br>
</div></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div><div>Hi all,<br>
<br>
translation comes after the docs have been written.<br>
<br>
The main barrier is not dependancies for translation tools,<br>
it's about *writing* documentation.<br>
<br>
Hence the idea of using a plain text light markup language.<br>
<br>
Maybe we could run an informal poll about this in the Sugar<br>
community to get a sense of what current devs are comfortable<br>
with? If they are comfortable with using MarkDown, I'd favor<br>
using this.<br>
<br>
Such feedback would be interesting anyway.<br>
<span><font color="#888888"><br>
--<br>
Bastien<br>
</font></span></div></div><div><div><div>_______________________________________________<br>
Sugar-devel mailing list<br>
<a href="mailto:Sugar-devel@lists.sugarlabs.org" target="_blank">Sugar-devel@lists.sugarlabs.org</a><br>
<a href="http://lists.sugarlabs.org/listinfo/sugar-devel" target="_blank">http://lists.sugarlabs.org/listinfo/sugar-devel</a><br>
</div></div></div></blockquote></div><br></div>
</blockquote></div></div><br><br clear="all"><div class="im"><div><br></div>-- <br>Best Regards,<br><br>Kalpa Welivitigoda<br>Junior Treasurer | Electrical Engineering Society<br>Undergraduate | Department of Electrical Engineering<br>
University of Moratuwa<br>
Sri Lanka<br><a href="http://about.me/callkalpa" target="_blank">http://about.me/callkalpa</a>
</div></div></div>
<br>_______________________________________________<br>
Sugar-devel mailing list<br>
<a href="mailto:Sugar-devel@lists.sugarlabs.org">Sugar-devel@lists.sugarlabs.org</a><br>
<a href="http://lists.sugarlabs.org/listinfo/sugar-devel" target="_blank">http://lists.sugarlabs.org/listinfo/sugar-devel</a><br>
<br></blockquote></div><br></div><div class="gmail_extra">There is perhaps more documentation already written than is generally known about. For example, there are many activities with pages in the wiki [1] and efforts such as [2] done by OLPC deployments. Spanish-language versions abound as well. Coming up with a decent framework which we can populate from these sources would take us a long ways.<br>
<br>[1] <a href="http://wiki.sugarlabs.org/go/Activities#Sugar_Activities">http://wiki.sugarlabs.org/go/Activities#Sugar_Activities</a><br>[2] <a href="http://academy.one-education.org/mod/book/view.php?id=130">http://academy.one-education.org/mod/book/view.php?id=130</a><br>
</div><div class="gmail_extra"><br></div><div class="gmail_extra">regards.<br><br></div><div class="gmail_extra">-walter<br clear="all"></div><div class="gmail_extra"><br>-- <br>Walter Bender<br>Sugar Labs<br><a href="http://www.sugarlabs.org">http://www.sugarlabs.org</a><br>
</div></div>