[Libreoffice-bugs] [Bug 109232] [META] Special character dialog and toolbar group button bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=109232 Bug 109232 depends on bug 156538, which changed state. Bug 156538 Summary: Insert Special Character TB splitbutton should indicate glyph names https://bugs.documentfoundation.org/show_bug.cgi?id=156538 What|Removed |Added Status|ASSIGNED|RESOLVED Resolution|--- |FIXED -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 103429] [META] Split and group buttons in toolbar and sidebar bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=103429 Bug 103429 depends on bug 156538, which changed state. Bug 156538 Summary: Insert Special Character TB splitbutton should indicate glyph names https://bugs.documentfoundation.org/show_bug.cgi?id=156538 What|Removed |Added Status|ASSIGNED|RESOLVED Resolution|--- |FIXED -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-commits] core.git: include/sfx2 sfx2/inc sfx2/source sfx2/uiconfig solenv/sanitizers
include/sfx2/charwin.hxx |7
sfx2/inc/charmapcontrol.hxx|3
sfx2/source/control/charmapcontrol.cxx | 22 +
sfx2/source/control/charwin.cxx| 39 +++
sfx2/uiconfig/ui/charmapcontrol.ui | 370 +
solenv/sanitizers/ui/sfx.suppr |1
6 files changed, 260 insertions(+), 182 deletions(-)
New commits:
commit 717fa28e88f382ad86b2be2fdbc24f4f60bc524d
Author: Jim Raykowski
AuthorDate: Fri Aug 4 21:27:15 2023 -0800
Commit: Jim Raykowski
CommitDate: Wed Aug 16 07:50:25 2023 +0200
tdf#156538 Enhancement to show character information in the insert
special characters control
This patch makes a tooltip show when the mouse pointer is over a
character window in the special characters control. It also adds a
label that is used to display character information of the highlighted
character. Code for creating the character information text shown in
the tooltip and label was referenced from SvxCharacterMap.
Change-Id: I4b62e63b27310cbe9e9661ff51c2db206e9e3507
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/155547
Tested-by: Jenkins
Reviewed-by: Jim Raykowski
diff --git a/include/sfx2/charwin.hxx b/include/sfx2/charwin.hxx
index d0a8f86d2e51..75a6fad12a38 100644
--- a/include/sfx2/charwin.hxx
+++ b/include/sfx2/charwin.hxx
@@ -35,6 +35,7 @@ private:
boolmaHasInsert;
OUStringm_sText;
+Link maFocusInHdl;
Link maMouseClickHdl;
Link maClearClickHdl;
Link maClearAllClickHdl;
@@ -44,6 +45,7 @@ private:
virtual bool MouseButtonDown(const MouseEvent&) override;
virtual void GetFocus() override;
virtual void LoseFocus() override;
+virtual OUString RequestHelp(tools::Rectangle) override;
virtual bool KeyInput(const KeyEvent&) override;
virtual bool Command(const CommandEvent&) override;
virtual void SetDrawingArea(weld::DrawingArea* pDrawingArea) override;
@@ -54,6 +56,7 @@ public:
vcl::Font const & GetFont() const { return maFont; }
voidSetText( const OUString& rText );
OUString const & GetText() const { return m_sText; }
+OUString GetCharInfoText();
voidSetHasInsert( bool bInsert );
voidInsertCharToDoc();
@@ -61,6 +64,7 @@ public:
Sizeget_preferred_size() const { return
GetDrawingArea()->get_preferred_size(); }
+void setFocusInHdl(const Link );
void setMouseClickHdl(const Link );
void setClearClickHdl(const Link );
void setClearAllClickHdl(const Link );
@@ -96,7 +100,8 @@ public:
voidinit(bool bHasInsert, const Link
,
const Link ,
- const Link );
+ const Link ,
+ const Link =
Link());
voidgetFavCharacterList();
voidupdateFavCharControl();
diff --git a/sfx2/inc/charmapcontrol.hxx b/sfx2/inc/charmapcontrol.hxx
index c6045154583e..72f0328da2af 100644
--- a/sfx2/inc/charmapcontrol.hxx
+++ b/sfx2/inc/charmapcontrol.hxx
@@ -45,9 +45,12 @@ private:
std::unique_ptr m_xRecentLabel;
std::unique_ptr m_xDlgBtn;
+std::unique_ptr m_xCharInfoLabel;
+DECL_LINK(CharFocusInHdl, SvxCharView*, void);
DECL_LINK(CharClickHdl, SvxCharView*, void);
DECL_LINK(OpenDlgHdl, weld::Button&, void);
+DECL_LINK(DlgBtnFocusInHdl, weld::Widget&, void);
DECL_LINK(UpdateRecentHdl, void*, void);
};
diff --git a/sfx2/source/control/charmapcontrol.cxx
b/sfx2/source/control/charmapcontrol.cxx
index c71dbc8bb402..76e37174fd49 100644
--- a/sfx2/source/control/charmapcontrol.cxx
+++ b/sfx2/source/control/charmapcontrol.cxx
@@ -105,7 +105,8 @@ SfxCharmapContainer::SfxCharmapContainer(weld::Builder&
rBuilder, const VclPtr
,
const Link& rUpdateFavHdl,
- const Link& rUpdateRecentHdl)
+ const Link& rUpdateRecentHdl,
+ const Link )
{
m_aUpdateFavHdl = rUpdateFavHdl;
m_aUpdateRecentHdl = rUpdateRecentHdl;
@@ -118,10 +119,12 @@ void SfxCharmapContainer::init(bool bHasInsert, const
Link
for(int i = 0; i < 16; i++)
{
m_aRecentCharView[i].SetHasInsert(bHasInsert);
+m_aRecentCharView[i].setFocusInHdl(rFocusInHdl);
m_aRecentCharView[i].setMouseClickHdl(rMouseClickHdl);
m_aRecentCharView[i].setClearClickHdl(LINK(this, SfxCharmapContainer,
RecentClearClickHdl));
m_aRecentCharView[i].setClearAllClickHdl(LINK(this,
SfxCharmapContainer, RecentClearAllClickHdl));
m_aFavCharView[i].SetHasInsert(bHasInsert);
+m_aFavCharView[i].setFocusInHdl(rFocusInHdl);
m_aFavCharView[i].setMouseClickHdl(rMouseClickHdl);
m_aFavCharView[i].setClearClickHdl(LINK(this, SfxCharmapContainer,
FavClearClickHdl));
[Libreoffice-bugs] [Bug 156776] Base Save As New Table Name not refreshed if schema could be chosen
https://bugs.documentfoundation.org/show_bug.cgi?id=156776 Robert Großkopf changed: What|Removed |Added Status|UNCONFIRMED |NEW Ever confirmed|0 |1 Summary|Base Save As New Table Name |Base Save As New Table Name |not refreshed |not refreshed if schema ||could be chosen --- Comment #11 from Robert Großkopf --- Ah, now I see the problem you got. I understood: Table won't appear. But you wanted to save the name automatically without changing the entry. Only in internal databases without any schema the file name of the table will be changed automatically. I get the same behavior without changing schema: Table name will always be "Table1". If I try to save a new table in the same schema it will be the same name - also in default schema. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156780] New: Libre Office crashes during Find and Replace
https://bugs.documentfoundation.org/show_bug.cgi?id=156780 Bug ID: 156780 Summary: Libre Office crashes during Find and Replace Product: LibreOffice Version: 7.5.2.2 release Hardware: x86 (IA32) OS: Windows (All) Status: UNCONFIRMED Severity: normal Priority: medium Component: Writer Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: twentyjazzfunkgre...@hotmail.com Description: If you try to Find and Replace to adjust formatting, Libre Office crashes- every time, even after updating. Steps to Reproduce: 1.Ctrl +H 2. Find Format [italic] 3. Replace Format [bold italic, Font coloour Green 700] 4 Replace all Actual Results: Error: "undo must be turned off to complete the operation. Do you wish to proceed?" [yes] Libre Writer and Calc Not Responding. Libre Office had to be shut down in Taskman Expected Results: All italic to become bold and green in this perfectly ordinary, minimally formatted 13Kb Writer document. Reproducible: Always User Profile Reset: No Additional Info: Should have taken 5 seconds, without turning off 'Undo', to make all text that's formatted [italic], green and bold as well. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156779] New: TOOLBAR: 'Text formatting' toolbar disappears once you click outside of text box
https://bugs.documentfoundation.org/show_bug.cgi?id=156779 Bug ID: 156779 Summary: TOOLBAR: 'Text formatting' toolbar disappears once you click outside of text box Product: LibreOffice Version: 7.5.3.2 release Hardware: x86-64 (AMD64) OS: Linux (All) Status: UNCONFIRMED Severity: normal Priority: medium Component: Impress Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: green...@yandex.ru Description: 'Text formatting' toolbar disappears once you click outside of text box despite the fact it was ticked in View/Toolbars before - this tick disappears as well. It's a bug - Impress shouldn't change my settings at it's own will without notice. Steps to Reproduce: 1. tick 'Text formatting' in View/Toolbars 2. check if toolbar appeared 3. enter and leave any textbox 4. check that both toolbar and your tick disappeared Actual Results: both toolbar and tick 'Text formatting' in View/Toolbars disappear Expected Results: Impress respects and keeps my settings Reproducible: Always User Profile Reset: Yes Additional Info: Very annoying. Version: 7.5.3.2 (X86_64) / LibreOffice Community Build ID: 9f56dff12ba03b9acd7730a5a481eea045e468f3 CPU threads: 4; OS: Linux 5.10; UI render: default; VCL: gtk3 Locale: ru-RU (ru_RU.UTF-8); UI: en-US Calc: threaded -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156757] font issues
https://bugs.documentfoundation.org/show_bug.cgi?id=156757 --- Comment #9 from QA Administrators --- [Automated Action] NeedInfo-To-Unconfirmed -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156511] interface XStorage no more usable on odb with 7.6 and 7.7
https://bugs.documentfoundation.org/show_bug.cgi?id=156511 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 153031] Dark mode is too dark
https://bugs.documentfoundation.org/show_bug.cgi?id=153031 --- Comment #4 from QA Administrators --- Dear untenshu, 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 153017] printer chaos
https://bugs.documentfoundation.org/show_bug.cgi?id=153017 --- Comment #4 from QA Administrators --- Dear alignedtraining, 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 153017] printer chaos
https://bugs.documentfoundation.org/show_bug.cgi?id=153017 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 152863] Mismatch between ODT and DOCX page layout
https://bugs.documentfoundation.org/show_bug.cgi?id=152863 --- Comment #3 from QA Administrators --- Dear Telesto, 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 152168] Libre Office crashes every time I try to copy a portion of text using two stroke (ie command x)
https://bugs.documentfoundation.org/show_bug.cgi?id=152168 --- Comment #5 from QA Administrators --- Dear rchene...@gmail.com, 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 150210] fileopen docx blank
https://bugs.documentfoundation.org/show_bug.cgi?id=150210 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 150210] fileopen docx blank
https://bugs.documentfoundation.org/show_bug.cgi?id=150210 --- Comment #8 from QA Administrators --- Dear jindam, vani, 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 149323] Contents cannot display or blinking when clicking on PPSX file by using Impress
https://bugs.documentfoundation.org/show_bug.cgi?id=149323 --- Comment #3 from QA Administrators --- Dear James Sun, 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 149134] Black boxes present on document when scrolling through text in writer document
https://bugs.documentfoundation.org/show_bug.cgi?id=149134 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 149146] Spurious Err:522
https://bugs.documentfoundation.org/show_bug.cgi?id=149146 --- Comment #8 from QA Administrators --- Dear studog, 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 148377] Crashes soon after opening and choosing icon for picture insertion. I am using the Mac Mini Silicone Processor, 16 gigs ram
https://bugs.documentfoundation.org/show_bug.cgi?id=148377 --- Comment #4 from QA Administrators --- Dear Neal Shafto, 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 147030] LibreOffice 7.1 and 7.2 are unstable and frequently crash on macOS Catalina and Big Sur.
https://bugs.documentfoundation.org/show_bug.cgi?id=147030 --- Comment #6 from QA Administrators --- Dear George W Gerrity, 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 149134] Black boxes present on document when scrolling through text in writer document
https://bugs.documentfoundation.org/show_bug.cgi?id=149134 --- Comment #4 from QA Administrators --- Dear bjcorso101, 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 144413] Crash with copy paste functions (ARM only?)
https://bugs.documentfoundation.org/show_bug.cgi?id=144413 --- Comment #13 from QA Administrators --- Dear Lise, 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 87321] FILEOPEN: high memory footprint opening a xls containg a big html table in Calc
https://bugs.documentfoundation.org/show_bug.cgi?id=87321 --- Comment #16 from QA Administrators --- Dear Gabriele, 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 98681] FILEOPEN DOCX Incorrect display of specific file with Corel Draw OLE embedding
https://bugs.documentfoundation.org/show_bug.cgi?id=98681 --- Comment #14 from QA Administrators --- Dear Vladimir Potapov, 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 151043] Toggle between two figures via animation in Impress
https://bugs.documentfoundation.org/show_bug.cgi?id=151043 --- Comment #2 from QA Administrators --- Dear Emily Grace Seville, This bug has been in NEEDINFO status with no change for at least 6 months. Please provide the requested information as soon as possible and mark the bug as UNCONFIRMED. Due to regular bug tracker maintenance, if the bug is still in NEEDINFO status with no change in 30 days the QA team will close the bug as INSUFFICIENTDATA due to lack of needed information. For more information about our NEEDINFO policy please read the wiki located here: https://wiki.documentfoundation.org/QA/Bugzilla/Fields/Status/NEEDINFO If you have already provided the requested information, please mark the bug as UNCONFIRMED so that the QA team knows that the bug is ready to be confirmed. Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-NeedInfo-Ping -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153652] Input Line in Calc Version 7.4.5.1 on Windows 11 does not show numbers properly unless box is expanded
https://bugs.documentfoundation.org/show_bug.cgi?id=153652 --- Comment #2 from QA Administrators --- Dear HumpbackLover, This bug has been in NEEDINFO status with no change for at least 6 months. Please provide the requested information as soon as possible and mark the bug as UNCONFIRMED. Due to regular bug tracker maintenance, if the bug is still in NEEDINFO status with no change in 30 days the QA team will close the bug as INSUFFICIENTDATA due to lack of needed information. For more information about our NEEDINFO policy please read the wiki located here: https://wiki.documentfoundation.org/QA/Bugzilla/Fields/Status/NEEDINFO If you have already provided the requested information, please mark the bug as UNCONFIRMED so that the QA team knows that the bug is ready to be confirmed. Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-NeedInfo-Ping -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 81165] in xls spreadsheet FILESAVE - dotted lines round cells print but then do not save
https://bugs.documentfoundation.org/show_bug.cgi?id=81165 --- Comment #9 from QA Administrators --- Dear Jacky Leman, 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 134684] Conditional Colour Formatting in CALC becomes inconsistent as table columns are deleted
https://bugs.documentfoundation.org/show_bug.cgi?id=134684 --- Comment #19 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 137716] Incorrect sorting order for Persian (a.k.a Farsi) text
https://bugs.documentfoundation.org/show_bug.cgi?id=137716 --- Comment #5 from QA Administrators --- Dear MohammadReza Hosseini, 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 127207] Dashes, dots and spaces are too large in Writer
https://bugs.documentfoundation.org/show_bug.cgi?id=127207 --- Comment #7 from QA Administrators --- Dear Regina Henschel, 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 130911] Policy on converting Perl scripts to Python
https://bugs.documentfoundation.org/show_bug.cgi?id=130911 --- Comment #14 from QA Administrators --- Dear Jussi Pakkanen, 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 122556] DDE link is specified by absolute system path. Hyperlink not working.
https://bugs.documentfoundation.org/show_bug.cgi?id=122556 --- Comment #6 from QA Administrators --- Dear Andreas Säger, 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 122420] FILESAVE: VBA Worksheet_Change Listener lost on saving .xlsm in LO
https://bugs.documentfoundation.org/show_bug.cgi?id=122420 --- Comment #6 from QA Administrators --- Dear Oliver Brinzing, 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 118867] EDITING Formula is not pasted correctly after Cut - Delete - Paste
https://bugs.documentfoundation.org/show_bug.cgi?id=118867 --- Comment #13 from QA Administrators --- Dear Emil Tanev, 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 121829] Linked section to protected (password or gpg encrypted) document does not work
https://bugs.documentfoundation.org/show_bug.cgi?id=121829 --- Comment #12 from QA Administrators --- Dear bugzilla, 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 100061] Table cells in specific Microsoft Word document not merge without changing column width
https://bugs.documentfoundation.org/show_bug.cgi?id=100061 --- Comment #8 from QA Administrators --- Dear weml, 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 107410] FILEOPEN RTF: "Expression is faulty" instead of numbers (take alternate part if formula parsing fails)
https://bugs.documentfoundation.org/show_bug.cgi?id=107410 --- Comment #16 from QA Administrators --- Dear Xisco Faulí, 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 156778] Borders: Image Padding
https://bugs.documentfoundation.org/show_bug.cgi?id=156778 m.a.riosv changed: What|Removed |Added CC||miguelangelrv@libreoffice.o ||rg --- Comment #1 from m.a.riosv --- It is so by design file:///C:/Program Files/LibreOffice/help/en-US/text/shared/01/05030500.html?System=WIN=WRITER=cui/ui/borderpage/BorderPage#bm_id3150756 " Padding Specify the amount of space that you want to leave between the border and the contents of the selection. " To do as you like, change both the size of the frame where the image is in and the padding. Also in the [Wrap] tab of frame properties, there are 'Spacing' options, depending on how the frame is anchored and wrapped in the text. At much could be a request for enhancement not a bug. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156501] Calc View Headers setting is not saved to file
https://bugs.documentfoundation.org/show_bug.cgi?id=156501 --- Comment #11 from ady --- (In reply to Heiko Tietze from comment #10) > Why do you expert View > View Headers (uno:ViewRowColumnHeaders) to be > stored per document? Because the creator of the specific spreadsheet has in mind what other users (of that specific spreadsheet) should see when opening the file and how that specific spreadsheet is supposed to be used by such users, in their own systems / LO installation. In a similar way, a worksheet has some specific cells protected/blocked while some content-changing is allowed (on specific cells). Or some form, or fields, or Freeze Panes, or… The setting is not about a user always using every_and_all spreadsheets without Row/Column headers. The expectation (not just mine but from every spreadsheet user) is what is already supposed to happen, and has happened since... forever; except other bugs related to this feature (e.g. tdf#153295). Just test LO 3.3, or whichever other spreadsheet tool that includes this feature. In LO 7.6, the initially-limited situation described in tdf#153295 is much worse, described in this bug 156501; these are not duplicates of each other. > > On the other hand, Gridlines on/off is stored per document. As it should, for the same reasons I mentioned. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 137402] Can't select some body text with the mouse, when a comment exists
https://bugs.documentfoundation.org/show_bug.cgi?id=137402 Aaron changed: What|Removed |Added CC||aaronth...@gmail.com --- Comment #10 from Aaron --- This bug is still present in Version: 7.5.5.2 (X86_64) / LibreOffice Community Build ID: ca8fe7424262805f223b9a2334bc7181abbcbf5e CPU threads: 4; OS: Windows 10.0 Build 19045; UI render: Skia/Raster; VCL: win Locale: en-AU (fr_FR); UI: en-US Calc: threaded -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156757] font issues
https://bugs.documentfoundation.org/show_bug.cgi?id=156757 --- Comment #8 from Aaron --- (In reply to ksso from comment #6) > mmm, it seems the fonts are different, one is > Times New Roman and the other is > Times News Roman You know now that you mention it, I didn't notice it before that the fonts are different. I think that's the explanation for the bug. The reason why the text looks different is because that's just how the font looks like. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 148084] Half Letter format missing in page formats
https://bugs.documentfoundation.org/show_bug.cgi?id=148084 Paolo Benvenuto changed: What|Removed |Added Ever confirmed|0 |1 Status|UNCONFIRMED |NEW --- Comment #2 from Paolo Benvenuto --- Why is this trivial bug so difficult to fix? If your page format is letter, in order to print in brochure mode you need the half-letter page format. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156776] Base Save As New Table Name not refreshed
https://bugs.documentfoundation.org/show_bug.cgi?id=156776 --- Comment #10 from prrv...@gmail.com --- Reading the file again: dlgsave.cxx, it seems that m_xMetaData->getUserName() is an Oracle JDBC specification. There is no reason for the connection user's name to be called here, except to use an Oracle JDBC driver. see: https://opengrok.libreoffice.org/xref/core/dbaccess/source/ui/dlg/dlgsave.cxx?r=75fcdffd#137 The UNO API does not seem to be able to retrieve the default schema of the connection, however there is the getSchema() method in JDBC since Java 7 see: https://docs.oracle.com/javase/8/docs/api/java/sql/Connection.html#getSchema-- -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156778] New: Borders: Image Padding
https://bugs.documentfoundation.org/show_bug.cgi?id=156778 Bug ID: 156778 Summary: Borders: Image Padding Product: LibreOffice Version: 7.5.4.2 release Hardware: All OS: Linux (All) Status: UNCONFIRMED Severity: normal Priority: medium Component: Writer Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: restrepo.seat...@gmail.com Description: When uses the border padding for an image to create a space between the image and the text, the image gets shrinked and the text remains in the same. The padding should be as follows: Leave the image size intact, and move the text 2, 4, 6... pixels away. Steps to Reproduce: 1. Insert an image into a document. 2. Make it 3" wide and place on the left side of the page 3. Roght-Click >> Wrap as Optimal 4. Right Click >> Properties 5. Select Borders Tab 6. Use 10 pixels for space betw image and text Actual Results: You will notice that the image gets shrunk partially losing the proportions and the text starts in the same location of the original image boundary. Expected Results: Leave image intact and add space between image and text Reproducible: Always User Profile Reset: No Additional Info: The correct way would be to leave the correct size of the image and add a space between the image and the text. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156318] LibreOffice hangs when floating table tries to break
https://bugs.documentfoundation.org/show_bug.cgi?id=156318 raal changed: What|Removed |Added CC||r...@post.cz Ever confirmed|0 |1 Status|UNCONFIRMED |NEW --- Comment #7 from raal --- No crash after step (1). Freeze/100% CPU after step (2) Version: 24.2.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: 4403b4e6bac19d89afded080d80de049aaa294ca CPU threads: 4; OS: Linux 5.19; UI render: default; VCL: gtk3 Locale: cs-CZ (cs_CZ.UTF-8); UI: en-US Calc: threaded -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156210] Build failure with gcc-11
https://bugs.documentfoundation.org/show_bug.cgi?id=156210 raal changed: What|Removed |Added CC||hoss...@libreoffice.org, ||r...@post.cz --- Comment #1 from raal --- cc to Hossein, maybe he can help. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156481] failure of word 97-2003 recordings
https://bugs.documentfoundation.org/show_bug.cgi?id=156481 raal changed: What|Removed |Added CC||r...@post.cz Ever confirmed|0 |1 Status|UNCONFIRMED |NEEDINFO --- Comment #12 from raal --- Tested with DM - 803 - Sceance2.doc ( Reply 3 - to your e-mail)- open the file, change data, save, reopen. I can open the file, it's not corrupted. Please provide steps to reproduce the bug. Thank you. Version: 24.2.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: 4403b4e6bac19d89afded080d80de049aaa294ca CPU threads: 4; OS: Linux 5.19; UI render: default; VCL: gtk3 Locale: cs-CZ (cs_CZ.UTF-8); UI: en-US Calc: threaded -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156751] Pop-up menu in Find/Replace text boxes lists "Insert Emoji" instead of "Special Character"
https://bugs.documentfoundation.org/show_bug.cgi?id=156751 raal changed: What|Removed |Added Keywords||bibisected, bisected, ||regression Regression By||Caolán McNamara CC||caolan.mcnamara@collabora.c ||om --- Comment #3 from raal --- This seems to have begun at the below commit in bibisect repository/OS bibisect-linux-64-6.3$. Adding Cc: to Caolán McNamara ; Could you possibly take a look at this one? Thanks dc4d983b636de530f77708ce4d16a1977ebb081d is the first bad commit commit dc4d983b636de530f77708ce4d16a1977ebb081d Author: Jenkins Build User Date: Sun Mar 24 18:38:27 2019 +0100 source sha:f920e86fbf3968104e1dfc0e9934e80652ed0837 69569: weld SvxSearchDialog | https://gerrit.libreoffice.org/c/core/+/69569 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 103182] [META] GTK3-specific bugs
https://bugs.documentfoundation.org/show_bug.cgi?id=103182 raal changed: What|Removed |Added Depends on||156751 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=156751 [Bug 156751] Pop-up menu in Find/Replace text boxes lists "Insert Emoji" instead of "Special Character" -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156751] Pop-up menu in Find/Replace text boxes lists "Insert Emoji" instead of "Special Character"
https://bugs.documentfoundation.org/show_bug.cgi?id=156751 raal changed: What|Removed |Added CC||r...@post.cz Ever confirmed|0 |1 Status|UNCONFIRMED |NEW Blocks||103182 --- Comment #2 from raal --- it's OK in Version: 24.2.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: 4403b4e6bac19d89afded080d80de049aaa294ca CPU threads: 4; OS: Linux 5.19; UI render: default; VCL: x11 Locale: cs-CZ (cs_CZ.UTF-8); UI: en-US Calc: threaded repro in Version: 24.2.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: 4403b4e6bac19d89afded080d80de049aaa294ca CPU threads: 4; OS: Linux 5.19; UI render: default; VCL: gtk3 Locale: cs-CZ (cs_CZ.UTF-8); UI: en-US Calc: threaded Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=103182 [Bug 103182] [META] GTK3-specific bugs -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156098] Writer: "Insert - Page number" button missing in Tabbed
https://bugs.documentfoundation.org/show_bug.cgi?id=156098 --- Comment #6 from Justin L --- (In reply to Justin L from comment #4) > It is in 24.2, but I won't backport to 7.6 because the icon is still missing. It has been backported to 7.6.1 because the icon is there now. (In reply to Dieter from comment #5) > I can see the button in > or do I oversee something? The Insert tab has an insert field page number which is just a simple page number, but is NOT the new page number wizard. The page number wizard is on the LAYOUT tab in 24.2 and 7.6. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156776] Base Save As New Table Name not refreshed
https://bugs.documentfoundation.org/show_bug.cgi?id=156776 --- Comment #9 from prrv...@gmail.com --- Created attachment 188988 --> https://bugs.documentfoundation.org/attachment.cgi?id=188988=edit Base Save AS screenshot error -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-commits] core.git: extras/source
extras/source/templates/presnt/Candy/content.xml |2 +- 1 file changed, 1 insertion(+), 1 deletion(-) New commits: commit 5fecd865303b3f0a2eeb0b9466d2bcf23cfce068 Author: Gabor Kelemen AuthorDate: Thu Aug 10 11:10:53 2023 +0200 Commit: Thorsten Behrens CommitDate: Tue Aug 15 23:35:21 2023 +0200 Fix typo in default Impress template text Change-Id: I7c8550e3b71e8efaa70d966f91fc3fbee2b93939 Reviewed-on: https://gerrit.libreoffice.org/c/core/+/11 Reviewed-by: Julien Nabet Tested-by: Jenkins Reviewed-by: Thorsten Behrens diff --git a/extras/source/templates/presnt/Candy/content.xml b/extras/source/templates/presnt/Candy/content.xml index aef0e01fa93b..c2e28dbad4e9 100644 --- a/extras/source/templates/presnt/Candy/content.xml +++ b/extras/source/templates/presnt/Candy/content.xml @@ -1427,7 +1427,7 @@ - Ispum + Ipsum
[Libreoffice-bugs] [Bug 156776] Base Save As New Table Name not refreshed
https://bugs.documentfoundation.org/show_bug.cgi?id=156776 --- Comment #8 from prrv...@gmail.com --- (In reply to Julien Nabet from comment #6) > https://opengrok.libreoffice.org/ > search?project=core==OSaveAsDlg==1 > i=defs=defs may help. If it is the dialog that saves the table name, and I believe it is, the default table name seems to be loaded when the dialog is initialized (const OUString& rDefault) with a unique full table name (catalog.schema.tablename) and nothing seems to be done after changing the catalog name or the schema name. Now I could be wrong, I don't know much about C. (In reply to Robert Großkopf from comment #7) > have tested with PostgreSQL direct driver, PostgreSQL JDBC connection, > MariaDB JDBC connection. Could create as many tables as I want in the > schema, which isn't selected as default schema. All tables will directly > appear in the schema. If I use MariaDB JDBC (mariadb-java-client-3.1.4.jar with LibreOffice JDBC native driver) and I let Base choose the name of the table (table1 by default), it only works the first time (when table1 does not exist) but fails the second time (see the screenshot of the error) The only driver for which I have no problem is the SQLite JDBC driver (sqlite-jdbc-3.42.0.0.jar) under jdbcDriverOOo (the automatic numbering of table names works well) and this is due to the fact that SQLite does not support either schema or catalog and therefore the uniqueness of the name of the tables is therefore ensured. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156771] Mail Merge create fails to include all lines with fields
https://bugs.documentfoundation.org/show_bug.cgi?id=156771 --- Comment #2 from Erik Fjerstad --- Created attachment 188987 --> https://bugs.documentfoundation.org/attachment.cgi?id=188987=edit Zip file containing test files, instructions, and description of the bug. Actual database has proprietary and personal info. Created test database that successfully shows the bug. Zip file contains a description file and the necessary test input and output files: .ods, .odb, .odt inputs as well as the .odt output with evidence of the bug. Also included is the build info on the sw. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 126933] LO Writer shows some Buttons almost Unreadable when using High Contrast Theme
https://bugs.documentfoundation.org/show_bug.cgi?id=126933 --- Comment #24 from Adalbert Hanßen --- Created attachment 188986 --> https://bugs.documentfoundation.org/attachment.cgi?id=188986=edit Colibre can not be selected with Hoher Kontrast, tests repeated Yes, you are right. Colibre is incompatible with Hoher Kontrast. However it can be selected with the Linux system theme Adwaita. This test (see attachment) with Adwaita (rather than Hoher Kontrast) does not show, that my proposed improvement under the headline "Still one detail to improve" has been realized. The findings about the LibreOffice internal Icon Styles Sifr (and others) versus Colibre does not relate to this topic. However it rises further topics: At least the manual https://documentation.libreoffice.org/assets/Uploads/Documentation/en/GS7.3/GS73-GettingStarted.pdf should mention (e.g. on page 43) that some of the LibreOffice internal Icon Styles (e.g. Colibre) are incompatible with appearance settings of the operating system and will not be honored if selected, if this is the case. It would be better, not to offer those incompatible LibreOffice internal Icon Styles- At least they should be shown greyed out if they are incompatible with the chosen operating system theme. If this proposal is followed, such a line should be added to the manual: "The selectable icon themes depend on the theme settings of the operating system. Incompatible themes are grayed out in the drop-down list under Icon Style Icon Style." -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156098] Writer: "Insert - Page number" button missing in Tabbed
https://bugs.documentfoundation.org/show_bug.cgi?id=156098 --- Comment #5 from Dieter --- Created attachment 188985 --> https://bugs.documentfoundation.org/attachment.cgi?id=188985=edit Screenshot with button I can see the button in Version: 24.2.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: e25e27c85ed970cdb97c468bdac86c80964f4231 CPU threads: 4; OS: Windows 10.0 Build 19045; UI render: Skia/Raster; VCL: win Locale: de-DE (de_DE); UI: en-GB Calc: CL threaded or do I oversee something? -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156218] funny display of pages and tables when pages are not separated
https://bugs.documentfoundation.org/show_bug.cgi?id=156218 Dieter changed: What|Removed |Added Status|UNCONFIRMED |NEEDINFO Ever confirmed|0 |1 --- Comment #18 from Dieter --- Kss(In reply to ksso from comment #16) Ksso, I think there might be a misunderstanding her or I don't grasp the problem. So first of all i think, that double click as you explain it hides and shows whitespace. You get the same result, if you select View -> Whitespace in menu. Is this correct? > it is an annoying problem because it damages the pagination and you have to > go back to restart the structure (double click) so that the text reappears > as it is in reality. "Reality" is text showing whitespace, correct? If you hide whitespace you don't really see page breaks. So if you add a table, that doesn't fit a page it will break across two pages. This could be seen as damage of layout, athough it is a regular behaviour. Does this describe your problem? => NEEDINFO -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 155870] Format Word 2003 XML not supported
https://bugs.documentfoundation.org/show_bug.cgi?id=155870 --- Comment #10 from Dieter --- (In reply to Harry Fischer from comment #9) > Hello, > > I don't know what you mean with "Do you want to narrow down bug report to > that problem?" Bug description "Format Word2003 XML not supported" is too broad. As you can see in meta bug 113869 we have several different report related to that format. So every bug report should only focus on one specific problem. So I propose to focus here on the header problem I've described in comment 6. And my question is: Do you confirm the header problem? Do you agree to focus report on that report. Feel free to open different report for other problems with Word2003 XML format. => NEEDINFO -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 121829] Linked section to protected (password or gpg encrypted) document does not work
https://bugs.documentfoundation.org/show_bug.cgi?id=121829 --- Comment #11 from bugzi...@venere.me --- I can confirm that the bug still present in the version informed below: Version: 7.5.5.2 (x86) / LibreOffice Community Build ID: ca8fe7424262805f223b9a2334bc7181abbcbf5e CPU threads: 2; OS: Windows 6.1 Service Pack 1 Build 7601; UI render: Skia/Raster; VCL: win Locale: pt-BR (pt_BR); UI: pt-BR Calc: threaded -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 88278] [META] SVG import image filter (all modules)
https://bugs.documentfoundation.org/show_bug.cgi?id=88278 Bug 88278 depends on bug 156777, which changed state. Bug 156777 Summary: SVG: incorrect style in textPath https://bugs.documentfoundation.org/show_bug.cgi?id=156777 What|Removed |Added Status|ASSIGNED|RESOLVED Resolution|--- |FIXED -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-commits] core.git: svgio/qa svgio/source
svgio/qa/cppunit/SvgImportTest.cxx | 21 +
svgio/qa/cppunit/data/tdf156777.svg| 14 ++
svgio/source/svgreader/svgtextpathnode.cxx |2 +-
3 files changed, 36 insertions(+), 1 deletion(-)
New commits:
commit 20f57e14362674d321ef184e1987f41a6418adc2
Author: Xisco Fauli
AuthorDate: Tue Aug 15 19:43:42 2023 +0200
Commit: Xisco Fauli
CommitDate: Tue Aug 15 21:42:31 2023 +0200
tdf#156777: check for css style in textpath
Change-Id: I63a274dd9fba37852412a194a490cb2b7634f1cb
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/155726
Tested-by: Xisco Fauli
Reviewed-by: Xisco Fauli
diff --git a/svgio/qa/cppunit/SvgImportTest.cxx
b/svgio/qa/cppunit/SvgImportTest.cxx
index d68e7ebf728a..31e5bdb3ef13 100644
--- a/svgio/qa/cppunit/SvgImportTest.cxx
+++ b/svgio/qa/cppunit/SvgImportTest.cxx
@@ -710,6 +710,27 @@ CPPUNIT_TEST_FIXTURE(Test, testTdf97941)
assertXPath(pDocument, "/primitive2D/transform/textsimpleportion[1]",
"familyname", "Times New Roman");
}
+CPPUNIT_TEST_FIXTURE(Test, testTdf156777)
+{
+Primitive2DSequence aSequence =
parseSvg(u"/svgio/qa/cppunit/data/tdf156777.svg");
+CPPUNIT_ASSERT_EQUAL(1, static_cast(aSequence.getLength()));
+
+drawinglayer::Primitive2dXmlDump dumper;
+xmlDocUniquePtr pDocument =
dumper.dumpAndParse(Primitive2DContainer(aSequence));
+
+CPPUNIT_ASSERT (pDocument);
+
+assertXPath(pDocument, "/primitive2D/transform/textsimpleportion", 23);
+assertXPath(pDocument, "/primitive2D/transform/textsimpleportion[1]",
"text", "Quick brown fox jumps over the lazy dog.");
+
+// Without the fix in place, this test would have failed with
+// - Expected: #008000
+// - Actual : #00
+assertXPath(pDocument, "/primitive2D/transform/textsimpleportion[1]",
"fontcolor", "#008000");
+assertXPath(pDocument, "/primitive2D/transform/textsimpleportion[1]", "x",
"84");
+assertXPath(pDocument, "/primitive2D/transform/textsimpleportion[1]", "y",
"23");
+}
+
CPPUNIT_TEST_FIXTURE(Test, testTdf104339)
{
Primitive2DSequence aSequenceTdf104339 =
parseSvg(u"/svgio/qa/cppunit/data/tdf104339.svg");
diff --git a/svgio/qa/cppunit/data/tdf156777.svg
b/svgio/qa/cppunit/data/tdf156777.svg
new file mode 100644
index ..9ce1dd8cd37c
--- /dev/null
+++ b/svgio/qa/cppunit/data/tdf156777.svg
@@ -0,0 +1,14 @@
+http://www.w3.org/2000/svg;>
+
+
+
+
+ Quick brown fox jumps over the lazy dog.
+
+
+
+
diff --git a/svgio/source/svgreader/svgtextpathnode.cxx
b/svgio/source/svgreader/svgtextpathnode.cxx
index 2c5a823566ed..4dad47f62bb6 100644
--- a/svgio/source/svgreader/svgtextpathnode.cxx
+++ b/svgio/source/svgreader/svgtextpathnode.cxx
@@ -252,7 +252,7 @@ namespace svgio::svgreader
const SvgStyleAttributes* SvgTextPathNode::getSvgStyleAttributes()
const
{
-return
+return checkForCssStyle(maSvgStyleAttributes);
}
void SvgTextPathNode::parseAttribute(const OUString& rTokenName,
SVGToken aSVGToken, const OUString& aContent)
[Libreoffice-commits] core.git: oox/source sw/qa
oox/source/drawingml/fillproperties.cxx | 24
sw/qa/extras/ooxmlexport/ooxmlexport6.cxx |8
2 files changed, 16 insertions(+), 16 deletions(-)
New commits:
commit d2c7cbc7d724d608f6d37bbb0233ad2b39eb938e
Author: Mike Kaganski
AuthorDate: Tue Aug 15 21:09:27 2023 +0300
Commit: Mike Kaganski
CommitDate: Tue Aug 15 21:41:24 2023 +0200
Simplify and improve conversion
Using o3tl::convert makes sure that rounding is correct, which
shows in the improved unit test, that now doesn't need different
values before and after roundtrip.
Change-Id: If46e27300bc199e89c0abf0ea4d0cd825024aeb2
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/155728
Tested-by: Jenkins
Reviewed-by: Mike Kaganski
diff --git a/oox/source/drawingml/fillproperties.cxx
b/oox/source/drawingml/fillproperties.cxx
index a11aeb6236ee..8cc400257155 100644
--- a/oox/source/drawingml/fillproperties.cxx
+++ b/oox/source/drawingml/fillproperties.cxx
@@ -105,9 +105,9 @@ std::optional
CropQuotientsFromSrcRect(geometry::IntegerRectangle2D a
aSrcRect.X2 = std::max(aSrcRect.X2, sal_Int32(0));
aSrcRect.Y1 = std::max(aSrcRect.Y1, sal_Int32(0));
aSrcRect.Y2 = std::max(aSrcRect.Y2, sal_Int32(0));
-if (aSrcRect.X1 + aSrcRect.X2 >= 100'000 || aSrcRect.Y1 + aSrcRect.Y2 >=
100'000)
+if (aSrcRect.X1 + aSrcRect.X2 >= MAX_PERCENT || aSrcRect.Y1 + aSrcRect.Y2
>= MAX_PERCENT)
return {}; // Cropped everything
-return getQuotients(aSrcRect, 100'000.0, 100'000.0);
+return getQuotients(aSrcRect, MAX_PERCENT, MAX_PERCENT);
}
// ECMA-376 Part 1 20.1.8.30 fillRect (Fill Rectangle)
@@ -118,8 +118,8 @@ std::optional
CropQuotientsFromFillRect(geometry::IntegerRectangle2D
aFillRect.Y1 = std::min(aFillRect.Y1, sal_Int32(0));
aFillRect.Y2 = std::min(aFillRect.Y2, sal_Int32(0));
// Negative divisor and negative relative offset give positive value
wanted in lclCropGraphic
-return getQuotients(aFillRect, -100'000.0 + aFillRect.X1 + aFillRect.X2,
--100'000.0 + aFillRect.Y1 + aFillRect.Y2);
+return getQuotients(aFillRect, -MAX_PERCENT + aFillRect.X1 + aFillRect.X2,
+-MAX_PERCENT + aFillRect.Y1 + aFillRect.Y2);
}
// Crops a piece of the bitmap. lclCropGraphic doesn't handle growing.
@@ -624,13 +624,13 @@ void FillProperties::pushToPropMap(ShapePropertyMap&
rPropMap, const GraphicHelp
{
text::GraphicCrop aGraphCrop( 0, 0, 0, 0 );
if ( aFillRect.X1 )
-aGraphCrop.Left = static_cast< sal_Int32 >( (
static_cast< double >( aOriginalSize.Width ) * aFillRect.X1 ) / 10 );
+aGraphCrop.Left = o3tl::convert(aFillRect.X1,
aOriginalSize.Width, MAX_PERCENT);
if ( aFillRect.Y1 )
-aGraphCrop.Top = static_cast< sal_Int32 >( (
static_cast< double >( aOriginalSize.Height ) * aFillRect.Y1 ) / 10 );
+aGraphCrop.Top = o3tl::convert(aFillRect.Y1,
aOriginalSize.Height, MAX_PERCENT);
if ( aFillRect.X2 )
-aGraphCrop.Right = static_cast< sal_Int32 >( (
static_cast< double >( aOriginalSize.Width ) * aFillRect.X2 ) / 10 );
+aGraphCrop.Right = o3tl::convert(aFillRect.X2,
aOriginalSize.Width, MAX_PERCENT);
if ( aFillRect.Y2 )
-aGraphCrop.Bottom = static_cast< sal_Int32 >(
( static_cast< double >( aOriginalSize.Height ) * aFillRect.Y2 ) / 10 );
+aGraphCrop.Bottom =
o3tl::convert(aFillRect.Y2, aOriginalSize.Height, MAX_PERCENT);
bool bHasCropValues = aGraphCrop.Left != 0 ||
aGraphCrop.Right !=0 || aGraphCrop.Top != 0 || aGraphCrop.Bottom != 0;
// Negative GraphicCrop values means "crop" here.
@@ -817,13 +817,13 @@ void GraphicProperties::pushToPropMap( PropertyMap&
rPropMap, const GraphicHelpe
{
text::GraphicCrop aGraphCrop( 0, 0, 0, 0 );
if ( oClipRect.X1 )
-aGraphCrop.Left = rtl::math::round( ( static_cast< double
>( aOriginalSize.Width ) * oClipRect.X1 ) / 10 );
+aGraphCrop.Left = o3tl::convert(oClipRect.X1,
aOriginalSize.Width, MAX_PERCENT);
if ( oClipRect.Y1 )
-aGraphCrop.Top = rtl::math::round( ( static_cast< double
>( aOriginalSize.Height ) * oClipRect.Y1 ) / 10 );
+aGraphCrop.Top = o3tl::convert(oClipRect.Y1,
aOriginalSize.Height, MAX_PERCENT);
if ( oClipRect.X2 )
-aGraphCrop.Right = rtl::math::round( ( static_cast< double
>( aOriginalSize.Width ) * oClipRect.X2 ) / 10 );
+
[Libreoffice-commits] core.git: sw/source
sw/source/core/text/EnhancedPDFExportHelper.cxx |4 1 file changed, 4 insertions(+) New commits: commit 7712221f5340b8eb875d391967b2726e93285ab4 Author: Michael Stahl AuthorDate: Tue Aug 15 16:29:31 2023 +0200 Commit: Michael Stahl CommitDate: Tue Aug 15 21:25:59 2023 +0200 sw: PDF/UA export: add /Placement/Block to Note PDF 1.7 defines Note as an ILSE (inline), but that is rather odd and definitely not how footnotes work in Writer. PAC 3 complains about "Possibly inappropriate use of a "Note" structure element" and "Possibly inappropriate use of a "P" structure element" which is rather opaque but experimenting shows the warnings disappear when the Note has a /Placement/Block attribute. PDF 2.0 (ISO-32000-2:2020 Annex M) even removes the Note ILSE and introduces FENote as a BLSE to replace it. Change-Id: I46ee32c88d4be495bf79549280e2fa68d7da091c Reviewed-on: https://gerrit.libreoffice.org/c/core/+/155722 Tested-by: Jenkins Reviewed-by: Michael Stahl diff --git a/sw/source/core/text/EnhancedPDFExportHelper.cxx b/sw/source/core/text/EnhancedPDFExportHelper.cxx index 9124522379c8..4473b89d25b4 100644 --- a/sw/source/core/text/EnhancedPDFExportHelper.cxx +++ b/sw/source/core/text/EnhancedPDFExportHelper.cxx @@ -585,6 +585,10 @@ void SwTaggedPDFHelper::SetAttributes( vcl::PDFWriter::StructElement eType ) bWritingMode = true; break; +case vcl::PDFWriter::Note: +bPlacement = true; +break; + case vcl::PDFWriter::Table : bPlacement = bWritingMode =
[Libreoffice-commits] core.git: basctl/inc chart2/inc cui/inc cui/source docmodel/Library_docmodel.mk docmodel/source editeng/source include/docmodel include/oox include/sfx2 offapi/com oox/inc oox/qa
basctl/inc/pch/precompiled_basctl.hxx|1 chart2/inc/pch/precompiled_chartcontroller.hxx |1 cui/inc/pch/precompiled_cui.hxx |1 cui/source/tabpages/chardlg.cxx |3 docmodel/Library_docmodel.mk |2 docmodel/source/color/ComplexColorJSON.cxx |4 docmodel/source/theme/ColorSet.cxx |6 - docmodel/source/uno/UnoComplexColor.cxx |2 editeng/source/items/textitem.cxx|6 - editeng/source/uno/unotext.cxx |4 include/docmodel/color/ComplexColor.hxx | 75 ++--- include/docmodel/theme/ColorSet.hxx |1 include/docmodel/theme/FormatScheme.hxx | 19 ++-- include/docmodel/theme/Theme.hxx |1 include/docmodel/theme/ThemeColor.hxx| 101 --- include/docmodel/uno/UnoComplexColor.hxx |2 include/oox/export/ThemeExport.hxx |2 include/sfx2/namedcolor.hxx |6 - offapi/com/sun/star/util/XComplexColor.idl |5 - oox/inc/pch/precompiled_oox.hxx |1 oox/qa/unit/drawingml.cxx| 14 +-- oox/qa/unit/shape.cxx|2 oox/source/drawingml/color.cxx |7 - oox/source/drawingml/colorchoicecontext.cxx | 11 -- oox/source/drawingml/fillproperties.cxx |2 oox/source/drawingml/fontworkhelpers.cxx | 11 -- oox/source/drawingml/lineproperties.cxx |4 oox/source/export/ThemeExport.cxx| 36 oox/source/export/drawingml.cxx |4 reportdesign/inc/pch/precompiled_rptui.hxx |1 sc/qa/unit/SparklineImportExportTest.cxx | 15 +-- sc/qa/unit/ThemeImportExportTest.cxx | 24 ++--- sc/qa/unit/ucalc_DocumentThemes.cxx |4 sc/qa/unit/ucalc_sparkline.cxx |4 sc/source/filter/excel/export/ExportTools.cxx|6 - sc/source/filter/excel/xestream.cxx |4 sc/source/filter/excel/xestyle.cxx |4 sc/source/filter/xml/SparklineGroupsExport.cxx |2 sc/source/ui/theme/ThemeColorChanger.cxx | 52 --- sd/inc/pch/precompiled_sdui.hxx |1 sd/qa/unit/uiimpress.cxx |4 sd/source/core/stlsheet.cxx |2 sd/source/ui/view/drtxtob1.cxx |2 sd/source/ui/view/drviews2.cxx |2 svx/inc/pch/precompiled_svx.hxx |1 svx/qa/unit/styles.cxx |4 svx/qa/unit/xoutdev.cxx |4 svx/source/table/cell.cxx|3 svx/source/tbxctrls/PaletteManager.cxx |2 svx/source/theme/ThemeColorChanger.cxx |6 - svx/source/theme/ThemeColorPaletteManager.cxx|2 svx/source/unodraw/unoshape.cxx |3 svx/source/xoutdev/xattr.cxx |6 - sw/inc/pch/precompiled_msword.hxx|1 sw/inc/pch/precompiled_swui.hxx |1 sw/qa/core/theme/ThemeTest.cxx | 92 ++-- sw/qa/extras/ooxmlexport/ooxml_ThemeExport.cxx | 16 +-- sw/source/core/model/ThemeColorChanger.cxx | 97 +++--- sw/source/filter/ww8/docxattributeoutput.cxx | 17 +-- writerfilter/source/dmapper/BorderHandler.cxx|2 writerfilter/source/dmapper/CellColorHandler.cxx |4 writerfilter/source/dmapper/DomainMapper.cxx |6 - writerfilter/source/dmapper/TDefTableHandler.cxx |2 xmloff/qa/unit/draw.cxx | 14 +-- xmloff/source/text/XMLComplexColorContext.cxx|6 - xmloff/source/text/XMLComplexColorExport.cxx |5 - 66 files changed, 299 insertions(+), 456 deletions(-) New commits: commit 9d5a7d9257db78eb3f4d77c39eae1affe877ea6b Author: Tomaž Vajngerl AuthorDate: Thu Aug 3 10:14:40 2023 +0200 Commit: Tomaž Vajngerl CommitDate: Tue Aug 15 20:58:13 2023 +0200 ComplexColor various clean-up and (trivial) refactorings Don't allow access to member variables of ComplexColor and makes them private. Needs a lot of changes. Change "scheme" to "theme" to be more consistent. In LO we usually call the "theme color" what is usually refered to as "scheme color" in OOXML, where it is sometimes refered to as "scheme" and other times as theme color. Remove ThemeColor class which was replaced with CmplexColor some time ago. Remove un-needed includes and un-needed components. Use isValidThemeColor in many places where we check that the ComplexColor is of "Theme" type and that ThemeColorType is set to a valid value. Change-Id:
[Libreoffice-bugs] [Bug 32884] support session management for KDE, GTK so SessionSave runs on OS logout/shutdown
https://bugs.documentfoundation.org/show_bug.cgi?id=32884 Justin L changed: What|Removed |Added See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=10 ||9085 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 109085] LO exits abruptly when logging off in Windows while LO is running (needs to run SessionSave)
https://bugs.documentfoundation.org/show_bug.cgi?id=109085 Justin L changed: What|Removed |Added Summary|LO exits abruptly when |LO exits abruptly when |logging off in Windows |logging off in Windows |while LO is running |while LO is running (needs ||to run SessionSave) Version|5.4.0.1 rc |Inherited From OOo See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=32 ||884 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 32884] support session management for KDE, GTK so SessionSave runs on OS logout/shutdown
https://bugs.documentfoundation.org/show_bug.cgi?id=32884 Justin L changed: What|Removed |Added OS|All |Linux (All) Version|3.4.4 release |unspecified Summary|recovery should |support session management |differentiate between |for KDE, GTK so SessionSave |crashes and session |runs on OS logout/shutdown |restoring | --- Comment #10 from Justin L --- I learned a bit more about AutoRecovery today. (In reply to Mark from comment #0) > At the moment LibreOffice what happens when LibreOffice was closed without > all documents saved is something which was seemingly build for a crash There are three types of AutoRecovery. Timed autorecovery is for hard crashes, and EmergencySave is for soft crashes. The OS sending a kill signal would trigger one of these two, which you are probably experiencing. The third type is a SessionSave, and it does restore all documents silently. It even silently ignores /tmp files etc. > I use Linux (KDE) which has the benefit of a session management. Based on my commit reading, it sounds like work was done to support KDE session management. However, in my testing I didn't get it to work. However, all the pieces are there - they just need to be wired up properly. vcl/unx/generic/app/sm.cxx vcl/source/app/session.cxx > I wish that LibreOffice would handle this specific case better: A valid desire. Needed for KDE, GTK, Windows (bug 109085). > - If I am using session management, I do not want to answer any questions, > which documents should be restored. It should just happen. If officecfg::Office::Recovery::RecoveryInfo::SessionData is true instead of officecfg::Office::Recovery::RecoveryInfo::Crashed, it will be silent. > - It does not make sense to try and restore documents which were stored in > the /tmp-folder since this will be deleted on reboot. Or SessionSave could ensure there is a recoveryFile available for them. This would certainly be useful for USB or disconnected server files. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 126933] LO Writer shows some Buttons almost Unreadable when using High Contrast Theme
https://bugs.documentfoundation.org/show_bug.cgi?id=126933 --- Comment #23 from Buovjaga --- (In reply to Adalbert Hanßen from comment #22) > Created attachment 188981 [details] > the same test done again, trying with colibre, which might not have been set > > (In reply to Buovjaga from comment #21) > > (In reply to Adalbert Hanßen from comment #20) > >... > > > > You are again testing with Sifr even though I requested to test with > > Colibre. > > > Buovjaga, sorry for my misunderstanding. > > I have repeated the test with LibreOfficeDev, but possibly I was unable to > use Colibre, see attached bug report. Feel free to log this as a separate > bug report, if my suspicion is right, that selecting Colibre instead of Sifr > dir not work in my version. I think your Linux distribution is forcing you to use Sifr due to choosing high contrast in the Xfce settings. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 144073] UI. Corner of screen appears white when presenting, using the Lights template (Windows-only)
https://bugs.documentfoundation.org/show_bug.cgi?id=144073 Patrick Luby changed: What|Removed |Added See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=15 ||6539 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156539] Fontwork with transparency won't be visible in presentation mode with Skia Raster
https://bugs.documentfoundation.org/show_bug.cgi?id=156539 Patrick Luby changed: What|Removed |Added See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=14 ||4073 --- Comment #10 from Patrick Luby --- (In reply to Telesto from comment #9) > The gradient fill issue mentioned at comment 2 is likely bug 147645 I also noticed that after the fixes for bug 144073, gradient fill is also missing. I believe that part of this bug and the missing gradient fill in bug 144073 are caused by code surrounding the code in the following commit: https://cgit.freedesktop.org/libreoffice/core/commit/?id=adc2ac31fb2763077e48658756946a39d91c8e12 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 129062] [META] Skia library bugs
https://bugs.documentfoundation.org/show_bug.cgi?id=129062 Bug 129062 depends on bug 153306, which changed state. Bug 153306 Summary: Cursor leftovers keep being displayed when using Skia Vulkan/Metal https://bugs.documentfoundation.org/show_bug.cgi?id=153306 What|Removed |Added Status|NEW |RESOLVED Resolution|--- |FIXED -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153306] Cursor leftovers keep being displayed when using Skia Vulkan/Metal
https://bugs.documentfoundation.org/show_bug.cgi?id=153306 Patrick Luby changed: What|Removed |Added Resolution|--- |FIXED Status|NEW |RESOLVED --- Comment #15 from Patrick Luby --- So it seems that this bug is fixed in master so I am marking it as resolved/fixed. I assume that the fix is a byproduce of commit 81994cb2b8b32453a92bcb011830fcb884f22ff3 which included several changes for inverting bitmaps and alpha masks. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-commits] core.git: Branch 'feature/cib_contract57d' - 2 commits - sw/qa sw/source
sw/qa/extras/layout/data/fdo56797-2-min.odt |binary
sw/qa/extras/layout/layout.cxx | 31
sw/source/core/layout/layact.cxx|6 ++---
3 files changed, 34 insertions(+), 3 deletions(-)
New commits:
commit 70265179db368c1f3f5d4463bcb303be88c07e10
Author: Michael Stahl
AuthorDate: Mon Aug 14 17:27:52 2023 +0200
Commit: Thorsten Behrens
CommitDate: Tue Aug 15 20:20:34 2023 +0200
tdf#156724 tdf#156722 sw: layout: remove IsPaintLocked() check
Get rid of the problematic IsPaintLocked() and only check for a column
parent; effectively this prevents formatting frames in columns even when
loaded from the UI, so the layout will hopefully be the same regardless
of how it is invoked.
Change-Id: Ib4cc2efdb68ef4db73dcad01c7e1bd4be35de071
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/155673
Tested-by: Jenkins
Reviewed-by: Michael Stahl
(cherry picked from commit 61a78a523a6131ff98b5d846368e5626fe58d99c)
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/155710
Tested-by: Thorsten Behrens
Reviewed-by: Thorsten Behrens
diff --git a/sw/source/core/layout/layact.cxx b/sw/source/core/layout/layact.cxx
index 88185c8de95a..2de17673e0e2 100644
--- a/sw/source/core/layout/layact.cxx
+++ b/sw/source/core/layout/layact.cxx
@@ -1365,7 +1365,7 @@ bool SwLayAction::FormatLayout( OutputDevice
*pRenderContext, SwLayoutFrame *pLa
else if( !pLow->IsSctFrame() ||
static_cast(pLow)->GetSection() )
bChanged |= FormatLayout( pRenderContext,
static_cast(pLow), bAddRect );
}
-else if (m_pImp->GetShell()->IsPaintLocked() ||
!pLay->IsColBodyFrame())
+else if (!pLay->IsColBodyFrame())
{ // tdf#156724 unconditionally for frames in tables, so their
footnotes exist before trying to split
pLow->OptCalc();
}
commit 46274983c3ac31a0580a4baeb26e3b5d79ed3c91
Author: Michael Stahl
AuthorDate: Mon Aug 14 17:13:17 2023 +0200
Commit: Thorsten Behrens
CommitDate: Tue Aug 15 20:20:22 2023 +0200
tdf#156724 tdf#156722 tdf#156745 sw: layout: partially remove
IsPaintLocked()
Having the layout algorithm dependend on IsPaintLocked() is very
problematic; it is typically set when the layout is invoked from
SwViewShell code, as happens several times when loading a document in
response to window resize events etc., but not for idle formatting or
from SwXTextDocument::getRendererCount(), hence these bugs only
reproduce with soffice --convert-to pdf, not via UI.
For tdf#156724 the problem is that the table is split, during formatting
of the split row a new footnote is created on page 1, and this reduces
the space, so splitting fails and is never attempted again.
When the document is loaded from UI, when the table is split the
footnote already exists and so splitting succeeds; it was created by
a call from SwLayAction::FormatLayout() of the cell frame.
It turns out that when the condition is removed completely, testUXTSOREL
will take 5 minutes instead of 5 seconds, which seems excessive; the
problem there appears to be that a text frame in a columned section
moves forward and backward; plausibly columned section content should be
formatted by ::CalcContent() only.
(reportedly regression from commit c605283ad6785dea762feab5fdffd9d27e75c292
and commit
7e8b4756d95057f069467b34e7849f9354856578)
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/155672
Tested-by: Michael Stahl
Reviewed-by: Michael Stahl
(cherry picked from commit 610c6f02b11b4b4c555a78b0feb2a1eb35159e39)
Change-Id: I9ed73588efeec654a769eee8aa825186bd51e059
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/155689
Tested-by: Thorsten Behrens
Reviewed-by: Thorsten Behrens
diff --git a/sw/qa/extras/layout/data/fdo56797-2-min.odt
b/sw/qa/extras/layout/data/fdo56797-2-min.odt
new file mode 100644
index ..624149ec0248
Binary files /dev/null and b/sw/qa/extras/layout/data/fdo56797-2-min.odt differ
diff --git a/sw/qa/extras/layout/layout.cxx b/sw/qa/extras/layout/layout.cxx
index 11c502d4c09d..f72715fcba43 100644
--- a/sw/qa/extras/layout/layout.cxx
+++ b/sw/qa/extras/layout/layout.cxx
@@ -3641,6 +3641,37 @@ CPPUNIT_TEST_FIXTURE(SwLayoutWriter, testTdf155324)
assertXPath(pXmlDoc, "/root/page[5]/ftncont/ftn", 5);
}
+CPPUNIT_TEST_FIXTURE(SwLayoutWriter, testTdf156724)
+{
+discardDumpedLayout();
+if (mxComponent.is())
+mxComponent->dispose();
+
+OUString const url(m_directories.getURLFromSrc(DATA_DIRECTORY) +
"/fdo56797-2-min.odt");
+
+// note: must set Hidden property, so that
SfxFrameViewWindow_Impl::Resize()
+// does *not* forward initial VCL Window Resize and thereby triggers a
+// layout which does not happen on soffice --convert-to pdf.
+std::vector
[Libreoffice-commits] core.git: Branch 'feature/cib_contract57d' - configure.ac
configure.ac |2 +- 1 file changed, 1 insertion(+), 1 deletion(-) New commits: commit 687147ba9ff646c76347380ca13fd7c09acf618f Author: Thorsten Behrens AuthorDate: Tue Aug 15 20:14:49 2023 +0200 Commit: Thorsten Behrens CommitDate: Tue Aug 15 20:14:49 2023 +0200 Release 6.3.6.28 Change-Id: I6b3e703968a82c8d48f4d0cec8605177a246f3eb diff --git a/configure.ac b/configure.ac index 1b71847401b9..e7779a82ce49 100644 --- a/configure.ac +++ b/configure.ac @@ -9,7 +9,7 @@ dnl in order to create a configure script. # several non-alphanumeric characters, those are split off and used only for the # ABOUTBOXPRODUCTVERSIONSUFFIX in openoffice.lst. Why that is necessary, no idea. -AC_INIT([LibreOffice],[6.3.6.27],[],[],[http://documentfoundation.org/]) +AC_INIT([LibreOffice],[6.3.6.28],[],[],[http://documentfoundation.org/]) dnl libnumbertext needs autoconf 2.68, but that can pick up autoconf268 just fine if it is installed dnl whereas aclocal (as run by autogen.sh) insists on using autoconf and fails hard
[Libreoffice-bugs] [Bug 88278] [META] SVG import image filter (all modules)
https://bugs.documentfoundation.org/show_bug.cgi?id=88278 Xisco Faulí changed: What|Removed |Added Depends on||156777 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=156777 [Bug 156777] SVG: incorrect style in textPath -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156198] LibreOffice can't create .lock file for opened document with CIFS using
https://bugs.documentfoundation.org/show_bug.cgi?id=156198 --- Comment #8 from Roman --- So I believe that the problem of disappearing files exists in the open for reading mode. That is, this mode tries to fix the lock, thereby deleting it, due to the absence of entries in this file. Так что полагаю что проблема исчезновения файлов, существует в режиме открыть для чтения. То есть этот режим пытается починить lock, тем самым удаляя его, по причине отсутствия в этом файле записей. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156198] LibreOffice can't create .lock file for opened document with CIFS using
https://bugs.documentfoundation.org/show_bug.cgi?id=156198 --- Comment #7 from Roman --- Created attachment 188984 --> https://bugs.documentfoundation.org/attachment.cgi?id=188984=edit read_only -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156777] SVG: incorrect style in textPath
https://bugs.documentfoundation.org/show_bug.cgi?id=156777 Xisco Faulí changed: What|Removed |Added Assignee|libreoffice-b...@lists.free |xiscofa...@libreoffice.org |desktop.org | CC||xiscofa...@libreoffice.org Status|UNCONFIRMED |ASSIGNED Ever confirmed|0 |1 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156777] New: SVG: incorrect style in textPath
https://bugs.documentfoundation.org/show_bug.cgi?id=156777 Bug ID: 156777 Summary: SVG: incorrect style in textPath Product: LibreOffice Version: 24.2.0.0 alpha0+ Master Hardware: All OS: All Status: UNCONFIRMED Severity: normal Priority: medium Component: filters and storage Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: xiscofa...@libreoffice.org Created attachment 188983 --> https://bugs.documentfoundation.org/attachment.cgi?id=188983=edit sample file Steps to reproduce: 1. Open attached document -> Text fill should be green. it's black Reproduced in Version: 24.2.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: dedf098e742550622cec6fdc639550371d9e58cf CPU threads: 8; OS: Linux 5.10; UI render: default; VCL: gtk3 Locale: es-ES (es_ES.UTF-8); UI: en-US Calc: threaded -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156198] LibreOffice can't create .lock file for opened document with CIFS using
https://bugs.documentfoundation.org/show_bug.cgi?id=156198 Roman changed: What|Removed |Added Ever confirmed|0 |1 Status|UNCONFIRMED |NEW --- Comment #6 from Roman --- You won't believe it!, but it's straight original. I quote verbatim from an error deduced by chance. "The lock file is corrupted" "The lock file is corrupted and probably empty. Opening the document for reading and closing it will delete the corrupted lock file." "Select Notify to open read-only and get notified when the document becomes editable." Since I haven't seen nbrl yet where it came from, and we don't have it yet and opening the file turns out to be a useless activity, so I have fewer requests. Then I quote the people who tested LO. They found a function that disables .the lock file, and during further testing received the disappearance of documents. Ты не поверишь!, но это прям оригинально. Цитирую дословно с ошибки выведенной случайно. «Файл блокировки повреждён» «Файл блокировки повреждён и, вероятно, пуст. Открытие документа для чтения и его закрытия удалит повреждённый файл блокировки.» «Выберите Уведомить, чтобы открыть только для чтения и получить уведомление, когда документ станет доступны для редактирования.» Так как nobrl я ещё не видел откуда она взялась, а у нас её ещё нету и открытие файла получается бесполезным занятием, поэтому кол-во обращений у меня поменьше. Дальше цитирую людей которые тестили LO. Они нашли функцию которая отключает .lock файл, и при дальнейшем тестировании получили исчезновение документов. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 154020] DOC with Mac-Picts: images don't import
https://bugs.documentfoundation.org/show_bug.cgi?id=154020 --- Comment #8 from bunkem --- Thanks @Mike. The additional info is very helpful. I'm old enough to remember MS Word 6 for Mac and still have the install discs. Oh my was that software a piece of s**t. I got on the first name basis with many MS support staff due to all the problems. :LOL: I remember there were numerous graphics issues with Word 6 but can't remember if this happened when the software converted the PICT images to Microsoft BMP or EMF images. @ilmari, we need your input. I can confirm the issue and being able to open old doc files created on Word Mac should work. I'm not sure if there is a time line on how long old files need to be usable or convertible using the current versions of LO. I can't test further since I don't have old enough hardware to run Word 6 Mac and Apple/Mac PICT files have been official unsupported for at least a decade. Should this be pushed to Document Liberation project that deals with file conversions?? -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 91614] Inserting of SVG containing text put on a path has incorrect offset for text
https://bugs.documentfoundation.org/show_bug.cgi?id=91614 --- Comment #13 from Xisco Faulí --- (In reply to Xisco Faulí from comment #12) > Issue related to startOffset="50%" sorry, issue related to text-anchor:middle -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 146769] Reopen documents from previous session on start
https://bugs.documentfoundation.org/show_bug.cgi?id=146769 --- Comment #17 from Justin L --- A patch that re-purposes SID_LOGOUT to "Exit with session save" is at https://gerrit.libreoffice.org/c/core/+/155460. I'm not yet ready to propose it for submission though, since I took a lot of liberties. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156768] No page number wizard found in LibreOffice Writer 7.6
https://bugs.documentfoundation.org/show_bug.cgi?id=156768 --- Comment #4 from David García --- This has been marked as the duplicate of a bug, so I understand it's considered undesired behaviour. I wish it can be fixed because it's a nuisance to have to reset parts of LibreOffice in order to access to new features. I would have never known about the page number wizard if I hadn't read the release notes for version 7.6, which is something that most users don't do, I presume. In any case, thanks again for all the help! -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-commits] core.git: framework/source vcl/source
framework/source/services/sessionlistener.cxx |3 ++-
vcl/source/app/session.cxx|4 +++-
2 files changed, 5 insertions(+), 2 deletions(-)
New commits:
commit 918cd8cbf383e0099d80db2e12a1071a0bc4f200
Author: Justin Luth
AuthorDate: Tue Aug 15 08:55:09 2023 -0400
Commit: Justin Luth
CommitDate: Tue Aug 15 19:04:45 2023 +0200
VCLSession: avoid null dereferences
Found while I was (mis)using
XSessionManagerListener2 in
https://gerrit.libreoffice.org/c/core/+/155460
But I think these are valid anyway.
Certainly one is when it is checked in the try clause
but not in the catch clause.
Change-Id: Ia3f7211e4a4c86dd503ffe1b04e5b5c13227218e
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/155719
Tested-by: Jenkins
Reviewed-by: Justin Luth
diff --git a/framework/source/services/sessionlistener.cxx
b/framework/source/services/sessionlistener.cxx
index 188b082fe94c..a77e7f961ebb 100644
--- a/framework/source/services/sessionlistener.cxx
+++ b/framework/source/services/sessionlistener.cxx
@@ -366,7 +366,8 @@ void SAL_CALL SessionListener::approveInteraction( sal_Bool
bInteractionGranted
catch( const css::uno::Exception& )
{
StoreSession( true );
-m_rSessionManager->interactionDone( this );
+if (m_rSessionManager.is())
+m_rSessionManager->interactionDone(this);
}
if ( m_rSessionManager.is() && m_bTerminated )
diff --git a/vcl/source/app/session.cxx b/vcl/source/app/session.cxx
index c0dfe71d7bc3..3b1bf3565bb2 100644
--- a/vcl/source/app/session.cxx
+++ b/vcl/source/app/session.cxx
@@ -309,7 +309,9 @@ void SAL_CALL VCLSession::queryInteraction( const
css::uno::ReferencequeryInteraction();
+if (m_xSession)
+m_xSession->queryInteraction();
+
m_bInteractionRequested = true;
}
for (auto & listener: m_aListeners)
[Libreoffice-bugs] [Bug 156776] Base Save As New Table Name not refreshed
https://bugs.documentfoundation.org/show_bug.cgi?id=156776 --- Comment #7 from Robert Großkopf --- (In reply to prrvchr from comment #3) > Hi Robert, > > If we use the default names proposed by Base (Table1, Table2, Table...) the > conflict only occurs when we create the second table in this same schema and > this schema is not selected by default in the save as dialog box... Hi prrvchr, have tested with PostgreSQL direct driver, PostgreSQL JDBC connection, MariaDB JDBC connection. Could create as many tables as I want in the schema, which isn't selected as default schema. All tables will directly appear in the schema. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-commits] core.git: Branch 'libreoffice-7-6' - 2 commits - svgio/inc svgio/Library_svgio.mk svgio/qa svgio/source
svgio/Library_svgio.mk|1
svgio/inc/svgcharacternode.hxx| 98 ---
svgio/inc/svgtextnode.hxx | 11
svgio/inc/svgtextposition.hxx | 72 +
svgio/inc/svgtspannode.hxx| 51 +++-
svgio/qa/cppunit/SvgImportTest.cxx| 140 ++-
svgio/qa/cppunit/data/tdf151103.svg | 18 +
svgio/qa/cppunit/data/tdf156616.svg | 29 ++
svgio/source/svgreader/svgcharacternode.cxx | 322 +++---
svgio/source/svgreader/svgdocumenthandler.cxx | 92 ++-
svgio/source/svgreader/svgtextnode.cxx| 25 --
svgio/source/svgreader/svgtextposition.cxx| 200
svgio/source/svgreader/svgtspannode.cxx | 85 ++
13 files changed, 668 insertions(+), 476 deletions(-)
New commits:
commit 87e0ac2b92f7a7aac16bf66d2379688238496a75
Author: Xisco Fauli
AuthorDate: Sat Aug 12 02:28:02 2023 +0200
Commit: Xisco Fauli
CommitDate: Tue Aug 15 19:01:22 2023 +0200
tdf#156616: check if character's parent has x or y
if so, only concatenate the characters that are in the same line
so the alignment will be calculated based on the
line's width
Change-Id: I704370c0a470f8b4cff97c51ad9863158118ee8a
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/155636
Tested-by: Jenkins
Reviewed-by: Xisco Fauli
Signed-off-by: Xisco Fauli
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/155657
diff --git a/svgio/inc/svgcharacternode.hxx b/svgio/inc/svgcharacternode.hxx
index 391c4029e46c..059aa9ece1fd 100644
--- a/svgio/inc/svgcharacternode.hxx
+++ b/svgio/inc/svgcharacternode.hxx
@@ -40,7 +40,7 @@ namespace svgio::svgreader
// keep a copy of string data before space handling
OUString maTextBeforeSpaceHandling;
-SvgTextNode*mpTextParent;
+SvgTspanNode*mpParentLine;
/// local helpers
rtl::Reference
createSimpleTextPrimitive(
@@ -68,7 +68,7 @@ namespace svgio::svgreader
/// Text content
const OUString& getText() const { return maText; }
-void setTextParent(SvgTextNode* pTextParent) { mpTextParent =
pTextParent; }
+void setParentLine(SvgTspanNode* pParentLine) { mpParentLine =
pParentLine; }
};
} // end of namespace svgio::svgreader
diff --git a/svgio/inc/svgtextnode.hxx b/svgio/inc/svgtextnode.hxx
index 2d5f98ec18fc..787687977e11 100644
--- a/svgio/inc/svgtextnode.hxx
+++ b/svgio/inc/svgtextnode.hxx
@@ -33,10 +33,6 @@ namespace svgio::svgreader
std::optional
mpaTransform;
-// The text line composed by the different SvgCharacterNode
children
-// it will be used to calculate their alignment
-OUString maTextLine;
-
/// local helpers
void DecomposeChild(
const SvgNode& rCandidate,
@@ -59,9 +55,6 @@ namespace svgio::svgreader
/// transform content, set if found in current context
const std::optional& getTransform() const {
return mpaTransform; }
void setTransform(const std::optional&
pMatrix) { mpaTransform = pMatrix; }
-
-void concatenateTextLine(std::u16string_view rText) {maTextLine +=
rText;}
-const OUString& getTextLine() const { return maTextLine; }
};
} // end of namespace svgio::svgreader
diff --git a/svgio/inc/svgtspannode.hxx b/svgio/inc/svgtspannode.hxx
index d5d86c5a7c1a..92ed8319c628 100644
--- a/svgio/inc/svgtspannode.hxx
+++ b/svgio/inc/svgtspannode.hxx
@@ -39,6 +39,10 @@ namespace svgio::svgreader
boolmbLengthAdjust : 1; // true = spacing,
false = spacingAndGlyphs
+// The text line composed by the different SvgCharacterNode
children
+// it will be used to calculate their alignment
+OUString maTextLine;
+
public:
SvgTspanNode(
SVGToken aType,
@@ -78,6 +82,9 @@ namespace svgio::svgreader
/// LengthAdjust content
bool getLengthAdjust() const { return mbLengthAdjust; }
void setLengthAdjust(bool bNew) { mbLengthAdjust = bNew; }
+
+void concatenateTextLine(std::u16string_view rText) {maTextLine +=
rText;}
+const OUString& getTextLine() const { return maTextLine; }
};
} // end of namespace svgio::svgreader
diff --git a/svgio/qa/cppunit/SvgImportTest.cxx
b/svgio/qa/cppunit/SvgImportTest.cxx
index c52e20594b10..42cb98c4b6be 100644
--- a/svgio/qa/cppunit/SvgImportTest.cxx
+++ b/svgio/qa/cppunit/SvgImportTest.cxx
@@ -740,7 +740,45 @@ CPPUNIT_TEST_FIXTURE(Test, testTdf85770)
assertXPath(pDocument, "/primitive2D/transform/textsimpleportion[3]",
"text", " End");
assertXPath(pDocument,
[Libreoffice-ux-advise] [Bug 94989] ENHANCEMENT: Select all text with the same formatting
https://bugs.documentfoundation.org/show_bug.cgi?id=94989 Eyal Rozenberg changed: What|Removed |Added CC||eyalr...@gmx.com --- Comment #9 from Eyal Rozenberg --- (In reply to Heiko Tietze from comment #7) > We resolved requests like this by pointing to the F dialog. And reading > comment 1 and 2 seems to do it here too. Why not close WF/NAB? The F is absolutely not the place anyone would look for this functionality, because: 1. Neither "Find" nor "Replace" suggests "Select", and certainly not "Select all at once". 2. That functionality in the F dialog kind of bastardizes it, replacing the "Replace" box with a drop-down listbox; it doesn't seem to naturally fit there. 2. I personally keep forgetting I can do that through the F dialog, and that's after I've seen it before already! 3. F is not something that's opened from any context that involves styles. So, not only should this not be closed, I'd say that the accessibility only through F is even a (usability) _bug_. So I would remove the "enhancement" characterization and make it a regular bug. (In reply to Stéphane Guillou (stragu) from comment #6) > I think a context menu item would be an overkill, Ah, but a context menu for the main Writer pane; the context menu for styles in the sidebar. -- You are receiving this mail because: You are on the CC list for the bug.
[Libreoffice-bugs] [Bug 94989] ENHANCEMENT: Select all text with the same formatting
https://bugs.documentfoundation.org/show_bug.cgi?id=94989 Eyal Rozenberg changed: What|Removed |Added CC||eyalr...@gmx.com --- Comment #9 from Eyal Rozenberg --- (In reply to Heiko Tietze from comment #7) > We resolved requests like this by pointing to the F dialog. And reading > comment 1 and 2 seems to do it here too. Why not close WF/NAB? The F is absolutely not the place anyone would look for this functionality, because: 1. Neither "Find" nor "Replace" suggests "Select", and certainly not "Select all at once". 2. That functionality in the F dialog kind of bastardizes it, replacing the "Replace" box with a drop-down listbox; it doesn't seem to naturally fit there. 2. I personally keep forgetting I can do that through the F dialog, and that's after I've seen it before already! 3. F is not something that's opened from any context that involves styles. So, not only should this not be closed, I'd say that the accessibility only through F is even a (usability) _bug_. So I would remove the "enhancement" characterization and make it a regular bug. (In reply to Stéphane Guillou (stragu) from comment #6) > I think a context menu item would be an overkill, Ah, but a context menu for the main Writer pane; the context menu for styles in the sidebar. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 126933] LO Writer shows some Buttons almost Unreadable when using High Contrast Theme
https://bugs.documentfoundation.org/show_bug.cgi?id=126933 --- Comment #22 from Adalbert Hanßen --- Created attachment 188981 --> https://bugs.documentfoundation.org/attachment.cgi?id=188981=edit the same test done again, trying with colibre, which might not have been set (In reply to Buovjaga from comment #21) > (In reply to Adalbert Hanßen from comment #20) >... > > You are again testing with Sifr even though I requested to test with Colibre. Buovjaga, sorry for my misunderstanding. I have repeated the test with LibreOfficeDev, but possibly I was unable to use Colibre, see attached bug report. Feel free to log this as a separate bug report, if my suspicion is right, that selecting Colibre instead of Sifr dir not work in my version. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156776] Base Save As New Table Name not refreshed
https://bugs.documentfoundation.org/show_bug.cgi?id=156776 --- Comment #6 from Julien Nabet --- (In reply to prrvchr from comment #5) > I would like to find the code for the Save As dialog? > > Because I think there is no handler on the drop-down list of schemas > allowing the update of the default table name... I didn't check but perhaps https://opengrok.libreoffice.org/search?project=core==OSaveAsDlg==1=defs=defs may help. You can put breakpoint + use "bt" in gdb and/or add some fprintf. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-ux-advise] [Bug 156702] Make it easier to crop page to contents / selection
https://bugs.documentfoundation.org/show_bug.cgi?id=156702 --- Comment #3 from Eyal Rozenberg --- (In reply to Heiko Tietze from comment #1) > *** This bug has been marked as a duplicate of bug 81118 *** Fixing 81118 would go a long way towards fixing the problem, but this functionality should be accessible from at least one, and perhaps more, additional places. -- You are receiving this mail because: You are on the CC list for the bug.
[Libreoffice-bugs] [Bug 156702] Make it easier to crop page to contents / selection
https://bugs.documentfoundation.org/show_bug.cgi?id=156702 --- Comment #3 from Eyal Rozenberg --- (In reply to Heiko Tietze from comment #1) > *** This bug has been marked as a duplicate of bug 81118 *** Fixing 81118 would go a long way towards fixing the problem, but this functionality should be accessible from at least one, and perhaps more, additional places. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-ux-advise] [Bug 156702] Make it easier to crop page to contents / selection
https://bugs.documentfoundation.org/show_bug.cgi?id=156702 Eyal Rozenberg changed: What|Removed |Added Status|RESOLVED|UNCONFIRMED Resolution|DUPLICATE |--- Depends on||81118 --- Comment #2 from Eyal Rozenberg --- (In reply to Heiko Tietze from comment #1) > *** This bug has been marked as a duplicate of bug 81118 *** Fixing 81118 would go a long way towards fixing the problem, but this functionality should be accessible from at least one, and perhaps more, additional places. Please Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=81118 [Bug 81118] UI: add "fit page size to drawing" button to the page format window -- You are receiving this mail because: You are on the CC list for the bug.
[Libreoffice-bugs] [Bug 81118] UI: add "fit page size to drawing" button to the page format window
https://bugs.documentfoundation.org/show_bug.cgi?id=81118 Eyal Rozenberg changed: What|Removed |Added Blocks||156702 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=156702 [Bug 156702] Make it easier to crop page to contents / selection -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156702] Make it easier to crop page to contents / selection
https://bugs.documentfoundation.org/show_bug.cgi?id=156702 Eyal Rozenberg changed: What|Removed |Added Status|RESOLVED|UNCONFIRMED Resolution|DUPLICATE |--- Depends on||81118 --- Comment #2 from Eyal Rozenberg --- (In reply to Heiko Tietze from comment #1) > *** This bug has been marked as a duplicate of bug 81118 *** Fixing 81118 would go a long way towards fixing the problem, but this functionality should be accessible from at least one, and perhaps more, additional places. Please Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=81118 [Bug 81118] UI: add "fit page size to drawing" button to the page format window -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 108764] LibreOffice Writer and PDF export don’t respect the SVG 'crispEdges' value for the shape-rendering attribute
https://bugs.documentfoundation.org/show_bug.cgi?id=108764 --- Comment #15 from miikka.salmi...@gmail.com --- The bug is still present in the latest version of LibreOffice. Help -> About LibreOffice: Version: 7.5.5.2 (X86_64) / LibreOffice Community Build ID: ca8fe7424262805f223b9a2334bc7181abbcbf5e CPU threads: 24; OS: Windows 10.0 Build 19045; UI render: Skia/Raster; VCL: win Locale: fi-FI (en_FI); UI: en-US Calc: threaded -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156685] Default font color in tables is white over white background (font color should be black)
https://bugs.documentfoundation.org/show_bug.cgi?id=156685 Regina Henschel changed: What|Removed |Added See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=15 ||6182 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-ux-advise] [Bug 156182] FORMATTING Automatic text color can be unreadable with darker cell colors
https://bugs.documentfoundation.org/show_bug.cgi?id=156182 Regina Henschel changed: What|Removed |Added See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=15 ||6685 CC||rb.hensc...@t-online.de --- Comment #20 from Regina Henschel --- Please reconsider the threshold. See the discussion in bug 156685. Less or equal 150 would not mark the default background color as "dark" and should be high enough for cell backgrounds. -- You are receiving this mail because: You are on the CC list for the bug.
