[Bug 158814] FILEOPEN DOCX RTF Empty header with formatted paragraph and shape appears

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=158814

--- Comment #6 from Miklos Vajna  ---
I think the useful reference for desktop Writer's Word format handling is
desktop Word. Seeing that our render differs in attachment 191551 , I would
tend to say it's useful to fix our side to match.

And it's indeed annoying that sometimes Office Online 365 itself differs from
desktop Word, but that's their problem. :-)

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

core.git: Branch 'libreoffice-24-2': "Don't mess with UserInstallation setting of --with-package-format=archive"

[Stephan Bergmann]

FYI, in case anybody relied on the old behavior:


commit 37fb56a1ce031f929067b37c2959b970ff39efd2 (origin/libreoffice-24-2)
Author: Stephan Bergmann 
Date:   Thu Jan 4 21:35:36 2024 +0100

Don't mess with UserInstallation setting of --with-package-format=archive

Ever since 9043c50f5e284f00a7eadeab5a3add0417c32227 "INTEGRATION: CWS native62

(1.68.8); FILE MERGED" and its "2006/09/15 14:51:02 is 1.68.8.2: #i67179# 
new
user dir for all simple-package installation sets" archive installation 
sets had
set the UserInstallation bootstrap variable to $ORIGIN/../... instead of the
normal $SYSUSERCONFIG/... that is used for other installation set formats.

However, I see no good reason for that, and it interferes with my current work

of making the --enable-online-update-mar `make create-update-info` work 
again
(which builds a mar file from an archive installation set, so contained a
boostrap ini-file with an unexpected UserInstallation value).

(I don't know about the "installed" installation set format, which also messes

with the UserInstallation setting, so I left that alone.)

Change-Id: I3bd1e00771a4149922c3ce4e4d187abd3889b4ea

Reviewed-on: https://gerrit.libreoffice.org/c/core/+/161650
Tested-by: Jenkins
Reviewed-by: Stephan Bergmann 
(cherry picked from commit 512cc9e8d2be9cdcce0792e44461d0e8ce8c775f)
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/161637

