-
Notifications
You must be signed in to change notification settings - Fork 4
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
RFC - Proposed updated Table of Contents #2
Comments
@dmitrizagidulin Pillar handles LaTeX book parts the same way it handles all other section types. You just have to use
then, you have to map the number of |
@DamienCassou I made a stab at a parts + chapter structure here: 9940083 (if you scroll down to the bottom, there's an image of the rendered ToC). I wasn't able to nest the chapters within the parts directory, since that seemed to break the relative |
@DamienCassou one more question, related. |
Pillar now supports this. Instead of referencing relative links like |
I've never tried that from Pillar. For EnterprisePharo we put the foreword in a LaTeX master file directly. You may try changing the LaTeX Mustache template for this particular file and making sure the pillar file itself does not have any chapter definition (i.e., no line starting with |
I do not understand because I cannot add a comment to the license file. |
@Ducasse - what do you mean, you can't add comment to the license file? And, tell me more, about the book license? I was just going by what it said on the bottom of the book web site, "This book is licensed under a Creative Commons Attribution-Noncommercial-Share Alike 3.0 license." Is that not the actual license? |
@DamienCassou - I'll see if I can figure it out (the nested |
@DamienCassou - I can't seem to get this to work. Here's the start of my chapter latex template: \ifx\wholebook\relax\else
% Lulu:
\documentclass[a4paper,10pt,twoside]{book}
\usepackage[
papersize={6.13in,9.21in},
hmargin={.75in,.75in},
vmargin={.75in,1in},
ignoreheadfoot
]{geometry}
\usepackage{import}
\subimport{root/support/latex/}{common.tex}
\input{../support/latex/common.tex}
\setboolean{lulu}{true} And it gives me something like:
Do I need the line |
Added the existing `.pier` converted chapters into the Introduction chapter. Also, trying out the "parts and chapters" structure as discussed in issue #2 (proposed ToC).
Trying out @DamienCassou's suggestion of using
Here's what the ToC looks like now: This looks OK (although it doesn't quite capture the same chapter numbering as the online book's ToC, that's not a required goal). What I don't like is how it renders Part I as Chapter 2: I suspect this is what Damien meant by "you have to map the number of I'm going to go with the "flat" chapter structure proposed at the start of this discussion, for the moment. |
@cdlm with sbabook, how can we have a paragraph introducing a part? As you can see above, \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. will put the paragraph 2 pages after the page with the "Getting Started" title |
I've created a book with the structure I think you want: https://github.com/DamienCassou/pillar-seaside-book. The result is in the |
Hard to say. If I understood correctly, the default behavior is that part, Of course, the implementation can be hacked, but that is highly dependent On 8 December 2015 at 11:37, Damien Cassou notifications@github.com wrote:
Damien Pollet |
Since the intention is to port the book from its original format to Pillar (which doesn't, as far as I know, support the notion of Parts or Book Sections (a way to group Chapters)), some thought should be put into a slight re-formatting of the table of contents to make it a slightly flatter hierarchy.
I propose the following chapters:
The text was updated successfully, but these errors were encountered: