If you've ever wondered why people say tools like Scribus aren't ready for professional production work let me share this blog post by @davidrevoy
This should be a slam dunk. David knows what he's doing and One Bookshelf provides instructions that clearly show how to produce a PDF to their specifications.
We need to do better, folks. Color Profiles that work for everyone except FOSS tools are unacceptable. Period. There are no excuses for this.
If you want FOSS tools to still be the "I pay for it with my time because my time is meaningless" then we don't need to change a thing. Keep on making it so folks have to play some perverse roulette to ensure that things work with outside printers and publishers.
But if we're ever going to show that we're just as good as the professional tools then we need to start emulating all of the imperfections of those tools. Specs be damned, if everyone else figured it out so can we.
I've seen this with other independent creators where they use Scribus to print their book, only to get a mangled proof back that takes longer to sort out.
You know what they did to solve the problem? Did they file bugs and wait for patches? Nope. They bought InDesign because Scribus lost them over a month's worth of sales and they couldn't afford to keep puttering around with Scribus to make it work.
This seems like a chicken or the egg problem. Programs can never be ready for "production" unless they have been used extensively by demanding users in the industry. Why? Because a developer can't possibly find all of the problems users might encounter when using the software. The man from the blog post you mentioned seems to be very aware of that and is actually motivated to discover bugs and report them so that the developers are able to improve their software. Imo that's great!
Amsterdam based mastodon instance for the Dutch community, but open to anyone. Primary languages Dutch and English.