LibreOffice community focus: Documentation

Earlier this month we talked to the localisation community about the preparations they are making for LibreOffice 6.0, which is due to be released in late January (or early February). Now we turn to the documentation project, and Olivier Hallot, who is coordinating updates to guidebooks and a new help system…

olivier_hallot_07062010_964x1036What has the documentation community been working on in preparation for LibreOffice 6.0?

The community is engaged in delivering two major features for the 6.0 release: the first is a new and updated Getting Started Guide, a book targeted at new users of LibreOffice 6.0. We included the latest developments that are in the scope of an introductory text for LibreOffice 6.0. For 2018 we are assembling a team of writers to update our other guides, starting with the Calc Guide.

The other major feature is the new LibreOffice help system, a completely redesigned help system that now uses the operating system’s web browser to display help pages. Here’s a screenshot from the LibreOffice 6.0 release notes, showing how it looks in a mobile web browser:

What are your favourite new features in this release?

I always appreciate applications that have beautiful aesthetics. When choosing between two applications or desktop environments with the same features, I take the one that’s good-looking and has a well-crafted user interface. There are so many excellent programs with clumsy interfaces or ugly aesthetics struggling to survive. It is purely subjective but in the end, beauty pays. So my take for 6.0 are the features that bring a better and nicer UI: new icons, toolbars and redesigned dialogs. Here’s a preview of the Elementary icon set, which will be included in 6.0:

Aesthetics, together with essential technology evolutions, were the drive to develop our new help system based on web technology. We expect to open an avenue for improving the contents of our help with multimedia, animations and better navigation – altogether bringing a modern web experience for our users who are reading the help.

What tools and services do you use in the documentation community?

At the moment we use Plone as our document repository, and we have a workflow for editing, revision and publication. Released documents are available on our documentation website for download, and some l10n (localisation) communities prefer to use the TDF wiki.

With the recent developments in LibreOffice Online, I am planning to use it for document editing and production, in a simpler way than using Plone. LibreOffice Online is by far the best online editor for OpenDocument formatted files, and is an essential feature for preserving our current documents and making editing easier.

For 2018, we will work to develop an special online editor for help files, making it easier for occasional contributors to make changes to the content.

Finally, how can people get involved with the documentation community?

The first step is to read this page and follow the instructions there. We need good software documenters, along with people who really know how an office suite works, and who are capable of writing about new features with authority.

Thanks Olivier, and thanks to the whole documentation community for their work in LibreOffice 6.0. Over the next few weeks, we’ll be talking to other projects, including QA and development – keep checking this blog for updates.

LibreOffice community focus: Localisation

LibreOffice 6.0 is due to be released at the end of this month (or in early February), and you can learn about the changes in on the wiki. Closer to the release, we’ll make a short video showing off the new features in action. But as we head towards LibreOffice 6.0, we want to hear from the many communities that have contributed to this version. We start off by talking to Sophie Gautier, who has been working with the localisation community to make the software available in as many languages as possible…

What has the localisation community been doing in preparation for LibreOffice 6.0?

Each time a developer makes a change to the user interface (UI), that means some work for the localisation team, both in terms of the UI itself and the help system. And our UX/Design team has been very busy moving menu entries, designing new dialogs and making new toolbars – so all this work ends up in the hands of the translation team.

Once we have finished the translations of the suite, we have to check that our translations are correct. Sometimes, the localisation process means that you’re translating out of context, with very poor references for where you are in the interface.

Then, there are also press release preparations, new features pages for the website, videos, and all the work done by the marketing team that we have to translate and adapt to our languages, to cover the LibreOffice 6.0 launch.

What are your favourite new features in this release?

I’m not sure I have a preferred one – I’m just always amazed by the work done by the community at each level. I’m very grateful for it, but to name a few: I like the new and easy way to customise the UI, OpenPGP signing of documents, and the work done to modernise the help system.

What tools and services do you use in the localisation community?

Most of the teams use Pootle as an online tool for translations. Some other teams use Pootle as a repository for their files, but also use a computer-assisted translation tool (like OmegaT) to work on the files. Some others don’t use Pootle as a
repository and commit their files directly to Gerrit. We want our teams to be able to use the tools they like the best to translate.

To search for the strings in the source code and get some context (which dialog the string is in, other strings in the dialog, accelerators, etc.) we use OpenGrok which is a simplified web interface for browsing the code.

Finally, how can people get involved with the localisation community?

If a language team already exists, it’s best to contact them directly (the address can be found on our wiki). If none exists, then the best way is to ask on l10n@libreoffice.org for the creation of the language – both in LibreOffice itself, and on Pootle. We will help the newcomers with the first steps in localisation.

Also, Yousuf Philips has written a script that categorises and references the most important strings to translate at the beginning. This shows what is most visible in the interface, and will be of the most help for the users.

Thanks Sophie for that overview – and indeed, a hearty thanks to the whole localisation community for their great help with preparing LibreOffice 6.0. Over the next couple of weeks, we’ll be talking to other communities in the LibreOffice project, so stay tuned to the blog…