Skip to content

[book-dp1] Chapter 1 discrepancies between HTML and PDF #26

Description

@Chihiro2000GitHub

Hi @mmcky @jstac

I found a number of places in Chapter 1 that may need attention, so this issue has become quite long.

I would appreciate it if you could take a look when you have time.

Summary

While comparing Chapter 1 of the MyST/HTML version against the PDF, I noticed the following discrepancies and possible rendering issues.

1. Algorithm blocks are not rendered like the PDF

  • PDF: The first two algorithm-style displays in Chapter 1 are not given algorithm numbers. Later, the “Value function iteration for job search” algorithm is numbered as “Algorithm 1.1”.
  • HTML: The first two algorithm-style displays are numbered as “Algorithm 1.1” and “Algorithm 1.2”. As a result, the “Value function iteration for job search” algorithm is numbered as “Algorithm 1.3” instead of “Algorithm 1.1”.
  • Issue: The algorithm numbering differs from the PDF, and this affects numbering parity.

Additional formatting differences:

  • the PDF uses numbered algorithm lines, while the HTML uses bullet points;
  • in the HTML, do is missing from some loop statements such as while ... do and for ... do;
  • the HTML is missing the corresponding end lines;
  • in the first algorithm-style block, the phrase “depends on the current state and action” is rendered as a separate bullet point, although it belongs to the preceding reward step.

2. Distribution symbol differs from the PDF throughout Chapter 1

Image
  • PDF: As shown above, the wage distribution symbol is rendered as \varphi in multiple places throughout Chapter 1.
  • HTML: The corresponding symbol is rendered as \phi in multiple places.
  • Issue: The HTML is internally consistent, but the symbol differs from the PDF across Chapter 1.

3. Figure 1.3 line color differs from the PDF

  • PDF: In Figure 1.3, the line for w_1 + \beta w_1 is shown in a lighter blue. This makes the black dashed value-function line easier to distinguish where the two lines overlap after the kink.
  • HTML: The corresponding line is rendered in a darker blue. As a result, the black dashed line becomes slightly less visible where it overlaps with the blue line.
  • Issue: This is a minor visual difference, but it affects the readability of the figure relative to the PDF.

4. Possible issue with the value-function symbol throughout Chapter 1

  • PDF: In the main text, the value-function symbol generally appears to be v. However, in Figure 1.3, the legend also looks closer to \upsilon_1 than to v_1.
  • HTML: Throughout Chapter 1, the value-function symbols often look closer to \upsilon than to v, including in the main text, equations, and captions.
  • Issue: This may simply be a font/rendering difference, but I wanted to flag it because the intended notation v is not always displayed clearly.

Minor note: In Figure 1.3, the value-function symbol appears similar in both the PDF and HTML versions, and in both cases it looks closer to \upsilon_1 than to v_1.

5. Listing references and captions differ from the PDF

  • PDF: In Section 1.1.1.3, the text refers to “Listing 1.1” (“Parameters and functions underlying the figure are shown in Listing 1.1.”). The corresponding code block is also captioned as “Listing 1.1”.
  • HTML: The corresponding text refers to “Listing 1” instead of “Listing 1.1”. The code block is captioned as “Program 1” rather than “Listing 1.1”.
  • Issue: The numbering and object type differ from the PDF. This creates a mismatch between the PDF and HTML in both the cross-reference text and the code-block caption.

The same issue appears to occur for all listings in Chapter 1. In the PDF, they are numbered as “Listing 1.1” through “Listing 1.6”, while in the HTML the corresponding text references appear as “Listing 1” through “Listing 6” and the code-block captions appear as “Program 1” through “Program 6”.

6. Exercise numbering differs from the PDF throughout Chapter 1

  • PDF: Exercises in Chapter 1 use a three-part numbering scheme, such as “Exercise 1.1.1”.
  • HTML: The corresponding exercises use a shorter numbering scheme, such as “Exercise 1.1”.
  • Issue: Exercise numbering differs systematically from the PDF throughout Chapter 1. This affects numbering parity and may also cause confusion when comparing the PDF and HTML versions.

7. Figure references are rendered as “Figure Figure ...”

  • PDF: In-text references to figures are rendered normally, such as “Figure 1.1” and “Figure 1.2”.
  • HTML: In Chapter 1, the in-text figure references appear to be rendered as “Figure Figure 1.1” and “Figure Figure 1.2”.
  • Issue: The word “Figure” appears twice because the surrounding text already includes “Figure” and the cross-reference itself also renders with “Figure”. This seems to occur throughout Chapter 1 wherever figures are referenced in the main text.

