On 13 Nov 2013, at 20:44, Stéphane Ducasse <[email protected]> wrote:
> > On Nov 13, 2013, at 8:22 PM, Alexandre Bergel <[email protected]> wrote: > >> Why not generating markdown code from pier code? >> If the whole problem is exposure on the web. Someone has considered pdf2html >> or latex2html? > > I did => suicidal tendencies. > The results looks like shit. > > I did not try pdf2html. > > Now pier is a compromise so that normal people can write chapter without > being a latex freaks like us. > > Stef That’s also the thing, md is designed in a (shitty) way so one does not have to “learn” it since it’s is “close” to what one will write in an email Ben > > >> Maybe my question is naive, I do not know. >> >> On some point, i have tried to generate the roassal documentation from the >> Roassal Help, but it makes the maintenance loop heavy: If I want to fix >> something in the text, I had to edit the Help in Pharo, generating the >> document, compiling into .pdf. Quite heavy it was. At the end, I only worked >> on the .tex files. >> >> Alexandre >> >> >> On Nov 13, 2013, at 4:05 PM, Sven Van Caekenberghe <[email protected]> wrote: >> >>> >>> On 13 Nov 2013, at 19:59, Benjamin <[email protected]> >>> wrote: >>> >>>> It was a real question, and it feels like you overreacted the answer … >>>> >>>> To me, markdown or pier is a new syntax to learn so I am asking … >>>> To me, doing Pier because you do or because you said to is no really an >>>> argument. >>>> >>>> Then I am open to a real answer but I also see that markdown is integrated >>>> to a lot of tools (github and jekylls by examples) >>>> and that a lot of people knows about markdown. >>>> >>>> This was a real question, not a troll … >>> >>> I like .md as well and yes, the github integration makes it compelling. >>> >>> But one objective argument against Markdown and in favour of Pier is that >>> the former has no good parser and/or document model and and the latter does >>> have both, in Pharo. That means that we can write all sorts of tools >>> ourselves and get things finished, as was proven with the books. >>> >>> There simply isn’t any definitive, unambiguous Markdown syntax (the github >>> variant is only one version). >>> >>>> Ben >>>> >>>> On 13 Nov 2013, at 19:22, Stéphane Ducasse <[email protected]> >>>> wrote: >>>> >>>>> do you really think that I insist of using pier syntax because >>>>> A- I want to lose my time >>>>> B- this is for my ego? >>>>> C- because I'm funny >>>>> D- ... >>>>> >>>>> No seriously? >>>>> >>>>> If you want to get an answer read the thread that yuri raised a while ago. >>>>> Because we already discussed discussed and discussed it. >>>>> >>>>> I will not write any book in markdown. Now you can try and we see. >>>>> >>>>> Stef >>>>> >>>>>> Stef, what is the advantages of writing it in Pier compared to markdown ? >>>>>> >>>>>> Ben >>>>>> >>>>> >>>>> >>>> >>> >>> >> >> -- >> _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: >> Alexandre Bergel http://www.bergel.eu >> ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. >> >> >> >> > >
