<html> <head> <meta http-equiv="Content-Type" content="text/html; charset=UTF-8"> </head> <body> Hi Mariono, IMHO, you will make Erudite even much more interesting for Cuis and Cuis application developer by extending its importation capabilities. For example, for DrGeo the user guides are written with Texinfo wich can export to several documentation output formats (html subset, dvi,pdf, docbook, xml, info). The import could be made so that @code fragment will be converted as dynamic media to execute Smalltalk code. Likely more work but it will have a more direct impact. Hilaire <div class="moz-cite-prefix">Le 09/07/2020 à 02:06, Mariano Montone via Cuis-dev a écrit : </div> <blockquote type="cite" cite="mid:21db99dc-1d9e-65c7-0bf7-e4cbdef4db73@gmail.com"> <pre class="moz-quote-pre" wrap="">You could do it the other way around perhaps. Write the book in Erudite and export to Sphinx or HTML. There's a Latex exporter already, and the PDFs result looks quite good IMO. It would not be too hard to generate other exporters. But: I would have to implement better Erudite books persistence to support easier collaborative editing. At the moment books are just stored as a single message that returns a book previously serializaed with #storeOn: . That's very simple, but would be almost impossible to collaborate using that serialized format. I was thinking of serializing an Erudite book to its own class, with a method for each section. The resulting git diffs should be more managable like that I guess. Mariano</pre> </blockquote> <pre class="moz-signature" cols="72">-- GNU Dr. Geo <a class="moz-txt-link-freetext" href="http://drgeo.eu">http://drgeo.eu</a> <a class="moz-txt-link-freetext" href="https://pouet.chapril.org/@hilaire">https://pouet.chapril.org/@hilaire</a></pre> </body> </html>