Hi, I would go both suggestions of including both support for PetitParser (Esteban's ) and Markdown (Tim's) . Having our own syntax for documentation would make us more insular. In the same way that support for Git is strategical in wider acceptance and visibility (even if we use other DVCS like Fossil with Iceberg) in the coding front, support for Markdown is similar in the documentation front. Pandoc's Markdown has all features for professional book/thesis/article like documents already and Markdown is widely used (like Git) in the code documentation
Cheers, Offray On 11/08/17 15:14, Tim Mackinnon wrote: > If we are considering this, might we take the hard decision to actually > support proper markdown (or even kramdown if we need more control). > > Pillar is a weird variant that isn't like everyone else - so i always have to > think about how to do formatting. > > I know it's not nice, and lots of things are done in pillar - but could we > convert them to be like everyone else? The readme.md that Peter is talking > about is gfm markdown.' > > Tim > > Sent from my iPhone > >> On 11 Aug 2017, at 20:24, Peter Uhnak <i.uh...@gmail.com> wrote: >> >>> On Fri, Aug 11, 2017 at 09:14:01PM +0200, Esteban Lorenzano wrote: >>> >>>> On 11 Aug 2017, at 21:10, Esteban Lorenzano <esteba...@gmail.com> wrote: >>>> >>>> hi, >>>> >>>>> On 11 Aug 2017, at 18:57, Cyril Ferlicot D. <cyril.ferli...@gmail.com >>>>> <mailto:cyril.ferli...@gmail.com>> wrote: >>>>> >>>>> Another step would be to get a minimal parser not relying on >>>>> PetitParser. >>>> Let’s think differently: why not to include a tiny PetitParser? >>>> Then we can think on: >>>> >>>> - pillar sintax (better than just a restricted version) >>> *syntax*… sorry for spanish intromission ;) >>> >>> btw… not just outside the image (as readme). >> Yes, one of the points I want is to have the readme available in Pharo's >> Help Browser with rich content. >> >> Peter >> > >