diff --git a/solenv/bin/modules/installer/simplepackage.pm 
b/solenv/bin/modules/installer/simplepackage.pm
index 86b3da71f440..a8b98a222e5f 100644
--- a/solenv/bin/modules/installer/simplepackage.pm
+++ b/solenv/bin/modules/installer/simplepackage.pm
@@ -42,13 +42,13 @@ sub check_simple_packager_project
 {
 my ( $allvariables ) = @_;
 
-if (( $installer::globals::packageformat eq "installed" ) ||

-( $installer::globals::packageformat eq "archive" ))
+if ( $installer::globals::packageformat eq "installed" )
 {
 $installer::globals::is_simple_packager_project = 1;
 $installer::globals::patch_user_dir = 1;
 }
-elsif( $installer::globals::packageformat eq "dmg" )
+elsif(( $installer::globals::packageformat eq "archive" ) ||
+  ( $installer::globals::packageformat eq "dmg" ) )
 {
 $installer::globals::is_simple_packager_project = 1;
 }

[Bug 36310] [EDITING]"Insert cross-reference" drag-n-drop mode for navigator

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=36310

--- Comment #16 from Jim Raykowski  ---
(In reply to sdc.blanco from comment #14)
> 1.  Maybe the "Insert as" can (should?) be dropped for all options?
Maybe the 'Drag Mode' tool tip could be something like 'Drag Mode Insert Type'
or 'Drag Mode Insert As' to eliminate the need for 'Insert as' in each of the
options.

> 2.  There is a discrepancy between the Navigator bar and the context menu
> for Drag Mode.  (I prefer the Drag Mode version where Page, Chapter, Text
> appears first).
The order shows the same for me for the Drag Mode drop down control and the
context menu Drag Mode sub menu. I think it also shows it that way in the demo.

> 3.  Maybe Reference should be "Cross-reference"
Probably

> 4. What happens if one tries to drag frames, shapes, bookmarks, etc. with
> the "Text" option?
At this point the patch only works for headings.

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

Re: Question about async methods (related to tdf#158965 "Find Record: Similarities dialog won't appear")

[Miklos Vajna]

Hi Julien,

On Wed, Jan 03, 2024 at 02:01:51PM +0100, Julien Nabet  
wrote:
> I noticed several methods about async:
> 
> 1) from include/vcl/abstdlg.hxx:
> 
> StartExecuteAsync

I think this is the usual codepath for modal dialogs. Some uno command
decides to open a dialog, we call StartExecuteAsync() with a callback to
handle the dialog result and that handler will be executed at some stage
in the future, instead of right now.

> 2) from include/svtools/genericasyncunodialog.hxx
> 
> executedAsyncDialog which seems used only for PDF dialog
> 
> createAsyncDialog  used for PDF dialog but above all in startExecuteModal
> 
> startExecuteModal
> 
> runAsync
> 
> (perhaps I forgot some).
> 
> Is there some plan to unify them (or at least reduce the number of them) or
> each one has its useful role?

This looks like a special case for the situation when an import or
export action wants to show a dialog, as part of a synchronous filter()
API call. In this case you can't move the "rest of the code" to an async
callback, so that needs special handling. Luckily these dialogs are
rather rare.

I fear there is not much you can unify here. Perhaps it's useful to
document which one is the usual case and which one is some special
minority?

Regards,

Miklos

core.git: Branch 'libreoffice-24-2' - solenv/bin

[Stephan Bergmann (via logerrit)]

 solenv/bin/modules/installer/simplepackage.pm |6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

New commits:
commit 37fb56a1ce031f929067b37c2959b970ff39efd2
Author: Stephan Bergmann 
AuthorDate: Thu Jan 4 21:35:36 2024 +0100
Commit: Stephan Bergmann 
CommitDate: Fri Jan 5 08:37:45 2024 +0100

Don't mess with UserInstallation setting of --with-package-format=archive

Ever since 9043c50f5e284f00a7eadeab5a3add0417c32227 "INTEGRATION: CWS 
native62
(1.68.8); FILE MERGED" and its "2006/09/15 14:51:02 is 1.68.8.2: #i67179# 
new
user dir for all simple-package installation sets" archive installation 
sets had
set the UserInstallation bootstrap variable to $ORIGIN/../... instead of the
normal $SYSUSERCONFIG/... that is used for other installation set formats.

However, I see no good reason for that, and it interferes with my current 
work
of making the --enable-online-update-mar `make create-update-info` work 
again
(which builds a mar file from an archive installation set, so contained a
boostrap ini-file with an unexpected UserInstallation value).

(I don't know about the "installed" installation set format, which also 
messes
with the UserInstallation setting, so I left that alone.)

Change-Id: I3bd1e00771a4149922c3ce4e4d187abd3889b4ea
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/161650
Tested-by: Jenkins
Reviewed-by: Stephan Bergmann 
(cherry picked from commit 512cc9e8d2be9cdcce0792e44461d0e8ce8c775f)
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/161637

diff --git a/solenv/bin/modules/installer/simplepackage.pm 
b/solenv/bin/modules/installer/simplepackage.pm
index 86b3da71f440..a8b98a222e5f 100644
--- a/solenv/bin/modules/installer/simplepackage.pm
+++ b/solenv/bin/modules/installer/simplepackage.pm
@@ -42,13 +42,13 @@ sub check_simple_packager_project
 {
 my ( $allvariables ) = @_;
 
-if (( $installer::globals::packageformat eq "installed" ) ||
-( $installer::globals::packageformat eq "archive" ))
+if ( $installer::globals::packageformat eq "installed" )
 {
 $installer::globals::is_simple_packager_project = 1;
 $installer::globals::patch_user_dir = 1;
 }
-elsif( $installer::globals::packageformat eq "dmg" )
+elsif(( $installer::globals::packageformat eq "archive" ) ||
+  ( $installer::globals::packageformat eq "dmg" ) )
 {
 $installer::globals::is_simple_packager_project = 1;
 }

[Bug 36310] [EDITING]"Insert cross-reference" drag-n-drop mode for navigator

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=36310

--- Comment #15 from Jim Raykowski  ---
(In reply to Heiko Tietze from comment #13)
> is tedious. Can we, in addition maybe, have modifier keys so one presses
> ctrl, for instance, and the target is the title?
I didn't know about being able to use modifier keys with the Navigator dnd.
While making the patch I was wondering about what use there was for some of
things in the code. This explains them! The ctrl modifier makes the drop a
hyperlink, ctrl+shifts makes it a section link, and shift makes it a section
copy. The current patch ignores these modifiers when the drag mode is set to
any of the reference modes.

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

[Bug 159018] Special characters changed with new version

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=159018

--- Comment #10 from Angelo  ---
I know that everyone of you seems to be an engineer or some experienced
developer but I'm a common user and that I want to be.

My procedure was what I wrote earlier and I don't like to be named a liar or
stupid.

If it is not a bug close my report and amen, otherwise don't keep on going to
tell me new procedure or whatever else you dream in the night.

1-I changed the default font to Arial because I hate that other font
2 I wrote whatever I wanted
3-I saved in this automatic format ods, I suppose is
4-Later on I did the work and decided to add a red bold checkmark to know the
work had been done.
5-When I made some other work I copied the full row of cells and add to the
plot.
6-If I needed more checkmarks I copied (CTRL+C) from one cell and added into
another.
That's all, no other copy and paste, neither notepad++ nor any other bla bla.

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

[Bug 158419] FILEOPEN: DOCX: fix cursor position in a paragraph line shrunk by the new justification algorithm

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=158419

László Németh  changed:

   What|Removed |Added

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

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

[Bug 119908] FILEOPEN: DOCX: Layout differences with justified paragraph. MS 2013 introduced a new "smart justify" that can shrink as well as expand.

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=119908

László Németh  changed:

   What|Removed |Added

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

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

[Bug 131304] [META] MS Word compatibilityMode = 15

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=131304

László Németh  changed:

   What|Removed |Added

 Depends on||159034


Referenced Bugs:

https://bugs.documentfoundation.org/show_bug.cgi?id=159034
[Bug 159034] fix shading position at smart justify
-- 
You are receiving this mail because:
You are the assignee for the bug.

[Bug 107830] [META] DOCX (OOXML) paragraph-related issues

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=107830

László Németh  changed:

   What|Removed |Added

 Depends on||159034


Referenced Bugs:

https://bugs.documentfoundation.org/show_bug.cgi?id=159034
[Bug 159034] fix shading position at smart justify
-- 
You are receiving this mail because:
You are the assignee for the bug.

[Bug 159034] fix shading position at smart justify

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=159034

László Németh  changed:

   What|Removed |Added

 Status|UNCONFIRMED |ASSIGNED
 Ever confirmed|0   |1
 CC||nem...@numbertext.org
   Assignee|libreoffice-b...@lists.free |nem...@numbertext.org
   |desktop.org |

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

[Bug 159034] New: fix shading position at smart justify

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=159034

Bug ID: 159034
   Summary: fix shading position at smart justify
   Product: LibreOffice
   Version: 24.2.0.0 beta1+
  Hardware: All
OS: All
Status: UNCONFIRMED
  Severity: normal
  Priority: medium
 Component: Writer
  Assignee: libreoffice-bugs@lists.freedesktop.org
  Reporter: nem...@numbertext.org

Description:
Shading, e.g. a soft hyphen is there in a bad position. 

Steps to Reproduce:
1. open test document

Actual Results:
Shading of soft hyphen is not between "a" and "s" of "Cras".

Expected Results:
Shading of soft hyphen is between "a" and "s" of "Cras".


Reproducible: Always


User Profile Reset: No

Additional Info:
See also Bug 119908 and Bug 158419

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

[Bug 117085] [META] Compress image dialog bugs and enhancements

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=117085
Bug 117085 depends on bug 158780, which changed state.

Bug 158780 Summary: Image compression dialog should grey out Resolution fields 
if "Reduce image resolution" is not ticked (comment 7)
https://bugs.documentfoundation.org/show_bug.cgi?id=158780

   What|Removed |Added

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

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

[Bug 156465] save to xls and xlsx files corrupted

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=156465

--- Comment #16 from Elmar  ---
There was a hidden sheet in the fiile which was a mess, in a workbook received
from a colleague.
When I deleted the sheet, everything was fine.

The offending sheet had been created years ago.

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

core.git: include/svx svx/source

[Heiko Tietze (via logerrit)]

 include/svx/compressgraphicdialog.hxx   |1 +
 svx/source/dialog/compressgraphicdialog.cxx |   16 +++-
 2 files changed, 12 insertions(+), 5 deletions(-)

New commits:
commit 79018bac2ed73fbfaacf661ae1272086e3ddd342
Author: Heiko Tietze 
AuthorDate: Thu Jan 4 14:45:13 2024 +0100
Commit: Heiko Tietze 
CommitDate: Fri Jan 5 07:36:33 2024 +0100

Resolves tdf#158780 - Disable resolution controls initially

Change-Id: I80e620085868925643d4b7561cd7aeff2d9c930f
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/161620
Tested-by: Jenkins
Reviewed-by: Heiko Tietze 

diff --git a/include/svx/compressgraphicdialog.hxx 
b/include/svx/compressgraphicdialog.hxx
index 088d0b6fd45e..d46220d17a1f 100644
--- a/include/svx/compressgraphicdialog.hxx
+++ b/include/svx/compressgraphicdialog.hxx
@@ -79,6 +79,7 @@ private:
 DECL_DLLPRIVATE_LINK( OkayClickHdl, weld::Button&, void );
 
 void Update();
+void UpdateSensitivity(const bool bSensitive);
 void UpdateNewWidthMF();
 void UpdateNewHeightMF();
 void UpdateResolutionLB();
diff --git a/svx/source/dialog/compressgraphicdialog.cxx 
b/svx/source/dialog/compressgraphicdialog.cxx
index 35899bec2f5f..df1d3a8c3db6 100644
--- a/svx/source/dialog/compressgraphicdialog.cxx
+++ b/svx/source/dialog/compressgraphicdialog.cxx
@@ -108,6 +108,8 @@ void CompressGraphicsDialog::recallParameter()
 m_xQualitySlider->set_value( memp.QualityMF );
 
 m_xInterpolationCombo->set_active( memp.InterpolationCombo );
+
+UpdateSensitivity(m_xReduceResolutionCB->get_active());
 }
 
 void CompressGraphicsDialog::Initialize()
@@ -207,6 +209,14 @@ void CompressGraphicsDialog::Update()
 m_xFixedText6->set_label("??");
 }
 
+void CompressGraphicsDialog::UpdateSensitivity(const bool bSensitive)
+{
+m_xMFNewWidth->set_sensitive(bSensitive);
+m_xMFNewHeight->set_sensitive(bSensitive);
+m_xResolutionLB->set_sensitive(bSensitive);
+m_xInterpolationCombo->set_sensitive(bSensitive);
+}
+
 void CompressGraphicsDialog::UpdateNewWidthMF()
 {
 int nPixelX = static_cast( GetViewWidthInch() * m_dResolution );
@@ -353,11 +363,7 @@ IMPL_LINK_NOARG( CompressGraphicsDialog, 
ToggleCompressionRB, weld::Toggleable&,
 
 IMPL_LINK_NOARG( CompressGraphicsDialog, ToggleReduceResolutionRB, 
weld::Toggleable&, void )
 {
-bool choice = m_xReduceResolutionCB->get_active();
-m_xMFNewWidth->set_sensitive(choice);
-m_xMFNewHeight->set_sensitive(choice);
-m_xResolutionLB->set_sensitive(choice);
-m_xInterpolationCombo->set_sensitive(choice);
+UpdateSensitivity(m_xReduceResolutionCB->get_active());
 Update();
 }
 

[Bug 157986] Contents in rotated text frame invisible if SKIA rendering is disabled.

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=157986

⁨خالد حسني⁩  changed:

   What|Removed |Added

 CC||rb.hensc...@t-online.de

--- Comment #10 from ⁨خالد حسني⁩  ---
*** Bug 158991 has been marked as a duplicate of this bug. ***

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

[Bug 158991] Text in rotated shape is cut when Skia is disabled

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=158991

⁨خالد حسني⁩  changed:

   What|Removed |Added

 Resolution|--- |DUPLICATE
 Status|NEW |RESOLVED

--- Comment #6 from ⁨خالد حسني⁩  ---


*** This bug has been marked as a duplicate of bug 157986 ***

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

[Bug 159032] crash with smart justify

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=159032

--- Comment #1 from Commit Notification 
 ---
László Németh committed a patch related to this issue.
It has been pushed to "master":

https://git.libreoffice.org/core/commit/96b3ed389fa5d434ed738d7f84dada4b6e2fabec

tdf#159032 sw smart justify: fix crash with complex tables

It will be available in 24.8.0.

The patch should be included in the daily builds available at
https://dev-builds.libreoffice.org/daily/ in the next 24-48 hours. More
information about daily builds can be found at:
https://wiki.documentfoundation.org/Testing_Daily_Builds

Affected users are encouraged to test the fix and report feedback.

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

[Bug 159032] crash with smart justify

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=159032

Commit Notification  changed:

   What|Removed |Added

 Whiteboard||target:24.8.0

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

core.git: sw/qa sw/source

[László Németh (via logerrit)]

 sw/qa/extras/ooxmlexport/data/tdf124795-5.docx |binary
 sw/qa/extras/ooxmlexport/ooxmlexport14.cxx |6 ++
 sw/source/core/text/portxt.cxx |1 +
 3 files changed, 7 insertions(+)

New commits:
commit 96b3ed389fa5d434ed738d7f84dada4b6e2fabec
Author: László Németh 
AuthorDate: Fri Jan 5 01:11:34 2024 +0100
Commit: László Németh 
CommitDate: Fri Jan 5 06:08:09 2024 +0100

tdf#159032 sw smart justify: fix crash with complex tables

Regression from commit 36bfc86e27fa03ee16f87819549ab126c5a68cac
"tdf#119908 tdf#158776 sw smart justify: shrink only spaces"

Change-Id: Ia3f39ad6549ea909bfe327ff8c8cbde821b90f46
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/161652
Tested-by: Jenkins
Reviewed-by: László Németh 

diff --git a/sw/qa/extras/ooxmlexport/data/tdf124795-5.docx 
b/sw/qa/extras/ooxmlexport/data/tdf124795-5.docx
new file mode 100644
index ..19fd5f49c89c
Binary files /dev/null and b/sw/qa/extras/ooxmlexport/data/tdf124795-5.docx 
differ
diff --git a/sw/qa/extras/ooxmlexport/ooxmlexport14.cxx 
b/sw/qa/extras/ooxmlexport/ooxmlexport14.cxx
index 0656bb868795..4b0fbdd13716 100644
--- a/sw/qa/extras/ooxmlexport/ooxmlexport14.cxx
+++ b/sw/qa/extras/ooxmlexport/ooxmlexport14.cxx
@@ -1414,6 +1414,12 @@ DECLARE_OOXMLEXPORT_TEST(testTdf158436, "tdf158436.docx")
 CPPUNIT_ASSERT_EQUAL(1, getPages());
 }
 
+DECLARE_OOXMLEXPORT_TEST(testTdf159032, "tdf124795-5.docx")
+{
+// This resulted crashing
+CPPUNIT_ASSERT_EQUAL(57, getPages());
+}
+
 CPPUNIT_TEST_FIXTURE(Test, testHyphenationAuto)
 {
 loadAndReload("hyphenation.odt");
diff --git a/sw/source/core/text/portxt.cxx b/sw/source/core/text/portxt.cxx
index 0372a357df6e..228e2e02e4d6 100644
--- a/sw/source/core/text/portxt.cxx
+++ b/sw/source/core/text/portxt.cxx
@@ -308,6 +308,7 @@ bool SwTextPortion::Format_( SwTextFormatInfo  )
 // adjusted line by shrinking spaces using the know space count from the 
first Guess() call
 const SvxAdjust& rAdjust = 
rInf.GetTextFrame()->GetTextNodeForParaProps()->GetSwAttrSet().GetAdjust().GetAdjust();
 if ( bFull && rAdjust == SvxAdjust::Block &&
+ aGuess.BreakPos() != TextFrameIndex(COMPLETE_STRING) &&
  rInf.GetTextFrame()->GetDoc().getIDocumentSettingAccess().get(
 DocumentSettingId::JUSTIFY_LINES_WITH_SHRINKING) &&
  // tdf#158436 avoid shrinking at underflow, e.g. no-break space after 
a

[Bug 131304] [META] MS Word compatibilityMode = 15

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=131304
Bug 131304 depends on bug 159032, which changed state.

Bug 159032 Summary: crash with smart justify
https://bugs.documentfoundation.org/show_bug.cgi?id=159032

   What|Removed |Added

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

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

[Bug 107830] [META] DOCX (OOXML) paragraph-related issues

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=107830
Bug 107830 depends on bug 159032, which changed state.

Bug 159032 Summary: crash with smart justify
https://bugs.documentfoundation.org/show_bug.cgi?id=159032

   What|Removed |Added

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

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

[Bug 159032] crash with smart justify

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=159032

László Németh  changed:

   What|Removed |Added

 Status|ASSIGNED|RESOLVED
   Assignee|nem...@numbertext.org   |libreoffice-b...@lists.free
   ||desktop.org
 Resolution|--- |FIXED
   Keywords|bibisectRequest |bibisected

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

[Bug 159018] Special characters changed with new version

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=159018

--- Comment #9 from Mike Kaganski  ---
(In reply to Angelo from comment #6)
> I'm sorry if you misunderstood my comment.

I understood your comment.
Please try this procedure yourself:

1. In a new clean document, change a cell's font to Arial. Alternatively,
change default cell style's font to Arial (for the test, it doesn't really
matter);
2. Open the Special Character dialog ("Omega" toolbar button, r Insert->Special
Character);
3. Select Wingdings font, scroll down till the checkmark, double-click it;
4. Now, when the cell contains the checkmark character, select the character in
the cell, and look at the displayed font name.

The #4 shows Wingdings, which illustrates my point: our tool not only inserts
the character, but also formats it explicitly, as using a specific chosen font.

5. Change another document's cell to Arial;
6. In initial document, select the checkmark (either in cell's edit mode, or
the whole cell), and copy to clipboard (Ctrl+C);
7. Paste into the second document (either in cell's edit mode, or over the
whole cell).

#7 will have all the pasted instances of checkmark to have explicit Wingdings
font applied, making this character survive save/reload, version upgrade, etc.

My point is: this worked this way (explicitly marking the special character's
font) all the way down, even in LO 3.3.

Now open your attachment 191759, and inspect your checkmark characters - select
them individually, and see the reported font. See that they have a *different*
font - namely, Liberation Serif.

This shows, that your procedure, or your workflow, included not only the steps
you mentioned in comment 3 and comment 6, but also *something* which broke the
explicit formatting of this character with the font. Multiple things may do
that: clearing cells' direct formatting; saving to file formats that don't
support partial cell formatting (like XLS(X)); using special paste (text only);
pasting to e.g. Notepad as intermediate place, then copying from there ... only
you can (possibly) tell what was that. But all that is not the program's fault.
As soon as user's actions removed the explicit "this is Wingdings!" mark from
the character, these characters become subject to the pure luck of accidentally
choosing the expected font (or not).

As I said, the real bug could be, if Calc would *not* itself mark the inserted
character using correct font initially. Also, a bug would be, if normal paste
of a copied correctly formatted character would drop the formatting. Another
possible bug could be, if saving to ODS would drop the formatting.

But I don't see any of the three in the versions I tested so far. The only
phenomenon I observe is "expected" (accidental) choice of *fallback* Wingdings
font for your (unformatted!) checkmarks in 7.4 and some earlier, and (normal,
not a bug) choice of a different fallback font in 7.5.0+.

(In reply to ady from comment #8)

> Regression?

This is already answered in comment 2. This doesn't looks like a regression. I
marked it "needing bisection", to learn which exact commit created the fallback
font choice difference - not because it looks like a bug, but because it
*could* be an unintended side effect, in which case there could be a potential
fix.

> Should this report be set as NEW?

No until either:
1. A bisection proves that the change was unwanted side effect;
2. Angelo provides steps to show how LibreOffice looses the font information.

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

[Bug 159009] UI: Calc text in first row disappears when right-clicking in cell then clicking on column header

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=159009

m_a_riosv  changed:

   What|Removed |Added

 Status|UNCONFIRMED |NEW
   Severity|normal  |minor
 Ever confirmed|0   |1

--- Comment #3 from m_a_riosv  ---
I have retried and getting to reproduce it now. Seems what matters is to have
right-clicked menu for spelling, open.

Version: 24.8.0.0.alpha0+ (X86_64) / LibreOffice Community
Build ID: 56767830b81fa21382b87cf43d78b1c73ca5dbd8
CPU threads: 16; OS: Windows 10.0 Build 22631; UI render: default; VCL: win
Locale: es-ES (es_ES); UI: en-US
Calc: CL threaded

Seems like a corner case, with no data lost.

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

[Bug 158928] Blurring of Calc cells when the curser goes from one cell to a group of cells

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=158928

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

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

[Bug 158891] VIEWING: make cell cursor more accessible to colourblind users

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=158891

QA Administrators  changed:

   What|Removed |Added

 Status|NEEDINFO|UNCONFIRMED
 Ever confirmed|1   |0

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

[Bug 158891] VIEWING: make cell cursor more accessible to colourblind users

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=158891

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

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

[Bug 155687] Crash in: sw::GetZOrderLayer::operator()(com::sun::star::uno::Reference const &)

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=155687

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

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.

[Bug 155683] After upgrade to 7.3.7.3, chart axis labels overlap so much it's just a black blob

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=155683

QA Administrators  changed:

   What|Removed |Added

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

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

[Bug 155683] After upgrade to 7.3.7.3, chart axis labels overlap so much it's just a black blob

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=155683

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

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.

[Bug 144566] LibreOffice won't start when there is an unreachable file in "recent documents" list

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=144566

--- Comment #10 from QA Administrators  ---
Dear roethig_j,

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.

[Bug 155481] Comments are not shown in MS Office, not exported to PDF

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=155481

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

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.

[Bug 136309] Moving an image produces wrong layout (solved after save and reload)

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=136309

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

To make sure we're focusing on the bugs that affect our users today,
LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed
bugs which have not been touched for over a year.

There have been thousands of bug fixes and commits since anyone checked on this
bug report. During that time, it's possible that the bug has been fixed, or the
details of the problem have changed. We'd really appreciate your help in
getting confirmation that the bug is still present.

If you have time, please do the following:

Test to see if the bug is still present with the latest version of LibreOffice
from https://www.libreoffice.org/download/

If the bug is present, please leave a comment that includes the information
from Help - About LibreOffice.

If the bug is NOT present, please set the bug's Status field to
RESOLVED-WORKSFORME and leave a comment that includes the information from Help
- About LibreOffice.

Please DO NOT

Update the version field
Reply via email (please reply directly on the bug tracker)
Set the bug's Status field to RESOLVED - FIXED (this status has a particular
meaning that is not 
appropriate in this case)


If you want to do more to help you can test to see if your issue is a
REGRESSION. To do so:
1. Download and install oldest version of LibreOffice (usually 3.3 unless your
bug pertains to a feature added after 3.3) from
https://downloadarchive.documentfoundation.org/libreoffice/old/

2. Test your bug
3. Leave a comment with your results.
4a. If the bug was present with 3.3 - set version to 'inherited from OOo';
4b. If the bug was not present in 3.3 - add 'regression' to keyword


Feel free to come ask questions or to say hello in our QA chat:
https://web.libera.chat/?settings=#libreoffice-qa

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

Warm Regards,
QA Team

MassPing-UntouchedBug

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

[Bug 132209] When copy/pasting objects to another slide, if text extends beyond the object boundary, the copy will not be in the same place as the original, otherwise it will.

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=132209

--- Comment #4 from QA Administrators  ---
Dear Mr Curious,

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.

[Bug 123967] Reference of Input Field (Variables) cannot be edited after creation; edit box for Reference in fact changes the fields' string

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=123967

--- Comment #6 from QA Administrators  ---
Dear Mike Kaganski,

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.

[Bug 108573] EDITING: No 'preview' while moving complex drawing object

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=108573

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

To make sure we're focusing on the bugs that affect our users today,
LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed
bugs which have not been touched for over a year.

There have been thousands of bug fixes and commits since anyone checked on this
bug report. During that time, it's possible that the bug has been fixed, or the
details of the problem have changed. We'd really appreciate your help in
getting confirmation that the bug is still present.

If you have time, please do the following:

Test to see if the bug is still present with the latest version of LibreOffice
from https://www.libreoffice.org/download/

If the bug is present, please leave a comment that includes the information
from Help - About LibreOffice.

If the bug is NOT present, please set the bug's Status field to
RESOLVED-WORKSFORME and leave a comment that includes the information from Help
- About LibreOffice.

Please DO NOT

Update the version field
Reply via email (please reply directly on the bug tracker)
Set the bug's Status field to RESOLVED - FIXED (this status has a particular
meaning that is not 
appropriate in this case)


If you want to do more to help you can test to see if your issue is a
REGRESSION. To do so:
1. Download and install oldest version of LibreOffice (usually 3.3 unless your
bug pertains to a feature added after 3.3) from
https://downloadarchive.documentfoundation.org/libreoffice/old/

2. Test your bug
3. Leave a comment with your results.
4a. If the bug was present with 3.3 - set version to 'inherited from OOo';
4b. If the bug was not present in 3.3 - add 'regression' to keyword


Feel free to come ask questions or to say hello in our QA chat:
https://web.libera.chat/?settings=#libreoffice-qa

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

Warm Regards,
QA Team

MassPing-UntouchedBug

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

[Bug 106441] When selecting the same image multiple times and moving it, the image will at some point spontaneously move to a new page

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=106441

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

To make sure we're focusing on the bugs that affect our users today,
LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed
bugs which have not been touched for over a year.

There have been thousands of bug fixes and commits since anyone checked on this
bug report. During that time, it's possible that the bug has been fixed, or the
details of the problem have changed. We'd really appreciate your help in
getting confirmation that the bug is still present.

If you have time, please do the following:

Test to see if the bug is still present with the latest version of LibreOffice
from https://www.libreoffice.org/download/

If the bug is present, please leave a comment that includes the information
from Help - About LibreOffice.

If the bug is NOT present, please set the bug's Status field to
RESOLVED-WORKSFORME and leave a comment that includes the information from Help
- About LibreOffice.

Please DO NOT

Update the version field
Reply via email (please reply directly on the bug tracker)
Set the bug's Status field to RESOLVED - FIXED (this status has a particular
meaning that is not 
appropriate in this case)


If you want to do more to help you can test to see if your issue is a
REGRESSION. To do so:
1. Download and install oldest version of LibreOffice (usually 3.3 unless your
bug pertains to a feature added after 3.3) from
https://downloadarchive.documentfoundation.org/libreoffice/old/

2. Test your bug
3. Leave a comment with your results.
4a. If the bug was present with 3.3 - set version to 'inherited from OOo';
4b. If the bug was not present in 3.3 - add 'regression' to keyword


Feel free to come ask questions or to say hello in our QA chat:
https://web.libera.chat/?settings=#libreoffice-qa

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

Warm Regards,
QA Team

MassPing-UntouchedBug

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

[Bug 105108] Object area frame isn't highlighted when clicking text contained within

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=105108

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

To make sure we're focusing on the bugs that affect our users today,
LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed
bugs which have not been touched for over a year.

There have been thousands of bug fixes and commits since anyone checked on this
bug report. During that time, it's possible that the bug has been fixed, or the
details of the problem have changed. We'd really appreciate your help in
getting confirmation that the bug is still present.

If you have time, please do the following:

Test to see if the bug is still present with the latest version of LibreOffice
from https://www.libreoffice.org/download/

If the bug is present, please leave a comment that includes the information
from Help - About LibreOffice.

If the bug is NOT present, please set the bug's Status field to
RESOLVED-WORKSFORME and leave a comment that includes the information from Help
- About LibreOffice.

Please DO NOT

Update the version field
Reply via email (please reply directly on the bug tracker)
Set the bug's Status field to RESOLVED - FIXED (this status has a particular
meaning that is not 
appropriate in this case)


If you want to do more to help you can test to see if your issue is a
REGRESSION. To do so:
1. Download and install oldest version of LibreOffice (usually 3.3 unless your
bug pertains to a feature added after 3.3) from
https://downloadarchive.documentfoundation.org/libreoffice/old/

2. Test your bug
3. Leave a comment with your results.
4a. If the bug was present with 3.3 - set version to 'inherited from OOo';
4b. If the bug was not present in 3.3 - add 'regression' to keyword


Feel free to come ask questions or to say hello in our QA chat:
https://web.libera.chat/?settings=#libreoffice-qa

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

Warm Regards,
QA Team

MassPing-UntouchedBug

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

[Bug 101646] UI option "Scaling" was removed

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=101646

--- Comment #88 from V Stuart Foote  ---
(In reply to waylon_darien from comment #87)
>
> To be clear, when I say "this feature", specifically I'm talking about the
> ability to do something like this: view > options > UI scaling > [ there's an
> input field where you can type a percentage ], you type 150%, and the font
> size of the menu "file, edit, tools, etc..." increases.
>

In essence that is what the SAL_FORCEDPI environment variable already provides.
Works well for the Linux vcl backends, not so much for macOS or Win which
fortunately have improved their ability to manipulate the os/DE UI and respond
to HiDPI displays and GPUs.

But, believe there is further utility to expanding on the SAL_FORCEDPI
approach, just applied with more granularity selectively against specific
elements of the LibreOffice UI.

It could be by Tools -> Options -> LibreOffice -> View setting, or more likely
via the Expert Configuration dialog.

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

[Bug 157845] Locking down the enabled status of the OpenCL feature leads to a startup crash

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=157845

Matt K  changed:

   What|Removed |Added

 Status|NEW |NEEDINFO

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

[Bug 159030] Fractions are created in Date Fields

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=159030

m_a_riosv  changed:

   What|Removed |Added

 CC||miguelangelrv@libreoffice.o
   ||rg
 Resolution|--- |NOTABUG
 Status|NEEDINFO|RESOLVED

--- Comment #2 from m_a_riosv  ---
You need to disable the Autocorrect recognition for those inputs.

If I remember fine, the only format in a cell that the input take care is
'Text'.

Maybe this thread
https://ask.libreoffice.org/t/calc-is-converting-date-to-fractions/60198/3 con
help.

If you don't want to modify Autocorrect (Menu/Tools/Autocorrect
options/Replace), enter at least the date with only one number for month/day
with a '0' before, so the date is recognized.
e.g. instead 1/4 enter 01/4 or 1/04.

Also, you can use [Ctrl+Z] just after [enter]

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

[Bug 159033] Using KDE, tooltips don't always appear at the right location

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=159033

Nicholas van Oudtshoorn  changed:

   What|Removed |Added

 CC||vano...@gmail.com

--- Comment #1 from Nicholas van Oudtshoorn  ---
Created attachment 191769
  --> https://bugs.documentfoundation.org/attachment.cgi?id=191769=edit
Image illustrating the bug

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

[Bug 159033] New: Using KDE, tooltips don't always appear at the right location

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=159033

Bug ID: 159033
   Summary: Using KDE, tooltips don't always appear at the right
location
   Product: LibreOffice
   Version: 24.8.0.0 alpha0+ Master
  Hardware: x86-64 (AMD64)
OS: Linux (All)
Status: UNCONFIRMED
  Severity: trivial
  Priority: medium
 Component: Writer
  Assignee: libreoffice-bugs@lists.freedesktop.org
  Reporter: vano...@gmail.com

Description:
When one has Libreoffice writer on one half of the screen, tooltips appear on
the other half of the screen.

Steps to Reproduce:
1.Run Libreoffice writer using the KDE VCL
2. Tile the Libreoffice window to the left hand side of the screen.
3. Start typing, until word completion tooltips start appearing! :-)

