SquareBracketAssociates/EnterprisePharo#74

Double-digit chapters and sections are a thing with tutorial books, and they get quite close to the border of the page.

• sectioning numbers in the body of the book
• table of contents

Most notably, the chapter headers are broken.

For the text block, a possibility is to keep the same text width as with US trade, and use the space for margin notes.

I have the impression that GentiumBookBasic is old stuff and GentiumPlus is currently recommended: http://software.sil.org/gentium/download/

SquareBracketAssociates/EnterprisePharo#93

If I write

\part{Getting Started}

This part will show you how to get a simple Seaside application up and running in your favourite Smalltalk dialect in less than 15 minutes.

I would like the part title and introductory paragraph to be on the same page

This

\begin{displaycode}{smalltalk}
'Ελλάδα'
\end{displaycode}

renders are

''

Look at the left pane of this screenshot:

We should normally see a list of sections and subsections of this chapter. We only see the chapter title.

This is due to the interaction between microtype and ragged2e, as described here

I have the impression subsubsections should be more visible than description lists, not the opposite. In the example above, the first line is the heading of a subsubsection.

Not enabled by default, maybe even left out of the table of contents…

The macro \hrefnote currently in sbabook.tex can be useful in several places. Could you please move that to sbabook.cls so that EnterprisePharo can make use of it?

The CC BY-SA logo is here for convenience, because that's the license of books by @SquareBracketAssociates. The SBAbook class itself should be considered as software and licensed as such. Creative Commons discourage using their licenses for software, so MIT seems more appropriate.

At the beginning of the Pillar chapter, the first figure appears below the footnote. Is that expected?

The LaTeX code is:

% -*- mode: latex; -*-
\ifx\wholebook\relax\else

    \documentclass[10pt,twoside,english]{root/support/latex/sbabook/sbabook}
  \usepackage{import}
  \subimport{root/support/latex/}{common.tex}

    \begin{document}
\fi



\chapter{Documenting and Presenting with Pillar}
\chapterprecis{Damien Cassou and Cyril Ferlicot Delbecque}

\label{cha:pillar}
This chapter describes Pillar version 2.
\section{Introduction}
\href{http://www.smalltalkhub.com/#!/~Pier/Pillar}{Pillar}\footnote{\url{http://www.smalltalkhub.com/\#!/~Pier/Pillar}} is a markup syntax and associated tools to write and generate documentation, books (such as this one) and slide-based presentations. The Pillar
screenshot below (see Figure \ref{voyageDocExample}) shows the HTML version of chapter \ref{cha:voyage}.


\begin{figure}

\begin{center}
\includegraphics[width=0.3\textwidth]{figures/voyageDocExample-small.png}\caption{An example Pillar output\label{voyageDocExample}}\end{center}
\end{figure}


Pillar has many features:

\begin{itemize}
\item simple markup syntax with references, tables, pictures, captions...);
\item export to HTML, LaTeX, Markdown, AsciiDoc and Pillar itself;
\item export presentations to Beamer and Deck.js;
\item customization of the export through a dedicated \href{http://smalltalkhub.com/#!/~SvenVanCaekenberghe/STON}{STON}\footnote{\url{http://smalltalkhub.com/\#!/~SvenVanCaekenberghe/STON}} configuration file;
\item support of templates using the \href{http://smalltalkhub.com/#!/~NorbertHartl/Mustache}{Mustache}\footnote{\url{http://smalltalkhub.com/\#!/~NorbertHartl/Mustache}} templating engine;
\item syntax-highlighting of generated code blocks (not yet in LaTeX);
\item configurable numbering of section titles and figures;
\item ...
\end{itemize}

This prevents Docker-based builds on home machines. Should work on Travis…

overcolored.sty seems to work fine but it has to be installed separately. The simpler option is simply to add \overfullrule=5mm, for the traditional black marks.

I'd also like to show the text block boudaries, to help decide if a particular overflow is acceptable or not.

…TeXlive 2019 change?

• gitinfo2.sh should check if it's being run within a git repo
• it should take the output file as parameter and not write it unless it's able to (redirecting stdout generates an empty file on failure)

pillar code like
!!! Using ==CMD-b== to browse
is transformed to latext
\subsection{Using \textcode{CMD-b} to browse}

but this can not be compiled, as long as \textcode is defined as
\let\textcode\texttt
whereas
\def\textcode{\texttt}
seems to work
(I don't know much about latex)

.. while Readme says Fira mono

I've counted 96 characters in a longish line…

US trade 6x9", plus 1/8" bleed on all sides