[Libreoffice-bugs] [Bug 112805] Support for "size" (optical size) OpenType table
https://bugs.documentfoundation.org/show_bug.cgi?id=112805 Volga changed: What|Removed |Added See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=15 ||3368 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153368] Support optical size for OpenType variable fonts
https://bugs.documentfoundation.org/show_bug.cgi?id=153368 Volga changed: What|Removed |Added See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=11 ||2805 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153369] New: dpkg: erreur: archive 'LibreOffice_7.5.0.3_Linux_x86-64_deb/' is not a regular file
https://bugs.documentfoundation.org/show_bug.cgi?id=153369 Bug ID: 153369 Summary: dpkg: erreur: archive 'LibreOffice_7.5.0.3_Linux_x86-64_deb/' is not a regular file Product: LibreOffice Version: 7.5.0.3 release Hardware: All OS: All Status: UNCONFIRMED Severity: normal Priority: medium Component: LibreOffice Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: m.se...@proximus.be Hello, I have download the new version of LibreOffice, Unzip the donwloaded files, an try to install the the pakage, michel@I7:~/Logiciel$ sudo dpkg -i LibreOffice_7.5.0.3_Linux_x86-64_deb/ the response is : dpkg: erreur: archive 'LibreOffice_7.5.0.3_Linux_x86-64_deb/' is not a regular file my home system; Nom OS : GNU/Linux Noyau : #1 SMP Debian 4.19.269-1 (2022-12-20) Relase : 4.19.0-23-amd64 Debian : 10.13 buster Nom PC : I7 Machine : x86_64 Thank you michel -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153368] New: Support optical size for OpenType variable fonts
https://bugs.documentfoundation.org/show_bug.cgi?id=153368 Bug ID: 153368 Summary: Support optical size for OpenType variable fonts Product: LibreOffice Version: 7.6.0.0 alpha0+ Master Hardware: All OS: All Status: UNCONFIRMED Severity: normal Priority: medium Component: LibreOffice Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: shanshandehongx...@outlook.com Description: OpenType font variation have the 'size' axis for optical fonts. In LibreOffice this should be activated by default for variable fonts so they would be able to produce proper rendition on documents. If a font have both 'size' axis and 'size' feature tag, the 'size' axis should override 'size' feature tag. Steps to Reproduce: - Actual Results: - Expected Results: - Reproducible: Always User Profile Reset: No Additional Info: - -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 143344] [META] Linux Dark Mode bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=143344 Bug 143344 depends on bug 153353, which changed state. Bug 153353 Summary: When switching between freedesktop light and dark mode, Calc's formula bar text entry has leftover colors from the previous theme https://bugs.documentfoundation.org/show_bug.cgi?id=153353 What|Removed |Added Status|ASSIGNED|RESOLVED Resolution|--- |FIXED -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-commits] core.git: sc/source
sc/source/ui/app/inputwin.cxx | 27 ---
sc/source/ui/inc/inputwin.hxx |2 ++
2 files changed, 22 insertions(+), 7 deletions(-)
New commits:
commit 462bbf692e41897552b4f4e1f9e4f033e5f76643
Author: Caolán McNamara
AuthorDate: Fri Feb 3 16:18:35 2023 +
Commit: Caolán McNamara
CommitDate: Sat Feb 4 07:38:17 2023 +
Resolves: tdf#153353 formula bar border area bg didn't change on theme
change
Change-Id: I720054d540a6352b8248aa59e231878c1832d998
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/146545
Tested-by: Jenkins
Reviewed-by: Caolán McNamara
diff --git a/sc/source/ui/app/inputwin.cxx b/sc/source/ui/app/inputwin.cxx
index 7b9e208aec14..a9b5a54367b9 100644
--- a/sc/source/ui/app/inputwin.cxx
+++ b/sc/source/ui/app/inputwin.cxx
@@ -853,14 +853,8 @@ ScInputBarGroup::ScInputBarGroup(vcl::Window* pParent,
ScTabViewShell* pViewSh)
{
InitControlBase(m_xContainer.get());
-const StyleSettings& rStyleSettings =
Application::GetSettings().GetStyleSettings();
-
SetPaintTransparent(false);
-SetBackground(rStyleSettings.GetFaceColor());
-
-// match to bg used in ScTextWnd::SetDrawingArea to the margin area is
drawn with the
-// same desired bg
-mxBackground->set_background(rStyleSettings.GetWindowColor());
+SetBackgrounds();
mxButtonUp->connect_clicked(LINK(this, ScInputBarGroup, ClickHdl));
mxButtonDown->connect_clicked(LINK(this, ScInputBarGroup, ClickHdl));
@@ -881,6 +875,25 @@ ScInputBarGroup::ScInputBarGroup(vcl::Window* pParent,
ScTabViewShell* pViewSh)
mxButtonDown->show();
}
+void ScInputBarGroup::SetBackgrounds()
+{
+const StyleSettings& rStyleSettings =
Application::GetSettings().GetStyleSettings();
+SetBackground(rStyleSettings.GetFaceColor());
+// match to bg used in ScTextWnd::SetDrawingArea to the margin area is
drawn with the
+// same desired bg
+mxBackground->set_background(rStyleSettings.GetWindowColor());
+}
+
+void ScInputBarGroup::DataChanged(const DataChangedEvent& rDCEvt)
+{
+InterimItemWindow::DataChanged(rDCEvt);
+if ((rDCEvt.GetType() == DataChangedEventType::SETTINGS) &&
(rDCEvt.GetFlags() & AllSettingsFlags::STYLE))
+{
+SetBackgrounds();
+Invalidate();
+}
+}
+
Point ScInputBarGroup::GetCursorScreenPixelPos(bool bBelow)
{
return mxTextWndGroup->GetCursorScreenPixelPos(bBelow);
diff --git a/sc/source/ui/inc/inputwin.hxx b/sc/source/ui/inc/inputwin.hxx
index ac96062af137..e8e63855ffd6 100644
--- a/sc/source/ui/inc/inputwin.hxx
+++ b/sc/source/ui/inc/inputwin.hxx
@@ -252,6 +252,7 @@ public:
virtual boolHasEditView() const override;
Point GetCursorScreenPixelPos(bool bBelowLine);
virtual voidResize() override;
+virtual voidDataChanged(const DataChangedEvent& rDCEvt)
override;
virtual const OUString& GetTextString() const override;
virtual voidStopEditEngine(bool bAll) override;
virtual voidTextGrabFocus() override;
@@ -272,6 +273,7 @@ public:
private:
voidTriggerToolboxLayout();
+voidSetBackgrounds();
std::unique_ptr mxBackground;
std::unique_ptr mxTextWndGroup;
[Libreoffice-bugs] [Bug 76131] Existing pinned icon on Win7/8/10/11 is taskbar invalid after re-installation/update and start menu icons are swapped (W10/W11)
https://bugs.documentfoundation.org/show_bug.cgi?id=76131 Fridrich Strba changed: What|Removed |Added CC|fridrich.st...@bluewin.ch | --- Comment #77 from Fridrich Strba --- . -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 76131] Existing pinned icon on Win7/8/10/11 is taskbar invalid after re-installation/update and start menu icons are swapped (W10/W11)
https://bugs.documentfoundation.org/show_bug.cgi?id=76131 --- Comment #76 from Kumāra --- (In reply to Dietmar from comment #75) > In the context of Mike's correct remarks, I would like to extend this bug > with a part of my bug 153337, so that I can mark it as duplicate. > > In my bug I addressed on the one hand the problem of icons in the taskbar > discussed here, however I also addressed a similar problem in the start menu > : > > If I pin links to several LibreOffice programs in the Start menu, e.g. > LibreOffice, LibreOffice Writer and LibreOffice Calc in exactly this order, > then these are still present and active after an update in contrast to the > icons in the TaskBar, but the order is swapped, e.g. LibreOffice Calc, > LibreOffice and LibreOffice Writer. So after each update I have to fix the > icons in the taskbar and also the order of the icons in the start menu. This > is not a big issue for single devices, but extremely annoying if you have to > do it several hundred times a year. I think you may rightly put the two together only if the fix is sure to address both issues. Otherwise, you should report this (new) issue separately. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153367] New: Allow numbered font weight
https://bugs.documentfoundation.org/show_bug.cgi?id=153367 Bug ID: 153367 Summary: Allow numbered font weight Product: LibreOffice Version: 7.6.0.0 alpha0+ Master Hardware: All OS: All Status: UNCONFIRMED Severity: normal Priority: medium Component: LibreOffice Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: shanshandehongx...@outlook.com Description: Currently LibreOffice could handle multiple font weights, however there are some variable fonts required to set font weight by number, thus it's necessary to allow users to input number to set font weight from the wght axis. Steps to Reproduce: - Actual Results: - Expected Results: - Reproducible: Always User Profile Reset: No Additional Info: -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 135871] Highlighting no fill is not the same as no fill; there is still direct formatting present according to paragraph style
https://bugs.documentfoundation.org/show_bug.cgi?id=135871 Dieter changed: What|Removed |Added Status|UNCONFIRMED |NEEDINFO CC||dgp-m...@gmx.de Ever confirmed|0 |1 --- Comment #60 from Dieter --- I don't want to read the whole "book", but just want to ask you, Telesto, if the situation is still the same with LO 7.5. And perhaps it is possible for you to summarize previous discussion. => NEEDINFO -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153366] New: New Main LibreOffice Icons Are a Complete Failure!
https://bugs.documentfoundation.org/show_bug.cgi?id=153366 Bug ID: 153366 Summary: New Main LibreOffice Icons Are a Complete Failure! Product: LibreOffice Version: 7.5.0.3 release Hardware: All OS: All Status: UNCONFIRMED Severity: normal Priority: medium Component: Writer Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: brendieel...@brenda-make.com Description: The main Libreoffice icons do not function. They are broken. The Writer icon used to look like a document. The new one? I can't tell. What the hell was it supposed to be? When was the last time, you wrote a document on dark blue paper? The icons do not need to be novel or fun; they should depict what the program should look like. This is beyond change for change's sake--they icons don't even work. To be nit-picky, the icons cannot even decide if there is rounded corners or folded. Please, put the old ones back until you come up with something that looks like something in this world. Did Microsoft make them for you? Steps to Reproduce: 1. Icon should convey usage. Actual Results: Icon doesn't look like paper or text, or a document. Expected Results: Icon should look like a document, perhaps a word processor document. Reproducible: Always User Profile Reset: No Additional Info: Seriously, it bears examination on just how the icons were ever approved. I am sorry, but if the designer cannot design a usable icon, then they shouldn't be making them. It doesn't matter if it's someone's first attempt, or that they are your friend; you have to think of the project, in large. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 145565] (Enhancement) In Writer, make it easier to align forms to text
https://bugs.documentfoundation.org/show_bug.cgi?id=145565 Dieter changed: What|Removed |Added Ever confirmed|0 |1 Status|UNCONFIRMED |NEEDINFO CC||dgp-m...@gmx.de --- Comment #3 from Dieter --- Marja, a new major release is available at https://www.libreoffice.org/download/download-libreoffice/ Could you please retest ith LO 7.5? If problem ist still present there, I will try to reproduce it, but I must admit that steps are unclear to me. => NEEDINFO -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153330] The XFilePickerControlAccess.setLabel method does not change the name of the "Open" button (when LO Open/Save dialogs are not used).
https://bugs.documentfoundation.org/show_bug.cgi?id=153330 Mike Kaganski changed: What|Removed |Added OS|All |Windows (All) --- Comment #4 from Mike Kaganski --- (In reply to Caolán McNamara from comment #3) Thanks - I must had been tested with an older version (even though I thought I checked that, but likely I confused myself). Yes, I see this in current master. Let's mark it Windows-only; any other VCL plugin, if it happens to not implement this, would need to have a separate bug, preferably with this in See Also. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 152976] Print preview should start with right page, if document is in book view mode
https://bugs.documentfoundation.org/show_bug.cgi?id=152976 --- Comment #6 from Dieter --- Having a look at bug 153127, I realized print preview toolbar for the first time. So using this toolbar, it is of course possible to have book view as preview. But some users (at least I) might be focused on icons in status bar. So I'd like to suggest 1. Remove view mode icons in status bar, because you can't change them and the selected multi-page-view indicates something wrong, if you change view mode in toolbar 2. Change current behaviour a) Document is in single view Actual: Two-pages-preview and Book Preview off Expected: Single-Page preview and Book Preview off b) Document is in Multi-page view Actual and expected result: Two-pages-preview and Book Preview off c) Document is in Book view Actual: Two-pages-preview and Book Preview off Expected: Two-pages-preview and Book Preview on -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153127] "Book preview" should be separate from other page preview buttons in Print Preview toolbar
https://bugs.documentfoundation.org/show_bug.cgi?id=153127 Dieter changed: What|Removed |Added Whiteboard| QA:needsComment| CC||dgp-m...@gmx.de See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=15 ||2976 --- Comment #1 from Dieter --- I support that idea. I must admit, that it's the first time I've recognized print preview toolbar. I would also recommend to remove view options in status bar in print preview (but I will comment this in bug 152976). -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 152976] Print preview should start with right page, if document is in book view mode
https://bugs.documentfoundation.org/show_bug.cgi?id=152976 Dieter changed: What|Removed |Added See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=15 ||3127 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-ux-advise] [Bug 153127] "Book preview" should be separate from other page preview buttons in Print Preview toolbar
https://bugs.documentfoundation.org/show_bug.cgi?id=153127 Dieter changed: What|Removed |Added Whiteboard| QA:needsComment| CC||dgp-m...@gmx.de See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=15 ||2976 --- Comment #1 from Dieter --- I support that idea. I must admit, that it's the first time I've recognized print preview toolbar. I would also recommend to remove view options in status bar in print preview (but I will comment this in bug 152976). -- You are receiving this mail because: You are on the CC list for the bug.
[Libreoffice-commits] core.git: 2 commits - vcl/source
vcl/source/window/window2.cxx | 14 +++---
1 file changed, 11 insertions(+), 3 deletions(-)
New commits:
commit d4c99f07ed4a795519797f56be29c24a242f4db2
Author: Aron Budea
AuthorDate: Thu Feb 2 00:08:41 2023 +0100
Commit: Andras Timar
CommitDate: Sat Feb 4 06:18:30 2023 +
vcl: fix online crash in vcl::Window::IsTracking()
Crashreport signature:
program/libmergedlo.so
vcl::Window::IsTracking() const
vcl/source/window/window2.cxx:340
program/libmergedlo.so
(anonymous namespace)::LOKPostAsyncEvent(void*, void*)
sfx2/source/view/lokhelper.cxx:812
program/libmergedlo.so
LokChartHelper::postMouseEvent(int, int, int, int, int, int,
double, double)
include/rtl/ref.hxx:128
program/libmergedlo.so
SfxLokHelper::testInPlaceComponentMouseEventHit(SfxViewShell*, int,
int, int, int, int, int, double, double, bool)
sfx2/source/view/lokhelper.cxx:980
/program/libswlo.so
SwXTextDocument::postMouseEvent(int, int, int, int, int, int)
sw/source/uibase/uno/unotxdoc.cxx:3663
program/libmergedlo.so
doc_postMouseEvent
desktop/source/lib/init.cxx:4831
Change-Id: Iab7d24a901e57dc8af3fb2c77fbea3b4fdad9fb9
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/146483
Tested-by: Jenkins CollaboraOffice
Reviewed-by: Miklos Vajna
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/146549
Tested-by: Jenkins
Reviewed-by: Andras Timar
diff --git a/vcl/source/window/window2.cxx b/vcl/source/window/window2.cxx
index 87db8e470e21..180edf5cf961 100644
--- a/vcl/source/window/window2.cxx
+++ b/vcl/source/window/window2.cxx
@@ -341,9 +341,15 @@ bool Window::IsTracking() const
{
if (!mpWindowImpl)
return false;
-return (mpWindowImpl->mbUseFrameData ?
-mpWindowImpl->mpFrameData->mpTrackWin == this :
-ImplGetSVData()->mpWinData->mpTrackWin == this);
+if (mpWindowImpl->mbUseFrameData && mpWindowImpl->mpFrameData)
+{
+return mpWindowImpl->mpFrameData->mpTrackWin == this;
+}
+if (!mpWindowImpl->mbUseFrameData && ImplGetSVData()->mpWinData)
+{
+return ImplGetSVData()->mpWinData->mpTrackWin == this;
+}
+return false;
}
void Window::StartAutoScroll( StartAutoScrollFlags nFlags )
commit cb44dab0784476a2be0708e801696f47486aa3a2
Author: Noel Grandin
AuthorDate: Fri Jan 27 08:50:04 2023 +0200
Commit: Andras Timar
CommitDate: Sat Feb 4 06:18:21 2023 +
fix online crash in WIndow::IsTracking
/opt/collaboraoffice/program/libmergedlo.so
vcl::Window::IsTracking() const
/home/collabora/jenkins/workspace/build_core_co-22.05_for_online_snapshot/vcl/source/window/window2.cxx:340
/opt/collaboraoffice/program/libmergedlo.so
(anonymous namespace)::LOKPostAsyncEvent(void*, void*)
/home/collabora/jenkins/workspace/build_core_co-22.05_for_online_snapshot/sfx2/source/view/lokhelper.cxx:812
/opt/collaboraoffice/program/libmergedlo.so
LokChartHelper::postMouseEvent(int, int, int, int, int, int, double,
double)
/home/collabora/jenkins/workspace/build_core_co-22.05_for_online_snapshot/include/rtl/ref.hxx:128
Change-Id: I204bac7d8f595054abe9b6e8e631c02b26e20361
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/146231
Tested-by: Jenkins CollaboraOffice
Reviewed-by: Noel Grandin
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/146548
Tested-by: Jenkins
Reviewed-by: Andras Timar
diff --git a/vcl/source/window/window2.cxx b/vcl/source/window/window2.cxx
index 978dc0b6ecf8..87db8e470e21 100644
--- a/vcl/source/window/window2.cxx
+++ b/vcl/source/window/window2.cxx
@@ -339,6 +339,8 @@ void Window::EndTracking( TrackingEventFlags nFlags )
bool Window::IsTracking() const
{
+if (!mpWindowImpl)
+return false;
return (mpWindowImpl->mbUseFrameData ?
mpWindowImpl->mpFrameData->mpTrackWin == this :
ImplGetSVData()->mpWinData->mpTrackWin == this);
[Libreoffice-bugs] [Bug 137942] pyuno package for linux contains windows executable files
https://bugs.documentfoundation.org/show_bug.cgi?id=137942 --- Comment #9 from lvm --- Still repeatable in Version: 7.4.4.2 / LibreOffice Community Build ID: 85569322deea74ec9134968a29af2df5663baa21 CPU threads: 4; OS: Linux 5.4; UI render: default; VCL: kf5 (cairo+xcb) Locale: en-GB (en_GB.UTF-8); UI: en-GB Calc: threaded $ find -name *.exe ./libreoffice7.4/program/python-core-3.8.16/lib/distutils/command/wininst-9.0-amd64.exe ./libreoffice7.4/program/python-core-3.8.16/lib/distutils/command/wininst-10.0.exe ./libreoffice7.4/program/python-core-3.8.16/lib/distutils/command/wininst-14.0-amd64.exe ./libreoffice7.4/program/python-core-3.8.16/lib/distutils/command/wininst-6.0.exe ./libreoffice7.4/program/python-core-3.8.16/lib/distutils/command/wininst-10.0-amd64.exe ./libreoffice7.4/program/python-core-3.8.16/lib/distutils/command/wininst-7.1.exe ./libreoffice7.4/program/python-core-3.8.16/lib/distutils/command/wininst-9.0.exe ./libreoffice7.4/program/python-core-3.8.16/lib/distutils/command/wininst-14.0.exe ./libreoffice7.4/program/python-core-3.8.16/lib/distutils/command/wininst-8.0.exe -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 123004] EDITING: Sheet/Named ranges/Insert - Paste all, only pastes named ranges with global scope
https://bugs.documentfoundation.org/show_bug.cgi?id=123004 --- Comment #7 from m.a.riosv --- Still Version: 7.6.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: fa1f2b7f5c65d66eaa5887acc9da5eb526570b18 CPU threads: 4; OS: Windows 10.0 Build 19045; UI render: Skia/Raster; VCL: win Locale: es-ES (es_ES); UI: en-US Calc: CL threaded Jumbo -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153365] Invoking font list freezes program and after long delay crashes LibreOffice
https://bugs.documentfoundation.org/show_bug.cgi?id=153365 --- Comment #1 from John Hale --- Error occurs from 7.4.2 onward through to including current 7.5 As noted, works fine on 7.3.7 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153365] New: Invoking font list freezes program and after long delay crashes LibreOffice
https://bugs.documentfoundation.org/show_bug.cgi?id=153365 Bug ID: 153365 Summary: Invoking font list freezes program and after long delay crashes LibreOffice Product: LibreOffice Version: 4.2.0.4 release Hardware: All OS: All Status: UNCONFIRMED Severity: normal Priority: medium Component: LibreOffice Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: hal...@gmail.com Description: Windows 64. With text program and slide program, invoking font list freezes program and after long delay crashes LibreOffice. Have tried repeatedly with all 7.4 releases and 7.5. One user online said that this problem did not exist with 7.3.7. I installed 7.3.7, and it pulled up my font list immediately without problem. The text used to experiment was very short, so file size is not the issue. My laptop has a modern CPU and 8mb of RAM. It has handled multiple graphics programs simultaneously with problem. The user scenario is that many users, such as I am, need to access multiple fonts for document design. Inability to access such a basic capability as fonts is a deal breaker. I am willing to use the deprecated 7.3 for a reasonable time to fix this bug. Otherwise, users needing more than basic text design will have to look elsewhere. Thanks for your help. Steps to Reproduce: 1.open Writer or Impress on Windows 2.type in a sentence 3.call up font list (I have, like other designers, a long list of fonts, which however works quickly and smoothly on 7.3.7. Actual Results: The new versions freeze the system including other applications, then at least 80% of the time completely crashes. Expected Results: Font list should invoke immediately to use in modifying text. Reproducible: Always User Profile Reset: Yes Additional Info: All as above -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 140147] position of cursor not saved
https://bugs.documentfoundation.org/show_bug.cgi?id=140147 --- Comment #43 from Peter --- I would like to add my experience to this thread. Note: I have tried the suggested solutions to this problem, without effect. • 19 Aug 2022 upgraded Libre Office 7.3.5.2 (x64) to 7.4.0.3 (x64) 21 Aug 2022 Noticed that this version does not properly remember where in the document the file was closed, so that when opened, the cursor is positioned somewhere quite remote from where it should be. Libre Office also opens in a fixed wide and shallow height window (that is, it does not remember the window size from the last close). • 18 Sep 2022 Upgraded Libre Office 7.4.0.3 (x64) to 7.4.1.2 (x64). This has fixed the opening size of the Libre Office window which was a problem from the 19 Aug 2022 7.4.0.3 (x64) upgrade. That is, the size when last closed is remembered again, but the position in the document is still not recalled. • 22 Oct 2022 Upgraded Libre Office 7.4.1.1 (x64) to 7.4.2.2 (x64). This has NOT FIXED the correct saving of the position in the document which has been a problem from the 19 Aug 2022 7.4.0.3 (x64) upgrade. • 15 Dec 2022 Upgraded Libre Office 7.4.2.3 to 7.4.3.2 (x64). This has NOT FIXED the correct saving of the position in the document which has been a problem from the 19 Aug 2022 7.4.0.3 (x64) upgrade. • 28 Jan 2023 Upgraded Libre Office 7.4.3.2 (x64) to: Version: 7.4.5.1 (x64) / LibreOffice Community Build ID: 9c0871452b3918c1019dde9bfac75448afc4b57f CPU threads: 8; OS: Windows 10.0 Build 19044; UI render: Skia/Raster; VCL: win Locale: en-NZ (en_NZ); UI: en-US Calc: threaded This has still NOT FIXED the correct saving of the position in the document which has been a problem from the 19 Aug 2022 7.4.0.3 (x64) upgrade. • 04 Feb 2023 Upgraded Libre Office Version: 7.4.5.1 (x64) to: Version: 7.5.0.3 (X86_64) / LibreOffice Community Build ID: c21113d003cd3efa8c53188764377a8272d9d6de CPU threads: 8; OS: Windows 10.0 Build 19045; UI render: Skia/Raster; VCL: win Locale: en-NZ (en_NZ); UI: en-US Calc: threaded This has still NOT FIXED the correct saving of the position in the document which has been a problem from the 19 Aug 2022 7.4.0.3 (x64) upgrade. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153127] "Book preview" should be separate from other page preview buttons in Print Preview toolbar
https://bugs.documentfoundation.org/show_bug.cgi?id=153127 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 153297] A complex formula does not work in Calc 7.4.x; (MATCH function)
https://bugs.documentfoundation.org/show_bug.cgi?id=153297 QA Administrators changed: What|Removed |Added Keywords||bibisectRequest -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-ux-advise] [Bug 153127] "Book preview" should be separate from other page preview buttons in Print Preview toolbar
https://bugs.documentfoundation.org/show_bug.cgi?id=153127 QA Administrators changed: What|Removed |Added Whiteboard|| QA:needsComment -- You are receiving this mail because: You are on the CC list for the bug.
[Libreoffice-bugs] [Bug 147519] 7.3.0.3 broken just crashes. 7.3.1 will work with --safe-mode.
https://bugs.documentfoundation.org/show_bug.cgi?id=147519 --- Comment #8 from QA Administrators --- Dear Michael Setzer II, 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 95239] Wrong ToC in Navigator and PDF when using frames
https://bugs.documentfoundation.org/show_bug.cgi?id=95239 --- Comment #7 from QA Administrators --- Dear Joaquim Pedro França Simão, 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 60814] Colors of shapes change after copy+paste from one drawing to another
https://bugs.documentfoundation.org/show_bug.cgi?id=60814 --- Comment #16 from QA Administrators --- Dear Clemens Eisserer, 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 77778] Writer thinly displays hidden column on Paste Special RTF paste from Calc table
https://bugs.documentfoundation.org/show_bug.cgi?id=8 --- Comment #17 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 140114] Line spacing partly lost after copy/paste
https://bugs.documentfoundation.org/show_bug.cgi?id=140114 --- 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 137942] pyuno package for linux contains windows executable files
https://bugs.documentfoundation.org/show_bug.cgi?id=137942 --- Comment #8 from QA Administrators --- Dear lvm, 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 123004] EDITING: Sheet/Named ranges/Insert - Paste all, only pastes named ranges with global scope
https://bugs.documentfoundation.org/show_bug.cgi?id=123004 --- Comment #6 from QA Administrators --- Dear m.a.riosv, 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 122545] FILEOPEN: Error on creating script provider for Python script from location=document
https://bugs.documentfoundation.org/show_bug.cgi?id=122545 --- Comment #13 from QA Administrators --- Dear spinnau, 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 117498] Ctrl+[ decreases only first cell in table
https://bugs.documentfoundation.org/show_bug.cgi?id=117498 --- Comment #6 from QA Administrators --- Dear Bastien Nocera, 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 120134] Page rendering: missing pages when pasting a large table
https://bugs.documentfoundation.org/show_bug.cgi?id=120134 --- Comment #4 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 108318] Copying a hyperlink into a textbox messes up its frame target
https://bugs.documentfoundation.org/show_bug.cgi?id=108318 --- Comment #10 from QA Administrators --- Dear Bernd Brinker, 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 117190] Formatting is applied to outer table when Embedding a formatted table (using a table style) into a table cell
https://bugs.documentfoundation.org/show_bug.cgi?id=117190 --- Comment #9 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 148872] Right-Click at the right end of Selected Text, the selection will be released
https://bugs.documentfoundation.org/show_bug.cgi?id=148872 nobu changed: What|Removed |Added Version|7.3.0.0 beta1+ |7.3.0.0 alpha0+ -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 152430] Libreoffice hangs when cycling through open documents
https://bugs.documentfoundation.org/show_bug.cgi?id=152430 Telesto changed: What|Removed |Added CC||solomonchar...@me.com --- Comment #9 from Telesto --- *** Bug 153348 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 153348] If I use Command-Tab on mac to change windows in LibreOffice the app freezes and I lose my work
https://bugs.documentfoundation.org/show_bug.cgi?id=153348 Telesto changed: What|Removed |Added Resolution|--- |DUPLICATE Status|NEEDINFO|RESOLVED --- Comment #2 from Telesto --- *** This bug has been marked as a duplicate of bug 152430 *** -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153323] Assertion `(nLen == TextFrameIndex(COMPLETE_STRING)) ? (nIdx.get() < rText.getLength()) : (nIdx + nLen).get() <= rText.getLength()' failed
https://bugs.documentfoundation.org/show_bug.cgi?id=153323 --- Comment #8 from Telesto --- (In reply to Buovjaga from comment #2) Incremental builds on macOS tend to produce spurious asserts (and other quirkiness) once in a while (at least for me). A make clean build might solve the problem -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153364] New: libreoffice writer dont open odt document
https://bugs.documentfoundation.org/show_bug.cgi?id=153364 Bug ID: 153364 Summary: libreoffice writer dont open odt document Product: LibreOffice Version: 7.5.0.3 release Hardware: All OS: All Status: UNCONFIRMED Severity: normal Priority: medium Component: Writer Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: elias__0...@yahoo.com Created attachment 185100 --> https://bugs.documentfoundation.org/attachment.cgi?id=185100=edit pspp created document libreoffice writer dont open odt document in linux bullseye 11. The writer is running and only its title bar appears and nothing else. No document is opened. document was created by pspp. I have opened many other odt pspp-saved documents from writer normally. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153363] FILEOPEN on mail attachments gives an invisible alert
https://bugs.documentfoundation.org/show_bug.cgi?id=153363 Michael Poisson 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 153363] New: FILEOPEN on mail attachments gives an invisible alert
https://bugs.documentfoundation.org/show_bug.cgi?id=153363 Bug ID: 153363 Summary: FILEOPEN on mail attachments gives an invisible alert Product: LibreOffice Version: unspecified Hardware: ARM OS: macOS (All) Status: UNCONFIRMED Severity: normal Priority: medium Component: Calc Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: mikedaf...@mpoisson.fr Created attachment 185099 --> https://bugs.documentfoundation.org/attachment.cgi?id=185099=edit Example of Alert window when problem occurs OS is MAC OS Monterey version 12.5.1 Libre Office is version 7.2.7.2 Context : Libre Office running with at least one file open and window displayed. Trigger: DoubleClick on a mail attachment .ods file results in a fullscreen empty window.` Actually a 'file lock cannot be created Alert' is raised BEHIND the empty window (see attachment). The Alert is normal and to be expected as attachments are held in protected directories. The fact that it stays behind is not, however. The empty window cannot be closed with close button at top left because it is waiting for the alert to be responded Workaround : use the minimise button instead of close... Solution: force Alert window to front. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153344] The size of icons in the status bar should be increased to at least 16px and the height of the status bar adjusted to allow this.
https://bugs.documentfoundation.org/show_bug.cgi?id=153344 --- Comment #4 from John Mills --- Sorry, I should say the photo compares, Writer, Word and TextMaker. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-ux-advise] [Bug 153344] The size of icons in the status bar should be increased to at least 16px and the height of the status bar adjusted to allow this.
https://bugs.documentfoundation.org/show_bug.cgi?id=153344 --- Comment #4 from John Mills --- Sorry, I should say the photo compares, Writer, Word and TextMaker. -- You are receiving this mail because: You are on the CC list for the bug.
[Libreoffice-bugs] [Bug 153344] The size of icons in the status bar should be increased to at least 16px and the height of the status bar adjusted to allow this.
https://bugs.documentfoundation.org/show_bug.cgi?id=153344 John Mills changed: What|Removed |Added Attachment #185098|Comparison of Status bar|Comparison of Status bar description|Icons, LibreOffice, |Icons, LibreOffice, |MicrosoftOffice 365,|MicrosoftOffice 365, |Kingsoft Office 2021|Softmaker Office 2021 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-ux-advise] [Bug 153344] The size of icons in the status bar should be increased to at least 16px and the height of the status bar adjusted to allow this.
https://bugs.documentfoundation.org/show_bug.cgi?id=153344 John Mills changed: What|Removed |Added Attachment #185098|Comparison of Status bar|Comparison of Status bar description|Icons, LibreOffice, |Icons, LibreOffice, |MicrosoftOffice 365,|MicrosoftOffice 365, |Kingsoft Office 2021|Softmaker Office 2021 -- You are receiving this mail because: You are on the CC list for the bug.
[Libreoffice-ux-advise] [Bug 153344] The size of icons in the status bar should be increased to at least 16px and the height of the status bar adjusted to allow this.
https://bugs.documentfoundation.org/show_bug.cgi?id=153344 --- Comment #3 from John Mills --- This shows the difference by default of the icons in LibreOffice, Microsoft Office and Kingsoft Office. Notice how much smaller the icons are in LibreOffice compared to the other two. >From Top to bottom: LibreOffice Microsoft Office Softmaker Office -- You are receiving this mail because: You are on the CC list for the bug.
[Libreoffice-bugs] [Bug 153344] The size of icons in the status bar should be increased to at least 16px and the height of the status bar adjusted to allow this.
https://bugs.documentfoundation.org/show_bug.cgi?id=153344 --- Comment #3 from John Mills --- This shows the difference by default of the icons in LibreOffice, Microsoft Office and Kingsoft Office. Notice how much smaller the icons are in LibreOffice compared to the other two. >From Top to bottom: LibreOffice Microsoft Office Softmaker Office -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-ux-advise] [Bug 153344] The size of icons in the status bar should be increased to at least 16px and the height of the status bar adjusted to allow this.
https://bugs.documentfoundation.org/show_bug.cgi?id=153344 --- Comment #2 from John Mills --- Created attachment 185098 --> https://bugs.documentfoundation.org/attachment.cgi?id=185098=edit Comparison of Status bar Icons, LibreOffice, MicrosoftOffice 365, Kingsoft Office 2021 -- You are receiving this mail because: You are on the CC list for the bug.
[Libreoffice-bugs] [Bug 153344] The size of icons in the status bar should be increased to at least 16px and the height of the status bar adjusted to allow this.
https://bugs.documentfoundation.org/show_bug.cgi?id=153344 --- Comment #2 from John Mills --- Created attachment 185098 --> https://bugs.documentfoundation.org/attachment.cgi?id=185098=edit Comparison of Status bar Icons, LibreOffice, MicrosoftOffice 365, Kingsoft Office 2021 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-commits] core.git: Branch 'distro/collabora/co-23.05' - 14 commits - cui/uiconfig helpcontent2 include/svl oox/qa oox/source sc/source svl/source sw/source ucb/source vcl/qt5 vcl/source v
cui/uiconfig/ui/qrcodegen.ui |1
helpcontent2 |2
include/svl/zformat.hxx |3
oox/qa/unit/data/tdf153258_VML_import_WordArt_detection.docx |binary
oox/qa/unit/vml.cxx | 18
oox/source/vml/vmlshape.cxx |7
sc/source/ui/app/inputwin.cxx|9
sc/source/ui/inc/inputwin.hxx|2
svl/source/numbers/zforlist.cxx | 85 -
svl/source/numbers/zformat.cxx | 20
sw/source/core/doc/docedt.cxx|4
sw/source/core/unocore/unosrch.cxx | 18
sw/source/filter/ww8/docxattributeoutput.cxx | 17
sw/source/uibase/inc/conttree.hxx|5
sw/source/uibase/utlui/content.cxx | 670 +--
ucb/source/ucp/webdav-curl/CurlSession.cxx | 24
ucb/source/ucp/webdav-curl/DAVException.hxx |1
vcl/qt5/QtGraphics_Controls.cxx |1
vcl/source/control/PriorityMergedHBox.cxx|6
vcl/unx/gtk3/gtkframe.cxx| 10
vcl/win/window/salframe.cxx |4
21 files changed, 510 insertions(+), 397 deletions(-)
New commits:
commit ae928386ece4708236038f0d14f0870c4ef01bf6
Author: Laurent Balland
AuthorDate: Mon Jan 2 18:39:35 2023 +0100
Commit: Andras Timar
CommitDate: Fri Feb 3 23:33:12 2023 +0100
tdf#152722 Number Format: keep NatNum modifiers
When modifying number format with UI (decimal places, negative in red...)
NatNum modifiers must be preserved
Implement an helper to get NatNum string
As NatNum12 already inserts currency unit, do not treat it
Change-Id: I38be1da08a44d75ef663eaf50fccb3820ff9ed5e
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/144963
Tested-by: Jenkins
Reviewed-by: Eike Rathke
(cherry picked from commit 8ba7657a9653f8ae5d1b865356d11138df7b2093)
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/146406
diff --git a/include/svl/zformat.hxx b/include/svl/zformat.hxx
index 43f6ad9775f4..ea08234e93a2 100644
--- a/include/svl/zformat.hxx
+++ b/include/svl/zformat.hxx
@@ -459,6 +459,9 @@ public:
void GetNatNumXml(
css::i18n::NativeNumberXmlAttributes2& rAttr,
sal_uInt16 nNumFor ) const;
+/** Return empty string if no NatNum modifier or unvalid nNumFor
+otherwhise return "[NatNum1]" or "[NatNum12 ...]" */
+OUString GetNatNumModifierString( sal_uInt16 nNumFor = 0 ) const;
/** Switches to the first non-"gregorian" calendar, but only if the current
calendar is "gregorian"; original calendar name and date/time returned,
diff --git a/svl/source/numbers/zforlist.cxx b/svl/source/numbers/zforlist.cxx
index cee75fc9265e..ca8b6524b9e2 100644
--- a/svl/source/numbers/zforlist.cxx
+++ b/svl/source/numbers/zforlist.cxx
@@ -3231,6 +3231,15 @@ OUString SvNumberFormatter::GenerateFormat(sal_uInt32
nIndex,
sString.append(GetNumDecimalSep());
padToLength(sString, sString.getLength() + nPrecision, '0');
}
+
+// Native Number
+const OUString sPosNatNumModifier = pFormat ?
pFormat->GetNatNumModifierString( 0 ) : "";
+const OUString sNegNatNumModifier = pFormat ?
+// if a negative format already exists, use its NatNum modifier
+// else use NatNum modifier of positive format
+( pFormat->GetNumForString( 1, 0 ) ?
pFormat->GetNatNumModifierString( 1 ) : sPosNatNumModifier )
+: "";
+
if (eType == SvNumFormatType::PERCENT)
{
sString.append( pFormat->GetPercentString() );
@@ -3254,50 +3263,62 @@ OUString SvNumberFormatter::GenerateFormat(sal_uInt32
nIndex,
OUString aCurr;
const NfCurrencyEntry* pEntry;
bool bBank;
-if ( GetNewCurrencySymbolString( nIndex, aCurr, , ) )
+bool isPosNatNum12 = sPosNatNumModifier.startsWith( "[NatNum12" );
+bool isNegNatNum12 = sNegNatNumModifier.startsWith( "[NatNum12" );
+if ( !isPosNatNum12 || !isNegNatNum12 )
{
-if ( pEntry )
+if ( GetNewCurrencySymbolString( nIndex, aCurr, , ) )
{
-sal_uInt16 nPosiForm =
NfCurrencyEntry::GetEffectivePositiveFormat(
-xLocaleData->getCurrPositiveFormat(),
-pEntry->GetPositiveFormat(), bBank );
-sal_uInt16 nNegaForm =
NfCurrencyEntry::GetEffectiveNegativeFormat(
-xLocaleData->getCurrNegativeFormat(),
-pEntry->GetNegativeFormat(), bBank );
-pEntry->CompletePositiveFormatString(
[Libreoffice-commits] core.git: Branch 'distro/collabora/co-23.05' - 2 commits - sw/qa sw/source writerfilter/qa
sw/qa/extras/ooxmlexport/ooxmlexport17.cxx |4 ++--
sw/source/core/doc/textboxhelper.cxx |1 -
sw/source/filter/ww8/docxattributeoutput.cxx |4 +++-
writerfilter/qa/cppunittests/dmapper/SdtHelper.cxx |2 +-
writerfilter/qa/cppunittests/dmapper/data/sdt-run-rich-text.docx |binary
5 files changed, 6 insertions(+), 5 deletions(-)
New commits:
commit 69a2c20b65347341f85e1d24c9de84b3b7e53089
Author: Mike Kaganski
AuthorDate: Tue Jan 31 11:57:38 2023 +0300
Commit: Andras Timar
CommitDate: Fri Feb 3 23:30:52 2023 +0100
tdf#153289: remove problematic assertion
It is unclear what it should guarantee; but at least when ungrouping,
SwDoc::UnGroupSelection copy-constructs a shared pointer (increasing
the refcount), then a copy-constructed argument passed to
lcl_CollectTextBoxesForSubGroupObj increases it once again, and then
the assertion expectedly fails.
Change-Id: I0cb5f303c67b2dc67d5583a9eb03fe405af3573d
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/146377
Tested-by: Jenkins
Reviewed-by: Mike Kaganski
diff --git a/sw/source/core/doc/textboxhelper.cxx
b/sw/source/core/doc/textboxhelper.cxx
index f253502e56a6..98fc0512acfd 100644
--- a/sw/source/core/doc/textboxhelper.cxx
+++ b/sw/source/core/doc/textboxhelper.cxx
@@ -1795,7 +1795,6 @@ SwFrameFormat* SwTextBoxNode::GetTextBox(const SdrObject*
pDrawObject) const
if (size_t(pTextBoxes.use_count()) != pTextBoxes->GetTextBoxCount() +
size_t(1))
{
SAL_WARN("sw.core", "SwTextBoxNode::GetTextBox(): RefCount and
TexBox count mismatch!");
-assert(false);
}
}
commit 82a937df8142da69f652e47c183b5dff1f82bc35
Author: Justin Luth
AuthorDate: Wed Jan 25 16:29:55 2023 -0500
Commit: Andras Timar
CommitDate: Fri Feb 3 23:30:33 2023 +0100
tdf#151548 sw content controls: preserve tabIndex val="-1"
Either we have to read sal_uInt32
(which I can't figure out how to do)
or else we have to write it out as sal_Int32.
Microsoft isn't much help here because their documentation
does not give any example of a non-tabsltop,
and one errata document indicates that MS Word
simply ignores tabIndex altogether for Sdt (and ffData).
According to the documentation,
tabIndex is a CT_UnsignedDecimalNumber
which we do not have in our model.xml
so it was defined as being a CT_DecimalNumber
which works fine for reading something human sensible like -1.
However, in our exporting we were exporting a sal_uInt32
which creates large, all positive numbers
which were not being read on import.
Nothing I tried worked to read these large numbers.
Perhaps it is even illegal to do so in MS formats?
Since it doesn't seem to matter to MS Word,
and for a human it is easier to understand -1,
and it is easier to solve in export than import,
I'm taking the easy road.
Change-Id: I6b296703c9a37149d9e11f29901e6db32bd041b7
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/146149
Tested-by: Jenkins
Reviewed-by: Justin Luth
Reviewed-by: Miklos Vajna
diff --git a/sw/qa/extras/ooxmlexport/ooxmlexport17.cxx
b/sw/qa/extras/ooxmlexport/ooxmlexport17.cxx
index a04a7813f9c6..bfc09d934343 100644
--- a/sw/qa/extras/ooxmlexport/ooxmlexport17.cxx
+++ b/sw/qa/extras/ooxmlexport/ooxmlexport17.cxx
@@ -426,7 +426,7 @@ CPPUNIT_TEST_FIXTURE(Test, testDateContentControlExport)
xContentControlProps->setPropertyValue("Alias",
uno::Any(OUString("myalias")));
xContentControlProps->setPropertyValue("Tag", uno::Any(OUString("mytag")));
xContentControlProps->setPropertyValue("Id",
uno::Any(static_cast(123)));
-xContentControlProps->setPropertyValue("TabIndex",
uno::Any(sal_uInt32(2)));
+xContentControlProps->setPropertyValue("TabIndex",
uno::Any(sal_uInt32(4294967295))); // -1
xContentControlProps->setPropertyValue("Lock",
uno::Any(OUString("sdtLocked")));
xText->insertTextContent(xCursor, xContentControl, /*bAbsorb=*/true);
@@ -453,7 +453,7 @@ CPPUNIT_TEST_FIXTURE(Test, testDateContentControlExport)
assertXPath(pXmlDoc, "//w:sdt/w:sdtPr/w:alias", "val", "myalias");
assertXPath(pXmlDoc, "//w:sdt/w:sdtPr/w:tag", "val", "mytag");
assertXPath(pXmlDoc, "//w:sdt/w:sdtPr/w:id", "val", "123");
-assertXPath(pXmlDoc, "//w:sdt/w:sdtPr/w:tabIndex", "val", "2");
+assertXPath(pXmlDoc, "//w:sdt/w:sdtPr/w:tabIndex", "val", "-1");
assertXPath(pXmlDoc, "//w:sdt/w:sdtPr/w:lock", "val", "sdtLocked");
}
diff --git a/sw/source/filter/ww8/docxattributeoutput.cxx
b/sw/source/filter/ww8/docxattributeoutput.cxx
index 03b73dbaee84..b361e5b171a0 100644
--- a/sw/source/filter/ww8/docxattributeoutput.cxx
+++ b/sw/source/filter/ww8/docxattributeoutput.cxx
@@ -2441,8 +2441,10 @@ void DocxAttributeOutput::WriteContentControlStart()
[Libreoffice-commits] core.git: Branch 'distro/collabora/co-23.05' - svx/source
svx/source/sidebar/area/AreaPropertyPanelBase.cxx |3 +--
1 file changed, 1 insertion(+), 2 deletions(-)
New commits:
commit 1aa01d562118a78a3e183e35a619b5fe1a9268cf
Author: Gülşah Köse
AuthorDate: Thu Jan 19 18:10:11 2023 +0300
Commit: Andras Timar
CommitDate: Fri Feb 3 23:29:39 2023 +0100
Hide fill Attribute widget if fill style is none
When Fill style is none we can not use fill attribute element. So It is
better to hide.
Change-Id: I88d5e49448040b3afa18fbf66377d254716e7415
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/145817
Tested-by: Jenkins
Tested-by: Pedro Silva
Reviewed-by: Pedro Silva
Reviewed-by: Mike Kaganski
diff --git a/svx/source/sidebar/area/AreaPropertyPanelBase.cxx
b/svx/source/sidebar/area/AreaPropertyPanelBase.cxx
index 996026d1fa6c..220e3f04b829 100644
--- a/svx/source/sidebar/area/AreaPropertyPanelBase.cxx
+++ b/svx/source/sidebar/area/AreaPropertyPanelBase.cxx
@@ -876,8 +876,7 @@ void AreaPropertyPanelBase::updateFillStyle(bool bDisabled,
bool bDefaultOrSet,
default:
case drawing::FillStyle_NONE:
{
-mxLbFillAttr->set_active(-1);
-mxLbFillAttr->set_sensitive(false);
+mxLbFillAttr->hide();
// "Use slide background" also uses FillStyle_NONE internally,
// don't switch listbox in that case (will be handled by
updateFillUseBackground)
nPos = meLastXFS == USE_BACKGROUND ? USE_BACKGROUND : NONE;
[Libreoffice-commits] core.git: Branch 'distro/collabora/co-23.05' - 5 commits - cui/inc cui/source cui/uiconfig sc/source vcl/jsdialog vcl/source
cui/inc/widgettestdlg.hxx|4
cui/source/dialogs/widgettestdlg.cxx | 26
cui/uiconfig/ui/widgettestdialog.ui | 200 +++
sc/source/ui/view/gridwin4.cxx |9 -
vcl/jsdialog/jsdialogbuilder.cxx |3
vcl/source/treelist/svtabbx.cxx | 17 ++
6 files changed, 230 insertions(+), 29 deletions(-)
New commits:
commit c10d9d194aec6f9c038f22862d2a61028d27e80e
Author: Szymon Kłos
AuthorDate: Tue Jan 10 10:56:18 2023 +0100
Commit: Andras Timar
CommitDate: Fri Feb 3 23:07:48 2023 +0100
lok: adjust paint rect for in-place editing
This allows to send correct cursor position (at the very end
of the cell) when typing numbers in LOK mode.
This fixes regression from:
commit 9257486636dfe95b73e5690462ba6e8408a12166
lok: sc: render expanded EditEngine when editing in-place
Change-Id: I1f6c7ce3de7a2ba7ccbd4f9f9becd49e352cf05e
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/145260
Tested-by: Jenkins CollaboraOffice
Reviewed-by: Andras Timar
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/145769
Tested-by: Jenkins
Reviewed-by: Szymon Kłos
diff --git a/sc/source/ui/view/gridwin4.cxx b/sc/source/ui/view/gridwin4.cxx
index 07265d4cf23e..5b41a6227b54 100644
--- a/sc/source/ui/view/gridwin4.cxx
+++ b/sc/source/ui/view/gridwin4.cxx
@@ -1176,7 +1176,9 @@ void ScGridWindow::DrawContent(OutputDevice ,
const ScTableInfo& rTableI
// Get top-left offset because of margin and
indent.
lcl_GetEditAreaTLOffset(nOffsetX, nOffsetY,
ScAddress(nCol1, nRow1, nTab), mrViewData, rDoc);
aEditRect.AdjustLeft(nOffsetX + 1);
+aEditRect.AdjustRight(1);
aEditRect.AdjustTop(nOffsetY + 1);
+aEditRect.AdjustBottom(1);
// EditView has an 'output area' which is used to
clip the 'paint area' we provide below.
// So they need to be in the same
coordinates/units. This is tied to the mapmode of the gridwin
@@ -1308,13 +1310,6 @@ void ScGridWindow::DrawContent(OutputDevice ,
const ScTableInfo& rTableI
// paint the editeng text
if (bIsTiledRendering)
{
-tools::Rectangle aEditRect(aBackground);
-tools::Long nOffsetX = 0, nOffsetY = 0;
-// Get top-left offset because of margin and indent.
-lcl_GetEditAreaTLOffset(nOffsetX, nOffsetY, ScAddress(nCol1,
nRow1, mrViewData.GetTabNo()), mrViewData, rDoc);
-aEditRect.AdjustLeft(nOffsetX + 1);
-aEditRect.AdjustTop(nOffsetY + 1);
-
// EditView has an 'output area' which is used to clip the paint
area we provide below.
// So they need to be in the same coordinates/units. This is tied
to the mapmode of the gridwin
// attached to the EditView, so we have to change its mapmode too
(temporarily). We save the
commit e68742c703fb76bede14d8c93d1f21967bf2d770
Author: Szymon Kłos
AuthorDate: Wed Jan 4 15:28:34 2023 +0100
Commit: Andras Timar
CommitDate: Fri Feb 3 23:06:49 2023 +0100
jsdialog: don't export collapsed/expanded icons when empty
Change-Id: Iec56c11fdba066f9b62b2d5d56ad011a821e4087
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/145040
Tested-by: Jenkins CollaboraOffice
Reviewed-by: Szymon Kłos
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/145066
Tested-by: Jenkins
diff --git a/vcl/source/treelist/svtabbx.cxx b/vcl/source/treelist/svtabbx.cxx
index f766cde70559..9ef0e145ed6d 100644
--- a/vcl/source/treelist/svtabbx.cxx
+++ b/vcl/source/treelist/svtabbx.cxx
@@ -75,9 +75,16 @@ static void lcl_DumpEntryAndSiblings(tools::JsonWriter&
rJsonWriter,
const SvLBoxContextBmp* pBmpItem = dynamic_cast();
if (pBmpItem)
{
-auto aColumn = rJsonWriter.startStruct();
-rJsonWriter.put("collapsed",
pBmpItem->GetBitmap1().GetStock());
-rJsonWriter.put("expanded",
pBmpItem->GetBitmap2().GetStock());
+const OUString& rCollapsed =
pBmpItem->GetBitmap1().GetStock();
+const OUString& rExpanded =
pBmpItem->GetBitmap2().GetStock();
+if (!rCollapsed.trim().isEmpty() ||
!rExpanded.trim().isEmpty())
+{
+auto aColumn = rJsonWriter.startStruct();
+if (!rCollapsed.trim().isEmpty())
+rJsonWriter.put("collapsed", rCollapsed);
+if (!rExpanded.trim().isEmpty())
+rJsonWriter.put("expanded", rExpanded);
+}
}
}
}
[Libreoffice-bugs] [Bug 153360] Languagetool 7.4 not working with languages different from default language (Languagetool installed from Preferences)
https://bugs.documentfoundation.org/show_bug.cgi?id=153360 --- Comment #2 from m.a.riosv --- Maybe in Mac, Menu/Edit/Preferences -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153360] Languagetool 7.4 not working with languages different from default language (Languagetool installed from Preferences)
https://bugs.documentfoundation.org/show_bug.cgi?id=153360 m.a.riosv changed: What|Removed |Added Status|UNCONFIRMED |NEEDINFO CC||miguelangelrv@libreoffice.o ||rg Ever confirmed|0 |1 --- Comment #1 from m.a.riosv --- It works for me, except for a few single words, like 'lkjafljks'. Version: 7.4.5.1 (x64) / LibreOffice Community Build ID: 9c0871452b3918c1019dde9bfac75448afc4b57f CPU threads: 4; OS: Windows 10.0 Build 19045; UI render: Skia/Raster; VCL: win Locale: es-ES (es_ES); UI: en-US Calc: threaded and Version: 7.5.0.3 (X86_64) / LibreOffice Community Build ID: c21113d003cd3efa8c53188764377a8272d9d6de CPU threads: 4; OS: Windows 10.0 Build 19045; UI render: Skia/Raster; VCL: win Locale: es-ES (es_ES); UI: en-US Calc: CL threaded Please test if you have the languages available with options enable, Menu/Tools/Options/Language Settings/Writing Aids - Available Language Modules - Edit -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-commits] core.git: Branch 'distro/collabora/co-23.05' - sw/source
sw/source/uibase/shells/translatehelper.cxx |9 -
1 file changed, 8 insertions(+), 1 deletion(-)
New commits:
commit a6b3eb3fbcccdc4873f10c946313f12712b3b231
Author: Szymon Kłos
AuthorDate: Wed Nov 30 17:53:34 2022 +0100
Commit: Andras Timar
CommitDate: Fri Feb 3 21:59:42 2023 +0100
deepl: don't introduce new bullets
Used HTML should be free from new line characters and also
marks so we don't generate new lines.
Change-Id: I02b8f9a9af9f93e8d90a7f4a22ea02c8e1f47651
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/143507
Tested-by: Jenkins CollaboraOffice
Reviewed-by: Andras Timar
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/144948
Tested-by: Jenkins
Reviewed-by: Szymon Kłos
diff --git a/sw/source/uibase/shells/translatehelper.cxx
b/sw/source/uibase/shells/translatehelper.cxx
index 8933d22db27f..507c2812a675 100644
--- a/sw/source/uibase/shells/translatehelper.cxx
+++ b/sw/source/uibase/shells/translatehelper.cxx
@@ -45,7 +45,7 @@ OString ExportPaMToHTML(SwPaM* pCursor, bool bReplacePTag)
SolarMutexGuard gMutex;
OString aResult;
WriterRef xWrt;
-GetHTMLWriter(u"NoLineLimit,SkipHeaderFooter", OUString(), xWrt);
+GetHTMLWriter(u"NoLineLimit,SkipHeaderFooter,NoPrettyPrint", OUString(),
xWrt);
if (pCursor != nullptr)
{
SvMemoryStream aMemoryStream;
@@ -63,6 +63,13 @@ OString ExportPaMToHTML(SwPaM* pCursor, bool bReplacePTag)
aResult = aResult.replaceAll("", "");
}
+
+// HTML has for that and also does new line
+aResult = aResult.replaceAll("", "");
+aResult = aResult.replaceAll("", "");
+aResult = aResult.replaceAll("", "");
+aResult = aResult.replaceAll("", "");
+aResult = aResult.replaceAll("\n", "").trim();
return aResult;
}
return {};
[Libreoffice-bugs] [Bug 142018] [EMF] Few Arcs with different pens: wrong line width for the 3rd arc
https://bugs.documentfoundation.org/show_bug.cgi?id=142018 Bartosz changed: What|Removed |Added Assignee|libreoffice-b...@lists.free |gan...@poczta.onet.pl |desktop.org | -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153355] Merging vertically adjacent cells turns a formula into data if the formula is the lower cell in the merge
https://bugs.documentfoundation.org/show_bug.cgi?id=153355 m.a.riosv changed: What|Removed |Added CC||miguelangelrv@libreoffice.o ||rg Status|UNCONFIRMED |NEW Ever confirmed|0 |1 --- Comment #3 from m.a.riosv --- Reproducible, the problem occurs by merging the cells vertically, not horizontally. Version: 7.5.0.3 (X86_64) / LibreOffice Community Build ID: c21113d003cd3efa8c53188764377a8272d9d6de CPU threads: 4; OS: Windows 10.0 Build 19045; UI render: Skia/Raster; VCL: win Locale: es-ES (es_ES); UI: en-US Calc: CL threaded -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153349] Missing Write lines
https://bugs.documentfoundation.org/show_bug.cgi?id=153349 m.a.riosv changed: What|Removed |Added Ever confirmed|0 |1 CC||miguelangelrv@libreoffice.o ||rg Status|UNCONFIRMED |NEEDINFO --- Comment #1 from m.a.riosv --- Please attach a sample file. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153297] A complex formula does not work in Calc 7.4.x; (MATCH function)
https://bugs.documentfoundation.org/show_bug.cgi?id=153297 m.a.riosv changed: What|Removed |Added Keywords||regression Severity|normal |critical -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-commits] core.git: Branch 'libreoffice-7-5' - cui/uiconfig sd/uiconfig sw/uiconfig
cui/uiconfig/ui/langtoolconfigpage.ui| 148 +++ cui/uiconfig/ui/optdeeplpage.ui | 82 + sd/uiconfig/simpress/ui/pmsummarypage.ui |1 sw/uiconfig/swriter/ui/numberinput.ui|1 4 files changed, 120 insertions(+), 112 deletions(-) New commits: commit cdd3af2364ebe9f8d2a23266a62be2597022f255 Author: Caolán McNamara AuthorDate: Thu Feb 2 11:54:27 2023 + Commit: Adolfo Jayme Barrientos CommitDate: Fri Feb 3 21:14:48 2023 + resave with latest glade Change-Id: I747aabe874474151b52127840cf6235448c82a8a Reviewed-on: https://gerrit.libreoffice.org/c/core/+/146498 Tested-by: Jenkins Reviewed-by: Adolfo Jayme Barrientos diff --git a/cui/uiconfig/ui/langtoolconfigpage.ui b/cui/uiconfig/ui/langtoolconfigpage.ui index 38aa184c2469..8be8c1c2359a 100644 --- a/cui/uiconfig/ui/langtoolconfigpage.ui +++ b/cui/uiconfig/ui/langtoolconfigpage.ui @@ -1,202 +1,204 @@ - + True -False -6 +False +6 12 True -False -0 -none +False +0 +none + True -False +False True True True -False +False start -6 -4 +6 +4 If you enable this, the data will be sent to an external server. True -0 -0 +0 +0 Please read the privacy policy True -True -True +True +True start start none https://languagetool.org/legal/privacy -0 -1 +0 +1 Enable LanguageTool True -True -False +True +False start -6 -9 -True +6 +9 +True -0 -2 +0 +2 -False -10 -0 -none +False +10 +0 +none + True -False -5 -12 +False +5 +12 True -False +False start Base URL: -True -baseurl +True +baseurl -0 -0 +0 +0 True -True -True +True True +True -1 -0 +1 +0 True -False +False start Username: -True -username +True +username -0 -2 +0 +2 True -False +False start API key: -True -apikey +True +apikey -0 -4 +
[Libreoffice-commits] core.git: Branch 'distro/collabora/co-23.05' - sfx2/source
sfx2/source/view/lokhelper.cxx |2 ++
1 file changed, 2 insertions(+)
New commits:
commit ede43e54ed7f89a20906ae84d9447eeb3412bc7f
Author: Aron Budea
AuthorDate: Thu Jan 26 03:31:24 2023 +0100
Commit: Andras Timar
CommitDate: Fri Feb 3 21:55:40 2023 +0100
sfx2: fix crash in SfxLokHelper::notifyAllViews(...)
Crashreport signature:
program/libmergedlo.so
SfxLokHelper::notifyAllViews(int, rtl::OString const&)
sfx2/source/view/lokhelper.cxx:682
program/libmergedlo.so
SfxClipboardChangeListener::ChangedContents()
include/rtl/string.hxx:413
program/libmergedlo.so
SfxClipboardChangeListener::LinkStubAsyncExecuteHdl_Impl(void*,
void*)
include/rtl/ref.hxx:128
program/libmergedlo.so
ImplWindowFrameProc(vcl::Window*, SalEvent, void const*)
include/rtl/ref.hxx:128
program/libmergedlo.so
SvpSalInstance::ProcessEvent(SalUserEventList::SalUserEvent)
Change-Id: Ibf70f42292d67a3d6cc68f579ee02f671da85acb
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/146150
Reviewed-by: Miklos Vajna
Tested-by: Jenkins CollaboraOffice
(cherry picked from commit dc17158c99c8a15fbca57a9a0b0ea7178dcc5a34)
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/146400
Tested-by: Jenkins
Reviewed-by: Aron Budea
diff --git a/sfx2/source/view/lokhelper.cxx b/sfx2/source/view/lokhelper.cxx
index 53c2abace8b5..29f64adbb74b 100644
--- a/sfx2/source/view/lokhelper.cxx
+++ b/sfx2/source/view/lokhelper.cxx
@@ -676,6 +676,8 @@ void SfxLokHelper::notifyAllViews(int nType, const OString&
rPayload)
const auto payload = rPayload.getStr();
const SfxViewShell* const pCurrentViewShell = SfxViewShell::Current();
+if (!pCurrentViewShell)
+return;
SfxViewShell* pViewShell = SfxViewShell::GetFirst();
while (pViewShell)
{
[Libreoffice-commits] core.git: Branch 'distro/collabora/co-23.05' - 2 commits - vcl/source
vcl/source/window/window2.cxx | 14 +++---
1 file changed, 11 insertions(+), 3 deletions(-)
New commits:
commit 22297965a0b8c94ad7f2173f22f91ee00ad4698e
Author: Aron Budea
AuthorDate: Thu Feb 2 00:08:41 2023 +0100
Commit: Andras Timar
CommitDate: Fri Feb 3 21:55:10 2023 +0100
vcl: fix online crash in vcl::Window::IsTracking()
Crashreport signature:
program/libmergedlo.so
vcl::Window::IsTracking() const
vcl/source/window/window2.cxx:340
program/libmergedlo.so
(anonymous namespace)::LOKPostAsyncEvent(void*, void*)
sfx2/source/view/lokhelper.cxx:812
program/libmergedlo.so
LokChartHelper::postMouseEvent(int, int, int, int, int, int,
double, double)
include/rtl/ref.hxx:128
program/libmergedlo.so
SfxLokHelper::testInPlaceComponentMouseEventHit(SfxViewShell*, int,
int, int, int, int, int, double, double, bool)
sfx2/source/view/lokhelper.cxx:980
/program/libswlo.so
SwXTextDocument::postMouseEvent(int, int, int, int, int, int)
sw/source/uibase/uno/unotxdoc.cxx:3663
program/libmergedlo.so
doc_postMouseEvent
desktop/source/lib/init.cxx:4831
Change-Id: Iab7d24a901e57dc8af3fb2c77fbea3b4fdad9fb9
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/146483
Tested-by: Jenkins CollaboraOffice
Reviewed-by: Miklos Vajna
diff --git a/vcl/source/window/window2.cxx b/vcl/source/window/window2.cxx
index 87db8e470e21..180edf5cf961 100644
--- a/vcl/source/window/window2.cxx
+++ b/vcl/source/window/window2.cxx
@@ -341,9 +341,15 @@ bool Window::IsTracking() const
{
if (!mpWindowImpl)
return false;
-return (mpWindowImpl->mbUseFrameData ?
-mpWindowImpl->mpFrameData->mpTrackWin == this :
-ImplGetSVData()->mpWinData->mpTrackWin == this);
+if (mpWindowImpl->mbUseFrameData && mpWindowImpl->mpFrameData)
+{
+return mpWindowImpl->mpFrameData->mpTrackWin == this;
+}
+if (!mpWindowImpl->mbUseFrameData && ImplGetSVData()->mpWinData)
+{
+return ImplGetSVData()->mpWinData->mpTrackWin == this;
+}
+return false;
}
void Window::StartAutoScroll( StartAutoScrollFlags nFlags )
commit 3239018539d0e2a5f120ef214013417cff79a572
Author: Noel Grandin
AuthorDate: Fri Jan 27 08:50:04 2023 +0200
Commit: Andras Timar
CommitDate: Fri Feb 3 21:55:10 2023 +0100
fix online crash in WIndow::IsTracking
/opt/collaboraoffice/program/libmergedlo.so
vcl::Window::IsTracking() const
/home/collabora/jenkins/workspace/build_core_co-22.05_for_online_snapshot/vcl/source/window/window2.cxx:340
/opt/collaboraoffice/program/libmergedlo.so
(anonymous namespace)::LOKPostAsyncEvent(void*, void*)
/home/collabora/jenkins/workspace/build_core_co-22.05_for_online_snapshot/sfx2/source/view/lokhelper.cxx:812
/opt/collaboraoffice/program/libmergedlo.so
LokChartHelper::postMouseEvent(int, int, int, int, int, int, double,
double)
/home/collabora/jenkins/workspace/build_core_co-22.05_for_online_snapshot/include/rtl/ref.hxx:128
Change-Id: I204bac7d8f595054abe9b6e8e631c02b26e20361
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/146231
Tested-by: Jenkins CollaboraOffice
Reviewed-by: Noel Grandin
diff --git a/vcl/source/window/window2.cxx b/vcl/source/window/window2.cxx
index 978dc0b6ecf8..87db8e470e21 100644
--- a/vcl/source/window/window2.cxx
+++ b/vcl/source/window/window2.cxx
@@ -339,6 +339,8 @@ void Window::EndTracking( TrackingEventFlags nFlags )
bool Window::IsTracking() const
{
+if (!mpWindowImpl)
+return false;
return (mpWindowImpl->mbUseFrameData ?
mpWindowImpl->mpFrameData->mpTrackWin == this :
ImplGetSVData()->mpWinData->mpTrackWin == this);
[Libreoffice-bugs] [Bug 153362] New: Dead link in ooxml-export-notes.txt
https://bugs.documentfoundation.org/show_bug.cgi?id=153362 Bug ID: 153362 Summary: Dead link in ooxml-export-notes.txt Product: LibreOffice Version: 7.6.0.0 alpha0+ Master Hardware: All URL: https://opengrok.libreoffice.org/xref/core/oox/source/ export/ooxml-export-notes.txt?r=c7008197#23 OS: All Status: UNCONFIRMED Severity: normal Priority: medium Component: LibreOffice Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: rb.hensc...@t-online.de The link [1] in line 23 of https://opengrok.libreoffice.org/xref/core/oox/source/export/ooxml-export-notes.txt?r=c7008197#23 is dead. [1] http://www.asahi-net.or.jp/~eb2m-mrt/ooxml/dependencies.html Does someone know, what kind of information it had? -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 146988] Opening at cursor position doesn't work in large documents (User Data must be entered)
https://bugs.documentfoundation.org/show_bug.cgi?id=146988 --- Comment #19 from MR Zenwiz --- This remains unfixed in LO 7.5: Version: 7.5.0.3 (X86_64) / LibreOffice Community Build ID: c21113d003cd3efa8c53188764377a8272d9d6de CPU threads: 32; OS: Linux 5.15; UI render: default; VCL: gtk3 Locale: en-US (en_US.UTF-8); UI: en-US Calc: threaded Last I saw this was supposed to be fixed in 7.5 and it is not. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 107158] [META] Notebookbar Groupedbar
https://bugs.documentfoundation.org/show_bug.cgi?id=107158 Bug 107158 depends on bug 153358, which changed state. Bug 153358 Summary: Wrong redimensioning of Groupedbar compact toolbar https://bugs.documentfoundation.org/show_bug.cgi?id=153358 What|Removed |Added Status|NEW |RESOLVED Resolution|--- |DUPLICATE -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153358] Wrong redimensioning of Groupedbar compact toolbar
https://bugs.documentfoundation.org/show_bug.cgi?id=153358 Stéphane Guillou (stragu) changed: What|Removed |Added CC||stephane.guillou@libreoffic ||e.org Resolution|--- |DUPLICATE Status|NEW |RESOLVED --- Comment #5 from Stéphane Guillou (stragu) --- I am pretty sure this is a duplicate of the regression described in bug 153078. Marking as such, but please set back to New if a master build that include bcf9e47791d5b3e1d6a75c73f3b8c9940abda8eb still reproduces it. (Stuart's version did not have that commit.) Fix will be available in 7.5.1 too. *** This bug has been marked as a duplicate of bug 153078 *** -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153317] MySQL/MariaDB direct connection: Content of field type 'Bit' isn't shown in Tools → SQL
https://bugs.documentfoundation.org/show_bug.cgi?id=153317 --- Comment #3 from jcs...@libreoffice.org --- I can reproduce this also in Windows 11 Version: 7.5.0.2 (X86_64) / LibreOffice Community Build ID: c0dd1bc3f1a385d110b88e26ece634da94921f58 CPU threads: 16; OS: Windows 10.0 Build 22621; UI render: Skia/Vulkan; VCL: win Locale: es-ES (es_ES); UI: es-ES Calc: CL threaded MariaDB 10.10 (x64) -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153229] [RFE] Please provide a user preference to disable inheriting the system UI theme
https://bugs.documentfoundation.org/show_bug.cgi?id=153229 --- Comment #17 from derei --- I've been having trouble with this behavior of LO picking from W10 theme for the past 2 or 3 releases. So, yes... Please be considerate and mindful towards the user by offering an option to select theme. Most apps have system/light/dark, so then user can decide. I prefer the light version of LO, even if i'm using the dark mode for Windows. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 75331] FILEOPEN: DOCX - floating table with text wrapping 'around' and vertical position relative to 'page' position is wrong (see Comment 15)
https://bugs.documentfoundation.org/show_bug.cgi?id=75331 --- Comment #29 from Ari Latvala --- Created attachment 185097 --> https://bugs.documentfoundation.org/attachment.cgi?id=185097=edit LO 7.5 vs Word two page view comparison -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 75331] FILEOPEN: DOCX - floating table with text wrapping 'around' and vertical position relative to 'page' position is wrong (see Comment 15)
https://bugs.documentfoundation.org/show_bug.cgi?id=75331 --- Comment #28 from Ari Latvala --- Layout of the example document still very different on LO 7.5 when compared outlook on Word. Screenshot added to the case showing both side by side. Version: 7.5.0.3 (X86_64) / LibreOffice Community Build ID: c21113d003cd3efa8c53188764377a8272d9d6de CPU threads: 8; OS: Windows 10.0 Build 19045; UI render: Skia/Raster; VCL: win Locale: fi-FI (fi_FI); UI: en-US Calc: threaded -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 75331] FILEOPEN: DOCX - floating table with text wrapping 'around' and vertical position relative to 'page' position is wrong (see Comment 15)
https://bugs.documentfoundation.org/show_bug.cgi?id=75331 --- Comment #27 from Ari Latvala --- Created attachment 185096 --> https://bugs.documentfoundation.org/attachment.cgi?id=185096=edit Layout LO 7.5 vs Word, still very wrong on LO 7.5 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153361] New: Theme color set has unsuitable lighten for background colors
https://bugs.documentfoundation.org/show_bug.cgi?id=153361 Bug ID: 153361 Summary: Theme color set has unsuitable lighten for background colors Product: LibreOffice Version: 7.6.0.0 alpha0+ Master Hardware: x86-64 (AMD64) OS: Windows (All) Status: UNCONFIRMED Severity: normal Priority: medium Component: LibreOffice Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: rb.hensc...@t-online.de Open attachment 185094 from bug 153359. The slide shows a screenshot of the theme color set in PowerPoint. The left shape uses the first from left theme color, a text color; the right shape uses the third from left theme color, a background color. Look at the light/darken values for the theme color of the right shape. PowerPoint provides the light/darken values darken 10% darken 25% darken 50% darken 75% darken 90% LibreOffice provides the light/darken values lighten 80% lighten 60% lighten 40% darken 25% darken 50% Problems: A) The theme color background colors in MS Office are light and therefore it makes no sense to lighten them even more. B) If LibreOffice uses different value than MS Office, the chosen color is not contained in the set shown to the user. [There is no problem with the colors themselves, because lighten and darken is not part of the theme but described by separate attributes. Besides ±1 off sometimes the colors are correct.] -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 94911] Autocorrect: em dash doesn't form after closing parenthesis
https://bugs.documentfoundation.org/show_bug.cgi?id=94911 --- Comment #9 from spikeo...@gmail.com --- Just started using new Writer version. This feature stopped working. I believe the troggering event was an ending quotation mark. Once the auto-em flipped off, I can't get it flipped back on! And the two -- looks very weird now, too. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153360] New: Languagetool 7.4 not working with languages different from default language (Languagetool installed from Preferences)
https://bugs.documentfoundation.org/show_bug.cgi?id=153360 Bug ID: 153360 Summary: Languagetool 7.4 not working with languages different from default language (Languagetool installed from Preferences) Product: LibreOffice Version: 7.4.4.2 release Hardware: ARM OS: macOS (All) Status: UNCONFIRMED Severity: normal Priority: medium Component: Writer Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: grass...@gmail.com Created attachment 185095 --> https://bugs.documentfoundation.org/attachment.cgi?id=185095=edit Various text showing the bug Hi, since the integration of LT in LO there is new bug which makes the use of LT in LO very difficult. When I am using strings of text in Latin, French, Italian and German within a paragraph in Spanish for ex. LT struggles to proof the text and sometimes does not specify what mistake it is underlining, sometimes it suggests corrections in Spanish. Sometimes if the text in the Foreign language starts in a new paragraph the bug is gone, others it persists (such as in the case of Latin tex). Version: 7.4.4.2 / LibreOffice Community Build ID: 85569322deea74ec9134968a29af2df5663baa21 CPU threads: 8; OS: Mac OS X 13.2; UI render: default; VCL: osx Locale: it-IT (en_IT.UTF-8); UI: en-US Calc: threaded -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-ux-advise] [Bug 153344] The size of icons in the status bar should be increased to at least 16px and the height of the status bar adjusted to allow this.
https://bugs.documentfoundation.org/show_bug.cgi?id=153344 V Stuart Foote changed: What|Removed |Added Keywords||needsUXEval CC||libreoffice-ux-advise@lists ||.freedesktop.org, ||vsfo...@libreoffice.org --- Comment #1 from V Stuart Foote --- The icons are of course not 10px they are 16px with padding. But, it could be helpful to provide an Icon Size option for the status bar--similar to the Tools -> Options -> View selectors for Toolbar, Notebookbar and Sidebar-- where UI responds to icons size of: Small (16px), Large (24px) or Extra Large (32px), or as scaled for HiDPI. On Large icon selection, text size should probably increase and more data elements would be hidden from view on the Status bar, continuing to use current element collapse sequence. So reasonable. -- You are receiving this mail because: You are on the CC list for the bug.
[Libreoffice-bugs] [Bug 153344] The size of icons in the status bar should be increased to at least 16px and the height of the status bar adjusted to allow this.
https://bugs.documentfoundation.org/show_bug.cgi?id=153344 V Stuart Foote changed: What|Removed |Added Keywords||needsUXEval CC||libreoffice-ux-advise@lists ||.freedesktop.org, ||vsfo...@libreoffice.org --- Comment #1 from V Stuart Foote --- The icons are of course not 10px they are 16px with padding. But, it could be helpful to provide an Icon Size option for the status bar--similar to the Tools -> Options -> View selectors for Toolbar, Notebookbar and Sidebar-- where UI responds to icons size of: Small (16px), Large (24px) or Extra Large (32px), or as scaled for HiDPI. On Large icon selection, text size should probably increase and more data elements would be hidden from view on the Status bar, continuing to use current element collapse sequence. So reasonable. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153359] New: Theme color UI mess with background <-> text labels
https://bugs.documentfoundation.org/show_bug.cgi?id=153359 Bug ID: 153359 Summary: Theme color UI mess with background <-> text labels Product: LibreOffice Version: 7.6.0.0 alpha0+ Master Hardware: All OS: All Status: UNCONFIRMED Severity: normal Priority: medium Component: LibreOffice Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: rb.hensc...@t-online.de Created attachment 185094 --> https://bugs.documentfoundation.org/attachment.cgi?id=185094=edit Shapes using theme colors Open attached file. It contains two shapes. The text in the shape is a quote of the label I see in PowerPoint. Now go to the area fill dialog and look at the labels you get in LibreOffice. "Text 1" becomes "Background - Dark 1" "Background 2" becomes "Text - Light 2". -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 150932] FILESAVE DOCX Underlined trailing spaces not drawn
https://bugs.documentfoundation.org/show_bug.cgi?id=150932 raal changed: What|Removed |Added CC||r...@post.cz --- Comment #5 from raal --- Created attachment 185093 --> https://bugs.documentfoundation.org/attachment.cgi?id=185093=edit test file test file created in LO 7.6. This file is without underlined trailing spaces in word 2010, but with Underlined trailing spaces in office.com => looks like word's problem. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153352] Promote/Demote level list should be in the Tabbed interface
https://bugs.documentfoundation.org/show_bug.cgi?id=153352 V Stuart Foote changed: What|Removed |Added Keywords||needsUXEval CC||libreoffice-ux-advise@lists ||.freedesktop.org, ||vsfo...@libreoffice.org --- Comment #1 from V Stuart Foote --- +1, for lists in a textbox we do a layout adjustment rather than an outline adjustment now. So, would replace the Tabbed NB use of .uno:DecrementIndent .uno:IncrementIndent to instead use .uno:OutlineLeft .uno:OutlineRight to match usage in the SB Properties "Lists" panel. But do we still need the layout adjustment (e.g. for graphical bullets)? -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-ux-advise] [Bug 153352] Promote/Demote level list should be in the Tabbed interface
https://bugs.documentfoundation.org/show_bug.cgi?id=153352 V Stuart Foote changed: What|Removed |Added Keywords||needsUXEval CC||libreoffice-ux-advise@lists ||.freedesktop.org, ||vsfo...@libreoffice.org --- Comment #1 from V Stuart Foote --- +1, for lists in a textbox we do a layout adjustment rather than an outline adjustment now. So, would replace the Tabbed NB use of .uno:DecrementIndent .uno:IncrementIndent to instead use .uno:OutlineLeft .uno:OutlineRight to match usage in the SB Properties "Lists" panel. But do we still need the layout adjustment (e.g. for graphical bullets)? -- You are receiving this mail because: You are on the CC list for the bug.
[Libreoffice-bugs] [Bug 153339] Feature request: Add option to NOT round up very large numbers or any numbers
https://bugs.documentfoundation.org/show_bug.cgi?id=153339 --- Comment #2 from NRL --- Created attachment 185092 --> https://bugs.documentfoundation.org/attachment.cgi?id=185092=edit Difference between a number and text Hi, I still cannot get the number. as a number I get: 5254615415121512155 5461154115994554615 --- (206,538,700,873,042,000.00) as plain text I get: 5254615415121512155 5461154115994554615 --- -2.06538700873042E+17 In plain text I cannot increase the number of decimal places. How do I get the exact number this way? What am I doing wrong? I don't understand? I'm sorry that I'm stupid. Thanks for getting back to me so quickly. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 149728] LibreOffice 7.3.3 and above: Locally Integrated Menu (LIM) disappears with kf5 and material-decoration theme
https://bugs.documentfoundation.org/show_bug.cgi?id=149728 --- Comment #12 from rom1...@gmail.com --- This looks like a related bug in the LO flatpak repo: https://github.com/flathub/org.libreoffice.LibreOffice/issues/63 As I understand it: - appmenu doesn't work with Gtk apps under KDE+Wayland¹ in general - using the kf5 VCL backend could work around the issue (but this backend seems absent from/broken in the flatpak distribution) - (at least on my machine) the Gtk VCL backend doesn't ensure that the menu bar is displayed in-app under KDE+Wayland, which is unlike every other Gtk apps (AFAICT) Perhaps this last point could be improved upon, if LO could detect that it's running under wayland, and make sure that an in-app menu is shown in this case? ¹: https://bugs.kde.org/show_bug.cgi?id=424485 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153357] Can't Type or See Characters in New LibreOffice Writer
https://bugs.documentfoundation.org/show_bug.cgi?id=153357 Julien Nabet changed: What|Removed |Added CC||serval2...@yahoo.fr --- Comment #2 from Julien Nabet --- Some info here: https://wiki.documentfoundation.org/QA/FirstSteps -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153341] Copied HTML text which uses the alpha channel is pasted either without it (when rgb(r g b / a) notation is used) or without any color (when rgba(r, g, b, a) notation is
https://bugs.documentfoundation.org/show_bug.cgi?id=153341 Julien Nabet changed: What|Removed |Added Ever confirmed|0 |1 Status|UNCONFIRMED |ASSIGNED Assignee|libreoffice-b...@lists.free |serval2...@yahoo.fr |desktop.org | --- Comment #1 from Julien Nabet --- On pc Debian x86-64 with master sources updated today, I could reproduce this. I gave a try with https://gerrit.libreoffice.org/c/core/+/146546 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 107575] [META] Number format bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=107575 Bug 107575 depends on bug 153023, which changed state. Bug 153023 Summary: NatNum12 number format (spell out): thousand separator should be disabled https://bugs.documentfoundation.org/show_bug.cgi?id=153023 What|Removed |Added Status|ASSIGNED|RESOLVED Resolution|--- |FIXED -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-commits] core.git: cui/source include/svl include/svx sc/source svl/source svx/source
cui/source/tabpages/numfmt.cxx |3 +-
include/svl/numformat.hxx |3 ++
include/svx/numfmtsh.hxx | 27 -
sc/source/ui/sidebar/NumberFormatPropertyPanel.cxx | 26 +++-
sc/source/ui/view/formatsh.cxx |3 ++
svl/source/numbers/zforlist.cxx|7 +
svx/source/items/numfmtsh.cxx |7 +
7 files changed, 58 insertions(+), 18 deletions(-)
New commits:
commit bbd487dc26c7e37982f64f6e6159c65ac77a89f1
Author: Laurent Balland
AuthorDate: Sat Jan 14 15:48:12 2023 +0100
Commit: Eike Rathke
CommitDate: Fri Feb 3 17:57:01 2023 +
tdf#153023 Disable Thousand separator for NatNum12
Add some helper to get NatNum12 state
Modify both Number format dialog and Sidebar
Transform CAT_ defines in enum
Change-Id: Iaa3127bf07223caac60e409306a1bee2edc37428
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/145513
Tested-by: Jenkins
Reviewed-by: Eike Rathke
diff --git a/cui/source/tabpages/numfmt.cxx b/cui/source/tabpages/numfmt.cxx
index e6e669de6422..63f9d5ce91f7 100644
--- a/cui/source/tabpages/numfmt.cxx
+++ b/cui/source/tabpages/numfmt.cxx
@@ -942,7 +942,8 @@ void SvxNumberFormatTabPage::UpdateOptions_Impl( bool
bCheckCatChange /*= sal_Fa
m_xBtnNegRed->set_active( bNegRed );
if ( nCategory != CAT_SCIENTIFIC )
{
-m_xBtnThousand->set_sensitive( nCategory != CAT_TIME );
+m_xBtnThousand->set_sensitive( nCategory != CAT_TIME
+&& !pNumFmtShell->IsNatNum12(
theFormat ) );
m_xBtnThousand->set_active( bThousand && nCategory != CAT_TIME
);
}
break;
diff --git a/include/svl/numformat.hxx b/include/svl/numformat.hxx
index 6ff04837b0bb..0a374f3c3301 100644
--- a/include/svl/numformat.hxx
+++ b/include/svl/numformat.hxx
@@ -238,6 +238,9 @@ public:
/// Whether format index nFIndex is of type text or not
bool IsTextFormat(sal_uInt32 nFIndex) const;
+/// Whether format index nFIndex has NatNum12 modifier
+bool IsNatNum12(sal_uInt32 nFIndex) const;
+
/// Get additional info of a format index, e.g. for dialog box
void GetFormatSpecialInfo(sal_uInt32 nFormat, bool& bThousand, bool& IsRed,
sal_uInt16& nPrecision, sal_uInt16& nLeadingCnt);
diff --git a/include/svx/numfmtsh.hxx b/include/svx/numfmtsh.hxx
index 360a067e06c9..db593eb8b77d 100644
--- a/include/svx/numfmtsh.hxx
+++ b/include/svx/numfmtsh.hxx
@@ -38,17 +38,20 @@ enum class SvxNumberValueType
};
// sort order of the category ListBox entries in the TabPage
-#define CAT_ALL 0
-#define CAT_USERDEFINED 1
-#define CAT_NUMBER 2
-#define CAT_PERCENT 3
-#define CAT_CURRENCY4
-#define CAT_DATE5
-#define CAT_TIME6
-#define CAT_SCIENTIFIC 7
-#define CAT_FRACTION8
-#define CAT_BOOLEAN 9
-#define CAT_TEXT10
+enum SvxNumberFormatCategory
+{
+CAT_ALL = 0,
+CAT_USERDEFINED,
+CAT_NUMBER,
+CAT_PERCENT,
+CAT_CURRENCY,
+CAT_DATE,
+CAT_TIME,
+CAT_SCIENTIFIC,
+CAT_FRACTION,
+CAT_BOOLEAN,
+CAT_TEXT
+};
#define SELPOS_NONE -1
@@ -130,6 +133,8 @@ public:
sal_uInt16 GetFormatIntegerDigits( std::u16string_view rFormat )
const;
+boolIsNatNum12( std::u16string_view rFormat ) const;
+
voidMakePreviewString( const OUString& rFormatStr,
OUString& rPreviewStr,
const Color*& rpFontColor );
diff --git a/sc/source/ui/sidebar/NumberFormatPropertyPanel.cxx
b/sc/source/ui/sidebar/NumberFormatPropertyPanel.cxx
index c9910cc1db82..b2530df9838f 100644
--- a/sc/source/ui/sidebar/NumberFormatPropertyPanel.cxx
+++ b/sc/source/ui/sidebar/NumberFormatPropertyPanel.cxx
@@ -23,6 +23,7 @@
#include
#include
#include
+#include
#include
#include
@@ -185,12 +186,17 @@ void NumberFormatPropertyPanel::NotifyItemUpdate(
sal_uInt16 nVal = pItem->GetValue();
mnCategorySelected = nVal;
mxLbCategory->set_active(nVal);
-if (nVal < 8 && // General, Number, Percent, Currency, Time,
Scientific, Fraction
-nVal != 4 ) // not Date
+// There is an offset between category list enum and listbox
in side panel
+SvxNumberFormatCategory nCategory = static_cast<
SvxNumberFormatCategory >( nVal + 1 );
+if (nCategory <= CAT_FRACTION && // General, Number, Percent,
Currency, Time, Scientific, Fraction
+nCategory != CAT_DATE ) // not Date
{
-bool bIsScientific ( nVal ==
[Libreoffice-bugs] [Bug 153357] Can't Type or See Characters in New LibreOffice Writer
https://bugs.documentfoundation.org/show_bug.cgi?id=153357 V Stuart Foote changed: What|Removed |Added Ever confirmed|0 |1 CC||vsfo...@libreoffice.org Status|UNCONFIRMED |NEEDINFO --- Comment #1 from V Stuart Foote --- Please reset your user profile and retest. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 107158] [META] Notebookbar Groupedbar
https://bugs.documentfoundation.org/show_bug.cgi?id=107158 V Stuart Foote changed: What|Removed |Added Depends on||153358 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=153358 [Bug 153358] Wrong redimensioning of Groupedbar compact toolbar -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153358] Wrong redimensioning of Groupedbar compact toolbar
https://bugs.documentfoundation.org/show_bug.cgi?id=153358 V Stuart Foote changed: What|Removed |Added Status|UNCONFIRMED |NEW OS|macOS (All) |All Blocks||107158 CC||heiko.tietze@documentfounda ||tion.org, ||kain...@gmail.com, ||vsfo...@libreoffice.org Ever confirmed|0 |1 --- Comment #4 from V Stuart Foote --- Confirmed Version: 7.6.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: d8e6b488ceaff7c88856ebcfcfec14d2d8cd7652 CPU threads: 8; OS: Windows 10.0 Build 19044; UI render: Skia/Raster; VCL: win Locale: en-US (en_US); UI: en-US Calc: threaded The vcl canvas looks to be mispositioned on redraw. Screen draw overwrites the MUFFIN Groupedbar Comact UI elements aligned with the left margin of the document. I can force it to redraw the Notebook Bar simply expanding the Styles listbox which is still showing. @Heiko, Andreas can you think of who'd be able to look at this? Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=107158 [Bug 107158] [META] Notebookbar Groupedbar -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 146468] Use same border preset tooltips between toolbar and sidebar
https://bugs.documentfoundation.org/show_bug.cgi?id=146468 Radhey Parekh changed: What|Removed |Added Status|NEW |ASSIGNED -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 146468] Use same border preset tooltips between toolbar and sidebar
https://bugs.documentfoundation.org/show_bug.cgi?id=146468 --- Comment #4 from Radhey Parekh --- I would like to look into this. One doubt, till what index, do we need to assign the RID_SVXSTR to the code line? Like you have started from (0,...) then '(1,)', so till which index we need to assign this? Thanks :) -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-ux-advise] [Bug 153335] Establishing a keyboard shortcut is doubly counter-intuitive
https://bugs.documentfoundation.org/show_bug.cgi?id=153335 --- Comment #8 from V Stuart Foote --- While here a duplicate of bug 115527 (and its dupes), please note the UI function of the Customize dialog's Keyboard panel is equally to make shortcut assignments, but also to inspect assignments already in place. The listing of Keys (those available to Shortcut assign) is sequential and logically grouped. While filtering might be useful, a search against the Keys would be of limited use. Actions/Functions can be filtered by the Category a function is assigned/performs, and at the 5.4 release actions/functions can be searched by name. Where a function has an shortcut key assignment made that assignment is indicated in the lower right Keys panel following search--to help (along with the pop-up description) to identify the correct function. So in practice the Shortcut Keys panel on top makes the most sense: both to visually review existing assignments, and to select the shortcut that would be modified/assigned. -- You are receiving this mail because: You are on the CC list for the bug.
[Libreoffice-bugs] [Bug 153335] Establishing a keyboard shortcut is doubly counter-intuitive
https://bugs.documentfoundation.org/show_bug.cgi?id=153335 --- Comment #8 from V Stuart Foote --- While here a duplicate of bug 115527 (and its dupes), please note the UI function of the Customize dialog's Keyboard panel is equally to make shortcut assignments, but also to inspect assignments already in place. The listing of Keys (those available to Shortcut assign) is sequential and logically grouped. While filtering might be useful, a search against the Keys would be of limited use. Actions/Functions can be filtered by the Category a function is assigned/performs, and at the 5.4 release actions/functions can be searched by name. Where a function has an shortcut key assignment made that assignment is indicated in the lower right Keys panel following search--to help (along with the pop-up description) to identify the correct function. So in practice the Shortcut Keys panel on top makes the most sense: both to visually review existing assignments, and to select the shortcut that would be modified/assigned. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153358] Wrong redimensioning of Groupedbar compact toolbar
https://bugs.documentfoundation.org/show_bug.cgi?id=153358 --- Comment #3 from Vincent Boudry --- Created attachment 185091 --> https://bugs.documentfoundation.org/attachment.cgi?id=185091=edit Screenshot of the standard toolbar -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153358] Wrong redimensioning of Groupedbar compact toolbar
https://bugs.documentfoundation.org/show_bug.cgi?id=153358 --- Comment #2 from Vincent Boudry --- Created attachment 185090 --> https://bugs.documentfoundation.org/attachment.cgi?id=185090=edit Screenshot of compressed toolbar -- You are receiving this mail because: You are the assignee for the bug.
