[Libreoffice-bugs] [Bug 152752] New: View - User Interface... in a new document: warnings in console with debug LO

2022-12-30 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=152752

Bug ID: 152752
   Summary: View - User Interface... in a new document: warnings
in console with debug LO
   Product: LibreOffice
   Version: 7.6.0.0 alpha0+ Master
  Hardware: All
OS: All
Status: UNCONFIRMED
  Severity: normal
  Priority: medium
 Component: Writer
  Assignee: libreoffice-bugs@lists.freedesktop.org
  Reporter: buzea.bog...@libreoffice.org

Description:
Open a new Writer document. View - User Interface... - Tabbed - Apply to All

In the dbg build of LibreOffice I get in terminal this warnings:
warn:vcl.builder:418533:418533:vcl/source/window/builder.cxx:3465: probably
need to implement NotebookBarAddonsMenuMergePoint
warn:vcl:418533:418533:vcl/source/image/ImplImage.cxx:93: Failed to load scaled
image from cmd/sc_stylespreview.png at 1
warn:vcl:418533:418533:vcl/source/image/ImplImage.cxx:116: Failed to load stock
icon cmd/sc_stylespreview.png


Steps to Reproduce:
see description

Actual Results:
warnings

Expected Results:
no warnings


Reproducible: Always


User Profile Reset: Yes

Additional Info:
Version: 7.6.0.0.alpha0+ (X86_64) / LibreOffice Community
Build ID: 12e8d57e791bb1befc0716d4d02af7d1d1ccb4ae
CPU threads: 4; OS: Linux 5.19; UI render: default; VCL: gtk3
Locale: ro-RO (ro_RO.UTF-8); UI: en-US
Calc: threaded

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

[Libreoffice-bugs] [Bug 113944] [META] Options dialog's Writer settings bugs and enhancements

2022-12-30 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=113944
Bug 113944 depends on bug 152676, which changed state.

Bug 152676 Summary: Writer: Compatibility options no longer saved as default
https://bugs.documentfoundation.org/show_bug.cgi?id=152676

   What|Removed |Added

 Status|NEW |RESOLVED
 Resolution|--- |FIXED

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

[Libreoffice-bugs] [Bug 152676] Writer: Compatibility options no longer saved as default

2022-12-30 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=152676

Noel Grandin  changed:

   What|Removed |Added

 Resolution|--- |FIXED
 Status|NEW |RESOLVED

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

[Libreoffice-bugs] [Bug 152676] Writer: Compatibility options no longer saved as default

2022-12-30 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=152676

Commit Notification  changed:

   What|Removed |Added

 Whiteboard||target:7.6.0

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

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

2022-12-30 Thread Noel Grandin (via logerrit)
 include/unotools/compatibility.hxx   |   11 ---
 sw/source/ui/config/optcomp.cxx  |   10 --
 unotools/source/config/compatibility.cxx |2 --
 3 files changed, 8 insertions(+), 15 deletions(-)

New commits:
commit c6f756e968bbb72522bd01dea283288a61a286a7
Author: Noel Grandin 
AuthorDate: Sat Dec 31 08:52:53 2022 +0200
Commit: Noel Grandin 
CommitDate: Sat Dec 31 07:49:03 2022 +

tdf#152676 Writer: Compatibility options no longer saved as default

regression from
commit 78adf246d5e99d0f5d91d2e03c1379b154289d8d
Date:   Mon Jul 26 10:54:36 2021 +0200
return SvtCompatibilityEntry from SvtCompatibilityOptions::GetList

where I mistakenly assumed that the bIsDefault flag in
SvtCompatibilityEntry was being set by the SvtCompatibilityOptions
code. Rather remove this field if it is not going to be maintained
properly.

Change-Id: I23963ae885563d5abc8a99cfd144d7fe00c6f192
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/144882
Tested-by: Jenkins
Reviewed-by: Noel Grandin 

diff --git a/include/unotools/compatibility.hxx 
b/include/unotools/compatibility.hxx
index 73e77a598ec9..72017812ab8b 100644
--- a/include/unotools/compatibility.hxx
+++ b/include/unotools/compatibility.hxx
@@ -129,19 +129,8 @@ class SvtCompatibilityEntry
 setValue(rIdx, css::uno::Any(rValue));
 }
 
-bool isDefaultEntry() const
-{
-return m_bDefaultEntry;
-}
-
-void setDefaultEntry( bool rValue )
-{
-m_bDefaultEntry = rValue;
-}
-
 private:
 std::vector m_aPropertyValue;
-bool   m_bDefaultEntry;
 };
 
 
