Home » Technology » Page 8

Category: Technology

Interviewing Hypra’s Jean-Philippe Mengual about software accessibility

Accessibility is a key factor for the inclusiveness of digital transformation, but only a few people are really competent in the topic. To learn more about accessibility, we interviewed Hypra’s co-founder, Jean-Philippe Mengual.

Q1. Jean-Philippe, can you tell us about the birth of Hypra?

A1. In 2008 I met Corentin at the Sciences Po higher-learning school in Aix-en-Provence. Through our friendship and the time we spent together studying, he realized how much IT can bring to visually impaired people, but also realized the current limitations.

Together, we understood the revolution it represents: digital technology may erase some inequalities, when one knows how to use it of course. We studied how digital technology can bring equality between visually impaired and sighted people, and then we realized that other people may also benefit from this phenomenon.

We were looking for a solution to this challenge, and we decided to create a computer that was accessible to all, easy to use, adaptable and accompanied by an empowering training.

That is how Hypra was born.

Q2. How challenging is it to work full-time to improve accessibility, and to help seniors and people with disabilities to leverage the opportunities offered by IT?

A2. It is a challenge indeed, and most of us are actually split between several jobs and specialties: psychology, sociology, teaching, but also hacking a distro, patching code, debugging, testing, talking with many communities. The most difficult is to experience regressions and needing of “race” after the accessibility regression to ensure a good end-user experience. And either the upstream project is reactive with our bug reports and/or patches, or it is not, so it may become disappointing.

However, working with people who, because of age or disabilities, are reluctant to use a computer, has allowed us to come to the conclusion that anyone can learn to use a computer fully autonomously, no matter your situation their age, as long as they are well supported at the beginning.

When we see such people progress and succeed, we realize that all of our work is worthwhile.

Q3. How far is free and open source software from offering true accessibility?

A3. Since I started with FOSS in the 2000s, I have seen a lot of real improvements. I, for one, am now able to only use free open source software in my daily activities, with a nice graphical interface.

However, I think reaching actual feature parity would allow users to be fully autonomous with FOSS. At the top of my mind, all features regarding speech synthesis (text to speech) and voice recognition (speech to text) are not quite up to what is achievable with proprietary software. It is the same for OCR (optical character recognition).

Another important dimension is the durability of software environments. Indeed, some programs that used to be perfectly accessible may cease to be so, from one day to another. This may be because some crucial contributors have abandoned that particular project, or it may be due to an update in which accessibility has been put on the back burner.

Q4. Hypra provides hardware solutions both for seniors and for people with disabilities. Can you tell us about these products, and about the software?

A4. We rely on Debian GNU/Linux for our products. We chose it because of its stability and careful update pace, which allows us to guarantee optimal use for our customers including our own layer of customizations in good conditions.

We mainly use free and open source software on our computers. To enable individual support, we provide Mumble, VNC to take control of the system remotely, and we use SSH for maintenance.

Regarding the tools for our visually impaired customers, we have chosen the Orca screen reader and Compiz for visual filters, rely on the MATE desktop (great for its full flexibility from a user point of view). Alongside with the computers, we provide scanners which, together with the screen reader, turn your laptop into a reading machine.

Generally speaking, the fact we produce only free code and use mainly free software enables us to sell, for a standard price, hardware with a high service level.

Q5. Hypra is working with enterprises to integrate people with disabilities in business environments. How difficult is this task?

A5. It’s important to know that the first task when adapting a workstation is to reassure both the user and their company. They have to be reassured that the equipment is compatible with the work environment already in place and that we’ll be there to support them.

In fact, the highest challenge is the diversity of the infrastructures: many solutions, more and more remote, few free software in the workstation (which is not always accessible, by the way, under Windows). It depends on the size of the organization and the flexibility possible in respect with the IT teams and the security needs of the company. The good news comes when the clients are web interfaces, even if some improvements are needed to make everything accessible. But a web interface is potentially easier to make accessible than software, because it is governed by standards, while software is based on various toolkits, not always compatible with any accessibility solution – in particular remotely.

Q6. What kind of integration have you done with LibreOffice?

A6. We only use vanilla LibreOffice versions. We’re generally very happy with these, except for certain aspects such as the stability of certain versions or occasional accessibility regressions in LibreOffice.

