Frontmatter

[Sean Fitzpatrick]

One of the things that never got migrated to the PreTeXt version is the preface.

I've just taken care of that (I think).

It will need some updating (mostly by Greg, but maybe any of us can say a bit more about the PreTeXt version) but it's better than nothing.

I also added in the APEX logo provided by Greg on another thread on here.

One concern: in an earlier cleanup commit, Alex took the overall introduction to the book (which had been in the text for the first chapter) and moved it to a preface section in the frontmatter.

That belongs after the preface I've just added, and after the acknowledgements.

Can it remain a preface?

Can we have

<preface>

<acknowledgements>

<preface>?

We will soon find out, I suppose!

No pull request yet, because I wasn't paying attention, and built the branch that it's in off of my branch for changing the indexing in Riemann sums, instead of the main branch. So I will wait until that's merged.

[Rob Beezer]

On 7/13/21 2:07 PM, Sean Fitzpatrick wrote:
> Can we have
> <preface>
> <acknowledgements>
> <preface>?
>
> We will soon find out, I suppose!

I suspect the schema will tell you that is wrong. :-(

> No pull request yet, because I wasn't paying attention, and built the branch
> that it's in off of my branch for changing the indexing in Riemann sums, instead
> of the main branch. So I will wait until that's merged.

Cherry-pick onto a new branch and delete?

http://git-scm.com/book/en/Git-Branching-Rebasing, Figure 39 is what you have?

Every git-astrophe is an opportunity to increase your git-Fu. But first make
copies of relevant files. ;-)

[Sean Fitzpatrick]

Rebasing worked fine :-)

Except afterwards git wouldn't let me push to that branch, since the local was now "behind". I just made a new branch.

Just came across some documentation issues here:

https://pretextbook.org/doc/guide/html/overview-frontmatter.html

1. Documentation uses the American spelling <acknowledgment> but the schema uses the British spelling <acknowledgement> :-)

2. There is no <foreword> element in the schema. But I can find it in pretext-common.xsl, so maybe it is implemented but forgotten in the schema?

3. The documentation does indicate that you can have more than one preface, and it works, but I need the order <acknowledgement><preface><preface>

This changes the ordering from Greg's original (where there was a "Thanks" section at the end of the preface) but I think we should be all right.

[Sean Fitzpatrick]

PS to Rob: I have the correction to the acknowledgement tag done on a branch, but I'll hold off on a PR so I don't end up in the KDC doghouse.

I am not confident that I know how to add the foreword element to the schema.

PS to Alex: every one of the schema validation errors for APEX now comes from either a 'data' or an 'instruction' in a webwork exercise. 

[gregory...@gmail.com]

Just to make sure I'm tracking:

Is Preface 1 (mostly) the Preface from Version 4?

Is Acknowledgements the "Thanks" part of the old Preface?

Is Preface 2 the content that used to appear right before Section 1.1?

If so, could we put Preface 2 at the beginning of Preface 1? I liked having it as part of Chapter 1, but I see that most Chapter intros are short and focused on that chapter, not the book as a whole. 

The preface could have subsections to it, such as 

- What is Calculus? (Use Preface 2)

- How to Read This Text

- APEX (rewritten); combine with something about PreTeXt?

- Changes to V 5.0

[Sean Fitzpatrick]

Yes, Preface 1 is the text/preface.tex file from the APEXCalculusV5 repo, with a bit of tweaking.
Acknowledgements, is the "Thanks", and it is titled as such (so it shows up as "Thanks" in the table of contents).

Preface 2 is the short overview of the development of calculus that used to be at the beginning of Chapter 1.

We can easily change the order of the two prefaces, but I think the acknowledgements have to come before both of them.

The sections are there, but they are "paragraphs". A paragraphs element carries a title, but doesn't get a number, so it's the appropriate division in a preface.

The .tex version had multiple prefaces, depending on which volume they would be in.
I've tried to go with a common preface here.

Some rewriting of the preface would be very welcome.

--
You received this message because you are subscribed to the Google Groups "APEX/Active Calculus MBX conversion" group.
To unsubscribe from this group and stop receiving emails from it, send an email to apexactive-calculus-mbx...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/apexactive-calculus-mbx-conversion/cfbc0e8d-7f11-4837-a451-1c2d4bad7634n%40googlegroups.com.

[Rob Beezer]

Dear Sean,

Thanks for these. But tehre is *no way* I can track these off in all the work
you are doing on APEX.

Can you make three issues on the "mathbook" repository?

Rob

> <http://git-scm.com/book/en/Git-Branching-Rebasing>, Figure 39 is what you

> have?
>
> Every git-astrophe is an opportunity to increase your git-Fu. But first make
> copies of relevant files. ;-)
>

> --
> You received this message because you are subscribed to the Google Groups
> "APEX/Active Calculus MBX conversion" group.
> To unsubscribe from this group and stop receiving emails from it, send an email
> to apexactive-calculus-mbx...@googlegroups.com

> <mailto:apexactive-calculus-mbx...@googlegroups.com>.

> To view this discussion on the web visit

> https://groups.google.com/d/msgid/apexactive-calculus-mbx-conversion/e2978b1c-7483-447b-976a-d8765200d811n%40googlegroups.com
> <https://groups.google.com/d/msgid/apexactive-calculus-mbx-conversion/e2978b1c-7483-447b-976a-d8765200d811n%40googlegroups.com?utm_medium=email&utm_source=footer>.

[Rob Beezer]

On 7/14/21 10:48 AM, Sean Fitzpatrick wrote:

> 3. The documentation does indicate that you can have more than one preface, and
> it works, but I need the order <acknowledgement><preface><preface>

That is what I see in teh schema:

BookFrontMatter = element frontmatter {
MetaDataTitleOptional,
TitlePage?,
ColophonFront?,
Biography*,
Dedication?,
Acknowledgement?,
Preface*
}

and the order may/should be enforced in the XSL.

Why the "but"?

Rob