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.
photo: All rights reserved.
hanseatic productivity liberator, LibreOffice guy, sometimes grumpy, always a troll
PGP-Key: 0xc8be3f1f92cb264617fe361ddcd9c191e48dbf5f
blog -- fediverse -- twitter (inactive)
posts on:
All views expressed on this blog are those of Bjoern Michaelsen and do not necessarily reflect the views of any other entity, including current and former employers.
LibreOffice 7.6 will be released as final in mid August, 2023 ( Check the Release Plan ) being LibreOffice 7.6 Alpha1 the first pre-release since the development of version 7.6 started in mid December, 2022. Since then, 4670 commits have been submitted to the code repository and more than 754 bugs were set to FIXED in Bugzilla. Check the release notes to find the new features included in this version of LibreOffice.
LibreOffice 7.6 Alpha1 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!!
…
Flamerobin 0.9.7 Snapshot released with a few Firebird 4 fixesInt128 does not respect scale (Issue #166) Make Domain::dataTypeToString able to process fb4 types. fix some bugs converting int128/dec34/dec16 to string replace CMAKE_SOURCE_DIR to CMAKE_CURRENT_SOURCE_DIR when copy templates in CMakeList.txt by @Khalyutin in #310
Il 3 maggio si celebra in tutto il mondo la Giornata Internazionale della Libertà di Stampa, un’occasione per riflettere sull’importanza dei principi in difesa della libertà di parola e il diritto all’informazione, del pluralismo e dell’indipendenza dei media. Questi diritti sanciti dalla Costituzione Italiana e dalle principali democrazie di tutto mondo assumono un significato di […]
Writer now has continued steps to handle tables that are both floating and span over multiple pages.
This work is primarily for Collabora Online, but is useful on the desktop as well. See the second post for background.
The previous post finished with cursor traversal: if a floating table is on both page 1 and page 2, then you expect Writer to be able to move between the rows of the table, even if those are not on the same page. In this post, we'll see what else started to work during the past month.
The feature is enabled by default and now the DOCX/DOC/RTF import makes use of it if. This allows stress-testing the layout code with complex user documents, hopefully with the found breakage fixed before it would be released in a stable version.
On the positive side, core.git repository has has 19 files now which are focusing on correct handling of floating tables. Also, there are additional tests that quickly build a specific multi-page floating table in the memory and do some operation on it, e.g. delete the last row and assert what happens.
Here are some screenshots from the effort so far:
Editing of floating tables: delete the last row of a table with 3 rows
The first case is about editing: if a floating table had a first, middle and last page, then deleting the last row of a table lead to incorrect layout, which is now fixed.
Selection & dragging of split floating tables
An odd problem is that the vertical position of tables on non-first pages is generated by the layout, which means that normal drag&move to position them won't work, leading to annoying jumps. This is now fixed by selecting the first (master) fly frame on click, and you can always reposition that table (even vertically.)
Bad binary DOC import
Once DOCX import/export was there, the next step is binary DOC import, which gives us access to a larger corpus of test documents, to stress-test the layout code. This shows how the binary DOC import looked before the work.
Good binary DOC import
And this one shows how it works now.
Good binary DOC export
DOC import is not enough, e.g. Collabora Online will save your documents automatically, so we really want to export everything that is possible to import. Here is how good DOC export looks like in Word.
In-footer floating table
At this point the first crashtest results arrived (we try to import about 280 thousand documents and see what crashes). The first problem was floating tables in footers. Well, we should not try to split such tables (even if they don't fit): adding one more page does not give us more footer space.
Bad RTF import
Similar to the DOC filter, RTF can express floating tables. Here is how we did a bad rendering of an RTF document before.
Good RTF import
And here is how …
Desde la Comunidad hispana de LibreOffice tenemos el gran placer de participar en el congreso esLibre que se celebrará en Zaragoza (España) el 12 y 13 de mayo. Será un gran motivo para encontrarnos en persona con diferentes miembros de …
El día de mañana, la comunidad hispana de LibreOffice celebrará una reunión en línea a partir de las 20:00 UTC.
En este sentido queremos rescatar las palabras del Lic. Carlos Parra Saldivar de Cuba nos decía que “poder escuchar …
Thank you to all who attended our COOL Days 2023 meet up in Cambridge on 28th & 29th March. We had a great time organising the event for our partners, the Collabora team and open source community. It was a great success!
If you didn’t manage to make it to Cambridge, check out our 90 second YouTube short which shows a quick overview of the fun we had.
COOL Days was based at Clare College, the second oldest of the 31 historic Cambridge Colleges. We started off our packed schedule full of lightning talks, partner workshops and team building with a meal at Millworks on the Monday evening (famous for it’s delicious Shawarma!)
Is it possible to fit 45 lightning talks into one day? Yes!
We were live from Cambridge all day on Tuesday 28th March. It was wonderful to see so many presentations of all the work that’s been developing over the last 6 months by the Collabora Online team, community and partners all across Europe and beyond.
For those that would like to re-watch our COOL Days live stream, you can find it on our YouTube channel.
To download the slides from the Technical Talks, head to our github.
Wednesday 29th March was our Partner Day, full of workshops and discussions around our collaborative Partner Programme. It was a privilege to have Simon Phipps and Robert Riemann kick off the day with their insights into the importance of data protection in Europe and future of open source.
Throughout the rest of the day we had many open discussions with our Partners about how we can support them and work together even more successfully and talked about the development road map for 2023.
We made sure there were plenty of opportunities for team building including a treasure hunt around Cambridge, punting down the river Cam and of course, some delicious meals together. On the final evening we dined at Ridley Hall which for many, gave them a taster of what dining at Hogwarts might be like – minus the owls!
You may have seen some of our team live tweeting from the event – search #COOLDays and follow us on Twitter, Mastodon and Linkedin to see updates from events and conferences throughout the year.
We hope to see you at our next COOL Days event.
In the meantime, keep an eye out for where we’ll be next:
June 13, 2023 – Munich, Germany
September 20 - 23, 2023 – Bucharest, Romania
November 7-9, 2023 – Berlin, Germany
The post Recapping COOL Days 2023: The Event that Rocked Cambridge! appeared first on Collabora Office and Collabora Online.
Writer now has the early steps to handle tables that are both floating and span over multiple pages.
This work is primarily for Collabora Online, but is useful on the desktop as well. See the first post for background.
The previous post finished with split rows are now in a reasonable shape towards our journey to fix tdf#61594. In this post, we'll see what else is needed to get perfect rendering for that single document.
The plan is to iterate on that later, adding more and more incremental improvements & fixes for this feature.
The feature is still enabled by default, but the DOCX import only makes use of it if you set the
SW_FORCE_FLY_SPLIT=1 environment variable. This allows playing with the feature even if there are
lots of known problems still.
On the positive side, core.git sw/qa/core/layout/data/ has 12 files now which are rendered exactly
the way Word does. Also, there are additional tests that quickly build a specific multi-page
floating table in the memory and do some operation on it, e.g. delete the last row and assert what
happens.
Here are some screenshots from the effort so far:
Split row and an additional one on 2 pages
Here the problem was that a normal row went to a next page after a split row. Now the document is correctly of 2 pages, instead of the previous unwanted 3 pages.
Floating table with multiple columns
Here the additional complexity was to have multiple columns on a table, since previously we always had 1 column and 2 or more rows. Now these are also split correctly across pages.
Incorrect widow control inside split floating tables
This is an incorrect table row split, because widow control is broken.
Fixed widow control inside split floating tables
And here is how it looks when it's working. That little line on page 2 is no longer alone.
Working minimal height
Even better when the minimal height for non-first ("follow") table frames is working, as you can notice that space between the last line and the table bottom border on page 2.
At this point, the bug document from the motivation section worked fine, apart from the workaround that one has to re-save it in non-legacy mode in Word. So what's next? We need to instantly add a legacy mode for the brand new (not even fully enabled) multi-page floating table feature, since otherwise whatever we do, some DOCX files will be handled incorrectly.
Legacy mode: bad margin
As it turns out, the core of the legacy mode is that the floating table is sometimes allowed to flow into the footer / bottom margin area of the page, but not always. It's quite inconsistent, so one can understand why this is no longer the default behavior. The above is the naive rendering, which is logical, but incorrect.
Legacy mode: good margin
And this is the correct result in legacy mode. After …
Firebird Project announces the first Beta release of Firebird 5.0, the next major version of the Firebird relational database, which is now available for testing.This Beta release arrives with features and improvements already implemented by the Firebird development team, as well as with many bugfixes. Our users are appreciated giving it a try and providing feedback to the development mailing
In every C/C++ source code file, we use header files to put declarations of functions, data types, class, macro and other relevant things inside it. These files have the extension of .h (for C) and .hxx (for C++).
We have different header types: internal and global includes. You can find some of the header files in many places. For example, in LibreOffice we have several modules that many other modules depend on them. Here, we focus on the VCL module. For the global includes, they are placed inside include/ folder, and for internal headers of VCL module, the include files are put inside include/vcl/.
On the other hand, not all the VCL headers are beneficial outside the VCL module. In this case, it is preferred that these include files are put inside the vcl/ folder. Usually, those header files should be inside vcl/inc folder.
As an example, we have the header include/vcl/salnativewidgets.hxx file which have declarations that are not used outside vcl/. In this case, we can put the declarations inside vcl. The suggested place is vcl/inc/nativewidgets.hxx.
As suggested in the bug report, one trick is to look at the class/function declaration. If it doesn’t have a SAL_DLLPUBLIC attribute decorating it, there is good chance that you can move it to the private headers, and in this case, vcl/inc/ folder.
Other than that, you should use the include syntax <…>. For example, if you have created vcl/inc/nativewidgets.hxx, then the include syntax would be:
#include <nativewidgets.hxx>
This is because the file is not exactly next to the cxx file. You can read more here:
EasyHacks are good starting points for someone who wants to start LibreOffice development. This specific issue for improving header files of VCL is avaiable as tdf#97228 in TDF’s Bugzilla. To understand how to start LibreOffice development, you can refer to our getting involved page in the TDF Wiki, or our video tutorial for getting started with LibreOffice development.
Very little actually works, but a working base to start from.
You can compile just fine Firebird 4/5 on Oracle Linux 8 Ampere V1 (arm64) all you need is GCC Toolset 12 enabled as described here .Also same steps work for Oracle Linux 8.x on x86-64. sudo dnf group install "Development Tools" sudo dnf install libicu-devel cmake git sudo dnf install gcc-toolset-12 scl enable gcc-toolset-12 bash git clone https://github.com/FirebirdSQL/firebird.git cd
—Por Judith Ainara
El tema de la firma digital es algo más complejo de lo que parece y lo que comento es una ligera aproximación al tema, independientemente de
Rust Firebird Client updated to v0.23.0 with a few features :Firebird events support added on native client #133 #142Crates.io link is here .Sponsoring Link for Fernando Batels is here .
Por Mike Saunders
Anteriormente hemos hablado con Ximena Alcamán, que trabaja en mejoras al instalador de LibreOffice como parte del programa Outreachy. Outreachy ofrece pasantías a personas sometidas a sesgos sistémicos y que se ven afectadas por la …
Por Mike Saunders
En esta ocasión hemos charlado com Ximena Alcamán, que está trabajando en mejoras al instalador de LibreOffice como parte del programa Outreachy. Outreachy ofrece pasantías para personas sometidas a sesgos sistémicos e impactadas por la …
Recent user guides from the LibreOffice Documentation team are available for free download (PDF, ODT) from the Documentation page on the LibreOffice website, and low-cost printed copies can be purchased from Lulu.com.
LibreOffice 7.4 Draw Guide
LibreOffice 7.5 Writer Guide
LibreOffice 7.5 Calc Guide
LibreOffice uses an internal GUI toolkit, named VCL (Visual Class Library). It creates the GUI widgets for LibreOffice, but it is not generally available for other applications. But there are ways that you can create standalone applications with VCL, at least to learn it better.
If you take a look into the vcl/workben, you will see several workbenches that are actually built during the build process. Previously, we discussed some of them in this post.
Now, I want to discuss the code of the simplest example: minvcl.
It basically creates a simple application with a single window, and that’s all! But even doing that needs several steps. Let’s discuss the code itself.
First come the includes. The include sal/config.h should come with each and every file in LibreOffice, and also VCL. Then, we have several includes from framework, cpppuhelper, comphelper, com/sun/star/lang and com/sun/star/uno, and then language classes from i18nlangtag.
#include <sal/config.h> #include <framework/desktop.hxx> #include <cppuhelper/bootstrap.hxx> #include <comphelper/processfactory.hxx> #include <com/sun/star/lang/XMultiServiceFactory.hpp> #include <com/sun/star/uno/XComponentContext.hpp> #include <i18nlangtag/languagetag.hxx> #include <i18nlangtag/mslangid.hxx>
After that, comes the includes from VCL. We only use two: the one for a VCL application, and another for a VCL window:
#include <vcl/svapp.hxx> #include <vcl/wrkwin.hxx>
Keep in mind that you have to provide the link libraries via the make file. In this case, the make file is vcl/Executable_minvcl.mk:
...
$(eval $(call gb_Executable_use_libraries,minvcl,\
tl \
sal \
vcl \
cppu \
cppuhelper \
comphelper \
i18nlangtag \
fwk \
))...
And at last, the include file for the main function of the VCL application. Every VCL application is supposed to have SAL_IMPLEMENT_MAIN() instead of main(), which is declared in this file.
#include <sal/main.h> #include <iostream>
The class TheApplication should fall into an anonymous namespace. This class inherits the VCL application class with the name of Application. As you can see, we keep a VclPtr to a vcl::Window named mpWin that keeps a pointer to our window.
namespace
{
class TheApplication : public Application
{
public:
virtual int Main();
private:
VclPtr<vcl::Window> mpWin;
};
}
In the main file, we use a method named Create() to create a window. Then, we set the title using SetText(), and then invoke show() to make the window visible on the screen. This is the main file of the VCL application. It is the entry point for the application.
int TheApplication::Main()
{
mpWin = VclPtr<WorkWindow>::Create(nullptr, WB_APP | WB_STDWORK);
mpWin->SetText(u"Minimum VCL application with a window");
mpWin->Show();
Execute();
mpWin.disposeAndClear();
return 0;
}
We use LibreOffice APIs to create a component context and a service manager. The setProcessServiceFactory() function is used to set the service manager for the process. To understand the service manager, you can refer to the DevGuide:
The LanguageTag::setConfiguredSystemLanguage() function sets the language of the application to the system language. Finally, the framework::getDesktop() function …
Writer now has the early steps to handle tables that are both floating and span over multiple pages.
This work is primarily for Collabora Online, but is useful on the desktop as well.
As requested in tdf#61594 10 year ago, the use-case is that you can already have floating tables:
Table in a Writer text frame
And multi-page tables:
Multi-page table
And what we want is a combination of them, like this:
Multi-page floating table
This is a quite complicated feature, since both floating objects and tables are complex, and this combines them to create even more complexity.
However, such constructs are used in existing DOCX files and we're expected to correctly display them.
The feature is enabled by default, but the DOCX import only makes use of it if you set the
SW_FORCE_FLY_SPLIT=1 environment variable. This allows playing with the feature even if there are
lots of known problems still.
On the positive side, core.git sw/qa/core/layout/data/ has 4 files now which are rendered exactly
the way Word does.
A bit of terminology: once a frame is split, the first element of the chain is called master, the remaining frames are called follows.
Here are some screenshots from the journey so far:
Not splitting Writer text frame
This is a fly frame with enough content that it doesn't fit the body frame. It should split, but fly frames could not be split.
Writer text frame kept inside the body frame
First try, just limit the height of the (master) fly frame, so at least it stays inside the body frame. But now some content is not rendered.
Incorrect split of a text frame
Next try. Now have have 2 flys, but the second has zero height and the content of the second fly leaks into the body of the second page.
Last version with bad anchoring
This one is better, but the position of the follow fly frame is bad, no actual wrapping happens. Also, we assume that there are multiple paragraphs after the table, which will cause problems for floating tables at the end of the document. So I reworked the anchoring code to split the anchor to as many pages as necessary...
Duplicated anchor text
Which sounds good, but now the text around the anchor point is duplicated.
Less duplicated anchor text on the first page
Better, now the anchor text is gone in the master anchor, but still there is a misleading paragraph marker.
Last text frame without a table
And now this looks reasonable. Fine, we have some minimal split flys, let's try it with tables instead of just two paragraphs:
Floating table with duplicated anchor text
With a bit of work, the table's two rows can split, but again the text in the anchor is duplicated.
Bad horizontal position
Next try, now the anchor text is correct, but the horizontal position of the table is still bad, it bleeds out …
In this article, I will discuss the recent problems with compiling LibreOffice using Microsoft Visual Studio, things that I did to debug and find the root cause, the source of problem itself – which is problems in Microsoft’s telemetry – and how I could fix it.
Recently, I was encountering a problem when configuring LibreOffice’s source code before compilation. Sometimes, random errors appeared without further details on why. The title: “powershell.exe” was also strange, as I wasn’t using PowerShell directly.
Powershell Error
At first, I ignored the message, but then it become more error common, and at some point the configuration was aborted. I ignored that for a while, but after a few days, one of the mentees reported a somehow similar problem.
The error was that the UCRT (which is Microsoft Visual Studio C++’s standard C library), was not found. This is an error log:
$ ./autogen.sh . . . checking for Windows SDK... found Windows SDK 10.0 (/cygdrive/c/PROGRA~2/WI3CF2~1/10) checking for midl.exe... C:\Program Files (x86)\Windows Kits\10\/Bin/10.0.20348.0/x64/midl.exe checking for csc.exe... C:\Windows\Microsoft.NET\Framework\v4.0.30319\/csc.exe checking for al.exe... C:\Program Files (x86)\Microsoft SDKs\Windows\v10.0A\bin\NETFX 4.8 Tools\/al.exe checking .NET Framework... found: C:/PROGRA~2/WI3CF2~1/NETFXSDK/4.8/ checking whether jumbo sheets are supported... yes checking whether to enable runtime optimizations... yes checking for valgrind/valgrind.h... no checking for sys/sdt.h... no checking what the C++ library is... configure: error: Could not figure out what C++ library this is Error running configure at ./autogen.sh line 321.
The important log that contains the output of the configuration is the config.log file. In this file, I could see these related lines:
... configure:19511: result: no configure:20052: checking what the C++ library is configure:20078: C:/PROGRA~1/MIB055~1/2022/COMMUN~1/VC/Tools/MSVC/1430~1.307/bin/Hostx64/x64/cl.exe -c -IC:/PROGRA~2/WI3CF2~1/10/Include/ucrt -IC:/PROGRA~2/WI3CF2~1/10/Include/ucrt -IC:/PROGRA~1/MIB055~1/2022/COMMUN~1/VC/Tools/MSVC/1430~1.307/Include conftest.cpp >&5 conftest.cpp C:/PROGRA~1/MIB055~1/2022/COMMUN~1/VC/Tools/MSVC/1430~1.307/Include\cstddef(12): fatal error C1083: Cannot open include file: 'stddef.h': No such file or directory Microsoft (R) C/C++ Optimizing Compiler Version 19.30.30711.2 for x64 Copyright (C) Microsoft Corporation. All rights reserved. ...
The strange thing was that I could configure that compilation with another Cygwin terminal with slightly different settings. To find the differences, I used the command export to see the values of the environment variables in the two configured terminals, and compare them using diff.
Then, I found that I could evade the problem by setting this environment variable. This was the environment variable from …
Hoy, martes 21 de febrero, es el Día Internacional de la Lengua Materna de la ONU. Es un día «para abogar por la preservación y protección de todas las lenguas utilizadas por los pueblos del mundo» (https://www.un.org/en/observances/mother-language-day).
La trascendencia del …
Por Mike Saunders
En LibreOffice 7.5 se lanzó un novedoso modo oscuro que se activa de forma automática para coincidir con la configuración del sistema. Pero bastantes personas nos solicitaron un control manual, así que ¡nuestra comunidad de diseño la …
On last Saturday I talked online (using our jitsi) about QA process in LibreOffice for some Russian people who want to be QA engineer in near future. One smart person made the record of my video presentation and now you can watch it on Youtube by link below:
There were around 20 persons there. Some from them now want to try to contribute in LibreOffice project as QA. Let's see =)
| 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. | |