As far as Orca users are concerned, we’ve chosen to use an older LibreOffice build, version 4.2, as it gives us full satisfaction – which also applies to all low vision software.

However, we have noticed that accessibility is becoming more and more present in LibreOffice’s development in the recent years; we’re speculating that from version 8.x onwards we’ll hopefully be able to migrate all users to a more recent version.

On our end, we plan to systematize regression testing of the master branch in order to get more actively involved in the development process. This will also allow us to alert contributors immediately if a specific proposed change affects accessibility.

We also want to provide use cases to the community, so that each of its members can concretely test what a user with specific needs expects from the program in their daily use.

Tender to implement support for editing and creation of a Dynamic Diagram feature (#202108-02)

The Document Foundation (TDF) is the charitable entity behind the world’s leading free/libre open source (FLOSS) office suite LibreOffice.

We are looking for an individual or company to implement support for editing and creation of Dynamic Diagrams.

The work has to be developed on LibreOffice master, so that it will be released in the next major version.

The task is to solve the following problem: Our existing “SmartArt” import uses the fallback stream in OOX files (and has some issues). It therefore gives us only the draw shapes that are imported, so we lose the original layout. Additionally, in older file versions we don’t have the cached shapes, and therefore can’t render anything.

The solution we seek, and as such the scope of this tender, is to have a schema driven diagram layout as a core feature. This should be interoperable with OOX (at least MSO2016) and have suitable extensions for ODF. It should layout interoperability, and allow editing of the underlying data, and selection of a schema.

The tender consists of the packages

A) Import and export in ODF and OOXML

  • load/save diagram data (layout and data model)
  • show the diagram in a cross-platform and pixel-perfect way
  • this should solve the issues from tdf#106547
  • provide automated test for the diagram layout mechanism

B) Creation of new diagrams within all modules, at least Writer and Draw/Impress

    • the solution should provide a couple of exemplary layouts such as a hierarchy with rectangle for organizational charts, for example, and linear as well circular arrangements of shapes to illustrate processes
    • values should be entered by the user with a floating widget presenting a bullet list that describes the hierarchical position

  • consider accessibility at all UI parts

C) Modification of existing diagrams

  • It must be possible to modify the data model later and add or delete content to the diagram; ideally, the floating input widget opens when the diagram is selected

D) Sharing of diagram layouts via extensions

  • Diagrams are generated from complex XML layouts, which should be provided and shared by the community

E) Document the Dynamic Diagram feature

and optionally

F) Provision of an interactive diagram layout tool

  • In coordination with the UX/design team an user interface should be implemented that simplifies creation of XML layouts

The following two bugs are amongst the relevant ones for this tender:

Support for Editing and Creation of SmartArt: https://bugs.documentfoundation.org/show_bug.cgi?id=37932

Auto-Layout for flowcharts and automatic flowcharts from Calc / Excel: https://bugs.documentfoundation.org/show_bug.cgi?id=92902

Further information can also be found in these two blogposts:

Note: There was recent effort on the layouting side. While this is better than 2-3 years ago, it still requires much work. Especially the editing functionality is just a proof of concept.

All technology standards of relevance, as well as their targeted versions for this tender should be declared or defined in the offer’s description of implementation (e.g. name and version of the cryptographic API on the respective operating systems).

A key item of the deliverables for this tender, and therefore also a decision criteria – besides qualification, references, price, and completeness of fulfilment – is extensive documentation about the approach chosen to implement the above items, covering more than just the pure implementation. We expect bidders to provide documentation on both the code and the non-code parts of this tender, e.g. methodology, structure and technical aspects. The Document Foundation will publish this under a free and open source license and make it available to the general public. Another criteria for the evaluation of the bids will be the description of the required test activities and the delivery of (automated) tests supporting work items for the described tender implementation or feature specification.

Required skills

  • Extensive knowledge of C++
  • Experience working on the LibreOffice source code

Other skills

  • English (conversationally fluent in order to coordinate and plan with members of TDF)

We use free, libre and open source (FLOSS) software for development wherever possible, and the resulting work must be licensed under the Mozilla Public License v2.0.

TDF welcomes applications from all suitably qualified persons regardless of their race, sex, disability, religion/belief, sexual orientation or age.

