Date: prev next · Thread: first prev next last
May 2023 Archives by date, by thread · List index


lo_daily_tb_win_7-5 - Build # 110 - Fixed:


Check console output at https://ci.libreoffice.org/job/lo_daily_tb_win_7-5/110/ to view the results.

Changes for Build #109
[Caolán McNamara] tdf#155057: Wrong colors in some WPG2 (well rendered in WPG1)

[Xisco Fauli] fix mistake in commit "optimise ensureGeometry"

[Xisco Fauli] tdf#152246 Fix RTL content control field position

[Xisco Fauli] tdf#155077: use the selected URL when writing languages

[Xisco Fauli] tdf#154855 DOCX export: fix <wp:anchor layoutInCell="1"> with

[fitojb] Sync flatpak-manifest.in with Flathub

[Christian Lohmaier] update credits


Changes for Build #110
[Stephan Bergmann] tdf#151715 sfx2: do not use FORCERELOAD for document stored in /tmp

[Michael Stahl] tdf#147526 a macro case which results in a null Lower() result

[Xisco Fauli] tdf#127322 svx: add back MID_GRAPHIC_URL to SvxBrush

[Xisco Fauli] Resolves: tdf#155140 gallery right click for context menu doesn't

[Xisco Fauli] tdf#154478 fix comments empy after ToC
-- 
To unsubscribe e-mail to: libreoffice-ci+unsubscribe@global.libreoffice.org
Problems? https://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/
Posting guidelines + more: https://wiki.documentfoundation.org/Netiquette
List archive: https://listarchives.libreoffice.org/global/libreoffice-ci/
Privacy Policy: https://www.documentfoundation.org/privacy

Context


Privacy Policy | Impressum (Legal Info) | Copyright information: Unless otherwise specified, 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 (MPLv2). "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.