Donations to The Document Foundation help us to grow our community, run our infrastructure, organise events and share knowledge. And as a result, LibreOffice keeps on improving for all users! Many thanks to all of our supporters. Here’s a quick infographic showing how we used your donations in 2023:
LibreOffice is available in over 100 languages, thanks to our worldwide community of localisers and translators. And for the upcoming LibreOffice 24.2 release, it will be available in Armenian for the first time!
Armenian is an Indo-European language, spoken by 5 – 7 million people in the Republic of Armenia and elsewhere in the world. The translation of LibreOffice’s user interface was largely done by Tigran Zargaryan, who shared the announcement with us:
Dear members of The Document Foundation, and the LibreOffice community! With great pleasure, I’m informing that the Armenian localisation of LibreOffice is complete, and this is an especially significant event for Armenian community members worldwide, who are using various office suites in their daily work and – due to lack of Armenian user interface translations – are facing language difficulties.
I hope that the presence of the Armenian language interface translation will be of great support especially in schools, educational institutions and state organisations. In general, many state-based entities are financed by tax payers, and the presence of such a suite will ease their life, as they will legally be able to use office products without copyright infringement, and for them a totally new world of Free/Open Source Software (FOSS) philosophy will be introduced.
Big thanks and շնորհակալություն to Tigran for his contributions! Everyone is welcome to join our native-language communities, and help us to translate LibreOffice into even more languages.
And here, a couple of screenshots of the suite in Armenian:
The Document Foundation – the non-profit entity behind LibreOffice – recently teamed up with the California State University, Monterey Bay (CSUMB) to encourage students to learn about LibreOffice quality assurance (QA) and help out. A few days ago we chatted with Keldin Maldonado, and today we’re talking to Steven Casey…
During my 25 hours, I was primarily tasked with working on bug reports for LibreOffice. At the beginning of my service, I was simply testing unconfirmed reports and retesting confirmed reports to ensure the bugs were still present in the up-to-date version of the software. I would leave comments on those reports about my findings and follow up later if needed. Once I got a better understanding of Bugzilla, the software, and my duties (and I sure did make my fair share of mistakes), I moved on to binary bisecting. Binary bisecting was more advanced than what I was doing before, but it was also quite a bit of fun!
It was common for me to spend hours digging deep into a report to figure out which commit was causing the regression and more importantly, why. As a student studying computer science with an intention of becoming a software engineer, it was important to me to try and figure out why these bugs were happening. Often times, I came up with a theory and happily appended it to my comment on the report, but sometimes I would run into a roadblock and not be able to figure it out.
Honestly, the experience was a lot better than I initially expected. I think a large part of that was due to my mentor during my service, Ilmari Lauhakangas. Ilmari was both understanding and extremely helpful, not to mention just a great individual. I was often pretty loaded with work during my service and I really appreciated the no commitment, work on your own time whenever approach. There were some days I would work 5 hours mid-day, and other days where I would work for an hour between 1 and 2 in the morning!
LibreOffice also has a fantastic wiki with a lot of info for beginner bug triagers on getting started which helped a lot, as it was a little overwhelming in the beginning. Thanks to the wiki along with the tutorial videos Ilmari provided, I was able to mostly get a grasp on things pretty quickly. However, the wiki, while holding great information, feels a little scattered. There were a couple of times where I would search for something on the wiki, and end up not finding it to have Ilmari send me a link to a slightly different page I just happened to miss.
Please confirm that you want to play a YouTube video. By accepting, you will be accessing content from YouTube, a service provided by an external third party.
If you accept this notice, your choice will be saved and the page will refresh.
For example, there is a GetInvolved page and a BugTriage page, which have very similar info, but some small differences which can be important. While it wasn’t an issue for me, time zones can also be a slight issue for someone who is interested in volunteering. Being based in California in the United States, available meeting times would either be around 10pm or 9am or so. Luckily, I am often up late at night, so 10pm was great for me!
I still plan to contribute to bugs here and there very casually. I genuinely mean it when I say that this experience was “life changing” no matter how silly that may sound. I graduate in August of 2024 so I plan on focusing on that the most. I do need to be career ready, and secure a position for graduation. With that being said, Ilmari has asked me to email him if I’m interested in LibreOffice development after the holidays. I don’t know what that will entail quite yet, but I plan on taking him up on that offer. Maybe I will be the one accidentally introducing the regressions soon!
Many thanks thanks to Steven and Keldin for their help! All LibreOffice users are welcome to join our QA community and keep the software strong and robust.
TXDon (aka Don Matschull) is a regular on our Ask LibreOffice website, helping users with their questions. He also maintains a YouTube channel with video tutorials about the suite, and has created courses on Udemy. We chatted with him about his work – and here’s what he had to say.
Don Matschull: I really want to help others learn about what LibreOffice has to offer. I especially want to emphasize the advantage of using styles rather than trying to use LibreOffice Writer like other applications with direct formatting.
In the past, I tended to learn just enough about an application to accomplish the task at hand. After using one application for years, I had some extra time and started to read more of the user manual and other books. I quickly learned that I could have saved hours, days, months of time if I had delved more deeply when I first started using the application. Now, I try to gain a deeper knowledge of the application I am working with.
As I learn, I like to share the knowledge I’ve gained. Trying to explain something helps me understand it even better. When researching a topic, I tend to check the user guides, help files, do internet searches for written and video tutorials, and use help forums such as Ask LibreOffice. Often, I find only bits and pieces of what I want to know and end up experimenting until I’m satisfied that I have a decent grasp of the subject. Then, I try to share what I’ve learned to keep others from having to spend the time and frustration I spent learning.
I try to design my courses in a somewhat logical progression, though this can be difficult because of the way topics can be interrelated. My YouTube videos are more spontaneous. The biggest difficulty with these is trying to keep them short while also covering the topic in more than a superficial manner.
My next video will probably be about how to make lists more distinctive and attractive. Then, I expect to discuss the new features and changes introduced by LibreOffice 7.6 when it reaches the point that version 7.5 now holds.
Eventually, I would like to prepare a whole new course or more on LibreOffice Writer incorporating audio and video techniques I learned since my initial course.
Recently, The Document Foundation – the non-profit entity behind LibreOffice – teamed up with the California State University, Monterey Bay (CSUMB) to encourage students to learn about LibreOffice quality assurance (QA) and help out. Let’s hear from one of the students, Keldin Maldonado:
I worked in the QA team for LibreOffice. I was tasked with looking over bug reports and providing feedback on these reports by either confirming the bug, asking for more information, or providing my feedback if I wasn’t able to replicate the bug.
Later in my volunteer time, I learned about finding the specific commits that caused the bugs through bibisecting that made life for developers a lot easier. I must say, it was honestly really cool seeing the open source model in action. I was able to witness the community effort to resolve these issues in LibreOffice and see how this product was consistently improving.
This was the first time doing any sort of work like this, so I had a hard time getting used to some of the tooling, specifically Bugzilla with its infinite options. Luckily, I had Ilmari Lauhakangas to mentor me through this. He provided search queries that definitely made life easier. Apart from this, I also had issues with my working environment because of backward compatibility. I was able to use Distrobox, however, on a Linux box I built specifically for bug hunting that I then SSHed into from my main machine to be able to run older versions of LibreOffice, and my compatibility issues disappeared.
In terms of the good things, I genuinely think that the last couple of mentoring meetings that I had with Ilmari taught me things that will stick with me for life, and for that, I have to give him a huge thanks for being patient and a good mentor. Specifically, I think learning about bibisecting was a great skill to be taught. I will definitely continue to use this going into my professional career and participating further in the open source community.
I also think that having a chance to work in this community maintaining LibreOffice, a product that many people rely on a day to day basis, was great. It might sound a bit cliche, but it genuinely felt really good knowing about the impact I was making, albeit small on the grand scheme of things. I know that my efforts made people’s lives a bit easier in the long run.
In terms of my professional plans, I am still enrolled in my undergraduate computer science program, which I will finish in the summer of 2024, and then I hope to go into software engineering. Currently, that is what’s taking up the majority of my time. In regards to The Document Foundation and LibreOffice, I will continue to provide help. Last I spoke with Ilmari, he asked me if I wanted to continue with the development side of things, which I think is a great opportunity for me to further develop my skill, and it will give me a chance to continue helping with The Document Foundation’s efforts.
Big thanks to Keldin for his contributions! But he wasn’t alone – Steven Casey also joined the QA community, and we’ll talk to him in our next interview on this blog…
Zdeněk Crhonek (aka “raal”) from the Czech LibreOffice community writes:
The Czech team has finished its translation of the LibreOffice Impress Guide 7.5. As usual it was a team effort, with translations by Petr Kuběj, Zdeněk Crhonek and Radomír Strnad. Localized pictures were provided by Roman Toman, and technical support came from Miloš Šrámek. Thanks to all the team for their work!
The Czech translation of the Impress Guide 7.5 is available for download on this page. We haven’t yet decided what we will translate next – probably we will wait for the next big release (LibreOffice 24.2), but if any volunteers would like to join us in the meantime, please visit this page.
Great work everyone!