Bidders will get a preference for including a partner or independent developer who has not been involved in a successful tender before. For such developers, who have not yet been part of a successful tender bid, we aim on a best-effort basis, but without any guarantees whatsoever, to provide some mentoring in understanding the code base and the process in contributing to the code. We expect that time and efforts on the bidder’s side should not be part of the paid work for this tender. Please mention such need of LibreOffice development mentoring in your offer.

As always, TDF will give some preference to individuals who have previously shown a commitment to TDF, including but not limited to certified developers and/or members of TDF. Not being a member, or never having contributed before, does not exclude any applicants from consideration.

The task offered is a project-based one-off, with no immediate plans to a mid- or long-term contractual relationship. It is offered on a freelance, project basis. Individuals and companies applying can be located anywhere in the world.

When budgeting, we anticipated that this project (all items combined) to take in the region of 16 weeks of work. Should bidders’ assessment result in a significantly different number, please reach out to us before sending your bid, so we can clarify upfront.

TDF is looking forward to receiving your applications for one or more of the aforementioned tasks, your financial expectations and the earliest date of your availability, via e-mail to a committee at tender20210802@documentfoundation.org no later than September 20, 2021.

Applicants who have not received feedback by October 18, 2021 should consider that their application, after careful review, was not accepted.

All bidders are invited to ask their questions on this tender until September 6, 2021. Questions and answers will be made public in a collected and anonymized form.

 

