TDF Community Blog

Adhering to these guidelines can enhance productivity and guarantee that documents remain consistent, robust and accessible over time, irrespective of the platform.

Firstly, use an editor such as LibreOffice that natively supports the format without conversion. This preserves the nuances of the ODF XML structure, supports all its features and reduces the risk of formatting issues or data loss. It also ensures that documents are fully compatible with the ISO standard.

Secondly, use an up-to-date version of LibreOffice to benefit from continuous improvements in ODF feature management, avoid bugs that could cause file corruption (a rare event thanks to the robustness of the ODF format, but still possible) and enjoy the highest level of security in file management.

Thirdly, use LibreOffice document templates and styles for all elements, such as headings, fonts, paragraphs, and tables, to ensure consistent formatting throughout the document. This allows you to make global changes quickly by changing the style rather than each individual element, and improves accessibility, as screen readers and other assistive technologies rely on a consistent structure. This also results in smaller, more robust ODF files.

Creating and reusing LibreOffice templates is an excellent practice for companies that produce many similar documents (such as invoices or monthly reports). Once all the characteristics of the document have been defined, simply save it in ‘template’ format to obtain a blank copy with all repetitive elements already in place.

The fourth condition is to save and back up documents frequently and regularly. ODF files are compressed XML files, which makes them robust and reliable, but not immune to problems. In a business environment, it is advisable to use a cloud storage solution with a version history, such as Nextcloud, which allows you to revert to an earlier version of a file.

The fifth recommendation is to avoid overly complex formatting to ensure maximum compatibility when sharing ODF files with a diverse audience or converting them to other formats, such as Microsoft Office proprietary formats, because complicated layouts, embedded objects or macros may not work or appear differently.

It is recommended that you use basic styles and standard LibreOffice fonts (open source and available to all users), or fonts that can be installed by any user, independently of the operating system, even if backed by an End User Licence Agreement (such as Microsoft Aptos, which can only be downloaded from the Microsoft website). You should also avoid excessive use of tables or nested text boxes.

The sixth condition is to integrate multimedia content sensibly, optimising images or videos used in presentations to reduce their size without compromising quality.

The seventh and final condition is to always save the original file in ODF format, even when sharing with users who insist on using Microsoft Office’s proprietary format — thereby handing over ownership of their files to Microsoft. Once the document is finalised, save a copy in OOXML format and share this with Microsoft users.

Similarly, when receiving an OOXML document from a Microsoft user, immediately save a copy in ODF format for editing until the document is finalised and the OOXML copy can be shared again.

When sharing a document within a team, it is advisable to use comments to provide feedback instead of editing the body of the document, enabling change tracking so that changes can be reviewed before acceptance or rejection. Where possible, collaborate on a shared ODF platform based on LibreOffice technology and the cloud, such as Collabora Online.

Open standard formats such as ODF allow you to avoid dependence on a single supplier, maintain ownership and control of your documents, and future-proof your work — but only if used wisely. Following best practices will enable you to manage ODF documents more smoothly and conveniently without sacrificing any of the advantages of the ISO standard format.

ODF ensures that documents remain accessible, portable, and free from restrictions. Now that version 1.3 has been widely adopted and version 1.4 is on the horizon, it’s time to have a look at the new features and upcoming releases.

ODF 1.3: What’s New

ODF 1.3 was finalised in January 2021 by OASIS. It introduced a number of long-awaited improvements, particularly in the areas of security, digital signatures, and document integrity.

1. Digital signatures and document security:

One of the most significant enhancements in ODF 1.3 was the formal specification for digital signatures:

• It now supports XAdES (XML Advanced Electronic Signatures).
• You can sign entire documents, individual parts (e.g. only spreadsheets), or even multiple sections.
• Improved metadata provides information about who signed, when and under what circumstances.

This is a significant development for public administrations and organisations that require reliable document verification.

2. OpenPGP support for encryption

• ODF 1.3 now offers optional OpenPGP-based encryption in addition to the traditional Blowfish method.
• Higher cryptographic standards and better integration with tools such as GnuPG are also included.
• It encourages key-based encryption for personal and business documents.

3. Change management:

• The format now offers greater granularity for change management.
• Supports change tracking in tables, which was previously a weak point.
• Improves compatibility with editing tools that handle collaborative workflows.

4. Metadata:

• Improved management of custom metadata fields using RDF.
• Greater richness of semantic descriptions of content (e.g. for archival or academic purposes).
• Encourages integration with deep graphs and linked data systems.

5. Other changes:

• New chart types and charting features.
• Improved text formatting options.
• Improved compliance with accessibility standards.

ODF 1.3 introduced two new compliance modes: Strict, for clean documents that comply with the specifications, and Extended, which allows specific enhancements by a company for broader feature support.

What’s new in ODF 1.4

ODF 1.4 is still under active development, with the first drafts already implemented in the latest versions of LibreOffice. Although the specifications are not final, the following is planned:

1. Change tracking:

• Support for tracking style changes (e.g. switching from bold to italic).
• Better differentiation between insertions, deletions and formatting changes.
• Change IDs and support for real-time conflict resolution for collaborative editing.

2. Charts:

• More flexibility in charts, including custom colours, gradient fills, multiple axes and formatted data labels.
• Better alignment with modern expectations and improved interoperability with Excel.

3. Accessibility:

• Clearer semantics for assistive technologies.
• Improved navigation for screen readers.
• Structural tags for headings, lists and tables make documents easier to analyse programmatically.

4. Form controls:

• More robust form field types, such as date pickers, drop-down menus and sliders.
• Better interaction support for forms within spreadsheets and presentations.
• Cross-platform consistency.

5. Improved spreadsheet features:

• Native support for named ranges in the sheet.
• Improved formula representation for functions in edge cases.
• More complex conditional formatting rules.

6. Compatibility:

• Mapping of Microsoft Office formats (DOCX, XLSX and PPTX) to reduce conversion issues.
• Improved handling of embedded media and OOXML-style layouts.

Final considerations

ODF 1.3 represented a significant advancement in terms of security and interoperability. ODF 1.4 adds usability improvements, more modern features, and better alignment with current office suite trends.

With an increasing number of governments and organisations adopting open standards, the evolution of ODF is crucial. The focus is not on competing with Microsoft; it’s about ensuring that your documents remain yours.