Actual Results:
When a word-completion tooltip appears, it is on the right hand side of the
screen, rather than near the current cursor.

Expected Results:
Tooltip should be near the text-cursor.


Reproducible: Always


User Profile Reset: No

Additional Info:
Version: 24.8.0.0.alpha0+ (X86_64) / LibreOffice Community
Build ID: 960e37af28807ed1b376e26c4504ab755a81dfd5
CPU threads: 4; OS: Linux 6.6; UI render: default; VCL: kf5 (cairo+wayland)
Locale: en-AU (en_AU.UTF-8); UI: en-US
Calc: threaded

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

[Bug 159031] Calc "IF" statement incorrect value return when higher than column "N" input entered.

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=159031

ady  changed:

   What|Removed |Added

 Status|UNCONFIRMED |NEEDINFO
 Ever confirmed|0   |1

--- Comment #2 from ady  ---
Not repro (and most probably NAB/INVALID).

Rather than a bug report, this seems an issue to be posted at
. At any rate, they will probably need you to
attach the spreadsheet file, to be publicly available.

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

[Bug 158891] VIEWING: make cell cursor more accessible to colourblind users

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=158891

--- Comment #18 from Michael  ---
RE Comment 15: Ah, a Windows setting. I just tried it, but it didn't help. The
border around the Active Cell remained blue.

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

