Liteleaf 0.8-r16 makes moving between source files, review, and PDF more fluid. Since 0.8-r12, the interactive spell checker appears next to the word being reviewed and repositions itself as the editor scrolls or reaches its edges. When a word is added to the project dictionary, every matching underline is removed immediately and then reconciled with the server.
The viewer now includes PDF.js's native text layer. Text can be selected and copied without losing the canvas, zoom, links, or reading position. Inverse synchronization is more accurate as well: a double-click uses the center of the selected word to locate its corresponding source file and position through SyncTeX.
Collaboration is quieter and more efficient. The editor bar now shows only whether the connection is online or offline, while history identifies checkpoints as states of the sources' global revision. When content is already fully synchronized—or an edit produces no net change—the redundant HTTP autosave is no longer sent.
Larger academic projects gained more room too. The default compiled PDF limit
increased from 16 MiB to 64 MiB and can be configured between 1 MiB and
512 MiB. When output exceeds the configured value, the log reports both the
observed size and the limit. Index generation now uses a controlled makeindex
call, including support for the conventional StyleInd.ist, without executing
a project-provided latexmkrc.
Version 0.8-r16 completes this work by fixing persistence for PDFs above the old 16 MiB boundary. PostgreSQL and standalone SQLite now store PDF, SyncTeX, and logs according to the configured limit, remain compatible with older artifacts, and allow previously stuck builds to finish after the automatic migration. Private status and PDF endpoints also no longer cache negative responses.
For account management, changing your own email address takes effect only after confirmation at the new address with a six-digit code or single-use link. The old address remains active until then; afterward, sessions and temporary credentials are revoked without affecting projects, quotas, TOTP, or OIDC identities. Authorized administrators can also correct another account's email while protections for their own account and the primary administrator remain in place.
The standalone profile now offers SMTP password recovery with single-use tokens, expiration, and session revocation after a reset. Version 0.8-r15 brings its experience even closer to PostgreSQL deployments through shared authentication policies, OIDC login, per-user favorites, soft deletion, auditing, retention, collaborative history, and a compilation queue that can rebuild itself after restarts. Embedded Redis coordinates these tasks ephemerally, while SQLite and the file directory remain the durable source of truth and the data required for backups.
Together, revisions 0.8-r11 through 0.8-r16 make writing more precise, remove old limits for extensive work, and make standalone a more complete and predictable option for single-container installations.
← Back to the blog