/*-
diff --git a/sw/source/ui/config/optcomp.cxx b/sw/source/ui/config/optcomp.cxx
index 0ba1b147614c..d760e885a66e 100644
--- a/sw/source/ui/config/optcomp.cxx
+++ b/sw/source/ui/config/optcomp.cxx
@@ -205,10 +205,11 @@ void SwCompatibilityOptPage::InitControls( const 
SfxItemSet& rSet )
 {
 const OUString sEntryName = rEntry.getValue( 
SvtCompatibilityEntry::Index::Name );
 const bool bIsUserEntry= ( sEntryName == 
SvtCompatibilityEntry::USER_ENTRY_NAME );
+const bool bIsDefaultEntry = ( sEntryName == 
SvtCompatibilityEntry::DEFAULT_ENTRY_NAME );
 
 m_pImpl->m_aList.push_back( rEntry );
 
-if ( rEntry.isDefaultEntry() )
+if ( bIsDefaultEntry )
 continue;
 
 OUString sNewEntry;
@@ -260,7 +261,12 @@ IMPL_LINK_NOARG(SwCompatibilityOptPage, UseAsDefaultHdl, 
weld::Button&, void)
 return;
 
 auto pItem = std::find_if(m_pImpl->m_aList.begin(), m_pImpl->m_aList.end(),
-[](const SvtCompatibilityEntry& rItem) { return 
rItem.isDefaultEntry(); });
+[](const SvtCompatibilityEntry& rItem)
+{
+const OUString sEntryName = rItem.getValue( 
SvtCompatibilityEntry::Index::Name );
+const bool bIsDefaultEntry = ( sEntryName == 
SvtCompatibilityEntry::DEFAULT_ENTRY_NAME );
+return bIsDefaultEntry;
+});
 if (pItem != m_pImpl->m_aList.end())
 {
 const sal_Int32 nCount = m_xOptionsLB->n_children();
diff --git a/unotools/source/config/compatibility.cxx 
b/unotools/source/config/compatibility.cxx
index 4f0e1d2ac20c..eed01cce1c8b 100644
--- a/unotools/source/config/compatibility.cxx
+++ b/unotools/source/config/compatibility.cxx
@@ -65,8 +65,6 @@ SvtCompatibilityEntry::SvtCompatibilityEntry()
 setValue( Index::SubtractFlysAnchoredAtFlys, false );
 setValue( Index::EmptyDbFieldHidesPara, true );
 setValue( Index::AddTableLineSpacing, false );
-
-setDefaultEntry( false );
 }
 
 OUString SvtCompatibilityEntry::getName( const Index rIdx )


[Libreoffice-bugs] [Bug 150687] Simple inserting of text: too many warnings in console with debug LO

2022-12-30 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=150687

BogdanB  changed:

   What|Removed |Added

 CC||caol...@redhat.com

--- Comment #11 from BogdanB  ---
Caolan, I added you here, because is affecting simple text document.

Could be reproduce much easier with a new document, type "A" and press Enter.

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

[Libreoffice-bugs] [Bug 152751] New: Closing LibreOffice generate warnings in console with debug LO

2022-12-30 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=152751

Bug ID: 152751
   Summary: Closing LibreOffice generate warnings in console with
debug LO
   Product: LibreOffice
   Version: 7.6.0.0 alpha0+ Master
  Hardware: All
OS: All
Status: UNCONFIRMED
  Severity: normal
  Priority: medium
 Component: Writer
  Assignee: libreoffice-bugs@lists.freedesktop.org
  Reporter: buzea.bog...@libreoffice.org

Description:
Open a new LibreOffice Writer document. Close LibreOffice (File - Close
LibreOffice).

In the terminal, in the dbg version of LibreOffice I get this messages:
warn:vcl.schedule.deinit:332666:332666:vcl/source/app/scheduler.cxx:177: DeInit
task: Timer a: 1 p: 1 framework::AutoRecovery m_aTimer 60ms (0x176cb68)
warn:vcl.schedule.deinit:332666:332666:vcl/source/app/scheduler.cxx:177: DeInit
task: Timer a: 1 p: 1 graphic::Manager maSwapOutTimer 1ms (0x7fc2ed3cece0)
warn:vcl.schedule.deinit:332666:332666:vcl/source/app/scheduler.cxx:198: DeInit
active tasks: 2 (ignored: 0)
warn:unotools.config:332666:332666:unotools/source/config/configmgr.cxx:147:
ConfigManager not empty

Steps to Reproduce:
see description

Actual Results:
warnings

Expected Results:
no warnings


Reproducible: Always


User Profile Reset: Yes

Additional Info:
Version: 7.6.0.0.alpha0+ (X86_64) / LibreOffice Community
Build ID: 12e8d57e791bb1befc0716d4d02af7d1d1ccb4ae
CPU threads: 4; OS: Linux 5.19; UI render: default; VCL: gtk3
Locale: ro-RO (ro_RO.UTF-8); UI: en-US
Calc: threaded

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

[Libreoffice-bugs] [Bug 152750] New: File - Digital Signatures generate a warning in console with debug LO

2022-12-30 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=152750

Bug ID: 152750
   Summary: File - Digital Signatures generate a warning in
console with debug LO
   Product: LibreOffice
   Version: 7.6.0.0 alpha0+ Master
  Hardware: All
OS: All
Status: UNCONFIRMED
  Severity: normal
  Priority: medium
 Component: Writer
  Assignee: libreoffice-bugs@lists.freedesktop.org
  Reporter: buzea.bog...@libreoffice.org

Description:
Open a new LibreOffice Writer document. SAVE. File - Digital Signatures

In the terminal, in the dbg version of LibreOffice I get this messages:
warn:xmlsecurity.helper:284617:284617:xmlsecurity/source/helper/xmlsignaturehelper.cxx:281:
DBG_UNHANDLED_EXCEPTION in ReadAndVerifySignature exception:
com.sun.star.xml.sax.SAXParseException message: "[ line 1]: no elementserror at
/home/tdf/lode/jenkins/workspace/lo_gerrit/tb/src_master/sax/source/expatwrap/sax_expat.cxx:677"
wrapped: com.sun.star.xml.sax.SAXParseException message: "at
/home/tdf/lode/jenkins/workspace/lo_gerrit/tb/src_master/sax/source/expatwrap/sax_expat.cxx:472"
wrapped: void message: "at
/home/tdf/lode/jenkins/workspace/lo_gerrit/tb/src_master/comphelper/source/misc/diagnose_ex.cxx:66"
PublicId:  SystemId:  LineNumber: 0 ColumnNumber: 0 PublicId:  SystemId: 
LineNumber: 1 ColumnNumber: 0



If I don't save the document BEFORE going to File - Digital Signatures I get
the windows asking me to save, I save and then I get the message in the
terminal:
warn:sfx.appl:298141:298141:sfx2/source/appl/appserv.cxx:313: no parent for
dialogs


Steps to Reproduce:
see description

Actual Results:
warnings

Expected Results:
no warnings


Reproducible: Always


User Profile Reset: Yes

Additional Info:
Version: 7.6.0.0.alpha0+ (X86_64) / LibreOffice Community
Build ID: 12e8d57e791bb1befc0716d4d02af7d1d1ccb4ae
CPU threads: 4; OS: Linux 5.19; UI render: default; VCL: gtk3
Locale: ro-RO (ro_RO.UTF-8); UI: en-US
Calc: threaded

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

[Libreoffice-bugs] [Bug 152749] New: File - Print generates warnings in console with debug LO

2022-12-30 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=152749

Bug ID: 152749
   Summary: File - Print generates warnings in console with debug
LO
   Product: LibreOffice
   Version: 7.6.0.0 alpha0+ Master
  Hardware: All
OS: All
Status: UNCONFIRMED
  Severity: normal
  Priority: medium
 Component: Writer
  Assignee: libreoffice-bugs@lists.freedesktop.org
  Reporter: buzea.bog...@libreoffice.org

Description:
Open a new LibreOffice Writer document. File - Print.

In the terminal, in the dbg version of LibreOffice I get this messages:
warn:vcl.unx.print:208486:208486:vcl/unx/generic/printer/ppdparser.cxx:845: no
Resolution in /tmp/63afe2daa1327
warn:vcl:208486:208486:vcl/unx/generic/printer/printerinfomanager.cxx:546: Do
not ask for info about nonexistent printers

The second line could be true. I have a printer that I can NOT delete from my
Linux  and I can not use it.

Steps to Reproduce:
see description

Actual Results:
warnings

Expected Results:
no warnings


Reproducible: Always


User Profile Reset: Yes

Additional Info:
Version: 7.6.0.0.alpha0+ (X86_64) / LibreOffice Community
Build ID: 12e8d57e791bb1befc0716d4d02af7d1d1ccb4ae
CPU threads: 4; OS: Linux 5.19; UI render: default; VCL: gtk3
Locale: ro-RO (ro_RO.UTF-8); UI: en-US
Calc: threaded

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

[Libreoffice-bugs] [Bug 152748] New: Print Preview in a new document generate warnings in console with debug LO

2022-12-30 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=152748

Bug ID: 152748
   Summary: Print Preview in a new document generate warnings in
console with debug LO
   Product: LibreOffice
   Version: 7.6.0.0 alpha0+ Master
  Hardware: All
OS: All
Status: UNCONFIRMED
  Severity: normal
  Priority: medium
 Component: Writer
  Assignee: libreoffice-bugs@lists.freedesktop.org
  Reporter: buzea.bog...@libreoffice.org

Description:
Open a new LibreOffice Writer document. Press the icon Print Preview.

In the terminal, in the dbg version of LibreOffice I get this messages:
warn:legacy.osl:208486:208486:sw/source/core/access/accpage.cxx:51: bSelected
out of sync
warn:legacy.osl:208486:208486:sw/source/core/access/accpage.cxx:51: bSelected
out of sync

After I close the preview window:
warn:legacy.osl:208486:208486:sw/source/core/access/acccontext.cxx:91: no
window

Steps to Reproduce:
see description

Actual Results:
warnings

Expected Results:
no warnings


Reproducible: Always


User Profile Reset: Yes

Additional Info:
Version: 7.6.0.0.alpha0+ (X86_64) / LibreOffice Community
Build ID: 12e8d57e791bb1befc0716d4d02af7d1d1ccb4ae
CPU threads: 4; OS: Linux 5.19; UI render: default; VCL: gtk3
Locale: ro-RO (ro_RO.UTF-8); UI: en-US
Calc: threaded

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

[Libreoffice-bugs] [Bug 152747] New: File - Export as ... - Export as EPUB in a new document generate warnings in console with debug LO

2022-12-30 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=152747

Bug ID: 152747
   Summary: File - Export as ... - Export as EPUB in a new
document generate warnings in console with debug LO
   Product: LibreOffice
   Version: 7.6.0.0 alpha0+ Master
  Hardware: All
OS: All
Status: UNCONFIRMED
  Severity: normal
  Priority: medium
 Component: Writer
  Assignee: libreoffice-bugs@lists.freedesktop.org
  Reporter: buzea.bog...@libreoffice.org

Description:
Open a new LibreOffice Writer document. File - Export as ... - Export as EPUB

In the terminal, in the dbg version of LibreOffice I get this messages:

warn:writerperfect:116729:116729:writerperfect/source/writer/exp/xmlimp.cxx:81:
DBG_UNHANDLED_EXCEPTION in FindMediaDir exception:
com.sun.star.uno.RuntimeException message: "C++ code threw unknown exception at
/home/tdf/lode/jenkins/workspace/lo_gerrit/tb/src_master/bridges/source/cpp_uno/gcc3_linux_x86-64/uno2cpp.cxx:245"
warn:legacy.osl:116729:116729:xmloff/source/style/xmlexppr.cxx:915: no prop
type specified
warn:legacy.osl:116729:116729:xmloff/source/style/xmlexppr.cxx:915: no prop
type specified
warn:legacy.osl:116729:116729:xmloff/source/style/xmlexppr.cxx:915: no prop
type specified
warn:legacy.osl:116729:116729:xmloff/source/style/xmlexppr.cxx:915: no prop
type specified
warn:legacy.osl:116729:116729:xmloff/source/style/xmlexppr.cxx:915: no prop
type specified
warn:legacy.osl:116729:116729:xmloff/source/style/xmlexppr.cxx:915: no prop
type specified
warn:legacy.osl:116729:116729:xmloff/source/style/xmlexppr.cxx:915: no prop
type specified

Steps to Reproduce:
see description

Actual Results:
warnings

Expected Results:
no warnings


Reproducible: Always


User Profile Reset: Yes

Additional Info:
Version: 7.6.0.0.alpha0+ (X86_64) / LibreOffice Community
Build ID: 12e8d57e791bb1befc0716d4d02af7d1d1ccb4ae
CPU threads: 4; OS: Linux 5.19; UI render: default; VCL: gtk3
Locale: ro-RO (ro_RO.UTF-8); UI: en-US
Calc: threaded

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

[Libreoffice-bugs] [Bug 152738] LO75RC1: Automatic spell-check on macOS not underlining misspelled words

2022-12-30 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=152738

--- Comment #2 from Telesto  ---
I'm noticing bug 152742 right now.. so might be actually something

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

[Libreoffice-bugs] [Bug 152738] LO75RC1: Automatic spell-check on macOS not underlining misspelled words

2022-12-30 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=152738

--- Comment #1 from Telesto  ---
No issue in regular mode and safe mode with Dutch language
Version: 7.6.0.0.alpha0+ (X86_64) / LibreOffice Community
Build ID: 8635c9aa8c6f1078a9e220076d5a08daf30077e8
CPU threads: 8; OS: Mac OS X 12.3.1; UI render: default; VCL: osx
Locale: nl-NL (nl_NL.UTF-8); UI: en-US
Calc: threaded

You did try a profile reset? 


Sidenote: The spell checker s using macos spell checker + dictionary's in my
case (Menu LibreOffice -> Preferences -> Language settings ->  Writing aids. If
I uncheck macos spell nothing will be checked

Reason: There are no bundled dictionary's for hunspell (see Tools -> Extension
Manager) by default.

Does it work if you install the Slovenian (sl) dictionary for hunspell

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

[Libreoffice-bugs] [Bug 152746] File - Export as ... - Export as PDF in a new document generate warnings in console with debug LO

2022-12-30 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=152746

BogdanB  changed:

   What|Removed |Added

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

--- Comment #1 from BogdanB  ---
Interesting that File - Export as ... - Export directly as PDF is NOT
generating this warnings.

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

[Libreoffice-bugs] [Bug 152746] New: File - Export as ... - Export as PDF in a new document generate warnings in console with debug LO

2022-12-30 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=152746

Bug ID: 152746
   Summary: File - Export as ... - Export as PDF in a new document
generate warnings in console with debug LO
   Product: LibreOffice
   Version: 7.6.0.0 alpha0+ Master
  Hardware: All
OS: All
Status: UNCONFIRMED
  Severity: normal
  Priority: medium
 Component: Writer
  Assignee: libreoffice-bugs@lists.freedesktop.org
  Reporter: buzea.bog...@libreoffice.org

Description:
Open a new LibreOffice Writer document. File - Export as ... - Export as PDF

In the terminal, in the dbg version of LibreOffice I get this messages:
warn:sfx.dialog:116729:116729:sfx2/source/dialog/tabdlg.cxx:887:
CreateInputItemSet not implemented
warn:sfx.dialog:116729:116729:sfx2/source/dialog/tabdlg.cxx:887:
CreateInputItemSet not implemented
warn:sfx.dialog:116729:116729:sfx2/source/dialog/tabdlg.cxx:887:
CreateInputItemSet not implemented
warn:sfx.dialog:116729:116729:sfx2/source/dialog/tabdlg.cxx:887:
CreateInputItemSet not implemented
warn:sfx.dialog:116729:116729:sfx2/source/dialog/tabdlg.cxx:887:
CreateInputItemSet not implemented
warn:sfx.dialog:116729:116729:sfx2/source/dialog/tabdlg.cxx:887:
CreateInputItemSet not implemented

Steps to Reproduce:
see description

Actual Results:
warnings

Expected Results:
no warnings


Reproducible: Always


User Profile Reset: Yes

Additional Info:
Version: 7.6.0.0.alpha0+ (X86_64) / LibreOffice Community
Build ID: 12e8d57e791bb1befc0716d4d02af7d1d1ccb4ae
CPU threads: 4; OS: Linux 5.19; UI render: default; VCL: gtk3
Locale: ro-RO (ro_RO.UTF-8); UI: en-US
Calc: threaded

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

[Libreoffice-bugs] [Bug 152745] New: File - Save Remote in a new document generate a warning in console with debug LO

2022-12-30 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=152745

Bug ID: 152745
   Summary: File - Save Remote in a new document generate a
warning in console with debug LO
   Product: LibreOffice
   Version: 7.6.0.0 alpha0+ Master
  Hardware: All
OS: All
Status: UNCONFIRMED
  Severity: normal
  Priority: medium
 Component: Writer
  Assignee: libreoffice-bugs@lists.freedesktop.org
  Reporter: buzea.bog...@libreoffice.org

Description:
Open a new LibreOffice Writer document. File - Save Remote

In the terminal, in the dbg version of LibreOffice I get this messages:

warn:legacy.tools:66022:66022:fpicker/source/office/OfficeControlAccess.cxx:342:
OControlAccess::SetValue: don't have this control in the current mode!


Steps to Reproduce:
see description

Actual Results:
warning

Expected Results:
no warning


Reproducible: Always


User Profile Reset: Yes

Additional Info:
Version: 7.6.0.0.alpha0+ (X86_64) / LibreOffice Community
Build ID: 12e8d57e791bb1befc0716d4d02af7d1d1ccb4ae
CPU threads: 4; OS: Linux 5.19; UI render: default; VCL: gtk3
Locale: ro-RO (ro_RO.UTF-8); UI: en-US
Calc: threaded

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

[Libreoffice-commits] core.git: Branch 'distro/collabora/co-22.05' - sc/inc sc/source

2022-12-30 Thread Noel Grandin (via logerrit)
 sc/inc/scmatrix.hxx  |5 
 sc/source/core/tool/interpr5.cxx |  109 +++---
 sc/source/core/tool/scmatrix.cxx |  231 ---
 3 files changed, 243 insertions(+), 102 deletions(-)

New commits:
commit 2375300d34a57b389ddcf8eda844c846bf5fb419
Author: Noel Grandin 
AuthorDate: Thu Dec 22 18:41:19 2022 +0200
Commit: Noel Grandin 
CommitDate: Sat Dec 31 06:34:43 2022 +

optimise SUMPRODUCT(IF..) a little

Move the AddSub calculation inside ScMatrix so we
can use an iterator to walk the matrix and avoid lookup
cost for each element.
Shaves 50% off the time spent here in my test sheet.

Change-Id: I171d7dd4ae86419a563342a4120d14106e8d71db
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/144826
Tested-by: Jenkins
Reviewed-by: Noel Grandin 
(cherry picked from commit 96f162d02adee9b4edbb440896be90a64523c119)
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/144900
Tested-by: Jenkins CollaboraOffice 

diff --git a/sc/inc/scmatrix.hxx b/sc/inc/scmatrix.hxx
index 9026288c55cf..bae3f8e3f920 100644
--- a/sc/inc/scmatrix.hxx
+++ b/sc/inc/scmatrix.hxx
@@ -130,6 +130,7 @@ public:
 typedef std::function BoolOpFunction;
 typedef std::function 
StringOpFunction;
 typedef std::function EmptyOpFunction;
+typedef std::function CalculateOpFunction;
 
 /**
  * When adding all numerical matrix elements for a scalar result such as
@@ -422,6 +423,10 @@ public:
 void MatConcat(SCSIZE nMaxCol, SCSIZE nMaxRow, const ScMatrixRef& xMat1, 
const ScMatrixRef& xMat2,
 SvNumberFormatter& rFormatter, svl::SharedStringPool& rPool) ;
 
+/** Apply binary operation to values from two input matrices, storing 
result into this matrix. */
+void ExecuteBinaryOp(SCSIZE nMaxCol, SCSIZE nMaxRow, const ScMatrix& 
rInputMat1, const ScMatrix& rInputMat2,
+ScInterpreter* pInterpreter, CalculateOpFunction op);
+
 #if DEBUG_MATRIX
 void Dump() const;
 #endif
diff --git a/sc/source/core/tool/interpr5.cxx b/sc/source/core/tool/interpr5.cxx
index 74807696e055..ec03f981c294 100644
--- a/sc/source/core/tool/interpr5.cxx
+++ b/sc/source/core/tool/interpr5.cxx
@@ -46,45 +46,30 @@ using namespace formula;
 
 namespace {
 
-struct MatrixAdd
+double MatrixAdd(const double& lhs, const double& rhs)
 {
-double operator() (const double& lhs, const double& rhs) const
-{
-return ::rtl::math::approxAdd( lhs,rhs);
-}
-};
+return ::rtl::math::approxAdd( lhs,rhs);
+}
 
-struct MatrixSub
+double MatrixSub(const double& lhs, const double& rhs)
 {
-double operator() (const double& lhs, const double& rhs) const
-{
-return ::rtl::math::approxSub( lhs,rhs);
-}
-};
+return ::rtl::math::approxSub( lhs,rhs);
+}
 
-struct MatrixMul
+double MatrixMul(const double& lhs, const double& rhs)
 {
-double operator() (const double& lhs, const double& rhs) const
-{
-return lhs * rhs;
-}
-};
+return lhs * rhs;
+}
 
-struct MatrixDiv
+double MatrixDiv(const double& lhs, const double& rhs)
 {
-double operator() (const double& lhs, const double& rhs) const
-{
-return ScInterpreter::div( lhs,rhs);
-}
-};
+return ScInterpreter::div( lhs,rhs);
+}
 
-struct MatrixPow
+double MatrixPow(const double& lhs, const double& rhs)
 {
-double operator() (const double& lhs, const double& rhs) const
-{
-return ::pow( lhs,rhs);
-}
-};
+return ::pow( lhs,rhs);
+}
 
 // Multiply n x m Mat A with m x l Mat B to n x l Mat R
 void lcl_MFastMult(const ScMatrixRef& pA, const ScMatrixRef& pB, const 
ScMatrixRef& pR,
@@ -1163,66 +1148,18 @@ static SCSIZE lcl_GetMinExtent( SCSIZE n1, SCSIZE n2 )
 return n2;
 }
 