[Bug 159030] Fractions are created in Date Fields

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=159030

ady  changed:

   What|Removed |Added

 Status|UNCONFIRMED |NEEDINFO
 Ever confirmed|0   |1

--- Comment #1 from ady  ---
Please take a look at:

Calc > menu Tools > Options > Language settings > Languages > "Date acceptance
patterns".

Please modify the field according to your needs and try again.

Hint: the use of "/" as date separator for "Date acceptance patterns"
frequently generates a conflict. You can have the resulting cell displaying the
date with one format, but the acceptance pattern with another format.

Please post your results, so we would know what to do with this report.

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

[Bug 158891] VIEWING: make cell cursor more accessible to colourblind users

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=158891

--- Comment #17 from Michael  ---
RE Comment 16: We tried all sorts of different combinations of settings in
Tools/Options. What we need is a editing cell background that can be
configurable but separate from the Document Background, and an Active Cell
border colour that can be configurable. Right now it is to be Blue and
unchangeable.

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

[Bug 158997] Calc Format>Columns>Optimal Width [OK] causes some columns to be too narrow

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=158997

--- Comment #12 from ady  ---
With attachment 191723 I can repro the behavior since LO 6.1 and newer, but not
in LO 6.0 and older.

In the following procedure, please do not confuse "Column width" with "Optimal
width"; we are referring to the latter (and the "Add" field in it set to zero),
not the former.

