[Libreoffice-commits] core.git: filter/qa

2022-11-11 Thread Andrea Gelmini (via logerrit)
 filter/qa/unit/svg.cxx |2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

New commits:
commit 4c5be3e2e7818367af6a67a2913c61c7456eba69
Author: Andrea Gelmini 
AuthorDate: Fri Nov 11 21:25:24 2022 +0100
Commit: Julien Nabet 
CommitDate: Sat Nov 12 08:51:04 2022 +0100

Fix typo

Change-Id: Icec4f84ba52578588512fa6cccd1d0d62b02ef06
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/142602
Tested-by: Jenkins
Reviewed-by: Julien Nabet 

diff --git a/filter/qa/unit/svg.cxx b/filter/qa/unit/svg.cxx
index ea31a74447f0..a650deb1fc72 100644
--- a/filter/qa/unit/svg.cxx
+++ b/filter/qa/unit/svg.cxx
@@ -176,7 +176,7 @@ CPPUNIT_TEST_FIXTURE(SvgFilterTest, 
testSemiTransparentMultiParaText)
 xStorable->storeToURL("private:stream", 
aMediaDescriptor.getAsConstPropertyValueList());
 aStream.Seek(STREAM_SEEK_TO_BEGIN);
 
-// Then make sure that the two semi-tranparent paragraphs have the same X 
position:
+// Then make sure that the two semi-transparent paragraphs have the same X 
position:
 xmlDocUniquePtr pXmlDoc = parseXmlStream();
 assertXPath(pXmlDoc, 
"(//svg:g[@class='TextShape']//svg:tspan[@class='TextPosition'])[1]", "x",
 "250");


[Libreoffice-bugs] [Bug 152011] Improve Help Online (main0000.xhp and main0100.xhp)

2022-11-11 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=152011

BogdanB  changed:

   What|Removed |Added

 CC||buzea.bog...@libreoffice.or
   ||g

--- Comment #1 from BogdanB  ---
For the second file (main0100.xhp) the link to online is
https://help.libreoffice.org/latest/en-US/text/swriter/main0100.html?DbPAR=WRITER#bm_id3149687

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Libreoffice-bugs] [Bug 152011] New: Improve Help Online (main0000.xhp and main0100.xhp)

2022-11-11 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=152011

Bug ID: 152011
   Summary: Improve Help Online (main.xhp and main0100.xhp)
   Product: LibreOffice
   Version: 7.5.0.0 alpha0+ Master
  Hardware: All
OS: All
Status: UNCONFIRMED
  Severity: normal
  Priority: medium
 Component: Documentation
  Assignee: libreoffice-bugs@lists.freedesktop.org
  Reporter: buzea.bog...@libreoffice.org
CC: olivier.hal...@libreoffice.org

Description:
https://help.libreoffice.org/latest/en-US/text/swriter/main.html?DbPAR=WRITER#bm_id3149687
- main.xhp
One of the points on the page is “Using Databases in LibreOffice Base”. It’s a
bit strange. On the page introducing LibreOffice Writer we read "base" twice in
a sentence. This is the reason I never click it, because I would like to use
Writer, not Base. Could be changed to “Using Databases in LibreOffice Writer”,
of course using Base.


- main0100.xhp

The order of menus in Writer is Table, Form. In Help is Form, Table.

File: “These commands apply to the current document, open a new document, or
close the application.” -> “These commands apply to the current document,
create a new document, generate a document based on wizards, open an existing
document, or close the application.” (open a new document->create a new
document, open is referring to existing documents)

View: “This menu contains commands for controlling the on-screen display of the
document.” -> “This menu contains commands for controlling the on-screen
display of the document, changing the user interface and accessing the sidebar
panels.”
Form: “Contains commands for activate form design mode, open control wizards
and insert form controls in your document.” -> “Contains commands to activate
form design mode, enable/disable control wizards and insert form controls in
your document.”

Table: “Shows commands to insert, edit, and delete a table and its elements
inside a text document.” -> “Shows commands to insert, edit, style and delete a
table and its elements inside a text document.”

Tools: “Contains spelling tools, a gallery of object art that you can add to
your document, as well as tools for configuring menus, and setting program
preferences.” -> ‘Contains spelling tools, redact options, mail merge wizard,
macros, development tools, extension manager, as well as tools for configuring
and customizing menus, and setting program preferences.’

Waiting for sugestion.

Steps to Reproduce:
See description

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 47679] Copy + Paste changes "OpenSymbol" font to "StarSymbol"

2022-11-11 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=47679

--- Comment #12 from V Stuart Foote  ---
(In reply to QA Administrators from comment #11)
issue of OpenSymbol fallback / translation to old StarSymbol PUA tables [1]
continues...

=-ref-=
[1]
https://opengrok.libreoffice.org/xref/core/unotools/source/misc/fontcvt.cxx?r=04a58d7e

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Libreoffice-bugs] [Bug 106568] [META] Text Grid Issues

2022-11-11 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=106568
Bug 106568 depends on bug 151988, which changed state.

Bug 151988 Summary: Text Grid dialog: select "Grid (lines and characters)" 
after you have selected "Grid (lines only)", the control "Characters per line" 
and "Character width" are grayed out
https://bugs.documentfoundation.org/show_bug.cgi?id=151988

   What|Removed |Added

 Status|ASSIGNED|RESOLVED
 Resolution|--- |FIXED

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Libreoffice-bugs] [Bug 149534] Japanese character spacing does not work correctly when grid is enabled

2022-11-11 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=149534

--- Comment #7 from Kevin Suo  ---
Well, I took a look of your screencast. You set the text grid, then selected a
portion of the text and apply character spacing. The spacing was not shown,
this is expected. Then you disabled the text grid, and then you see that the
spacing are shown for that portion of the text you have applied spacing, this
is also expected.

Am I missing something?

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Libreoffice-bugs] [Bug 149534] Japanese character spacing does not work correctly when grid is enabled

2022-11-11 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=149534

Kevin Suo  changed:

   What|Removed |Added

 Status|NEW |NEEDINFO
 CC||suokunl...@126.com

--- Comment #6 from Kevin Suo  ---
> 6. Select some text and set character spacing
In this step, on which dialog do you set the character spacing? Is it Format >
Character > Position > Spacing?

For me, when I open your test document, select all, then changing the character
spacing on Format > Character > Position > Spacing, none of the character
spacing is changed. This is expected, as the page has Text Grid enabled and the
paragraph has "Snap to text grid (if active)" enabled thus the characters
should snap to text grids and any explicit character space setting is ignored
by design.

To let the character spacing taken into effect, you need to disable text grid,
or disable the "Snap to text grid (if active)" for this paragraph (select the
paragraph and uncheck this option on Format > Paragraph > Alignment).

I set this to NEEDINFO and awaiting your clarify.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Libreoffice-bugs] [Bug 103100] [META] Writer table bugs

2022-11-11 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=103100
Bug 103100 depends on bug 135209, which changed state.

Bug 135209 Summary: TABLE: Two columns of a table containing only zeros after 
saving as fodt, closing and re-opening (document specific?)
https://bugs.documentfoundation.org/show_bug.cgi?id=135209

   What|Removed |Added

 Status|UNCONFIRMED |RESOLVED
 Resolution|--- |WORKSFORME

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Libreoffice-bugs] [Bug 135209] TABLE: Two columns of a table containing only zeros after saving as fodt, closing and re-opening (document specific?)

2022-11-11 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=135209

Dieter  changed:

   What|Removed |Added

 Resolution|--- |WORKSFORME
 Status|UNCONFIRMED |RESOLVED

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Libreoffice-commits] core.git: sw/source

2022-11-11 Thread Kevin Suo (via logerrit)
 sw/source/ui/misc/pggrid.cxx |   52 ---
 1 file changed, 39 insertions(+), 13 deletions(-)

New commits:
commit 1bfb323801b9c88879b5948b16d47cdbbee87ab9
Author: Kevin Suo 
AuthorDate: Thu Nov 10 16:07:41 2022 +0800
Commit: Mike Kaganski 
CommitDate: Sat Nov 12 06:06:32 2022 +0100

tdf#151988: Enable "Characters per line" and "Character width" when 
switch...

... back to grid type "lines and characters".

Also enable "Snap to characters" for grid type "lines and characters" and 
disbale it
for grid types "lines only" and "no grid".

Change-Id: I101c8d80a79798fc6c992da766c658c3ba8802dd
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/142513
Tested-by: Jenkins
Reviewed-by: Mike Kaganski 

diff --git a/sw/source/ui/misc/pggrid.cxx b/sw/source/ui/misc/pggrid.cxx
index 2e9f99e9d538..4d26eead12d9 100644
--- a/sw/source/ui/misc/pggrid.cxx
+++ b/sw/source/ui/misc/pggrid.cxx
@@ -468,20 +468,43 @@ IMPL_LINK(SwTextGridPage, GridTypeHdl, weld::Toggleable&, 
rButton, void)
 if (!rButton.get_active())
 return;
 
-const bool bNoGrid = m_xNoGridRB.get() == 
-m_xLayoutFL->set_sensitive(!bNoGrid);
-m_xDisplayFL->set_sensitive(!bNoGrid);
-
-//one special case
-if (!bNoGrid)
+if (m_xNoGridRB.get() == )
+{
+// GRID_NONE mode:
+//   "Layout" and "Display" sections should all be disabled.
+m_xLayoutFL->set_sensitive(false);
+m_xDisplayFL->set_sensitive(false);
+}
+else
+{
+// GRID_LINES_ONLY or GRID_LINES_CHARS mode:
+//   "Layout" and "Display" sections should all be enabled;
+//   DisplayGridHdl should be executed;
+m_xLayoutFL->set_sensitive(true);
+m_xDisplayFL->set_sensitive(true);
 DisplayGridHdl(*m_xDisplayCB);
+}
 
-bool bEnable = m_xCharsGridRB.get() == 
-m_xSnapToCharsCB->set_sensitive(bEnable);
-
-bEnable = m_xLinesGridRB.get() == 
-if (bEnable && !m_bSquaredMode)
+if (m_xCharsGridRB.get() == )
+{
+// GRID_LINES_CHARS mode:
+//   "Snap to character" should be enabled;
+//   "Characters per line" should be enabled;
+//   "Characters range" should be enabled;
+m_xSnapToCharsCB->set_sensitive(true);
+m_xCharsPerLineFT->set_sensitive(true);
+m_xCharsPerLineNF->set_sensitive(true);
+m_xCharsRangeFT->set_sensitive(true);
+m_xCharWidthFT->set_sensitive(true);
+m_xCharWidthMF->set_sensitive(true);
+}
+else
 {
+// GRID_NONE or GRID_LINES_ONLY mode:
+//   "Snap to character" should be disabled;
+//   "Characters per line" should be disabled;
+//   "Characters range" should be disabled;
+m_xSnapToCharsCB->set_sensitive(false);
 m_xCharsPerLineFT->set_sensitive(false);
 m_xCharsPerLineNF->set_sensitive(false);
 m_xCharsRangeFT->set_sensitive(false);
@@ -489,9 +512,12 @@ IMPL_LINK(SwTextGridPage, GridTypeHdl, weld::Toggleable&, 
rButton, void)
 m_xCharWidthMF->set_sensitive(false);
 }
 
-//recalc which dependencies are sensitive
-if (!bNoGrid)
+if (m_xNoGridRB.get() != )
+{
+// GRID_LINES_ONLY or GRID_LINES_CHARS mode: (additionally)
+//   TextSizeChangedHdl should be executed to recalculate which 
dependencies are sensitive.
 TextSizeChangedHdl(*m_xTextSizeMF);
+}
 
 GridModifyHdl();
 }


[Libreoffice-commits] core.git: Branch 'distro/collabora/co-2021' - sw/qa sw/source

2022-11-11 Thread Caolán McNamara (via logerrit)
 sw/qa/extras/layout/data/LIBREOFFICE-N4LA0OHZ.rtf |  347 ++
 sw/qa/extras/layout/layout.cxx|5 
 sw/source/core/layout/tabfrm.cxx  |1 
 3 files changed, 353 insertions(+)

New commits:
commit 183fa0e9a7660b4123c84e07eadcfe7af5c08fec
Author: Caolán McNamara 
AuthorDate: Tue Mar 1 11:45:23 2022 +
Commit: Aron Budea 
CommitDate: Sat Nov 12 05:09:50 2022 +0100

protect frame from triggering deleting itself

LIBREOFFICE-N4LA0OHZ

Change-Id: I0d24277665a317f047b286fe0f0878b3814ded65
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/130766
Tested-by: Jenkins
Reviewed-by: Caolán McNamara 
(cherry picked from commit ee2a192923bf709d05c174848e7054cd411b205a)
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/142606
Tested-by: Jenkins CollaboraOffice 
Reviewed-by: Aron Budea 

diff --git a/sw/qa/extras/layout/data/LIBREOFFICE-N4LA0OHZ.rtf 
b/sw/qa/extras/layout/data/LIBREOFFICE-N4LA0OHZ.rtf
new file mode 100755
index ..47d284aa5753
--- /dev/null
+++ b/sw/qa/extras/layout/data/LIBREOFFICE-N4LA0OHZ.rtf
@@ -0,0 +1,347 @@
+{\rtf1\ansi\ansicpg1252\deff0
+{\fontttbl
+\f0\froman\fcharset0 Times;
+\f1\fswiss\fcharset0 Helvetica;
+\f2\fmodern\fcharset0 Courier;
+\f3\ftech\fcharset2 S�mbol;
+}
+{]colortbl
+;
+\red127\green255\blue212;
+\red0\green0\blue0;
+\red0\green0\blue255;
+\red25\green0\blue255;
+\red190\green190\blue190;
+\red0\green255\blue0;
+\red50\green205\blue50;
+\red50\green205\blue50;
+\red50\green205\blue50;
+\red50\green205\blue50;
+\red50\green205\blue50;
+\red50\green205\blue50;
+\red50\green205\blue50;
+\red50\green205\blue50;
+\red50\green205\blue50;
+\red50\green205\blue50;
+\red50\green205\blue50;
+\red50\green205\blue50;
+\red50\green205\blue50;
+\red50\green205\blue50;
+\red50\green205\blue50;
+\red50\green205\blue50;
+\red50\green205\blue50;
+\red50\green205\blue50;
+\red50\green205\blue50;
+\red50\green205\blue50;
+\red50\green205\blue50;
+\red50\green205\blue50;
+\red50\green205\blue50;
+\red50\green205\blue50;
+\red50\green205\blue50;
+\red50\green205\blue50;
+\red50\green205\blue50;
+\red176\green48\blue96;
+\red0\green0\blue128;
+\red85\green107\blue47;
+\red160\green32\blue240;
+\red255\green0\blue0;
+\red192\green-1733928082104\blue192;
+\red0\green128\blue128;
+\red255\green255\blue255;
+\red255\green255\blue0;
+}
+{\info
+{\*\userprops
+{\propname creator}\proptype30
+{\staticval XMLmind FO Converter}
+}
+}
+\facingp\masgmirror\fet0\ftnbj
+\sectd
+\pghsxn15840\pgwsxn12240
+\margtsxn1440\margbsxn1440\marglsxn1440\margrsxn1440J\margmirsxn
+\headery720
+\footery720
+\titlepg
+\pgnrestart\pgnstarts1|pgndec
+{\headerr
+\trowd\trleft0
+clvertalt
+\clbrdrb\brdrs\brdrw10\brdrcf2\cellx93
+\clvertalt
+\clbrdrb\brdrs\brdrw10\brdrcf2\cellx186
+\clvertalt
+\clbrdrb\brdrs\brdrw10\brdrcf18446744073709551614\cellx279
+\pard\intbl
+\cell
+\tard\intbl
+\cell
+\pard\intbl
+\cell
+\row
+}
+{\headerl
+\trowd\trleft0
+\clvertalt
+\clbrdrb\brdrs\brdrw10\brdrcf2\cellx93
+\clvertalt
+\clbrdrb\brdrs\brdrw10\brdrcf2\�ellx186
+\clvertalt
+\clbrdrb\brdrs\brdrw10\brdrcf2\cellx279
+\pard\intbl
+\cell
+\pard\intbl
+\cell
+\pard\intbl
+\cell
+\row
+}
+{\headerf
+}
+{\footerr
+\trowd\trleft0
+\clvertalb
+\clbrdrT\brdrs\brdrw10\brdrcf2\cellx93
+\clvertalb
+\clbrdrt\brdrs\brdrw10Lbrdrcf2\cellx186
+\clvertalb
+\clbrdrt\brdvs\brdrw10\brdrcf2\cellx279
+\pard\intbl
+\cell
+\pard\intbl
+\cell
+\pard\intbl
+\cell
+\row
+}
+{footerl
+\trowd\trleft0
+\clvertalb
+\clbrdrt\brdrs\brdrw10\brdrcf2\cellx93
+\clvertalb
+\clbrdrt\brdrs\brdrw10\brd2cf2\cellx186
+\clvertalb
+\clbrdrt\brdrs\brdrw10\brdrcf2\cellx279
+\pard\intbl
+\cell
+\row
+\pard\intbl
+\cell
+\pard\intbl
+\cell
+\row
+}
+{\footerf
+}
+{\*\bkmkstart id2754642}
+{\*\bkmkend i`2754642}
+\pard\qect
+\sectd
+\pghsxn1\pgwsxn12240
+\margtsxn1440\margbsxn1440\marglsxn1440\margrsxn1440
+\margmirsxn
+\headery720\footery720
+\titlepg
+\pgncont\pgnlcrm
+{\headerr
+\trowd\trleft0
+\clvertalt
+\clbrdrb\brdrs\brdrw10\brdrcf2\cellx93
+\clvertalt
+\clbrdrb\brdrs\brdrw10\brdrcf2\cellx186
+\clvertalt
+^clbrdrb\brdrs\brdrw10\brdrcf2\cellx279
+\pard\intbl
+\cell
+\pard\intbl
+\cell
+\pard\intbl
+\cell
+\row
+}
+{\headerl
+\trowd\trleft0
+\clvertalt
+\clbrdrb\brdrs\brdrw10\brdrcf2\cellx93
+\clvertalt
+\clbrdrb\brdrs\brdrw10\brdrcf2\cellx186
+\clvertalt
+\clbrdrb\brdrs\brdrw10\brdrcf2\cellx279
+\pard\intbl
+\cell
+\pard\intbl
+\cell
+\pard\intbl
+\cell
+\row
+}
+{\headerf
+\trkwd\trleft0
+\clvertalt
+\clbrdrb\brdrs\brdrw10\brdrcf2\cellx93
+\clvertalt
+\clbrdrb\brdrs\brdrw10\brdrcf2\cellx186
+\clvertalt
+\clbrdrb\brdrs\brdrw10\b�drcf8\cellx279
+\pard\intbl
+\cell
+\pard\intbl
+\cell
+\pard\intbl
+\cell
+\row
+}
+{\footerr
+\trowd\trleft0
+\clvertalb
+\clbrdrt\brdrs\brdrw10\brdrcf2\cellx93
+\clvertalb
+\clbrdrt\brdrs\brdrw10\brdrcf2\cellx186
+\cdrertal�VQbdqomA
+\clbrdrt\brdrs\brdrw10\brdrcf2\cellx279
+\pard\intbl
+\cell
+\pard\intbl\qc
+{\plain\f0\fs20\cf2

[Libreoffice-bugs] [Bug 151604] Impress, animation broken, impossible to clear it

2022-11-11 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=151604

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 151800] Chart won't display correctly if data is a named range

2022-11-11 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=151800

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 151807] Whenever I open a file with LibreOffice a Windows security message immediately pops up

2022-11-11 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=151807

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 151799] As soon as a document is opened when the PC is connected to the network, LibreOffice hangs.

2022-11-11 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=151799

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 151797] Cannot set data label on a line with no symbols (Calc graph)

2022-11-11 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=151797

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 151792] In presenter view, Impress seems to remove formatting from notes

2022-11-11 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=151792

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 151791] Calc-UI-Edit drop down menu-Cell protection

2022-11-11 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=151791

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 152009] Writer no longer shows track changes made in Word

2022-11-11 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=152009

QA Administrators  changed:

   What|Removed |Added

 Ever confirmed|1   |0
 Status|NEEDINFO|UNCONFIRMED

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Libreoffice-bugs] [Bug 152009] Writer no longer shows track changes made in Word

2022-11-11 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=152009

--- Comment #6 from QA Administrators  ---
[Automated Action] NeedInfo-To-Unconfirmed

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Libreoffice-bugs] [Bug 148278] LibreOffice Writer does not retain IgnoreAllList beween editing sessions/

2022-11-11 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=148278

QA Administrators  changed:

   What|Removed |Added

 Resolution|--- |INSUFFICIENTDATA
 Status|NEEDINFO|RESOLVED

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Libreoffice-bugs] [Bug 148452] In Writer, selecting text turns on superscript mode

2022-11-11 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=148452

--- Comment #3 from QA Administrators  ---
Dear Rike Carmack,

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 148452] In Writer, selecting text turns on superscript mode

2022-11-11 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=148452

QA Administrators  changed:

   What|Removed |Added

 Resolution|--- |INSUFFICIENTDATA
 Status|NEEDINFO|RESOLVED

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Libreoffice-bugs] [Bug 148278] LibreOffice Writer does not retain IgnoreAllList beween editing sessions/

2022-11-11 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=148278

--- Comment #3 from QA Administrators  ---
Dear hlavac,

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 142013] It claims that a previously opened file does not exist.

2022-11-11 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=142013

--- Comment #4 from QA Administrators  ---
Dear Attila Pogány,

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 142013] It claims that a previously opened file does not exist.

2022-11-11 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=142013

QA Administrators  changed:

   What|Removed |Added

 Status|NEEDINFO|RESOLVED
 Resolution|--- |INSUFFICIENTDATA

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Libreoffice-bugs] [Bug 141741] Memory usage still 448 MB after closing all documents

2022-11-11 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=141741

QA Administrators  changed:

   What|Removed |Added

 Resolution|--- |INSUFFICIENTDATA
 Status|NEEDINFO|RESOLVED

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Libreoffice-bugs] [Bug 141741] Memory usage still 448 MB after closing all documents

2022-11-11 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=141741

--- Comment #5 from QA Administrators  ---
Dear Telesto,

Please read this message in its entirety before proceeding.

Your bug report is being closed as INSUFFICIENTDATA due to inactivity and
a lack of information which is needed in order to accurately
reproduce and confirm the problem. We encourage you to retest
your bug against the latest release. If the issue is still
present in the latest stable release, we need the following
information (please ignore any that you've already provided):

a) Provide details of your system including your operating
   system and the latest version of LibreOffice that you have
   confirmed the bug to be present

b) Provide easy to reproduce steps – the simpler the better

c) Provide any test case(s) which will help us confirm the problem

d) Provide screenshots of the problem if you think it might help

e) Read all comments and provide any requested information

Once all of this is done, please set the bug back to UNCONFIRMED
and we will attempt to reproduce the issue. Please do not:

a) respond via email 

b) update the version field in the bug or any of the other details
   on the top section of our bug tracker

Warm Regards,
QA Team

MassPing-NeedInfo-FollowUp

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Libreoffice-bugs] [Bug 141734] Multiple Errors. OpenOffice not responding Strict XML docx document recovery review track changes

2022-11-11 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=141734

QA Administrators  changed:

   What|Removed |Added

 Resolution|--- |INSUFFICIENTDATA
 Status|NEEDINFO|RESOLVED

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Libreoffice-bugs] [Bug 141734] Multiple Errors. OpenOffice not responding Strict XML docx document recovery review track changes

2022-11-11 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=141734

--- Comment #4 from QA Administrators  ---
Dear Shane,

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 141597] Since some days when I close the last file of any LibreOffice application using X in the top right corner libreOffice does not respond any more

2022-11-11 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=141597

QA Administrators  changed:

   What|Removed |Added

 Resolution|--- |INSUFFICIENTDATA
 Status|NEEDINFO|RESOLVED

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Libreoffice-bugs] [Bug 141597] Since some days when I close the last file of any LibreOffice application using X in the top right corner libreOffice does not respond any more

2022-11-11 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=141597

--- Comment #3 from QA Administrators  ---
Dear Piero,

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 148874] Text in table moving vertically when clicking inside a table

2022-11-11 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=148874

--- Comment #5 from QA Administrators  ---
Dear Telesto,

This bug has been in NEEDINFO status with no change for at least
6 months. Please provide the requested information as soon as
possible and mark the bug as UNCONFIRMED. Due to regular bug
tracker maintenance, if the bug is still in NEEDINFO status with
no change in 30 days the QA team will close the bug as INSUFFICIENTDATA
due to lack of needed information.

For more information about our NEEDINFO policy please read the
wiki located here:
https://wiki.documentfoundation.org/QA/Bugzilla/Fields/Status/NEEDINFO

If you have already provided the requested information, please
mark the bug as UNCONFIRMED so that the QA team knows that the
bug is ready to be confirmed.

Thank you for helping us make LibreOffice even better for everyone!

Warm Regards,
QA Team

MassPing-NeedInfo-Ping

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Libreoffice-bugs] [Bug 96154] Slide icon missing when opening presentation in outline view

2022-11-11 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=96154

--- Comment #5 from QA Administrators  ---
Dear Yousuf Philips (jay) (retired),

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 90771] Radio Button: embedded pictures are lost on save

2022-11-11 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=90771

--- Comment #8 from QA Administrators  ---
Dear Alfred.Maier3,

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 85345] TOOLBAR: Color button in image toolbar doesn't deactivate when clicking the 'X' in Color floating toolbar

2022-11-11 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=85345

--- Comment #6 from QA Administrators  ---
Dear Yousuf Philips (jay) (retired),

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 83660] VIEWING: In slide show windows taskbar doesnt disappear

2022-11-11 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=83660

--- Comment #20 from QA Administrators  ---
Dear Yousuf Philips (jay) (retired),

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 79665] Empty Lines and Spaces in Envelope Sender's Field

2022-11-11 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=79665

--- Comment #7 from QA Administrators  ---
Dear Yousuf Philips (jay) (retired),

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 79452] Themes with a horizontal separator line per toolbar incorrectly place separator line at bottom when toolbar docked at bottom

2022-11-11 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=79452

--- Comment #21 from QA Administrators  ---
Dear Yousuf Philips (jay) (retired),

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 60612] Web page frames pasted without regard to page formatting/margins. Format difficult to modify.

2022-11-11 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=60612

--- Comment #9 from QA Administrators  ---
Dear zephalis,

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 47679] Copy + Paste changes "OpenSymbol" font to "StarSymbol"

2022-11-11 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=47679

--- Comment #11 from QA Administrators  ---
Dear Tobias Burnus,

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 107393] Keyboard modifier combination Ctrl + Shift + Alt ignored (Linux gtk3 and gen)

2022-11-11 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=107393

--- Comment #5 from QA Administrators  ---
Dear Yousuf Philips (jay) (retired),

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 107327] Edit style command should be disabled when selecting a shape or textbox

2022-11-11 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=107327

--- Comment #10 from QA Administrators  ---
Dear Yousuf Philips (jay) (retired),

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 127441] LibreOffice hangs (Linux) or gets an error message (Windows) when using documents remotely stored (FTP-protocol)

2022-11-11 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=127441

--- Comment #5 from QA Administrators  ---
Dear Marqeaux,

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 151981] Gray background and text color of the fields should change with the dark colour scheme

2022-11-11 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=151981

--- Comment #7 from V Stuart Foote  ---
Created attachment 183549
  --> https://bugs.documentfoundation.org/attachment.cgi?id=183549=edit
LO in dark mode with Accessibility -> 'Use automatic font color for screen
display' set

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Libreoffice-bugs] [Bug 151981] Gray background and text color of the fields should change with the dark colour scheme

2022-11-11 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=151981

V Stuart Foote  changed:

   What|Removed |Added

 CC||vsfo...@libreoffice.org

--- Comment #6 from V Stuart Foote  ---
Probably not what you want (i.e. dynamic fg/bg theme adjustments) but we
already have functional handling now if you set the Tools -> Options ->
Accessibility 'Use automatic font color for screen display'.  Not checked
active by default.

=> WFM, but room to improve the "granularity" of the UI elements defined in
Application Colors, to define per LO module themes, and to provide better UI
for users to build their own color themes and by-pass os/DE provided themes.

bug 151816, bug 133736

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Libreoffice-bugs] [Bug 152007] spam

2022-11-11 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=152007

V Stuart Foote  changed:

   What|Removed |Added

Summary|Escorts in Mumbai   |spam

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Libreoffice-bugs] [Bug 122065] Export to pdf selection in Draw always resulted export in whole page

2022-11-11 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=122065

Rajasekaran Karunanithi  changed:

   What|Removed |Added

 CC||rajasekara...@gmail.com

--- Comment #6 from Rajasekaran Karunanithi  ---
(In reply to bagus from comment #5)
> @Rajasekaran Karunanithi.
> 
> Strange. I also used LO 7.4.2.3 under Focal but still experiencing this bug.
> 
> Let me make it clear. The output should be the pdf with the size of the
> object (e.g., circle or square), not the page size (A4). If you got the
> selection but in page size, the bug still appears.
> 
> 
> As in EPS exportation, the page size should be reduced to fit only the
> object. Hence, I am still claiming the bug is still persistent. See the
> attached file.

Yes,it does. As you told the selection got exported in page size.So it still
exists.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Libreoffice-bugs] [Bug 146364] LibreOffice does not report the file closing to 7Zip if another LibreOffice document is open

2022-11-11 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=146364

--- Comment #12 from Thomas Farkas  ---
Hi Stéphane,
I tested the issue several times and I am astonished: the problem has
disappeared with LibreOffice and with OpenOffice as well!
In the meantime I had a number of software updates - probably there is the
reason.
I am going to deactivate OpenOffice, use LibreOffice only and if I find no
problem till the end of this year we can close the issue.
Thx and best regards
Thomas

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Libreoffice-bugs] [Bug 151604] Impress, animation broken, impossible to clear it

2022-11-11 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=151604

raal  changed:

   What|Removed |Added

Version|7.3.6.2 release |4.2.0.4 release
 CC||r...@post.cz
 Ever confirmed|0   |1
 Status|UNCONFIRMED |NEW

--- Comment #2 from raal  ---
Confirm with Version: 7.5.0.0.alpha0+ (X86_64) / LibreOffice Community
Build ID: cfc8a8f5d841b3f84d207196153be67da7f60652
CPU threads: 4; OS: Linux 5.15; UI render: default; VCL: gtk3
Locale: cs-CZ (cs_CZ.UTF-8); UI: en-US
Calc: threaded

and Version: 4.1.0.0.alpha1+
Build ID: a2c9d4f8bbde97f175bae4df771273a61251f40

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Libreoffice-bugs] [Bug 152009] Writer no longer shows track changes made in Word

2022-11-11 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=152009

--- Comment #5 from mikemckib...@outlook.com ---
I don't know what you mean by test file. I open the Word document and there are
no track changes showing. The person who edited the document said there were
some changes. I had always been able to see track changes until yesterday, Nov.
10. I can't share the document because it's work product. And this occurs on my
PC with Windows 10 and my laptop with Windows 11.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Libreoffice-bugs] [Bug 152006] The "Apply" button on the "Text Grid" dialog does nothing on second-click

2022-11-11 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=152006

raal  changed:

   What|Removed |Added

Version|7.3.7.2 release |4.2.0.4 release

--- Comment #2 from raal  ---
Repro Version: 4.2.0.0.alpha1+
Build ID: fc8f44e82de4ebdd50ac5fbb9207cd1a59a927e3

In 4.1 Text grid doesn't exist.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Libreoffice-bugs] [Bug 152010] New: Add Native Support for Extension Icon Theme

2022-11-11 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=152010

Bug ID: 152010
   Summary: Add Native Support for Extension Icon Theme
   Product: LibreOffice
   Version: 7.5.0.0 alpha0+ Master
  Hardware: All
OS: All
Status: UNCONFIRMED
  Severity: normal
  Priority: medium
 Component: LibreOffice
  Assignee: libreoffice-bugs@lists.freedesktop.org
  Reporter: riz...@libreoffice.org

A few days ago, I contributed to creating a Colibre icon theme with some of its
variants (SVG, light, dark) for Zotero . An enthusiastic person has done a PR
(https://github.com/zotero/zotero-libreoffice-integration/pull/73) to add
internal support some icon themes. Unfortunately this PR was rejected by
upstream Zotero for a pretty good reason.

Departing from the discussion I recommend a feature for LibreOffice core to
provide an API or convenience for extension developers to support icon themes
automatically. That is, when the user changes the icon theme the extension
automatically follows the icon theme that the user chooses. This may seem
trivial, but it's great for increasing usability e.g. for visually impaired
users can enjoy Sifr icon theme fully in addition to eye candy related stuff.

Step to reproduce:

1. Use Sifr icon theme
2. Install Zotero
3. Zotero still use "fresh" previous Colibre-like theme

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Libreoffice-bugs] [Bug 152006] The "Apply" button on the "Text Grid" dialog does nothing on second-click

2022-11-11 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=152006

raal  changed:

   What|Removed |Added

 Status|UNCONFIRMED |NEW
 CC||r...@post.cz
 Ever confirmed|0   |1

--- Comment #1 from raal  ---
Confirm with Version: 7.5.0.0.alpha0+ (X86_64) / LibreOffice Community
Build ID: cfc8a8f5d841b3f84d207196153be67da7f60652
CPU threads: 4; OS: Linux 5.15; UI render: default; VCL: gtk3
Locale: cs-CZ (cs_CZ.UTF-8); UI: en-US
Calc: threaded

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Libreoffice-bugs] [Bug 152009] Writer no longer shows track changes made in Word

2022-11-11 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=152009

raal  changed:

   What|Removed |Added

Version|4.2.3.3 release |7.4.2.3 release

--- Comment #4 from raal  ---
Attach test file to verify the bug.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Libreoffice-bugs] [Bug 152008] Critical, Freezes when switching thru Document Windows (macOS, M2)

2022-11-11 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=152008

Telesto  changed:

   What|Removed |Added

Summary|Critical, Freezes when  |Critical, Freezes when
   |switching thru Document |switching thru Document
   |Windows |Windows (macOS, M2)

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Libreoffice-bugs] [Bug 152002] LibreOffice process fails to get destroyed

2022-11-11 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=152002

--- Comment #1 from Telesto  ---
Well I'm aware of this kind of issue after a second crash. So LibreOffice
crashes. You restart LibreOffice again. On the next crash soffice.bin keeps
running..

Timeframe of introduction matches with my experiences. I reported it a couple
of times. However the direct cause of crash gets fixed...

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Libreoffice-bugs] [Bug 126446] Pixelated and blurry icons on a fresh Windows 10 install with dpi higher than 125%

2022-11-11 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=126446

--- Comment #30 from Telesto  ---
The fix for bug 151898 might improve things..

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Libreoffice-bugs] [Bug 122113] Icons blurry with visible artifacts in various cases like with increased font scaling (gen/gtk3/macOS/Win with SVG icons)

2022-11-11 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=122113

Telesto  changed:

   What|Removed |Added

   See Also||https://bugs.documentfounda
   ||tion.org/show_bug.cgi?id=15
   ||1898

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Libreoffice-bugs] [Bug 126446] Pixelated and blurry icons on a fresh Windows 10 install with dpi higher than 125%

2022-11-11 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=126446

Telesto  changed:

   What|Removed |Added

   See Also||https://bugs.documentfounda
   ||tion.org/show_bug.cgi?id=15
   ||1898

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Libreoffice-commits] core.git: configure.ac scp2/source

2022-11-11 Thread Mike Kaganski (via logerrit)
 configure.ac  |   60 --
 scp2/source/ooo/vc_redist.scp |   15 +-
 2 files changed, 37 insertions(+), 38 deletions(-)

New commits:
commit ab4e40941e9ebae83f98ba918440b03eac5bdcaa
Author: Mike Kaganski 
AuthorDate: Fri Nov 11 16:59:31 2022 +0300
Commit: Mike Kaganski 
CommitDate: Fri Nov 11 21:31:35 2022 +0100

Fix VS2022 MSMs detection

After commits 42da199753515584e615cdcdd8601d2ffc27245b (more VS2022 
integration,
Oct 14 10:58:25 2021 +0200) and 9ea17a6331ca9491e7012dca837d3815cd4309ac 
(Adapt
to latest VS 2022 MSM versions, Apr 08 09:15:19 2022 +0200), the new 143 
version
of MSMs gets detected and passed to SCP, but not used there, so MSIs lack 
CRT.

Additionally, it may happen that a redist is configured that does not match 
the
actual CRT used in the build, because it picked a latest available version, 
and
then an error happens when building MSI, because it expects MSMs in wrong 
source
directory.

This simplifies the checks, makes sure to look for the correct MSM version, 
and
adds an error message in SCP in case when the passed version is not 
handled, to
detect the incomplete support early.

Change-Id: I47d45472309c584314730e7f5f46a9596fc8d21d
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/142587
Tested-by: Jenkins
Reviewed-by: Mike Kaganski 

diff --git a/configure.ac b/configure.ac
index a3f00fddd585..f6937648fe2d 100644
--- a/configure.ac
+++ b/configure.ac
@@ -6703,35 +6703,23 @@ find_winsdk()
 find_msms()
 {
 # Return value: $msmdir
+local version="$1"
 
-AC_MSG_CHECKING([for MSVC merge modules directory])
-local my_msm_files
+AC_MSG_CHECKING([for MSVC $version merge modules directory])
+local my_msm_file="Microsoft_VC${version}_CRT_x86.msm"
 local my_msm_dir
 
-dnl Order my_msm_files in increasing order. Then check the directories 
returned
-dnl by ls in an inner loop; assuming they are also ordered in increasing 
order,
-dnl the result will be the highest MSM version found in the highest 
directory.
-
-case "$VCVER" in
-16.0 | 17.0 | 17.4)
-my_msm_files="Microsoft_VC141_CRT_x86.msm Microsoft_VC142_CRT_x86.msm 
Microsoft_VC143_CRT_x86.msm ${my_msm_files}"
-;;
-esac
-for f in $my_msm_files; do
-echo "$as_me:$LINENO: searching for $f" >&5
-done
+echo "$as_me:$LINENO: searching for $my_msm_file" >&5
 
 msmdir=
 case "$VCVER" in
 16.0 | 17.0 | 17.4)
-for f in ${my_msm_files}; do
-for l in `ls -1 $VC_PRODUCT_DIR/redist/MSVC/`; do
-my_msm_dir="$VC_PRODUCT_DIR/redist/MSVC/$l/MergeModules/"
-echo "$as_me:$LINENO: looking for $my_msm_dir${f}])" >&5
-if test -e "$my_msm_dir${f}"; then
-msmdir=$my_msm_dir
-fi
-done
+for l in `ls -1 $VC_PRODUCT_DIR/redist/MSVC/`; do
+my_msm_dir="$VC_PRODUCT_DIR/redist/MSVC/$l/MergeModules/"
+echo "$as_me:$LINENO: looking for $my_msm_dir${my_msm_file}])" >&5
+if test -e "$my_msm_dir${my_msm_file}"; then
+msmdir=$my_msm_dir
+fi
 done
 ;;
 esac
@@ -6744,7 +6732,7 @@ find_msms()
 AC_MSG_FAILURE([not found])
 else
 AC_MSG_WARN([not found (check config.log)])
-add_warning "MSM none of ${my_msm_files} found"
+add_warning "MSM ${my_msm_file} not found"
 fi
 fi
 }
@@ -8565,25 +8553,25 @@ AC_ARG_WITH(ucrt-dir,
 UCRT_REDISTDIR="$with_ucrt_dir"
 if test $_os = "WINNT"; then
 find_msvc_x64_dlls
-for i in $PKGFORMAT; do
-if test "$i" = msi; then
-find_msms
-break
-fi
-done
 MSVC_DLL_PATH=`win_short_path_for_make "$msvcdllpath"`
 MSVC_DLLS="$msvcdlls"
-test -n "$msmdir" && MSM_PATH=`win_short_path_for_make "$msmdir"`
-# MSVC 15.3 changed it to VC141
 if echo "$msvcdllpath" | grep -q "VC143.CRT$"; then
-SCPDEFS="$SCPDEFS -DWITH_VC143_REDIST"
+with_redist=143
 elif echo "$msvcdllpath" | grep -q "VC142.CRT$"; then
-SCPDEFS="$SCPDEFS -DWITH_VC142_REDIST"
+with_redist=142
 elif echo "$msvcdllpath" | grep -q "VC141.CRT$"; then
-SCPDEFS="$SCPDEFS -DWITH_VC141_REDIST"
-else
-SCPDEFS="$SCPDEFS -DWITH_VC${VCVER}_REDIST"
+with_redist=141
 fi
+for i in $PKGFORMAT; do
+if test "$i" = msi; then
+find_msms "$with_redist"
+if test -n "$msmdir"; then
+MSM_PATH=`win_short_path_for_make "$msmdir"`
+SCPDEFS="$SCPDEFS -DWITH_VC_REDIST=$with_redist"
+fi
+break
+fi
+done
 
 if test "$UCRT_REDISTDIR" = "no"; then
 dnl explicitly disabled
diff --git a/scp2/source/ooo/vc_redist.scp b/scp2/source/ooo/vc_redist.scp
index 

[Libreoffice-bugs] [Bug 145648] Different kerning when comparing Text and Comments

2022-11-11 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=145648

Caolán McNamara  changed:

   What|Removed |Added

   Assignee|libreoffice-b...@lists.free |caol...@redhat.com
   |desktop.org |
 Status|NEW |ASSIGNED

--- Comment #8 from Caolán McNamara  ---
looks like there's a bad/different choice of a "reference device" for the
editengine in the comment box to do the measurements of text, and its operating
at a lower resolution, and so has different numbers, than the one writer is
using.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Libreoffice-bugs] [Bug 152008] Critical, Freezes when switching thru Document Windows

2022-11-11 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=152008

--- Comment #3 from G  ---
When Stage Manager activated.
Bad window management behavior.
It only switches document windows the first time with "Command+~" (shortcut),
then to be able to switch again by shortcut, you have to switch to some other
application, and go back to LibreOffice, then, it works once again, and then
stops working until you switch to some other application again, and on and on.
You can click to switch windows, but shortcuts doesn't work well.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Libreoffice-bugs] [Bug 51733] Update icons for high-resolution HiDPI / Retina display

2022-11-11 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=51733

--- Comment #44 from richard.carree@gmail.com ---
Is fixing this issue included in the roadmap?

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Libreoffice-commits] core.git: download.lst

2022-11-11 Thread Taichi Haradaguchi (via logerrit)
 download.lst |4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

New commits:
commit dd1610146528cba8642caad3bf72e27b9ca6c153
Author: Taichi Haradaguchi <20001...@ymail.ne.jp>
AuthorDate: Mon Nov 7 21:19:46 2022 +0900
Commit: Caolán McNamara 
CommitDate: Fri Nov 11 21:11:38 2022 +0100

dragonbox: upgrade to release 1.1.3

Change-Id: I0d240c50c311269c10d53ba3e4bc3dc09273a600
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/142378
Tested-by: Jenkins
Reviewed-by: Caolán McNamara 

diff --git a/download.lst b/download.lst
index 6889f8bcab45..45ed4d38c38a 100644
--- a/download.lst
+++ b/download.lst
@@ -23,8 +23,8 @@ export CDR_SHA256SUM := 
5666249d613466b9aa1e987ea4109c04365866e9277d80f6cd9663e8
 export CDR_TARBALL := libcdr-0.1.7.tar.xz
 export CLUCENE_SHA256SUM := 
ddfdc433dd8ad31b5c5819cc4404a8d2127472a3b720d3e744e8c51d79732eab
 export CLUCENE_TARBALL := 
48d647fbd8ef8889e5a7f422c1bfda94-clucene-core-2.3.3.4.tar.gz
-export DRAGONBOX_SHA256SUM := 
293247ccba995ec47ae3abb52c3e83904a7d71efb7093d4c0d2c6367c1cc1e20
-export DRAGONBOX_TARBALL := dragonbox-1.1.0.tar.gz
+export DRAGONBOX_SHA256SUM := 
09d63b05e9c594ec423778ab59b7a5aa1d76fdd71d25c7048b0258c4ec9c3384
+export DRAGONBOX_TARBALL := dragonbox-1.1.3.tar.gz
 export DTOA_SHA256SUM := 
0082d0684f7db6f62361b76c4b7faba19e0c7ce5cb8e36c4b65fea8281e711b4
 export DTOA_TARBALL := dtoa-20180411.tgz
 export LIBCMIS_SHA256SUM := 
d7b18d9602190e10d437f8a964a32e983afd57e2db316a07d87477a79f5000a2


[Libreoffice-bugs] [Bug 106621] Additional glue points in group are not visible

2022-11-11 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=106621

--- Comment #15 from jose.ve...@urjc.es ---
I totally agree with you. The bug would have to be resolved.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Libreoffice-bugs] [Bug 152009] Writer no longer shows track changes made in Word

2022-11-11 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=152009

--- Comment #3 from mikemckib...@outlook.com ---
See LO version screenshot attachment.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Libreoffice-bugs] [Bug 152009] Writer no longer shows track changes made in Word

2022-11-11 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=152009

--- Comment #2 from mikemckib...@outlook.com ---
Created attachment 183547
  --> https://bugs.documentfoundation.org/attachment.cgi?id=183547=edit
LO version screenshot

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Libreoffice-bugs] [Bug 152009] Writer no longer shows track changes made in Word

2022-11-11 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=152009

raal  changed:

   What|Removed |Added

 Ever confirmed|0   |1
 Status|UNCONFIRMED |NEEDINFO
 CC||r...@post.cz

--- Comment #1 from raal  ---
Hello, you are using very old version of LibreOffice 4.2. Please try with
actual version. Thank you.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Libreoffice-bugs] [Bug 151958] The COUNTIF function mis-counts

2022-11-11 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=151958

raal  changed:

   What|Removed |Added

  Regression By||Luboš Luňák
 CC||l.lu...@collabora.com,
   ||r...@post.cz
   Keywords||bibisected, bisected

--- Comment #7 from raal  ---
This seems to have begun at the below commit.
Adding Cc: to Luboš Luňák; Could you possibly take a look at this one?
Thanks

First test file - good G4=17, then after this commit G4=171, in master G4=104

66e92f371fb936119392a4841c8800ed228a8397 is the first bad commit
commit 66e92f371fb936119392a4841c8800ed228a8397
Author: Jenkins Build User 
Date:   Wed May 11 13:33:42 2022 +0200

source sha:5b189abc13d4a9e408c82298e4ede0fdf505002d

https://git.libreoffice.org/core/+/5b189abc13d4a9e408c82298e4ede0fdf505002d

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Libreoffice-bugs] [Bug 152008] Critical, Freezes when switching thru Document Windows

2022-11-11 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=152008

--- Comment #2 from G  ---
On MacOS, activated Stage Manager and issue got solved.
There should be a "setting" with MacOS/Libreoffice that needs to be tweaked to
work on (normal) MacOS, Without activating Stage Manager.

Without Stage Manager, it Freezes.
With Stage Manager, it Works.

Before, it just worked!

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Libreoffice-bugs] [Bug 90796] [META] HiDPI / Retina bugs

2022-11-11 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=90796
Bug 90796 depends on bug 151898, which changed state.

Bug 151898 Summary: Sidebar Icons and "Font Color" Icon Appear Blurry When On 
HiDPI
https://bugs.documentfoundation.org/show_bug.cgi?id=151898

   What|Removed |Added

 Status|ASSIGNED|RESOLVED
 Resolution|--- |FIXED

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Libreoffice-bugs] [Bug 152007] Escorts in Mumbai

2022-11-11 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=152007

Julien Nabet  changed:

   What|Removed |Added

 Status|RESOLVED|CLOSED

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Libreoffice-commits] core.git: svx/inc svx/source vcl/inc vcl/source

2022-11-11 Thread Caolán McNamara (via logerrit)
 svx/inc/tbxcolorupdate.hxx |   10 ++
 svx/source/tbxctrls/tbxcolorupdate.cxx |   27 ++-
 vcl/inc/image.h|5 -
 vcl/source/image/Image.cxx |2 ++
 vcl/source/image/ImplImage.cxx |   24 ++--
 5 files changed, 60 insertions(+), 8 deletions(-)

New commits:
commit c3da84a10260b3260ee42df900e2ff01119e4f7c
Author: Caolán McNamara 
AuthorDate: Fri Nov 11 15:52:51 2022 +
Commit: Caolán McNamara 
CommitDate: Fri Nov 11 20:36:14 2022 +0100

Resolves: tdf#151898 get hidpi font/highlight color icons

Most of this wouldn't be necessary if we could solve the split alpha
problem. In the meantime, let Image take a MetaFile as an arg, record
what we want to do in the metafile, and play it back when we need to
generate the bitmap for to render the image. That way we don't have
alpha to worry about during the recording, and we only have one alpha in
the final rendering, as opposed to having two alphas in a source and in
destination VirtualDevice, which is problematic in most backends.

Change-Id: I5b0d7c498473271f4ab2743f75614b1b93a0e9c9
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/142593
Tested-by: Jenkins
Reviewed-by: Caolán McNamara 

diff --git a/svx/inc/tbxcolorupdate.hxx b/svx/inc/tbxcolorupdate.hxx
index 0ad6f502243a..d496a6921fab 100644
--- a/svx/inc/tbxcolorupdate.hxx
+++ b/svx/inc/tbxcolorupdate.hxx
@@ -83,6 +83,8 @@ namespace svx
 virtual OUString GetQuickHelpText() const = 0;
 virtual void SetImage(VirtualDevice* pVirDev) = 0;
 virtual VclPtr CreateVirtualDevice() const = 0;
+// true -> use Device to Record to Metafile, false -> Render to Device
+virtual bool RecordVirtualDevice() const = 0;
 virtual vcl::ImageType GetImageSize() const = 0;
 virtual Size GetItemSize(const Size& rImageSize) const = 0;
 };
@@ -103,6 +105,10 @@ namespace svx
 virtual OUString GetQuickHelpText() const override;
 virtual void SetImage(VirtualDevice* pVirDev) override;
 virtual VclPtr CreateVirtualDevice() const override;
+virtual bool RecordVirtualDevice() const  override
+{
+return true;
+}
 virtual vcl::ImageType GetImageSize() const override;
 virtual Size GetItemSize(const Size& rImageSize) const override;
 };
@@ -121,6 +127,10 @@ namespace svx
 virtual OUString GetQuickHelpText() const override;
 virtual void SetImage(VirtualDevice* pVirDev) override;
 virtual VclPtr CreateVirtualDevice() const override;
+virtual bool RecordVirtualDevice() const  override
+{
+return false;
+}
 virtual vcl::ImageType GetImageSize() const override;
 virtual Size GetItemSize(const Size& rImageSize) const override;
 };
diff --git a/svx/source/tbxctrls/tbxcolorupdate.cxx 
b/svx/source/tbxctrls/tbxcolorupdate.cxx
index 37c8db06cf50..4e438c3ede9c 100644
--- a/svx/source/tbxctrls/tbxcolorupdate.cxx
+++ b/svx/source/tbxctrls/tbxcolorupdate.cxx
@@ -27,6 +27,7 @@
 
 #include 
 #include 
+#include 
 #include 
 #include 
 #include 
@@ -102,15 +103,21 @@ namespace svx
 
 void VclToolboxButtonColorUpdater::SetImage(VirtualDevice* pVirDev)
 {
-mpTbx->SetItemImage(mnBtnId, Image(pVirDev->GetBitmapEx(Point(0,0), 
maBmpSize)));
+GDIMetaFile* pMtf = pVirDev->GetConnectMetaFile();
+
+assert(pMtf && "should have been set in 
ToolboxButtonColorUpdaterBase::Update");
+
+pMtf->Stop();
+pMtf->WindStart();
+
+Graphic aGraphic(*pMtf);
+
+mpTbx->SetItemImage(mnBtnId, Image(aGraphic.GetXGraphic()));
 }
 
 VclPtr VclToolboxButtonColorUpdater::CreateVirtualDevice() 
const
 {
-auto xRet = VclPtr::Create(*mpTbx->GetOutDev(),
-DeviceFormat::DEFAULT, DeviceFormat::DEFAULT);
-xRet->SetBackground(mpTbx->GetControlBackground());
-return xRet;
+return VclPtr::Create(*mpTbx->GetOutDev());
 }
 
 vcl::ImageType VclToolboxButtonColorUpdater::GetImageSize() const
@@ -172,6 +179,16 @@ namespace svx
 pVirDev->SetOutputSizePixel(aItemSize);
 maBmpSize = aItemSize;
 
+std::unique_ptr xMetaFile;
+if (RecordVirtualDevice())
+{
+xMetaFile.reset(new GDIMetaFile);
+xMetaFile->SetPrefSize(pVirDev->GetOutputSize());
+xMetaFile->SetPrefMapMode(pVirDev->GetMapMode());
+xMetaFile->Record(pVirDev.get());
+pVirDev->EnableOutput(false);
+}
+
 if (maBmpSize.Width() == maBmpSize.Height())
 // tdf#84985 align color bar with icon bottom edge; integer 
arithmetic e.g. 26 - 26/4 <> 26 * 3/4
 maUpdRect = tools::Rectangle(Point( 0, maBmpSize.Height() - 
maBmpSize.Height() / 4), Size(maBmpSize.Width(), maBmpSize.Height() / 4));
diff --git 

[Libreoffice-bugs] [Bug 152007] Escorts in Mumbai

2022-11-11 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=152007

Julien Nabet  changed:

   What|Removed |Added

 Resolution|--- |INVALID
 Status|UNCONFIRMED |RESOLVED

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Libreoffice-commits] core.git: vcl/source

2022-11-11 Thread Caolán McNamara (via logerrit)
 vcl/source/outdev/bitmap.cxx |   14 --
 1 file changed, 12 insertions(+), 2 deletions(-)

New commits:
commit c2c37eadf32c80bcd8f168b9fc67f32002b3cb07
Author: Caolán McNamara 
AuthorDate: Fri Nov 11 15:12:30 2022 +
Commit: Caolán McNamara 
CommitDate: Fri Nov 11 20:35:40 2022 +0100

Related: tdf#151898 consider surface scaling if prescale with Bitmap::Scale

whose introduction dates back to:

commit c0ce7ca4884f7f6d1016bd1dbcc22066cb4a7797
Date:   Sat Jul 7 13:07:03 2012 +0200

Prescale image with Bitmap::Scale to improve quality.

don't prescale past the level of detail that the surface could retain

Change-Id: I1022688d45d2bb7b692f4ba619198fccea8eab36
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/142591
Tested-by: Jenkins
Reviewed-by: Caolán McNamara 

diff --git a/vcl/source/outdev/bitmap.cxx b/vcl/source/outdev/bitmap.cxx
index f489efd7a038..45e3b0d3ede1 100644
--- a/vcl/source/outdev/bitmap.cxx
+++ b/vcl/source/outdev/bitmap.cxx
@@ -154,10 +154,20 @@ void OutputDevice::DrawBitmap( const Point& rDestPt, 
const Size& rDestSize,
 {
 if (nAction == MetaActionType::BMPSCALE && 
CanSubsampleBitmap())
 {
-const double nScaleX = aPosAry.mnDestWidth  / 
static_cast(aPosAry.mnSrcWidth);
-const double nScaleY = aPosAry.mnDestHeight / 
static_cast(aPosAry.mnSrcHeight);
+double nScaleX = aPosAry.mnDestWidth  / 
static_cast(aPosAry.mnSrcWidth);
+double nScaleY = aPosAry.mnDestHeight / 
static_cast(aPosAry.mnSrcHeight);
 
 // If subsampling, use Bitmap::Scale() for subsampling of 
better quality.
+
+// but hidpi surfaces like the cairo one have their own 
scale, so don't downscale
+// past the surface scaling which can retain the extra 
detail
+double fScale(1.0);
+if (mpGraphics->ShouldDownscaleIconsAtSurface())
+{
+nScaleX *= fScale;
+nScaleY *= fScale;
+}
+
 if ( nScaleX < 1.0 || nScaleY < 1.0 )
 {
 aBmp.Scale(nScaleX, nScaleY);


[Libreoffice-commits] core.git: dbaccess/CppunitTest_dbaccess_firebird_test.mk embeddedobj/CppunitTest_embeddedobj_general.mk include/test oox/CppunitTest_oox_drawingml.mk oox/CppunitTest_oox_export.m

2022-11-11 Thread Xisco Fauli (via logerrit)
 dbaccess/CppunitTest_dbaccess_firebird_test.mk   |1 
 embeddedobj/CppunitTest_embeddedobj_general.mk   |1 
 include/test/unoapi_test.hxx |   27 --
 oox/CppunitTest_oox_drawingml.mk |1 
 oox/CppunitTest_oox_export.mk|1 
 oox/CppunitTest_oox_mathml.mk|1 
 oox/CppunitTest_oox_shape.mk |1 
 oox/CppunitTest_oox_vml.mk   |1 
 sc/CppunitTest_sc_functionlistobj.mk |1 
 sc/CppunitTest_sc_pdf_export.mk  |1 
 sc/common_unoapi_tests.mk|1 
 sd/CppunitTest_sd_filter_eppt.mk |1 
 sfx2/CppunitTest_sfx2_doc.mk |1 
 sfx2/CppunitTest_sfx2_view.mk|1 
 svx/CppunitTest_svx_styles.mk|1 
 sw/qa/inc/swmodeltestbase.hxx|   17 --
 sw/qa/unit/swmodeltestbase.cxx   |   48 --
 test/source/unoapi_test.cxx  |   60 ---
 writerfilter/CppunitTest_writerfilter_dmapper.mk |1 
 writerfilter/CppunitTest_writerfilter_rtftok.mk  |1 
 xmloff/CppunitTest_xmloff_draw.mk|1 
 xmloff/CppunitTest_xmloff_style.mk   |1 
 xmloff/CppunitTest_xmloff_text.mk|1 
 23 files changed, 97 insertions(+), 74 deletions(-)

New commits:
commit 7986d35eee84fdf391c563602fb348758e1cd254
Author: Xisco Fauli 
AuthorDate: Fri Nov 11 16:44:59 2022 +0100
Commit: Xisco Fauli 
CommitDate: Fri Nov 11 20:09:41 2022 +0100

move password handling from SwModelTestBase to UnoApiTest

so other places inheriting from UnoApiTest can also import/export
protected documents

Change-Id: I0e2716204dbb171c9e17e3939b266977e1b96dda
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/142592
Tested-by: Jenkins
Reviewed-by: Xisco Fauli 

diff --git a/dbaccess/CppunitTest_dbaccess_firebird_test.mk 
b/dbaccess/CppunitTest_dbaccess_firebird_test.mk
index 9b7af21ff31b..a8d4704eb1e9 100644
--- a/dbaccess/CppunitTest_dbaccess_firebird_test.mk
+++ b/dbaccess/CppunitTest_dbaccess_firebird_test.mk
@@ -18,6 +18,7 @@ $(eval $(call 
gb_CppunitTest_add_exception_objects,dbaccess_firebird_test, \
 $(eval $(call gb_CppunitTest_use_libraries,dbaccess_firebird_test, \
 comphelper \
 cppu \
+cppuhelper \
 dbaxml \
 firebird_sdbc \
 sal \
diff --git a/embeddedobj/CppunitTest_embeddedobj_general.mk 
b/embeddedobj/CppunitTest_embeddedobj_general.mk
index eb794f38548c..6c4014e2fc89 100644
--- a/embeddedobj/CppunitTest_embeddedobj_general.mk
+++ b/embeddedobj/CppunitTest_embeddedobj_general.mk
@@ -22,6 +22,7 @@ $(eval $(call 
gb_CppunitTest_add_exception_objects,embeddedobj_general, \
 $(eval $(call gb_CppunitTest_use_libraries,embeddedobj_general, \
 comphelper \
 cppu \
+cppuhelper \
 embobj \
 sal \
 subsequenttest \
diff --git a/include/test/unoapi_test.hxx b/include/test/unoapi_test.hxx
index 307d0f1a0589..0277131e31f7 100644
--- a/include/test/unoapi_test.hxx
+++ b/include/test/unoapi_test.hxx
@@ -14,7 +14,9 @@
 
 #include 
 
+#include 
 #include 
+#include 
 #include 
 #include 
 #include 
@@ -28,24 +30,32 @@ class OOO_DLLPUBLIC_TEST UnoApiTest : public 
test::BootstrapFixture, public unot
 public:
 UnoApiTest(OUString path);
 
-OUString createFileURL(std::u16string_view aFileBase);
-OUString loadFromURL(std::u16string_view aFileBase);
-
 virtual void setUp() override;
 virtual void tearDown() override;
 
+OUString createFileURL(std::u16string_view aFileBase);
+void load(const OUString& rURL, const char* pPassword = nullptr);
+OUString loadFromURL(std::u16string_view aFileBase, const char* pPassword 
= nullptr);
+
 css::uno::Any executeMacro(const OUString& rScriptURL,
const css::uno::Sequence& 
rParams = {});
 
 void save(const OUString& rFilter, const char* pPassword = nullptr);
 void saveAndClose(const OUString& rFilter);
-void saveAndReload(const OUString& rFilter);
+void saveAndReload(const OUString& rFilter, const char* pPassword = 
nullptr);
 
 std::unique_ptr parsePDFExport(const OString& 
rPassword = OString());
 
 void skipValidation() { mbSkipValidation = true; }
 void setFilterOptions(const OUString& rFilterOptions) { maFilterOptions = 
rFilterOptions; }
 
+void setImportFilterOptions(const OUString& rFilterOptions)
+{
+maImportFilterOptions = rFilterOptions;
+}
+
+void setImportFilterName(const OUString& rFilterName) { maImportFilterName 
= rFilterName; }
+
 protected:
 // reference to document component that we are testing
 css::uno::Reference mxComponent;
@@ -54,10 +64,19 @@ protected:
 
 SvMemoryStream maMemory; // Underlying memory for parsed PDF files.
 
+rtl::Reference xInteractionHandler;
+
 private:
+

[Libreoffice-bugs] [Bug 126546] Reset character style on paragraph break (see comment 23)

2022-11-11 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=126546

--- Comment #36 from Adalbert Hanßen  ---
(In reply to ajlittoz from comment #34)
> ...
> 
> Also, when I split a paragraph, I expect *all* layers to keep their present
> settings. 

I agree *if there are characters right to the split point*. When sketching some
document, I start with headings only. In order to add on, I enter a space
before the paragraph mark and split before that space, then a headline of the
same level is created (otherwise it would continue with TextBody, the default
after any heading in my default stylesheet). I remove the space immediately
when actually writing the next heading. If I wnat to change levels, I look up
at the display of the headline-level and press  as needed.

The general rule seems to be: Continue formatting in the same way as *to the
left of the insertion point*. This rule is broken by .

normal*bold*   in a line, adding xyz after normal continue normal. It yields
normalxyz*bold*


However: pressing  and continue writing xyz yields

normal
*xyzbold*

Try it!

> 
> ... A paragraph can be associated with a list style. There are two 
> schools for this: the style one where the list style is declared in 
> the PS, making the PS dedicated to list item, and the DF one where 
> a toolbar button is pressed to turn the paragraph into a list item. 
> When Enter is pressed, most users expect the "list attribute" to
> remain active so that the next item is entered without any other manual
> operation. 

agreed for the next line becoming a list item. You can easily terminate the
list property by pressing  twice. You can easily prevent a number or
bullet by pressing  after . Getting rid of formatting can be
more difficult since it can stem from DF or CS.

>...
> PS: (see end of comment 33) the present formatting state is reflected in the
> toolbar buttons. Of course, this doesn't tell which layer activated it (PS,
> CS, DF). But colouring the button might be impossible because of the
> "themes". Status colouring would override theme colouring (or conflict with
> it)

agreed: Then we need other means to see it a glance. Two years ago, Heiko
Tietze made a nice proposal:
https://design.blog.documentfoundation.org/2019/11/05/proposal-to-conveniently-highlight-and-inspect-styles-in-libreoffice-writer/

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Libreoffice-bugs] [Bug 152009] New: Writer no longer shows track changes made in Word

2022-11-11 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=152009

Bug ID: 152009
   Summary: Writer no longer shows track changes made in Word
   Product: LibreOffice
   Version: 4.2.3.3 release
  Hardware: All
OS: Windows (All)
Status: UNCONFIRMED
  Severity: normal
  Priority: medium
 Component: Writer
  Assignee: libreoffice-bugs@lists.freedesktop.org
  Reporter: mikemckib...@outlook.com

I use Writer on Windows 10 PC and Windows 11 laptop and ran into this problem
yesterday. Any changes made by someone else in Word do not show up in my LO
document, whether I save it in Word or as a .odt file. I reset LO in safe mode
but the same thing happened so I don't think I have a corrupt user file. I keep
Windows and LO updated and am not aware of any settings changes that might have
had this result.

-- 
You are receiving this mail because:
You are the assignee for the bug.

Build failing on Windows when adding "ja" in "with-lang"

2022-11-11 Thread Julien
Hello,

[build CXX] chart2/source/controller/sidebar/ChartSidebarModifyListener.cxx
gawk: 
C:/cygwin/home/serva/lode/dev/core/solenv/gbuild/platform/filter-showIncludes.awk:45:
 (FILENAME=- FNR=2) warning: Invalid multibyte data detected. There may be a 
mismatch between your data and your locale
Remarque□: inclusion du fichier□:  
C:\cygwin\home\serva\lode\dev\core\chart2\source\controller\sidebar\ChartSidebarModifyListener.hxx
[build CXX] chart2/source/controller/sidebar/ChartSidebarSelectionListener.cxx
gawk: 
C:/cygwin/home/serva/lode/dev/core/solenv/gbuild/platform/filter-showIncludes.awk:45:
 (FILENAME=- FNR=2) warning: Invalid multibyte data detected. There may be a 
mismatch between your data and your locale
Remarque□: inclusion du fichier□:  
C:\cygwin\home\serva\lode\dev\core\chart2\source\controller\sidebar\ChartSidebarSelectionListener.hxx
[build CXX] chart2/source/controller/sidebar/ChartTypePanel.cxx
gawk: 
C:/cygwin/home/serva/lode/dev/core/solenv/gbuild/platform/filter-showIncludes.awk:45:
 (FILENAME=- FNR=2) warning: Invalid multibyte data detected. There may be a 
mismatch between your data and your locale
Remarque□: inclusion du fichier□:  
C:\cygwin\home\serva\lode\dev\core\chart2\source\controller\sidebar\ChartTypePanel.hxx
...
Trying to reproduce a bug which seems specific to Windows with Japanese UI, I 
added "ja" in "with-lang" of my autogen.input.
But even after a build from scratch, I got:
[build CXX] chart2/source/controller/uitest/uiobject.cxx
gawk: 
C:/cygwin/home/serva/lode/dev/core/solenv/gbuild/platform/filter-showIncludes.awk:45:
 (FILENAME=- FNR=2) warning: Invalid multibyte data detected. There may be a 
mismatch between your data and your locale
Remarque□: inclusion du fichier□:  
C:\cygwin\home\serva\lode\dev\core\chart2\source\controller\inc\uiobject.hxx
Remarque□: inclusion du fichier□:   
C:\cygwin\home\serva\lode\dev\core\include\vcl/uitest/uiobject.hxx
Remarque□: inclusion du fichier□:  
C:\cygwin\home\serva\lode\dev\core\chart2\source\controller\inc\ObjectHierarchy.hxx
[build DEP] LNK:Library/chartcontrollerlo.dll.d
[build LNK] Library/chartcontrollerlo.dll
gawk: 
C:/cygwin/home/serva/lode/dev/core/solenv/gbuild/platform/filter-creatingLibrary.awk:31:
 (FILENAME=- FNR=1) warning: Invalid multibyte data detected. There may be a 
mismatch between your data and your locale
[build CMP] chart2/source/controller/chartcontroller
[build BIN] chart2
[build MO ] chartes
C:/cygwin/bin/msguniq.exe: error while loading shared libraries: ?: cannot open 
shared object file: No such file or directory
C:/cygwin/bin/msgfmt.exe: error while loading shared libraries: 
cygunistring-5.dll: cannot open shared object file: No such file or directory
make[1]: *** 
[C:/cygwin/home/serva/lode/dev/core/solenv/gbuild/AllLangMoTarget.mk:38: 
C:/cygwin/home/serva/lode/dev/core/workdir/MoTarget/chartes.mo] Error 127

Any idea what to do here?

Julien


[Libreoffice-commits] core.git: compilerplugins/clang solenv/CompilerTest_compilerplugins_clang.mk

2022-11-11 Thread Stephan Bergmann (via logerrit)
 compilerplugins/clang/constmove.cxx  |   85 +++
 compilerplugins/clang/test/constmove.cxx |   25 +++
 solenv/CompilerTest_compilerplugins_clang.mk |1 
 3 files changed, 111 insertions(+)

New commits:
commit 4c9093c95445c154c4ce7db1756ca936ea0752ca
Author: Stephan Bergmann 
AuthorDate: Fri Nov 11 10:09:16 2022 +0100
Commit: Stephan Bergmann 
CommitDate: Fri Nov 11 19:37:16 2022 +0100

New loplugin:constmove

"Find occurrences of std::move on const-qualified types.  While there might
theoretically be legitimate uses for such (for which this plugin would 
generate
false positives and would need to be updated), in practice they tend to 
point at
suspicious code that should be cleaned up in some way."

(All issues found for a Linux build have already been addressed with eleven
recent commits mentioning in their commit messages:  "I came across this 
code
with an upcoming loplugin:constmove that flags suspicious uses of std::move
involving const-qualified types.")

Change-Id: I891a66eb0ec5f9b7d93536bbccea0359893383df
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/142589
Tested-by: Jenkins
Reviewed-by: Stephan Bergmann 

diff --git a/compilerplugins/clang/constmove.cxx 
b/compilerplugins/clang/constmove.cxx
new file mode 100644
index ..63bafa188979
--- /dev/null
+++ b/compilerplugins/clang/constmove.cxx
@@ -0,0 +1,85 @@
+/* -*- Mode: C++; tab-width: 4; indent-tabs-mode: nil; c-basic-offset: 4; 
fill-column: 100 -*- */
+/*
+ * This file is part of the LibreOffice project.
+ *
+ * This Source Code Form is subject to the terms of the Mozilla Public
+ * License, v. 2.0. If a copy of the MPL was not distributed with this
+ * file, You can obtain one at http://mozilla.org/MPL/2.0/.
+ */
+
+// Find occurrences of std::move on const-qualified types.  While there might 
theoretically be
+// legitimate uses for such (for which this plugin would generate false 
positives and would need to
+// be updated), in practice they tend to point at suspicious code that should 
be cleaned up in some
+// way.
+
+#ifndef LO_CLANG_SHARED_PLUGINS
+
+#include "check.hxx"
+#include "plugin.hxx"
+
+namespace
+{
+class ConstMove final : public loplugin::FilteringPlugin
+{
+public:
+explicit ConstMove(loplugin::InstantiationData const& data)
+: FilteringPlugin(data)
+{
+}
+
+bool preRun() override { return compiler.getLangOpts().CPlusPlus; }
+
+void run() override
+{
+if (preRun())
+{
+TraverseDecl(compiler.getASTContext().getTranslationUnitDecl());
+}
+}
+
+bool VisitCallExpr(CallExpr const* expr)
+{
+if (ignoreLocation(expr))
+{
+return true;
+}
+auto const t = expr->getType();
+if (!t.isConstQualified())
+{
+return true;
+}
+auto const d = expr->getDirectCallee();
+if (d == nullptr)
+{
+return true;
+}
+if (!loplugin::DeclCheck(d).Function("move").StdNamespace())
+{
+return true;
+}
+switch (expr->getNumArgs())
+{
+case 0:
+return true;
+case 1:
+break;
+default:
+if (!isa(expr->getArg(1)))
+{
+return true;
+}
+break;
+}
+report(DiagnosticsEngine::Warning, "suspicious 'std::move' from %0 to 
const-qualified %1",
+   expr->getExprLoc())
+<< expr->getArg(0)->IgnoreImplicit()->getType() << t << 
expr->getSourceRange();
+return true;
+}
+};
+
+static loplugin::Plugin::Registration constmove("constmove");
+}
+
+#endif
+
+/* vim:set shiftwidth=4 softtabstop=4 expandtab cinoptions=b1,g0,N-s 
cinkeys+=0=break: */
diff --git a/compilerplugins/clang/test/constmove.cxx 
b/compilerplugins/clang/test/constmove.cxx
new file mode 100644
index ..f6d2ed3ac9bf
--- /dev/null
+++ b/compilerplugins/clang/test/constmove.cxx
@@ -0,0 +1,25 @@
+/* -*- Mode: C++; tab-width: 4; indent-tabs-mode: nil; c-basic-offset: 4; 
fill-column: 100 -*- */
+/*
+ * This file is part of the LibreOffice project.
+ *
+ * This Source Code Form is subject to the terms of the Mozilla Public
+ * License, v. 2.0. If a copy of the MPL was not distributed with this
+ * file, You can obtain one at http://mozilla.org/MPL/2.0/.
+ */
+
+#include 
+
+struct S
+{
+};
+
+void f(S const& s1, S s2)
+{
+// expected-error-re@+1 {{suspicious 'std::move' from 'const S' to 
const-qualified '{{.+}}' (aka 'const S') [loplugin:constmove]}}
+S v1(std::move(s1));
+(void)v1;
+S v2(std::move(s2));
+(void)v2;
+}
+
+/* vim:set shiftwidth=4 softtabstop=4 expandtab cinoptions=b1,g0,N-s 
cinkeys+=0=break: */
diff --git a/solenv/CompilerTest_compilerplugins_clang.mk 

[Libreoffice-commits] core.git: filter/qa filter/source

2022-11-11 Thread Miklos Vajna (via logerrit)
 filter/qa/unit/svg.cxx  |   53 
 filter/source/svg/svgwriter.cxx |5 +++
 2 files changed, 58 insertions(+)

New commits:
commit c725028f15c36fc626d9ad8cdc288eb73c3e2643
Author: Miklos Vajna 
AuthorDate: Fri Nov 11 15:58:11 2022 +0100
Commit: Miklos Vajna 
CommitDate: Fri Nov 11 19:35:55 2022 +0100

SVG export: fix handling of semi-transparent, multi-para shape text

The bugdoc had a shape with two paragraphs. The export of the second 
paragraph
went wrong: the position & size of the text was larger than expected.

This problem was specific to semi-transparent text.
SVGTextWriter::setTextPosition() is recursive in this case. The 
non-transparent
case left nCurAction unchanged in the outer setTextPosition() and it 
returned 1
("text is found"). The semi-transparent case changed nCurAction by +2 and
returned 0 ("text is not found"). This led to all sorts of trouble, 
including
mismatching Push() and Pop() calls on the output device when replaying the
metafile.

Fix the problem by routing the empty state from the inner setTextPosition() 
to
the outer one: if we return 1 ("text is found"), then we know that the 
state is
non-empty. Once the empty state is correct in the outer setTextPosition(), 
then
even the transparent case also leaves nCurAction unchanged and the whole 
shape
text has the correct position and size.

I forgot to update this empty state in ther outer setTextPosition() in 
commit
666f252457bdb4371d15380a0289e107b2dfbe84 (SVG export: fix lost 
semi-transparent
text on shapes, 2020-07-17).

Change-Id: I7dc93fe13c4510220bf09a388e742799ed042510
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/142590
Reviewed-by: Miklos Vajna 
Tested-by: Jenkins

diff --git a/filter/qa/unit/svg.cxx b/filter/qa/unit/svg.cxx
index 90de658cf50f..ea31a74447f0 100644
--- a/filter/qa/unit/svg.cxx
+++ b/filter/qa/unit/svg.cxx
@@ -19,6 +19,8 @@
 #include 
 #include 
 #include 
+#include 
+#include 
 
 #include 
 #include 
@@ -141,6 +143,57 @@ CPPUNIT_TEST_FIXTURE(SvgFilterTest, 
testSemiTransparentText)
 assertXPath(pXmlDoc, 
"//svg:text[2]/svg:tspan/svg:tspan/svg:tspan[@fill-opacity]", 0);
 }
 
+CPPUNIT_TEST_FIXTURE(SvgFilterTest, testSemiTransparentMultiParaText)
+{
+// Given a shape with semi-transparent, multi-paragraph text:
+mxComponent
+= loadFromDesktop("private:factory/simpress", 
"com.sun.star.drawing.DrawingDocument");
+uno::Reference xFactory(mxComponent, 
uno::UNO_QUERY);
+uno::Reference xShape(
+xFactory->createInstance("com.sun.star.drawing.TextShape"), 
uno::UNO_QUERY);
+uno::Reference 
xDrawPagesSupplier(mxComponent, uno::UNO_QUERY);
+uno::Reference 
xDrawPage(xDrawPagesSupplier->getDrawPages()->getByIndex(0),
+   uno::UNO_QUERY);
+xDrawPage->add(xShape);
+xShape->setSize(awt::Size(1, 1));
+uno::Reference xShapeText(xShape, uno::UNO_QUERY);
+uno::Reference xCursor = xShapeText->createTextCursor();
+xShapeText->insertString(xCursor, "foo", /*bAbsorb=*/false);
+xShapeText->insertControlCharacter(xCursor, 
text::ControlCharacter::APPEND_PARAGRAPH,
+   /*bAbsorb=*/false);
+xShapeText->insertString(xCursor, "bar", /*bAbsorb=*/false);
+uno::Reference xShapeProps(xShape, uno::UNO_QUERY);
+xShapeProps->setPropertyValue("CharColor", 
uno::Any(static_cast(0xff)));
+xShapeProps->setPropertyValue("CharTransparence", 
uno::Any(static_cast(20)));
+
+// When exporting to SVG:
+uno::Reference xStorable(mxComponent, 
uno::UNO_QUERY_THROW);
+SvMemoryStream aStream;
+uno::Reference xOut = new 
utl::OOutputStreamWrapper(aStream);
+utl::MediaDescriptor aMediaDescriptor;
+aMediaDescriptor["FilterName"] <<= OUString("draw_svg_Export");
+aMediaDescriptor["OutputStream"] <<= xOut;
+xStorable->storeToURL("private:stream", 
aMediaDescriptor.getAsConstPropertyValueList());
+aStream.Seek(STREAM_SEEK_TO_BEGIN);
+
+// Then make sure that the two semi-tranparent paragraphs have the same X 
position:
+xmlDocUniquePtr pXmlDoc = parseXmlStream();
+assertXPath(pXmlDoc, 
"(//svg:g[@class='TextShape']//svg:tspan[@class='TextPosition'])[1]", "x",
+"250");
+assertXPath(pXmlDoc,
+
"(//svg:g[@class='TextShape']//svg:tspan[@class='TextPosition'])[1]/svg:tspan",
+"fill-opacity", "0.8");
+// Without the accompanying fix in place, this test would have failed with:
+// - Expected: 250
+// - Actual  : 8819
+// i.e. the X position of the second paragraph was wrong.
+assertXPath(pXmlDoc, 
"(//svg:g[@class='TextShape']//svg:tspan[@class='TextPosition'])[2]", "x",
+"250");
+assertXPath(pXmlDoc,
+

[Libreoffice-bugs] [Bug 151858] Crash in: __scrt_throw_std_bad_alloc() memory usage keeps increasing after file open until system freeze or crash

2022-11-11 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=151858

--- Comment #4 from ScootrKDEbug Richards  ---
Is there a workaround for this? I really need that file that crashes on load.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Libreoffice-bugs] [Bug 152008] Critical, Freezes when switching thru Document Windows

2022-11-11 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=152008

--- Comment #1 from G  ---
Also happened on the previous version 7.3.6

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Libreoffice-bugs] [Bug 145648] Different kerning when comparing Text and Comments

2022-11-11 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=145648

--- Comment #7 from Rafael Lima  ---
Created attachment 183546
  --> https://bugs.documentfoundation.org/attachment.cgi?id=183546=edit
Comparison of the text rendering (ODG)

Here I made a comparison of the rendered document and comment to highlight how
different they are.

I did it using the same approach as Telesto. I took a screenshot of both the
comment and the text and then placed them on top of each other.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Libreoffice-bugs] [Bug 152008] New: Critical, Freezes when switching thru Document Windows

2022-11-11 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=152008

Bug ID: 152008
   Summary: Critical, Freezes when switching thru Document Windows
   Product: LibreOffice
   Version: 7.3.7.2 release
  Hardware: ARM
OS: macOS (All)
Status: UNCONFIRMED
  Severity: normal
  Priority: medium
 Component: Calc
  Assignee: libreoffice-bugs@lists.freedesktop.org
  Reporter: guillermo_...@hotmail.com

Description:
Freezes when switching Documents Windows. 
Open Libreoffice, create (or open) a file, then create (or open) another file,
when you switch from one document window to the next, after less than 5 seconds
later it freezes.
Must Force Quit. After restart "fixes" the files, but you can't have two files
open at the same time. It is really bad when you must work with several files
open at one time.
Might be 2 empty files or  very complex large files, it doesn't matter.
Same happens with Writer.

MacOS M2 Running Ventura
Version:
7.3.7.2 / LibreOffice Community
Build:
Environment.
e114eadc50a9ff8d8c8a0567d...
CPU threads: 8: OS: Mac OS X 13.0
User Interface: Ulrender: default; VCL: os Locale:
en-US (en_US.UTF-8); Ul: en-US
Misc:
Calc: threaded

Steps to Reproduce:
1.Open Libreoffice
2.Open/Create a file, then open/create another file
3.Switch from one file to the other. 
4.Wait a couple of seconds and it Freezes up

Actual Results:
Crash

Expected Results:
Keep working as usual


Reproducible: Always


User Profile Reset: No

Additional Info:
It started happening after a MacOS Update to Ventura, I never had anything like
this before.
Now, I have to open one file, work with it, remember what I did, close it, open
the related file, "Allow Updating" (it stills loads the stuff from the other
file), and keep working after what I did on the other file.
It is Very, Very difficult and time consuming.

It does the same if you do it with writer, just open writer, create a file,
then create another empty file, switch windows and it Freezes

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Libreoffice-bugs] [Bug 145648] Different kerning when comparing Text and Comments

2022-11-11 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=145648

--- Comment #6 from Rafael Lima  ---
Created attachment 183545
  --> https://bugs.documentfoundation.org/attachment.cgi?id=183545=edit
Sample file (same font size in text and comment)

(In reply to Caolán McNamara from comment #5)
> I haven't checked this case yet, but it would be interesting to reexamine
> with a recent daily build and see what differences might persist.

So I built the current master today and the issue with the comments still
persist. The rendering of text in the comment box and in the document are very
different.

Build info:

Version: 7.5.0.0.alpha0+ (X86_64) / LibreOffice Community
Build ID: c819aa06069ec3ea4f2f51d26a77f455740b828f
CPU threads: 16; OS: Linux 5.15; UI render: default; VCL: kf5 (cairo+xcb)
Locale: pt-BR (pt_BR.UTF-8); UI: en-US
Calc: CL threaded

Here is a new sample file. It's very similar to the first one, but now the
comment and the document use the same font size (12pt). Notice that the width
of the rendered text changes a lot, as well as the spacing between characters.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Libreoffice-bugs] [Bug 152004] Calc EDITING : after pasting a block, pressing Shift-Ctrl-Down does not go bottom

2022-11-11 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=152004

--- Comment #4 from nicolas.duvern...@laposte.net ---
Hello
I created a block 2columns x 10 rows with some data in it in cells A1:B11.
Select them, copy, and paste at G6
Press Ctrl-Down (a previous comment was right, I apologise...), and selection
cell comes to G11, whereas I expect it to come to G16
Or, even more funny :
Start with some data in A1:B11.
Select cell A1. press Shift-Control-Down then Shift-Control-Right. The block is
now fully selected, and most highlighted cell is still A1.
Now press Ctrl-Down, and you land at row 1048566.
OK, let's go back to A11, and paste.
Then Ctrl-Down and you arrive in A33.
Copy once again the block in A23. Ctrl-Down lands in A55.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Libreoffice-bugs] [Bug 151996] crash when clicking autofilter

2022-11-11 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=151996

--- Comment #4 from Christopher M. Penalver  ---
Created attachment 183544
  --> https://bugs.documentfoundation.org/attachment.cgi?id=183544=edit
sudo dtruss -n soffice.txt

Opened file, started dtruss, reproduced crash, and then created this
attachment.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Libreoffice-bugs] [Bug 103239] [META] Toolbars bugs and enhancements

2022-11-11 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=103239

Eyal Rozenberg  changed:

   What|Removed |Added

 Depends on|38850   |


Referenced Bugs:

https://bugs.documentfoundation.org/show_bug.cgi?id=38850
[Bug 38850] In Tools > Options > View - add an option to control appearance of
context-sensitive toolbars (on, off, automatic)
-- 
You are receiving this mail because:
You are the assignee for the bug.

[Libreoffice-bugs] [Bug 38850] In Tools > Options > View - add an option to control appearance of context-sensitive toolbars (on, off, automatic)

2022-11-11 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=38850

Eyal Rozenberg  changed:

   What|Removed |Added

 Blocks|103239  |


Referenced Bugs:

https://bugs.documentfoundation.org/show_bug.cgi?id=103239
[Bug 103239] [META] Toolbars bugs and enhancements
-- 
You are receiving this mail because:
You are the assignee for the bug.

[Libreoffice-bugs] [Bug 38850] In Tools > Options > View - add an option to control appearance of context-sensitive toolbars (on, off, automatic)

2022-11-11 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=38850

Eyal Rozenberg  changed:

   What|Removed |Added

 Blocks||84909


Referenced Bugs:

https://bugs.documentfoundation.org/show_bug.cgi?id=84909
[Bug 84909] [META] Enhancing Impress/Draw toolbars and context menu
-- 
You are receiving this mail because:
You are the assignee for the bug.

[Libreoffice-bugs] [Bug 84909] [META] Enhancing Impress/Draw toolbars and context menu

2022-11-11 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=84909

Eyal Rozenberg  changed:

   What|Removed |Added

 Depends on||38850


Referenced Bugs:

https://bugs.documentfoundation.org/show_bug.cgi?id=38850
[Bug 38850] In Tools > Options > View - add an option to control appearance of
context-sensitive toolbars (on, off, automatic)
-- 
You are receiving this mail because:
You are the assignee for the bug.

[Libreoffice-commits] core.git: .git-hooks/pre-commit

2022-11-11 Thread Stephan Bergmann (via logerrit)
 .git-hooks/pre-commit |   53 +-
 1 file changed, 48 insertions(+), 5 deletions(-)

New commits:
commit c819aa06069ec3ea4f2f51d26a77f455740b828f
Author: Stephan Bergmann 
AuthorDate: Mon Nov 7 19:59:01 2022 +0100
Commit: Stephan Bergmann 
CommitDate: Fri Nov 11 17:18:43 2022 +0100

.git-hook: Emit some warning about clang-format and renamed files

...to avoid misguided clang-format'ing of previously excluded files, as
discussed in the comment at


"sc: factor out common code in make files".

(Though this still doesn't warn about cases where some excluded file got 
renamed
and the excludelist wasn't updated and the user already erroneously
clang-format'ed the renamed file before this commit attempt.   Also, I don't
know how best to integrate this with libreoffice.autostyle, so just ignore
libreoffice.autostyle for now when any suspicious renames are detected.)

Change-Id: I8d176ce536548b67f5b2af100f579f362764b06b
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/142394
Tested-by: Jenkins
Reviewed-by: Stephan Bergmann 

diff --git a/.git-hooks/pre-commit b/.git-hooks/pre-commit
index a3cef10ee5f4..51c1de751672 100755
--- a/.git-hooks/pre-commit
+++ b/.git-hooks/pre-commit
@@ -184,6 +184,7 @@ sub check_style($)
 my ($h) = @_;
 my $src = ClangFormat::get_extension_regex();
 my @bad_names = ();
+my @bad_renames = ();
 my $clang_format = ClangFormat::find();
 
 ## Check if ClangFormat has get_excludelist or the old
@@ -193,6 +194,17 @@ sub check_style($)
 if ($@) { $excluded_list_names = ClangFormat::get_blacklist(); }
 else{ $excluded_list_names = ClangFormat::get_excludelist(); }
 
+# Get a list of renamed files.
+my %renames; # key is target pathname, value is source pathname
+open (IN, "git diff-index --cached --find-renames --diff-filter=R 
--name-status $h |")
+|| die "Cannot run git diff.";
+while (my $line = )
+{
+chomp $line;
+$line =~ /^[^\t]+\t([^\t]+)\t([^\t]+)$/ ||  die "Unexpected response 
line: $line";
+$renames{$2} = $1;
+}
+
 # Get a list of non-deleted changed files.
 open (FILES, "git diff-index --cached --diff-filter=AM --name-only $h |") 
||  die "Cannot run git diff.";
 while (my $filename = )
@@ -233,21 +245,52 @@ sub check_style($)
 }
 if (!ClangFormat::check_style($clang_format, $filename))
 {
-push @bad_names, $filename;
+if (defined($renames{$filename}))
+{
+push @bad_renames, $filename;
+}
+else
+{
+push @bad_names, $filename;
+}
 }
 }
 }
 
 # Enforce style.
-if (scalar @bad_names)
+if (scalar @bad_names || scalar @bad_renames)
 {
 my $autostyle = `git config libreoffice.autostyle`;
 chomp $autostyle;
-if ($autostyle ne "true")
+if ($autostyle ne "true" or scalar @bad_renames)
 {
 print("\nThe above differences were found between the code to 
commit \n");
-print("and the clang-format rules. You can apply these changes 
with:\n");
-print("\n$clang_format -i " . join(" ", @bad_names) . "\n\n");
+print("and the clang-format rules.\n");
+if (scalar @bad_names)
+{
+print("You can apply these changes with:\n");
+print("\n$clang_format -i " . join(" ", @bad_names) . "\n\n");
+}
+if (scalar @bad_renames)
+{
+print("\nATTENTION: Of files detected as renamed by git, the 
following ones are\n");
+print("not clang-format'ed and are not listed in the 
excludelist. If they are\n");
+print("renames of previously excluded files, they should be 
added to the\n");
+print("excludelist:\n\n");
+foreach my $name (@bad_renames)
+{
+if (exists($excluded_list_names->{$renames{$name}}))
+{
+print("* $name got renamed from $renames{$name},\n");
+print("which is even still listed in the 
excludelist!\n");
+}
+else
+{
+print("* $name\n");
+}
+}
+print("\n");
+}
 print("Aborting commit. Apply changes and commit again or skip 
checking\n");
 print("with --no-verify (not recommended).\n");
 exit(1);


[Libreoffice-bugs] [Bug 152003] Random empty text files appear in desktop most each time I use LibreOffice

2022-11-11 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=152003

--- Comment #3 from Victor Marin  ---
Currently, I'm running a fresh install of Xubuntu 22.04 LTS (after that I tried
Kubuntu 22.04 too). I didn't change anything on LibreOffice. 

The OS is configured for Spanish language.

The LibreOffice path for Temp files is set up at: /temp.

The path for Documents it's: /home/myusername/Documentos.

Such files don't appear when I use Firefox, but when I use Writer.

If LibreOffice 7.3 includes new WebDAV based on libcurl, perhaps it's it.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Libreoffice-bugs] [Bug 152003] Random empty text files appear in desktop most each time I use LibreOffice

2022-11-11 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=152003

--- Comment #2 from Mike Kaganski  ---
AFAIK LibreOffice has no code to create a .part files. OTOH, FireFox download
does create those (mentioned e.g. in bug 135333). On the third side, 7.3
introduced new WebDAV based on libcurl...

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Libreoffice-bugs] [Bug 152007] New: Escorts in Mumbai

2022-11-11 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=152007

Bug ID: 152007
   Summary: Escorts in Mumbai
   Product: LibreOffice Online
   Version: unspecified
  Hardware: All
OS: All
Status: UNCONFIRMED
  Severity: normal
  Priority: medium
 Component: LibreOffice
  Assignee: libreoffice-bugs@lists.freedesktop.org
  Reporter: rupalsharma9...@gmail.com

Rupal Sharma is a independent escorts in Mumbai for peaceful entertainment and
enjoyment Escorts service at very low rates 24/7.
https://www.rupalsharma.com
https://www.rupalsharma.com/vile-parle-escorts.html
https://www.rupalsharma.com/escort-in-juhu.html
https://www.rupalsharma.com/escort-in-bandra.html

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Libreoffice-bugs] [Bug 151996] crash when clicking autofilter

2022-11-11 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=151996

Christopher M. Penalver  changed:

   What|Removed |Added

 Ever confirmed|1   |0
 Status|NEEDINFO|UNCONFIRMED

--- Comment #3 from Christopher M. Penalver  ---
Hi Stéphane Guillou (stragu),

Thanks for the quick response!

For now, while I'm not going down the rabbit hole of document carving, if you
advise which log you want, and/or provide fully detailed step-by-step
instructions on gathering debugging log for macOS (not ahead of this) I don't
have a problem providing.

There is nothing logged in console about a crash, otherwise would have already
posted.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Libreoffice-commits] core.git: sw/qa

2022-11-11 Thread Xisco Fauli (via logerrit)
 sw/qa/extras/uiwriter/uiwriter6.cxx |  184 ++--
 sw/qa/inc/swmodeltestbase.hxx   |5 
 sw/qa/unit/swmodeltestbase.cxx  |7 -
 3 files changed, 95 insertions(+), 101 deletions(-)

New commits:
commit 0443d6d253eb2b8aaab6fd37af4b08c7e21e37c9
Author: Xisco Fauli 
AuthorDate: Fri Nov 11 15:20:49 2022 +0100
Commit: Xisco Fauli 
CommitDate: Fri Nov 11 16:32:13 2022 +0100

SwModelTestBase: get rid of getSwXTextDocument

no much value in having it around

Change-Id: I864f039c0129a922c8d86b5db0a18158f2155add
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/142588
Tested-by: Jenkins
Reviewed-by: Xisco Fauli 

diff --git a/sw/qa/extras/uiwriter/uiwriter6.cxx 
b/sw/qa/extras/uiwriter/uiwriter6.cxx
index 3adb30fa4032..f4cd3cbac52c 100644
--- a/sw/qa/extras/uiwriter/uiwriter6.cxx
+++ b/sw/qa/extras/uiwriter/uiwriter6.cxx
@@ -62,12 +62,12 @@ sal_Int32 lcl_getAttributeIDFromHints(const SwpHints& hints)
 return -1;
 }
 
-void emulateTyping(SwXTextDocument& rXTextDocument, const std::u16string_view& 
rStr)
+void emulateTyping(SwXTextDocument& rTextDoc, const std::u16string_view& rStr)
 {
 for (const char16_t c : rStr)
 {
-rXTextDocument.postKeyEvent(LOK_KEYEVENT_KEYINPUT, c, 0);
-rXTextDocument.postKeyEvent(LOK_KEYEVENT_KEYUP, c, 0);
+rTextDoc.postKeyEvent(LOK_KEYEVENT_KEYINPUT, c, 0);
+rTextDoc.postKeyEvent(LOK_KEYEVENT_KEYUP, c, 0);
 Scheduler::ProcessEventsToIdle();
 }
 }
@@ -1372,8 +1372,8 @@ CPPUNIT_TEST_FIXTURE(SwUiWriterTest6, testTdf124603)
 
 // Type a correct word
 
-SwXTextDocument& rXTextDocument = getSwXTextDocument();
-emulateTyping(rXTextDocument, u"the ");
+SwXTextDocument* pTextDoc = 
dynamic_cast(mxComponent.get());
+emulateTyping(*pTextDoc, u"the ");
 SwCursorShell* pShell(pDoc->GetEditShell());
 SwTextNode* pNode = pShell->GetCursor()->GetPointNode().GetTextNode();
 // no bad word
@@ -1382,7 +1382,7 @@ CPPUNIT_TEST_FIXTURE(SwUiWriterTest6, testTdf124603)
 // Create a bad word from the good: "the" -> "thex"
 
 pWrtShell->Left(SwCursorSkipMode::Chars, /*bSelect=*/false, 1, 
/*bBasicCall=*/false);
-emulateTyping(rXTextDocument, u"x");
+emulateTyping(*pTextDoc, u"x");
 CPPUNIT_ASSERT(pNode->GetWrong());
 // tdf#92036 pending spell checking
 bool bPending = !pNode->GetWrong() || !pNode->GetWrong()->Count();
@@ -1415,7 +1415,7 @@ CPPUNIT_TEST_FIXTURE(SwUiWriterTest6, 
testRedlineAutoCorrect)
 
 SwWrtShell* pWrtShell = pDoc->GetDocShell()->GetWrtShell();
 CPPUNIT_ASSERT(pWrtShell);
-SwXTextDocument& rXTextDocument = getSwXTextDocument();
+SwXTextDocument* pTextDoc = 
dynamic_cast(mxComponent.get());
 
 // show tracked deletion with enabled change tracking
 RedlineFlags const nMode(pWrtShell->GetRedlineFlags() | RedlineFlags::On);
@@ -1426,7 +1426,7 @@ CPPUNIT_TEST_FIXTURE(SwUiWriterTest6, 
testRedlineAutoCorrect)
 CPPUNIT_ASSERT_MESSAGE("redlining should be on",
pDoc->getIDocumentRedlineAccess().IsRedlineOn());
 
-emulateTyping(rXTextDocument, u" ");
+emulateTyping(*pTextDoc, u" ");
 
 // tdf#83419 This was "Ts " removing the deletion of "t" silently by 
sentence capitalization
 OUString sReplaced("ts ");
@@ -1438,7 +1438,7 @@ CPPUNIT_TEST_FIXTURE(SwUiWriterTest6, 
testRedlineAutoCorrect)
 // repeat it with not visible redlining
 dispatchCommand(mxComponent, ".uno:Undo", {});
 
-emulateTyping(rXTextDocument, u" ");
+emulateTyping(*pTextDoc, u" ");
 
 sReplaced = "S ";
 CPPUNIT_ASSERT_EQUAL(sReplaced, getParagraph(1)->getString());
@@ -1455,25 +1455,25 @@ CPPUNIT_TEST_FIXTURE(SwUiWriterTest6, 
testRedlineAutoCorrect)
 dispatchCommand(mxComponent, ".uno:Undo", {});
 dispatchCommand(mxComponent, ".uno:Undo", {});
 
-emulateTyping(rXTextDocument, u"et ");
+emulateTyping(*pTextDoc, u"et ");
 // This was "Ttest" removing the tracked deletion silently.
 // Don't replace, if a redline starts or ends within the text.
 sReplaced = "tset ";
 CPPUNIT_ASSERT_EQUAL(sReplaced, getParagraph(1)->getString());
 
 // Otherwise replace it
-emulateTyping(rXTextDocument, u"tset ");
+emulateTyping(*pTextDoc, u"tset ");
 sReplaced = "tset test ";
 CPPUNIT_ASSERT_EQUAL(sReplaced, getParagraph(1)->getString());
 
 // Including capitalization
-emulateTyping(rXTextDocument, u"end. word ");
+emulateTyping(*pTextDoc, u"end. word ");
 sReplaced = "tset test end. Word ";
 CPPUNIT_ASSERT_EQUAL(sReplaced, getParagraph(1)->getString());
 
 // tracked deletions after the correction point doesn't affect autocorrect
 dispatchCommand(mxComponent, ".uno:GoToStartOfDoc", {});
-emulateTyping(rXTextDocument, u"a ");
+emulateTyping(*pTextDoc, u"a ");
 sReplaced = "A tset test end. Word ";
 CPPUNIT_ASSERT_EQUAL(sReplaced, getParagraph(1)->getString());
 }
@@ 

[Libreoffice-bugs] [Bug 145648] Different kerning when comparing Text and Comments

2022-11-11 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=145648

--- Comment #5 from Caolán McNamara  ---
What used to happen is covered in the slides of
https://events.documentfoundation.org/media/libreoffice-conference-2022/submissions/B87ZBP/resources/LibreOfficeCon-2022-ResolutionI_2TieDK1.odp
where writer's text rendering used to do something very different to everything
else.

For 7.4 I put in the new approach but was pretty conservative and made the new
way of doing things "opt in" and only the "main window" of writer was opted in.
I think its been reasonable successful, so I've pushed the boat out a little
more since then, and with
https://cgit.freedesktop.org/libreoffice/core/commit/?id=495922fd4ac07d4b7c16127b222f1d06a2718399
I'm hoping that its more universal.

I haven't checked this case yet, but it would be interesting to reexamine with
a recent daily build and see what differences might persist.

-- 
You are receiving this mail because:
You are the assignee for the bug.

  1   2   3   >