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.

Show thread

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.

Show thread

This is why professionals say FOSS tools like Scribus aren't ready for production work. Until it's fire and forget every recommendation of FOSS tools is just someone saying "please use this thing to satiate my religious convictions and pay for it with months of your time and missed income".

The nice ones tell you no.

Show thread

@craigmaloney I think there are a lot FOSS tools out there, that were never intended for "just use".

"Just use" is a concept that has a focus on users and user requests as the programmers behind that usually "write the software for the users" and therefore usually figure out a business model for it.

I think most FOSS projects are "feel free to use" projects, that share a piece of software that solved the problem the authors have/had. The user is not the focus here.


@sheogorath We passed "scratch the itch" a while ago when Scribus added PDF export for x1a and 3. Those have no other purpose other than professional printing. It's an excuse at this point.

@craigmaloney Feel free to correct me if I'm wrong as I'm not part of the community there.

When I see it correctly there is no commercial offering behind the software. There is no "Throw enough money at me and it'll be fixed tomorrow", I don't even see people working on that full-time.

Which again seems to be a funding problem. So I guess either someone steps up and offers some kind of commercial plan which could solve this, or it stays a "scratch my own itches"-kind of project.

@sheogorath I'm looking beyond trying to figure out what the root cause is. I just want it fixed so we can have more interesting conversations about Scribus and FOSS outside of "it's not ready for professional work and here's the receipts".

Telling me why it's not getting fixed is how we stay mired in the problem. Putting some will into getting it fixed is more productive.

@craigmaloney I guess the answer is: In order to get it fixed, send an email to the team members if they would like to offer paid support and how much it would cost to get this fixed ASAP?

In orst case the answer might be "No, no time" then you would extend the request to the rest of the community. If this doesn't work out, the answer is probably either fixing it yourself or hire a freelancer. Sorry when the solution is too boring 🤷

Sign in to participate in the conversation

The social network of the future: No ads, no corporate surveillance, ethical design, and decentralization! Own your data with Mastodon!