STR:

0. (Optional) Set the zoom factor to be comfortable. During the rest of the
procedure, do not modify the zoom (as it is also a relevant factor).

1. Open attachment 191723.
2. Select column headers A:Z.
3. Double click between column headers F and G.

Note that the complete contents of cells F2 and B2 are displayed.

4. With columns A:Z still selected, open menu Format > Columns > Optimal width.
5. In the Optimal width dialogue, set the "Add" box value to 0 (zero); OK.

Note cells F2 and B2, showing "###".

6. Modify cell's F2 content, from 511 to 888 [ENTER].
7. Select column headers A:Z.
8. Open menu Format > Columns > Optimal width.
9. In the Optimal width dialogue, set the "Add" box value to 0 (zero); OK.

Note that the content of cell F2 is now displayed.

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

[Bug 157482] Turn Security Warnings popup windows into infobars

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=157482

Stéphane Guillou (stragu)  changed:

   What|Removed |Added

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

-- 
You are receiving this mail because:
You are on the CC list for the bug.

[Bug 153322] RFE: Add Macro Security Settings button to macro infobar

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=153322

Stéphane Guillou (stragu)  changed:

   What|Removed |Added

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

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

[Bug 158600] "Macros disabled" show a button "Show macros" which does not make sense

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=158600

Stéphane Guillou (stragu)  changed:

   What|Removed |Added

   Keywords||needsUXEval
 CC||libreoffice-ux-advise@lists
   ||.freedesktop.org,
   ||stephane.guillou@libreoffic
   ||e.org
   See Also||https://bugs.documentfounda
   ||tion.org/show_bug.cgi?id=15
   ||7482,
   ||https://bugs.documentfounda
   ||tion.org/show_bug.cgi?id=15
   ||3322
 Blocks||83009


Referenced Bugs:

https://bugs.documentfoundation.org/show_bug.cgi?id=83009
[Bug 83009] [META] Bugs requiring the use of the Infobar
-- 
You are receiving this mail because:
You are on the CC list for the bug.

[Bug 158600] "Macros disabled" show a button "Show macros" which does not make sense

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=158600

Stéphane Guillou (stragu)  changed:

   What|Removed |Added

   Keywords||needsUXEval
 CC||libreoffice-ux-advise@lists
   ||.freedesktop.org,
   ||stephane.guillou@libreoffic
   ||e.org
   See Also||https://bugs.documentfounda
   ||tion.org/show_bug.cgi?id=15
   ||7482,
   ||https://bugs.documentfounda
   ||tion.org/show_bug.cgi?id=15
   ||3322
 Blocks||83009


Referenced Bugs:

https://bugs.documentfoundation.org/show_bug.cgi?id=83009
[Bug 83009] [META] Bugs requiring the use of the Infobar
-- 
You are receiving this mail because:
You are the assignee for the bug.

[Bug 83009] [META] Bugs requiring the use of the Infobar

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=83009

Stéphane Guillou (stragu)  changed:

   What|Removed |Added

 Depends on||158600


Referenced Bugs:

https://bugs.documentfoundation.org/show_bug.cgi?id=158600
[Bug 158600] "Macros disabled" show a button "Show macros" which does not make
sense
-- 
You are receiving this mail because:
You are the assignee for the bug.

[Bug 107237] [META] Notebookbar Tabbed

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=107237

Stéphane Guillou (stragu)  changed:

   What|Removed |Added

 Depends on||158598


Referenced Bugs:

https://bugs.documentfoundation.org/show_bug.cgi?id=158598
[Bug 158598] Command "Show Comment" should be available in the Tabbed UI
-- 
You are receiving this mail because:
You are the assignee for the bug.

[Bug 158598] Command "Show Comment" should be available in the Tabbed UI

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=158598

Stéphane Guillou (stragu)  changed:

   What|Removed |Added

 Blocks||107237
 CC||libreoffice-ux-advise@lists
   ||.freedesktop.org,
   ||stephane.guillou@libreoffic
   ||e.org
   Keywords||needsUXEval


Referenced Bugs:

https://bugs.documentfoundation.org/show_bug.cgi?id=107237
[Bug 107237] [META] Notebookbar Tabbed
-- 
You are receiving this mail because:
You are the assignee for the bug.

[Bug 158598] Command "Show Comment" should be available in the Tabbed UI

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=158598

Stéphane Guillou (stragu)  changed:

   What|Removed |Added

 Blocks||107237
 CC||libreoffice-ux-advise@lists
   ||.freedesktop.org,
   ||stephane.guillou@libreoffic
   ||e.org
   Keywords||needsUXEval


Referenced Bugs:

https://bugs.documentfoundation.org/show_bug.cgi?id=107237
[Bug 107237] [META] Notebookbar Tabbed
-- 
You are receiving this mail because:
You are on the CC list for the bug.

[Bug 123870] Calc Not Creating accessible PDF's (tagged content, tab and reading order)

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=123870

Thorsten Behrens (allotropia)  changed:

   What|Removed |Added

 CC||t...@libreoffice.org
   Assignee|libreoffice-b...@lists.free |tibor.nagy.extern@allotropi
   |desktop.org |a.de
 Status|NEW |ASSIGNED

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

[Bug 33743] Add "Basic Fonts" option to Calc, Impress, and Draw

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=33743

Stéphane Guillou (stragu)  changed:

   What|Removed |Added

 CC||traceyad2...@gmail.com

--- Comment #28 from Stéphane Guillou (stragu) 
 ---
*** Bug 158980 has been marked as a duplicate of this bug. ***

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

[Bug 158980] add default font option for calc

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=158980

Stéphane Guillou (stragu)  changed:

   What|Removed |Added

 CC||stephane.guillou@libreoffic
   ||e.org
Version|unspecified |Inherited From OOo
 Status|UNCONFIRMED |RESOLVED
 Resolution|--- |DUPLICATE

--- Comment #4 from Stéphane Guillou (stragu) 
 ---
This is already tracked in bug 33743, although there is support for doing quite
the opposite and removing any option to set a default font per component (and
relying entirely on templates instead, as suggested by ady).

*** This bug has been marked as a duplicate of bug 33743 ***

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

[Bug 159027] Writer table formulas calculated incorrectly in merged cells when table splits over pages

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=159027

m_a_riosv  changed:

   What|Removed |Added

 Status|UNCONFIRMED |NEEDINFO
 CC||miguelangelrv@libreoffice.o
   ||rg
 Ever confirmed|0   |1

--- Comment #1 from m_a_riosv  ---
Please attach a sample file.

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

[Bug 133092] [META] Crash bugs

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=133092

Stéphane Guillou (stragu)  changed:

   What|Removed |Added

 Depends on||159026


Referenced Bugs:

https://bugs.documentfoundation.org/show_bug.cgi?id=159026
[Bug 159026] Crash at undo: deleting table in footnote with track changes
record ON and undo
-- 
You are receiving this mail because:
You are the assignee for the bug.

[Bug 105948] [META] Undo/Redo bugs and enhancements

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=105948

Stéphane Guillou (stragu)  changed:

   What|Removed |Added

 Depends on||159026


Referenced Bugs:

https://bugs.documentfoundation.org/show_bug.cgi?id=159026
[Bug 159026] Crash at undo: deleting table in footnote with track changes
record ON and undo
-- 
You are receiving this mail because:
You are the assignee for the bug.

[Bug 103164] [META] Footnote and Endnote bugs and enhancements

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=103164

Stéphane Guillou (stragu)  changed:

   What|Removed |Added

 Depends on||159026


Referenced Bugs:

https://bugs.documentfoundation.org/show_bug.cgi?id=159026
[Bug 159026] Crash at undo: deleting table in footnote with track changes
record ON and undo
-- 
You are receiving this mail because:
You are the assignee for the bug.

[Bug 83946] [META] Tracking changes issues

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=83946

Stéphane Guillou (stragu)  changed:

   What|Removed |Added

 Depends on||159026


Referenced Bugs:

https://bugs.documentfoundation.org/show_bug.cgi?id=159026
[Bug 159026] Crash at undo: deleting table in footnote with track changes
record ON and undo
-- 
You are receiving this mail because:
You are the assignee for the bug.

[Bug 159026] Crash at undo: deleting table in footnote with track changes record ON and undo

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=159026

Stéphane Guillou (stragu)  changed:

   What|Removed |Added

 Blocks||133092, 103164, 105948,
   ||83946
 CC||nem...@numbertext.org
  Regression By||László Németh
 Ever confirmed|0   |1
 Status|UNCONFIRMED |NEW
   Keywords||bibisected, bisected,
   ||regression