-template
 static ScMatrixRef lcl_MatrixCalculation(
-const ScMatrix& rMat1, const ScMatrix& rMat2, ScInterpreter* pInterpreter)
+const ScMatrix& rMat1, const ScMatrix& rMat2, ScInterpreter* pInterpreter, 
ScMatrix::CalculateOpFunction Op)
 {
-static const Function Op;
-
 SCSIZE nC1, nC2, nMinC;
 SCSIZE nR1, nR2, nMinR;
-SCSIZE i, j;
 rMat1.GetDimensions(nC1, nR1);
 rMat2.GetDimensions(nC2, nR2);
 nMinC = lcl_GetMinExtent( nC1, nC2);
 nMinR = lcl_GetMinExtent( nR1, nR2);
 ScMatrixRef xResMat = pInterpreter->GetNewMat(nMinC, nMinR, 
/*bEmpty*/true);
 if (xResMat)
-{
-for (i = 0; i < nMinC; i++)
-{
-for (j = 0; j < nMinR; j++)
-{
-bool bVal1 = rMat1.IsValueOrEmpty(i,j);
-bool bVal2 = rMat2.IsValueOrEmpty(i,j);
-FormulaError nErr;
-if (bVal1 && bVal2)
-{
-double d = Op(rMat1.GetDouble(i,j), rMat2.GetDouble(i,j));
-xResMat->PutDouble( d, i, j);
-}
-else if (((nErr = rMat1.GetErrorIfNotString(i,j)) != 
FormulaError::NONE) ||
- ((nErr = 

[Libreoffice-bugs] [Bug 149616] FORTMATTING: Text and/or color element alignment issue in PDF document

2022-12-30 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=149616

--- Comment #5 from BogdanB  ---
Created attachment 184406
  --> https://bugs.documentfoundation.org/attachment.cgi?id=184406=edit
the image mentioned on comment 3, in order to be attached on this bug

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

[Libreoffice-bugs] [Bug 33603] Presenter notes should be available in normal view as a scrolling pane

2022-12-30 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=33603

--- Comment #39 from Benyamin Limanto  ---
(In reply to Regina Henschel from comment #38)
> (In reply to RichardNeill from comment #37)
> > Can I please reemphasise how much this would improve the process of making
> > slides! I literally switch to and from the notes mode every few seconds
> > while editing, and it turns a reasonably smooth process into a very, very
> > painstaking one. 
> 
> You know, that you can open a second window with the same presentation
> (Window > New Window) and use slide mode and notes mode side by side, so
> that changing something in the slide is immediately reflected in the notes?

Not quite usefull for presentation that's... big.. with small screen... I hope
this could be implemented new future...

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

[Libreoffice-bugs] [Bug 152744] New: Can't see selection on first document when interacting with second document

2022-12-30 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=152744

Bug ID: 152744
   Summary: Can't see selection on first document when interacting
with second document
   Product: LibreOffice
   Version: 7.4.3.2 release
  Hardware: x86 (IA32)
OS: Linux (All)
Status: UNCONFIRMED
  Severity: normal
  Priority: medium
 Component: Writer
  Assignee: libreoffice-bugs@lists.freedesktop.org
  Reporter: amab8...@protonmail.com

Description:
A while ago, I was able to have two separate documents open side-by-side, and
select text in one and then have the selection remain visible when I interact
with the other document. This is one of the key features that made LibreOffice
powerful as a tool for proofreading translations. But now it stopped working.

Now, if I select text on one document, it automatically stops showing the
selection when I interact with the other document. Please make the selection
visible again.

Steps to Reproduce:
1.Open two documents side-by-side
2.highlight/select text on one document
3.click on the other document

Actual Results:
the selection/highlight becomes invisible on the first document

Expected Results:
the selection/highlight should remain visible on first document when
interacting with the other document


Reproducible: Always


User Profile Reset: Yes

Additional Info:
Version: 7.4.3.2 / LibreOffice Community
Build ID: 40(Build:2)
CPU threads: 4; OS: Linux 5.15; UI render: default; VCL: gtk3
Locale: sv-SE (en_US.UTF-8); UI: en-US
7.4.3-3
Calc: threaded

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

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

2022-12-30 Thread Jim Raykowski (via logerrit)
 sw/qa/uitest/data/tdf151051.odt |binary
 sw/qa/uitest/navigator/tdf151051.py |   52 
 sw/source/uibase/utlui/content.cxx  |   41 +++-
 3 files changed, 91 insertions(+), 2 deletions(-)

New commits:
commit 5a06b3b789063e77afe7395226359c6ce8aad156
Author: Jim Raykowski 
AuthorDate: Mon Sep 19 00:44:04 2022 -0800
Commit: Jim Raykowski 
CommitDate: Sat Dec 31 03:49:18 2022 +

tdf#151051 Fix promote/demote outline-level promotes/demotes both

outline nodes for outline nodes with table content as last content
followed immediately by an outline node

SwCursorShell::MakeOutlineSel function, currently used to select the
range of outline nodes for outline-level promote/demote, makes a
cursor selection of outline nodes to the start of the next outline
node past the outline nodes to be promoted/demoted. The selection is
then adjusted to the end content of the previous node. When the
previous node is a table, the selection does not move into the table,
but remains at the start of outline node that is one node after the
wanted range. This patch avoids use of the MakeOutlineSel function
for outline-level promote/demote.

Change-Id: Ida505df6ec172681868e86570ae523494ed7929e
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/141128
Tested-by: Jenkins
Reviewed-by: Jim Raykowski 

diff --git a/sw/qa/uitest/data/tdf151051.odt b/sw/qa/uitest/data/tdf151051.odt
new file mode 100644
index ..d5b680b6bdc2
Binary files /dev/null and b/sw/qa/uitest/data/tdf151051.odt differ
diff --git a/sw/qa/uitest/navigator/tdf151051.py 
b/sw/qa/uitest/navigator/tdf151051.py
new file mode 100644
index ..1778cc94fe68
--- /dev/null
+++ b/sw/qa/uitest/navigator/tdf151051.py
@@ -0,0 +1,52 @@
+# -*- tab-width: 4; indent-tabs-mode: nil; py-indent-offset: 4 -*-
+#
+# This file is part of the LibreOffice project.
+#
+# This Source Code Form is subject to the terms of the Mozilla Public
+# License, v. 2.0. If a copy of the MPL was not distributed with this
+# file, You can obtain one at http://mozilla.org/MPL/2.0/.
+#
+
+from uitest.framework import UITestCase
+from libreoffice.uno.propertyvalue import mkPropertyValues
+from uitest.uihelper.common import get_state_as_dict, get_url_for_data_file
+
+class tdf151051(UITestCase):
+
+def test_tdf151051(self):
+
+with self.ui_test.load_file(get_url_for_data_file('tdf151051.odt')):
+xWriterDoc = self.xUITest.getTopFocusWindow()
+xWriterEdit = xWriterDoc.getChild('writer_edit')
+
+self.xUITest.executeCommand('.uno:Sidebar')
+xWriterEdit.executeAction('SIDEBAR', mkPropertyValues({'PANEL': 
'SwNavigatorPanel'}))
+
+# wait until the navigator panel is available
+xNavigatorPanel = 
self.ui_test.wait_until_child_is_available('NavigatorPanel')
+
+xContentTree = xNavigatorPanel.getChild("contenttree")
+
+xHeadings = xContentTree.getChild('0')
+xHeadings.executeAction("EXPAND", tuple())
+
+xChild = xHeadings.getChild('0')
+self.assertEqual('0', get_state_as_dict(xChild)['Children'])
+
+xNavigatorPanel = xWriterEdit.getChild("NavigatorPanel")
+xToolBar = xNavigatorPanel.getChild("content6")
+xToolBar.executeAction("CLICK", mkPropertyValues({"POS": "2"})) # 
'promote' button
+
+xHeadings = xContentTree.getChild('0')
+xHeadings.executeAction("EXPAND", tuple())
+
+xChild = xHeadings.getChild('0')
+xChild.executeAction("EXPAND", tuple())
+
+# Without the fix in place, this test would have failed with
+# AssertionError: '1' != '0'
+self.assertEqual('1', get_state_as_dict(xChild)['Children'])
+
+self.xUITest.executeCommand('.uno:Sidebar')
+
+# vim: set shiftwidth=4 softtabstop=4 expandtab:
diff --git a/sw/source/uibase/utlui/content.cxx 
b/sw/source/uibase/utlui/content.cxx
index c2220ad77f19..7b71b5acb08d 100644
--- a/sw/source/uibase/utlui/content.cxx
+++ b/sw/source/uibase/utlui/content.cxx
@@ -3599,9 +3599,10 @@ void SwContentTree::ExecCommand(std::string_view rCmd, 
bool bOutlineWithChildren
 }
 pShell->GotoOutline( nActPos); // If text selection != box selection
 pShell->Push();
-pShell->MakeOutlineSel(nActPos, nActPos, bOutlineWithChildren);
 if (bUpDown)
 {
+// move outline position up/down (outline position promote/demote)
+pShell->MakeOutlineSel(nActPos, nActPos, bOutlineWithChildren);
 const size_t nEntryAbsPos(GetAbsPos(*pCurrentEntry));
 SwOutlineNodes::difference_type nDir = bUp ? -1 : 1;
 if (!bOutlineWithChildren && ((nDir == -1 && nActPos > 0) ||
@@ -3754,8 +3755,44 @@ void SwContentTree::ExecCommand(std::string_view rCmd, 
bool bOutlineWithChildren
 

[Libreoffice-bugs] [Bug 152548] Line numbering sizes inconsistent when decreasing font size

2022-12-30 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=152548

QA Administrators  changed:

   What|Removed |Added

 Whiteboard|| QA:needsComment

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

[Libreoffice-bugs] [Bug 152694] Problem copying text from Writer to TRichViewEdit (.rtf)

2022-12-30 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=152694

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.

[Libreoffice-bugs] [Bug 152557] Chart data range reduces range / removes cell when adding series, shifts labels

2022-12-30 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=152557

QA Administrators  changed:

   What|Removed |Added

 Whiteboard|| QA:needsComment

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

[Libreoffice-bugs] [Bug 152542] background startup booster called quickstart.exe causing a write error

2022-12-30 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=152542

QA Administrators  changed:

   What|Removed |Added

 Whiteboard|| QA:needsComment

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

[Libreoffice-bugs] [Bug 152694] Problem copying text from Writer to TRichViewEdit (.rtf)

2022-12-30 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=152694

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

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

[Libreoffice-bugs] [Bug 152657] Extreme slow graphical performance and laggy behavior with LO Calc 7.4.3.2 on Linux Mint 20.3

2022-12-30 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=152657

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

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

[Libreoffice-bugs] [Bug 152657] Extreme slow graphical performance and laggy behavior with LO Calc 7.4.3.2 on Linux Mint 20.3

2022-12-30 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=152657

QA Administrators  changed:

   What|Removed |Added

 Ever confirmed|1   |0
 Status|NEEDINFO|UNCONFIRMED

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

[Libreoffice-bugs] [Bug 145906] Charts do NOT update when data is changed

2022-12-30 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=145906

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

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

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

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

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

Warm Regards,
QA Team

MassPing-NeedInfo-Ping

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

[Libreoffice-bugs] [Bug 136763] Crash:Open Property on sidebar, after pressing some table icon [gtk3 ONLY]

2022-12-30 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=136763

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

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

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

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

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

Warm Regards,
QA Team

MassPing-NeedInfo-Ping

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

[Libreoffice-bugs] [Bug 47924] FORMATTING: Paragraph alignment "right" lost in TABLE to text conversion

2022-12-30 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=47924

--- Comment #20 from QA Administrators  ---
Dear Serhiy,

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

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

If you have time, please do the following:

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

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

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

Please DO NOT

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


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

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


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

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

Warm Regards,
QA Team

MassPing-UntouchedBug

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

[Libreoffice-bugs] [Bug 90823] EDITING: Mark Precedents Error When continuous use

2022-12-30 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=90823

--- Comment #7 from QA Administrators  ---
Dear yanjingtao,

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

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

If you have time, please do the following:

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

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

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

Please DO NOT

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


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

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


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

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

Warm Regards,
QA Team

MassPing-UntouchedBug

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

[Libreoffice-bugs] [Bug 139261] Image anchor jumping unexpected position

2022-12-30 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=139261

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

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

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

If you have time, please do the following:

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

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

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

Please DO NOT

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


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

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


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

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

Warm Regards,
QA Team

MassPing-UntouchedBug

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

[Libreoffice-bugs] [Bug 134524] FILESAVE DOCX/DOC: Images gone after inserting a gallery object (followed by save & reload)

2022-12-30 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=134524

--- 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.

[Libreoffice-bugs] [Bug 138786] Image caption frame size to small after copy and paste into a new document

2022-12-30 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=138786

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

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

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

If you have time, please do the following:

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

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

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

Please DO NOT

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


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

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


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

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

Warm Regards,
QA Team

MassPing-UntouchedBug

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

[Libreoffice-bugs] [Bug 126922] Images anchored to hidden Calc rows reappear in wrong place when saved and loaded in XLSX

2022-12-30 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=126922

--- Comment #7 from QA Administrators  ---
Dear Chris Shaw,

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

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

If you have time, please do the following:

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

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

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

Please DO NOT

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


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

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


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

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

Warm Regards,
QA Team

MassPing-UntouchedBug

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

[Libreoffice-bugs] [Bug 121733] Words consist of a number with apostrophe and following a suffix are not send to Spellchecker extension.

2022-12-30 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=121733

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

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

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

If you have time, please do the following:

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

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

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

Please DO NOT

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


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

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


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

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

Warm Regards,
QA Team

MassPing-UntouchedBug

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

[Libreoffice-bugs] [Bug 121523] EDITING DOCX, The entry in the table of contents (TOC) is lost for Heading applied to a part of the paragraph (imported in LO as character style)

2022-12-30 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=121523

--- Comment #5 from QA Administrators  ---
Dear NISZ LibreOffice Team,

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

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

If you have time, please do the following:

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

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

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

Please DO NOT

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


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

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


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

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

Warm Regards,
QA Team

MassPing-UntouchedBug

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

[Libreoffice-bugs] [Bug 119664] In Writer Following Hyperlinks does not Work Correctly with Text Boxes and Shapes

2022-12-30 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=119664

--- Comment #10 from QA Administrators  ---
Dear Harald Koester,

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

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

If you have time, please do the following:

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

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

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

Please DO NOT

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


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

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


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

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

Warm Regards,
QA Team

MassPing-UntouchedBug

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

[Libreoffice-bugs] [Bug 104375] Table Default value for Date entered via UI cannot be modified using SQL

2022-12-30 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=104375

--- Comment #17 from QA Administrators  ---
Dear Stang,

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

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

If you have time, please do the following:

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

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

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

Please DO NOT

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


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

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


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

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

Warm Regards,
QA Team

MassPing-UntouchedBug

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

[Libreoffice-bugs] [Bug 151525] FILEOPEN: LibreOffice Draw renders emojis from some PDFs as the Unicode Replacement Character '�'

2022-12-30 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=151525

--- Comment #14 from Thomas Szymczak  ---
Is this a bug in Firefox or the font used?

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

[Libreoffice-bugs] [Bug 88173] [META] DOCX (OOXML) format limitations

2022-12-30 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=88173

--- Comment #8 from kr4...@yahoo.com ---
Bug 49179 - FILEOPEN: FILESAVE: Image anchored 'to page' in .doc result in 'to
character' when reopening

I just found this is also applicable to .docx format files

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

[Libreoffice-bugs] [Bug 88171] [META] Binary DOC format limitations

2022-12-30 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=88171

--- Comment #5 from kr4...@yahoo.com ---
Bug 49179 - FILEOPEN: FILESAVE: Image anchored 'to page' in .doc result in 'to
character' when reopening

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

[Libreoffice-bugs] [Bug 152710] CRASH: importing ooo84576-1.odt, crashtest; corrupt document structure

2022-12-30 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=152710

--- Comment #7 from Dave Gilbert  ---
The recursive change in the input file is:


  

  Baltix user
  2007-12-02T19:57:00

tainment
  


that id doesn't appear anywhere else in it.

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

[Libreoffice-bugs] [Bug 147522] Table-based totalization formulas convert to lower-case cell references, while the cells they reference stay in title case (correctly), causing totalizations to fail wi

2022-12-30 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=147522

m.a.riosv  changed:

   What|Removed |Added

 Status|UNCONFIRMED |RESOLVED
 Resolution|--- |NOTABUG

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

[Libreoffice-bugs] [Bug 147522] Table-based totalization formulas convert to lower-case cell references, while the cells they reference stay in title case (correctly), causing totalizations to fail wi

2022-12-30 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=147522

--- Comment #8 from m.a.riosv  ---
Created attachment 184405
  --> https://bugs.documentfoundation.org/attachment.cgi?id=184405=edit
File saved as xlsx

You need to save it always a xlsx. ODF doesn't support these formulas, and as I
know it is not i
Any further development should be reported as 'enhancement'.n development to
support them.

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

[Libreoffice-commits] core.git: Branch 'libreoffice-7-5' - cui/source

2022-12-30 Thread Brett T. Warden (via logerrit)
 cui/source/dialogs/QrCodeGenDialog.cxx |5 +
 1 file changed, 1 insertion(+), 4 deletions(-)

New commits:
commit 7f5a8384824b8570547ac982e07b6fb912af6e93
Author: Brett T. Warden 
AuthorDate: Fri Dec 30 08:43:25 2022 +0100
Commit: Caolán McNamara 
CommitDate: Fri Dec 30 22:33:33 2022 +

Remove dependency on BitArray.h from zxing-1.2.0

In zxing-1.4.0, numerous headers are no longer public. Rework the
ConvertToSVGFormat method so it uses bitmatrix.get instead of
bitmatrix.getRow, similar to the ToSVG method in zxing itself.

See https://github.com/zxing-cpp/zxing-cpp/issues/361

Change-Id: Ie25eb8f782e8799fbd57c24ef79bba92acf0f9ff
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/144895
Tested-by: René Engelhard 
Reviewed-by: René Engelhard 
Reviewed-by: Caolán McNamara 

diff --git a/cui/source/dialogs/QrCodeGenDialog.cxx 
b/cui/source/dialogs/QrCodeGenDialog.cxx
index f8cbac1d758d..817be7f21ede 100644
--- a/cui/source/dialogs/QrCodeGenDialog.cxx
+++ b/cui/source/dialogs/QrCodeGenDialog.cxx
@@ -27,7 +27,6 @@
 #endif
 
 #include 
-#include 
 #include 
 #include 
 #include 
@@ -79,7 +78,6 @@ OString ConvertToSVGFormat(const ZXing::BitMatrix& bitmatrix)
 OStringBuffer sb;
 const int width = bitmatrix.width();
 const int height = bitmatrix.height();
-ZXing::BitArray row(width);
 sb.append("\n"
   "http://www.w3.org/2000/svg\; version=\"1.1\" 
viewBox=\"0 0 "
   + OString::number(width) + " " + OString::number(height)
@@ -87,10 +85,9 @@ OString ConvertToSVGFormat(const ZXing::BitMatrix& bitmatrix)
 "

[Libreoffice-bugs] [Bug 150708] Inserting a page break generate 2 warnings in console with debug LO

2022-12-30 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=150708

Caolán McNamara  changed:

   What|Removed |Added

   See Also||https://bz.apache.org/ooo/s
   ||how_bug.cgi?id=88069

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

[Libreoffice-bugs] [Bug 150708] Inserting a page break generate 2 warnings in console with debug LO

2022-12-30 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=150708

Caolán McNamara  changed:

   What|Removed |Added

 Ever confirmed|0   |1
 Status|UNCONFIRMED |NEW
Version|7.5.0.0 alpha0+ |Inherited From OOo

--- Comment #3 from Caolán McNamara  ---
seems to date to:

commit 590a804e7815574a066c658f1f05875a6d0f448f
Date:   Fri Feb 27 05:38:42 2009 +

CWS-TOOLING: integrate CWS sw31a11y01
2009-01-09 11:36:08 +0100 ab  r266069 : #i97891#
NSAccessibilityRoleDescription
2009-01-07 11:01:19 +0100 od  r265955 : #i88069# emit accessibility event
TEXT_ATTRIBUTE_CHANGED on change of paragraph attributes
2009-01-06 11:50:21 +0100 od  r265904 : #i81824# methods
 and 
 - avoid unnecessary cursor movements due avoid unnecessary
   accessibility events.

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

[Libreoffice-commits] core.git: xmloff/inc

2022-12-30 Thread Stephan Bergmann (via logerrit)
 xmloff/inc/XMLThemeColorHandler.hxx |3 +--
 1 file changed, 1 insertion(+), 2 deletions(-)

New commits:
commit 12e8d57e791bb1befc0716d4d02af7d1d1ccb4ae
Author: Stephan Bergmann 
AuthorDate: Thu Dec 29 19:57:47 2022 +0100
Commit: Stephan Bergmann 
CommitDate: Fri Dec 30 22:09:29 2022 +

-Werror=maybe-uninitialized

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

diff --git a/xmloff/inc/XMLThemeColorHandler.hxx 
b/xmloff/inc/XMLThemeColorHandler.hxx
index e98ef725682c..d505935f7127 100644
--- a/xmloff/inc/XMLThemeColorHandler.hxx
+++ b/xmloff/inc/XMLThemeColorHandler.hxx
@@ -32,9 +32,8 @@ public:
const SvXMLUnitConverter&) const override
 {
 sal_Int16 nThemeIndex;
-rValue >>= nThemeIndex;
 
-if (nThemeIndex == -1) // Default
+if (!(rValue >>= nThemeIndex) || nThemeIndex == -1) // Default
 return false;
 
 OUStringBuffer aOutBuffer;


[Libreoffice-bugs] [Bug 152743] Table elements not accessible in field formulas and text field formulas not available in table cells

2022-12-30 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=152743

David Alden  changed:

   What|Removed |Added

 CC||dav5al...@gmail.com

--- Comment #1 from David Alden  ---
Created attachment 184404
  --> https://bugs.documentfoundation.org/attachment.cgi?id=184404=edit
Writer Doc with formula deficiency example

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

[Libreoffice-bugs] [Bug 152743] New: Table elements not accessible in field formulas and text field formulas not available in table cells

2022-12-30 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=152743

Bug ID: 152743
   Summary: Table elements not accessible in field formulas and
text field formulas not available in table cells
   Product: LibreOffice
   Version: 7.3.7.2 release
  Hardware: x86-64 (AMD64)
OS: Linux (All)
Status: UNCONFIRMED
  Severity: enhancement
  Priority: medium
 Component: Writer
  Assignee: libreoffice-bugs@lists.freedesktop.org
  Reporter: dav5al...@gmail.com

Description:
Writer 7.3.7.2 build e114eadc50a9ff8d8c8a0567d6da8f454beeb84f; text page with
two tables.  When I attempt to include a table cell *25 in a text
field calculation the result is "** Expression is faulty **" in gray.  If I put
the table cell value in the Formula instead (e.g., .032*25) it shows up
correctly.  If I copy and paste the document text line with the Formula field
into a table cell (e.g., A11), the text field value is not accessible for
calculations in another table cell (e.g., C11) example: * the result
is "0.00" rather than the correct calculated value.  It would seem that
LibreOffice Writer should allow table values to be used in text field Formulas
in the same document and recognize those Formula fields embedded in table cell
text for use in other table cell computations.

Steps to Reproduce:
1.In Writer document Insert new table with two rows and three columns.
2.Populate table column two with non-zero numerical values.
3.Below table enter text "Test text field _ value." and attempt to insert
Formula field with '*4*4' where '_' is shown. Note: "faulty" mesg.
4.Right click on text formula field and edit text field formula "
replacing with value entered in table cell B1. Note: correct gray value. 
5.Highlight and copy (Ctrl-C) entire text line below table and paste (Ctrl-V)
in table cell A2. Note: text shown with gray formula field in table cell.
6.Click on table cell C2 and press F2.  Enter formula "=*" and press
enter. Note: value in table cell C2 is zero instead of calculated value.


Actual Results:
See above; "** Expression is faulty **" instead of table cell value
calculation.
See above; Table cell "0" instead of correct calculated value.

Expected Results:
Calculated table cell *4*4 in gray text formula field.
Calculated text formula field using table cells as selected.


Reproducible: Always


User Profile Reset: No

Additional Info:
Documentation implies table cells can be included in Formulas if enclosed in
angle brackets <>.  Can provide TableDoc.odt as attachment.  Recognition of
table cells in text formula fields and visa versa would significantly improve
the usefulness of this feature.

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

[Libreoffice-bugs] [Bug 152657] Extreme slow graphical performance and laggy behavior with LO Calc 7.4.3.2 on Linux Mint 20.3

2022-12-30 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=152657

--- Comment #8 from lp.allar...@gmail.com ---
Just closed Calc and noticed this in "dmesg".. Not sure if related or not but
former LO versions did not segfault in any way (was very rare):

soffice.bin[24252]: segfault at 7f09207fa780 ip 7f0957a7b920 sp
7ffc4517a758 error 4 in libuno_sal.so.3[7f0957a6+68000]

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

[Libreoffice-bugs] [Bug 152716] Crash in: com::sun::star::uno::Any::Any(com::sun::star::uno::Any const &)

2022-12-30 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=152716

Julien Nabet  changed:

   What|Removed |Added

 OS|All |Windows (All)
   Hardware|All |x86-64 (AMD64)
Version|unspecified |7.4.3.2 release

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

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

2022-12-30 Thread Bogdan B (via logerrit)
 sw/uiconfig/swriter/ui/tocindexpage.ui |2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

New commits:
commit 7e6b8359b6f8833608a0574bd2931b6a62d92847
Author: Bogdan B 
AuthorDate: Wed Dec 28 19:21:07 2022 +
Commit: Adolfo Jayme Barrientos 
CommitDate: Fri Dec 30 21:38:47 2022 +

tdf#151065 Improve extended tip about bibliography

Change-Id: Ib712e9fed6ee81f3afdffbabcb3e05bd0ef72bd3
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/144808
Tested-by: Jenkins
Reviewed-by: Vernon, Stuart Foote 
Reviewed-by: Adolfo Jayme Barrientos 

diff --git a/sw/uiconfig/swriter/ui/tocindexpage.ui 
b/sw/uiconfig/swriter/ui/tocindexpage.ui
index 30512584e55c..aa87d26cdfa8 100644
--- a/sw/uiconfig/swriter/ui/tocindexpage.ui
+++ b/sw/uiconfig/swriter/ui/tocindexpage.ui
@@ -877,7 +877,7 @@
 
 
   
-Select the 
brackets that you want to enclose bibliography entries.
+Select the 
brackets used to enclose bibliography entries.
   
 
   


[Libreoffice-bugs] [Bug 152657] Extreme slow graphical performance and laggy behavior with LO Calc 7.4.3.2 on Linux Mint 20.3

2022-12-30 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=152657

--- Comment #7 from lp.allar...@gmail.com ---
Bonjour Stephane,

I attached a sample ODS file (Test ODS) made from scratch because my real life
examples contain confidential data and I cannot share them...

The lack of performance on this "test" file is not as bad as with my real files
and I believe it is because the amount of formatting and overall file size is
very different (the test file has only one tab while my real files have 15 to
20 tabs each, and the file size is 31kb VS 1.5MB for my other files)...

As you asked, I am observing performance issues with new (empty) files but on a
lower scale... The more the file grows, the more the performance hit seems to
be big.

I also attached a small video showing an example of performance hit while
typing text (Lag example).  Please note this "lag" also occurs while typing
formulae making it extremely difficult not to make errors..  Keep in mind
that the ODS file shown in the video is BLANK and there's a noticeable lag, so
imagine with a LARGE spreadsheet where the computers is many seconds behind me
when typing...

I made an interesting discovery.  If I make the Calc window pretty small, the
performance hit almost disappear. The larger I make the window the more severe
the "lag" is (see attachment "Window effect on lag").

Finally as requested, system info:

Version: 7.4.3.2 / LibreOffice Community
Build ID: 1048a8393ae2eeec98dff31b5c133c5f1d08b890
CPU threads: 4; OS: Linux 5.4; UI render: default; VCL: gtk3
Locale: en-CA (en_CA.UTF-8); UI: en-US
Calc: CL

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

[Libreoffice-commits] core.git: Branch 'libreoffice-7-5' - svx/source

2022-12-30 Thread Khaled Hosny (via logerrit)
 svx/source/dialog/fntctrl.cxx|4 +++-
 svx/source/styles/CommonStylePreviewRenderer.cxx |4 +++-
 2 files changed, 6 insertions(+), 2 deletions(-)

New commits:
commit 85f161ac76a07bcd1dd2080e4bda8f11a600262d
Author: Khaled Hosny 
AuthorDate: Fri Dec 30 18:56:41 2022 +0200
Commit: Adolfo Jayme Barrientos 
CommitDate: Fri Dec 30 21:36:00 2022 +

tdf#152737: Fix off-by-one errors

Regressions from:

commit 718af940435ae9d2ac90374e5880ecb38e96252c
Author: Khaled Hosny 
Date:   Fri Dec 16 00:10:34 2022 +0200

tdf#152533: Improve script handling in font preview

and:

commit bfecacb2487ba9470600e6f64056d9b1816ee96b
Author: Khaled Hosny 
Date:   Thu Dec 15 22:51:54 2022 +0200

tdf#152460: Improve script handling in style previews

Change-Id: I7b12f5accbd65459d724676efb7bec947a7faaa0
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/144880
Tested-by: Jenkins
Reviewed-by: خالد حسني 
(cherry picked from commit 95f0dc2dc74401a097105fcfe745aba3e571d9c4)
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/144898
Reviewed-by: Adolfo Jayme Barrientos 

diff --git a/svx/source/dialog/fntctrl.cxx b/svx/source/dialog/fntctrl.cxx
index 0712bbe92496..de39993061fd 100644
--- a/svx/source/dialog/fntctrl.cxx
+++ b/svx/source/dialog/fntctrl.cxx
@@ -250,7 +250,9 @@ void FontPrevWin_Impl::CheckScript()
 for (sal_Int32 i = 1; i <= maScriptText.getLength(); i++)
 {
 auto aNextScript = aEditEngine.GetScriptType({ 0, i, 0, i });
-if (aNextScript != aScript || i == maScriptText.getLength())
+if (aNextScript != aScript)
+maScriptChanges.emplace_back(aScript, i - 1);
+else if (i == maScriptText.getLength())
 maScriptChanges.emplace_back(aScript, i);
 aScript = aNextScript;
 }
diff --git a/svx/source/styles/CommonStylePreviewRenderer.cxx 
b/svx/source/styles/CommonStylePreviewRenderer.cxx
index 9ddf3cf15017..0ca34abe9a36 100644
--- a/svx/source/styles/CommonStylePreviewRenderer.cxx
+++ b/svx/source/styles/CommonStylePreviewRenderer.cxx
@@ -418,7 +418,9 @@ void CommonStylePreviewRenderer::CheckScript()
 for (sal_Int32 i = 1; i <= maScriptText.getLength(); i++)
 {
 auto aNextScript = aEditEngine.GetScriptType({ 0, i, 0, i });
-if (aNextScript != aScript || i == maScriptText.getLength())
+if (aNextScript != aScript)
+maScriptChanges.emplace_back(aScript, i - 1);
+else if (i == maScriptText.getLength())
 maScriptChanges.emplace_back(aScript, i);
 aScript = aNextScript;
 }


[Libreoffice-bugs] [Bug 152657] Extreme slow graphical performance and laggy behavior with LO Calc 7.4.3.2 on Linux Mint 20.3

2022-12-30 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=152657

--- Comment #6 from lp.allar...@gmail.com ---
Created attachment 184403
  --> https://bugs.documentfoundation.org/attachment.cgi?id=184403=edit
Window size effect on lag

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

[Libreoffice-bugs] [Bug 152657] Extreme slow graphical performance and laggy behavior with LO Calc 7.4.3.2 on Linux Mint 20.3

2022-12-30 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=152657

--- Comment #5 from lp.allar...@gmail.com ---
Created attachment 184402
  --> https://bugs.documentfoundation.org/attachment.cgi?id=184402=edit
Lag example

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

[Libreoffice-bugs] [Bug 152657] Extreme slow graphical performance and laggy behavior with LO Calc 7.4.3.2 on Linux Mint 20.3

2022-12-30 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=152657

--- Comment #4 from lp.allar...@gmail.com ---
Created attachment 184401
  --> https://bugs.documentfoundation.org/attachment.cgi?id=184401=edit
Test ODS

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

[Libreoffice-bugs] [Bug 152477] CRASH: After copying cell(s) to clipboard and closing Calc, crash report dialog is shown at next session (Cinnamon, MATE)

2022-12-30 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=152477

Julien Nabet  changed:

   What|Removed |Added

 CC|serval2...@yahoo.fr |

--- Comment #30 from Julien Nabet  ---
I tried gtk and gen rendering and can't reproduce this.
I don't have XFCE and LXDE, don't know Deepin and Cinnamon is specific Mint I
think.
=> uncc myself.

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

[Libreoffice-bugs] [Bug 152742] Writer tells me I'm writing Afrikaans - but I never chose that

2022-12-30 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=152742

Eyal Rozenberg  changed:

   What|Removed |Added

 Blocks||43808
   Keywords||regression

--- Comment #1 from Eyal Rozenberg  ---
This doesn't happen with 7.4.3.2, but does happen with:

Version: 7.6.0.0.alpha0+ (X86_64) / LibreOffice Community
Build ID: ad387d5b984c906505d25685065f710ed55d
CPU threads: 4; OS: Linux 6.0; UI render: default; VCL: gtk3
Locale: en-IL (en_IL); UI: en-US


Referenced Bugs:

https://bugs.documentfoundation.org/show_bug.cgi?id=43808
[Bug 43808] [META] Right-To-Left and Complex Text Layout language issues
(RTL/CTL)
-- 
You are receiving this mail because:
You are the assignee for the bug.

[Libreoffice-bugs] [Bug 43808] [META] Right-To-Left and Complex Text Layout language issues (RTL/CTL)

2022-12-30 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=43808

Eyal Rozenberg  changed:

   What|Removed |Added

 Depends on||152742


Referenced Bugs:

https://bugs.documentfoundation.org/show_bug.cgi?id=152742
[Bug 152742] Writer tells me I'm writing Afrikaans - but I never chose that
-- 
You are receiving this mail because:
You are the assignee for the bug.

[Libreoffice-bugs] [Bug 152742] New: Writer tells me I'm writing Afrikaans - but I never chose that

2022-12-30 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=152742

Bug ID: 152742
   Summary: Writer tells me I'm writing Afrikaans - but I never
chose that
   Product: LibreOffice
   Version: Inherited From OOo
  Hardware: All
OS: Linux (All)
Status: UNCONFIRMED
  Severity: minor
  Priority: medium
 Component: Writer
  Assignee: libreoffice-bugs@lists.freedesktop.org
  Reporter: eyalr...@gmx.com

My documents use English as the Western LG language. However, for a while now,
with LO 7.5 and then LO 7.6 nightlies, the Western LG I see on the bottom
status bar, and in the font selection dialog for Western languages, is
"Afrikaans (Namibia)".

I've never chosen Afrikaans. I believe somehow it gets chosen because it's the
first item on the languages menu - even though LO does know that there's a
default that may be different (for me it's "English (Israel)").

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

[Libreoffice-bugs] [Bug 139004] Crash with non-debug & assertion dynamic_cast(static_cast(pOldValue)->pChangedFormat)", file=ndtxt.cxx", line=5437

2022-12-30 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=139004

Telesto  changed:

   What|Removed |Added

Summary|Crash deleting applied  |Crash with non-debug &
   |footnote paragraph style|assertion
   |(swlo!SwList::GetDefaultLis |dynamic_cast(static_cast(pOldValue)->p
   ||ChangedFormat)",
   ||file=ndtxt.cxx", line=5437

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

[Libreoffice-bugs] [Bug 139004] Crash deleting applied footnote paragraph style (swlo!SwList::GetDefaultListStyleName+0x360)

2022-12-30 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=139004

Julien Nabet  changed:

   What|Removed |Added

   Keywords|wantBacktrace   |haveBacktrace

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

[Libreoffice-bugs] [Bug 139004] Crash deleting applied footnote paragraph style (swlo!SwList::GetDefaultListStyleName+0x360)

2022-12-30 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=139004

--- Comment #5 from Julien Nabet  ---
Created attachment 184400
  --> https://bugs.documentfoundation.org/attachment.cgi?id=184400=edit
gdb bt

On pc Debian x86-64 with master sources updated today, I could reproduce this.
Here's bt and some infos from gdb.

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

[Libreoffice-bugs] [Bug 152741] New: Single line plain text content control created with MS Word not recognized by Libre Office

2022-12-30 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=152741

Bug ID: 152741
   Summary: Single line plain text content control created with MS
Word not recognized by Libre Office
   Product: LibreOffice
   Version: 7.4.3.2 release
  Hardware: All
OS: Windows (All)
Status: UNCONFIRMED
  Severity: normal
  Priority: medium
 Component: LibreOffice
  Assignee: libreoffice-bugs@lists.freedesktop.org
  Reporter: luigi.prado...@sympatico.ca

Description:
I created a form with MS Word. I added single line plain text content controls
(text box). When the form is opened with Libre Office, it does not recognize
that these text boxes should be single line and allows multiple lines. Libre
Office does not trap the carriage returns. 

Steps to Reproduce:
1. Use MS Word to create a form with single line plain text content controls
2. Make sure they are single line. Save document.
3. Open document with LibreOffice
4. Type text in the single line controls. Press ENTER to type a second line.
5. Should not be able to add a second line since it was created as single line.
6. LibreOffice does not trap carriage returns.

Actual Results:
Multiple lines can be created in a single line text control.

Expected Results:
Single line only


Reproducible: Always


User Profile Reset: No

Additional Info:
[Information automatically included from LibreOffice]
Locale: en-US
Module: StartModule
[Information guessed from browser]
OS: Windows (All)
OS is 64bit: yes

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

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

2022-12-30 Thread Khaled Hosny (via logerrit)
 vcl/source/gdi/CommonSalLayout.cxx |   15 ++-
 1 file changed, 2 insertions(+), 13 deletions(-)

New commits:
commit 3344de28f6ddb559281d0b2c28f475a3e54fe7af
Author: Khaled Hosny 
AuthorDate: Fri Dec 30 17:39:24 2022 +0200
Commit: خالد حسني 
CommitDate: Fri Dec 30 20:23:22 2022 +

vcl: Simplify this code and remove the funny comment

Change-Id: Ia57f79ccb656eb570c4e481154eb6e74e2a32bd8
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/144879
Tested-by: Jenkins
Reviewed-by: خالد حسني 

diff --git a/vcl/source/gdi/CommonSalLayout.cxx 
b/vcl/source/gdi/CommonSalLayout.cxx
index 92b090222481..5997ea375192 100644
--- a/vcl/source/gdi/CommonSalLayout.cxx
+++ b/vcl/source/gdi/CommonSalLayout.cxx
@@ -772,21 +772,10 @@ void GenericSalLayout::ApplyDXArray(const double* 
pDXArray, const sal_Bool* pKas
 m_GlyphItems[i].addNewWidth(nDiff);
 m_GlyphItems[i].adjustLinearPosX(nDelta + nDiff);
 
-// Warning:
-// If you are tempted to improve the two loops below, think again.
-// Even though I wrote this code, I no longer understand how it
-// works, and every time I think I finally got it, I introduce a
-// bug. - Khaled
-
 // Adjust the X position of the rest of the glyphs in the cluster.
-size_t j = i;
-while (j > 0)
-{
---j;
-if (!m_GlyphItems[j].IsInCluster())
-break;
+// We iterate backwards since this is an RTL glyph.
+for (int j = i - 1; j >= 0 && m_GlyphItems[j].IsInCluster(); j--)
 m_GlyphItems[j].adjustLinearPosX(nDelta + nDiff);
-}
 
 // This is a Kashida insertion position, mark it. Kashida glyphs
 // will be inserted below.


[Libreoffice-bugs] [Bug 152739] Round ROUND_HALF_UP is OK in Python, but NO in Basic when call the same Python def.

2022-12-30 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=152739

--- Comment #1 from e...@helpidea.net ---
Created attachment 184399
  --> https://bugs.documentfoundation.org/attachment.cgi?id=184399=edit
macro

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

[Libreoffice-bugs] [Bug 152740] New: [LOCALHELP] Files hid2file.js and /bookmark.js not delivered in 'libreoffice-7-5' branch

2022-12-30 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=152740

Bug ID: 152740
   Summary: [LOCALHELP] Files hid2file.js and /bookmark.js
not delivered in 'libreoffice-7-5' branch
   Product: LibreOffice
   Version: unspecified
  Hardware: All
OS: All
Status: UNCONFIRMED
  Severity: normal
  Priority: medium
 Component: Documentation
  Assignee: libreoffice-bugs@lists.freedesktop.org
  Reporter: olivier.hal...@libreoffice.org
CC: olivier.hal...@libreoffice.org

The Helpcontent2 build process for branch libreoffice-7-5 does not deliver 2
files:
hid2file.js
/bookmark.js

Step to reproduce:
1) Build online help with autogen.sh parameters:
--with-lang=ALL
--with-help=online
--with-omindex=server

2) Inspect results

Actual results:
missing contents in 2 files

instdir/help/7.5/hid2file.js (files is 23B size, should be ~700 KB)

instdir/help/7.5//bookmarks.js (21B size, should be ~800 KB)

Note: files exist but has no contents.

Expected results:
Files with their respective contents

Note: no build issue with master branch

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

[Libreoffice-bugs] [Bug 139194] Non-matching parentheses/brackets in math formulas

2022-12-30 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=139194

--- Comment #9 from Bruno Grenet  ---
I confirm that the bug is still present with the most recent downloadable
version of Libreoffice. Tested with the following configuration:

Version: 7.4.3.2 / LibreOffice Community
Build ID: 1048a8393ae2eeec98dff31b5c133c5f1d08b890
CPU threads: 8; OS: Linux 5.15; UI render: default; VCL: gtk3
Locale: fr-FR (fr_FR.UTF-8); UI: en-US
Calc: threaded

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

[Libreoffice-bugs] [Bug 151769] Text disappearing from slide after saving presentation with animation

2022-12-30 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=151769

--- Comment #10 from Bob Corbin  ---
After reading the string of comments.  I see the "animation" tie.

To overcome the issue, I have had to make numerous slides.  (* A slide for
every animation, and have the slides advance automatically instead of as a
direct animation "after previous." *)

So that would seem to corroborate animation within a slide.

However, it only seems to pop on certain slides.  Not every slide with
animation is targeted.

So, maybe a specification animation?  or sequence of animations?

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

[Libreoffice-commits] core.git: Branch 'libreoffice-7-5' - download.lst external/hunspell

2022-12-30 Thread László Németh (via logerrit)
 download.lst   
   |4 
 
external/hunspell/0001-check-len-in-cpdpat_check-like-r1-blen-is-checked-63.patch
 |   27 ---
 
external/hunspell/0001-fix-LibreOffice-build-problem-with-basic_string-appe.patch
 |   84 ++
 external/hunspell/0001-improve-630-test-case-from-0m1.836s-0m1.223s-785.patch  
   |   52 --
 external/hunspell/0001-improve-630-test-case-from-0m2.427s-0m1.836s-781.patch  
   |   40 
 external/hunspell/UnpackedTarball_hunspell.mk  
   |4 
 6 files changed, 87 insertions(+), 124 deletions(-)

New commits:
commit 82e1d31b291b4d5c41161a12e4f8ea3fb3ba7849
Author: László Németh 
AuthorDate: Thu Dec 29 22:09:55 2022 +0100
Commit: Adolfo Jayme Barrientos 
CommitDate: Fri Dec 30 19:13:03 2022 +

upgrade to hunspell 1.7.2

Change-Id: If969eccc73926911a4a09440623adf83b8e2c520
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/144869
Tested-by: Jenkins
Reviewed-by: László Németh 
(cherry picked from commit 247e161cf1dca6811998b67d1138062fa4e14381)
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/144896
Reviewed-by: Adolfo Jayme Barrientos 

diff --git a/download.lst b/download.lst
index f193a571d4ee..abfe6e9eaedc 100644
--- a/download.lst
+++ b/download.lst
@@ -228,8 +228,8 @@ HSQLDB_TARBALL := 
17410483b5b5f267aa18b7e00b65e6e0-hsqldb_1_8_0.zip
 # three static lines
 # so that git cherry-pick
 # will not run into conflicts
-HUNSPELL_SHA256SUM := 
b2d9c5369c2cc7f321cb5983fda2dbf007dce3d9e17519746840a6f0c4bf7444
-HUNSPELL_TARBALL := hunspell-1.7.1.tar.gz
+HUNSPELL_SHA256SUM := 
11ddfa39afe28c28539fe65fc4f1592d410c1e9b6dd7d8a91ca25d85e9ec65b8
+HUNSPELL_TARBALL := hunspell-1.7.2.tar.gz
 # three static lines
 # so that git cherry-pick
 # will not run into conflicts
diff --git 
a/external/hunspell/0001-check-len-in-cpdpat_check-like-r1-blen-is-checked-63.patch
 
b/external/hunspell/0001-check-len-in-cpdpat_check-like-r1-blen-is-checked-63.patch
deleted file mode 100644
index 58b68d0dda43..
--- 
a/external/hunspell/0001-check-len-in-cpdpat_check-like-r1-blen-is-checked-63.patch
+++ /dev/null
@@ -1,27 +0,0 @@
-From 56ad6310c95695d25f936d3f89f6ee3d787df274 Mon Sep 17 00:00:00 2001
-From: =?UTF-8?q?Caol=C3=A1n=20McNamara?= 
-Date: Mon, 22 Aug 2022 21:21:36 +0100
-Subject: [PATCH] check 'len' in cpdpat_check like 'r1->blen' is checked (#633)
- (#780)
-
-we should check len against pos like we do r1->blen in the line above

- src/hunspell/affixmgr.cxx | 2 +-
- 1 file changed, 1 insertion(+), 1 deletion(-)
-
-diff --git a/src/hunspell/affixmgr.cxx b/src/hunspell/affixmgr.cxx
-index 7ea1ea5..c2432c0 100644
 a/src/hunspell/affixmgr.cxx
-+++ b/src/hunspell/affixmgr.cxx
-@@ -1330,7 +1330,7 @@ int AffixMgr::cpdpat_check(const char* word,
-  ((checkcpdtable[i].pattern[0] == '0' && r1->blen <= pos &&
-strncmp(word + pos - r1->blen, r1->word, r1->blen) == 0) ||
-   (checkcpdtable[i].pattern[0] != '0' &&
--   ((len = checkcpdtable[i].pattern.size()) != 0) &&
-+   ((len = checkcpdtable[i].pattern.size()) != 0) && len <= pos &&
-strncmp(word + pos - len, checkcpdtable[i].pattern.c_str(), len) 
== 0 {
-   return 1;
- }
--- 
-2.37.2
-
diff --git 
a/external/hunspell/0001-fix-LibreOffice-build-problem-with-basic_string-appe.patch
 
b/external/hunspell/0001-fix-LibreOffice-build-problem-with-basic_string-appe.patch
new file mode 100644
index ..3c6f9831b2b4
--- /dev/null
+++ 
b/external/hunspell/0001-fix-LibreOffice-build-problem-with-basic_string-appe.patch
@@ -0,0 +1,84 @@
+From 1587ea4ab5e8d94c9c0d552f7ab61c217ebdcbeb Mon Sep 17 00:00:00 2001
+From: =?UTF-8?q?L=C3=A1szl=C3=B3=20N=C3=A9meth?= 
+Date: Fri, 30 Dec 2022 12:20:02 +0100
+Subject: [PATCH] fix LibreOffice build problem with basic_string::append()
+
+---
+ src/hunspell/affentry.cxx | 6 +++---
+ src/hunspell/affixmgr.cxx | 8 
+ 2 files changed, 7 insertions(+), 7 deletions(-)
+
+diff --git a/src/hunspell/affentry.cxx b/src/hunspell/affentry.cxx
+index 46e8b58..6ee23be 100644
+--- a/src/hunspell/affentry.cxx
 b/src/hunspell/affentry.cxx
+@@ -290,7 +290,7 @@ struct hentry* PfxEntry::check_twosfx(const std::string& 
word,
+ // back any characters that would have been stripped
+ 
+ std::string tmpword(strip);
+-tmpword.append(word, start + appnd.size());
++tmpword.append(word, start + appnd.size(), tmpl);
+ 
+ // now make sure all of the conditions on characters
+ // are met.  Please see the appendix at the end of
+@@ -338,7 +338,7 @@ std::string PfxEntry::check_twosfx_morph(const 
std::string& word,
+ // back any characters that would have been stripped
+ 
+ std::string tmpword(strip);
+-tmpword.append(word, start + appnd.size());
++tmpword.append(word, start + appnd.size(), tmpl);
+ 
+ // now make sure all of the conditions on characters
+ // 

[Libreoffice-commits] core.git: Branch 'libreoffice-7-5' - vcl/source

2022-12-30 Thread Khaled Hosny (via logerrit)
 vcl/source/gdi/CommonSalLayout.cxx |   11 +++
 1 file changed, 7 insertions(+), 4 deletions(-)

New commits:
commit 062da9b0d5a44f47fb3fb3e15c7c2a3e9b6a70b8
Author: Khaled Hosny 
AuthorDate: Fri Dec 30 17:36:27 2022 +0200
Commit: Adolfo Jayme Barrientos 
CommitDate: Fri Dec 30 19:10:28 2022 +

tdf#152734: Calculate correctly the kashida glyph X position

Change-Id: I4c76aed58acd0598b9d09d147ed86e76ef468c4f
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/144878
Tested-by: Jenkins
Reviewed-by: خالد حسني 
(cherry picked from commit a838f92bb4b1bdc84f49c61f669b1f32ee1f83c3)
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/144897
Reviewed-by: Adolfo Jayme Barrientos 

diff --git a/vcl/source/gdi/CommonSalLayout.cxx 
b/vcl/source/gdi/CommonSalLayout.cxx
index 5cde002661d3..92b090222481 100644
--- a/vcl/source/gdi/CommonSalLayout.cxx
+++ b/vcl/source/gdi/CommonSalLayout.cxx
@@ -727,7 +727,7 @@ void GenericSalLayout::ApplyDXArray(const double* pDXArray, 
const sal_Bool* pKas
 
 // Map of Kashida insertion points (in the glyph items vector) and the
 // requested width.
-std::map pKashidas;
+std::map> pKashidas;
 
 // The accumulated difference in X position.
 double nDelta = 0;
@@ -791,7 +791,7 @@ void GenericSalLayout::ApplyDXArray(const double* pDXArray, 
const sal_Bool* pKas
 // This is a Kashida insertion position, mark it. Kashida glyphs
 // will be inserted below.
 if (pKashidaArray && pKashidaArray[nCharPos])
-pKashidas[i] = nDiff;
+pKashidas[i] = { nDiff, pNewCharWidths[nCharPos] };
 
 i++;
 }
@@ -823,7 +823,7 @@ void GenericSalLayout::ApplyDXArray(const double* pDXArray, 
const sal_Bool* pKas
 auto pGlyphIter = m_GlyphItems.begin() + nInserted + pKashida.first;
 
 // The total Kashida width.
-double nTotalWidth = pKashida.second;
+auto const& [nTotalWidth, nClusterWidth] = pKashida.second;
 
 // Number of times to repeat each Kashida.
 int nCopies = 1;
@@ -842,9 +842,12 @@ void GenericSalLayout::ApplyDXArray(const double* 
pDXArray, const sal_Bool* pKas
 nOverlap = nExcess / (nCopies - 1);
 }
 
-DevicePoint aPos(pGlyphIter->linearPos().getX() - nTotalWidth, 0);
+DevicePoint aPos = pGlyphIter->linearPos();
 int nCharPos = pGlyphIter->charPos();
 GlyphItemFlags const nFlags = GlyphItemFlags::IS_IN_CLUSTER | 
GlyphItemFlags::IS_RTL_GLYPH;
+// Move to the left side of the adjusted width and start inserting
+// glyphs there.
+aPos.adjustX(-nClusterWidth + pGlyphIter->origWidth());
 while (nCopies--)
 {
 GlyphItem aKashida(nCharPos, 0, nKashidaIndex, aPos, nFlags, 
nKashidaWidth, 0, 0);


[Libreoffice-bugs] [Bug 44597] FORMATTING: Margin notes (similar to footnotes, but vertically linked to content) should be enabled

2022-12-30 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=44597

V Stuart Foote  changed:

   What|Removed |Added

 CC||s.bu...@o2.pl

--- Comment #19 from V Stuart Foote  ---
*** Bug 152725 has been marked as a duplicate of this bug. ***

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

[Libreoffice-bugs] [Bug 152725] I propose a new function for Writer - Marginalia (i.e. sidenotes)

2022-12-30 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=152725

V Stuart Foote  changed:

   What|Removed |Added

 Resolution|--- |DUPLICATE
 Status|UNCONFIRMED |RESOLVED
 CC||vsfo...@libreoffice.org

--- Comment #2 from V Stuart Foote  ---
Available as frame with style "Marginalia"

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

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

[Libreoffice-bugs] [Bug 152363] Libreoffice hangs when trying to save / editing

2022-12-30 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=152363

--- Comment #9 from BogdanB  ---
Telesto, you have the same conditions in comment 4 and in comment 8. It's the
same windows, UI render: Skia/Raster; VCL: win.

So, it seems something change to better.

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

[Libreoffice-commits] core.git: 2 commits - sc/inc sc/source

2022-12-30 Thread Noel Grandin (via logerrit)
 sc/inc/scmatrix.hxx  |5 
 sc/source/core/tool/compiler.cxx |  225 ++---
 sc/source/core/tool/interpr5.cxx |  109 +++---
 sc/source/core/tool/scmatrix.cxx |  231 ---
 4 files changed, 400 insertions(+), 170 deletions(-)

New commits:
commit 9713a4aae980a52d08d38f5b12424aa5e33f9a75
Author: Noel Grandin 
AuthorDate: Wed Dec 28 17:30:12 2022 +0200
Commit: Noel Grandin 
CommitDate: Fri Dec 30 18:59:48 2022 +

optimise SUMPRODUCT(IF..) where we have entire column/row ranges

following the same pattern as for SUM, set those ranges to shrink to
available data.

Takes it from 3s to <500ms on my test spreadsheet.

Change-Id: I53ada996393a063b12ef7dd0f9bff40c90ecc8be
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/144850
Tested-by: Jenkins
Reviewed-by: Noel Grandin 

diff --git a/sc/source/core/tool/compiler.cxx b/sc/source/core/tool/compiler.cxx
index e55a7e923c19..f97bff3053dd 100644
--- a/sc/source/core/tool/compiler.cxx
+++ b/sc/source/core/tool/compiler.cxx
@@ -6465,89 +6465,178 @@ void ScCompiler::AnnotateTrimOnDoubleRefs()
 // OpCode of the "root" operator (which is already in RPN array).
 OpCode eOpCode = (*(pCode - 1))->GetOpCode();
 // eOpCode can be some operator which does not change with operands with 
or contains zero values.
-if (eOpCode != ocSum)
-return;
+if (eOpCode == ocSum)
+{
+FormulaToken** ppTok = pCode - 2; // exclude the root operator.
+// The following loop runs till a "pattern" is found or there is a 
mismatch
+// and marks the push DoubleRef arguments as trimmable when there is a 
match.
+// The pattern is
+// SUM(IF(=, ))
+// such that one of the operands of ocEqual is a double-ref.
+// Examples of formula that matches this are:
+//   SUM(IF(D:D=$A$1,F:F)*$H$1*2.3/$G$2)
+//   SUM((IF(D:D=$A$1,F:F)*$H$1*2.3/$G$2)*$H$2*5/$G$3)
+//   SUM(IF(E:E=16,F:F)*$H$1*100)
+bool bTillClose = true;
+bool bCloseTillIf = false;
+sal_Int16 nToksTillIf = 0;
+constexpr sal_Int16 MAXDIST_IF = 15;
+while (*ppTok)
+{
+FormulaToken* pTok = *ppTok;
+OpCode eCurrOp = pTok->GetOpCode();
+++nToksTillIf;
+
+// TODO : Is there a better way to handle this ?
+// ocIf is too far off from the sum opcode.
+if (nToksTillIf > MAXDIST_IF)
+return;
 
-FormulaToken** ppTok = pCode - 2; // exclude the root operator.
-// The following loop runs till a "pattern" is found or there is a mismatch
-// and marks the push DoubleRef arguments as trimmable when there is a 
match.
-// The pattern is
-// SUM(IF(=, ))
-// such that one of the operands of ocEqual is a double-ref.
-// Examples of formula that matches this are:
-//   SUM(IF(D:D=$A$1,F:F)*$H$1*2.3/$G$2)
-//   SUM((IF(D:D=$A$1,F:F)*$H$1*2.3/$G$2)*$H$2*5/$G$3)
-//   SUM(IF(E:E=16,F:F)*$H$1*100)
-bool bTillClose = true;
-bool bCloseTillIf = false;
-sal_Int16 nToksTillIf = 0;
-constexpr sal_Int16 MAXDIST_IF = 15;
-while (*ppTok)
-{
-FormulaToken* pTok = *ppTok;
-OpCode eCurrOp = pTok->GetOpCode();
-++nToksTillIf;
-
-// TODO : Is there a better way to handle this ?
-// ocIf is too far off from the sum opcode.
-if (nToksTillIf > MAXDIST_IF)
-return;
+switch (eCurrOp)
+{
+case ocDiv:
+case ocMul:
+if (!bTillClose)
+return;
+break;
+case ocPush:
 
-switch (eCurrOp)
-{
-case ocDiv:
-case ocMul:
-if (!bTillClose)
-return;
-break;
-case ocPush:
+break;
+case ocClose:
+if (bTillClose)
+{
+bTillClose = false;
+bCloseTillIf = true;
+}
+else
+return;
+break;
+case ocIf:
+{
+if (!bCloseTillIf)
+return;
 
-break;
-case ocClose:
-if (bTillClose)
-{
-bTillClose = false;
-bCloseTillIf = true;
-}
-else
+if (!pTok->IsInForceArray())
+return;
+
+const short nJumpCount = pTok->GetJump()[0];
+if (nJumpCount != 2) // Should have THEN but no ELSE.
+return;
+
+OpCode eCompOp = 

[Libreoffice-bugs] [Bug 151769] Text disappearing from slide after saving presentation with animation

2022-12-30 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=151769

Telesto  changed:

   What|Removed |Added

 CC||b...@corbinhome.net

--- Comment #9 from Telesto  ---
*** Bug 152735 has been marked as a duplicate of this bug. ***

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

[Libreoffice-bugs] [Bug 152735] Deleting text in text box (Editing, FileSave, or FileOpen ... not sure)

2022-12-30 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=152735

Telesto  changed:

   What|Removed |Added

 Status|UNCONFIRMED |RESOLVED
 Resolution|--- |DUPLICATE
 CC||tele...@surfxs.nl

--- Comment #1 from Telesto  ---
Probably bug 151769, based on the description.

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

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

[Libreoffice-bugs] [Bug 152739] New: Round ROUND_HALF_UP is OK in Python, but NO in Basic when call the same Python def.

2022-12-30 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=152739

Bug ID: 152739
   Summary: Round ROUND_HALF_UP is OK in Python, but NO in Basic
when call the same Python def.
   Product: LibreOffice
   Version: 7.1.8.1 release
  Hardware: All
OS: Windows (All)
Status: UNCONFIRMED
  Severity: normal
  Priority: medium
 Component: BASIC
  Assignee: libreoffice-bugs@lists.freedesktop.org
  Reporter: e...@helpidea.net

Description:
I have a Python function for round up numbers, that works fine:

' # RoundUP.py  file in Script 
' from decimal import Decimal, getcontext, ROUND_HALF_UP  # # Round UP
' round_context = getcontext()
' round_context.rounding = ROUND_HALF_UP
' # -
' def roundUp(x, digits, precision=5):
' tmp = round(Decimal(x), precision)
' fRet = float(tmp.__round__(digits))
' return fRet

' # ---
' if __name__ == '__main__':
' fRU = roundUp(2.125, 2)  # -> 2.13
' fRU = roundUp(3.125, 2)  # -> 3.13
' fRU = roundUp(-2.125, 2)  # -> -2.13
' fRU = roundUp(4.125, 2)  # -> 4.13
' fRU = roundUp(2.225, 2)  # -> 2.23
' pass

I call that function from Basic, and the result change:
fRU = RoundUp(2.125, 2) ' 2.12

Now i have 2.12, not 2.13. Why ???

'---BASIC
Function RoundUp(num, dec) ' Number to Double Up
Dim vRoundUp

sFunctionPy = "vnd.sun.star.script:RoundUP.py$roundUp"& _
"?language=Python=user"
oMSPF = createUnoService( _
 "com.sun.star.script.provider.MasterScriptProviderFactory")
gScriptProvider = oMSPF.createScriptProvider("")
oScript = gScriptProvider.getScript(sFunctionPy)
vRoundUp = oScript.invoke(Array(num, dec), Array(), Array())
RoundUp = vRoundUp 
End Function

Steps to Reproduce:
1.Copy a  RoundUP.py  file in Script (the code is in Description above)
2.Run Main in Calc RounUP.ods
3.Examine the different results

Actual Results:
2.12

Expected Results:
2.13


Reproducible: Always


User Profile Reset: No

Additional Info:
Version: 7.1.8.1 (x64) / LibreOffice Community
Build ID: e1f30c802c3269a1d052614453f260e49458c82c
CPU threads: 16; OS: Windows 10.0 Build 22621; UI render: Skia/Raster; VCL: win
Locale: it-IT (it_IT); UI: it-IT
Calc: CL

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

[Libreoffice-bugs] [Bug 152363] Libreoffice hangs when trying to save / editing

2022-12-30 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=152363

--- Comment #8 from Telesto  ---
No issue either with
Version: 7.6.0.0.alpha0+ (X86_64) / LibreOffice Community
Build ID: d5a9722874871576b864feb7bd815f9f8bfaac48
CPU threads: 4; OS: Windows 6.3 Build 9600; UI render: Skia/Raster; VCL: win
Locale: nl-NL (nl_NL); UI: en-US
Calc: CL threaded

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

[Libreoffice-bugs] [Bug 152676] Writer: Compatibility options no longer saved as default

2022-12-30 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=152676

raal  changed:

   What|Removed |Added

  Regression By||Noel Grandin
 CC||noelgran...@gmail.com,
   ||r...@post.cz
 OS|Windows (All)   |All
   Keywords|bibisectRequest |bibisected, bisected

--- Comment #2 from raal  ---
This seems to have begun at the below commit.
Adding Cc: to Noel Grandin ; Could you possibly take a look at this one?
Thanks

b1e45cb8691d9f7987808526d3b910e5494bfbb5 is the first bad commit
commit b1e45cb8691d9f7987808526d3b910e5494bfbb5
Author: Jenkins Build User 
Date:   Mon Jul 26 22:20:17 2021 +0200

source sha:78adf246d5e99d0f5d91d2e03c1379b154289d8d

https://gerrit.libreoffice.org/c/core/+/119514

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

[Libreoffice-bugs] [Bug 108736] [META] Font text preview bugs and enhancements

2022-12-30 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=108736
Bug 108736 depends on bug 152737, which changed state.

Bug 152737 Summary: Font preview in Characters dialog uses the wrong font for 
first Complex character
https://bugs.documentfoundation.org/show_bug.cgi?id=152737

   What|Removed |Added

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

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

[Libreoffice-bugs] [Bug 108734] [META] Character dialog bugs and enhancements

2022-12-30 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=108734
Bug 108734 depends on bug 152737, which changed state.

Bug 152737 Summary: Font preview in Characters dialog uses the wrong font for 
first Complex character
https://bugs.documentfoundation.org/show_bug.cgi?id=152737

   What|Removed |Added

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

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

[Libreoffice-bugs] [Bug 43808] [META] Right-To-Left and Complex Text Layout language issues (RTL/CTL)

2022-12-30 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=43808
Bug 43808 depends on bug 152737, which changed state.

Bug 152737 Summary: Font preview in Characters dialog uses the wrong font for 
first Complex character
https://bugs.documentfoundation.org/show_bug.cgi?id=152737

   What|Removed |Added

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

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

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

2022-12-30 Thread Khaled Hosny (via logerrit)
 svx/source/dialog/fntctrl.cxx|4 +++-
 svx/source/styles/CommonStylePreviewRenderer.cxx |4 +++-
 2 files changed, 6 insertions(+), 2 deletions(-)

New commits:
commit 95f0dc2dc74401a097105fcfe745aba3e571d9c4
Author: Khaled Hosny 
AuthorDate: Fri Dec 30 18:56:41 2022 +0200
Commit: خالد حسني 
CommitDate: Fri Dec 30 18:35:22 2022 +

tdf#152737: Fix off-by-one errors

Regressions from:

commit 718af940435ae9d2ac90374e5880ecb38e96252c
Author: Khaled Hosny 
Date:   Fri Dec 16 00:10:34 2022 +0200

tdf#152533: Improve script handling in font preview

and:

commit bfecacb2487ba9470600e6f64056d9b1816ee96b
Author: Khaled Hosny 
Date:   Thu Dec 15 22:51:54 2022 +0200

tdf#152460: Improve script handling in style previews

Change-Id: I7b12f5accbd65459d724676efb7bec947a7faaa0
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/144880
Tested-by: Jenkins
Reviewed-by: خالد حسني 

diff --git a/svx/source/dialog/fntctrl.cxx b/svx/source/dialog/fntctrl.cxx
index 0712bbe92496..de39993061fd 100644
--- a/svx/source/dialog/fntctrl.cxx
+++ b/svx/source/dialog/fntctrl.cxx
@@ -250,7 +250,9 @@ void FontPrevWin_Impl::CheckScript()
 for (sal_Int32 i = 1; i <= maScriptText.getLength(); i++)
 {
 auto aNextScript = aEditEngine.GetScriptType({ 0, i, 0, i });
-if (aNextScript != aScript || i == maScriptText.getLength())
+if (aNextScript != aScript)
+maScriptChanges.emplace_back(aScript, i - 1);
+else if (i == maScriptText.getLength())
 maScriptChanges.emplace_back(aScript, i);
 aScript = aNextScript;
 }
diff --git a/svx/source/styles/CommonStylePreviewRenderer.cxx 
b/svx/source/styles/CommonStylePreviewRenderer.cxx
index 9ddf3cf15017..0ca34abe9a36 100644
--- a/svx/source/styles/CommonStylePreviewRenderer.cxx
+++ b/svx/source/styles/CommonStylePreviewRenderer.cxx
@@ -418,7 +418,9 @@ void CommonStylePreviewRenderer::CheckScript()
 for (sal_Int32 i = 1; i <= maScriptText.getLength(); i++)
 {
 auto aNextScript = aEditEngine.GetScriptType({ 0, i, 0, i });
-if (aNextScript != aScript || i == maScriptText.getLength())
+if (aNextScript != aScript)
+maScriptChanges.emplace_back(aScript, i - 1);
+else if (i == maScriptText.getLength())
 maScriptChanges.emplace_back(aScript, i);
 aScript = aNextScript;
 }


[Libreoffice-bugs] [Bug 152363] Libreoffice hangs when trying to save / editing

2022-12-30 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=152363

raal  changed:

   What|Removed |Added

 CC||r...@post.cz

--- Comment #7 from raal  ---
No repro with Version: 7.5.0.1.0+ (X86_64) / LibreOffice Community
Build ID: 09848e94d20c067499ad69edf81fa80a45d0a632
CPU threads: 4; OS: Linux 5.15; UI render: default; VCL: gtk3
Locale: cs-CZ (cs_CZ.UTF-8); UI: en-US
Calc: threaded

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

[Libreoffice-bugs] [Bug 150285] [META] Problems with Justified Arabic/Persian text

2022-12-30 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=150285
Bug 150285 depends on bug 152734, which changed state.

Bug 152734 Summary: There is a visible gap after inserted Kashida with some 
fonts
https://bugs.documentfoundation.org/show_bug.cgi?id=152734

   What|Removed |Added

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

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

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

2022-12-30 Thread Khaled Hosny (via logerrit)
 vcl/source/gdi/CommonSalLayout.cxx |   11 +++
 1 file changed, 7 insertions(+), 4 deletions(-)

New commits:
commit a838f92bb4b1bdc84f49c61f669b1f32ee1f83c3
Author: Khaled Hosny 
AuthorDate: Fri Dec 30 17:36:27 2022 +0200
Commit: خالد حسني 
CommitDate: Fri Dec 30 18:03:33 2022 +

tdf#152734: Calculate correctly the kashida glyph X position

Change-Id: I4c76aed58acd0598b9d09d147ed86e76ef468c4f
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/144878
Tested-by: Jenkins
Reviewed-by: خالد حسني 

diff --git a/vcl/source/gdi/CommonSalLayout.cxx 
b/vcl/source/gdi/CommonSalLayout.cxx
index 5cde002661d3..92b090222481 100644
--- a/vcl/source/gdi/CommonSalLayout.cxx
+++ b/vcl/source/gdi/CommonSalLayout.cxx
@@ -727,7 +727,7 @@ void GenericSalLayout::ApplyDXArray(const double* pDXArray, 
const sal_Bool* pKas
 
 // Map of Kashida insertion points (in the glyph items vector) and the
 // requested width.
-std::map pKashidas;
+std::map> pKashidas;
 
 // The accumulated difference in X position.
 double nDelta = 0;
@@ -791,7 +791,7 @@ void GenericSalLayout::ApplyDXArray(const double* pDXArray, 
const sal_Bool* pKas
 // This is a Kashida insertion position, mark it. Kashida glyphs
 // will be inserted below.
 if (pKashidaArray && pKashidaArray[nCharPos])
-pKashidas[i] = nDiff;
+pKashidas[i] = { nDiff, pNewCharWidths[nCharPos] };
 
 i++;
 }
@@ -823,7 +823,7 @@ void GenericSalLayout::ApplyDXArray(const double* pDXArray, 
const sal_Bool* pKas
 auto pGlyphIter = m_GlyphItems.begin() + nInserted + pKashida.first;
 
 // The total Kashida width.
-double nTotalWidth = pKashida.second;
+auto const& [nTotalWidth, nClusterWidth] = pKashida.second;
 
 // Number of times to repeat each Kashida.
 int nCopies = 1;
@@ -842,9 +842,12 @@ void GenericSalLayout::ApplyDXArray(const double* 
pDXArray, const sal_Bool* pKas
 nOverlap = nExcess / (nCopies - 1);
 }
 
-DevicePoint aPos(pGlyphIter->linearPos().getX() - nTotalWidth, 0);
+DevicePoint aPos = pGlyphIter->linearPos();
 int nCharPos = pGlyphIter->charPos();
 GlyphItemFlags const nFlags = GlyphItemFlags::IS_IN_CLUSTER | 
GlyphItemFlags::IS_RTL_GLYPH;
+// Move to the left side of the adjusted width and start inserting
+// glyphs there.
+aPos.adjustX(-nClusterWidth + pGlyphIter->origWidth());
 while (nCopies--)
 {
 GlyphItem aKashida(nCharPos, 0, nKashidaIndex, aPos, nFlags, 
nKashidaWidth, 0, 0);


[Libreoffice-bugs] [Bug 152738] LO75RC1: Automatic spell-check on macOS not underlining misspelled words

2022-12-30 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=152738

Martin Srebotnjak  changed:

   What|Removed |Added

   Severity|normal  |major
 CC||nem...@numbertext.org

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

[Libreoffice-bugs] [Bug 152034] numbers have changed from comma to dot all 2, 5 are now 2.5

2022-12-30 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=152034

Mishy  changed:

   What|Removed |Added

 CC||mishy1...@gmail.com

--- Comment #6 from Mishy  ---
Sorry this was a not correct place for my previous comment.
The right place is: https://bugs.documentfoundation.org/show_bug.cgi?id=151210

Sorry,
M

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

[Libreoffice-bugs] [Bug 151210] 7-4-2-1 calc commas in decimal numbers are not converted to decimal-point, German surround

2022-12-30 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=151210

Mishy  changed:

   What|Removed |Added

 CC||mishy1...@gmail.com

--- Comment #7 from Mishy  ---
Previously I accidentally comentend to a not correct BUG (152034)
This is the right one, sorry.
My comment from the mentioned bug:

Same issue happens with all "," (comma) separator using languages, like
Hungarian, German...

It should be fixed, as it happens frequently to type numbers first in a cell,
then need to adjust it later with a simple "multiply" or "add" like: "4,5" to
"=2*4,5" or "=B1*4,5". Or using complicated functions gathered from our older
documents and we need to readjust the numbers every time when we need to modify
it and the text in a cell could be 100+ char long, with constants in some
random places with decimal separator!

Localized function names not only used for Copy-Paste but for easier handling
and finding. English function names mostly better than some pretty brain-dead
loalized function names what I would not find ever AND I do not want to learn
all of them in any other laguage what I may facing with!

If you (QA) think that it is normal to use DOT instead of COMMA in eglish
functions, think about the tousends of scientific users who SHOULD use
localized numbers BUT they dealing with lot of abbreviations and names in
almost only ENGLISH.

I guess the best would be to set a checkbox beside the "Use English Function
Names" with option like "Use dot in functions for decumal separator" which
maybe defaulted to ON but can be set by user.
And not the opposite! As under the Language Setting I have "decimal key = ,"
set, and even than, it is not handling the comma within fuctions just shows the
comma in the results.

Thanks

Other comment:
Tested system: Linux x64, 5.4.0-132-generic, Xubuntu 20.4.5
LibreOffcie: 7.4.2~rc3-0ubuntu0.20.04.1~lo1 (7.4.2.3)

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

[Libreoffice-bugs] [Bug 125093] Windows: Honor "Zone.Identifier" stream, and open files from restricted zones in read-only mode

2022-12-30 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=125093

Adolfo Jayme Barrientos  changed:

   What|Removed |Added

 Status|RESOLVED|NEW
 Resolution|WONTFIX |---

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

[Libreoffice-bugs] [Bug 152738] New: LO75RC1: Automatic spell-check on macOS not underlining misspelled words

2022-12-30 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=152738

Bug ID: 152738
   Summary: LO75RC1: Automatic spell-check on macOS not
underlining misspelled words
   Product: LibreOffice
   Version: 7.5.0.0 beta1+
  Hardware: All
OS: macOS (All)
Status: UNCONFIRMED
  Severity: normal
  Priority: medium
 Component: Linguistic
  Assignee: libreoffice-bugs@lists.freedesktop.org
  Reporter: mi...@filmsi.net
CC: so...@libreoffice.org

Description:
On macOS LO75RC1 spell-checking a document doesn't show errors/red underlines
under misspelled words. Opening the same document with LO74 shows the
underlines.

The strange thing is that when opening the Tools > Spelling window, the window
shows the first sentence as with no language set, although the whole language
has Slovenian (sl) set as text language and the status bar shows Slovenian as
the language of the current selection - this could be some error on the part of
detecting the right language?

I noticed that already in the development versions of 75 like aplha1 and
notified via e-mail the developer of the spell-checking, but got no reply.

Steps to Reproduce:
1. Open a document to test spelling.
2. 
3.

Actual Results:
Text is not underlined where words are misspelled.

Expected Results:
Should be underlined ...


Reproducible: Always


User Profile Reset: No

Additional Info:
Version: 7.5.0.1 (X86_64) / LibreOffice Community
Build ID: 77cd3d7ad4445740a0c6cf977992dafd8ebad8df
CPU threads: 8; OS: Mac OS X 11.7; UI render: default; VCL: osx
Locale: sl-SI (sl_SI.UTF-8); UI: sl-SI
Calc: threaded

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

[Libreoffice-bugs] [Bug 152034] numbers have changed from comma to dot all 2, 5 are now 2.5

2022-12-30 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=152034

--- Comment #5 from Mishy  ---
Hi!

Same issue happens with all "," (comma) separator using languages, like
Hungarian, German...

It should be fixed, as it happens frequently to type numbers first in a cell,
then need to adjust it later with a simple "multiply" or "add" like: "4,5" to
"=2*4,5" or "=B1*4,5". Or using complicated functions gathered from our older
documents and we need to readjust the numbers every time when we need to modify
it and the text in a cell could be 100+ char long, with constants in some
random places with decimal separator!

Localized function names not only used for Copy-Paste but for easier handling
and finding. English function names mostly better than some pretty brain-dead
loalized function names what I would not find ever AND I do not want to learn
all of them in any other laguage what I may facing with!

If you (QA) think that it is normal to use DOT instead of COMMA in eglish
functions, think about the tousends of scientific users who SHOULD use
localized numbers BUT they dealing with lot of abbreviations and names in
almost only ENGLISH.

I guess the best would be to set a checkbox beside the "Use English Function
Names" with option like "Use dot in functions for decumal separator" which
maybe defaulted to ON but can be set by user.
And not the opposite! As under the Language Setting I have "decimal key = ,"
set, and even than, it is not handling the comma within fuctions just shows the
comma in the results.

Thanks

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

[Libreoffice-bugs] [Bug 108734] [META] Character dialog bugs and enhancements

2022-12-30 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=108734

خالد حسني  changed:

   What|Removed |Added

 Depends on||152737


Referenced Bugs:

https://bugs.documentfoundation.org/show_bug.cgi?id=152737
[Bug 152737] Font preview in Characters dialog uses the wrong font for first
Complex character
-- 
You are receiving this mail because:
You are the assignee for the bug.

[Libreoffice-bugs] [Bug 108736] [META] Font text preview bugs and enhancements

2022-12-30 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=108736

خالد حسني  changed:

   What|Removed |Added

 Depends on||152737


Referenced Bugs:

https://bugs.documentfoundation.org/show_bug.cgi?id=152737
[Bug 152737] Font preview in Characters dialog uses the wrong font for first
Complex character
-- 
You are receiving this mail because:
You are the assignee for the bug.

[Libreoffice-bugs] [Bug 43808] [META] Right-To-Left and Complex Text Layout language issues (RTL/CTL)

2022-12-30 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=43808

خالد حسني  changed:

   What|Removed |Added

 Depends on||152737


Referenced Bugs:

https://bugs.documentfoundation.org/show_bug.cgi?id=152737
[Bug 152737] Font preview in Characters dialog uses the wrong font for first
Complex character
-- 
You are receiving this mail because:
You are the assignee for the bug.

  1   2   >