[Libreoffice-bugs] [Bug 147522] Table-based totalization formulas convert to lower-case cell references, while the cells they reference stay in title case (correctly), causing totalizations to fail wi
https://bugs.documentfoundation.org/show_bug.cgi?id=147522 Buovjaga changed: What|Removed |Added Ever confirmed|1 |0 Status|REOPENED|UNCONFIRMED -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 152731] New: Opening a new Impress document from StartCenter gets some warnings in console with debug LO
https://bugs.documentfoundation.org/show_bug.cgi?id=152731 Bug ID: 152731 Summary: Opening a new Impress document from StartCenter gets some warnings in console with debug LO Product: LibreOffice Version: 7.6.0.0 alpha0+ Master Hardware: All OS: All Status: UNCONFIRMED Severity: normal Priority: medium Component: Impress Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: buzea.bog...@libreoffice.org Description: - Open soffice from terminal for a dbg version of LibreOffice. - From the left menu choose Impress Presentation A lot of warnings: warn:vcl.gdi:90642:90642:vcl/source/outdev/font.cxx:1064: Font fallback to the same font, but has missing codes warn:vcl.gdi:90642:90642:vcl/source/outdev/font.cxx:1064: Font fallback to the same font, but has missing codes warn:vcl.gdi:90642:90642:vcl/source/outdev/font.cxx:1064: Font fallback to the same font, but has missing codes warn:vcl.gdi:90642:90642:vcl/source/outdev/font.cxx:1064: Font fallback to the same font, but has missing codes warn:vcl.gdi:90642:90642:vcl/source/outdev/font.cxx:1064: Font fallback to the same font, but has missing codes warn:vcl.gdi:90642:90642:vcl/source/outdev/font.cxx:1064: Font fallback to the same font, but has missing codes warn:vcl.gdi:90642:90642:vcl/source/outdev/font.cxx:1064: Font fallback to the same font, but has missing codes warn:vcl.gdi:90642:90642:vcl/source/outdev/font.cxx:1064: Font fallback to the same font, but has missing codes warn:vcl.gdi:90642:90642:vcl/source/outdev/font.cxx:1064: Font fallback to the same font, but has missing codes warn:vcl.gdi:90642:90642:vcl/source/outdev/font.cxx:1064: Font fallback to the same font, but has missing codes warn:vcl.gdi:90642:90642:vcl/source/outdev/font.cxx:1064: Font fallback to the same font, but has missing codes warn:vcl.gdi:90642:90642:vcl/source/outdev/font.cxx:1064: Font fallback to the same font, but has missing codes warn:vcl.gdi:90642:90642:vcl/source/outdev/font.cxx:1064: Font fallback to the same font, but has missing codes warn:vcl.gdi:90642:90642:vcl/source/outdev/font.cxx:1064: Font fallback to the same font, but has missing codes warn:vcl.gdi:90642:90642:vcl/source/outdev/font.cxx:1064: Font fallback to the same font, but has missing codes warn:vcl.gdi:90642:90642:vcl/source/outdev/font.cxx:1064: Font fallback to the same font, but has missing codes warn:vcl.gdi:90642:90642:vcl/source/outdev/font.cxx:1064: Font fallback to the same font, but has missing codes warn:vcl.gdi:90642:90642:vcl/source/outdev/font.cxx:1064: Font fallback to the same font, but has missing codes warn:sd:90642:90642:sd/source/ui/framework/tools/FrameworkHelper.cxx:210: DBG_UNHANDLED_EXCEPTION in lcl_getViewShell exception: com.sun.star.uno.RuntimeException message: "unsatisfied query for interface of type com.sun.star.lang.XUnoTunnel! at /home/tdf/lode/jenkins/workspace/lo_gerrit/tb/src_master/include/com/sun/star/uno/Reference.hxx:85" warn:sd:90642:90642:sd/source/ui/framework/tools/FrameworkHelper.cxx:210: DBG_UNHANDLED_EXCEPTION in lcl_getViewShell exception: com.sun.star.uno.RuntimeException message: "unsatisfied query for interface of type com.sun.star.lang.XUnoTunnel! at /home/tdf/lode/jenkins/workspace/lo_gerrit/tb/src_master/include/com/sun/star/uno/Reference.hxx:85" warn:sd:90642:90642:sd/source/ui/framework/tools/FrameworkHelper.cxx:210: DBG_UNHANDLED_EXCEPTION in lcl_getViewShell exception: com.sun.star.uno.RuntimeException message: "unsatisfied query for interface of type com.sun.star.lang.XUnoTunnel! at /home/tdf/lode/jenkins/workspace/lo_gerrit/tb/src_master/include/com/sun/star/uno/Reference.hxx:85" warn:sd:90642:90642:sd/source/ui/framework/tools/FrameworkHelper.cxx:210: DBG_UNHANDLED_EXCEPTION in lcl_getViewShell exception: com.sun.star.uno.RuntimeException message: "unsatisfied query for interface of type com.sun.star.lang.XUnoTunnel! at /home/tdf/lode/jenkins/workspace/lo_gerrit/tb/src_master/include/com/sun/star/uno/Reference.hxx:85" warn:sd:90642:90642:sd/source/ui/framework/tools/FrameworkHelper.cxx:210: DBG_UNHANDLED_EXCEPTION in lcl_getViewShell exception: com.sun.star.uno.RuntimeException message: "unsatisfied query for interface of type com.sun.star.lang.XUnoTunnel! at /home/tdf/lode/jenkins/workspace/lo_gerrit/tb/src_master/include/com/sun/star/uno/Reference.hxx:85" warn:sd:90642:90642:sd/source/ui/framework/tools/FrameworkHelper.cxx:210: DBG_UNHANDLED_EXCEPTION in lcl_getViewShell exception: com.sun.star.uno.RuntimeException message: "unsatisfied query for interface of type com.sun.star.lang.XUnoTunnel! at /home/tdf/lode/jenkins/workspace/lo_gerrit/tb/src_master/include/com/sun/star/uno/Reference.hxx:85" Steps to Reproduce: see description Actual Results: warnings Expected Results: no warnings Reproducible: Always User Profile Reset: Yes Additional Info: Version: 7.6.0.0.alpha0+ (X86_64)
[Libreoffice-bugs] [Bug 152730] New: Trying to open a file from StartCenter gets some warnings in console with debug LO
https://bugs.documentfoundation.org/show_bug.cgi?id=152730 Bug ID: 152730 Summary: Trying to open a file from StartCenter gets some warnings in console with debug LO Product: LibreOffice Version: 7.6.0.0 alpha0+ Master Hardware: All OS: All Status: UNCONFIRMED Severity: normal Priority: medium Component: LibreOffice Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: buzea.bog...@libreoffice.org Description: - Open soffice from terminal for a dbg version of LibreOffice. - Press Open from the left option (to open an existing file), but don't open anything... I get this messages from terminal: warn:sfx.dialog:79868:79868:sfx2/source/dialog/filtergrouping.cxx:359: already have an element for WordPerfect warn:sfx.dialog:79868:79868:sfx2/source/dialog/filtergrouping.cxx:359: already have an element for writerweb8_writer_template warn:sfx.dialog:79868:79868:sfx2/source/dialog/filtergrouping.cxx:359: already have an element for writerglobal8 warn:vcl.gtk:79868:79868:vcl/unx/gtk3/fpicker/SalGtkFilePicker.cxx:955: no parent widget set Steps to Reproduce: see description Actual Results: warnings Expected Results: no warnings Reproducible: Always User Profile Reset: Yes Additional Info: Version: 7.6.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: b9e3e20bfd102880d12384892eaeca094c38a519 CPU threads: 16; OS: Linux 5.15; UI render: default; VCL: gtk3 Locale: ro-RO (ro_RO.UTF-8); UI: en-US Calc: threaded -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 152729] New: Save a new Calc file gets some warnings in console with debug LO
https://bugs.documentfoundation.org/show_bug.cgi?id=152729 Bug ID: 152729 Summary: Save a new Calc file gets some warnings in console with debug LO Product: LibreOffice Version: 7.6.0.0 alpha0+ Master Hardware: All OS: All Status: UNCONFIRMED Severity: normal Priority: medium Component: Calc Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: buzea.bog...@libreoffice.org Description: Open scalc from terminal for a dbg version of LibreOffice. Save the file. Messages from terminal: warn:xmloff:46901:46901:xmloff/source/style/impastpl.cxx:379: Adding duplicate family table-column with mismatching mapper ! P25SvXMLExportPropertyMapper 25SvXMLExportPropertyMapper warn:xmloff:46901:46901:xmloff/source/style/impastpl.cxx:379: Adding duplicate family table-row with mismatching mapper ! P25SvXMLExportPropertyMapper 25SvXMLExportPropertyMapper warn:xmloff:46901:46901:xmloff/source/style/impastpl.cxx:379: Adding duplicate family table-cell with mismatching mapper ! P25SvXMLExportPropertyMapper 28XMLShapeExportPropertyMapper warn:editeng:46901:46901:editeng/source/uno/unofield.cxx:386: Id service unknown: 5 warn:editeng:46901:46901:editeng/source/uno/unofield.cxx:386: Id service unknown: 2 warn:editeng:46901:46901:editeng/source/uno/unofield.cxx:386: Id service unknown: 5 warn:editeng:46901:46901:editeng/source/uno/unofield.cxx:386: Id service unknown: 2 warn:xmloff:46901:46901:xmloff/source/style/impastpl.cxx:379: Adding duplicate family table-column with mismatching mapper ! P25SvXMLExportPropertyMapper 25SvXMLExportPropertyMapper warn:xmloff:46901:46901:xmloff/source/style/impastpl.cxx:379: Adding duplicate family table-row with mismatching mapper ! P25SvXMLExportPropertyMapper 25SvXMLExportPropertyMapper warn:xmloff:46901:46901:xmloff/source/style/impastpl.cxx:379: Adding duplicate family table-cell with mismatching mapper ! P25SvXMLExportPropertyMapper 28XMLShapeExportPropertyMapper warn:legacy.osl:46901:46901:xmloff/source/core/SettingsExportHelper.cxx:176: this type is not implemented now Steps to Reproduce: see description Actual Results: warnings Expected Results: no warnings Reproducible: Always User Profile Reset: Yes Additional Info: Version: 7.6.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: b9e3e20bfd102880d12384892eaeca094c38a519 CPU threads: 16; OS: Linux 5.15; UI render: default; VCL: gtk3 Locale: ro-RO (ro_RO.UTF-8); UI: en-US Calc: threaded -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 152728] New: Print Preview in a new Calc file gets some warnings in console with debug LO
https://bugs.documentfoundation.org/show_bug.cgi?id=152728 Bug ID: 152728 Summary: Print Preview in a new Calc file gets some warnings in console with debug LO Product: LibreOffice Version: 7.6.0.0 alpha0+ Master Hardware: All OS: All Status: UNCONFIRMED Severity: normal Priority: medium Component: Calc Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: buzea.bog...@libreoffice.org Description: - Open scalc from terminal for a dbg version of LibreOffice. - type anything in any cell and press Print Preview icon I get this messages in the terminal warn:legacy.osl:46901:46901:sc/source/ui/view/tabvwshh.cxx:232: no accessibility broadcaster? warn:legacy.osl:46901:46901:sc/source/ui/view/tabvwshh.cxx:232: no accessibility broadcaster? warn:legacy.osl:46901:46901:sc/source/ui/view/tabvwshh.cxx:232: no accessibility broadcaster? warn:legacy.osl:46901:46901:sc/source/ui/view/tabvwshh.cxx:232: no accessibility broadcaster? warn:legacy.osl:46901:46901:sc/source/ui/view/tabvwshh.cxx:232: no accessibility broadcaster? warn:legacy.osl:46901:46901:sc/source/ui/view/tabvwshh.cxx:232: no accessibility broadcaster? warn:legacy.osl:46901:46901:sc/source/ui/view/tabvwshh.cxx:232: no accessibility broadcaster? Steps to Reproduce: see description Actual Results: warnings Expected Results: no warnings Reproducible: Always User Profile Reset: Yes Additional Info: Version: 7.6.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: b9e3e20bfd102880d12384892eaeca094c38a519 CPU threads: 16; OS: Linux 5.15; UI render: default; VCL: gtk3 Locale: ro-RO (ro_RO.UTF-8); UI: en-US Calc: threaded -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 150339] Wrong type for text color: Property not convertible
https://bugs.documentfoundation.org/show_bug.cgi?id=150339 --- Comment #6 from BogdanB --- Caolan, I get a similar warn in Calc warn:legacy.osl:46901:46901:svl/source/items/custritm.cxx:70: CntUnencodedStringItem::PutValue(): Wrong type warn:sfx:46901:46901:sfx2/source/appl/appuno.cxx:310: Property not convertible: Color Should I open a new bug or they shared the same code? -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 152727] New: Opening a new Calc gets some warnings in console with debug LO
https://bugs.documentfoundation.org/show_bug.cgi?id=152727 Bug ID: 152727 Summary: Opening a new Calc gets some warnings in console with debug LO Product: LibreOffice Version: 7.6.0.0 alpha0+ Master Hardware: All OS: All Status: UNCONFIRMED Severity: normal Priority: medium Component: Calc Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: buzea.bog...@libreoffice.org Description: Open scalc from terminal for a dbg version of LibreOffice. I get the messages: warn:sfx.control:46901:46901:sfx2/source/control/dispatch.cxx:1206: Childwindow slot missing: 25917 warn:sfx.control:46901:46901:sfx2/source/control/dispatch.cxx:1206: Childwindow slot missing: 26189 warn:sfx.control:46901:46901:sfx2/source/control/dispatch.cxx:1206: Childwindow slot missing: 26190 warn:sfx.control:46901:46901:sfx2/source/control/dispatch.cxx:1206: Childwindow slot missing: 25917 warn:sfx.control:46901:46901:sfx2/source/control/dispatch.cxx:1206: Childwindow slot missing: 26189 warn:sfx.control:46901:46901:sfx2/source/control/dispatch.cxx:1206: Childwindow slot missing: 26190 warn:vcl.schedule:46901:46901:vcl/source/app/scheduler.cxx:606: Stop the task before changing the priority, as it will just change after the task was scheduled with the old prio! Steps to Reproduce: See description Actual Results: Warnings Expected Results: No warnings Reproducible: Always User Profile Reset: Yes Additional Info: Version: 7.6.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: b9e3e20bfd102880d12384892eaeca094c38a519 CPU threads: 16; OS: Linux 5.15; UI render: default; VCL: gtk3 Locale: ro-RO (ro_RO.UTF-8); UI: en-US Calc: threaded -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 68419] FORMATTING: Paragraph borders are not merged between two pages
https://bugs.documentfoundation.org/show_bug.cgi?id=68419 Cashmagnet changed: What|Removed |Added URL||https://coupondiscountfreed ||eal.com --- Comment #17 from Cashmagnet --- CashMagnet.com, where you will find exclusive coupon codes and deals. With our exclusive offers, you can save money on a wide range of products and services by using https://coupondiscountfreedeal.com coupon codes. We hope you find the information helpful. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 125093] Windows: Honor "Zone.Identifier" stream, and open files from restricted zones in read-only mode
https://bugs.documentfoundation.org/show_bug.cgi?id=125093 Commit Notification changed: What|Removed |Added Whiteboard||target:7.6.0 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 125093] Windows: Honor "Zone.Identifier" stream, and open files from restricted zones in read-only mode
https://bugs.documentfoundation.org/show_bug.cgi?id=125093 --- Comment #6 from Commit Notification --- Vasily Melenchuk committed a patch related to this issue. It has been pushed to "master": https://git.libreoffice.org/core/commit/b22bbfa25ab1f0b9cfa1dedc85b8f9874f0a5e5b Related: tdf#125093 Check Windows Security Zones for macros It will be available in 7.6.0. The patch should be included in the daily builds available at https://dev-builds.libreoffice.org/daily/ in the next 24-48 hours. More information about daily builds can be found at: https://wiki.documentfoundation.org/Testing_Daily_Builds Affected users are encouraged to test the fix and report feedback. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-commits] core.git: officecfg/registry sfx2/source sw/CppunitTest_sw_odfimport.mk sw/qa
officecfg/registry/schema/org/openoffice/Office/Common.xcs | 125
sfx2/source/doc/docmacromode.cxx | 57 +
sw/CppunitTest_sw_odfimport.mk |8
sw/qa/extras/odfimport/data/ZoneMacroTest.odt |binary
sw/qa/extras/odfimport/odfimport.cxx | 130 +
5 files changed, 320 insertions(+)
New commits:
commit b22bbfa25ab1f0b9cfa1dedc85b8f9874f0a5e5b
Author: Vasily Melenchuk
AuthorDate: Mon Dec 5 20:32:41 2022 +0300
Commit: Thorsten Behrens
CommitDate: Fri Dec 30 04:24:27 2022 +
Related: tdf#125093 Check Windows Security Zones for macros
In Windows, files get assigned security zones (local, from intranet,
from internet, etc) after download via browser or email client. This
is used by MS Word to decide in which mode it is safe to open file.
This patch implements basic support for similar feature: by default
there are no changes in macro behavior. But it is possible to use
expert configuration options to tweak default behavior, and for
example disable macros automatically, if a file is downloaded from
Internet or other unsafe locations.
Change-Id: I0bf1ae4e54d75dd5d07cab309124a67a85ef2d4d
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/143680
Tested-by: Jenkins
Reviewed-by: Thorsten Behrens
diff --git a/officecfg/registry/schema/org/openoffice/Office/Common.xcs
b/officecfg/registry/schema/org/openoffice/Office/Common.xcs
index 023ed391bfe1..f333657151f5 100644
--- a/officecfg/registry/schema/org/openoffice/Office/Common.xcs
+++ b/officecfg/registry/schema/org/openoffice/Office/Common.xcs
@@ -2814,6 +2814,131 @@
List with trusted authors.
+
+
+Contains security settings regarding Basic scripts.
+
+
+
+ Action needed for opening document with macro with Windows
zone
+ identifier URLZONE_LOCAL_MACHINE (0, local machine).
+
+
+
+
+ Ask
+
+
+
+
+ Allow
+
+
+
+
+ Deny
+
+
+
+0
+
+
+
+ Action needed for opening document with macro with Windows
zone
+ identifier URLZONE_INTRANET (1, local machine).
+
+
+
+
+ Ask
+
+
+
+
+ Allow
+
+
+
+
+ Deny
+
+
+
+0
+
+
+
+ Action needed for opening document with macro with Windows
zone
+ identifier URLZONE_TRUSTED (2, trusted).
+
+
+
+
+ Ask
+
+
+
+
+ Allow
+
+
+
+
+ Deny
+
+
+
+0
+
+
+
+ Action needed for opening document with macro with Windows
zone
+ identifier URLZONE_INTERNET (3, internet).
+
+
+
+
+ Ask
+
+
+
+
+ Allow
+
+
+
+
+ Deny
+
+
+
+0
+
+
+
+ Action needed for opening document with macro with Windows
zone
+ identifier URLZONE_UNTRUSTED (3, untrusted source).
+
+
+
+
+ Ask
+
+
+
+
+ Allow
+
+
+
+
+ Deny
+
+
+
+0
+
+
diff --git a/sfx2/source/doc/docmacromode.cxx b/sfx2/source/doc/docmacromode.cxx
index bdae350b22f5..cbd720132323 100644
--- a/sfx2/source/doc/docmacromode.cxx
+++ b/sfx2/source/doc/docmacromode.cxx
@@ -38,6 +38,10 @@
#include
#include
+#if defined(_WIN32)
+#include
+#include
+#endif
namespace sfx2
{
@@ -284,6 +288,59 @@ namespace sfx2
}
}
+#if defined(_WIN32)
+// Windows specific: try to decide macros loading depending on Windows
Security Zones
[Libreoffice-bugs] [Bug 152726] Pasting Selection Range to Sheet as BMP Image, Font size of Button Control increases.
https://bugs.documentfoundation.org/show_bug.cgi?id=152726 nobu changed: What|Removed |Added Version|7.0.0.3 release |7.3.0.3 release -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 152714] Exporting Selected Range in JPG, Position of the Shape is out of place.
https://bugs.documentfoundation.org/show_bug.cgi?id=152714 nobu changed: What|Removed |Added See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=15 ||2726 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 152726] Pasting Selection Range to Sheet as BMP Image, Font size of Button Control increases.
https://bugs.documentfoundation.org/show_bug.cgi?id=152726 nobu changed: What|Removed |Added See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=15 ||2714 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 152726] Pasting Selection Range to Sheet as BMP Image, Font size of Button Control increases.
https://bugs.documentfoundation.org/show_bug.cgi?id=152726 nobu changed: What|Removed |Added Summary|When Selection Range is |Pasting Selection Range to |pasted to Sheet with BMP, |Sheet as BMP Image, Font |Font size of the button |size of Button Control |increases. |increases. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 149413] record macro is gone
https://bugs.documentfoundation.org/show_bug.cgi?id=149413 --- Comment #5 from QA Administrators --- Dear Iat_Johnny, Please read this message in its entirety before proceeding. Your bug report is being closed as INSUFFICIENTDATA due to inactivity and a lack of information which is needed in order to accurately reproduce and confirm the problem. We encourage you to retest your bug against the latest release. If the issue is still present in the latest stable release, we need the following information (please ignore any that you've already provided): a) Provide details of your system including your operating system and the latest version of LibreOffice that you have confirmed the bug to be present b) Provide easy to reproduce steps – the simpler the better c) Provide any test case(s) which will help us confirm the problem d) Provide screenshots of the problem if you think it might help e) Read all comments and provide any requested information Once all of this is done, please set the bug back to UNCONFIRMED and we will attempt to reproduce the issue. Please do not: a) respond via email b) update the version field in the bug or any of the other details on the top section of our bug tracker Warm Regards, QA Team MassPing-NeedInfo-FollowUp -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 152529] Theme colour gets clipped on an ultrawide screen
https://bugs.documentfoundation.org/show_bug.cgi?id=152529 QA Administrators changed: What|Removed |Added Whiteboard|| QA:needsComment -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 152534] Dark Mode on Windows 11 Active selections from the tabbed menu bar have light blue backgrond which makes the white icon alsmost invisible
https://bugs.documentfoundation.org/show_bug.cgi?id=152534 QA Administrators changed: What|Removed |Added Whiteboard|| QA:needsComment -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 152527] Exchange presentation with presenter console does not move the presenter console in windowed mode
https://bugs.documentfoundation.org/show_bug.cgi?id=152527 QA Administrators changed: What|Removed |Added Whiteboard|| QA:needsComment -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 152528] Closing the windowed presenter console does nothing
https://bugs.documentfoundation.org/show_bug.cgi?id=152528 QA Administrators changed: What|Removed |Added Whiteboard|| QA:needsComment -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 152513] FORMATTING: Enhancement request [Custom Layouts]
https://bugs.documentfoundation.org/show_bug.cgi?id=152513 QA Administrators changed: What|Removed |Added Whiteboard|| QA:needsComment -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 149410] When set Conditional Format in a cell (color) it changes the colour of all of the cells
https://bugs.documentfoundation.org/show_bug.cgi?id=149410 --- Comment #3 from QA Administrators --- Dear Federico, Please read this message in its entirety before proceeding. Your bug report is being closed as INSUFFICIENTDATA due to inactivity and a lack of information which is needed in order to accurately reproduce and confirm the problem. We encourage you to retest your bug against the latest release. If the issue is still present in the latest stable release, we need the following information (please ignore any that you've already provided): a) Provide details of your system including your operating system and the latest version of LibreOffice that you have confirmed the bug to be present b) Provide easy to reproduce steps – the simpler the better c) Provide any test case(s) which will help us confirm the problem d) Provide screenshots of the problem if you think it might help e) Read all comments and provide any requested information Once all of this is done, please set the bug back to UNCONFIRMED and we will attempt to reproduce the issue. Please do not: a) respond via email b) update the version field in the bug or any of the other details on the top section of our bug tracker Warm Regards, QA Team MassPing-NeedInfo-FollowUp -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 149413] record macro is gone
https://bugs.documentfoundation.org/show_bug.cgi?id=149413 QA Administrators changed: What|Removed |Added Resolution|--- |INSUFFICIENTDATA Status|NEEDINFO|RESOLVED -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 149410] When set Conditional Format in a cell (color) it changes the colour of all of the cells
https://bugs.documentfoundation.org/show_bug.cgi?id=149410 QA Administrators changed: What|Removed |Added Status|NEEDINFO|RESOLVED Resolution|--- |INSUFFICIENTDATA -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 147148] Paste in Writer loses Source Format
https://bugs.documentfoundation.org/show_bug.cgi?id=147148 --- Comment #4 from QA Administrators --- Dear Digi Abros, Please read this message in its entirety before proceeding. Your bug report is being closed as INSUFFICIENTDATA due to inactivity and a lack of information which is needed in order to accurately reproduce and confirm the problem. We encourage you to retest your bug against the latest release. If the issue is still present in the latest stable release, we need the following information (please ignore any that you've already provided): a) Provide details of your system including your operating system and the latest version of LibreOffice that you have confirmed the bug to be present b) Provide easy to reproduce steps – the simpler the better c) Provide any test case(s) which will help us confirm the problem d) Provide screenshots of the problem if you think it might help e) Read all comments and provide any requested information Once all of this is done, please set the bug back to UNCONFIRMED and we will attempt to reproduce the issue. Please do not: a) respond via email b) update the version field in the bug or any of the other details on the top section of our bug tracker Warm Regards, QA Team MassPing-NeedInfo-FollowUp -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 95228] FILEOPEN DOCX Textboxes overlap
https://bugs.documentfoundation.org/show_bug.cgi?id=95228 --- Comment #7 from QA Administrators --- Dear Scott, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 92363] FORMATTING & TABLE: Insert page break (Ctrl + Enter) and insert paragraph (Alt + Enter) before table does not work after page break
https://bugs.documentfoundation.org/show_bug.cgi?id=92363 --- Comment #4 from QA Administrators --- Dear Gordo, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 91723] UI: File Properties Dialog width changes with length of Created and Modified
https://bugs.documentfoundation.org/show_bug.cgi?id=91723 --- Comment #4 from QA Administrators --- Dear Gordo, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 139279] Writter does not properly export cropped picture to PDF on Windows
https://bugs.documentfoundation.org/show_bug.cgi?id=139279 --- Comment #5 from QA Administrators --- Dear artragis, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 91323] UI: Status Bar will not stay on after using Print Preview with it turned off
https://bugs.documentfoundation.org/show_bug.cgi?id=91323 --- Comment #6 from QA Administrators --- Dear Gordo, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 63497] BASIC: BASIC-error after opening XLS
https://bugs.documentfoundation.org/show_bug.cgi?id=63497 --- Comment #7 from QA Administrators --- Dear markus, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 139254] Zero on y axis of graph in scalc is not shown as zero but as very small number close to zero with many digits
https://bugs.documentfoundation.org/show_bug.cgi?id=139254 --- Comment #3 from QA Administrators --- Dear snowboard975, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 119659] LOOKUP function >> application crashes, if "Result vector" argument is array of constant with at least 1 empty cell, and search value is out of vector
https://bugs.documentfoundation.org/show_bug.cgi?id=119659 --- Comment #16 from QA Administrators --- Dear Andrey, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 115190] Template manager shows extension on OOXML templates
https://bugs.documentfoundation.org/show_bug.cgi?id=115190 --- Comment #7 from QA Administrators --- Dear Gabor Kelemen, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 114947] FORMATTING: Context Menu, Font Colour / Color
https://bugs.documentfoundation.org/show_bug.cgi?id=114947 --- Comment #5 from QA Administrators --- Dear Colin, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 147522] Table-based totalization formulas convert to lower-case cell references, while the cells they reference stay in title case (correctly), causing totalizations to fail wi
https://bugs.documentfoundation.org/show_bug.cgi?id=147522 aev changed: What|Removed |Added Resolution|NOTABUG |--- Status|RESOLVED|REOPENED Ever confirmed|0 |1 --- Comment #7 from aev --- The problem is that after converting from the Excel sheet, in which the references and formulas work, to a Calc sheet, the formulas fail. It means that during the conversion, something went wrong. As Miguel pointed out: Calc can do it when using labels. If that is what is needed to keep the formulas working, then the conversion should have made that happen. The end user (me) should not have to worry about such things. Converting from the most important competition should work flawlessly. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 152714] Exporting Selected Range in JPG, Position of the Shape is out of place.
https://bugs.documentfoundation.org/show_bug.cgi?id=152714 m.a.riosv changed: What|Removed |Added Status|UNCONFIRMED |NEW Ever confirmed|0 |1 CC||miguelangelrv@libreoffice.o ||rg --- Comment #3 from m.a.riosv --- Reproducible Version: 7.6.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: 376152fbd110cdc0a2cde1fa9758f36c016d9352 CPU threads: 4; OS: Windows 10.0 Build 19045; UI render: Skia/Raster; VCL: win Locale: es-ES (es_ES); UI: en-US Calc: CL threaded Jumbo -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 152723] NatNum12 modifier, in the Spanish locales that have comma as decimal separator, the format spell out point not coma.
https://bugs.documentfoundation.org/show_bug.cgi?id=152723 m.a.riosv changed: What|Removed |Added Summary|NatNum12 modifier, in the |NatNum12 modifier, in the |Spanish locales, that have |Spanish locales that have |comma as decimal separator, |comma as decimal separator, |the format spell out point |the format spell out point |not coma. |not coma. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 152725] I propose a new function for Writer - Marginalia (i.e. sidenotes)
https://bugs.documentfoundation.org/show_bug.cgi?id=152725 --- Comment #1 from s.bu...@o2.pl --- Created attachment 184392 --> https://bugs.documentfoundation.org/attachment.cgi?id=184392=edit Preview of proposed solutions - example of comments and sidenotes (marginalia) -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 145988] macOS skia: colors not displayed correctly for all document previews e.g. start center or impress templates
https://bugs.documentfoundation.org/show_bug.cgi?id=145988 --- Comment #58 from Patrick Luby --- (In reply to خالد حسني from comment #57) > With Skia/Metal: https://paste.debian.net/1265585/ > With Skia/Raster: https://paste.debian.net/1265583/ Thank you for running the patch. The bad news, your output is the same as mine: both machines are using the same pixel format and alpha types. Looking at the Skia source is a bit overwhelming so I am going to see if I can implement a test when loading Skia/Metal. @Luboš Luñák already does a test at launch so if can detect something unique on machines that have this bug, I can then force LibreOffice to switch to Skia/Raster. The following patch prints out some debug messages that will tell me if your machine has drawn red, green, blue, or alpha in an unexpected byte within the pixel: https://gerrit.libreoffice.org/c/core/+/144814/5 Can you apply the patch and post the Terminal messages? There should only be 8 messages: ./instdir/LibreOfficeDev.app/Contents/MacOS/soffice 2>&1 | grep vcl.skia.colortest -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-commits] core.git: Branch 'distro/lhm/libreoffice-6-1+backports' - officecfg/registry sfx2/source
officecfg/registry/schema/org/openoffice/Office/Common.xcs | 125 +
sfx2/source/doc/docmacromode.cxx | 56 +
2 files changed, 180 insertions(+), 1 deletion(-)
New commits:
commit f6bcd6eea8a8b0c75193c99e806ce48c007fa58d
Author: Thorsten Behrens
AuthorDate: Thu Dec 29 23:08:43 2022 +0100
Commit: Thorsten Behrens
CommitDate: Fri Dec 30 00:33:51 2022 +
Support for Windows Security Zones for macro enable/disable
In Windows, files have security zones (local, from intranet, from
internet, etc) used by MS Word to decide in which mode it is safe to
open file.
This patch implements basic support for similar feature: it is now
possible to use expert configuration options to set up default
behavior and configure for example automatic disabling of macros, if
a file is downloaded from Internet or other unsafe location.
Changed defaults: files from untrusted zones, or the internet, get
macros disabled unconditionally. Can be overridden via
officecfg::Office::Common::Security::Scripting::WindowsSecurityZone.*
in the expert config dialog.
Change-Id: I0bf1ae4e54d75dd5d07cab309124a67a85ef2d4d
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/143750
Tested-by: Thorsten Behrens
Reviewed-by: Thorsten Behrens
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/144871
diff --git a/officecfg/registry/schema/org/openoffice/Office/Common.xcs
b/officecfg/registry/schema/org/openoffice/Office/Common.xcs
index fb627eba4317..8c9add931d14 100644
--- a/officecfg/registry/schema/org/openoffice/Office/Common.xcs
+++ b/officecfg/registry/schema/org/openoffice/Office/Common.xcs
@@ -2707,6 +2707,131 @@
List with trusted authors.
+
+
+Contains security settings regarding Basic scripts.
+
+
+
+ Action needed for opening document with macro with Windows
zone
+ identifier URLZONE_LOCAL_MACHINE (0, local machine).
+
+
+
+
+ Ask
+
+
+
+
+ Allow
+
+
+
+
+ Deny
+
+
+
+0
+
+
+
+ Action needed for opening document with macro with Windows
zone
+ identifier URLZONE_INTRANET (1, local machine).
+
+
+
+
+ Ask
+
+
+
+
+ Allow
+
+
+
+
+ Deny
+
+
+
+0
+
+
+
+ Action needed for opening document with macro with Windows
zone
+ identifier URLZONE_TRUSTED (2, trusted).
+
+
+
+
+ Ask
+
+
+
+
+ Allow
+
+
+
+
+ Deny
+
+
+
+0
+
+
+
+ Action needed for opening document with macro with Windows
zone
+ identifier URLZONE_INTERNET (3, internet).
+
+
+
+
+ Ask
+
+
+
+
+ Allow
+
+
+
+
+ Deny
+
+
+
+2
+
+
+
+ Action needed for opening document with macro with Windows
zone
+ identifier URLZONE_UNTRUSTED (3, untrusted source).
+
+
+
+
+ Ask
+
+
+
+
+ Allow
+
+
+
+
+ Deny
+
+
+
+2
+
+
diff --git a/sfx2/source/doc/docmacromode.cxx b/sfx2/source/doc/docmacromode.cxx
index ea0d46babdfa..58edfba428c9 100644
--- a/sfx2/source/doc/docmacromode.cxx
+++ b/sfx2/source/doc/docmacromode.cxx
@@ -38,6 +38,10 @@
#include
#include
+#if defined(_WIN32)
+#include
+#include
+#endif
namespace sfx2
{
@@ -286,7 +290,57 @@ namespace sfx2
}
}
-// conformation is required
+#if defined(_WIN32)
+// Windows specific: try to decide
[Libreoffice-commits] core.git: Branch 'distro/lhm/libreoffice-6-4+backports' - sw/source
sw/source/core/inc/flyfrms.hxx |1 +
sw/source/core/layout/flylay.cxx | 13 +
2 files changed, 14 insertions(+)
New commits:
commit 148c938020f5467b78da37a5045672635e2e3afa
Author: Michael Stahl
AuthorDate: Tue Dec 20 21:04:05 2022 +0100
Commit: Thorsten Behrens
CommitDate: Fri Dec 30 00:33:01 2022 +
tdf#146875 sw: move also at-frame flys off SwPageFrame
The bugdoc contains an at-frame anchored fly on page 77, which is
anchored to an at-page anchored fly.
While layouting page 74, the fly is moved to page 77, and the content on
page 74 invalidated.
Unexpectedly, calling RegisterAtPage on a SwFlyLayFrame does absolutely
nothing, as it calls the base class SwFlyFrame, so the fly stays on page
74.
Thus, page 74 never actually becomes valid, and later pages are never
layouted.
(regression from commit eb85de8e6b61fb3fcb6c03ae0145f7fe5478bccf)
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/144631
Tested-by: Jenkins
Reviewed-by: Michael Stahl
(cherry picked from commit abef9ea8aa99561e6f84451acf387abde4ec14ab)
Change-Id: I4fcbed4daf83f9e554de5a877a40b2c2419c0f2f
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/144759
Tested-by: Thorsten Behrens
Reviewed-by: Thorsten Behrens
diff --git a/sw/source/core/inc/flyfrms.hxx b/sw/source/core/inc/flyfrms.hxx
index 04b505ddd548..cb94b7cbd259 100644
--- a/sw/source/core/inc/flyfrms.hxx
+++ b/sw/source/core/inc/flyfrms.hxx
@@ -151,6 +151,7 @@ public:
SwFlyLayFrame( SwFlyFrameFormat*, SwFrame*, SwFrame *pAnchor );
+virtual void RegisterAtPage(SwPageFrame &) override;
protected:
virtual void Modify( const SfxPoolItem*, const SfxPoolItem* ) override;
};
diff --git a/sw/source/core/layout/flylay.cxx b/sw/source/core/layout/flylay.cxx
index 4a7030ea241e..c915ee82d95a 100644
--- a/sw/source/core/layout/flylay.cxx
+++ b/sw/source/core/layout/flylay.cxx
@@ -723,6 +723,19 @@ SwFlyLayFrame::SwFlyLayFrame( SwFlyFrameFormat *pFormat,
SwFrame* pSib, SwFrame
m_bLayout = true;
}
+void SwFlyLayFrame::RegisterAtPage(SwPageFrame & rPageFrame)
+{
+assert(GetPageFrame() != );
+if (GetPageFrame())
+{
+GetPageFrame()->MoveFly( this, );
+}
+else
+{
+rPageFrame.AppendFlyToPage( this );
+}
+}
+
// #i28701#
void SwFlyLayFrame::Modify( const SfxPoolItem* pOld, const SfxPoolItem *pNew )
[Libreoffice-bugs] [Bug 152726] When Selection Range is pasted to Sheet with BMP, Font size of the button increases.
https://bugs.documentfoundation.org/show_bug.cgi?id=152726 --- Comment #1 from nobu --- Created attachment 184391 --> https://bugs.documentfoundation.org/attachment.cgi?id=184391=edit sample file -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 152726] New: When Selection Range is pasted to Sheet with BMP, Font size of the button increases.
https://bugs.documentfoundation.org/show_bug.cgi?id=152726 Bug ID: 152726 Summary: When Selection Range is pasted to Sheet with BMP, Font size of the button increases. Product: LibreOffice Version: 7.0.0.3 release Hardware: All OS: All Status: UNCONFIRMED Severity: normal Priority: medium Component: Calc Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: tac...@hotmail.co.jp Description: When Selection Range is pasted to Sheet with BMP, Font size of the button increases. Steps to Reproduce: 1. Open a new Calc. 2. Place the Shape (ex. Button) in Cell [B1]. 3. Control Title is Default. 4. Select Range [A1:B1] & Copy. 5. Move the cursor somewhere. 6. Paste Image in BMP using PasteDropdownIcon. Actual Results: 7. The text of the button is getting bigger. Expected Results: 7. The text on the button does not grow. Reproducible: Always User Profile Reset: No Additional Info: There is a similar Bug in PNG. Not Reproduced with before Version 7.2.7.2 64bit, OS:Windows10 64bit Reproducible with Version 7.3.0.3 32bit, OS:Windows10 64bit Reproducible with Version 7.5.0.1 64bit, OS:Windows10 64bit -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 152714] Exporting Selected Range in JPG, Position of the Shape is out of place.
https://bugs.documentfoundation.org/show_bug.cgi?id=152714 nobu changed: What|Removed |Added Summary|Exporting Selected Range in |Exporting Selected Range in |JPG, Shapes placed below|JPG, Position of the Shape |are greatly shifted.|is out of place. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 152725] New: I propose a new function for Writer - Marginalia (i.e. sidenotes)
https://bugs.documentfoundation.org/show_bug.cgi?id=152725 Bug ID: 152725 Summary: I propose a new function for Writer - Marginalia (i.e. sidenotes) Product: LibreOffice Version: 7.4.3.2 release Hardware: All OS: All Status: UNCONFIRMED Severity: enhancement Priority: medium Component: Writer Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: s.bu...@o2.pl Description: I suggest that Marginalia (i.e. sidenotes) be added automatically (like as well as footnotes and endnotes), at the same height as the anchoring to the word / phrase to which it refers. This will allow you to index sidenotes, etc. This feature is used by language publications. The second proposal is that in the "comment" view it is possible to leave only the comment itself - without the author and the time of attaching the comment. I often publish documents in pdf form and it is very unprofessional if the comment window contains information about the author, time, etc. In some types of documents, nothing more than the view of the comment itself is recommended (so it would be very helpful for many user if they could manually disable the visibility of unnecessary information in the comment window) Steps to Reproduce: 1. Marginalia - no simple tool to insert them 2. Comments - it is not possible to enable the view of the comment itself (without the view of the author, time of adding the comment, etc.) Actual Results: Marginalia (sidenotes) - currently you can manually add a text field, but you have to edit it every time, it is not always possible to arrange everything vertically (with 200-300 sidenotes it is a big problem). This can be solved by adding comments (however, the visibility of information about the author of the comment, about the time it was turned on, makes such a publication/digital document look very unprofessional) Expected Results: 1.For Marginalia (sidenotes) - so that they can be turned on and handled like e.i. footnotes. Possibly without numbering. In the event that marginalia will occur, you can include a vertical line (black or colored) separating the main document from the sidenotes. Alternatively, over time, an option to include color in the margins where there are sidenotes can be included. 2.In the case of "comments" - to add an option in the comments options - turn off the view of the author, - turn off the view of the comment's adding time, - turn on the view of the comment content only) Reproducible: Always User Profile Reset: No Additional Info: The case applies to all LibreOffice releases. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 152712] Support setting style attributes relative to parent style
https://bugs.documentfoundation.org/show_bug.cgi?id=152712 --- Comment #3 from Eyal Rozenberg --- (In reply to Mike Kaganski from comment #1) > (In reply to Eyal Rozenberg from comment #0) > > we can't apply multiple styles at once, see 149271.) > > This is not correct ... So the > feature for that style category exists - but indeed, the UI has much to > improve (basically, to create from scratch). Yes, you're right, I should have said "we can't effectively apply". > > 1. Multiplicative relation of numeric attributes. Example: "Font weight at > > 125% of the parent style" > > This is already possible. See [1]: That's only one single feature, in one (or two) kinds of style. I'm talking about all of them. Like: Vertical space after paragraph. > Any > feature should only be created to implement some specific need, not just > because we can. The specific need is being able to define styles progressively as one moves down the hierarchy. With my example above: I want to be able to increase or decrease the spacing after all Heading N lines, with each of them increasing by the same factor. I can't do that right now. > The overall complexity makes every new feature a source of > problems for quite large number of users, so unless this solves a real > problem for many users, I disagree that we should do this. I am actually betting that this is not complex as an ODF feature. But - I realize this could potentially be quite complex in terms of the UI. There are different avenues for dealing with the expression of such complexity, which merit discussion IMO; at worst, there could be an ability for advanced users to edit a textual or semi-textual representation of the everything the style changes relative to its parent (similar to what we currently have in read-only form in the organizer), and in this representation, the relative-ease of the ODF level could be more readily expressed. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-ux-advise] [Bug 152712] Support setting style attributes relative to parent style
https://bugs.documentfoundation.org/show_bug.cgi?id=152712 --- Comment #3 from Eyal Rozenberg --- (In reply to Mike Kaganski from comment #1) > (In reply to Eyal Rozenberg from comment #0) > > we can't apply multiple styles at once, see 149271.) > > This is not correct ... So the > feature for that style category exists - but indeed, the UI has much to > improve (basically, to create from scratch). Yes, you're right, I should have said "we can't effectively apply". > > 1. Multiplicative relation of numeric attributes. Example: "Font weight at > > 125% of the parent style" > > This is already possible. See [1]: That's only one single feature, in one (or two) kinds of style. I'm talking about all of them. Like: Vertical space after paragraph. > Any > feature should only be created to implement some specific need, not just > because we can. The specific need is being able to define styles progressively as one moves down the hierarchy. With my example above: I want to be able to increase or decrease the spacing after all Heading N lines, with each of them increasing by the same factor. I can't do that right now. > The overall complexity makes every new feature a source of > problems for quite large number of users, so unless this solves a real > problem for many users, I disagree that we should do this. I am actually betting that this is not complex as an ODF feature. But - I realize this could potentially be quite complex in terms of the UI. There are different avenues for dealing with the expression of such complexity, which merit discussion IMO; at worst, there could be an ability for advanced users to edit a textual or semi-textual representation of the everything the style changes relative to its parent (similar to what we currently have in read-only form in the organizer), and in this representation, the relative-ease of the ODF level could be more readily expressed. -- You are receiving this mail because: You are on the CC list for the bug.
[Libreoffice-bugs] [Bug 149271] Support composition of multiple styles of the same kind
https://bugs.documentfoundation.org/show_bug.cgi?id=149271 --- Comment #3 from Eyal Rozenberg --- (In reply to Mike Kaganski from comment #2) > I don't see what aggregation of several styles of the same category could > mean for a style category like paragraph, where styles by definition define > every single property Well, not if you consider inheritance. > (either directly, or by inheritance). Ah, but that's the point. If we have styles A, B, C with B and C inheriting A, then applying B and C means applying both the changes B makes to A and the changes C makes to A. Naturally there's the question of conflicts. This can be settled either by order of application (i.e. search orders C,B,A or B,C,A with the A being implicit), or arbitrarily, i.e. the app doesn't guarantee which of B and C's changes would be used, and it's the user's problem. Since all styles inherit from the Default Style of their kind, we don't have the problem of multiple inheritance-roots. For a concrete example, think of Default Page Style, RTL page, and a DecorativeFrame style. Each of the child styles only defines what its name suggests. The composition would be "RTL, DecorativeFrame" (or the other way around, doesn't matter). -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-commits] core.git: sw/qa writerfilter/source
sw/qa/extras/rtfexport/data/invalidParagraphStyle.rtf | 14 ++
sw/qa/extras/rtfexport/rtfexport3.cxx |9 +
writerfilter/source/dmapper/DomainMapper_Impl.cxx | 10 +-
3 files changed, 32 insertions(+), 1 deletion(-)
New commits:
commit d5a9722874871576b864feb7bd815f9f8bfaac48
Author: Vasily Melenchuk
AuthorDate: Wed Dec 28 23:52:10 2022 +0300
Commit: Thorsten Behrens
CommitDate: Thu Dec 29 22:39:55 2022 +
ms format import: better handling for invalid styles
If referred paragraph style is not found or it is not a paragraph
style, this can lead to exceptions in writer core and thus current
paragraph can be not corretly initialized. For example, numbering
can be not applied because of exception of not found style earlier.
This is not a critical error, we should just not apply a style
we could not resolve.
Of course such documents are invalid but bit more tolerance to errors
will not harm.
Change-Id: I9150786e6357a7d6098440bac29ec501fc6aa802
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/144852
Tested-by: Jenkins
Reviewed-by: Thorsten Behrens
diff --git a/sw/qa/extras/rtfexport/data/invalidParagraphStyle.rtf
b/sw/qa/extras/rtfexport/data/invalidParagraphStyle.rtf
new file mode 100644
index ..cb5ec80eb3cf
--- /dev/null
+++ b/sw/qa/extras/rtfexport/data/invalidParagraphStyle.rtf
@@ -0,0 +1,14 @@
+{\rtf1
+
+{\stylesheet
+{\cs30\fs72 Super Duper Style;}}
+
+{\*\listtable
+{\list
+{\listlevel\levelstartat1{\leveltext\'02\'00.;}{\levelnumbers\'01;}}
+{\listname ;}\listid1235362366}}
+{\*\listoverridetable{\listoverride\listid1235362366\listoverridecount0\ls1}}
+
+\pard\s30\ls1\fs24 AAA BBB CCC\par
+
+}
diff --git a/sw/qa/extras/rtfexport/rtfexport3.cxx
b/sw/qa/extras/rtfexport/rtfexport3.cxx
index 90adb69f2bf7..6c1a4d524b7f 100644
--- a/sw/qa/extras/rtfexport/rtfexport3.cxx
+++ b/sw/qa/extras/rtfexport/rtfexport3.cxx
@@ -514,6 +514,15 @@ CPPUNIT_TEST_FIXTURE(Test, testTdf127806)
CPPUNIT_ASSERT_EQUAL(static_cast(635), aSize.Width);
}
+DECLARE_RTFEXPORT_TEST(testInvalidParagraphStyle, "invalidParagraphStyle.rtf")
+{
+// Given test has character style #30, but referred as paragraph style #30
+// This was causing exception in finishParagraph(), so numbering and other
+// properties were not applied. Ensure numbering is still here
+sal_Int16 numFormat = getNumberingTypeOfParagraph(1);
+CPPUNIT_ASSERT_EQUAL(style::NumberingType::ARABIC, numFormat);
+}
+
CPPUNIT_PLUGIN_IMPLEMENT();
/* vim:set shiftwidth=4 softtabstop=4 expandtab: */
diff --git a/writerfilter/source/dmapper/DomainMapper_Impl.cxx
b/writerfilter/source/dmapper/DomainMapper_Impl.cxx
index 377c133c8192..668f7f6758fe 100644
--- a/writerfilter/source/dmapper/DomainMapper_Impl.cxx
+++ b/writerfilter/source/dmapper/DomainMapper_Impl.cxx
@@ -1946,13 +1946,21 @@ void DomainMapper_Impl::finishParagraph( const
PropertyMapPtr& pPropertyMap, con
#endif
const StyleSheetEntryPtr pEntry =
GetStyleSheetTable()->FindStyleSheetByConvertedStyleName(
GetCurrentParaStyleName() );
-OSL_ENSURE( pEntry, "no style sheet found" );
+SAL_WARN_IF(!pEntry, "writerfilter.dmapper", "no style sheet found");
const StyleSheetPropertyMap* pStyleSheetProperties = pEntry ?
pEntry->pProperties.get() : nullptr;
sal_Int32 nListId = pParaContext ? pParaContext->props().GetListId() : -1;
bool isNumberingViaStyle(false);
bool isNumberingViaRule = nListId > -1;
if ( !bRemove && pStyleSheetProperties && pParaContext )
{
+if (!pEntry || pEntry->nStyleTypeCode != StyleType::STYLE_TYPE_PARA) {
+// We could not resolve paragraph style or it is not a paragraph
style
+// Remove this style reference, otherwise it will cause exceptions
during further
+// processing and not all paragraph styles will be initialized.
+SAL_WARN("writerfilter.dmapper", "Paragraph style is incorrect.
Ignored");
+pParaContext->Erase(PROP_PARA_STYLE_NAME);
+}
+
bool bNumberingFromBaseStyle = false;
if (!isNumberingViaRule)
nListId = lcl_getListId(pEntry, GetStyleSheetTable(),
bNumberingFromBaseStyle);
[Libreoffice-bugs] [Bug 142468] LibreOffice randomly hangs on macOS Big Sur 2020 MacBook Air M1
https://bugs.documentfoundation.org/show_bug.cgi?id=142468 --- Comment #20 from M-Rick --- I tried this development version : Version: 7.5.0.1.0+ (X86_64) / LibreOffice Community Build ID: 1e6e59f874b219d2ff3c8363a69ce7ba6a44bc1c CPU threads: 4; OS: Mac OS X 12.6.2; UI render: default; VCL: osx Locale: fr-FR (fr_FR.UTF-8); UI: fr-FR Calc: threaded It doesn't freeze anymore. It began to happen when I upgraded macOS to Monterey. I used my 48 Mb settings folder that used to make LibreOffice hanging after a few minutes, and nothing happened during these last 2 days. I am even surprised for its stability for a development version. It remains to check if this version works well on a Mx Mac as well. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 150707] Saving a new document gets some warnings in console with debug LO
https://bugs.documentfoundation.org/show_bug.cgi?id=150707 Caolán McNamara changed: What|Removed |Added Ever confirmed|0 |1 Status|UNCONFIRMED |NEW --- Comment #4 from Caolán McNamara --- I can reproduce with dbgutil: speculative fix at https://gerrit.libreoffice.org/c/core/+/144870 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 152575] PDF Export prints comments only to the margin of the first page
https://bugs.documentfoundation.org/show_bug.cgi?id=152575 BogdanB changed: What|Removed |Added Status|NEEDINFO|NEW --- Comment #13 from BogdanB --- Sorry for noise, I remove all my wrong comments. Not working with Version: 7.5.0.0.alpha1+ (X86_64) / LibreOffice Community Build ID: ad085990b8073a122ac5222e5220f8f1d6826dcf CPU threads: 16; OS: Linux 5.15; UI render: default; VCL: gtk3 Locale: ro-RO (ro_RO.UTF-8); UI: en-US Calc: threaded Neither with Version: 7.6.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: ad387d5b984c906505d25685065f710ed55d CPU threads: 16; OS: Linux 5.15; UI render: default; VCL: gtk3 Locale: ro-RO (ro_RO.UTF-8); UI: en-US Calc: threaded -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 133573] Footnotes Alignment not saved in RTF files
https://bugs.documentfoundation.org/show_bug.cgi?id=133573 --- Comment #10 from fra...@slacky.it --- Hi, I confirm the perdurance of this bug in LibreOffice 7.4.2.3 on Linux and in 7.4.3.2 for Windows -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 34391] FORMATTING: Introduce table cell styles
https://bugs.documentfoundation.org/show_bug.cgi?id=34391 --- Comment #29 from Eyal Rozenberg --- (In reply to Xisco Faulí from comment #28) > Changing enhancement priority to 'high' since the number of people in CC is > higher than 20 So, 3 years has passed, and now 36 users are in the CC list. Perhaps it is time to consider another measure... what do you think about possibly adding this to the list of potential tenders for 2023? -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 152724] New: FILEOPEN FORMATTING Cell custom Format Code is changed (or not saved correctly) when reopening ods file
https://bugs.documentfoundation.org/show_bug.cgi?id=152724 Bug ID: 152724 Summary: FILEOPEN FORMATTING Cell custom Format Code is changed (or not saved correctly) when reopening ods file Product: LibreOffice Version: 7.4.3.2 release Hardware: x86-64 (AMD64) OS: Windows (All) Status: UNCONFIRMED Severity: normal Priority: medium Component: Calc Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: adylo811...@gmail.com Description: After saving and closing an .ods file in Calc, when the file is opened again the custom Format Code that was used before has now changed. Either it was not saved correctly, or some "automatic" process is changing it when opening the file. Steps to Reproduce: 1_ Fill a column with the following values (one value in each row/cell): -12 12 0 1 2 -1 -2 2_ Select the column and change the font type to some mono-spaced (i.e. fixed-pitch, fixed-width, or non-proportional) font (e.g. Liberation Mono, Source Code Pro, Courier New, Consolas, Lucida Console, ...). 3_ Select "Align center" for the column. 4_ (Ctrl+1) Format -> Cell -> Numbers -> (custom) Format Code field: _-?0;-?0 (underscore, minus, question mark, zero, semicolon, minus, question mark, zero) 5_ Please note that, under the above conditions, these (whole) numbers are (correctly) shown "aligned", even-though the font alignment for the cells is (intentionally) "center", with the negative sign also aligned, and the zero value is also displayed. At this point, save and _close_ the workbook. 6_ Reopen the workbook and notice the following changes: 6.1_ The values are not shown "aligned" (in the sense they were before). The font alignment is still "center", but the contents are not shown in the same way they were before saving_and_closing the file. 6.2_ The zero value is not shown. 6.3_ The custom Format Code (Ctrl+1) has changed, without user knowledge / intervention: 6.3.1_ Before: _-?0;-?0 6.3.2_ After: " "#;-# 7_ Select the column. 8_ (Ctrl+1): change the Format Code to: _-?0;-?0;_-?0 (please note the additional third section, for zero). 9_ Save and Close. 10_ Reopen the workbook and notice the following changes (again): 10.1_ The values are not shown "aligned" (in the sense they were before). The font alignment is still "center", but the contents are not shown the same way they were before saving_and_closing the file. 10.2_ The zero value is not shown. 10.3_ The custom Format Code (Ctrl+1) has changed, without user knowledge / intervention: 10.3.1_ Before: __-?0;-?0;_-?0 10.3.2_ After: [>0]" "#;[<0]-#;" "# At the moment of writing, the reference for "Number Format Codes" in LO 7.4 is: https://help.libreoffice.org/7.4/en-US/text/shared/01/05020301.html Actual Results: Custom Format Code is not preserved after closing the file. In particular, the underscore_and_minus is being changed, and the "question_mark" and "zero" are being changed to "#". Expected Results: Custom Format Code should be preserved as the user introduced it and saved, not changed. Reproducible: Always User Profile Reset: No Additional Info: Version: 7.4.3.2 (x64) / LibreOffice Community Build ID: 1048a8393ae2eeec98dff31b5c133c5f1d08b890 CPU threads: 4; OS: Windows 10.0 Build 19044; UI render: Skia/Raster; VCL: win Locale: es-AR (es_AR); UI: en-US Calc: CL -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 152723] NatNum12 modifier, in the Spanish locales, that have comma as decimal separator, the format spell out point not coma.
https://bugs.documentfoundation.org/show_bug.cgi?id=152723 --- Comment #1 from m.a.riosv --- Created attachment 184390 --> https://bugs.documentfoundation.org/attachment.cgi?id=184390=edit Sample file showing the issue. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 152723] New: NatNum12 modifier, in the Spanish locales, that have comma as decimal separator, the format spell out point not coma.
https://bugs.documentfoundation.org/show_bug.cgi?id=152723 Bug ID: 152723 Summary: NatNum12 modifier, in the Spanish locales, that have comma as decimal separator, the format spell out point not coma. Product: LibreOffice Version: 7.6.0.0 alpha0+ Master Hardware: All OS: All Status: UNCONFIRMED Severity: normal Priority: medium Component: Localization Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: miguelange...@libreoffice.org With NatNum12 modifier, in the Spanish locales, that have comma as decimal separator, the format spell out point not coma. 12,55 'Spanish (Spain)' '[NatNum12 capitalize]0,00' 'Doce punto cincuenta y cinco' should be 'Doce coma cincuenta y cinco' -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 152722] NatNum12 number format (spell out): add/delete decimal places is loosing format
https://bugs.documentfoundation.org/show_bug.cgi?id=152722 m.a.riosv changed: What|Removed |Added Status|UNCONFIRMED |NEW CC||miguelangelrv@libreoffice.o ||rg Ever confirmed|0 |1 --- Comment #2 from m.a.riosv --- Reproducible. Version: 7.6.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: 376152fbd110cdc0a2cde1fa9758f36c016d9352 CPU threads: 4; OS: Windows 10.0 Build 19045; UI render: Skia/Raster; VCL: win Locale: es-ES (es_ES); UI: en-US Calc: CL threaded Jumbo But works by adding the decimals by hand. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-commits] core.git: sc/source
sc/source/core/tool/ddelink.cxx |3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) New commits: commit 37723413115baafdc7d13ad26d11aa5f917c2036 Author: Mike Kaganski AuthorDate: Thu Dec 29 17:53:42 2022 + Commit: Mike Kaganski CommitDate: Thu Dec 29 20:10:50 2022 + tdf#152717: ScDdeLink::DataChanged may get OUString directly ... after commit 94df17f58fe6269452b7252b712a89978c444bec (tdf#151429: don't convert OUStrings to system encoding, 2022-10-08) Change-Id: Ie9d6eb2a4465a576eefe0840a30636e898fa9028 Reviewed-on: https://gerrit.libreoffice.org/c/core/+/144810 Tested-by: Jenkins Reviewed-by: Mike Kaganski diff --git a/sc/source/core/tool/ddelink.cxx b/sc/source/core/tool/ddelink.cxx index 95591dddb461..775c71808488 100644 --- a/sc/source/core/tool/ddelink.cxx +++ b/sc/source/core/tool/ddelink.cxx @@ -130,7 +130,8 @@ sfx2::SvBaseLink::UpdateResult ScDdeLink::DataChanged( return SUCCESS; OUString aLinkStr; -ScByteSequenceToString::GetString( aLinkStr, rValue, osl_getThreadTextEncoding() ); +if (!(rValue >>= aLinkStr)) +ScByteSequenceToString::GetString( aLinkStr, rValue, osl_getThreadTextEncoding() ); aLinkStr = convertLineEnd(aLinkStr, LINEEND_LF); // if string ends with line end, discard:
[Libreoffice-commits] core.git: Branch 'libreoffice-7-5' - vcl/inc vcl/Library_vcl.mk vcl/quartz vcl/skia
vcl/Library_vcl.mk | 12 ++ vcl/inc/quartz/cgutils.h | 34 +++ vcl/inc/quartz/salbmp.h| 12 -- vcl/inc/salbmp.hxx | 23 + vcl/inc/skia/quartz/cgutils.h | 40 vcl/inc/skia/salbmp.hxx|7 + vcl/quartz/AquaGraphicsBackend.cxx | 169 ++--- vcl/quartz/cgutils.mm | 73 +++ vcl/quartz/salbmp.cxx | 115 ++--- vcl/skia/osx/gdiimpl.cxx | 23 - vcl/skia/quartz/salbmp.mm | 107 +++ 11 files changed, 323 insertions(+), 292 deletions(-) New commits: commit 1675ed7816c9078a8fbc744afab76e206634fc3a Author: Patrick Luby AuthorDate: Sun Dec 25 10:17:01 2022 -0500 Commit: Xisco Fauli CommitDate: Thu Dec 29 19:55:46 2022 + Related: tdf#146842 Eliminate temporary copies of SkiaSalBitmap when printing Commit 9eb732a32023e74c44ac8c3b5af9f5424273bb6c fixed crashing when printing SkiaSalBitmaps to a non-Skia SalGraphics. However, the fix almost always makes two copies of the SkiaSalBitmap's bitmap data: the first copy is made in SkiaSalBitmap::AcquireBuffer() and then QuartzSalBitmap makes a copy of the first copy. By making QuartzSalBitmap's methods that return a CGImageRef pure virtual, a non-Skia SalGraphics can now create a CGImageRef directly from a SkiaSalBitmap's Skia bitmap data without copying to any intermediate buffers. Change-Id: If6ab7f175889cb4839d8a2461b7be7671e575c08 Reviewed-on: https://gerrit.libreoffice.org/c/core/+/144856 Tested-by: Jenkins Reviewed-by: Noel Grandin Signed-off-by: Xisco Fauli Reviewed-on: https://gerrit.libreoffice.org/c/core/+/144864 Reviewed-by: Patrick Luby diff --git a/vcl/Library_vcl.mk b/vcl/Library_vcl.mk index cff520ccb03f..7b985b13711c 100644 --- a/vcl/Library_vcl.mk +++ b/vcl/Library_vcl.mk @@ -682,6 +682,12 @@ ifeq ($(OS),iOS) $(eval $(call gb_Library_add_cxxflags,vcl,\ $(gb_OBJCXXFLAGS) \ )) +$(eval $(call gb_Library_add_objcxxobjects,vcl,\ +vcl/quartz/cgutils \ +$(if $(filter SKIA,$(BUILD_TYPE)), \ +vcl/skia/quartz/salbmp \ +) \ +)) $(eval $(call gb_Library_add_exception_objects,vcl,\ vcl/ios/iosinst \ vcl/ios/dummies \ @@ -707,6 +713,12 @@ endif ifeq ($(OS),MACOSX) +$(eval $(call gb_Library_add_objcxxobjects,vcl,\ +vcl/quartz/cgutils \ +$(if $(filter SKIA,$(BUILD_TYPE)), \ +vcl/skia/quartz/salbmp \ +) \ +)) $(eval $(call gb_Library_use_system_darwin_frameworks,vcl,\ Cocoa \ CoreFoundation \ diff --git a/vcl/inc/quartz/cgutils.h b/vcl/inc/quartz/cgutils.h new file mode 100644 index ..6c499448c721 --- /dev/null +++ b/vcl/inc/quartz/cgutils.h @@ -0,0 +1,34 @@ +/* -*- Mode: C++; tab-width: 4; indent-tabs-mode: nil; c-basic-offset: 4 -*- */ +/* + * This file is part of the LibreOffice project. + * + * This Source Code Form is subject to the terms of the Mozilla Public + * License, v. 2.0. If a copy of the MPL was not distributed with this + * file, You can obtain one at http://mozilla.org/MPL/2.0/. + * + * This file incorporates work covered by the following license notice: + * + * Licensed to the Apache Software Foundation (ASF) under one or more + * contributor license agreements. See the NOTICE file distributed + * with this work for additional information regarding copyright + * ownership. The ASF licenses this file to you under the Apache + * License, Version 2.0 (the "License"); you may not use this file + * except in compliance with the License. You may obtain a copy of + * the License at http://www.apache.org/licenses/LICENSE-2.0 . + */ + +#pragma once + +#include + +#include +#include +#include + +class SalBitmap; + +CGImageRef VCL_DLLPUBLIC CreateWithSalBitmapAndMask(const SalBitmap& rBitmap, +const SalBitmap& rMask, int nX, int nY, +int nWidth, int nHeight); + +/* vim:set shiftwidth=4 softtabstop=4 expandtab: */ diff --git a/vcl/inc/quartz/salbmp.h b/vcl/inc/quartz/salbmp.h index 459a2b528f99..8f4e6a34ee1c 100644 --- a/vcl/inc/quartz/salbmp.h +++ b/vcl/inc/quartz/salbmp.h @@ -30,9 +30,6 @@ #include #include #include -#if HAVE_FEATURE_SKIA -#include -#endif #include @@ -64,9 +61,6 @@ public: boolCreate( const SalBitmap& rSalBmp ) override; boolCreate( const SalBitmap& rSalBmp, SalGraphics* pGraphics ) override; boolCreate( const SalBitmap& rSalBmp, vcl::PixelFormat eNewPixelFormat) override; -#if HAVE_FEATURE_SKIA -boolCreate( const SkiaSalBitmap& rSkiaSalBmp, const SalTwoRect& rPosAry ); -#endif virtual boolCreate( const css::uno::Reference< css::rendering::XBitmapCanvas >& rBitmapCanvas, Size& rSize,
[Libreoffice-commits] core.git: Branch 'libreoffice-7-5' - vcl/quartz
vcl/quartz/salbmp.cxx |2 +- 1 file changed, 1 insertion(+), 1 deletion(-) New commits: commit 8cc9a76bdd94ddc0e20a20f3b312883864f8c346 Author: Andrea Gelmini AuthorDate: Sun Dec 11 21:48:41 2022 +0100 Commit: Xisco Fauli CommitDate: Thu Dec 29 19:55:03 2022 + Fix typo Change-Id: Ifd46201254b8a5db1d21d99d469d331688e8731c Reviewed-on: https://gerrit.libreoffice.org/c/core/+/143952 Tested-by: Jenkins Reviewed-by: Adolfo Jayme Barrientos Signed-off-by: Xisco Fauli Reviewed-on: https://gerrit.libreoffice.org/c/core/+/144863 diff --git a/vcl/quartz/salbmp.cxx b/vcl/quartz/salbmp.cxx index cd191482f5aa..05b5093bafc1 100644 --- a/vcl/quartz/salbmp.cxx +++ b/vcl/quartz/salbmp.cxx @@ -123,7 +123,7 @@ bool QuartzSalBitmap::Create( const SkiaSalBitmap& rSalBmp, const SalTwoRect& rP // Ugly but necessary to acquire the bitmap buffer because all of the // SalBitmap instances that callers pass are already const. At least we -// only need to read, not write to the bitmap paramter. +// only need to read, not write to the bitmap parameter. SkiaSalBitmap& rSkiaSalBmp = const_cast( rSalBmp ); BitmapBuffer *pSrcBuffer = rSkiaSalBmp.AcquireBuffer( BitmapAccessMode::Read );
[Libreoffice-bugs] [Bug 150339] Wrong type for text color: Property not convertible
https://bugs.documentfoundation.org/show_bug.cgi?id=150339 Caolán McNamara changed: What|Removed |Added CC||szymon.k...@collabora.com --- Comment #5 from Caolán McNamara --- https://gerrit.libreoffice.org/c/core/+/144866 might do it, but then something else presumably is using "Color" that might need to be adjusted to use "ColorString" ? -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 152722] NatNum12 number format (spell out): add/delete decimal places is loosing format
https://bugs.documentfoundation.org/show_bug.cgi?id=152722 --- Comment #1 from Laurent Balland --- Entry point: https://opengrok.libreoffice.org/s?defs=ChangeNumFmtDecimals=core -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 152722] New: NatNum12 number format (spell out): add/delete decimal places is loosing format
https://bugs.documentfoundation.org/show_bug.cgi?id=152722 Bug ID: 152722 Summary: NatNum12 number format (spell out): add/delete decimal places is loosing format Product: LibreOffice Version: 7.5.0.0 beta1+ Hardware: All OS: All Status: UNCONFIRMED Severity: normal Priority: medium Component: Calc Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: jumbo4...@yahoo.fr When changing the number of decimal places with add/delete buttons or with sidebar or with cell number format dialog, of a number format based on NatNum12 (spell out), number format looses NatNum12 flag. Steps to reproduce: 1. In Calc, open dialog Format > Cells > Numbers 2. Select Category: Number, Format: "one hundred" Number format code is now: [NatNum12 cardinal]0 3. Increment Decimal places Actual behavior: NatNum12 flag is lost and number format code is now 0.0 Expected behavior: NatNum12 flag should be kept with expected number format code: [NatNum12 cardinal]0.0 Same behavior with Add or Delete decimal places buttons, and with side bar panel. Workaround: Manually modify number format code in dialog. Display is then correct. Version: 7.5.0.0.beta1 (X86_64) / LibreOffice Community Build ID: 3aca23eec42e9d6fbe57071d7633ae1fc4bc5fcc CPU threads: 8; OS: Windows 10.0 Build 19045; UI render: Skia/Vulkan; VCL: win Locale: fr-FR (fr_FR); UI: fr-FR Calc: CL threaded Confirmed with 7.5.0.1 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 151757] Changing the spacing of RTL tables messes up the spacing of the entire table
https://bugs.documentfoundation.org/show_bug.cgi?id=151757 --- Comment #3 from William Friedman --- Reconfirmed with 7.4.3.2. This is almost certainly a regression in 7.3, but I am unable to check older versions. Are there others who can be tagged to check this? This bug severely impacts working with RTL tables, to the point that they are completely unusable if any formatting needs to be changed. Thank you. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 103030] [META] Navigator sidebar deck and floating window
https://bugs.documentfoundation.org/show_bug.cgi?id=103030 Bug 103030 depends on bug 149815, which changed state. Bug 149815 Summary: As character anchored frames are called shapes in navigator after docx export https://bugs.documentfoundation.org/show_bug.cgi?id=149815 What|Removed |Added Status|NEW |RESOLVED Resolution|--- |NOTABUG -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 149815] As character anchored frames are called shapes in navigator after docx export
https://bugs.documentfoundation.org/show_bug.cgi?id=149815 Gabor Kelemen (allotropia) changed: What|Removed |Added CC||kelem...@ubuntu.com Status|NEW |RESOLVED Resolution|--- |NOTABUG --- Comment #4 from Gabor Kelemen (allotropia) --- (In reply to Roman Kuznetsov from comment #3) > Possibly it is not a bug at all Indeed, the frames are saved as drawing objects to docx, this is a known limitation of docx support and differences between Writer/Word frames and shapes. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 142381] DOCX export: Table behind chart regression when reopen in LO (OK in MSO)
https://bugs.documentfoundation.org/show_bug.cgi?id=142381 Gabor Kelemen (allotropia) changed: What|Removed |Added CC||kelem...@ubuntu.com See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=11 ||2313 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 112313] FILESAVE Text below image moves up next to it when file saved as DOCX
https://bugs.documentfoundation.org/show_bug.cgi?id=112313 Gabor Kelemen (allotropia) changed: What|Removed |Added See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=14 ||2381 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 107553] [META] Writer table styles bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=107553 Stéphane Guillou (stragu) changed: What|Removed |Added Depends on||152711 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=152711 [Bug 152711] Make Writer table styles _proper_ styles -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 107326] [META] Writer style bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=107326 Stéphane Guillou (stragu) changed: What|Removed |Added Depends on|152711 | Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=152711 [Bug 152711] Make Writer table styles _proper_ styles -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 49437] Writer/Calc: Use XML for serializing table autoformats instead of the current brittle binary format
https://bugs.documentfoundation.org/show_bug.cgi?id=49437 Stéphane Guillou (stragu) changed: What|Removed |Added Blocks||152711 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=152711 [Bug 152711] Make Writer table styles _proper_ styles -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 152711] Make Writer table styles _proper_ styles
https://bugs.documentfoundation.org/show_bug.cgi?id=152711 Stéphane Guillou (stragu) changed: What|Removed |Added CC||stephane.guillou@libreoffic ||e.org Blocks|107326 |107553 Ever confirmed|0 |1 Status|UNCONFIRMED |NEW Depends on||49437 --- Comment #4 from Stéphane Guillou (stragu) --- There is a relevant conversation around the work that recently made Table Designs editable in Impress/Draw: https://gerrit.libreoffice.org/c/core/+/141825/4#message-60f3292076828cfc8544059b4c264b8cf1a2f22c Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=49437 [Bug 49437] Writer/Calc: Use XML for serializing table autoformats instead of the current brittle binary format https://bugs.documentfoundation.org/show_bug.cgi?id=107326 [Bug 107326] [META] Writer style bugs and enhancements https://bugs.documentfoundation.org/show_bug.cgi?id=107553 [Bug 107553] [META] Writer table styles bugs and enhancements -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 152717] DDE linking in calc is broken since 7.4.3 RC1
https://bugs.documentfoundation.org/show_bug.cgi?id=152717 Mike Kaganski changed: What|Removed |Added Status|NEW |ASSIGNED Assignee|libreoffice-b...@lists.free |mikekagan...@hotmail.com |desktop.org | --- Comment #3 from Mike Kaganski --- https://gerrit.libreoffice.org/c/core/+/144810 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 152721] New: variable x is not used
https://bugs.documentfoundation.org/show_bug.cgi?id=152721 Bug ID: 152721 Summary: variable x is not used Product: cppunit Version: unspecified Hardware: All OS: All Status: UNCONFIRMED Severity: normal Priority: medium Component: General Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: ifrahidre...@gmail.com CC: markus.mohrh...@googlemail.com jjfc -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-commits] core.git: include/svx
include/svx/ColorSets.hxx |6 ++
1 file changed, 6 insertions(+)
New commits:
commit f0ff9162950487f1e7ccc01e01160d60bf102488
Author: Caolán McNamara
AuthorDate: Thu Dec 29 12:15:28 2022 +
Commit: Caolán McNamara
CommitDate: Thu Dec 29 16:57:29 2022 +
cid#1518241 Improper use of negative value
and
cid#1518243 Improper use of negative value
cid#1518244 Improper use of negative value
Change-Id: I82de403d833d931703d52a368aa0b467abffa54b
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/144861
Tested-by: Jenkins
Reviewed-by: Caolán McNamara
diff --git a/include/svx/ColorSets.hxx b/include/svx/ColorSets.hxx
index 6b4504ebb877..47e1d8866e5d 100644
--- a/include/svx/ColorSets.hxx
+++ b/include/svx/ColorSets.hxx
@@ -15,6 +15,7 @@
#include
#include
+#include
#include
#include
#include
@@ -68,6 +69,11 @@ public:
Color getColor(ThemeColorType nType) const
{
+if (nType == ThemeColorType::Unknown)
+{
+SAL_WARN("svx", "ColorSet::getColor with ThemeColorType::Unknown");
+return COL_AUTO;
+}
return maColors[size_t(nType)];
}
[Libreoffice-bugs] [Bug 152706] TRANSLATION: Error message when trying to use new translation feature
https://bugs.documentfoundation.org/show_bug.cgi?id=152706 Dieter changed: What|Removed |Added Status|UNCONFIRMED |NEW Ever confirmed|0 |1 --- Comment #5 from Dieter --- (In reply to Sebastiaan Veld from comment #4) > Sorry, misread the issue: so -yes- I have the same issue as I reported as > part of bug 152247: => NEW -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 152575] PDF Export prints comments only to the margin of the first page
https://bugs.documentfoundation.org/show_bug.cgi?id=152575 --- Comment #12 from devsepp...@gmail.com --- @BogdanB, the procedure you are describing is for regular printing (or for using third party PDF printing software). This bug report is about the LibreOffice native PDF export File->Export As->Export as PDF The regular comment printing to margins works fine, it is the PDF Export that is the problem. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 152720] Spreadsheet closes while scrolling thumb
https://bugs.documentfoundation.org/show_bug.cgi?id=152720 --- Comment #2 from Larry Hinsley --- Created attachment 184389 --> https://bugs.documentfoundation.org/attachment.cgi?id=184389=edit My spreadsheet -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 152720] Spreadsheet closes while scrolling thumb
https://bugs.documentfoundation.org/show_bug.cgi?id=152720 Larry Hinsley changed: What|Removed |Added Ever confirmed|1 |0 Status|NEEDINFO|UNCONFIRMED -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 152720] Spreadsheet closes while scrolling thumb
https://bugs.documentfoundation.org/show_bug.cgi?id=152720 Xisco Faulí changed: What|Removed |Added CC||xiscofa...@libreoffice.org Status|UNCONFIRMED |NEEDINFO Ever confirmed|0 |1 --- Comment #1 from Xisco Faulí --- Thank you for reporting the bug. Please attach a sample document, as this makes it easier for us to verify the bug. I have set the bug's status to 'NEEDINFO'. Please change it back to 'UNCONFIRMED' once the requested document is provided. (Please note that the attachment will be public, remove any sensitive information before attaching it. See https://wiki.documentfoundation.org/QA/FAQ#How_can_I_eliminate_confidential_data_from_a_sample_document.3F for help on how to do so.) -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 149770] Over the past few weeks when I open a document that has already been saved, it wants to save it.
https://bugs.documentfoundation.org/show_bug.cgi?id=149770 m.a.riosv changed: What|Removed |Added Status|NEEDINFO|RESOLVED Resolution|--- |WORKSFORME -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 152575] PDF Export prints comments only to the margin of the first page
https://bugs.documentfoundation.org/show_bug.cgi?id=152575 --- Comment #11 from BogdanB --- 2 steps in order to work: - Tools - Options - LibreOffice Writer - Print - Comments - check "In margins" - OK - with the document you want to print opened press Ctrl+P (or File - Print), in the next window go to the next TAB (LibreOffice Writer) TAB and check Comments - Place in margin. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 152720] New: Spreadsheet closes while scrolling thumb
https://bugs.documentfoundation.org/show_bug.cgi?id=152720 Bug ID: 152720 Summary: Spreadsheet closes while scrolling thumb Product: LibreOffice Version: 7.3.2.2 release Hardware: All OS: Windows (All) Status: UNCONFIRMED Severity: normal Priority: medium Component: Calc Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: larryhins...@gmail.com Description: I have a large spreadsheet with over 2000 rows. If I grab the thumb and scroll forward or backward for a large number of rows, after a while the scrolling will stop and the program will exit without saving changes. I've finally discovered the cause. If I move the mouse pointer off of the spreadsheet this problem will occur. If I keep the mouse pointer on the spreadsheet while scrolling it doesn't happen. Steps to Reproduce: 1. See description 2. 3. Actual Results: Calc closes without saving changes Expected Results: Shouldn't close. Reproducible: Always User Profile Reset: No Additional Info: Version: 7.3.2.2 (x64) / LibreOffice Community Build ID: 49f2b1bff42cfccbd8f788c8dc32c1c309559be0 CPU threads: 8; OS: Windows 10.0 Build 19045; UI render: Skia/Vulkan; VCL: win Locale: en-US (en_US); UI: en-US Calc: threaded -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 117636] Multi-page block of Chinese glyphs slows down file opening and navigation
https://bugs.documentfoundation.org/show_bug.cgi?id=117636 خالد حسني changed: What|Removed |Added Hardware|x86-64 (AMD64) |All -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 117636] Multi-page block of Chinese glyphs slows down file opening and navigation
https://bugs.documentfoundation.org/show_bug.cgi?id=117636 خالد حسني changed: What|Removed |Added OS|Linux (All) |All -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 137007] Enhancement: Please integrate or replicate the functionality of the "Save As Images" extension directly into draw (with bug fixes)
https://bugs.documentfoundation.org/show_bug.cgi?id=137007 --- Comment #14 from xordevore...@gmail.com --- This extension is now absolutely completely useless under 7.5 of LibreOffice. Is there any way this functionality can be added to the program itself soon? https://imgur.com/46yVKEB -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 95276] SVG-image text layout bug (pixels cut off from text)
https://bugs.documentfoundation.org/show_bug.cgi?id=95276 --- Comment #16 from devsepp...@gmail.com --- Created attachment 184387 --> https://bugs.documentfoundation.org/attachment.cgi?id=184387=edit Lo 7.5 RC1 100% zoom. Third text box has pixels missing from top of the fonts -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 149770] Over the past few weeks when I open a document that has already been saved, it wants to save it.
https://bugs.documentfoundation.org/show_bug.cgi?id=149770 --- Comment #4 from Brad --- It was a bug in libre office. I uninstalled it and installed a different version. thanks -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 152719] New: Scrolling slow
https://bugs.documentfoundation.org/show_bug.cgi?id=152719 Bug ID: 152719 Summary: Scrolling slow Product: LibreOffice Version: 7.5.0.0 beta1+ Hardware: All OS: Windows (All) Status: UNCONFIRMED Severity: normal Priority: medium Component: LibreOffice Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: jlerne...@comcast.net Description: When in Calc and you use the mouse scroll wheel to scroll the sheets are slow (lags behind) to move. The right side bar is the same way. Writer is not as slow as Calc. Steps to Reproduce: 1.Use mouse scroll wheel or right side bar to scroll up or down 2.Sheet movement lags 3. Actual Results: The sheet moves slow when using either the mouse scroll wheel or right side bar. Expected Results: Smooth scrolling with no lag. Reproducible: Always User Profile Reset: No Additional Info: Tried in Safe Mode got the same results. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 152575] PDF Export prints comments only to the margin of the first page
https://bugs.documentfoundation.org/show_bug.cgi?id=152575 --- Comment #10 from devsepp...@gmail.com --- Now I tested 7.6.0.0.alpha0+ (2022-Dec-28) and this version prints comments only to the margin of the first page. So for me, none of the versions work corretly. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 152706] TRANSLATION: Error message when trying to use new translation feature
https://bugs.documentfoundation.org/show_bug.cgi?id=152706 --- Comment #4 from Sebastiaan Veld --- Sorry, misread the issue: so -yes- I have the same issue as I reported as part of bug 152247: To duplicate: * Installed fresh 7.5 beta1 in Dutch (Nederlands), reset the user profile * Start a New document * Setup Translation in Settings, https://api-free.deepl.com/v2/translate and added verification key. * Added some English text to my document * Select no text, all or part of the text and hit Translate from the menu * Results in "Requested clipboard format is not available." (in my case this error message is shown in Dutch). Result: Noting is translated and the original text selected for translation is lost in the document. Expected result: Translated text should be shown in the document. Version: 7.5.0.1 (X86_64) / LibreOffice Community Build ID: 77cd3d7ad4445740a0c6cf977992dafd8ebad8df CPU threads: 16; OS: Windows 10.0 Build 22621; UI render: Skia/Vulkan; VCL: win Locale: nl-NL (nl_NL); UI: nl-NL Calc: CL threaded -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 152575] PDF Export prints comments only to the margin of the first page
https://bugs.documentfoundation.org/show_bug.cgi?id=152575 --- Comment #9 from BogdanB --- (In reply to devseppala from comment #8) > I retested the following: > > LibreOfficeDev_7.5.0.0.alpha1_Win_x86-64 >Does not have the feature implemented eyet. > > LibreOfficeDev_7.5.0.0.beta1_Win_x86-64.msi >First implementation build of this feature and comments are printed only > to the margin of the first page > > LibreOffice_7.5.0.1_Win_x86-64.msi (RC1?) >comments are printed only to the margin of the first page > > > However, I have not and can't test 7.6.0.0.alpha0+, because I don't know > where to download it. I have only tested versions available on the > pre-releases server. I only mentioned 7.6.0.0.alpha0+ because stragu > commented it on bug 77650. Here you can find development versions everyday and choose what is wright for youȘ Mac/Linux/Windows https://dev-builds.libreoffice.org/daily/master/ -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-commits] core.git: vcl/inc vcl/Library_vcl.mk vcl/quartz vcl/skia
vcl/Library_vcl.mk | 12 ++ vcl/inc/quartz/cgutils.h | 34 +++ vcl/inc/quartz/salbmp.h| 12 -- vcl/inc/salbmp.hxx | 23 + vcl/inc/skia/quartz/cgutils.h | 40 vcl/inc/skia/salbmp.hxx|7 + vcl/quartz/AquaGraphicsBackend.cxx | 169 ++--- vcl/quartz/cgutils.mm | 73 +++ vcl/quartz/salbmp.cxx | 115 ++--- vcl/skia/osx/gdiimpl.cxx | 23 - vcl/skia/quartz/salbmp.mm | 107 +++ 11 files changed, 323 insertions(+), 292 deletions(-) New commits: commit b99464ef2ff58670aacee2fb5f0ea4398420ad47 Author: Patrick Luby AuthorDate: Sun Dec 25 10:17:01 2022 -0500 Commit: Noel Grandin CommitDate: Thu Dec 29 14:14:36 2022 + Related: tdf#146842 Eliminate temporary copies of SkiaSalBitmap when printing Commit 9eb732a32023e74c44ac8c3b5af9f5424273bb6c fixed crashing when printing SkiaSalBitmaps to a non-Skia SalGraphics. However, the fix almost always makes two copies of the SkiaSalBitmap's bitmap data: the first copy is made in SkiaSalBitmap::AcquireBuffer() and then QuartzSalBitmap makes a copy of the first copy. By making QuartzSalBitmap's methods that return a CGImageRef pure virtual, a non-Skia SalGraphics can now create a CGImageRef directly from a SkiaSalBitmap's Skia bitmap data without copying to any intermediate buffers. Change-Id: If6ab7f175889cb4839d8a2461b7be7671e575c08 Reviewed-on: https://gerrit.libreoffice.org/c/core/+/144856 Tested-by: Jenkins Reviewed-by: Noel Grandin diff --git a/vcl/Library_vcl.mk b/vcl/Library_vcl.mk index f3a165b830ca..0c018b7bb9b4 100644 --- a/vcl/Library_vcl.mk +++ b/vcl/Library_vcl.mk @@ -684,6 +684,12 @@ ifeq ($(OS),iOS) $(eval $(call gb_Library_add_cxxflags,vcl,\ $(gb_OBJCXXFLAGS) \ )) +$(eval $(call gb_Library_add_objcxxobjects,vcl,\ +vcl/quartz/cgutils \ +$(if $(filter SKIA,$(BUILD_TYPE)), \ +vcl/skia/quartz/salbmp \ +) \ +)) $(eval $(call gb_Library_add_exception_objects,vcl,\ vcl/ios/iosinst \ vcl/ios/dummies \ @@ -709,6 +715,12 @@ endif ifeq ($(OS),MACOSX) +$(eval $(call gb_Library_add_objcxxobjects,vcl,\ +vcl/quartz/cgutils \ +$(if $(filter SKIA,$(BUILD_TYPE)), \ +vcl/skia/quartz/salbmp \ +) \ +)) $(eval $(call gb_Library_use_system_darwin_frameworks,vcl,\ Cocoa \ CoreFoundation \ diff --git a/vcl/inc/quartz/cgutils.h b/vcl/inc/quartz/cgutils.h new file mode 100644 index ..6c499448c721 --- /dev/null +++ b/vcl/inc/quartz/cgutils.h @@ -0,0 +1,34 @@ +/* -*- Mode: C++; tab-width: 4; indent-tabs-mode: nil; c-basic-offset: 4 -*- */ +/* + * This file is part of the LibreOffice project. + * + * This Source Code Form is subject to the terms of the Mozilla Public + * License, v. 2.0. If a copy of the MPL was not distributed with this + * file, You can obtain one at http://mozilla.org/MPL/2.0/. + * + * This file incorporates work covered by the following license notice: + * + * Licensed to the Apache Software Foundation (ASF) under one or more + * contributor license agreements. See the NOTICE file distributed + * with this work for additional information regarding copyright + * ownership. The ASF licenses this file to you under the Apache + * License, Version 2.0 (the "License"); you may not use this file + * except in compliance with the License. You may obtain a copy of + * the License at http://www.apache.org/licenses/LICENSE-2.0 . + */ + +#pragma once + +#include + +#include +#include +#include + +class SalBitmap; + +CGImageRef VCL_DLLPUBLIC CreateWithSalBitmapAndMask(const SalBitmap& rBitmap, +const SalBitmap& rMask, int nX, int nY, +int nWidth, int nHeight); + +/* vim:set shiftwidth=4 softtabstop=4 expandtab: */ diff --git a/vcl/inc/quartz/salbmp.h b/vcl/inc/quartz/salbmp.h index 459a2b528f99..8f4e6a34ee1c 100644 --- a/vcl/inc/quartz/salbmp.h +++ b/vcl/inc/quartz/salbmp.h @@ -30,9 +30,6 @@ #include #include #include -#if HAVE_FEATURE_SKIA -#include -#endif #include @@ -64,9 +61,6 @@ public: boolCreate( const SalBitmap& rSalBmp ) override; boolCreate( const SalBitmap& rSalBmp, SalGraphics* pGraphics ) override; boolCreate( const SalBitmap& rSalBmp, vcl::PixelFormat eNewPixelFormat) override; -#if HAVE_FEATURE_SKIA -boolCreate( const SkiaSalBitmap& rSkiaSalBmp, const SalTwoRect& rPosAry ); -#endif virtual boolCreate( const css::uno::Reference< css::rendering::XBitmapCanvas >& rBitmapCanvas, Size& rSize, bool bMask = false ) override; @@ -99,9 +93,9 @@ public: boolCreate(CGLayerHolder const
[Libreoffice-bugs] [Bug 106179] [META] Writer comment bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=106179 --- Comment #49 from saad ali khan --- Here at Distinguished.io, you can scan our site to explore the https://distinguished.io/companies/software-development;>top software development company that can deliver professional services which can help your brand in maximizing its performance and customer engagement. We conduct extensive research and utilize credible sources to ensure our selection of top companies is legit and the best for clients. Click here for more information. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 152575] PDF Export prints comments only to the margin of the first page
https://bugs.documentfoundation.org/show_bug.cgi?id=152575 --- Comment #8 from devsepp...@gmail.com --- I retested the following: LibreOfficeDev_7.5.0.0.alpha1_Win_x86-64 Does not have the feature implemented eyet. LibreOfficeDev_7.5.0.0.beta1_Win_x86-64.msi First implementation build of this feature and comments are printed only to the margin of the first page LibreOffice_7.5.0.1_Win_x86-64.msi (RC1?) comments are printed only to the margin of the first page However, I have not and can't test 7.6.0.0.alpha0+, because I don't know where to download it. I have only tested versions available on the pre-releases server. I only mentioned 7.6.0.0.alpha0+ because stragu commented it on bug 77650. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-commits] core.git: svtools/source
svtools/source/uno/wizard/wizardpagecontroller.cxx | 11 ++-
1 file changed, 10 insertions(+), 1 deletion(-)
New commits:
commit aef2ee893c7b76794bc9db869f08bbbea60606a8
Author: Ilhan Yesil
AuthorDate: Fri Dec 16 07:30:13 2022 +0100
Commit: Michael Weghorn
CommitDate: Thu Dec 29 13:46:04 2022 +
tdf#152508 Initiate container request size after call of createPage
As the container's request size of wizard pages can't be changed
directly by the UNO call setPosSize, the UNO caller can set the size
in the callback function createPage, this size will then taken as
request size. This doesn't solve the problem entirely as descriped
in tdf#152508, but the most important is, that the wizard page can
be initialized with an appropriate size at startup.
Change-Id: I1899da9c018681291559eb7c0de25a3e2e8af14e
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/144287
Tested-by: Jenkins
Reviewed-by: Caolán McNamara
Reviewed-by: Michael Weghorn
diff --git a/svtools/source/uno/wizard/wizardpagecontroller.cxx
b/svtools/source/uno/wizard/wizardpagecontroller.cxx
index 333d7ce27351..850d9b102c7a 100644
--- a/svtools/source/uno/wizard/wizardpagecontroller.cxx
+++ b/svtools/source/uno/wizard/wizardpagecontroller.cxx
@@ -50,7 +50,16 @@ namespace svt::uno
try
{
// Plug a toplevel SalFrame into the native page which can host
our awt widgetry
-
m_xWizardPage.set(m_xController->createPage(pParent->CreateChildFrame(),
i_nPageId), UNO_SET_THROW);
+css::uno::Reference xChildFrame =
pParent->CreateChildFrame();
+// If size of page is changed by createPage, then the requested
size of the container
+// should also be set to this size, to avoid annoying resizings.
+com::sun::star::awt::Rectangle r0 = xChildFrame->getPosSize();
+m_xWizardPage.set(m_xController->createPage(xChildFrame,
i_nPageId), UNO_SET_THROW);
+com::sun::star::awt::Rectangle r1 = xChildFrame->getPosSize();
+if (r0.Width != r1.Width || r0.Height != r1.Height)
+{
+pParent->set_size_request(r1.Width, r1.Height);
+}
Reference< XWindow > xPageWindow(m_xWizardPage->getWindow(),
UNO_SET_THROW);
xPageWindow->setVisible( true );
[Libreoffice-bugs] [Bug 152029] Visually draw attention to in-view bookmark or hyperlink when selecting/hovering it in the Navigator
https://bugs.documentfoundation.org/show_bug.cgi?id=152029 --- Comment #52 from BogdanB --- Also I tested: hyperlink, bookmarks, drawing controls (for example Form - Textbox), tables, frames, images, OLE Object, footnotes, endnotes. Everything fine. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 152029] Visually draw attention to in-view bookmark or hyperlink when selecting/hovering it in the Navigator
https://bugs.documentfoundation.org/show_bug.cgi?id=152029 BogdanB changed: What|Removed |Added Status|RESOLVED|VERIFIED --- Comment #51 from BogdanB --- I checked comments, sections and headings, and everything is fine in Version: 7.5.0.1.0+ (X86_64) / LibreOffice Community Build ID: 1e6e59f874b219d2ff3c8363a69ce7ba6a44bc1c CPU threads: 4; OS: Windows 10.0 Build 19045; UI render: Skia/Raster; VCL: win Locale: ro-RO (ro_RO); UI: en-US Calc: threaded Just as a note: It's hard to see for comments that are inserted when the cursor is only in the text, and we have no selection made. When the comment is inserted after some text is selected, the area for text is bigger and easier to see the effect. -- You are receiving this mail because: You are the assignee for the bug.