Version|24.8.0.0 alpha0+ Master |7.3.3.2 release
Crash report or||["lcl_IsCalcUpperAllowed(Sw
crash signature||Frame const&)"]
   Severity|normal  |critical

--- Comment #1 from Stéphane Guillou (stragu) 
 ---
Reproduced in:

Version: 7.3.7.2 / LibreOffice Community
Build ID: e114eadc50a9ff8d8c8a0567d6da8f454beeb84f
CPU threads: 8; OS: Linux 5.15; UI render: default; VCL: gtk3
Locale: en-AU (en_AU.UTF-8); UI: en-US
Calc: threaded

Version: 7.6.4.1 (X86_64) / LibreOffice Community
Build ID: e19e193f88cd6c0525a17fb7a176ed8e6a3e2aa1
CPU threads: 8; OS: Linux 5.15; UI render: default; VCL: gtk3
Locale: en-AU (en_AU.UTF-8); UI: en-US
Calc: threaded

Version: 24.8.0.0.alpha0+ (X86_64) / LibreOffice Community
Build ID: 56767830b81fa21382b87cf43d78b1c73ca5dbd8
CPU threads: 8; OS: Linux 5.15; UI render: default; VCL: gtk3
Locale: en-AU (en_AU.UTF-8); UI: en-US
Calc: threaded

with "lcl_IsCalcUpperAllowed(SwFrame const&)" signature:
https://crashreport.libreoffice.org/stats/crash_details/fdc912c9-a2b4-4700-9cbb-44cd44e6dc60

Not reproduced in:

Version: 7.2.0.4 / LibreOffice Community
Build ID: 9a9c6381e3f7a62afc1329bd359cc48accb6435b
CPU threads: 8; OS: Linux 5.15; UI render: default; VCL: gtk3
Locale: en-AU (en_AU.UTF-8); UI: en-US
Calc: threaded

Bibisected with linux-64-7.3 repo to first bad build
[df9a79f154879de8998598ee11fd17fc4ada6456] which points to core commit
e07ea7a6f5f7059663e99daa97cbda5e63b141dd which is a cherrypick of:

commit  0c6221e1545e7b96d9df23cdc24302c28ae935b8
author  László Németh Fri Mar 25 15:27:21 2022 +0100
committer   László Németh Mon Mar 28 09:41:34 2022 +0200
tdf#148227 sw: fix Undo of tracked row deletion in Hide Changes mode
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/132123

László, can you please have a look?


Referenced Bugs:

https://bugs.documentfoundation.org/show_bug.cgi?id=83946
[Bug 83946] [META] Tracking changes issues
https://bugs.documentfoundation.org/show_bug.cgi?id=103164
[Bug 103164] [META] Footnote and Endnote bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=105948
[Bug 105948] [META] Undo/Redo bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=133092
[Bug 133092] [META] Crash bugs
-- 
You are receiving this mail because:
You are the assignee for the bug.

[Bug 59068] Allow different Drawing Scale per document (see comment 7)

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=59068

Stéphane Guillou (stragu)  changed:

   What|Removed |Added

 CC||juani...@gmail.com

--- Comment #11 from Stéphane Guillou (stragu) 
 ---
*** Bug 158590 has been marked as a duplicate of this bug. ***

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

[Bug 158590] Interface design bug "Scale" for Draw documents

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=158590

Stéphane Guillou (stragu)  changed:

   What|Removed |Added

 Resolution|--- |DUPLICATE
 Status|UNCONFIRMED |RESOLVED
 CC||stephane.guillou@libreoffic
   ||e.org

--- Comment #2 from Stéphane Guillou (stragu) 
 ---
Thanks for the suggestion!
This enhancement is already tracked in bug 59068, see bug 59068 comment 7 for a
summary.

*** This bug has been marked as a duplicate of bug 59068 ***

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

[Bug 159010] FIREBIRD: Text in queries will be followed by many spaces

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=159010

m_a_riosv  changed:

   What|Removed |Added

 OS|Linux (All) |All

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

[Bug 159010] FIREBIRD: Text in queries will be followed by many spaces

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=159010

m_a_riosv  changed:

   What|Removed |Added

 Ever confirmed|0   |1
 CC||miguelangelrv@libreoffice.o
   ||rg
 Status|UNCONFIRMED |NEW

--- Comment #1 from m_a_riosv  ---
Reproducible
Version: 7.6.4.1 (X86_64) / LibreOffice Community
Build ID: e19e193f88cd6c0525a17fb7a176ed8e6a3e2aa1
CPU threads: 16; OS: Windows 10.0 Build 22631; UI render: Skia/Raster; VCL: win
Locale: es-ES (es_ES); UI: en-US
Calc: CL threaded

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

[Bug 158787] Slowness of LibreOffice available on the Microsoft Store

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=158787

Stéphane Guillou (stragu)  changed:

   What|Removed |Added

 CC||stephane.guillou@libreoffic
   ||e.org
 Whiteboard| QA:needsComment|
 Status|UNCONFIRMED |NEEDINFO
 Ever confirmed|0   |1

--- Comment #1 from Stéphane Guillou (stragu) 
 ---
Thank you for the report.

Do the two versions you tested have the same version number?
Can you paste the version information for both here? (Like you did in the
Description)

Please also test with a new profile, more information is available here:
https://wiki.documentfoundation.org/UserProfile#Backup_first

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

[Bug 158788] Applying math formula (MAX()) to individual array elements

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=158788

Stéphane Guillou (stragu)  changed:

   What|Removed |Added

 CC||stephane.guillou@libreoffic
   ||e.org
 Status|UNCONFIRMED |NEEDINFO
 Ever confirmed|0   |1

--- Comment #11 from Stéphane Guillou (stragu) 
 ---
So you are after something like R's *apply() family (or purrr's map*() family),
with recycling of arrays in case of mismatch in their length?

Isn't MS Excel's MAP function close to that?

https://support.microsoft.com/en-us/office/map-function-48006093-f97c-47c1-bfcc-749263bb1f01

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

[Bug 159009] UI: Calc text in first row disappears when right-clicking in cell then clicking on column header

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=159009

Matt K  changed:

   What|Removed |Added

 Status|NEEDINFO|UNCONFIRMED
 Ever confirmed|1   |0

--- Comment #2 from Matt K  ---
(In reply to m_a_riosv from comment #1)
> Please test in safe mode, Menu/Help/Restart in Safe Mode

Confirmed occurs in safe mode as well.  For step (3), you may need to double
click on the column header "A" until the whole column is highlighted.  It also
happens if you double click the row header for row "1".

Here is what I used:

Version: 24.8.0.0.alpha0+ (X86_64) / LibreOffice Community
Build ID: 205dd919179f34815d7e16c8dc73d2a7efd34535
CPU threads: 16; OS: Windows 10.0 Build 22631; UI render: default; VCL: win
Locale: en-US (en_US); UI: en-US
Calc: threaded

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

[Bug 159009] UI: Calc text in first row disappears when right-clicking in cell then clicking on column header

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=159009

m_a_riosv  changed:

   What|Removed |Added

 Status|UNCONFIRMED |NEEDINFO
 Ever confirmed|0   |1
 CC||miguelangelrv@libreoffice.o
   ||rg

--- Comment #1 from m_a_riosv  ---
I can't reproduce
Version: 7.6.4.1 (X86_64) / LibreOffice Community
Build ID: e19e193f88cd6c0525a17fb7a176ed8e6a3e2aa1
CPU threads: 16; OS: Windows 10.0 Build 22631; UI render: Skia/Raster; VCL: win
Locale: es-ES (es_ES); UI: en-US Calc: CL threaded

Please test in safe mode, Menu/Help/Restart in Safe Mode

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

[Bug 158776] DOCX import: unnecessary shrinking of spaces

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=158776

László Németh  changed:

   What|Removed |Added

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

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

[Bug 131304] [META] MS Word compatibilityMode = 15

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=131304

László Németh  changed:

   What|Removed |Added

 Depends on||159032


Referenced Bugs:

https://bugs.documentfoundation.org/show_bug.cgi?id=159032
[Bug 159032] crash with smart justify
-- 
You are receiving this mail because:
You are the assignee for the bug.

[Bug 159032] crash with smart justify

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=159032

László Németh  changed:

   What|Removed |Added

 Ever confirmed|0   |1
 Blocks||107830, 131304
 CC||nem...@numbertext.org
   Assignee|libreoffice-b...@lists.free |nem...@numbertext.org
   |desktop.org |
   See Also||https://bugs.documentfounda
   ||tion.org/show_bug.cgi?id=15
   ||8776
 Status|UNCONFIRMED |ASSIGNED
   Keywords||regression


Referenced Bugs:

https://bugs.documentfoundation.org/show_bug.cgi?id=107830
[Bug 107830] [META] DOCX (OOXML) paragraph-related issues
https://bugs.documentfoundation.org/show_bug.cgi?id=131304
[Bug 131304] [META] MS Word compatibilityMode = 15
-- 
You are receiving this mail because:
You are the assignee for the bug.

[Bug 107830] [META] DOCX (OOXML) paragraph-related issues

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=107830

László Németh  changed:

   What|Removed |Added

 Depends on||159032


Referenced Bugs:

https://bugs.documentfoundation.org/show_bug.cgi?id=159032
[Bug 159032] crash with smart justify
-- 
You are receiving this mail because:
You are the assignee for the bug.

[Bug 159032] New: crash with smart justify

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=159032

Bug ID: 159032
   Summary: crash with smart justify
   Product: LibreOffice
   Version: 24.2.0.0 beta1+
  Hardware: All
OS: All
Status: UNCONFIRMED
  Severity: normal
  Priority: medium
 Component: Writer
  Assignee: libreoffice-bugs@lists.freedesktop.org
  Reporter: nem...@numbertext.org

Description:
>From Caolán McNamara's bug report from
https://gerrit.libreoffice.org/c/core/+/160988/comments/721d6430_e5d6277e:

"We've got a new crashtesting assert I bisected to here, to reproduce:

wget https://bugs.documentfoundation.org/attachment.cgi?id=157047 -O
~/Downloads/tdf124795-5.docx
./instdir/program/soffice --headless --convert-to pdf
~/Downloads/tdf124795-5.docx"


Steps to Reproduce:
1. Follow the description.

Actual Results:
crash (also with opening the file)

Expected Results:
no crash


Reproducible: Always


User Profile Reset: No

Additional Info:
Regression from commit 36bfc86e27fa03ee16f87819549ab126c5a68cac.

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

[Bug 108827] [META] Calc functions bugs and enhancements

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=108827

Stéphane Guillou (stragu)  changed:

   What|Removed |Added

 Depends on||158789


Referenced Bugs:

https://bugs.documentfoundation.org/show_bug.cgi?id=158789
[Bug 158789] Allow SUMIF and SUBTOTAL to apply to arrays
-- 
You are receiving this mail because:
You are the assignee for the bug.

[Bug 158789] Allow SUMIF and SUBTOTAL to apply to arrays

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=158789

Stéphane Guillou (stragu)  changed:

   What|Removed |Added

 Ever confirmed|0   |1
 Status|UNCONFIRMED |NEEDINFO
 Blocks||108827
URL||https://ask.libreoffice.org
   ||/t/is-there-an-alternative-
   ||to-sumif-for-arrays/99693
 CC||rb.hensc...@t-online.de,
   ||stephane.guillou@libreoffic
   ||e.org

--- Comment #10 from Stéphane Guillou (stragu) 
 ---
I agree with Mike that the inconsistency is problematic, and would support more
interoperability with other tools.

However, looking at the ODF specification[1], I understand using an array on
the first argument is not allowed:

"Constraints: Does not accept constant values as the range parameter."

...which contradicts the working example in comment 7.

Regina, what is your opinion? Any potential future evolution in ODF here? Or
maybe I am reading the spec wrong?

Regarding SUBTOTAL: arrays already work, e.g.: =SUBTOTAL(1,{1,2,3,4,5})
Jonathan, can you confirm?

[1]:
https://docs.oasis-open.org/office/OpenDocument/v1.3/os/part4-formula/OpenDocument-v1.3-os-part4-formula.html#__RefHeading__1018584_715980110


Referenced Bugs:

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

[Bug 159031] Calc "IF" statement incorrect value return when higher than column "N" input entered.

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=159031

--- Comment #1 from fl...@yahoo.com ---
This bug has been in the last several releases.

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

[Bug 159031] New: Calc "IF" statement incorrect value return when higher than column "N" input entered.

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=159031

Bug ID: 159031
   Summary: Calc "IF" statement incorrect value return when higher
than column "N" input entered.
   Product: LibreOffice
   Version: 7.4.0.3 release
  Hardware: All
OS: Windows (All)
Status: UNCONFIRMED
  Severity: normal
  Priority: medium
 Component: Calc
  Assignee: libreoffice-bugs@lists.freedesktop.org
  Reporter: fl...@yahoo.com

Description:
Using Calc on a large spreadsheet "IF" formula will return "#VALUE!" when
column used in formula is greater than column "N".

example: =IF(N42>0,N42-N41,"") will return correct value if N42 has a value
greater than 0 and a blank if 0.

example: =IF(O42>0,O42-O41,"") will return correct value if O42 has a value
greater than 0 but will return #VALUE! if O42 is 0.

This seems to be true for all columns "O" and greater.

Steps to Reproduce:
1.use "IF" statement
2. reference column "O" or higher 
3. use "" for a blank return as last part of formula

Actual Results:
See description for results

Expected Results:
Should be a blank return if the input value is 0


Reproducible: Always


User Profile Reset: No

Additional Info:
cdeefe4 Version 7.5.9.2, tag libreoffice-7.5.9.2 by Xisco Fauli ·

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

[Bug 144050] FILEOPEN on an RTF document replaces multiple spaces with other characters, losing layout justification

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=144050

--- Comment #14 from Jonas Camillus Jeppesen  ---
I was about to open an bug report on what I now believe to be the same
bug/issue as this.

Working on RTF-output for the Pygments project I see consecutive spaces
rendered width variable width or maybe even replaced with a number of other
characters (in Libre Office Write 7.6.x on Linux and Windows 10).

Both my own minimal example [1], as well as the originally attached
RFT-example[2] render correctly in WordPad[3] on Windows or Apache
OpenOffice[4] (Windows+Linux).

An interesting observation I made was that adding the following line to the
RTF-files makes the spaces render correctly in Libre Office.


{\*\generator anystring} 

The `{\*\generator ...}`-line appears in RTF-files produced by WordPad. I can't
however find the \generator control word described anywhere in the
rtf-specification. `\*` instructs readers to ignore the control word (a
destination) if they do not implement it. WordPad appears to use it to declare
which version of Microsoft Rich Edit was used to generate the file (e.g.
`{\*\generator Riched20 10.0.18362}`.

[5] shows how replacing the blank line 3 in [1] with `{\*\generator anystring}`
cause Libre Office to render the spaces at equal width. [5] also show a
selection of the first 4 characters in Libre Office, e.g. ` 2  ` (space 2 space
space), which Libre Office detects as a selection of 6 characters.

As I understand Comment 8 by Buovjaga a commit has been identified which
introduced the bug. That commit is dated August 2019 so I picked a version from
2018 (6.1.6.3) and that version (6.1.6.3) is free of this bug/issue. It renders
the spaces correctly.


[1] https://bugs.documentfoundation.org/attachment.cgi?id=191766
[2] https://bugs.documentfoundation.org/attachment.cgi?id=174514
[3] https://bugs.documentfoundation.org/attachment.cgi?id=191750
[4] https://bugs.documentfoundation.org/attachment.cgi?id=191751
[5] https://bugs.documentfoundation.org/attachment.cgi?id=191767

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

[Bug 158799] Editing. Have a cell background separate from the document background.

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=158799

Stéphane Guillou (stragu)  changed:

   What|Removed |Added

   See Also||https://bugs.documentfounda
   ||tion.org/show_bug.cgi?id=68
   ||359
   Keywords||needsUXEval
 CC||libreoffice-ux-advise@lists
   ||.freedesktop.org,
   ||stephane.guillou@libreoffic
   ||e.org

--- Comment #7 from Stéphane Guillou (stragu) 
 ---
I don't think allowing different "Document Background" colours is realistic as
it's an app-wide setting, affecting all components.

I see that using cell styles does not help as the background ends up above an
image sent to the background.

I can imagine two ways to solve it:
A) Allow setting the "cell edit mode background" colour (or lack thereof) in
Application Colours > Spreadsheet (the default being "Automatic" and using the
document background unless the cell has a background colour)
B) Allow images as sheet backgrounds, as requested in bug 68359

UX/Design team, what do you think?

-- 
You are receiving this mail because:
You are on the CC list for the bug.

[Bug 68359] FORMATTING: implement sheet background image (always visible, with formatting options like tiled)

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=68359

Stéphane Guillou (stragu)  changed:

   What|Removed |Added

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

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

[Bug 158799] Editing. Have a cell background separate from the document background.

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=158799

Stéphane Guillou (stragu)  changed:

   What|Removed |Added

   See Also||https://bugs.documentfounda
   ||tion.org/show_bug.cgi?id=68
   ||359
   Keywords||needsUXEval
 CC||libreoffice-ux-advise@lists
   ||.freedesktop.org,
   ||stephane.guillou@libreoffic
   ||e.org

--- Comment #7 from Stéphane Guillou (stragu) 
 ---
I don't think allowing different "Document Background" colours is realistic as
it's an app-wide setting, affecting all components.

I see that using cell styles does not help as the background ends up above an
image sent to the background.

I can imagine two ways to solve it:
A) Allow setting the "cell edit mode background" colour (or lack thereof) in
Application Colours > Spreadsheet (the default being "Automatic" and using the
document background unless the cell has a background colour)
B) Allow images as sheet backgrounds, as requested in bug 68359

UX/Design team, what do you think?

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

[Bug 158806] Allow copying partial text from fields

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=158806

Stéphane Guillou (stragu)  changed:

   What|Removed |Added

 Status|UNCONFIRMED |NEW
 Blocks||112182
   Keywords||needsUXEval
 CC||libreoffice-ux-advise@lists
   ||.freedesktop.org,
   ||stephane.guillou@libreoffic
   ||e.org
   Priority|medium  |low
 Ever confirmed|0   |1

--- Comment #3 from Stéphane Guillou (stragu) 
 ---
Agree this would be useful. OnlyOffice also allows it.

Copying UX/Design team regarding what would be copied: should a field be
copied, like when the full field is copied? Or only the text, like in MS Office
and OnlyOffice?
I think copying only text would avoid us some headaches.

And do we agree that a single-click on a field should still select the whole
field?


Referenced Bugs:

https://bugs.documentfoundation.org/show_bug.cgi?id=112182
[Bug 112182] [META] Selection of text, cells and objects
-- 
You are receiving this mail because:
You are the assignee for the bug.

[Bug 112182] [META] Selection of text, cells and objects

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=112182

Stéphane Guillou (stragu)  changed:

   What|Removed |Added

 Depends on||158806


Referenced Bugs:

https://bugs.documentfoundation.org/show_bug.cgi?id=158806
[Bug 158806] Allow copying partial text from fields
-- 
You are receiving this mail because:
You are the assignee for the bug.

[Bug 158806] Allow copying partial text from fields

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=158806

Stéphane Guillou (stragu)  changed:

   What|Removed |Added

 Status|UNCONFIRMED |NEW
 Blocks||112182
   Keywords||needsUXEval
 CC||libreoffice-ux-advise@lists
   ||.freedesktop.org,
   ||stephane.guillou@libreoffic
   ||e.org
   Priority|medium  |low
 Ever confirmed|0   |1

--- Comment #3 from Stéphane Guillou (stragu) 
 ---
Agree this would be useful. OnlyOffice also allows it.

Copying UX/Design team regarding what would be copied: should a field be
copied, like when the full field is copied? Or only the text, like in MS Office
and OnlyOffice?
I think copying only text would avoid us some headaches.

And do we agree that a single-click on a field should still select the whole
field?


Referenced Bugs:

https://bugs.documentfoundation.org/show_bug.cgi?id=112182
[Bug 112182] [META] Selection of text, cells and objects
-- 
You are receiving this mail because:
You are on the CC list for the bug.

[Bug 158814] FILEOPEN DOCX RTF Empty header with formatted paragraph and shape appears

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=158814

--- Comment #5 from Stéphane Guillou (stragu) 
 ---
(In reply to Stéphane Guillou (stragu) from comment #4)
> Created attachment 191768 [details]
> DOCX exported to PDF by Office 365
Sorry, I need to clarify: this is the export _after_ expanding the header in
the DOCX (but without editing it).
If the document is exported without expanding the header, there are no lines
and no extra space.

Still feels like a MS Office bug to me.

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

[Bug 158814] FILEOPEN DOCX RTF Empty header with formatted paragraph and shape appears

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=158814

--- Comment #4 from Stéphane Guillou (stragu) 
 ---
Created attachment 191768
  --> https://bugs.documentfoundation.org/attachment.cgi?id=191768=edit
DOCX exported to PDF by Office 365

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

[Bug 158814] FILEOPEN DOCX RTF Empty header with formatted paragraph and shape appears

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=158814

Stéphane Guillou (stragu)  changed:

   What|Removed |Added

 Ever confirmed|0   |1
 CC||stephane.guillou@libreoffic
   ||e.org,
   ||vmik...@collabora.com
  Regression By||Miklos Vajna
 Status|UNCONFIRMED |NEEDINFO

--- Comment #3 from Stéphane Guillou (stragu) 
 ---
Confirmed for both DOCX and RTF in recent trunk build:

Version: 24.8.0.0.alpha0+ (X86_64) / LibreOffice Community
Build ID: 56767830b81fa21382b87cf43d78b1c73ca5dbd8
CPU threads: 8; OS: Linux 5.15; UI render: default; VCL: gtk3
Locale: en-AU (en_AU.UTF-8); UI: en-US
Calc: threaded

Online Office 365 has no such spacing and line at the top.

But doesn't it make sense that LO shows the header if it has contents?
Export the DOCX to PDF with Office 365 and you get two lines and spacing in
both header and footer. I think LO is doing better as a WYSIWYG than MS Office
here, so my take is "not a bug".

Miklos, what do you think?

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

core.git: solenv/bin

[Stephan Bergmann (via logerrit)]

 solenv/bin/modules/installer/simplepackage.pm |6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

New commits:
commit 5056da285da2f130d741add1f8432cd590116a96
Author: Stephan Bergmann 
AuthorDate: Thu Jan 4 21:35:36 2024 +0100
Commit: Stephan Bergmann 
CommitDate: Thu Jan 4 23:07:13 2024 +0100

Don't mess with UserInstallation setting of --with-package-format=archive

Ever since 9043c50f5e284f00a7eadeab5a3add0417c32227 "INTEGRATION: CWS 
native62
(1.68.8); FILE MERGED" and its "2006/09/15 14:51:02 is 1.68.8.2: #i67179# 
new
user dir for all simple-package installation sets" archive installation 
sets had
set the UserInstallation bootstrap variable to $ORIGIN/../... instead of the
normal $SYSUSERCONFIG/... that is used for other installation set formats.

However, I see no good reason for that, and it interferes with my current 
work
of making the --enable-online-update-mar `make create-update-info` work 
again
(which builds a mar file from an archive installation set, so contained a
boostrap ini-file with an unexpected UserInstallation value).

(I don't know about the "installed" installation set format, which also 
messes
with the UserInstallation setting, so I left that alone.)

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

diff --git a/solenv/bin/modules/installer/simplepackage.pm 
b/solenv/bin/modules/installer/simplepackage.pm
index 86b3da71f440..a8b98a222e5f 100644
--- a/solenv/bin/modules/installer/simplepackage.pm
+++ b/solenv/bin/modules/installer/simplepackage.pm
@@ -42,13 +42,13 @@ sub check_simple_packager_project
 {
 my ( $allvariables ) = @_;
 
-if (( $installer::globals::packageformat eq "installed" ) ||
-( $installer::globals::packageformat eq "archive" ))
+if ( $installer::globals::packageformat eq "installed" )
 {
 $installer::globals::is_simple_packager_project = 1;
 $installer::globals::patch_user_dir = 1;
 }
-elsif( $installer::globals::packageformat eq "dmg" )
+elsif(( $installer::globals::packageformat eq "archive" ) ||
+  ( $installer::globals::packageformat eq "dmg" ) )
 {
 $installer::globals::is_simple_packager_project = 1;
 }

[Bug 159030] New: Fractions are created in Date Fields

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=159030

Bug ID: 159030
   Summary: Fractions are created in Date Fields
   Product: LibreOffice
   Version: 7.4.7.2 release
  Hardware: All
OS: Windows (All)
Status: UNCONFIRMED
  Severity: normal
  Priority: medium
 Component: Calc
  Assignee: libreoffice-bugs@lists.freedesktop.org
  Reporter: idmoose...@yahoo.com

Description:
Today, when I entered "1/4" in a cell with "Date Format" specified, instead of
seeing "1/4/2024" as expected, the "Date Format" was ignored and my entry was
converted to a fraction. This FORMATTING issue is a long-term issue.

Steps to Reproduce:
1. Create a cell with "Date Format".
2. Enter "1/4".
3. Press Enter.

Actual Results:
A fraction, 1/4, is returned instead of today's date.

Expected Results:
Today's date, 1/4/2024, is the expected result in a cell with "Date Format"
specified, not a mathematical fraction.


Reproducible: Always


User Profile Reset: No

Additional Info:
Version: 7.5.9.2 (X86_64) / LibreOffice Community
Build ID: cdeefe45c17511d326101eed8008ac4092f278a9
CPU threads: 24; OS: Windows 10.0 Build 19045; UI render: Skia/Vulkan; VCL: win
Locale: en-US (en_US); UI: en-US
Calc: CL threaded

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

[Bug 144050] FILEOPEN on an RTF document replaces multiple spaces with other characters, losing layout justification

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=144050

--- Comment #13 from Jonas Camillus Jeppesen  ---
Created attachment 191767
  --> https://bugs.documentfoundation.org/attachment.cgi?id=191767=edit
Montage showing rendering with/without \generator control word

Montage showing the rendering of
https://bugs.documentfoundation.org/attachment.cgi?id=191766 with and without
the \generator control word. 

Highlighted in red are regions of interest.

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

[Bug 144050] FILEOPEN on an RTF document replaces multiple spaces with other characters, losing layout justification

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=144050

--- Comment #12 from Jonas Camillus Jeppesen  ---
Created attachment 191766
  --> https://bugs.documentfoundation.org/attachment.cgi?id=191766=edit
WordPad-inspired example demonstrating the consecutive space issue.

WordPad-inspired example demonstrating the consecutive space issue. Line 3 is
blank, replace it with {\*\generator anystring} and the spaces render
correctly.

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

[Bug 158809] LibreOffice not found in French AppStore (macOS)

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=158809

Stéphane Guillou (stragu)  changed:

   What|Removed |Added

 Status|UNCONFIRMED |NEW
 CC||cl...@documentfoundation.or
   ||g,
   ||stephane.guillou@libreoffic
   ||e.org
 Ever confirmed|0   |1

--- Comment #1 from Stéphane Guillou (stragu) 
 ---
Tried fr website: https://www.apple.com/fr/search/libreoffice?src=globalnav:
not listed
However, the US version doesn't list it either:
https://www.apple.com/us/search/libreoffice?src=globalnav

It is true that LibreOffice does not come up in the list, but I am unsure how
apps are indexed and/or curated.

Regarding the actual Mac App Store on macOS Ventura 13.2.1 , I can confirm
that:
- LibreOffice is the first result in the Australian app store
- LibreOffice is not listed in the French app store

So I confirm the issue (although Bugzilla is not where such issues should be
tracked, Redmine is the place).

This is likely related to an extra legal requirement that prevented us to make
the app available at the same time as other countries.

Cloph, any news on this, and would you like me to move this to a Redmine
ticket?

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

[Bug 159007] Moving a grouped object to a different layer makes it disappear

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=159007

m_a_riosv  changed:

   What|Removed |Added

 Status|UNCONFIRMED |NEW
 Ever confirmed|0   |1

--- Comment #4 from m_a_riosv  ---
Ok, I can reproduce it now. As you mention, can be selected with the mouse or
with the navigator.

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