<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
<div class="moz-cite-prefix">A possible idea for the implementation:</div>
<div class="moz-cite-prefix"><br>
</div>
<div class="moz-cite-prefix">Have an EruditeBookFilesSerializer that
converts books to and from disk.</div>
<div class="moz-cite-prefix"><br>
</div>
<div class="moz-cite-prefix">On disk, have a main file with the book
title and sections descriptions, in Smalltalk format.</div>
<div class="moz-cite-prefix"><br>
</div>
<div class="moz-cite-prefix">Let's say, book.st:</div>
<div class="moz-cite-prefix"><br>
</div>
<div class="moz-cite-prefix">EruditeBook new <br>
</div>
<div class="moz-cite-prefix"> title: 'My book';</div>
<div class="moz-cite-prefix"> sections: {'Section1'.</div>
<div class="moz-cite-prefix"> 'Section2' ->
{'Subsection1'. 'Subsection2'}}</div>
<div class="moz-cite-prefix"><br>
</div>
<div class="moz-cite-prefix">Sections and subsections point to files
on disk.<br>
</div>
<div class="moz-cite-prefix">I thought of using yaml for that file,
but Cuis does not have support.</div>
<div class="moz-cite-prefix"><br>
</div>
<div class="moz-cite-prefix">Then, each section and subsection lives
on its own file; they have plain Erudite contents.</div>
<div class="moz-cite-prefix"><br>
</div>
<div class="moz-cite-prefix">Please let me know if you have other
ideas for an implementation.</div>
<div class="moz-cite-prefix"><br>
</div>
<div class="moz-cite-prefix">Cheers,</div>
<div class="moz-cite-prefix"><br>
</div>
<div class="moz-cite-prefix"> Mariano</div>
<div class="moz-cite-prefix"><br>
</div>
<div class="moz-cite-prefix"><br>
</div>
<div class="moz-cite-prefix">El 15/10/22 a las 18:36, Hilaire
Fernandes via Cuis-dev escribió:<br>
</div>
<blockquote type="cite"
cite="mid:e8b199a2-dbc2-78ba-5062-5606f39dc97d@free.fr">
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<p><font size="4">Hi Mariano, <br>
</font></p>
<p><font size="4">Ok I got it.<br>
</font></p>
<p><font size="4">Writing the documentation in Erudite source
format is fine as long as it is not melted with Smalltalk
classes and methods, can be versioned independently,
translated, etc. I don't think then it will be more difficult
to edit than Texinfo. <br>
</font></p>
<p><font size="4">So it only needs to build Erudite book from
erudite source format files.<br>
</font></p>
<p><br>
</p>
<div class="moz-cite-prefix">Le 15/10/2022 à 15:18, Mariano
Montone via Cuis-dev a écrit :<br>
</div>
<blockquote type="cite"
cite="mid:8c30ffe3-6b59-8d4a-5903-62d8f412d25d@gmail.com"><font
size="4">My example was with Markdown, but you would use files
in Erudite source format, not Markdown, for your usecase. Then
you build Erudite books from those files. It is
straightforward. There are no conversions. Only matter: there
are no good external editing tools for those files, that can
give you a preview, etc. But, are there good user-facing
editing tools for TexInfo, for example? Not sure Emacs counts.
So, I think it would be more or less like what you have now
with TexInfo, but you would have Erudite source files instead.
Also, I'm thinking a specialized Erudite editor could be
provided for files in Erudite format, coded in Cuis + Erudite,
if you wanted. </font></blockquote>
<pre class="moz-signature" cols="72">--
GNU Dr. Geo
<a class="moz-txt-link-freetext" href="http://drgeo.eu" moz-do-not-send="true">http://drgeo.eu</a>
<a class="moz-txt-link-freetext" href="http://blog.drgeo.eu" moz-do-not-send="true">http://blog.drgeo.eu</a></pre>
<br>
<fieldset class="moz-mime-attachment-header"></fieldset>
</blockquote>
<p><br>
</p>
</body>
</html>