Tender to implement autoupdater (#202108-01)

The Document Foundation (TDF) is the charitable entity behind the world’s leading free/libre open source (FLOSS) office suite LibreOffice.

We are looking for an individual or company to implement an autoupdater for LibreOffice.

Currently, LibreOffice can notify the user about a new version, but download and installation require manual action by the user, it is not automated. With plans of a “rolling release” model, that results in more frequent updates, e.g. biweekly or monthly, we want to improve this system.

Mandatory requirements

  • The solution has to work on all currently LibreOffice-supported Windows, Linux and macOS versions.
  • The implemented solution should not break the MSI-based LibreOffice installation set.
  • The implemented solution cannot solely rely on app stores autoupdaters, as The Document Foundation does not provide binaries in app stores currently.
  • The work has to be developed on LibreOffice master, so that it will be released in the next major version.
  • The implementation has to be provided with extensive documentation, about the approach chosen to implement the above items. We expect bidders to provide documentation on both the code and the non-code parts of the implementation, e.g. methodology, structure and technical aspects.

Optional items

The proposed solution might include some of the items of the following list, which is neither complete nor exhaustive, and is presented as a set of examples. These items are not mandatory to the completion of the tender, but might favor the granting of the tender in case of ex aequos, after checking that mandatory requirements are fulfilled:

  • Achieve partial and/or delta downloads: in order to optimize the bandwidth of the users, the implementation might proceed with the sole download of the whole changed files (partial downloads) or chunks of changed files or the whole package (delta downloads).
  • The implementation might keep track of other languages than English that the user might have installed and currently uses, and implement the download of the respective updated language packs, as well as of eventual offline help packages.
  • The implementation might verify the compatibility and/or update any extensions the user might have installed and currently uses.
  • The implementation is ready for the integration with the app stores’ installers/updaters.

Additional considerations

The choice of technology or technologies used is up to the bidders. Some of the available options, with none of them being a sole strict requirement, are the following:

The idea behind this tender is described in the following required tickets, whereas the implementation we seek for does not mandate a specific technology to be used, even if the tickets suggest otherwise:

The Document Foundation will publish the related documentation under a free and open source license and make it available to the general public.

Required skills

  • Extensive knowledge of C++
  • Experience working on the LibreOffice source code

Other skills

  • English (conversationally fluent in order to coordinate and plan with members of TDF)

We use free, libre and open source (FLOSS) software for development wherever possible, and the resulting work on the program code must be licensed under the Mozilla Public License v2.0.

TDF welcomes applications from all suitably qualified persons regardless of their race, sex, disability, religion/belief, sexual orientation or age.

Bidders will get a preference for including a partner or independent developer who has not been involved in a successful tender before.

As always, TDF will give some preference to individuals who have previously shown a commitment to TDF, including but not limited to certified developers and/or members of TDF. Not being a member, or never having contributed before, does not exclude any applicants from consideration.

The task offered is a project-based one-off, with no immediate plans to a mid- or long-term contractual relationship. It is offered on a freelance, project basis. Individuals and companies applying can be located anywhere in the world.

When budgeting, we anticipated that this project (all items combined) to take in the region of 60 days of work. Should bidders’ assessment result in a significantly different number, please reach out to us before sending your bid, so we can clarify upfront.

TDF is looking forward to receiving your applications for one or more of the aforementioned tasks, your financial expectations and the earliest date of your availability, via e-mail to a committee at tender20210801@documentfoundation.org no later than September 20, 2021.

Applicants who have not received feedback by October 18, 2021 should consider that their application, after careful review, was not accepted.

All bidders are invited to ask their questions on this tender until September 6, 2021. Questions and answers will be made public in a collected and anonymized form.

LibreOffice’s New Website: Meet the Design Team

LibreOffice is getting a shiny new website! We’re still working on it, and everyone interested in testing and helping out can join our mailing list for updates.

But today, we’re talking to the team who created the new design. Say hello to Dan Gallagher, Cat de Leon, Irene Geller, Helen Tran and Zarema Ross. Together, they identified needs and use cases for the website, created mockups, and then moved on to more concrete designs. Let’s see what they have to say…

Tell us a bit about yourselves!

Dan Gallagher: I’m a UX Designer coming from a background in psychology and education. I’m interested in creating intuitive designs based on human psychology. I’m currently living in Chicago, IL. In my free time, I like to box, make music, or play Dungeons and Dragons.

Cat de Leon: My name is Cat and I’m from the San Francisco Bay Area. I have an untraditional background, having majored in math in college, worked in higher education as an institutional researcher, and recently worked as a social media manager. Luckily, I’ve found my dream job in product design! If I’m not designing, I’m probably eating good food, playing video games, playing tennis, watching NBA games, or working out. I will never reject an opportunity to see a picture of your pet. 🙂

Irene Geller: I’m a digital designer from New Jersey (USA) with a focus on UI, visual assets, and branding at the moment. But I began my creative life as a traditional artist, just painting, drawing, and teaching others, too!

Helen Tran: I’m from San Francisco, California. My hobbies include finding scenic sights and building on my UX Research career on the side. I’m a killer for awesome views!

Zarema Ross: Originally I’m from Russia. Today, I live and work in the USA as a UX designer. Before my career in design, I finished an MS in Economics and Management, conducted market research, analysis, and built strategies in the oil and gas industry. I’ve led 10 subsidiaries, approved budgets, and was involved in financial planning.

Being skilled in turning data into actionable information to improve business results, andbeing passionate about solving problems, I end up becoming a User Experience Designer. I get my inspiration from my hobbies such as traveling, Russian ballet, Broadway shows, contemporary art galleries, and digital trends (AR, VR, etc.).

I consider myself a dreamer and a futurist. I hope new technologies will bring enhancements into our everyday lives, and will offer the opportunity to all people around the world to use them. That is why today, I’m working on different UX design projects, helping the world become a better place.

New banner for the front page

How did you get involved in the LibreOffice website redesign project?

Dan Gallagher: I was connected with a member of the website redesign project through a friend. We hopped on a video call and discussed the project, and it sounded like a great opportunity! I had used LibreOffice before, and I really like the idea of giving free office tools away to anyone.

Cat de Leon: I was recruited by Christine Louie and Lisa Lin who did the initial research for LibreOffice’s redesign project. They brought on a team of designers and researchers to continue their work and bring their concepts to life.

Irene Geller: During the 2020 pandemic year, I attended several webinars about UX/UI, to keep myself occupied, fresh on industry knowledge, and to be quite honest, sane. Apparently, at one of these webinars- we don’t even remember which one!- I had connected with Christine Louie (who is now a UX Researcher at Facebook). I must have made a positive impression in the live comments section, because some time after the webinar, Christine reached out to me about volunteering to assist with LibreOffice’s website redesign project. Since I was already a user of LibreOffice in my day-to-day life, I thought it would be an interesting project to take on!

Helen Tran: I met Christine, who was the lead UX Researcher, through a webinar – and after getting to know each other she reached out to me for this amazing opportunity to join the LibreOffice website redesign project. I got to meet the rest of the team which included Lisa, Dan, Cat, Zarema, and Irene who were also all a pleasure to work with. Thanks to everyone who contributed as this team and the team at LibreOffice made this project such a success! 🙂

Zarema Ross: I was invited into the project by one of my colleagues from the UX bootcamp I went to. I liked LibreOffice’s mission to support the community and develop software that everyone can use. I’ve met an amazing team of software developers and UX designers. I really enjoyed working on the project, as it was well organized, and I had a chance to collaborate with cross-functional teams from software developers to the marketing team, as well as run workshops with them in order to improve the information architecture.

New graphics and cleaner design

What particular aspects did you work on, and what was it like?

Dan Gallagher: I focused more on the sketching, wireframing, and documentation of the project. It was my first time working on a team of designers and researchers – it was amazing to be able to share my work and get feedback at every stage of the design process. Every call, someone suggested something I wouldn’t have thought of if I were working alone. I was fortunate to be on a team of skilled and dedicated designers!

Cat de Leon: Before this project, I have only done solo projects so working with a team has been absolutely fantastic. I’ve enjoyed every conversation and meeting I’ve had with this team and I hope to continue our relationships after we’re all done here. I’ve also thoroughly enjoyed connecting with our stakeholders all over the world, like Ilmari, Heiko, and Mike! Our team would probably agree that we’ve gotten far more well versed in time zones after this project. 🙂

Irene Geller: I helped with creating high fidelity UI designs that captured our stakeholders’ key goals for various webpage designs. However, the best part of this project wasn’t working as an individual designer – but as a team!

We used Figma for all of our design work, which allows multiple users to collaboratively work on a design, in real-time. That was a new experience for me as I usually work as a “design team of one”. I found that we often came up with our best ideas when we worked together!

For example, one time we met up to look over the page designs that Cat, Dan, and Zarema had completed. I immediately saw which elements worked best in each approach (ie what fit the stakeholders’ goals best), and quickly combined them together in one new page design, with adjustments to make it all cohesive. Everyone responded positively, so we spent the remainder of the meeting polishing all the elements of this new design. When we presented it at our next stakeholder meeting, they absolutely loved it – an immediate success! That showed me the power of collaborative design.

Overall, it was a real pleasure to work with such talented and smart individuals for a good cause. It certainly made the pandemic lockdown a little brighter, too!

Helen Tran: I worked as a UX Researcher for this project. I helped recruit participants, ran usability tests, and interpreted data to test the projected website launches. It was an amazing experience! It was definitely enjoyable to see the combined efforts made by everyone on this team go into play during the usability runs to witness how individuals engaged with the various features. This experience was rewarding from start to finish seeing the behind the scenes work to a polished website based on all of our hard efforts.

Zarema Ross: Working within an international team of UX designers and Software developers (in the USA and Germany), I:

  • Led design workshops with cross-functional teams to explore innovative solutions for problems and opportunities identified through research and data
  • Performed content audit, validated the SiteMap, restructured the information architecture
  • Sketched designs, created low and hi-fi mockups
  • Iterated on designs and performed usability testing
  • Contributed and maintained the UI kit and style guides

At the end of the day, it was teamwork that drove us to the results we have. I would like to say special thanks to our UX design team: Helen Tran – the time we spent on usability testing, deriving the insights from the research; Dan Gallagher, Cat de Leon and Irene Geller- for the brainstorming we did together, going from lo-fi to hi-fi designs.

And a redesigned download page

What are you interested in doing next?

Dan Gallagher: I’ll continue freelancing, working on personal projects, and searching for a full-time job. Working on this project was a great experience to highlight on my resume, it shows I work well within a team and can balance user and business needs!

Cat de Leon: Now I’m a product Designer for CaaStle. And I just know that wherever I go in future, I’ll be solving users’ problems to the best of my product design abilities and I’ll be having a blast doing it. Thank you so much for this opportunity, LibreOffice!

Helen Tran: I’m interested in growing my UX Research career! I’m ready to dive deep and hop along new projects to learn and enhance my UX skills. Hoping for many more grateful experiences like this project! 🙂

Zarema Ross: I’m interested in the topic of accessibility and inclusive design. I’m currently working on Accessifier which is a crowdsourced web app that provides accessibility ratings of specific apps for users with accessibility needs. I also do UX design on a freelance basis. And I’m looking forward to collaborating with new people, exchange knowledge and create impactful designs. Here’s my LinkedIn page.

Many thanks again to the whole team for their work! And as mentioned, anyone can join our website mailing list to help us to finalise, test and promote the new website. Let’s make it happen together!

Tender to implement master document fixes (#202106-02)

The Document Foundation (TDF) is the charitable entity behind the world’s leading free/libre open source (FLOSS) office suite LibreOffice.

We are looking for an individual or company to implement master document fixes.

The documentation team regularly publishes guides and books. The underlying workflow requires to fix bugs and issues with the master document feature of Writer.

The scope of this tender is to fix at least the following issues:

  1. ToC is never shown in Master Document if it is in ODT in a section with a hide condition
    https://bugs.documentfoundation.org/show_bug.cgi?id=103612
  2. Exported PDF of master document with hidden sections containing headings shows headings anyway
    https://bugs.documentfoundation.org/show_bug.cgi?id=142129
  3. Creating master document from *.odt breaks cross-references
    https://bugs.documentfoundation.org/show_bug.cgi?id=128106
  4. TRACK CHANGES: linked files changes are not shown in the master document
    https://bugs.documentfoundation.org/show_bug.cgi?id=121166

The work has to be developed on LibreOffice master, so that it will be released in the next major version.

The bugs must be fixed and verified.

All technology standards of relevance, as well as their targeted versions for this tender should be declared or defined in the offer’s description of implementation.

A key item of the deliverables for this tender and therefore also a decision criteria – besides qualification, references, price, and completeness of fullfilment – is extensive is documentation about the approach chosen to implement or fix the above items. We expect bidders to provide documentation on both the code and the non-code parts of this tender, e.g. methodology, structure and technical aspects. The Document Foundation will publish this under a free and open source license and make it available to the general public. Publications will be in the Help system and in the Guides books.

If the bug fix incurs in a change in the user interface or user procedure, it should also contain the necessary instructions to activate the procedure.

Required skills

  • Extensive knowledge of C++
  • Experience working on the LibreOffice source code

Other skills

  • English (conversationally fluent in order to coordinate and plan with members of TDF)

We use free, libre and open source (FLOSS) software for development wherever possible, and the resulting work on the program code must be licensed under the Mozilla Public License v2.0.

TDF welcomes applications from all suitably qualified persons regardless of their race, sex, disability, religion/belief, sexual orientation or age.

Bidders will get a preference for including a partner or independent developer who has not been involved in a successful tender before. For such developers, who have not yet been part of a successful tender bid, we aim on a best-effort basis, but without any guarantees whatsoever, to provide some mentoring in understanding the code base and the process in contributing to the code. We expect that time and efforts on the bidder’s side for this should not be part of the paid work for this tender. Please mention such need of LibreOffice development mentoring in your offer.

As always, TDF will give some preference to individuals who have previously shown a commitment to TDF, including but not limited to certified developers and/or members of TDF. Not being a member, or never having contributed before, does not exclude any applicants from consideration.

The task offered is a project-based one-off, with no immediate plans to a mid- or long-term contractual relationship. It is offered on a freelance, project basis. Individuals and companies applying can be located anywhere in the world.

When budgeting, we anticipated that this project (all items combined) to take in the region of 5 days of work. Should bidders’ assessment result in a significantly different number, please reach out to us before sending your bid, so we can clarify upfront.

TDF is looking forward to receiving your applications for the aforementioned tasks, your offer in form of a fixed-time, fixed-budget approach, and the duration period for the implementation in calendar weeks after the final awarding of the tender, via e-mail to a committee at tender20210602@documentfoundation.org no later than July 5, 2021.

Applicants who have not received feedback by August 2, 2021 should consider that their application, after careful review, was not accepted.

All bidders are invited to ask their questions on this tender until June 23, 2021. Questions and answers will be made public in a collected and anonymized form.

Press Releases

LibreOffice 26.2 is here: a faster, more polished office suite that you control

We’re pleased to announce the release of LibreOffice 26.2, the newest version of the free and open source office suite…

  • Announcement of LibreOffice 25.8.4

    Berlin, 18 December 2025 – LibreOffice 25.8.4, the fourth minor update to the free office suite developed by volunteers for…

  • Announcement of LibreOffice 25.8.3

    Berlin, 13 November 2025 - LibreOffice 25.8.3, the third minor release of the free, volunteer-supported office suite for personal productivity…

Open Document Format

The philosophy behind ODF: openness, freedom and control

File formats are not usually the subject of philosophical debate because most users just want to open, save and share…