Skip to content
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

Broken code formatting in Kindle version #1984

Open
3 of 5 tasks
snpefk opened this issue Oct 7, 2024 · 0 comments
Open
3 of 5 tasks

Broken code formatting in Kindle version #1984

snpefk opened this issue Oct 7, 2024 · 0 comments
Labels

Comments

@snpefk
Copy link

snpefk commented Oct 7, 2024

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

@snpefk snpefk added the bug label Oct 7, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant