Broken code formatting in Kindle version
Nadie ha tomado este issue todavía.
Evaluación
- Dificultad
- 4/5
- Tiempo estimado
- 3-5 días
- Aptitud para principiantes
- 25/100
- Tipo de issue
- Error
- Claridad
- Necesita aclaración
- Estado de actividad
- Estancado
- Área
- documentation
Línea de trabajo
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.
Escrito por el modelo de indexación a partir del texto del issue.
Descripción
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:
- Go to https://www.amazon.de/-/en/Scott-Chacon-ebook/dp/B01ISNIKES
- Click on "Buy"
- Open in your Kindle account
- Scroll any any available code formatting
Expected behavior:
Code formatting as in old .mobi versions
Screenshots:
Additional context:
No response
Device
mobile device / e-reader
Operating system
macOS, iOS, Kindle
Browser/application + version
No response
- Lenguaje dominante
- CSS
- Estrellas
- 6.6k
- Forks
- 2.1k
- Métricas de merge de PR
- Sin PR fusionados en 30 d
Guía de contribución
Primeros pasos
- Lee el issue completo y luego la guía de contribución del proyecto.
- Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
- Haz un fork del repositorio y trabaja en una rama.
- Abre un pull request que haga referencia al número del issue.
Más de progit/progit2
-
bug
Dificultad 2/5 1-3 horas Aptitud para principiantes 78/100
-
bug
Dificultad 2/5 1-3 horas Aptitud para principiantes 72/100
-
Semi-stale link for GitHosting Abiertobug
Dificultad 2/5 1-3 horas Aptitud para principiantes 68/100
-
enhancement
Dificultad 1/5 Menos de una hora Aptitud para principiantes 82/100
-
enhancement
Dificultad 1/5 1-3 horas Aptitud para principiantes 65/100
Todos los issues de progit/progit2
Issues similares
-
Dificultad 1/5 Menos de una hora Aptitud para principiantes 95/100
Git-it-App/git-it-electron#1047 ·
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 75/100
neondatabase/website#5944 ·
-
📕documentation
Dificultad 2/5 1-3 horas Aptitud para principiantes 75/100
db-ux-design-system/core-web#8239 ·
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 70/100
libsdl-org/sdlwiki#1008 ·
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 70/100