> I wrote documentation for my packages in Markdown + pandoc + LaTeX. > > The TeX macros contains syntax colorization for Smalltalk code which > can be easily added to Pillar (I suppose) > Would you consider adding the syntax coloring from the TeX macros I sent to > you?
Sure now I'm not a latex expert and I want to keep dependencies to a minimum What you can do is > > I have some silly questions about Pillar: > > The documents can be integrated with toc through pandoc, can this be > done in Pillar? I do not understand what you mean here. > For tables I use tabu, longtable, booktabs, what to use in Pillar? In pillar you have | a column | a column | > For multiple language suppor I use fontspec and lmodern, what to use in > Pillar? I do not know that. And what are the use. In pillar we have utf-8 > For link I use hyperref, what to use in Pillar? * * > I have some chapters ready and I would love to be published in a book, > under the umbrella of Pharo Books: > > https://github.com/hernanmd/Territorial/raw/master/Territorial.pdf > http://biosmalltalk.github.io/web/doc/BioSmalltalk-1.0.pdf > https://github.com/PhyloclassTalk/phyloclasstalk.github.io/raw/master/doc/PhyloclassTalk-1.0.pdf > > What do you think? Good! now I would start simple in plain pillar and avoid as much as possible to use specific latex function and see if this is really a problem and then we can see if we need to extend the latex template or pillar. Pillar is not latex. We want to keep agnostic about latex. > > Cheers > > Hernán > > > 2017-10-29 17:53 GMT-03:00 Stephane Ducasse <stepharo.s...@gmail.com>: >> Hi guys >> >> I just published a new little booklet on Pharo tips and tricks! >> Available at: http://books.pharo.org >> >> Feedback and contributions are welcome as usual. >> >> Stef >> >
