ElixirOffice 0.6.1 — desktop build 26
Release cut: 2026-10-31. Update metadata must pass owner signing and public verification before publication.
What's new
- PDF export of a Word document with tracked changes now shows the final
revision: deleted text no longer appears in the PDF. - Chinese, Japanese and Korean text in PDF export can use the native
WebAssembly path when the runtime declares the capability, for the safe case
described under known limitations.
Measured against Microsoft Word for the web, the 0.6.1 build was compared page by page on 74 real-world reference documents. 73 of the 74 could be compared (72 in 0.6.0). Page counts, page agreement with Word and changed ink showed no regression against 0.6.0. One document that failed the strict WebAssembly-only PDF check in 0.6.0 now passes it. One document that contains CJK Extension B characters still fails that check. These are measurements on that set of documents, not a claim of full Word compatibility, and no speed improvement is claimed.
AI stays optional and off by default. Sending document context requires your
configured service, consent and explicit request. Documents are not sent to the
publisher.
Qualification
The portable test suite and the Windows packaging test suite each ran 1,365 tests with 1,365 passed and none failed or skipped. The packaged resource audit passed 18,780 resource hashes and licences for the Linux build and for the extracted DEB, and the Windows installer's version resources were checked.
On Apple Silicon macOS, the Darwin unit tests reported 1,365 tests: 1,296 passed, none failed and 69 were skipped. The disk-image audit passed (19,063 application entries). A packaged smoke test passed for six formats: DOCX, XLSX, PPTX, ODT, ODS and ODP.
Not passed and not claimed for this build: the unattended Mac check did not pass (a fonts assertion did not match on the attended Mac), and two native Mac interface checks, Mailings and Avenir Next, were not run. A previous unattended Mac harness failure with SIGKILL (-9), with its source unverified, has not been turned into a pass. Physical native acceptance on Windows, physical printing, downloaded-installer handling, Gatekeeper and Intel Macs were not verified. Existing failed checks remain failed even where a separately documented known limitation is accepted for this release. No all-green suite, native platform acceptance, speed improvement or Office-layout equivalence is claimed.
Installation and updates
Use the package for your operating system and follow the
desktop installation instructions.
Exact download links and checksums accompany the qualified release.
Installers remain publisher-unsigned. macOS packages are arm64-only, ad-hoc
signed and not notarized; Gatekeeper may require the documented manual
approval. Update signatures authenticate update metadata and bytes; they do
not provide an OS publisher certificate. Silent updates are not available.
Known limitations
- The table page-break change was tested on Linux and in Chromium. Its effects
on macOS, Windows and system print dialogs have not been checked separately.
One additional Word reference could not be exported and remains unverified.
The measured page allocations do not certify every table type, vertical
geometry or all documents. - Chinese, Japanese and Korean text in PDF export now uses the native path only
for the safe case (one character at a time, from the basic multilingual
plane). Rare characters such as CJK Extension B, variation sequences and
multi-character clusters still use the JavaScript fallback and can be missing
from the PDF. One document with CJK Extension B still fails the strict
WebAssembly-only PDF check; a fallback is not counted as native success. - Additional footnote-position regression guards remain deferred; the existing
omitted position default remains page-bottom. - Physical printing, downloaded-installer handling, Gatekeeper and all-users
installation require separate native checks. Package construction and source
tests do not certify them. - On Linux hosts that restrict unprivileged user namespaces, the AppImage can
run without Chromium's sandbox. Prefer the DEB on affected systems. - Long-session memory growth, Windows CPU spikes/pauses on lower-end computers,
and the historical forced-cleanup crash remain unresolved. - Display density can affect a spreadsheet's derived noncustom default row
height when saving. Explicit custom heights are a separate case. - Font substitution cannot reproduce every missing typeface or glyph. CJK
coverage is limited to the bundled and available fonts; italic is synthesized. - Existing conversion, PDF, ODF, embedded-object and AI tool limits remain.
Modern LibreOffice 26.8 encrypted ODS is not supported. AI can make mistakes.
Reporting problems
Open an issue with the app
version, operating system, steps and expected/actual behavior. Prefer a small
synthetic reproducer; remove personal information, private content and API keys
before sharing attachments.
Corresponding source contains 17 selected repositories: three newly qualified public snapshots (sdkjs, DocumentServer and the product), two repositories unchanged since 0.6.0 (core and web-apps) and twelve unchanged qualified dependencies. The focused public tests passed: 220 product tests with no failures or skips, and 17 passed with 1 recorded TODO in two new SDK test files. This does not establish a full public-source suite, a clean-machine rebuild or a byte-identical rebuild.
Public product revision: ff532ff.
Source archive: elixiroffice-desktop-source.tar.gz.
Source archive SHA-256: 30a260f03ec778cd1eda30e4ac1fc9b6a6fa4f67e935e98e784b9cb1c6647743.