8. Equation numbering no longer matches the PDF after equation (1.4)

  • PDF: Equation numbering matches the HTML up to equation (1.4). After that, many displayed equations are left unnumbered in the PDF. The final numbered equation in Chapter 1 is (1.34).
  • HTML: Equation numbering also matches the PDF up to equation (1.4), but from equation (1.5) onward, many displays that are unnumbered in the PDF receive equation numbers in the HTML. As a result, the final equation number in Chapter 1 is (1.61).
  • Issue: Equation numbering diverges substantially between the PDF and HTML after equation (1.4). This affects numbering parity and may also break or confuse cross-references to equations in Chapter 1.

9. Notation for distribution sets differs from the PDF in multiple places

  • PDF: In Assumption 1.1.1 and Section 1.2.4.3, the distribution-set notation appears as D(W) and D(X). In Assumption 1.1.1, the iid notation also appears in small caps, and the wage distribution symbol is rendered as \varphi.
  • HTML: The corresponding D(W) and D(X) notation uses a visibly different font/style. In Assumption 1.1.1, the IID notation is also rendered differently, and the wage distribution symbol is rendered as \phi.
  • Issue: As I noted in this issue: [book-dp1] Text and rendering discrepancies in Common Symbols table #24 (comment), the rendering of D(...) and the iid notation is not preserved exactly in the MyST/HTML version. This appears in multiple places in Chapter 1, including Assumption 1.1.1 and Section 1.2.4.3. In addition, Assumption 1.1.1 also shows the broader \varphi / \phi discrepancy noted above (2. Distribution symbol differs from the PDF throughout Chapter 1).

10. Appendix reference is rendered as “Appendix §Appendix A”

  • PDF: In Section 1.2.1.1, the appendix reference is rendered as “Appendix §A”.
  • HTML: The corresponding reference is rendered as “Appendix §Appendix A”.
  • Issue: This appears similar to the “Figure Figure ...” issue noted above. The surrounding text already includes “Appendix”, while the cross-reference itself also renders with “Appendix A”. In addition, the position of the section symbol § differs from the PDF.

11. List of norm properties is rendered incorrectly in Section 1.2.1.2

  • PDF: In Section 1.2.1.2, the four properties of a norm are listed as (a), (b), (c), and (d). The corresponding descriptions, such as “nonnegativity” and “positive definiteness,” appear aligned on the right-hand side of the same lines.
  • HTML: The same content is rendered as a numbered list from 1 to 8. In addition, an isolated “2” appears before the list.
  • Issue: The structure of the list is not preserved in the HTML version. The four mathematical properties and their corresponding descriptions are split into separate numbered items, which makes the list harder to read and changes the layout relative to the PDF.

See the attached screenshot for the HTML rendering.

Image

12. Indicator function symbol differs from the PDF

13. Matrix norm properties are numbered differently from the PDF

  • PDF: In Section 1.2.1.4, the matrix norm properties are listed as (a), (b), (c), and (d).
  • HTML: The corresponding properties are rendered as a numbered list from 1 to 4.
  • Issue: The list numbering differs from the PDF. This appears related to the list-formatting issue for norm properties noted above.

14. Theorem titles are missing from some theorem blocks

  • PDF: Some theorems include titles in parentheses. For example, Theorem 1.2.1 is displayed as “Theorem 1.2.1 (Neumann Series Lemma),” and Theorem 1.2.3 is displayed as “Theorem 1.2.3 (Banach’s contraction mapping theorem).”
  • HTML: The corresponding theorem blocks are displayed only as “Theorem 1.2.1” and “Theorem 1.2.3”; the titles in parentheses are missing.
  • Issue: The theorem numbers are preserved, but the theorem titles/names are not carried over to the HTML version.

15. Subitems inside exercises use different numbering from the PDF

  • PDF: In some exercises, subitems are labeled with roman numerals, such as “(i)” and “(ii)”. This appears, for example, in Exercise 1.2.11 and Exercise 1.2.26.
  • HTML: The corresponding subitems are rendered as ordinary numbered lists, such as “1.” and “2.”
  • Issue: This is a minor formatting difference, but I wanted to flag it just in case. The exercise content appears to be the same, but the subitem numbering style differs from the PDF.

16. Labels are missing from Figure 1.9

Image
  • PDF: As shown above, Figure 1.9 labels the four points as u, v, u∨v, u∧v.
  • HTML: The corresponding figure shows the four points, but the labels next to the points are missing.
  • Issue: The figure number and caption appear to be the same, but part of the figure content is missing in the HTML version. This changes the information conveyed by the figure relative to the PDF.

17. Proof heading differs from the PDF

  • PDF: In Section 1.3.1.2, the proof begins with “Proof of Proposition 1.3.1.” There is no separate heading such as “Proof 1.3.1”.
  • HTML: The proof is displayed inside a block headed “Proof 1.3.1”, followed immediately by the text “Proof of Proposition 1.3.1.”
  • Issue: The HTML introduces an additional proof heading that does not appear in the PDF. This makes the proof heading look duplicated. The PDF-style heading “Proof of Proposition 1.3.1” seems to be the relevant heading here.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions