2016-11-08 9:32 GMT+01:00 Nicolai Hess <nicolaih...@gmail.com>: > > > 2016-11-07 23:47 GMT+01:00 Damien Pollet <damien.pol...@gmail.com>: > >> On 7 November 2016 at 23:03, Nicolai Hess <nicolaih...@gmail.com> wrote: >> >>> I look at the pdf for the update PBE and the references to code example >>> don't >>> work (just show ??, it works for figures). >>> >> >> Could be that the reference or label simply don't match… >> > > But it is the same source that works for the html output. > > >> >> >>> The code in the code example isn't highlight and >>> does't have a dark background (as it is in the html output). >>> >> >> Don't expect PDF and HTML to look the same. >> > > Yes, but the latext template at least looks like the listing for smalltalk > language at least should recognize some syntax words (self/super/...) > > >> Pillar does its job at a semantic level, not at form level. Both have >> their own independent way of styling stuff. For LaTeX it relies on a >> specific document class setup, including some macros to have a layer of >> decoupling between pillar's output and what some packages offer. The >> listing environment you're mentioning is an example; I haven't looked at >> pre-EnterprisePharo books in a while, but it should indeed just be defined >> as an alias to the lstlisting provided by listings.sty. >> > > OK, I 'll check this. > > >> >> BTW I'd recommend migrating the books to the EnterprisePharo layout… but >> that requires being somehow versed in the dark arts of LaTeX and ready to >> spend a couple days checking for problems and matching format conventions… >> > Hm, the Enterprise book does not use named scripts or refer to scripts in the text, I don't know, maybe it doesn't work even there.
> >> -- >> Damien Pollet >> type less, do more [ | ] http://people.untyped.org/damien.pollet >> > >
