Broken code formatting in Kindle version

Open
#1,984 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
25/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Stale
Domain
documentation

Research direction

Start by comparing the purchased Kindle copy with the latest .mobi version linked from the Release page to determine whether the formatting problem is in the source or the published artifact. Done means code formatting renders correctly in the Kindle version across the reported Kindle and iOS contexts.

Written by the indexing model from the issue text.

Description

bug
There's no existing/similar bug report.
  • I have searched the existing issues
This report is about a single actionable bug.
  • I'm reporting a single actionable bug
This report is about the ProGit book, version 2, English language.
  • This bug is not about a translation or old version
Bug covers book website/pdf
  • I confirm the bug is about the book as found on the website/pdf
Problem is present in the Pro Git book on the website?
  • This bug also affects the Pro Git book as published on the website.
Which version of the book is affected?

I don't know

Describe the bug:

Hi! If you "buy" the Kindle version of the book from Amazon, the copy you receive will have broken code formatting. I’ve attached an example from the iOS Kindle version in the "Screenshot" section.

As far as I know, Kindle uses the mobi format. I checked the latest available mobi version from the "Release" page, and the code formatting looks fine.

Steps to reproduce:
  1. Go to https://www.amazon.de/-/en/Scott-Chacon-ebook/dp/B01ISNIKES
  2. Click on "Buy"
  3. Open in your Kindle account
  4. Scroll any any available code formatting
Expected behavior:

Code formatting as in old .mobi versions

Screenshots:

IMG_1465
Screenshot 2024-10-07 at 21 12 23

Additional context:

No response

Device

mobile device / e-reader

Operating system

macOS, iOS, Kindle

Browser/application + version

No response

Dominant language
CSS
Stars
6.6k
Forks
2.1k
PR merge metrics
No merged PRs in 30d

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from progit/progit2

All issues in progit/progit2

Similar issues

More Documentation issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.