Our great sponsors
- SonarLint - Clean code begins in your IDE with SonarLint
- Onboard AI - Learn any GitHub repo in 59 seconds
- InfluxDB - Collect and Analyze Billions of Data Points in Real Time
- Revelo Payroll - Free Global Payroll designed for tech teams
-
You could use pandoc to convert it to a PDF, from which the first page could be extracted (e.g. via pdfseparate(1)) and then converted to an image (e.g. via convert(1)). But perhaps someone else has a more elegant suggestion.
-
Gah, didn't even consider that the OP might have meant the cover image! Probably at least partly because i know that EPUBs don't necessarily need a cover image - i learnt this as a result of learning how to create a minimal EPUB. (And i actually have many EPUBs without a cover image.)
-
SonarLint
Clean code begins in your IDE with SonarLint. Up your coding game and discover issues early. SonarLint is a free plugin that helps you find & fix bugs and security issues from the moment you start writing code. Install from your favorite IDE marketplace today.
-
Standard Ebooks, as part of its mission of creating quality ebooks, ensures that there's an art-based cover image, but from having been on the relevant mailing list for a while, people regularly have challenges finding appropriate art that can be legally used.
-
Perl has traditionally been my language of choice for this sort of stuff (e.g. this script for converting mdBook to LaTeX), but more recently i've been focusing on POSIX shell scripts as a personal challenge and learning exercise.
-
i remember looking at that Google style guide a while back, and not being enthused about it. It's true my style across my POSIX scripts isn't yet entirely consistent, as i'm new to writing POSIX shell scripts, and am still working out what's best for me, as the person who's going to be the primary maintainer. Still, i believe my style to be basically consistent within a given script. Having been programming for a few decades now - although i only started coding-for-pay in the late 90s, starting with Perl - i've developed my own preferences regarding code layout (such as in my ELisp packages, e.g. Ebuku), and nowadays take the approach: I'll follow others' style in others' projects, and will generally try to follow common style standards in my own projects, but will modify them as needed when i find they're not conducive to my work.
-
Onboard AI
Learn any GitHub repo in 59 seconds. Onboard AI learns any GitHub repo in minutes and lets you chat with it to locate functionality, understand different parts, and generate new code. Use it for free at www.getonboard.dev.
