This is a feed aggregator that collects what LibreOffice and Document Foundation contributors are writing in their respective blogs.
To have your blog added to this aggregator, please mail the website@global.libreoffice.org mailinglist or file a ticket in Redmine.
Ekipa jamstva kakovosti LibreOffice (QA Team) ponosno objavlja, da je za preizkušanje na voljo prvi kandidat za izdajo LibreOffice 7.5 Community!
LibreOffice 7.5 Community RC1 lahko prenesete s tega mesta za sisteme Linux, macOS in Windows, z njeno namestitvijo pa boste zamenjali standardno izdajo.
Če naletite na kakršno koli težavi s to predizdajo, o težavah poročajte v sistemu Bugzilla (potrebujete le veljaven e-poštni račun, da ustvarite nov račun).
Za pomoč se lahko obrnete neposredno na ekipo QA v kanalu QA na IRC ali prek Matrixa.
LibreOffice je projekt skupnosti prostovoljcev, izjemno veseli bomo vaše pomoči.LibreOffice 7.5 will be released as final at the beginning of February, 2023 ( Check the Release Plan ) being LibreOffice 7.5 Release Candidate 1 (RC1) the third pre-release since the development of version 7.5 started in mid June, 2022. Since the previous release, LibreOffice 7.5 Beta1, 213 commits have been submitted to the code repository and 70 issues got fixed. Check the Release Notes to find the new features included in this version of LibreOffice.
LibreOffice 7.5 RC1 can be downloaded for Linux, macOS and Windows, and it will replace the standard version.
In case you find any problem in this pre-release, please report it in Bugzilla ( You just need a legit email account in order to create a new account ).
For help, you can contact the QA Team directly in the QA IRC channel or via Matrix.
LibreOffice is a volunteer-driven community project, so please help us to test – we appreciate it!
Happy testing!!
…
En este momento existen dos puestos de desarrollador disponibles, uno tiene que ver con cuestiones de RTL/CTL y el otro se centra en la accesibilidad.
The Document Foundation (TDF) es la entidad sin fines de lucro que está detrás de …
alsVarious data types are used in LibreOffice code and also in LibreOffice API. Here we discuss some of these data types, which are important when you are working with LibreOffice code and API.
You should know that LibreOffice API can be used from many languages, but here we only focus on C++. LibreOffice uses a component model called UNO (Universal Network Objects), which is designed to provide an environment for accessing network objects from different languages. The data types that we discuss here are among UNO data types.
The data types used in LibreOffice API are called UNO data types. They are also used extensively inside the LibreOffice code. Here we discuss the fundamental UNO data types.
First, let’s talk about simple UNO data types. If you take a look at the below table from the LibreOffice Developer’s Guide, chapter 1: First Steps you will see that it shows the numerical/character data types. When working with LibreOffice API, we do not simply use byte, short, long, int and other underlying C++ data types, but rather data types defined in LibreOffice. Those include sal_Int8, sal_Int16, sal_Int32 and their unsigned counterparts, sal_uInt8, sal_uInt16, sal_uInt32. In the past, sal_Bool was used for the boolean variables, but it is now deprecated and we simply use bool data type.
The table shows detailed information about these UNO data types, and how they are mapped into several programming languages:
Table 1: Mapping simple UNO data types to data types in different programming languages
| UNO | Type description | Java | C++ | Basic |
|---|---|---|---|---|
| void | empty type, used only as method return type and in any |
void | void | – |
| boolean | Boolean type; true and false | boolean | bool (sal_Bool is deprecated) |
Boolean |
| byte | signed 8-bit integer type | byte | sal_Int8 | Integer |
| short | signed 16-bit integer type | short | sal_Int16 | Integer |
| unsigned short | unsigned 16-bit integer type (deprecated) | – | sal_uInt16 | – |
| long | signed 32-bit integer type | int | sal_Int32 | Long |
| unsigned long | unsigned 32-bit integer type (deprecated) | – | sal_uInt32 | – |
| hyper | signed 64-bit integer type | long | sal_Int64 | – |
| unsigned hyper | unsigned 64-bit integer type (deprecated) | – | sal_uInt64 | – |
| float | IEC 60559 single precision floating point type | float | float (if appropriate) | Single |
| double | IEC 60559 double precision floating point type | double | double (if appropriate) | Double |
| char | 16-bit Unicode character type (more precisely: UTF-16 code units)- | char | sal_Unicode | – |
Another important data type is sal_Unicode, which is used instead of char for storing Unicode character data. In C/C++, for storing strings we use OUString which can store Unicode data. As DevGuide says, LibreOffice Basic strings are mapped to UNO strings transparently. So, you don’t have to worry about converting strings to OUStrings back and forth. But in C++, you have to do the conversion from other string types yourself. We will discuss strings in a separate blog post.
| UNO | Description | Java | C++ | Basic |
|---|---|---|---|---|
| string | Unicode string type (more precisely: strings of Unicode scalar values) | java.lang.String | rtl::OUString | String |
In C …
LibreOffice 7.5 will be released as final at the beginning of February, 2023 ( Check the Release Plan ) being LibreOffice 7.5 Beta1 the second pre-release since the development of version 7.5 started in mid June, 2022. Since the previous release, LibreOffice 7.5 Alpha1, 353 commits have been submitted to the code repository and 116 issues got fixed. Check the Release Notes to find the new features included in this version of LibreOffice.
LibreOffice 7.5 Beta1 can be downloaded for Linux, MacOS and Windows, and it can be installed alongside the standard version.
In case you find any problem in this pre-release, please report it in Bugzilla ( You just need a legit email account in order to create a new account ).
For help, you can contact the QA Team directly in the QA IRC channel or via Matrix.
LibreOffice is a volunteer-driven community project, so please help us to test – we appreciate it!
Happy testing!!
…
Firebird high-level native client for Node.js / TypeScript status status for Firebird / Typescript Advent 2022https://qiita.com/advent-calendar/2022/firebirdTo use the driver you can start with the readme from npm/githubhttps://www.npmjs.com/package/node-firebird-driver-nativeA few more examples are in the packages/node-firebird-driver/src/test directoryWe have seen several releases with a few
LibreOffice 7.5 will be released as final at the beginning of February, 2023 ( Check the Release Plan ) being LibreOffice 7.5 Alpha1 the first pre-release since the development of version 7.5 started in mid June, 2022. Since then, 4875 commits have been submitted to the code repository and more than 759 bugs were set to FIXED in Bugzilla. Check the release notes to find the new features included in this version of LibreOffice.
LibreOffice 7.5 Alpha1 can be downloaded from here for Linux, MacOS and Windows, and it can be installed alongside the standard version.
In case you find any problem in this pre-release, please report it in Bugzilla ( You just need a legit email account in order to create a new account ).
For help, you can contact the QA Team directly in the QA IRC channel or via Telegram.
LibreOffice is a volunteer-driven community project, so please help us to test – we appreciate it!
Happy testing!!
…
The PDF export now supports various additional properties for the optional PDF watermark.
First, thanks Docmosis for funding this work by Collabora.
Rendering of a PDF watermark with custom rotation and color
When you hear the word "watermark", you probably have something like the above picture in mind.
Instead, what the PDF export had is more like a proof of concept:
Rendering of a PDF watermark with default settings
The request was to add new options to control the font size, font name, rotation angle and color of the watermark, so in case an organization already has a given style of watermarks they prefer, our PDF export can be adapted accordingly.
First, now you can specify a custom color, e.g. gray (#7f7f7f), using:
soffice --convert-to pdf:writer_pdf_Export:'{"Watermark":{"type":"string","value":"draft"}, "WatermarkColor":{"type":"long","value":"8355711"}}' test.odt
Rendering of a PDF watermark with custom color
Then you can also customize the font size, in case the automatic size would not fit your needs, using:
soffice --convert-to pdf:writer_pdf_Export:'{"Watermark":{"type":"string","value":"draft"}, "WatermarkFontHeight":{"type":"long","value":"100"}}' test.odt
Rendering of a PDF watermark with custom font size
Or perhaps you want a serif font, not a sans one:
soffice --convert-to pdf:writer_pdf_Export:'{"Watermark":{"type":"string","value":"draft"}, "WatermarkFontName":{"type":"string","value":"Times"}}' test.odt
Rendering of a PDF watermark with custom font name
Finally you can have a custom rotate angle:
soffice --convert-to pdf:writer_pdf_Export:'{"Watermark":{"type":"string","value":"draft"}, "WatermarkRotateAngle":{"type":"long","value":"450"}}' test.odt
Rendering of a PDF watermark with custom rotation
Using these building blocks, you can also build combinations, the first screenshot above was created using:
soffice --convert-to pdf:writer_pdf_Export:'{"Watermark":{"type":"string","value":"draft"}, "WatermarkRotateAngle":{"type":"long","value":"450"}, "WatermarkColor":{"type":"long","value":"8355711"}}' test.odt
i.e. the configuration JSON is:
{
"Watermark": {
"type": "string",
"value": "draft"
},
"WatermarkRotateAngle": {
"type": "long",
"value": "450"
},
"WatermarkColor": {
"type": "long",
"value": "8355711"
}
}
If you would like to know a bit more about how this works, continue reading... :-)
As usual, the high-level problem was addressed by a series of small changes:
You can get a snapshot / demo of Collabora Office 22.05 and try it out yourself right now: try the unstable snapshot. Collabora intends to continue supporting and contributing to LibreOffice, the code is merged so we expect all of this work will be available in TDF's next release too (7.5).
node-firebird status for Firebird Advent 2022 https://qiita.com/advent-calendar/2022/firebird also for Javascript Advent https://qiita.com/advent-calendar/2022/javascriptThis year we have seen several releases with a few features and changes :Version 1.1.0 Changes : Srp implementation by @maratth in #242Add optional callback for pool destroy by @Tomas2D in #244Set protocolVersion as optional in
LibreOffice uses a build system called gbuild which uses GNU Make. Migrating from the old build system to gbuild started in the OpenOffice days, but the migration took a while and a lot of effort, finishing around LibreOffice 4.1.
This LibreOffice build system uses GNU Make, Perl and Python, so you need to have these prerequisites in order to be able to build LibreOffice. However, LibreOffice bundled Python can be used.
To get a nice description, just try this inside the LibreOffice core source folder:
make help
You can find gbuild in solvenv/gbuild folder of the LibreOffice core source code. There are many macros available in gbuild that are useful when doing the actual build. Let’s start from a simple one that creates a nice output.
If you look at the build output, you see many three letter outputs. They are short forms denoting the category of what is being built, for example, [BIN] means binary, [MOD] means module, and [ALL] is what it is! There are other short names like [CXX] for compiling C++ files, [C ] for compiling C files, and [LNK] for the linking.
... [BIN] postprocess [MOD] postprocess [MOD] libreoffice [BIN] top level modules: libreoffice [ALL] top level modules: build-non-l10n-only build-l10n-only ...
These are the outputs, generated by a macro named gb_Output_announce. This macro does the printing, and its code is available in “solenv/gbuild/Output.mk”
define gb_Output_announce $(info $(call gb_Output_announce_str,$(1),$(2),$(3),$(4))) endef
Then, it calls this macro:
$(call gb_Output_announce,$*.cxx,$(true),CXX,3)
And, you will see the nice result in the output which contains [CXX]. You can see that another macro, gb_Output_announce_str is called here, that creates the output.
There are many other macros available for developers. You find the makefiles with the .mk extensions, and you see a lot of them for the executables, libraries, and tests.
For example, let’s take a look at the xmlscript folder. Here are the .mk files:
1) xmlscript/CppunitTest_xmlscript_cppunit.mk
2) xmlscript/Module_xmlscript.mk
3) xmlscript/Library_xmlscript.mk
4) xmlscript/Package_dtd.mk
The makefile #1 is the CppunitTest_xmlscript_cppunit, which is used for adding a test, which can be run by:
make CppunitTest_xmlscript_cppunit
The makefile #2 is the main makefile for the module, which in turn, invokes makefile #3, which builds the xmlscript library, and #4, which creates the xmlscript dtd package, and also makefile #1 which contains the tests. This code does the job:
$(eval $(call gb_Module_Module,xmlscript)) $(eval $(call gb_Module_add_targets,xmlscript,\ Library_xmlscript \ Package_dtd \ )) $(eval $(call gb_Module_add_check_targets,xmlscript,\ CppunitTest_xmlscript_cppunit \ ))
As you can see, gb_Module_Module, gb_Module_add_targets and gb_Module_add_check_targets are the macros that are invoked to make this happen. All of these macros are defined in solenv/gbuild/Module.mk. In this file, you get this overview:
# Overview of dependencies and tasks of Module
#
# target task depends on
# Module build the product all product targets
# excluding tests recursive Modules
# Module/unitcheck run unit tests all unit tests
# recursive Module/checks
# Module/slowcheck run all slow unit tests …
Similar to the questionnaires about LibreOffice Draw (see first and second blog post) and LibreOffice Calc (see this post) we now run a survey on LibreOffice Impress to learn how the program is utilized, what features are used most frequently, and what users see as positive and negative and what they expect of the future.…
LibreOffice Base can connect to an external Firebird server , here is an example with employee.fdb from Firebird 3 examples folder copied to c:\tmpTested with LibreOffice 7.4.x and Firebird 3 default install on Windows 11 (all 64 bits versions)and here is the Relation Design in LibreOffice Base
Do you want to submit a patch to LibreOffice Gerrit, and you’re wondering if your code will be accepted or not? Other than providing a good solution to resolve a problem (fix a bug, implement a feature or enhancement), you should care about the code conventions, and in particular, code formatting. Suitable code formatting for LibreOffice is what we discuss here.
LibreOffice is based on the old code base of OpenOffice. Because of that, LibreOffice uses the coding conventions of OpenOffice in most places. There is a list of rules that you can refer to when needed, in the OpenOffice Wiki:
Here is a comprehensive list of C++ coding rules:
You can see many rules and standards there – beyond code formatting – from design to the way you should declare and implement classes, and their functions and variables. You will also find topics about how to create header files, how to document code and how to achieve type safety.
But, focusing only on C++ code formatting, you should make sure that:
These rules have their own name in the OpenOffice code formatting conventions.
Let’s look at this code snippet from a C++ file: chart2/qa/extras/charttest.hxx.
uno::Sequence < OUString > ChartTest::getImpressChartColumnDescriptions( std::u16string_view pDir, const char* pName )
{
uno::Reference< chart::XChartDocument > xChartDoc = getChartDocFromImpress( pDir, pName );
uno::Reference< chart::XChartDataArray > xChartData ( xChartDoc->getData(), uno::UNO_QUERY_THROW);
uno::Sequence < OUString > seriesList = xChartData->getColumnDescriptions();
return seriesList;
}
As you can see, in the old OpenOffice style, there is a space after the starting parenthesis (, and also before the ending parenthesis ). Also, before and after <>. This might look old fashioned, but this is the way old code is written, and you are supposed to avoid changing the old code only for making it look better! I am going to describe why.
There is a very good reason to keep the old style code formatting. To understand the code, and possible problems, developers usually refer to the code, and its history. Thus, it is important to keep the history of the code clean.
To achieve this, experienced developers suggest that you should avoid changing the formatting of the code, even if you are tempted to do so! Changing spacing, curly braces and other things in order to look nicer will pollute the git history.
The nice tool git blame can show who to blame for each line of code! If you change the code format randomly, you may prevent other developers to understand the root cause of the change, and thus fixing the problems more difficult.
Bruce Byfield and Jean Hollis Weber announce the second edition of Designing with LibreOffice. The book is available as an .ODT or .PDF file under the Creative Commons Attribution/Sharealike License version 4.0 or later from https://designingwithlibreoffice.com/
The first edition was published in 2016, and was downloaded over thirty-five thousand times. Michael Meeks, one of the co-founders of LibreOffice, described the first edition as “an outstanding contribution to help people bring the full power of LibreOffice into their document.” Similarly, free software author and journalist Carla Schroder wrote, “Designing With LibreOffice teaches everything you need to know about document production…. suitable for beginners to wizened old pros, who will probably discover things about LibreOffice that they didn’t know.”
The second edition updates the original, removing outdated information and adding updated screenshots and new information about topics such as Harfbuzz font shaping codes, export to EPUB formats for ereaders, the Zotero extension for bibliographies, and Angry Reviewer, a Grammarly-like extension for editing diction. In the future, the writers plan to release other editions as necessary to keep Designing with LibreOffice current.
For more information or interviews, contact Bruce Byfield at bbyfield@axion.net.
The LibreOffice Conference 2022 (LibOCon) took place from September 28 to October 1 in Milan. It was the first LibreOffice Conference since the outbreak of the COVID-19 Pandemic that took place as an in-person event. Collabora was one of the sponsors, and a significant number of our developers contributed talks on various aspects of LibreOffice technology. Did you miss any of those? Don’t worry! All our talks are available for you on YouTube inside our LibOCon playlist. Please also feel free to download the slides we included in this blog post.
Michael Meeks, Managing Director of Collabora Productivity, takes a look at the latest developments in LibreOffice from an organisational and ecosystem perspective. See details 
Watch the talk
Download the slidesHear Michael Meeks tell the history of LibreOffice in the browser. From it’s pre-historic past as StarPortal, through gtk-broadway prototypes, to Collabora Online as we know it today. See details
Watch the talk
Download the slidesDuring the Quality Assurance track, Sarper Akdemir explained how to fix an interoperability bug by showcasing the whole process of understanding, fixing, and implementing tests. See details
Watch the talk
Download the slidesSparklines are mini charts, that are drawn into a cell. In his talk, senior software engineer Tomaž Vajngerl presented the features and the challenges during the development. See details
Watch the talk
Download the slidesWhile LibreOffice and Collabora Office were already capable of filling forms via form controls or form fields, they can now also fully represent content controls. In this talk by Senior Software Engineer Miklos Vajna, see how this work was implemented! See details
Watch the talk
Download the slides
Collabora Productivity created Collabora Online, a powerful online office suite, which you can integrate into your own infrastructure. It prioritises your digital sovereignty and provides you with all the tools to keep your data secure, without compromising on features. Collabora provides a wide range of products, as well as consulting services for enterprises and governments. Powered by the largest team of certified LibreOffice engineers in the world, Collabora is a leading contributor to the LibreOffice Technology codebase and community. Collabora Office for Desktop and Collabora Online provide a business-hardened office suite with long-term support. Collabora’s multi-platform policy is completed with Collabora Office for iOS, Android, and Chrome OS. Collabora Productivity is a division of Collabora, the global software consultancy dedicated to providing the benefits Open Source to the commercial world, specializing in mobile, automotive and consumer electronics industries. For more information, follow us on Twitter, LinkedIn and YouTube.
The post Collabora’s Contributions to the LibreOffice Conference 2022 in Milan appeared …
| Imprint Privacy Policy | |
|
The Document Foundation is not responsible for the content on planet.documentfoundation.org. However - if you have any concerns about content please contact act Uwe Altmann for moderation. Copyright information: Unless otherwise specified in the author's blog, all text and images on this website are licensed under the Creative Commons Attribution-Share Alike 3.0 License. This does not include the source code of LibreOffice, which is licensed under the "Mozilla Public License v2.0". "LibreOffice" and "The Document Foundation" are registered trademarks of their corresponding registered owners or are in actual use as trademarks in one or more countries. Their respective logos and icons are also subject to international copyright laws. Use thereof is explained in our trademark policy. |
 |
| this site runs a modified version of planet.opensuse (https://github.com/openSUSE/planet.opensuse.org) © 2010 Pascal Bleser and the openSUSE Community. | |