The Document Foundation Pushes Back on Euro-Office Hype, Asks for Native ODF

The Document Foundation, the nonprofit behind LibreOffice, has issued a measured response to the pre-announcement of Euro-Office, a proposed European open source office suite that generated a wave of coverage across the European press over the past few days. The Foundation's statement does two things: it corrects a factual claim that crept into the coverage, and it draws a line between two technical postures that often get blurred, supporting a file format versus treating it as native.

Both points are worth separating from the launch-day enthusiasm, because they turn on a distinction that matters a great deal once you look at how documents actually get stored and read back years later.

What was claimed

Several reports described Euro-Office as "the first European open source office suite." The Document Foundation says it cannot find that claim in the actual text of the pre-announcement, and it declines to endorse it. The reasoning is straightforward and checkable: Europe has been producing free and open source office software for years. LibreOffice itself is European in origin, governed by a Berlin-based foundation, and developed by a worldwide community of contributors. It is mature, widely deployed across European public administrations, and far from the only project in the category. The "first" framing, the Foundation suggests, emerged from the speed of a launch day rather than from anything the coalition wrote down.

The Foundation is explicit that it raises this not to claim precedence. Its point is narrower and more useful: accuracy serves the cause of open standards better than enthusiasm does. When a movement built on transparency lets an inaccurate superlative stand, it spends credibility it will want later.

What is actually new

Strip away the "first European" framing and what remains is a coalition committing to improve support for the OpenDocument Format, the ISO-standardized (ISO/IEC 26300) XML-based format that LibreOffice, Apache OpenOffice, and several other suites use. That commitment is what the European free software community has asked for repeatedly, and the Document Foundation takes it in good faith.

The context here is the slow push for digital sovereignty in European public institutions, the idea that a government should not have its records locked inside a format controlled by a single vendor. Schleswig-Holstein's migration to LibreOffice and away from Microsoft products is the most cited example, and the Euro-Office announcement reads as part of that same current.

The Foundation's framing of sovereignty is the part worth holding onto: "sovereignty begins with the format, not with the logo on the application." That sentence does real work. It moves the conversation away from branding, who builds the suite, whose flag is on it, and toward the technical artifact that outlives any particular application: the file on disk.

The distinction the response is built on

Here is the substance of the Foundation's expectation, and it rewards a careful read because the difference is easy to wave past.

A format that is supported is one a suite can read and write as a compatibility courtesy. The application's real internal representation lives somewhere else, and ODF is an import/export target. You have probably seen how this plays out: open a document round-tripped through a non-native format and the formatting drifts, comments get mangled, change-tracking breaks, embedded objects shift. The format works, technically, but it is a second-class citizen, and the fidelity loss accumulates every time a file passes through it.

A native format is the one the application creates, stores, and reads back as its primary representation. Its data model is built around the format rather than translated into it. Nothing is lost on save because there is no translation step to lose anything. For an office suite, native ODF means the documents a public institution produces today remain fully readable, with full fidelity, in any conforming application decades from now, regardless of what happens to the vendor.

That is the line the Document Foundation is drawing. "Improved support is a beginning, not a destination," the statement reads, and "the only destination consistent with the sovereignty Euro-Office invokes is ODF as its native document format." A suite that treats the open standard as a concession to outsiders has not actually escaped the trap that vendor lock-in sets; it has just relabeled it. Real sovereignty, the argument goes, requires the suite to "speak ODF as its mother tongue."

Why the framing holds up

The technical claim survives scrutiny because it maps onto how lock-in actually operates. Lock-in is rarely about an application refusing to open a competitor's files. It is about the slow degradation that happens when your real data model and your storage format disagree. Every save through a non-native format is a small lossy transcoding, and the losses are exactly the features institutions care about, structured metadata, accessibility tagging, revision history.

This is also why the Foundation can credibly welcome the announcement and still ask for more without contradiction. Supporting ODF better is a genuine improvement and worth acknowledging. It is also, by itself, insufficient for the sovereignty goal the project names. Those two statements are consistent, and the response holds them together rather than collapsing into either uncritical praise or dismissal.

The practical test, once Euro-Office moves past pre-announcement into shipping software, will be simple to apply. Watch where the suite stores documents by default, and watch what a complex file looks like after a save-and-reopen cycle with no conversion in between. If ODF is genuinely native, fidelity stays intact and the default save format is ODF without a dialog box nudging users elsewhere. If it is merely supported, the round-trip will tell on it.

The Document Foundation says it looks forward to the moment native ODF arrives and will acknowledge it when it does. That is the right posture for a standards body: encouragement with a clearly stated, technically grounded benchmark, rather than applause for an intention that has not yet been built.