[Libreoffice-commits] core.git: sw/inc sw/source
sw/inc/editsh.hxx |4 +++
sw/source/core/edit/eddel.cxx | 46
sw/source/core/edit/edlingu.cxx | 15 ---
sw/source/uibase/shells/textsh1.cxx | 23 ++
4 files changed, 54 insertions(+), 34 deletions(-)
New commits:
commit 6da9d629f7f17ec569e7fb6d0f1931dd410b1d28
Author: EMartinGube
AuthorDate: Thu Jul 20 23:33:37 2023 +0200
Commit: Mike Kaganski
CommitDate: Sun Oct 15 07:42:07 2023 +0200
tdf#156250: sw: Keep comments when spell correction replaces a word
New method SwEditShell:ReplaceKeepComments for comment preserving
spell correction.
Change-Id: Ifdb9d5664ab8d457a16ad8f7ec62dd968c89d580
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/154761
Tested-by: Jenkins
Reviewed-by: Mike Kaganski
diff --git a/sw/inc/editsh.hxx b/sw/inc/editsh.hxx
index 8fc1afb9483a..a3b181440237 100644
--- a/sw/inc/editsh.hxx
+++ b/sw/inc/editsh.hxx
@@ -172,6 +172,10 @@ public:
--> "xx\t..zzz..&" */
bool Replace( const OUString& rNewStr, bool bRegExpRplc );
+/** Replace a selected range in a TextNode by given string.
+ Possible comments will be kept (moved to the end of the selection). */
+bool ReplaceKeepComments( const OUString& rNewStr);
+
/** Delete content of all ranges.
If whole nodes are selected, these nodes get deleted. */
bool Delete(bool isArtificialSelection = false);
diff --git a/sw/source/core/edit/eddel.cxx b/sw/source/core/edit/eddel.cxx
index 10d086bbac63..989cddfd3a28 100644
--- a/sw/source/core/edit/eddel.cxx
+++ b/sw/source/core/edit/eddel.cxx
@@ -359,6 +359,52 @@ bool SwEditShell::Replace( const OUString& rNewStr, bool
bRegExpRplc )
return bRet;
}
+/** Replace a selected area in a text node with a given string.
+ *
+ * Method to replace a text selection with a new string while
+ * keeping possible comments (they will be moved to the end
+ * of the selection).
+ *
+ * @param rNewStr the new string which the selected area is to be replaced
with
+ * @returntrue, if something has been replaced, false otherwise.
+ */
+bool SwEditShell::ReplaceKeepComments( const OUString& rNewStr)
+{
+bool bRet = false;
+SwPaM *pCursor = GetCursor();
+
+if(pCursor != nullptr)
+{
+// go sure that the text selection pointed to by pCursor is valid
+if(pCursor->HasMark())
+{
+// preserve comments inside of the number by deleting number
portions starting from the back
+OUString aSelectedText = pCursor->GetText();
+sal_Int32 nCommentPos(aSelectedText.lastIndexOf(CH_TXTATR_INWORD));
+// go sure that we have a valid selection and a comment has been
found
+while((nCommentPos > -1) && (aSelectedText.getLength() > 0) &&
(pCursor->HasMark()))
+{
+// select the part of the text after the last found comment
+// selection start:
+pCursor->GetPoint()->AdjustContent(nCommentPos + 1);
+// selection end ist left where it is -> will be adjusted
later on
+// delete the part of the word after the last found comment
+Replace(OUString(), false);
+// put the selection start back to the beginning of the word
+pCursor->GetPoint()->AdjustContent(-(nCommentPos + 1));
+// adjust the selection end, so that the last comment is no
longer selected:
+pCursor->GetMark()->AdjustContent(-1);
+// search for the next possible comment
+aSelectedText = pCursor->GetText();
+nCommentPos = aSelectedText.lastIndexOf(CH_TXTATR_INWORD);
+}
+bRet = Replace(rNewStr, false);
+}
+}
+
+return bRet;
+}
+
/// special method for JOE's wizards
bool SwEditShell::DelFullPara()
{
diff --git a/sw/source/core/edit/edlingu.cxx b/sw/source/core/edit/edlingu.cxx
index ab89fc5b7241..63ea37ba8233 100644
--- a/sw/source/core/edit/edlingu.cxx
+++ b/sw/source/core/edit/edlingu.cxx
@@ -1167,20 +1167,7 @@ void SwEditShell::ApplyChangedSentence(const
svx::SpellPortions& rNewPortions, b
// if there is a comment inside the original word, don't
delete it:
// but keep it at the end of the replacement
-// TODO: keep all the comments with a recursive function
-sal_Int32
nCommentPos(pCursor->GetText().indexOf(OUStringChar(CH_TXTATR_INWORD)));
-if ( nCommentPos > -1 )
-{
-// delete the original word after the comment
-pCursor->GetPoint()->AdjustContent(nCommentPos + 1);
-
-
mxDoc->getIDocumentContentOperations().ReplaceRange(*pCursor, OUString(),
false);
-// and select only the remaining part before the comment
-
[Libreoffice-bugs] [Bug 106179] [META] Writer comment bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=106179 Dieter changed: What|Removed |Added URL|https://ww-peacocktv.com/tv | |/ | -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 106179] [META] Writer comment bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=106179 --- Comment #67 from Know You --- This website is really amazing and get on https://grouplinkonly.com/tamil-girls-whatsapp-group-link/ for amazing contents. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 66567] SLIDESHOW: impress slideshow shows empty slides if the monitor has too high resolution
https://bugs.documentfoundation.org/show_bug.cgi?id=66567 saintjones changed: What|Removed |Added Resolution|DUPLICATE |FIXED --- Comment #15 from saintjones --- The Lowe’s survey is a customer feedback survey that rewards participants with a chance to win a $500 gift card. Visit https://lowescomsurvey.co/ official survey portal to complete the Lowes guest satisfaction survey and learn more to get Lowes sweepstakes within 5 minutes. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 157780] Calc: Web hyperlinks not preserved after export to PDF
https://bugs.documentfoundation.org/show_bug.cgi?id=157780 FranDries changed: What|Removed |Added Ever confirmed|1 |0 Status|NEEDINFO|UNCONFIRMED --- Comment #3 from FranDries --- I looked at tdf#155351 describing formatting issues after Export to PDF, but this seems unrelated to the current very specific issue of invalid web hyperlinks. This issue was first discussed in Ask: 'https://ask.libreoffice.org/t/web-hyperlinks-not-preserved-after-export-to-pdf/96762?u=frandries' and determined there was not a matching report yet. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 157535] #10 envelope printing fails to print correctly on envelope
https://bugs.documentfoundation.org/show_bug.cgi?id=157535 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 157527] Libreoffice 7.4 file recovery does not work with files loaded from WebDAV (e.g. Nextcloud)
https://bugs.documentfoundation.org/show_bug.cgi?id=157527 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 154240] Relative Formula Calculations do not work correctly with Autofilters that reorder applied
https://bugs.documentfoundation.org/show_bug.cgi?id=154240 --- Comment #6 from QA Administrators --- Dear jgraham11, 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 157537] Character style "blinks" in-and-out of being applied as I type
https://bugs.documentfoundation.org/show_bug.cgi?id=157537 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 157410] Use SVG instead of bitmap when possible for HTML filters
https://bugs.documentfoundation.org/show_bug.cgi?id=157410 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 157744] find is hampered by settings in find/replace
https://bugs.documentfoundation.org/show_bug.cgi?id=157744 --- Comment #4 from QA Administrators --- [Automated Action] NeedInfo-To-Unconfirmed -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 104742] [META] Network-involved bugs
https://bugs.documentfoundation.org/show_bug.cgi?id=104742 Bug 104742 depends on bug 153318, which changed state. Bug 153318 Summary: Cannot save or open files on gvfs mounted smb share https://bugs.documentfoundation.org/show_bug.cgi?id=153318 What|Removed |Added Status|NEEDINFO|RESOLVED Resolution|--- |INSUFFICIENTDATA -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153318] Cannot save or open files on gvfs mounted smb share
https://bugs.documentfoundation.org/show_bug.cgi?id=153318 --- Comment #6 from QA Administrators --- Dear nico.winkelstraeter, 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 152966] pdf export to fillable pdf changes tab order through fields
https://bugs.documentfoundation.org/show_bug.cgi?id=152966 --- Comment #15 from QA Administrators --- Dear Mike Sapsard, 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 152715] I was hovering over a grouped set of objects, when a faulty tool tip appeared
https://bugs.documentfoundation.org/show_bug.cgi?id=152715 --- Comment #3 from QA Administrators --- Dear matthijs.volker.bo...@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 150092] FILESAVE XLSX Very slow saving time for spreadsheet with large number of columns
https://bugs.documentfoundation.org/show_bug.cgi?id=150092 --- Comment #17 from QA Administrators --- Dear Owen Savill, 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 152699] infinitely spread window on libre office calc when apply base filter - by clicking filtermenu
https://bugs.documentfoundation.org/show_bug.cgi?id=152699 --- Comment #4 from QA Administrators --- Dear Roman, 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 102998] [META] Mail merge bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=102998 Bug 102998 depends on bug 147481, which changed state. Bug 147481 Summary: Writer Mail Merge does not use CR/LF as paragraph separator https://bugs.documentfoundation.org/show_bug.cgi?id=147481 What|Removed |Added Status|NEEDINFO|RESOLVED Resolution|--- |INSUFFICIENTDATA -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 147481] Writer Mail Merge does not use CR/LF as paragraph separator
https://bugs.documentfoundation.org/show_bug.cgi?id=147481 --- Comment #7 from QA Administrators --- Dear titanemdg, 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 141535] VIEWING: base crashes when viewing a form
https://bugs.documentfoundation.org/show_bug.cgi?id=141535 --- Comment #9 from QA Administrators --- Dear userxyz, 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 117073] [META] WebDAV bugs
https://bugs.documentfoundation.org/show_bug.cgi?id=117073 Bug 117073 depends on bug 108009, which changed state. Bug 108009 Summary: Can't save new file to WebDAV server via Save Remote https://bugs.documentfoundation.org/show_bug.cgi?id=108009 What|Removed |Added Status|NEEDINFO|RESOLVED Resolution|--- |INSUFFICIENTDATA -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 108009] Can't save new file to WebDAV server via Save Remote
https://bugs.documentfoundation.org/show_bug.cgi?id=108009 QA Administrators changed: What|Removed |Added Resolution|--- |INSUFFICIENTDATA Status|NEEDINFO|RESOLVED -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 108009] Can't save new file to WebDAV server via Save Remote
https://bugs.documentfoundation.org/show_bug.cgi?id=108009 --- Comment #13 from QA Administrators --- Dear Vitaliy Lotorev, 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 154848] Using bigger images on slides may lead to a crash of Impress during presenting
https://bugs.documentfoundation.org/show_bug.cgi?id=154848 --- Comment #2 from QA Administrators --- Dear Joysn71, 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 154847] When cloning slide with animation and removing objects on cloned slide, navigation backwards breaks
https://bugs.documentfoundation.org/show_bug.cgi?id=154847 --- Comment #2 from QA Administrators --- Dear Joysn71, 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 154840] 7.5 not connecting to printer
https://bugs.documentfoundation.org/show_bug.cgi?id=154840 --- Comment #2 from QA Administrators --- Dear Nigel Wakefield, 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 154835] When I insert a chart in any document and click the "Properties" button in the right side of the screen, its content shows up but instantly disappears.
https://bugs.documentfoundation.org/show_bug.cgi?id=154835 --- Comment #2 from QA Administrators --- Dear Ronnel Portugal, 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 91739] nvda can not read documents from top to bottom.
https://bugs.documentfoundation.org/show_bug.cgi?id=91739 --- Comment #18 from QA Administrators --- Dear zahra, 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 53614] FILEOPEN: Document In Use Dialog appearing after cancelling Text Import dialog
https://bugs.documentfoundation.org/show_bug.cgi?id=53614 --- Comment #13 from QA Administrators --- Dear Erik, 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 144531] Undo of textbox keeps the textbox insert button activated
https://bugs.documentfoundation.org/show_bug.cgi?id=144531 --- Comment #6 from QA Administrators --- Dear Telesto, 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 143221] Menu/Toolbar entry to show hidden character
https://bugs.documentfoundation.org/show_bug.cgi?id=143221 --- Comment #10 from QA Administrators --- Dear S.Zosgornik, 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 135659] Images positioned wrongly after paste RFT undo regular paste
https://bugs.documentfoundation.org/show_bug.cgi?id=135659 --- Comment #7 from QA Administrators --- Dear Telesto, 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 135586] Accessibility Quotes are not announced when working with screenreaders
https://bugs.documentfoundation.org/show_bug.cgi?id=135586 --- Comment #6 from QA Administrators --- Dear Karl-Heinz Arkenau, 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 136022] Accessibility Status of Checkbox in Spelling options not announced when using Screenreader
https://bugs.documentfoundation.org/show_bug.cgi?id=136022 --- Comment #7 from QA Administrators --- Dear Karl-Heinz Arkenau, 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 135585] Accessibility To short announcements in options for auto correction when working with screenreader
https://bugs.documentfoundation.org/show_bug.cgi?id=135585 --- Comment #6 from QA Administrators --- Dear Karl-Heinz Arkenau, 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 135423] ACCESSIBILITY: No Screenreader Output in the "Autotext" create/edit dialog
https://bugs.documentfoundation.org/show_bug.cgi?id=135423 --- Comment #7 from QA Administrators --- Dear Karl-Heinz Arkenau, 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 135435] ACCESSIBILITY: No information from screenreader in "check for updates" window
https://bugs.documentfoundation.org/show_bug.cgi?id=135435 --- Comment #7 from QA Administrators --- Dear Karl-Heinz Arkenau, 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 124377] Make better bitmap export quality to PDF for Redaction
https://bugs.documentfoundation.org/show_bug.cgi?id=124377 --- Comment #18 from QA Administrators --- Dear Roman Kuznetsov, 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 117529] Can't paste chart from clipboard into Writer after closing LibO in between (works for Calc/Draw) (not Gtk3)
https://bugs.documentfoundation.org/show_bug.cgi?id=117529 --- Comment #7 from QA Administrators --- Dear Telesto, 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 114047] Keyboard shortcut Option + Left/Right Arrow Key Should Scroll to the Previous/Next Word not Reduce/Increase the Column Width
https://bugs.documentfoundation.org/show_bug.cgi?id=114047 --- Comment #15 from QA Administrators --- Dear gurol, 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 117840] Layer properties visible/printable/locked are wrong in watch window
https://bugs.documentfoundation.org/show_bug.cgi?id=117840 --- Comment #8 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 133095] UI: No restart in safe mode menu item for tabbed toolbar (and similar onces)
https://bugs.documentfoundation.org/show_bug.cgi?id=133095 --- Comment #2 from Justin L --- I doubt I have ever restarted LO in safe mode. Just because a command exists doesn't mean it needs to be in the notebookbar. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 139700] UI: no hoover over effect page size picker in tabbed mode
https://bugs.documentfoundation.org/show_bug.cgi?id=139700 Justin L changed: What|Removed |Added See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=13 ||7067 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 137067] User interface - Inconsistent fonts in tabbed style (Remote Documents looks out-of-place)
https://bugs.documentfoundation.org/show_bug.cgi?id=137067 Justin L changed: What|Removed |Added See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=13 ||9700 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 139700] UI: no hoover over effect page size picker in tabbed mode
https://bugs.documentfoundation.org/show_bug.cgi?id=139700 --- Comment #6 from Justin L --- The Page Size option is not a GTK widget, but a home-grown thing. So it acts differently to pretty much everything else. (A few other things like paragraph styles, fonts are also home-grown.) -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 107237] [META] Notebookbar Tabbed
https://bugs.documentfoundation.org/show_bug.cgi?id=107237 Bug 107237 depends on bug 139692, which changed state. Bug 139692 Summary: collapsible tabbed UI (Workaround: Tabbed Compact) https://bugs.documentfoundation.org/show_bug.cgi?id=139692 What|Removed |Added Status|NEW |RESOLVED Resolution|--- |DUPLICATE -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 130342] Auto-Hide Notebook bar content
https://bugs.documentfoundation.org/show_bug.cgi?id=130342 Justin L changed: What|Removed |Added CC||shariqk...@gmail.com --- Comment #4 from Justin L --- *** Bug 139692 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 139692] collapsible tabbed UI (Workaround: Tabbed Compact)
https://bugs.documentfoundation.org/show_bug.cgi?id=139692 Justin L changed: What|Removed |Added Status|NEW |RESOLVED Resolution|--- |DUPLICATE --- Comment #4 from Justin L --- *** This bug has been marked as a duplicate of bug 130342 *** -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 154917] Remove Random Number Generator from the context menu and add it to the Insert menu at the NBs
https://bugs.documentfoundation.org/show_bug.cgi?id=154917 Justin L changed: What|Removed |Added Status|NEW |ASSIGNED CC||jl...@mail.com Assignee|libreoffice-b...@lists.free |jl...@mail.com |desktop.org | --- Comment #10 from Justin L --- In the classic menu, this is under Sheet - Fill Cells. The other Fill Cells commands are also grouped in the notebookbar. Makes sense to me, so I won't remove it (since it does not harm here). https://gerrit.libreoffice.org/c/core/+/157986 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 101376] Wordcount Beanshell macro execution causes crash
https://bugs.documentfoundation.org/show_bug.cgi?id=101376 Patrick Luby changed: What|Removed |Added Status|NEW |ASSIGNED Assignee|libreoffice-b...@lists.free |plub...@neooffice.org |desktop.org | --- Comment #34 from Patrick Luby --- I went way down a rabbit hole today and got OpenJDK to build. With a few softlinks in /Library/Java/JavaVirtualMachines, LibreOffice could see it and, with a debug build of OpenJDK, the crash logs started to be more specific as to which function the crash was occurring in. So, after chasing some wild theories, I've got a patch that works for me: https://gerrit.libreoffice.org/c/core/+/157985 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 157783] FILESAVE PPTX: graphic elements change color on save/reload cycle
https://bugs.documentfoundation.org/show_bug.cgi?id=157783 --- Comment #2 from Gerald Pfeifer --- Created attachment 190224 --> https://bugs.documentfoundation.org/attachment.cgi?id=190224=edit Visual comparison: Left as it should be, right as it is after save/open -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 157783] FILESAVE PPTX: graphic elements change color on save/reload cycle
https://bugs.documentfoundation.org/show_bug.cgi?id=157783 --- Comment #1 from Gerald Pfeifer --- Created attachment 190223 --> https://bugs.documentfoundation.org/attachment.cgi?id=190223=edit Second deck to reproduce issue (PPTX format) -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 157783] New: FILESAVE PPTX: graphic elements change color on save/reload cycle
https://bugs.documentfoundation.org/show_bug.cgi?id=157783 Bug ID: 157783 Summary: FILESAVE PPTX: graphic elements change color on save/reload cycle Product: LibreOffice Version: 7.6.2.1 release Hardware: All OS: All Status: UNCONFIRMED Keywords: bibisectRequest, regression Severity: normal Priority: medium Component: Impress Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: ger...@pfeifer.com Created attachment 190222 --> https://bugs.documentfoundation.org/attachment.cgi?id=190222=edit First deck to reproduce issue (PPTX format) How to reproduce: 1. Open slide1.pptx and slide2.pptx as attached to this report. 2. Copy slides from the latter and... 3. ...paste them into the former. 4. Save combined deck with three slides as PPTX. 5. Open just saved deck. Expected: Deck looks the same before and after save/reopen cycle. Actual: Colors of various graphical elements changed quite a bit. Not seen in: Version: 7.3.8.0.0+ / LibreOffice Community Build ID: 0f7fb0a2decec3f8869098ae5e47ee6055545486 CPU threads: 8; OS: Linux 6.5; UI render: default; VCL: gtk3 Locale: en-US (en_US.UTF-8); UI: en-US Version: 7.5.6.0.0+ (X86_64) / LibreOffice Community Build ID: 0a5c49aa4f65c8e661f7da3934ab9bea8cacf662 CPU threads: 8; OS: Linux 6.5; UI render: default; VCL: gtk3 Locale: en-US (en_US.UTF-8); UI: en-US Seen in: Version: 7.6.3.0.0+ (X86_64) / LibreOffice Community Build ID: 9c8a1994bea590db7436638580231daf31844fd6 CPU threads: 8; OS: Linux 6.5; UI render: default; VCL: gtk3 Locale: en-US (en_US.UTF-8); UI: en-US Version: 24.2.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: e9374f74385d7dfe77d1902d3d82af20143bc775 CPU threads: 8; OS: Linux 6.5; UI render: default; VCL: gtk3 Locale: en-US (en_US.UTF-8); UI: en-US -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 150466] Hide Print File Directly by default in the tabbed and tabbed compact user interfaces
https://bugs.documentfoundation.org/show_bug.cgi?id=150466 Justin L changed: What|Removed |Added CC||jl...@mail.com Status|NEW |RESOLVED Resolution|--- |FIXED Assignee|libreoffice-b...@lists.free |jl...@mail.com |desktop.org | -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 107237] [META] Notebookbar Tabbed
https://bugs.documentfoundation.org/show_bug.cgi?id=107237 Bug 107237 depends on bug 150466, which changed state. Bug 150466 Summary: Hide Print File Directly by default in the tabbed and tabbed compact user interfaces https://bugs.documentfoundation.org/show_bug.cgi?id=150466 What|Removed |Added Status|NEW |RESOLVED Resolution|--- |FIXED -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 150466] Hide Print File Directly by default in the tabbed and tabbed compact user interfaces
https://bugs.documentfoundation.org/show_bug.cgi?id=150466 Commit Notification changed: What|Removed |Added Whiteboard||target:24.2.0 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-commits] core.git: sc/uiconfig sd/uiconfig sw/uiconfig
sc/uiconfig/scalc/ui/notebookbar.ui |9 ++- sc/uiconfig/scalc/ui/notebookbar_compact.ui | 12 ++-- sc/uiconfig/scalc/ui/notebookbar_groupedbar_compact.ui|9 ++- sc/uiconfig/scalc/ui/notebookbar_groupedbar_full.ui |9 ++- sd/uiconfig/sdraw/ui/notebookbar.ui |9 ++- sd/uiconfig/sdraw/ui/notebookbar_compact.ui | 39 -- sd/uiconfig/sdraw/ui/notebookbar_groupedbar_compact.ui|9 ++- sd/uiconfig/simpress/ui/notebookbar.ui|9 ++- sd/uiconfig/simpress/ui/notebookbar_compact.ui| 15 +++-- sd/uiconfig/simpress/ui/notebookbar_groupedbar_compact.ui |9 ++- sd/uiconfig/simpress/ui/notebookbar_groupedbar_full.ui|9 ++- sw/uiconfig/swriter/ui/notebookbar.ui |7 ++ sw/uiconfig/swriter/ui/notebookbar_compact.ui | 13 ++-- sw/uiconfig/swriter/ui/notebookbar_groupedbar_compact.ui |9 ++- sw/uiconfig/swriter/ui/notebookbar_groupedbar_full.ui |9 ++- 15 files changed, 145 insertions(+), 31 deletions(-) New commits: commit 489da34e9bffb234fa27155cef1931bd6f21dc1d Author: Justin Luth AuthorDate: Sat Oct 14 16:49:56 2023 -0400 Commit: Justin Luth CommitDate: Sun Oct 15 02:48:40 2023 +0200 tdf#150466 notebookbar: hide PrintDefault on compact and standardize As in the classic toolbars, do not promote direct printing since it easily leads to mistakes and wasted paper. Additionally, the printer settings is really never needed, so it should not have a prominent place, especially on COMPACT. At the same time, I standardized the File menu: - always include print (especially useful for accessibility) - always use the same order - consistently provide access to print/web preview Change-Id: I9ffbba179206274b5ed1788e496b7c5aa0503726 Reviewed-on: https://gerrit.libreoffice.org/c/core/+/157984 Tested-by: Jenkins Reviewed-by: Justin Luth diff --git a/sc/uiconfig/scalc/ui/notebookbar.ui b/sc/uiconfig/scalc/ui/notebookbar.ui index 54419a9c4385..714ad44e6e39 100644 --- a/sc/uiconfig/scalc/ui/notebookbar.ui +++ b/sc/uiconfig/scalc/ui/notebookbar.ui @@ -505,9 +505,16 @@ - + True False +.uno:Print + + + + +False +False .uno:PrintDefault diff --git a/sc/uiconfig/scalc/ui/notebookbar_compact.ui b/sc/uiconfig/scalc/ui/notebookbar_compact.ui index 810d8e00ee05..7c64e36a4d3b 100644 --- a/sc/uiconfig/scalc/ui/notebookbar_compact.ui +++ b/sc/uiconfig/scalc/ui/notebookbar_compact.ui @@ -745,17 +745,17 @@ - + True False -.uno:PrintDefault +.uno:Print - + False False -.uno:Print +.uno:PrintDefault @@ -2865,7 +2865,7 @@ both-horiz -True +False .uno:PrintDefault @@ -2904,7 +2904,7 @@ False -True +False False .uno:PrinterSetup sfx2/res/symphony/open_more.png diff --git a/sc/uiconfig/scalc/ui/notebookbar_groupedbar_compact.ui b/sc/uiconfig/scalc/ui/notebookbar_groupedbar_compact.ui index 8547ef8f3aec..364ac8323397 100644 --- a/sc/uiconfig/scalc/ui/notebookbar_groupedbar_compact.ui +++ b/sc/uiconfig/scalc/ui/notebookbar_groupedbar_compact.ui @@ -730,9 +730,16 @@ - + True False +.uno:Print + + + + +False +False .uno:PrintDefault diff --git a/sc/uiconfig/scalc/ui/notebookbar_groupedbar_full.ui b/sc/uiconfig/scalc/ui/notebookbar_groupedbar_full.ui index e12befff2f1d..c6053993b96f 100644 --- a/sc/uiconfig/scalc/ui/notebookbar_groupedbar_full.ui +++ b/sc/uiconfig/scalc/ui/notebookbar_groupedbar_full.ui @@ -1308,9 +1308,16 @@ - + True False +.uno:Print + + + + +False +False .uno:PrintDefault diff --git a/sd/uiconfig/sdraw/ui/notebookbar.ui b/sd/uiconfig/sdraw/ui/notebookbar.ui index 4f91cd52e122..eb3f977a15a5 100644 --- a/sd/uiconfig/sdraw/ui/notebookbar.ui +++ b/sd/uiconfig/sdraw/ui/notebookbar.ui @@ -561,9 +561,16 @@ - + True False +.uno:Print + + + + +False +False
[Libreoffice-bugs] [Bug 119745] Scrolling with a laptop touchpad in Libreoffice way too fast
https://bugs.documentfoundation.org/show_bug.cgi?id=119745 --- Comment #65 from yrtin...@duck.com --- I have been experiencing this bug (or design flaw) for a while now, but I have not bothered to create a bugzilla account and report my experience until now. I am merely a casual libreoffice user, if there is such a thing, and therefore I likely know the least among everyone here as to how libreoffice or even software/programming in general works. I mainly just use Writer. In my case, I operate an LG Gram laptop with Windows 10, Version 10.0.19045, Build 19045. My current libreoffice installation is version 7.5.5.2, but as I have said before I have had this issue for a while now and indeed experienced it in recent, past versions. If I can provide anymore information that would be useful, please let me know. As others have reported, when I scroll through a libreoffice document with a trackpad (in my case in Writer) I jump several lines away from the line that I wanted to read, edit, or write. The scrolling is highly sensitive. I have grown so accustomed to such sensitivity that I sometimes glide through dozens of pages in the larger documents I have written just for the fun of it (even though I could just use Navigator to jump to the section I need to see). At my gentlest touch, I can sometimes scroll to the subsequent line I want to read. It takes much effort and precision, though, and I more often than not skip over that next line I need to read. Yet, with any other application or software, in Microsoft Word (before I switched to Libreoffice) I can scroll just fine. I can smoothly scroll back and forth with ease. The contrast between scrolling in Libreoffice versus any other application is almost astoundingly bad, until one gets used to it. I hope that some talented developer/programmer, or someone in the main team of The Document Foundation, takes a look at this issue and assigns a fix to a future update. I do appreciate that Libreoffice is a community driven project, but I personally do not know anyone with the skill and permission to develop such a patch. I do not know who to contact, or if it is even possible to contribute to some kind of fund that would entice a willing developer. This bug is not of dire importance; it does not risk breaking the software. Yet, it does an incredible job of destroying Libreoffice's ease of use. And for someone like me, a person that sits on their butt all day writing on a latptop, such an issue is significant. (I write some of this in jest.) -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 140401] LibreOffice crashed due to custom installed fonts
https://bugs.documentfoundation.org/show_bug.cgi?id=140401 --- Comment #21 from Vivodo Lio --- The "Ex" file names are from here: https://github.com/cjkvi/HanaMinAFDKO/releases/tag/8.030 Just need to show all 28 font files. I found a solution to fix this issue: just delete "HanaMin.sfont" and "HanaMinEx.sfont", then active all my HanaMin fonts and everything is OK. I don't know why this can fix the issue. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 157781] Adding datatable to Column and line graph does not display properly
https://bugs.documentfoundation.org/show_bug.cgi?id=157781 m.a.riosv changed: What|Removed |Added CC||miguelangelrv@libreoffice.o ||rg Ever confirmed|0 |1 Status|UNCONFIRMED |NEW --- Comment #1 from m.a.riosv --- Confirmed Version: 24.2.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: 9eb419b0b0f019f5fbc48ff1a11977e8b041edee CPU threads: 16; OS: Windows 10.0 Build 22621; UI render: Skia/Raster; VCL: win Locale: es-ES (es_ES); UI: en-US Calc: CL threaded Jumbo -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 157775] Writer: lost calculations when a table is copied from one file to another
https://bugs.documentfoundation.org/show_bug.cgi?id=157775 Stéphane Guillou (stragu) changed: What|Removed |Added See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=15 ||7287 Status|UNCONFIRMED |NEEDINFO Ever confirmed|0 |1 Summary|fichier texte : Copier un |Writer: lost calculations |tableau d'un fichier sur un |when a table is copied from |autre fichier, calculs |one file to another |perdus | CC||stephane.guillou@libreoffic ||e.org --- Comment #2 from Stéphane Guillou (stragu) --- We would need more details to understand the exact issue, but this sounds like the regression in bug 157287. Can you please: - share the full version information from Help > About LibreOffice - attach an example file for us to test the copy-paste - reply in English Thank you! -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 157287] Cross-reference a formula does not work since 7.6x
https://bugs.documentfoundation.org/show_bug.cgi?id=157287 Stéphane Guillou (stragu) changed: What|Removed |Added See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=15 ||7775 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 139007] [META] PDF accessibility
https://bugs.documentfoundation.org/show_bug.cgi?id=139007 Stéphane Guillou (stragu) changed: What|Removed |Added Depends on||157517 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=157517 [Bug 157517] possible regression in PDF/UA export: PDF/UA identifier missing when PDF/A also used -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 157517] possible regression in PDF/UA export: PDF/UA identifier missing when PDF/A also used
https://bugs.documentfoundation.org/show_bug.cgi?id=157517 Stéphane Guillou (stragu) changed: What|Removed |Added Blocks||139007 Keywords||accessibility, bibisected, ||bisected See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=15 ||3472 Regression By||Michael Stahl CC||michael.st...@allotropia.de Summary|possible regression in |possible regression in |PDF/UA export: PDF/UA |PDF/UA export: PDF/UA |identifier missing |identifier missing when ||PDF/A also used Status|UNCONFIRMED |NEW Ever confirmed|0 |1 Version|7.6.2.1 release |7.6.0.2 rc OS|Windows (All) |All --- Comment #9 from Stéphane Guillou (stragu) --- Yes, I can now reproduce if I also use PDF-A/3b and PDF/UA. Bibisected with linux-64-7.6 repo to first bad commit 3543a32a8872c7b77b978aa7c20f8f9a49af9061 which points to core commit c4b12d06698402984b3ffdbd2c139f261fa35ca1 which is a cherrypick of: commit 41717420af68994c2fde522ea86db6e5ed643034 author Michael Stahl Fri Jul 07 16:43:45 2023 +0200 committer Michael Stahl Fri Jul 07 18:32:30 2023 +0200 tdf#153472 vcl: PDF/A export: produce valid XMP metadata Reviewed-on: https://gerrit.libreoffice.org/c/core/+/154169 Michael, I assume this change was unintended. Can you please have a look? Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=139007 [Bug 139007] [META] PDF accessibility -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 157780] Calc: Web hyperlinks not preserved after export to PDF
https://bugs.documentfoundation.org/show_bug.cgi?id=157780 m.a.riosv changed: What|Removed |Added CC||miguelangelrv@libreoffice.o ||rg Status|NEW |NEEDINFO --- Comment #2 from m.a.riosv --- The issue is when in the options to export as PDF, on the first tab Export whole sheet is enabled. There is another bug about 'Whole sheet export' tdf#155351, maybe the same root. Please don't put as new your own report, someone else must do it after confirm. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 144488] HYPERLINKS: Hyperlink to target in external document doesn't work in exported PDF (steps in comment 4)
https://bugs.documentfoundation.org/show_bug.cgi?id=144488 Stéphane Guillou (stragu) changed: What|Removed |Added Status|NEW |NEEDINFO --- Comment #12 from Stéphane Guillou (stragu) --- (In reply to harald.braun.p from comment #11) > Evince: link does not work. > Foxit reader: link works. [...] > Foxit Reader: Link does not work. > muPDF: Link works. OK, so at least we can confirm that PDF links not working (as in comment 4) is not our issue but rather missing support in some PDF readers. (In reply to harald.braun.p from comment #11) > Note: But this is not my problem. See bug description. Let's have a look at this ODM to ODT issue then. I know you shared them with Dieter, but can you please attach your sample documents here so others can test? https://bugs.documentfoundation.org/attachment.cgi?bugid=144488=enter -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 157503] Remapping mouse buttons not working
https://bugs.documentfoundation.org/show_bug.cgi?id=157503 Stéphane Guillou (stragu) changed: What|Removed |Added Whiteboard||needsLogitechMouse -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 157503] Remapping mouse buttons not working
https://bugs.documentfoundation.org/show_bug.cgi?id=157503 Stéphane Guillou (stragu) changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |NOTOURBUG --- Comment #4 from Stéphane Guillou (stragu) --- >From what I understand, the software does not support LibreOffice: https://support.logi.com/hc/en-us/articles/360050312134-Logitech-Options-supported-applications Someone else mentioned it's a shame Logi Options+ does not support mapping to LibreOffice commands: https://www.computerweekly.com/blog/Inspect-a-Gadget/Logitech-MX-Master-3S-for-business-MX-Keys-combo So closing as "not our bug" as it should be implemented on Logi Options+'s side. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-commits] core.git: accessibility/inc accessibility/source
accessibility/inc/extended/accessibletabbarpagelist.hxx|4 +---
accessibility/source/extended/accessibletabbarpagelist.cxx |1 -
2 files changed, 1 insertion(+), 4 deletions(-)
New commits:
commit 2a3023bc91d6f16133b5c869a1159342f9223228
Author: Michael Weghorn
AuthorDate: Sat Oct 14 20:49:53 2023 +0200
Commit: Michael Weghorn
CommitDate: Sun Oct 15 00:10:37 2023 +0200
a11y: Add include to fix clang-cl build
Without this, my clang-cl build on windows would fail
like this:
In file included from
C:/tools/cygwin/home/user/development/git/libreoffice/accessibility/source/extended/accessibletabbarbase.cxx:20:
In file included from
C:/tools/cygwin/home/user/development/git/libreoffice/accessibility/inc\extended/accessibletabbarbase.hxx:24:
In file included from
C:/tools/cygwin/home/user/development/git/libreoffice/include\vcl/vclptr.hxx:25:
C:/tools/cygwin/home/user/development/git/libreoffice/include\rtl/ref.hxx(129,20):
error: member access into incomplete type 'accessibility::AccessibleTabBarPage'
129 | m_pBody->release();
|^
C:/PROGRA~1/MICROS~2/2022/COMMUN~1/VC/Tools/MSVC/1437~1.328/Include\xmemory(321,21):
note: in instantiation of member function
'rtl::Reference::~Reference' requested here
321 | _Location->~_Ty();
| ^
C:/tools/cygwin/home/user/development/git/libreoffice/accessibility/inc\extended/accessibletabbarpagelist.hxx(32,11):
note: forward declaration of 'accessibility::AccessibleTabBarPage'
32 | class AccessibleTabBarPage;
| ^
1 error generated.
make[1]: ***
[C:/tools/cygwin/home/user/development/git/libreoffice/solenv/gbuild/LinkTarget.mk:340:
C:/tools/cygwin/home/user/development/git/libreoffice/workdir/CxxObject/accessibility/source/extended/accessibletabbarbase.o]
Error 1
make: *** [Makefile:121: accessibility] Error 2
Change-Id: I3961fb95602b96667f33ea0b087e1df5375faf19
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/157982
Tested-by: Jenkins
Reviewed-by: Michael Weghorn
diff --git a/accessibility/inc/extended/accessibletabbarpagelist.hxx
b/accessibility/inc/extended/accessibletabbarpagelist.hxx
index d3f3d56f317d..b3045aa77c6f 100644
--- a/accessibility/inc/extended/accessibletabbarpagelist.hxx
+++ b/accessibility/inc/extended/accessibletabbarpagelist.hxx
@@ -24,14 +24,12 @@
#include
#include
#include
+#include
#include
namespace accessibility
{
-class AccessibleTabBarPage;
-
-
class AccessibleTabBarPageList final : public cppu::ImplInheritanceHelper<
AccessibleTabBarBase,
css::accessibility::XAccessible,
diff --git a/accessibility/source/extended/accessibletabbarpagelist.cxx
b/accessibility/source/extended/accessibletabbarpagelist.cxx
index 5faaed6846e2..8ad6b168ebaf 100644
--- a/accessibility/source/extended/accessibletabbarpagelist.cxx
+++ b/accessibility/source/extended/accessibletabbarpagelist.cxx
@@ -19,7 +19,6 @@
#include
#include
-#include
#include
#include
#include
[Libreoffice-bugs] [Bug 157782] New: FOOTNOTE FORMATTING. MAXIMUM FOOTNOTE AREA LIMIT MALFUNCTION -Ref Bug 73977
https://bugs.documentfoundation.org/show_bug.cgi?id=157782 Bug ID: 157782 Summary: FOOTNOTE FORMATTING. MAXIMUM FOOTNOTE AREA LIMIT MALFUNCTION -Ref Bug 73977 Product: LibreOffice Version: 7.4.5.1 release Hardware: x86-64 (AMD64) OS: other Status: UNCONFIRMED Severity: normal Priority: medium Component: Writer Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: h...@rdmorenolaw.com Created attachment 190221 --> https://bugs.documentfoundation.org/attachment.cgi?id=190221=edit Sample tExt exhibiting formatting issue AMERICAN ENGLISH FOOTNOTE FORMATTING. MAXIMUM FOOTNOTE AREA MALFUNCTION Ref Bug # 73977 Linux Mageia Version 7 Version: 7.4.5.1 Build ID: 40(Build:1) CPU threads: 4; OS: Linux 5.15; UI render: default; VCL: gtk3 Locale: en-US (en_US.UTF-8); UI: en-US Calc: threaded Legal Treatise created with LO Writer 7.4.5.1 in .odt format with uniform default page and footnote definitions. Page size is user defined as 6" x 9". A section may have a page or few pages of body text with 20-50 or more substantive footnotes. In the pages without body text LO Writer puts 2-3" of blank body text area. Adjusting Page Style->Default Page Style->Footnote->Maximum Footnote Height does not reduce the blank body text area. The result is much wasted space increasing cost of printing. Question: Is there another means to adjust Maximum Footnote Height ? RDM -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 73977] Other: Increase available footnote area to support traditional Arabic, Urdu, and Persian typesetting
https://bugs.documentfoundation.org/show_bug.cgi?id=73977 Richard Moreno changed: What|Removed |Added CC||h...@rdmorenolaw.com --- Comment #12 from Richard Moreno --- Created attachment 190220 --> https://bugs.documentfoundation.org/attachment.cgi?id=190220=edit One Section of Book Linux Mageia Version 7 Version: 7.4.5.1 Build ID: 40(Build:1) CPU threads: 4; OS: Linux 5.15; UI render: default; VCL: gtk3 Locale: en-US (en_US.UTF-8); UI: en-US Calc: threaded American English Legal Treatise created with LO Writer 7.4.5.1 in .odt format with uniform default page and footnote definitions. Page size is user defined as 6" x 9". A section may have a page or few pages of body text with 20-50 or more substantive footnotes. In the pages without body text LO Writer puts 2-3" of blank body text area. Adjusting Page Style->Default Page Style->Footnote->Maximum Footnote Height does not reduce the blank body text area. The result is much wasted space increasing cost of printing. Question: Is there another means to adjust Maximum Footnote Height ? RDM -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 142443] Libre Office Writer breaks the text adding unwanted tags in the content.xml file
https://bugs.documentfoundation.org/show_bug.cgi?id=142443 Dieter changed: What|Removed |Added See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=14 ||6458 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 146458] Opening typographic quotation mark always gets separate tag when inside text box/shape
https://bugs.documentfoundation.org/show_bug.cgi?id=146458 Dieter changed: What|Removed |Added See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=14 ||2443 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 157781] New: Adding datatable to Column and line graph does not display properly
https://bugs.documentfoundation.org/show_bug.cgi?id=157781 Bug ID: 157781 Summary: Adding datatable to Column and line graph does not display properly Product: LibreOffice Version: 7.5.7.1 release Hardware: All OS: All Status: UNCONFIRMED Severity: normal Priority: medium Component: Chart Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: librebug.youn...@jbymail.org Created attachment 190219 --> https://bugs.documentfoundation.org/attachment.cgi?id=190219=edit Spreadsheet with sample graphs showing datatable issue I am having an issue in making a chart from some data in LibreCalc that is using the chart type of "Columns and Lines" if I try to add a datatable to the graph. If just using a column graph or a line graph, the datatable is presented correctly. If using the columns and lines (with 1 line), then the graph appears to be doubling the X axis and it messes up the display. I have created a stripped down spreadsheet that has the base data for the table and several graphs. The third and fourth charts are displaying improperly. There are descriptions in the spreadsheet on each of the graphs and what they depict. Thanks for your assistance with this bug. Please let me know if I can be of assistance in reproducing the issue. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 157780] Calc: Web hyperlinks not preserved after export to PDF
https://bugs.documentfoundation.org/show_bug.cgi?id=157780 FranDries changed: What|Removed |Added Status|UNCONFIRMED |NEW Ever confirmed|0 |1 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 157780] Calc: Web hyperlinks not preserved after export to PDF
https://bugs.documentfoundation.org/show_bug.cgi?id=157780 --- Comment #1 from FranDries --- Created attachment 190218 --> https://bugs.documentfoundation.org/attachment.cgi?id=190218=edit Exported PDF file with invalid web hyperlink -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 157780] New: Calc: Web hyperlinks not preserved after export to PDF
https://bugs.documentfoundation.org/show_bug.cgi?id=157780 Bug ID: 157780 Summary: Calc: Web hyperlinks not preserved after export to PDF Product: LibreOffice Version: 7.6.2.1 release Hardware: All OS: Windows (All) Status: UNCONFIRMED Severity: normal Priority: medium Component: Calc Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: frandr...@edpnet.be Created attachment 190217 --> https://bugs.documentfoundation.org/attachment.cgi?id=190217=edit Sample Calc file with web hyperlink. In Calc I have a web hyperlink with URL 'www.uba.be' ; after Export as PDF ... the hyperlink changes to something like ‘file:///C:/…’. This happens only when PDF Option 'Whole sheet export' is selected. Wehen this option is not selected, then the hyperlinks are OK in the PDF file. Detected release: Win 11 LO Calc 7.6.2.1, but the problem was already there in version 6.4 wher 'Whole Sheet Export' was introduced. See sample Calc file 'Whole_sheet_export.ods' and exported PDF 'Whole_sheet_export.pdf'. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-commits] core.git: cui/source framework/source include/vcl offapi/com officecfg/registry vcl/osx vcl/qt5 vcl/unx vcl/win
cui/source/customize/acccfg.cxx|8
framework/source/accelerators/keymapping.cxx |1 +
include/vcl/keycodes.hxx |1 +
offapi/com/sun/star/awt/Key.idl|3 +++
officecfg/registry/data/org/openoffice/Office/Accelerators.xcu |6 ++
vcl/osx/salframe.cxx |1 +
vcl/osx/salmenu.cxx|3 +++
vcl/qt5/QtFrame.cxx|3 +++
vcl/qt5/QtWidget.cxx |3 +++
vcl/unx/generic/app/saldisp.cxx|7 +++
vcl/unx/gtk3/gtkframe.cxx |2 ++
vcl/win/app/salinst.cxx|1 +
vcl/win/window/salframe.cxx|3 +++
13 files changed, 42 insertions(+)
New commits:
commit ca74511985981444dbd72ade7244484c131e36a7
Author: Gökay Şatır
AuthorDate: Wed Oct 4 15:01:38 2023 +0300
Commit: Caolán McNamara
CommitDate: Sat Oct 14 21:51:43 2023 +0200
Add NUMBERSIGN key handler.
German keyboard layout has number sign key.
Users can print number sign without using modification keys.
So this key can be assigned a shortcut.
Subscript is assigned to CTRL + NUMBERSIGN.
Below PR is used as reference when adding the new key handler:
https://gerrit.libreoffice.org/c/core/+/86713
Signed-off-by: Gökay Şatır
Change-Id: I340dc47764e9200d2477f8db740a629f62f48004
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/157554
Tested-by: Jenkins CollaboraOffice
(cherry picked from commit 1db8f6d484b884301a7d3673f4d05478e28cd853)
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/157959
Tested-by: Jenkins
Reviewed-by: Caolán McNamara
diff --git a/cui/source/customize/acccfg.cxx b/cui/source/customize/acccfg.cxx
index f28eee88afa4..54b7eb73c81a 100644
--- a/cui/source/customize/acccfg.cxx
+++ b/cui/source/customize/acccfg.cxx
@@ -186,6 +186,7 @@ const sal_uInt16 KEYCODE_ARRAY[] = { KEY_F1,
KEY_MOD1 | KEY_X,
KEY_MOD1 | KEY_Y,
KEY_MOD1 | KEY_Z,
+ KEY_MOD1 | KEY_NUMBERSIGN,
KEY_MOD1 | KEY_COLON,
KEY_MOD1 | KEY_SEMICOLON,
KEY_MOD1 | KEY_QUOTELEFT,
@@ -271,6 +272,7 @@ const sal_uInt16 KEYCODE_ARRAY[] = { KEY_F1,
KEY_SHIFT | KEY_MOD1 | KEY_X,
KEY_SHIFT | KEY_MOD1 | KEY_Y,
KEY_SHIFT | KEY_MOD1 | KEY_Z,
+ KEY_SHIFT | KEY_MOD1 | KEY_NUMBERSIGN,
KEY_SHIFT | KEY_MOD1 | KEY_COLON,
KEY_SHIFT | KEY_MOD1 | KEY_SEMICOLON,
KEY_SHIFT | KEY_MOD1 | KEY_QUOTELEFT,
@@ -352,6 +354,7 @@ const sal_uInt16 KEYCODE_ARRAY[] = { KEY_F1,
KEY_MOD2 | KEY_X,
KEY_MOD2 | KEY_Y,
KEY_MOD2 | KEY_Z,
+ KEY_MOD2 | KEY_NUMBERSIGN,
KEY_MOD2 | KEY_COLON,
KEY_MOD2 | KEY_SEMICOLON,
KEY_MOD2 | KEY_QUOTELEFT,
@@ -431,6 +434,7 @@ const sal_uInt16 KEYCODE_ARRAY[] = { KEY_F1,
KEY_SHIFT | KEY_MOD2 | KEY_X,
KEY_SHIFT | KEY_MOD2 | KEY_Y,
KEY_SHIFT | KEY_MOD2 | KEY_Z,
+ KEY_SHIFT | KEY_MOD2 | KEY_NUMBERSIGN,
KEY_SHIFT | KEY_MOD2 | KEY_COLON,
KEY_SHIFT | KEY_MOD2 | KEY_SEMICOLON,
KEY_SHIFT | KEY_MOD2 | KEY_QUOTELEFT,
@@ -511,6 +515,7 @@ const sal_uInt16 KEYCODE_ARRAY[] = { KEY_F1,
KEY_MOD1 | KEY_MOD2 | KEY_X,
KEY_MOD1 | KEY_MOD2 | KEY_Y,
KEY_MOD1 | KEY_MOD2 | KEY_Z,
+ KEY_MOD1 | KEY_MOD2 | KEY_NUMBERSIGN,
KEY_MOD1 | KEY_MOD2 | KEY_COLON,
KEY_MOD1 | KEY_MOD2 | KEY_SEMICOLON,
KEY_MOD1 | KEY_MOD2 | KEY_QUOTELEFT,
@@ -590,6 +595,7 @@ const sal_uInt16 KEYCODE_ARRAY[] = { KEY_F1,
KEY_SHIFT | KEY_MOD1 | KEY_MOD2 | KEY_X,
[Libreoffice-commits] core.git: 2 commits - compilerplugins/clang sw/source vcl/inc
compilerplugins/clang/unnecessaryvirtual.results |2 -- sw/source/uibase/utlui/navipi.cxx|6 ++ vcl/inc/salvtables.hxx |2 +- 3 files changed, 7 insertions(+), 3 deletions(-) New commits: commit 025372363e5310ffe0e729648f97faef2fe784eb Author: Caolán McNamara AuthorDate: Sat Oct 14 19:01:48 2023 +0100 Commit: Caolán McNamara CommitDate: Sat Oct 14 21:51:32 2023 +0200 get_iter_abs_pos doesn't neeed to be virtual Change-Id: If69768ffac37aa7b39a806b3c67ad8cbdafc5d2f Reviewed-on: https://gerrit.libreoffice.org/c/core/+/157981 Tested-by: Jenkins Reviewed-by: Caolán McNamara diff --git a/compilerplugins/clang/unnecessaryvirtual.results b/compilerplugins/clang/unnecessaryvirtual.results index 7404a1cffd85..96c0ef52a9b5 100644 --- a/compilerplugins/clang/unnecessaryvirtual.results +++ b/compilerplugins/clang/unnecessaryvirtual.results @@ -448,8 +448,6 @@ vcl/inc/salobj.hxx:49 void SalObject::Enable(_Bool,) vcl/inc/salprn.hxx:116 enum SalPrinterError SalPrinter::GetErrorCode() -vcl/inc/salvtables.hxx:1771 -_Bool SalInstanceTreeView::get_iter_abs_pos(class weld::TreeIter &,int,)const vcl/inc/skia/gdiimpl.hxx:230 void SkiaSalGraphicsImpl::createSurface() vcl/inc/skia/gdiimpl.hxx:240 diff --git a/vcl/inc/salvtables.hxx b/vcl/inc/salvtables.hxx index 09186972a3ab..8648db8e5143 100644 --- a/vcl/inc/salvtables.hxx +++ b/vcl/inc/salvtables.hxx @@ -1770,7 +1770,7 @@ public: virtual bool get_iter_first(weld::TreeIter& rIter) const override; -virtual bool get_iter_abs_pos(weld::TreeIter& rIter, int nPos) const; +bool get_iter_abs_pos(weld::TreeIter& rIter, int nPos) const; virtual bool iter_next_sibling(weld::TreeIter& rIter) const override; commit 5bdcd30a64ef814e63d1548ab798cc8a81944b49 Author: Attila Szűcs AuthorDate: Thu May 18 10:36:38 2023 +0200 Commit: Caolán McNamara CommitDate: Sat Oct 14 21:51:22 2023 +0200 LOK: Navigator: headings expanded by default Called an expand_row for the first element of the contetnTree in the navigator constructor. Right now contructor is called every time when navigator is opened, it may change later. (desktop app do it only if navigator opens in a new window, not on sidebar) Change-Id: Ibe4b71e6a6ddb573269178f83c295b0c2cbd53b0 Reviewed-on: https://gerrit.libreoffice.org/c/core/+/151939 Tested-by: Jenkins CollaboraOffice Reviewed-by: Szymon Kłos (cherry picked from commit 09c40d669cac5f167fa68cb5c6ad94a6a9e2a844) Reviewed-on: https://gerrit.libreoffice.org/c/core/+/157960 Tested-by: Jenkins Tested-by: Caolán McNamara Reviewed-by: Caolán McNamara diff --git a/sw/source/uibase/utlui/navipi.cxx b/sw/source/uibase/utlui/navipi.cxx index ad89c6b1a7bb..67807c69f8bc 100644 --- a/sw/source/uibase/utlui/navipi.cxx +++ b/sw/source/uibase/utlui/navipi.cxx @@ -734,6 +734,12 @@ SwNavigationPI::SwNavigationPI(weld::Widget* pParent, m_xGlobalBox->hide(); m_xGlobalToolBox->hide(); m_xGlobalTree->HideTree(); + +//Open Headings by default +auto& pTreeView = m_xContentTree->get_widget(); +std::unique_ptr itEntry(pTreeView.make_iterator()); +pTreeView.get_iter_first(*itEntry); +pTreeView.expand_row(*itEntry); } }
[Libreoffice-bugs] [Bug 157776] "Save changes to document" appears even after just opening and closing and no edits
https://bugs.documentfoundation.org/show_bug.cgi?id=157776 m.a.riosv changed: What|Removed |Added Status|UNCONFIRMED |NEW CC||miguelangelrv@libreoffice.o ||rg Ever confirmed|0 |1 --- Comment #1 from m.a.riosv --- Maybe something in the file, it doesn't happen to me with other files, with one or several slides. It happens also, opening and saving with PowerPoint. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 157774] Crash after installing the last version (7.6.2.1)
https://bugs.documentfoundation.org/show_bug.cgi?id=157774 m.a.riosv changed: What|Removed |Added Ever confirmed|0 |1 Status|UNCONFIRMED |NEEDINFO CC||miguelangelrv@libreoffice.o ||rg --- Comment #2 from m.a.riosv --- Can you test in another folder. Verify you have write access in it. Please paste here the information on Menu/Help/About LibreOffice (There is an icon to copy) Please test in safe mode, Menu/Help/Restart in Safe Mode -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 157741] Show Comment: The show comment option displays the comment away from the source cell
https://bugs.documentfoundation.org/show_bug.cgi?id=157741 m.a.riosv changed: What|Removed |Added Ever confirmed|0 |1 Status|UNCONFIRMED |NEEDINFO --- Comment #3 from m.a.riosv --- Please don't forget to attach a sample, with the step to reproduce the issue. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 144853] Sentence case applied around word, not undone when cycling case with Shift + F3
https://bugs.documentfoundation.org/show_bug.cgi?id=144853 --- Comment #14 from Mihail Balabanov --- I have lost hope that this issue is going to be resolved. For the time being, I published my workaround solution as an extension. It is a LibreOffice Basic macro for Cycle Case which honors the selection, changes only a single word when there is no selection, uses the current case of the selected text for a starting point instead of a counter, and can cycle the case of word the user just typed (including when there is already a space between it and the cursor). https://extensions.libreoffice.org/en/extensions/show/4036 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 152029] Visually draw attention to in-view bookmark or hyperlink when selecting/hovering it in the Navigator
https://bugs.documentfoundation.org/show_bug.cgi?id=152029 --- Comment #59 from Commit Notification --- Jim Raykowski committed a patch related to this issue. It has been pushed to "master": https://git.libreoffice.org/core/commit/18f35dffae44e741ea492ed5304f2d2d9d000f2d tdf#152029 related: Remove attention overlay on document view change It will be available in 24.2.0. The patch should be included in the daily builds available at https://dev-builds.libreoffice.org/daily/ in the next 24-48 hours. More information about daily builds can be found at: https://wiki.documentfoundation.org/Testing_Daily_Builds Affected users are encouraged to test the fix and report feedback. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-commits] core.git: sw/source
sw/source/uibase/utlui/content.cxx |1 +
1 file changed, 1 insertion(+)
New commits:
commit 18f35dffae44e741ea492ed5304f2d2d9d000f2d
Author: Jim Raykowski
AuthorDate: Thu Oct 12 09:01:27 2023 -0800
Commit: Jim Raykowski
CommitDate: Sat Oct 14 20:38:44 2023 +0200
tdf#152029 related: Remove attention overlay on document view change
Fixes stale overlay that can happen when Navigator use causes a
document view change. For example, when the Navigator is used to
change a heading level or to delete a heading by key input.
Change-Id: If4c0aa2e31f088a8fa12d7ed02012033c4d13509
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/157892
Tested-by: Jenkins
Reviewed-by: Jim Raykowski
diff --git a/sw/source/uibase/utlui/content.cxx
b/sw/source/uibase/utlui/content.cxx
index 9d96415c5c35..64e2c4aad25b 100644
--- a/sw/source/uibase/utlui/content.cxx
+++ b/sw/source/uibase/utlui/content.cxx
@@ -3272,6 +3272,7 @@ void SwContentTree::Notify(SfxBroadcaster & rBC, SfxHint
const& rHint)
break;
}
case SfxHintId::DocChanged:
+OverlayObject();
if (!m_bIgnoreDocChange)
{
m_bDocHasChanged = true;
Re: Any ideas why lock files do not work in Chrome OS’ Linux VM?
On 13.10.2023 19:46, Paul Menzel wrote: The German tutorial *LibreOffice unter Google Chrome OS auf einem Chromebook nutzen* [1] says to disable create of lock files by editing `/usr/lib/libreoffice/program/soffice` and commenting out the lines below: SAL_ENABLE_FILE_LOCKING=1 export SAL_ENABLE_FILE_LOCKING Then, under expert settings `useLocking` and `UseDocumentOOoLockfile` need to be set to `false`. Does somebody know, why this is needed? Could LibreOffice be improved to enable/disable file locking at runtime depending on the environment? ... [1]: https://linux-in-der-schule.de/2021/05/03/libreoffice-unter-google-chrome-os-auf-einem-chromebook-nutzen/ The tutorial explains, that "unfortunately you can't open any files yet because LibreOffice can't create lock files". If it is so, only you can tell (I would suggest trying first); and if so, please file a bug report at https://bugs.documentfoundation.org/, with steps to reproduce. Only that could enable to improve LibreOffice. -- Best regards, Mike Kaganski
[Libreoffice-bugs] [Bug 157778] Help file for MATCH function is inconsistent for multiple occurrences of the search criterion
https://bugs.documentfoundation.org/show_bug.cgi?id=157778 Mike Kaganski changed: What|Removed |Added Component|Calc|Documentation CC||olivier.hallot@libreoffice. ||org --- Comment #1 from Mike Kaganski --- The help article [1] is completely correct. It tells you, that type 1 of search (the default value of the optional third argument of MATCH) tells the function, that the lookup array *is* sorted ascending. And when it is *not* sorted accordingly, when the type is 1 (or missing), it is user's error, and the return value can be anything - user must not expect a meaningful result in this case. We need to add a note about that fact, similar to what we added for VLOOKUP [2]. It is completely unclear what "=MATCH(3: D:D)" in your description might stand for. [1] https://help.libreoffice.org/7.6/en-US/text/scalc/01/04060109.html?DbPAR=CALC#bm_id3158407 [2] https://help.libreoffice.org/7.6/en-US/text/scalc/01/04060109.html?DbPAR=CALC#bm_id3153152 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 157779] New: Icon needed for (somewhat) new UNO command InsertSparkline in Calc
https://bugs.documentfoundation.org/show_bug.cgi?id=157779 Bug ID: 157779 Summary: Icon needed for (somewhat) new UNO command InsertSparkline in Calc Product: LibreOffice Version: unspecified Hardware: All OS: All Status: UNCONFIRMED Severity: normal Priority: medium Component: UI Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: jl...@mail.com CC: jl...@mail.com Blocks: 148539 New in 7.4 I think. There are a number of "sparkline" commands. The prominent ones are InsertSparkline and FormatSparklineMenu. See sparkline branch https://gerrit.libreoffice.org/q/owner:quikee%2540gmail.com+sparklines+branch:master Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=148539 [Bug 148539] Notebookbar, Insert tab: lacks InsertSparkLine button -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 144853] Sentence case applied around word, not undone when cycling case with Shift + F3
https://bugs.documentfoundation.org/show_bug.cgi?id=144853 Tex2002ans changed: What|Removed |Added CC||Tex2002ans+LibreOffice@gmai ||l.com --- Comment #13 from Tex2002ans --- I confirm this issue happens in: Version: 7.6.2.1 (X86_64) / LibreOffice Community Build ID: 56f7684011345957bbf33a7ee678afaf4d2ba333 CPU threads: 8; OS: Windows 10.0 Build 19045; UI render: Skia/Raster; VCL: win Locale: en-US (en_US); UI: en-US Calc: CL threaded - - - I used the example text: - Mary Jones met Joe Smith at the park. and put my cursor in "met". Then I pressed Shift+F3 multiple times: 1. Mary Jones Met Joe Smith at the park. 2. Mary jones met joe smith at the park. 3. Mary jones MET joe smith at the park. 4. Mary jones met joe smith at the park. 5. Mary jones Met joe smith at the park. - - - I agree with Heiko's/Sascha's suggestion in Comment #3: > the ideal behavior would be as OP suggest, only change current word if no > selection is done If cursor only exists in a single word, it should not change casing of the entire sentence/paragraph. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 157778] New: Help file for MATCH function is inconsistent for multiple occurrences of the search criterion
https://bugs.documentfoundation.org/show_bug.cgi?id=157778 Bug ID: 157778 Summary: Help file for MATCH function is inconsistent for multiple occurrences of the search criterion Product: LibreOffice Version: 7.5.7.1 release Hardware: All OS: Windows (All) Status: UNCONFIRMED Severity: normal Priority: medium Component: Calc Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: wright...@hotmail.com Description: The example given in the helpfile does not match the definition. Most people see the example as the one to be followed. In this case, the result of believing the helpfile example can be very subtle but significant. As I know to my cost in time and energy! Consider the array D:D as 199,200,200,200,201 (no further entries) The help file for MATCH says:- 'If Type = 1 or the third parameter is omitted, the index of the last value that is smaller than or equal to the search criterion is returned.' so =MATCH(200; D:D) will give the value 4 THIS IS CORRECT BUT consider the example given '=MATCH(200;D1:D100) searches the area D1:D100, which is sorted by column D, for the value 200. As soon as this value is reached, the number of the row in which it was found is returned.' According to this example, =MATCH(3: D:D) will stop when it finds the criterion '200' and return the row number 2. This example is wrong! The error becomes a problem when, for instance, looking for a particular date when there are multiple records for each date. FURTHER ERROR The statement says 'which is sorted by column D' It is not necessary for the column to be sorted by Column D. In fact, it can be in ANY order according to the definition. Steps to Reproduce: 1.Create a sheet with D:D as stated 2.In a cell (eg A1), enter=MATCH(200;D:D) 3.Note that the answer (4) is correct according to the definition 4. Check that the example would give the number 2 5. Correct the wording. Note that the correct wording should also cope with the situation when there are several 200 values randomly placed Actual Results: as stated Expected Results: as stated Reproducible: Always User Profile Reset: No Additional Info: [Information automatically included from LibreOffice] Locale: en-GB Module: SpreadsheetDocument [Information guessed from browser] OS: Windows (All) OS is 64bit:yes MATCH Returns the relative position of an item in an array that matches a specified value. The function returns the position of the value found in the lookup_array as a number. Syntax MATCH(SearchCriterion; LookupArray; Type) SearchCriterion is the value which is to be searched for in the single-row or single-column array. LookupArray is the reference searched. A lookup array can be a single row or column, or part of a single row or column. Type may take the values 1, 0, or -1. If Type = 1 or if this optional parameter is omitted, it is assumed that the first column of the search array is sorted in ascending order. If Type = -1 it is assumed that the column is sorted in descending order. This corresponds to the same function in Microsoft Excel. If Type = 0, only exact matches are found. If the search criterion is found more than once, the function returns the index of the first matching value. Only if Type = 0 can you search for regular expressions (if enabled in calculation options) or wildcards (if enabled in calculation options). If Type = 1 or the third parameter is omitted, the index of the last value that is smaller than or equal to the search criterion is returned. This applies even when the search array is not sorted. For Type = -1, the index of the first value that is larger than or equal is returned. The search supports regular expressions. You can enter "all.*", for example to find the first location of "all" followed by any characters. If you want to search for a text string that is also a regular expression, you must precede every character with a \ character. You can switch the automatic evaluation of regular expression on and off in Tools - Options - LibreOffice Calc - Calculate. Example =MATCH(200;D1:D100) searches the area D1:D100, which is sorted by column D, for the value 200. As soon as this value is reached, the number of the row in which it was found is returned. If a higher value is found during the search in the column, the number of the previous row is returned. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 157704] language settings for document are not applied
https://bugs.documentfoundation.org/show_bug.cgi?id=157704 m.a.riosv changed: What|Removed |Added Ever confirmed|1 |0 Status|NEEDINFO|UNCONFIRMED -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 157777] Saving an ODT document as DOC or RTF corrupts the column-named-section
https://bugs.documentfoundation.org/show_bug.cgi?id=15 Mike Kaganski changed: What|Removed |Added Resolution|--- |NOTABUG Status|UNCONFIRMED |RESOLVED --- Comment #1 from Mike Kaganski --- It is not a bug: you save to file formats that have no support for Writer's (ODF) sections. MS Word (and all formats created for it) uses the word "section" for something different; and that thing is not named. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 63432] FORMATTING: "Change Case" does not work in some situations when symbols appear
https://bugs.documentfoundation.org/show_bug.cgi?id=63432 --- Comment #13 from Tex2002ans --- I confirm this is still an issue in: Version: 7.6.2.1 (X86_64) / LibreOffice Community Build ID: 56f7684011345957bbf33a7ee678afaf4d2ba333 CPU threads: 8; OS: Windows 10.0 Build 19045; UI render: Skia/Raster; VCL: win Locale: en-US (en_US); UI: en-US Calc: CL threaded I used the document in Comment #9. - - - These 2 seem correct: - Format > Text > Capitalize Every Word - Format > Text > tOGGLE cASE but this one is partially broken: - Format > Text > Sentence Case - - - I think tommy27 put his finger on it in Comment #6... it seems like LO currently says: - If the first character in sentence is punctuation... - Do nothing. - (Or "Capitalize the punctuation"... which does nothing.) When it should be: - If first character in sentence is punctuation... - Find the next valid character/letter to capitalize. - - - I also tested Steps 1–3 in Comment #3 by Ákos: - That now works fine. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 157777] New: Saving an ODT document as DOC or RTF corrupts the column-named-section
https://bugs.documentfoundation.org/show_bug.cgi?id=15 Bug ID: 15 Summary: Saving an ODT document as DOC or RTF corrupts the column-named-section Product: LibreOffice Version: 7.5.6.2 release Hardware: All OS: Windows (All) Status: UNCONFIRMED Severity: normal Priority: medium Component: Writer Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: traceyad2...@gmail.com Created attachment 190216 --> https://bugs.documentfoundation.org/attachment.cgi?id=190216=edit column named sections bug When saving an ODT document in LibreOffice as a DOC or an RTF, the 247 column-named-section get changed to Sections1 thru Section490 (normal mode or safe mode) I saved the document in LibreOffice as a DOC and an RTF then reopened the documents in LibreOffice to verify that the column-named-sections are being corrupted by LibreOffice itself. Please help Thanks, Tracey Since LibreOffice find-replace font-style corrupts the document (bug 157743), my alternate attempt to fix the text was to export as (DOC or RTF) to (Word2000 or Word2002) and it fixed the text, but I discovered this issue. When I export the ODT document from LibreOffice as DOC: opening/changing/saving the DOC in Word2000 find-replace: 21,632 times does NOT corrupt the text-fonts opening/changing/saving the DOC in Word2002 find-replace: 21,632 times does NOT corrupt the text-fonts -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 157744] find is hampered by settings in find/replace
https://bugs.documentfoundation.org/show_bug.cgi?id=157744 --- Comment #3 from Tracey --- I use search/replace specifying a text with a particular font (or any restrictive characteristics). When I exit search/replace then try to find some text, if it fails to find something I know is there, I have to go back into search/replace and click on "no format". After that, the find function works fine. Thanks, Tracey Version: 7.5.6.2 (X86_64) / LibreOffice Community Build ID: f654817fb68d6d4600d7d2f6b647e47729f55f15 CPU threads: 2; OS: Windows 6.1 Service Pack 1 Build 7601; UI render: Skia/Raster; VCL: win Locale: en-US (en_US); UI: en-US Calc: CL threaded -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 157775] fichier texte : Copier un tableau d'un fichier sur un autre fichier, calculs perdus
https://bugs.documentfoundation.org/show_bug.cgi?id=157775 accu...@allaisentreprise.fr changed: What|Removed |Added Version|unspecified |7.6.2.1 release --- Comment #1 from accu...@allaisentreprise.fr --- Calculs perdus. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 157776] "Save changes to document" appears even after just opening and closing and no edits
https://bugs.documentfoundation.org/show_bug.cgi?id=157776 Gerald Pfeifer changed: What|Removed |Added Summary|"Save changes to document" |"Save changes to document" ||appears even after just ||opening and closing and no ||edits -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 157776] New: "Save changes to document"
https://bugs.documentfoundation.org/show_bug.cgi?id=157776 Bug ID: 157776 Summary: "Save changes to document" Product: LibreOffice Version: 7.1.8.1 release Hardware: All OS: All Status: UNCONFIRMED Keywords: bibisectRequest, regression Severity: normal Priority: medium Component: Impress Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: ger...@pfeifer.com Created attachment 190215 --> https://bugs.documentfoundation.org/attachment.cgi?id=190215=edit Sample document (PPTX) How to reproduce: 1. Open sample document "savechanges.pptx" 2. - - or- "File" - "Exit LibreOffice" 3. Expected behavior: Window or LibreOffice closes. Actual behavior "Save Document Save changes to document "savechanges.pptx" before closing? Your changes will be lost if you don't save them." appears. Note: Same document, first slide removed, no longer reproduces. Same document, graphics on second slide removed, no longer reproduces. Not present in Version: 7.0.7.0.0+ Build ID: 54e9dd41dc9dd45af12c9346199f601ea4a5994d CPU threads: 8; OS: Linux 6.5; UI render: default; VCL: gtk3 Locale: en-US (en_US.UTF-8); UI: en-US TinderBox: Linux-rpm_deb-x86_64@86-TDF, Branch:libreoffice-7-0, Time: 2021-05-07_08:22:18 Present in Version: 7.1.8.0.0+ / LibreOffice Community Build ID: 4784990eda6098f0408276b4d424e81382a50460 CPU threads: 8; OS: Linux 6.5; UI render: default; VCL: gtk3 Locale: en-US (en_US.UTF-8); UI: en-US TinderBox: Linux-rpm_deb-x86_64@86-TDF, Branch:libreoffice-7-1, Time: 2021-10-15_11:37:03 and still in Version: 24.2.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: e9374f74385d7dfe77d1902d3d82af20143bc775 CPU threads: 8; OS: Linux 6.5; UI render: default; VCL: gtk3 Locale: en-US (en_US.UTF-8); UI: en-US So a regression between 7.0.7 and 7.1.8. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 157775] New: fichier texte : Copier un tableau d'un fichier sur un autre fichier, calculs perdus
https://bugs.documentfoundation.org/show_bug.cgi?id=157775 Bug ID: 157775 Summary: fichier texte : Copier un tableau d'un fichier sur un autre fichier, calculs perdus Product: LibreOffice Version: unspecified Hardware: All OS: All Status: UNCONFIRMED Severity: normal Priority: medium Component: Writer Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: accu...@allaisentreprise.fr Copie d'un tableau d'un fichier versun autre. Calculs perdus. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 157743] find replace font style size finds wrong text
https://bugs.documentfoundation.org/show_bug.cgi?id=157743 --- Comment #2 from Tracey --- Created attachment 190214 --> https://bugs.documentfoundation.org/attachment.cgi?id=190214=edit find-replace bug sample Issue : LibreOffice find-replace font-style feature corrupts the text-fonts My desire was to: Change from: LibreOffice Sans Regular 12point Change to: LibreOffice Serif Italic 12point Find-Replace actually changes 14point text when it should not and fails to change 12point text when it should (normal mode or safe mode). LibreOffice find-replace: 11,853 times and corrupts the text-fonts (see attached) Thanks, Tracey When I export the ODT document from LibreOffice as DOC: opening/changing/saving the DOC in Word2000 find-replace: 21,632 times does NOT corrupt the text-fonts opening/changing/saving the DOC in Word2002 find-replace: 21,632 times does NOT corrupt the text-fonts However, when saving an ODT document with LibreOffice as a DOC or an RTF, the column-section names get corrupted (but that is another issue). -- You are receiving this mail because: You are the assignee for the bug.
