[Bug 116108] Add option to fit images into their cell

2023-12-07 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=116108

Stéphane Guillou (stragu)  changed:

   What|Removed |Added

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

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

[Bug 155285] Cell anchored callout loses position in save and reload

2023-12-07 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=155285

Stéphane Guillou (stragu)  changed:

   What|Removed |Added

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

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

[Bug 87740] [META] Anchor and text wrapping bugs and enhancements

2023-12-07 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=87740

Stéphane Guillou (stragu)  changed:

   What|Removed |Added

 Depends on||158592


Referenced Bugs:

https://bugs.documentfoundation.org/show_bug.cgi?id=158592
[Bug 158592] Control anchored and fit to cell jumps to different cell when
changing Anchor setting in Control Properties
-- 
You are receiving this mail because:
You are the assignee for the bug.

[Bug 107742] [META] Form control bugs and enhancements

2023-12-07 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=107742

Stéphane Guillou (stragu)  changed:

   What|Removed |Added

 Depends on||158592


Referenced Bugs:

https://bugs.documentfoundation.org/show_bug.cgi?id=158592
[Bug 158592] Control anchored and fit to cell jumps to different cell when
changing Anchor setting in Control Properties
-- 
You are receiving this mail because:
You are the assignee for the bug.

[Bug 158592] New: Control anchored and fit to cell jumps to different cell when changing Anchor setting in Control Properties

2023-12-07 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=158592

Bug ID: 158592
   Summary: Control anchored and fit to cell jumps to different
cell when changing Anchor setting in Control
Properties
   Product: LibreOffice
   Version: Inherited From OOo
  Hardware: x86-64 (AMD64)
OS: Linux (All)
Status: UNCONFIRMED
  Severity: normal
  Priority: medium
 Component: Calc
  Assignee: libreoffice-bugs@lists.freedesktop.org
  Reporter: stephane.guil...@libreoffice.org
CC: samuel.mehrbr...@allotropia.de
Blocks: 87740, 107742

If the anchoring of a form control that was resized to fit the cell is set "to
cell" from the Control Properties dialog, it moves to another cell toward the
top left.

Steps:
1. Open Calc (or open attachment and jump to step 6)
2. Insert > Form Control > Text box
3. Trace the control further than column C and row 2 (for example, on cell E10)
4. right-click on the control > Anchor > To cell (or "resize with cell", same
thing)
5. right-click on the control > Fit to cell size
6. right-click on the control > Control properties > Anchor > To cell
(repeatedly)

Result: the control jumps from cell to cell at each click, until it settles in
cell C2. The change can't be undone.
Same happens with other controls, e.g. a Numerical Field.

Note that the setting does not have the option "To cell (resize with cell)",
which might be related to the issue?

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

Also reproduced with sample file in Ooo 3.3, so issue is inherited (although
the option to "Fit to Cell Size" was only added in 6.1 for bug 116108).

Seems to have to do with the position of the top-right corner, possibly because
of rounding.

Samuel, I thought you might be interested?


Referenced Bugs:

https://bugs.documentfoundation.org/show_bug.cgi?id=87740
[Bug 87740] [META] Anchor and text wrapping bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=107742
[Bug 107742] [META] Form control bugs and enhancements
-- 
You are receiving this mail because:
You are the assignee for the bug.

[Bug 158588] ODT bloats in file size by factor 4 by saving without changes, font embedding options based on two checkboxes should be redesigned

2023-12-07 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=158588

OfficeUser  changed:

   What|Removed |Added

 CC||libreoffice-ux-advise@lists
   ||.freedesktop.org
   Keywords||needsUXEval

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

[Bug 158588] ODT bloats in file size by factor 4 by saving without changes, font embedding options based on two checkboxes should be redesigned

2023-12-07 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=158588

OfficeUser  changed:

   What|Removed |Added

 CC||libreoffice-ux-advise@lists
   ||.freedesktop.org
   Keywords||needsUXEval

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

core.git: sc/source sc/uiconfig

2023-12-07 Thread Balazs Varga (via logerrit)
 sc/source/ui/inc/tpview.hxx|   22 ++
 sc/source/ui/optdlg/tpview.cxx |  112 ++
 sc/uiconfig/scalc/ui/tpviewpage.ui |  387 -
 3 files changed, 476 insertions(+), 45 deletions(-)

New commits:
commit cb099da3923ae2e6cca70a73049f79e55f808d47
Author: Balazs Varga 
AuthorDate: Thu Dec 7 15:35:25 2023 +0100
Commit: Balazs Varga 
CommitDate: Fri Dec 8 08:27:03 2023 +0100

tdf#158466 - UI: Part 49 - Unify lockdown behavior of Options dialog

for Calc - View Page.

Change-Id: I75fcb41b82c4946812d27dd364ffef8eb3086c0b
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/160439
Tested-by: Jenkins
Reviewed-by: Balazs Varga 

diff --git a/sc/source/ui/inc/tpview.hxx b/sc/source/ui/inc/tpview.hxx
index 6854f77c5eb0..97addc9f530d 100644
--- a/sc/source/ui/inc/tpview.hxx
+++ b/sc/source/ui/inc/tpview.hxx
@@ -29,32 +29,54 @@ class ScTpContentOptions : public SfxTabPage
 std::unique_ptr m_xLocalOptions;
 
 std::unique_ptr m_xGridLB;
+std::unique_ptr m_xGridImg;
 std::unique_ptr m_xBreakCB;
+std::unique_ptr m_xBreakImg;
 std::unique_ptr m_xGuideLineCB;
+std::unique_ptr m_xGuideLineImg;
 
 std::unique_ptr m_xFormulaCB;
+std::unique_ptr m_xFormulaImg;
 std::unique_ptr m_xNilCB;
+std::unique_ptr m_xNilImg;
 std::unique_ptr m_xAnnotCB;
+std::unique_ptr m_xAnnotImg;
 std::unique_ptr m_xFormulaMarkCB;
+std::unique_ptr m_xFormulaMarkImg;
 std::unique_ptr m_xValueCB;
+std::unique_ptr m_xValueImg;
 std::unique_ptr m_xColRowHighCB;
+std::unique_ptr m_xColRowHighImg;
 std::unique_ptr m_xAnchorCB;
+std::unique_ptr m_xAnchorImg;
 std::unique_ptr m_xRangeFindCB;
+std::unique_ptr m_xRangeFindImg;
 
 std::unique_ptr m_xObjGrfLB;
+std::unique_ptr m_xObjGrfImg;
 std::unique_ptr m_xDiagramLB;
+std::unique_ptr m_xDiagramImg;
 std::unique_ptr m_xDrawLB;
+std::unique_ptr m_xDrawImg;
 
 std::unique_ptr m_xSyncZoomCB;
+std::unique_ptr m_xSyncZoomImg;
 
 std::unique_ptr m_xRowColHeaderCB;
+std::unique_ptr m_xRowColHeaderImg;
 std::unique_ptr m_xHScrollCB;
+std::unique_ptr m_xHScrollImg;
 std::unique_ptr m_xVScrollCB;
+std::unique_ptr m_xVScrollImg;
 std::unique_ptr m_xTblRegCB;
+std::unique_ptr m_xTblRegImg;
 std::unique_ptr m_xOutlineCB;
+std::unique_ptr m_xOutlineImg;
 std::unique_ptr m_xSummaryCB;
+std::unique_ptr m_xSummaryImg;
 std::unique_ptr m_xThemedCursorRB;
 std::unique_ptr m_xSystemCursorRB;
+std::unique_ptr m_xCursorImg;
 
 voidInitGridOpt();
 DECL_LINK( GridHdl, weld::ComboBox&, void );
diff --git a/sc/source/ui/optdlg/tpview.cxx b/sc/source/ui/optdlg/tpview.cxx
index 213d4e73eb7b..73f305dd7ff7 100644
--- a/sc/source/ui/optdlg/tpview.cxx
+++ b/sc/source/ui/optdlg/tpview.cxx
@@ -38,28 +38,50 @@
 ScTpContentOptions::ScTpContentOptions(weld::Container* pPage, 
weld::DialogController* pController, const SfxItemSet&  rArgSet)
 : SfxTabPage(pPage, pController, "modules/scalc/ui/tpviewpage.ui", 
"TpViewPage", )
 , m_xGridLB(m_xBuilder->weld_combo_box("grid"))
+, m_xGridImg(m_xBuilder->weld_widget("lockgrid"))
 , m_xBreakCB(m_xBuilder->weld_check_button("break"))
+, m_xBreakImg(m_xBuilder->weld_widget("lockbreak"))
 , m_xGuideLineCB(m_xBuilder->weld_check_button("guideline"))
+, m_xGuideLineImg(m_xBuilder->weld_widget("lockguideline"))
 , m_xFormulaCB(m_xBuilder->weld_check_button("formula"))
+, m_xFormulaImg(m_xBuilder->weld_widget("lockformula"))
 , m_xNilCB(m_xBuilder->weld_check_button("nil"))
+, m_xNilImg(m_xBuilder->weld_widget("locknil"))
 , m_xAnnotCB(m_xBuilder->weld_check_button("annot"))
+, m_xAnnotImg(m_xBuilder->weld_widget("lockannot"))
 , m_xFormulaMarkCB(m_xBuilder->weld_check_button("formulamark"))
+, m_xFormulaMarkImg(m_xBuilder->weld_widget("lockformulamark"))
 , m_xValueCB(m_xBuilder->weld_check_button("value"))
+, m_xValueImg(m_xBuilder->weld_widget("lockvalue"))
 , m_xColRowHighCB(m_xBuilder->weld_check_button("colrowhigh"))
+, m_xColRowHighImg(m_xBuilder->weld_widget("lockcolrowhigh"))
 , m_xAnchorCB(m_xBuilder->weld_check_button("anchor"))
+, m_xAnchorImg(m_xBuilder->weld_widget("lockanchor"))
 , m_xRangeFindCB(m_xBuilder->weld_check_button("rangefind"))
+, m_xRangeFindImg(m_xBuilder->weld_widget("lockrangefind"))
 , m_xObjGrfLB(m_xBuilder->weld_combo_box("objgrf"))
+, m_xObjGrfImg(m_xBuilder->weld_widget("lockobjgrf"))
 , m_xDiagramLB(m_xBuilder->weld_combo_box("diagram"))
+, m_xDiagramImg(m_xBuilder->weld_widget("lockdiagram"))
 , m_xDrawLB(m_xBuilder->weld_combo_box("draw"))
+, m_xDrawImg(m_xBuilder->weld_widget("lockdraw"))
 , m_xSyncZoomCB(m_xBuilder->weld_check_button("synczoom"))
+, m_xSyncZoomImg(m_xBuilder->weld_widget("locksynczoom"))
 , 

[Bug 112059] Events fired by subform changed, when form is write-protected

2023-12-07 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=112059

--- Comment #14 from Robert Großkopf  ---
Behavior still exists in
Version: 24.2.0.0.alpha1 (X86_64) / LibreOffice Community
Build ID: 06946980c858649160c634007e5fac9a5aa81f38
CPU threads: 6; OS: Linux 5.14; UI render: default; VCL: kf5 (cairo+xcb)
Locale: de-DE (de_DE.UTF-8); UI: de-DE
Calc: threaded

Don't know why "AfterRecordChange should appear when there isn't any record,
which could be shown and could be changed.

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

[Bug 158587] Improve column/row highlighting in Calc

2023-12-07 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=158587

Buovjaga  changed:

   What|Removed |Added

 CC||ilmari.lauhakangas@libreoff
   ||ice.org

--- Comment #5 from Buovjaga  ---
So should the extra highlighting be deactivated in case multiple cells are
selected?

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

[Bug 158587] Improve column/row highlighting in Calc

2023-12-07 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=158587

Buovjaga  changed:

   What|Removed |Added

 CC||ilmari.lauhakangas@libreoff
   ||ice.org

--- Comment #5 from Buovjaga  ---
So should the extra highlighting be deactivated in case multiple cells are
selected?

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

core.git: external/libnumbertext

2023-12-07 Thread Stephan Bergmann (via logerrit)
 external/libnumbertext/deprecated.patch.0 |8 +---
 1 file changed, 1 insertion(+), 7 deletions(-)

New commits:
commit ad6ba4a3a63a25c5b9043bb5d0b178411b3eb714
Author: Stephan Bergmann 
AuthorDate: Thu Dec 7 17:40:23 2023 +0100
Commit: Stephan Bergmann 
CommitDate: Fri Dec 8 07:31:54 2023 +0100

external/libnumbertext: Silence -Werror,-Wdeprecated-declarations

...when building against LLVM 18 trunk libc++,

> In file included from Numbertext.cxx:6:
> ~/llvm/inst/bin/../include/c++/v1/locale:3772:1: error: 
'wstring_convert>' is deprecated 
[-Werror,-Wdeprecated-declarations]
>  3772 | wstring_convert<_Codecvt, _Elem, _WideAlloc, _ByteAlloc>::
>   | ^
> ~/llvm/inst/bin/../include/c++/v1/locale:3649:17: note: in instantiation 
of member function 'std::wstring_convert>::to_bytes' 
requested here
>  3649 | {return to_bytes(__wstr.data(), __wstr.data() + 
__wstr.size());}
>   | ^
> Numbertext.cxx:164:22: note: in instantiation of member function 
'std::wstring_convert>::to_bytes' requested here
>   164 | return converter.to_bytes( s );
>   |  ^
> ~/llvm/inst/bin/../include/c++/v1/locale:3591:28: note: 
'wstring_convert>' has been explicitly marked 
deprecated here
>  3591 | class _LIBCPP_TEMPLATE_VIS _LIBCPP_DEPRECATED_IN_CXX17 
wstring_convert
>   |^
> ~/llvm/inst/bin/../include/c++/v1/__config:942:41: note: expanded from 
macro '_LIBCPP_DEPRECATED_IN_CXX17'
>   942 | #define _LIBCPP_DEPRECATED_IN_CXX17 _LIBCPP_DEPRECATED
>   | ^
> ~/llvm/inst/bin/../include/c++/v1/__config:915:49: note: expanded from 
macro '_LIBCPP_DEPRECATED'
>   915 | #  define _LIBCPP_DEPRECATED __attribute__((__deprecated__))
>   | ^

(The warning is apparently only emitted late during compilation when
instantiating template code, so extending the existing `#pragma GCC 
diagnostic
push/pop` area did not work, and the `#pragma GCC diagnostic ignored` 
rather had
to be enabled all through to the end of the TU.)

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

diff --git a/external/libnumbertext/deprecated.patch.0 
b/external/libnumbertext/deprecated.patch.0
index 1fe5c214f602..8ee86ac135c5 100644
--- a/external/libnumbertext/deprecated.patch.0
+++ b/external/libnumbertext/deprecated.patch.0
@@ -31,19 +31,13 @@
  return converter.from_bytes( s );
  #else
  return ::locale::conv::utf_to_utf(s.c_str(), s.c_str() + 
s.size());
-@@ -138,8 +152,15 @@
+@@ -138,6 +152,9 @@
  WideCharToMultiByte(CP_UTF8, 0, s.c_str(), -1, str.get(), nSize, nullptr, 
nullptr);
  return str.get();
  #elif !defined NUMBERTEXT_BOOST
 +#if defined __GNUC__
-+#pragma GCC diagnostic push
 +#pragma GCC diagnostic ignored "-Wdeprecated-declarations"
 +#endif
  typedef std::codecvt_utf8 convert_type;
  std::wstring_convert converter;
-+#if defined __GNUC__
-+#pragma GCC diagnostic pop
-+#endif
  return converter.to_bytes( s );
- #else
- return ::locale::conv::utf_to_utf(s.c_str(), s.c_str() + s.size());


core.git: Branch 'distro/collabora/co-23.05' - sc/source

2023-12-07 Thread Caolán McNamara (via logerrit)
 sc/source/filter/xml/xmlexprt.cxx |8 +++-
 1 file changed, 7 insertions(+), 1 deletion(-)

New commits:
commit eec05aa9cf4a283efa3be76ecf18aa77f714d26e
Author: Caolán McNamara 
AuthorDate: Thu Dec 7 12:30:37 2023 +
Commit: Tomaž Vajngerl 
CommitDate: Fri Dec 8 07:20:38 2023 +0100

busy loop seen on ods export attempt

ScXMLExport::ExportFormatRanges cannot advance because nMaxCols is 0
so busy loop and no progression

In ScRowFormatRanges::GetMaxRows, aRowFormatRanges is empty which is why
nMaxCols is 0

In ScFormatRangeStyles::GetFormatRanges aTables appears to be 30 empty
items.

But why it is empty can't be seen from the bt.

Force this to be an assert to ensure crashtesting can flush out this
case, rather than letting it get killed off as a timeout.

Set this case as an error and break so failure results in an error
message of failure to save instead of a hang.

Change-Id: I827e1e638cddd976a48340f86741c21075afe856
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/160428
Tested-by: Jenkins CollaboraOffice 
Reviewed-by: Tomaž Vajngerl 

diff --git a/sc/source/filter/xml/xmlexprt.cxx 
b/sc/source/filter/xml/xmlexprt.cxx
index 4a9b9db6662a..6b5a0592a195 100644
--- a/sc/source/filter/xml/xmlexprt.cxx
+++ b/sc/source/filter/xml/xmlexprt.cxx
@@ -1565,7 +1565,13 @@ void ScXMLExport::ExportFormatRanges(const sal_Int32 
nStartCol, const sal_Int32
 pRowFormatRanges->Clear();
 pCellStyles->GetFormatRanges(0, 
pSharedData->GetLastColumn(nSheet), nStartRow + nRows, nSheet, 
pRowFormatRanges.get());
 sal_Int32 nMaxRows = pRowFormatRanges->GetMaxRows();
-OSL_ENSURE(nMaxRows, "something went wrong");
+assert(nMaxRows && "ScXMLExport::ExportFormatRanges cannot 
make progress with zero rows, something went wrong");
+if (!nMaxRows)
+{
+uno::Sequence aEmptySeq;
+SetError(XMLERROR_CANCEL|XMLERROR_FLAG_SEVERE, aEmptySeq);
+break;
+}
 if (nMaxRows >= nTotalRows - nRows)
 {
 OpenRow(nSheet, nStartRow + nRows, nTotalRows - nRows, 
aRowAttr);


[Bug 133092] [META] Crash bugs

2023-12-07 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=133092

BogdanB  changed:

   What|Removed |Added

 Depends on||158505


Referenced Bugs:

https://bugs.documentfoundation.org/show_bug.cgi?id=158505
[Bug 158505] Crash exporting .docx file to Pdf
-- 
You are receiving this mail because:
You are the assignee for the bug.

[Bug 101258] [META] Bibliography bugs and enhancements

2023-12-07 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=101258

BogdanB  changed:

   What|Removed |Added

 Depends on||158505


Referenced Bugs:

https://bugs.documentfoundation.org/show_bug.cgi?id=158505
[Bug 158505] Crash exporting .docx file to Pdf
-- 
You are receiving this mail because:
You are the assignee for the bug.

[Bug 158505] Crash exporting .docx file to Pdf

2023-12-07 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=158505

BogdanB  changed:

   What|Removed |Added

 Blocks||101258, 133092
 CC||buzea.bog...@libreoffice.or
   ||g


Referenced Bugs:

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

[Bug 108252] [META] Cell-related bugs and enhancements (including formatting)

2023-12-07 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=108252

BogdanB  changed:

   What|Removed |Added

 Depends on||158555


Referenced Bugs:

https://bugs.documentfoundation.org/show_bug.cgi?id=158555
[Bug 158555] [NatNum12] does not allow literal text to the left of 0
-- 
You are receiving this mail because:
You are the assignee for the bug.

[Bug 158555] [NatNum12] does not allow literal text to the left of 0

2023-12-07 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=158555

BogdanB  changed:

   What|Removed |Added

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


Referenced Bugs:

https://bugs.documentfoundation.org/show_bug.cgi?id=108252
[Bug 108252] [META] Cell-related bugs and enhancements (including formatting)
-- 
You are receiving this mail because:
You are the assignee for the bug.

[Bug 103304] [META] Page style dialog bugs and enhancements

2023-12-07 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=103304

BogdanB  changed:

   What|Removed |Added

 Depends on||158572


Referenced Bugs:

https://bugs.documentfoundation.org/show_bug.cgi?id=158572
[Bug 158572] Translation problem in Calc - Portuguese PT
-- 
You are receiving this mail because:
You are the assignee for the bug.

[Bug 158572] Translation problem in Calc - Portuguese PT

2023-12-07 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=158572

BogdanB  changed:

   What|Removed |Added

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


Referenced Bugs:

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

[Bug 158584] Problem "Save As" from LibreOffice Writer to fileformat: "Word 2003 XML (.xml)" - width of table(s) decreases to 2%

2023-12-07 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=158584

BogdanB  changed:

   What|Removed |Added

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


Referenced Bugs:

https://bugs.documentfoundation.org/show_bug.cgi?id=108254
[Bug 108254] [META] File format filters (import/export) bugs and enhancements
-- 
You are receiving this mail because:
You are the assignee for the bug.

[Bug 108254] [META] File format filters (import/export) bugs and enhancements

2023-12-07 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=108254

BogdanB  changed:

   What|Removed |Added

 Depends on||158584


Referenced Bugs:

https://bugs.documentfoundation.org/show_bug.cgi?id=158584
[Bug 158584] Problem "Save As" from LibreOffice Writer to fileformat: "Word
2003 XML (.xml)" - width of table(s) decreases to 2%
-- 
You are receiving this mail because:
You are the assignee for the bug.

[Bug 158591] New: gdb prints "No symbol 'xxx' in current context" when debuging on riscv64

2023-12-07 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=158591

Bug ID: 158591
   Summary: gdb prints "No symbol 'xxx' in current context" when
debuging on riscv64
   Product: LibreOffice
   Version: unspecified
  Hardware: Other
OS: Linux (All)
Status: UNCONFIRMED
  Severity: normal
  Priority: medium
 Component: LibreOffice
  Assignee: libreoffice-bugs@lists.freedesktop.org
  Reporter: sakura...@outlook.com

Description:
I am working with the latest commit of the source code on an riscv64 machine.
But gdb behaves not correctly.

When I print a variable, such as xxx, gdb prints "No symbol 'xxx' in current
context". I can't print the value of any variable. But other functions of gdbs
are working fine, such as setting breakpoint and print stack.

What should I do to fix this?

Steps to Reproduce:
On a riscv64 machine, build libreoffice with "--enable-debug". Then debug any
.cxx file and print any variable.

Actual Results:
gdb prints "No symbol 'xxx' in current context"

Expected Results:
The value of the variable printed.


Reproducible: Always


User Profile Reset: No

Additional Info:
gdb version 13.2
gcc version 13.2

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

[Bug 116979] [META] Regression introduced by Aw080

2023-12-07 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=116979
Bug 116979 depends on bug 122735, which changed state.

Bug 122735 Summary: Entering a group does not make the other objects paler / 
dimmed anymore
https://bugs.documentfoundation.org/show_bug.cgi?id=122735

   What|Removed |Added

 Status|REOPENED|RESOLVED
 Resolution|--- |FIXED

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

[Bug 108640] [META] Object meta bugs and enhancements

2023-12-07 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=108640
Bug 108640 depends on bug 122735, which changed state.

Bug 122735 Summary: Entering a group does not make the other objects paler / 
dimmed anymore
https://bugs.documentfoundation.org/show_bug.cgi?id=122735

   What|Removed |Added

 Status|REOPENED|RESOLVED
 Resolution|--- |FIXED

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

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

2023-12-07 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=158590

Mike Kaganski  changed:

   What|Removed |Added

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

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

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

2023-12-07 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=158590

--- Comment #1 from Mike Kaganski  ---
(In reply to juani...@gmail.com from comment #0)
> This means that if I want to change the scale used for the current document,
> I must change the scale on the "options" dialog

https://wiki.documentfoundation.org/ReleaseNotes/7.2#User_Interface

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

[Bug 158577] Allow locking down adding new trusted authors

2023-12-07 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=158577

QA Administrators  changed:

   What|Removed |Added

   Keywords||bibisectRequest

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

[Bug 158340] Page Style Header and Footer tabs: Add setting for choosing Header Right/Left Footer Right/Left

2023-12-07 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=158340

QA Administrators  changed:

   What|Removed |Added

 Whiteboard|| QA:needsComment

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

[Bug 158332] Areas from the context menu remain after exiting the presentation (VCL gtk3, DE kde and Xfce)

2023-12-07 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=158332

QA Administrators  changed:

   What|Removed |Added

 Whiteboard|| QA:needsComment

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

[Bug 158334] EDITING selecting and deselecting a connector is slow

2023-12-07 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=158334

QA Administrators  changed:

   What|Removed |Added

 Whiteboard|| QA:needsComment

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

[Bug 158523] Whole pages of Comments are not PRINTING or exported to PDF in margins

2023-12-07 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=158523

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

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

[Bug 98259] [META] Keyboard shortcuts and accelerators bugs and enhancements

2023-12-07 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=98259
Bug 98259 depends on bug 106196, which changed state.

Bug 106196 Summary: EDITING Impress doesn't recognize shortcuts for bulleted 
lists
https://bugs.documentfoundation.org/show_bug.cgi?id=106196

   What|Removed |Added

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

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

[Bug 158523] Whole pages of Comments are not PRINTING or exported to PDF in margins

2023-12-07 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=158523

QA Administrators  changed:

   What|Removed |Added

 Status|NEEDINFO|UNCONFIRMED
 Ever confirmed|1   |0

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

[Bug 155237] Items on drawing moved between different sessions, and now unable to correct or delete them

2023-12-07 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=155237

--- Comment #3 from QA Administrators  ---
Dear Gordon Patnude,

Please read this message in its entirety before proceeding.

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

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

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

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

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

e) Read all comments and provide any requested information

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

a) respond via email 

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

Warm Regards,
QA Team

MassPing-NeedInfo-FollowUp

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

[Bug 106196] EDITING Impress doesn't recognize shortcuts for bulleted lists

2023-12-07 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=106196

QA Administrators  changed:

   What|Removed |Added

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

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

[Bug 104485] Alphabetizing text selection function in Writer

2023-12-07 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=104485

--- Comment #6 from QA Administrators  ---
Dear Dr. Pam Halton,

Please read this message in its entirety before proceeding.

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

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

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

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

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

e) Read all comments and provide any requested information

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

a) respond via email 

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

Warm Regards,
QA Team

MassPing-NeedInfo-FollowUp

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

[Bug 106196] EDITING Impress doesn't recognize shortcuts for bulleted lists

2023-12-07 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=106196

--- Comment #7 from QA Administrators  ---
Dear doriano.mag,

Please read this message in its entirety before proceeding.

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

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

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

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

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

e) Read all comments and provide any requested information

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

a) respond via email 

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

Warm Regards,
QA Team

MassPing-NeedInfo-FollowUp

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

[Bug 104485] Alphabetizing text selection function in Writer

2023-12-07 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=104485

QA Administrators  changed:

   What|Removed |Added

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

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

[Bug 155734] It takes too long time to open an '.odt' document

2023-12-07 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=155734

--- Comment #2 from QA Administrators  ---
Dear Ole Jansen,

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.

[Bug 94512] SIDEBAR collapses when previewing a document

2023-12-07 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=94512

--- Comment #11 from QA Administrators  ---
Dear Jean-Francois Nifenecker,

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

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

If you have time, please do the following:

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

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

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

Please DO NOT

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


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

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


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

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

Warm Regards,
QA Team

MassPing-UntouchedBug

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

[Bug 92762] WRITER paragraph with list style is different from paragraph style + separate list style

2023-12-07 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=92762

--- Comment #9 from QA Administrators  ---
Dear Philippe Jung,

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

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

If you have time, please do the following:

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

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

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

Please DO NOT

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


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

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


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

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

Warm Regards,
QA Team

MassPing-UntouchedBug

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

[Bug 82170] FILEOPEN: MSO ODT - Incorrect indent for bullets and numbering

2023-12-07 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=82170

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

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

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

If you have time, please do the following:

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

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

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

Please DO NOT

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


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

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


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

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

Warm Regards,
QA Team

MassPing-UntouchedBug

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

[Bug 76736] ODF import: default-cell-style-name attribute is ignored everywhere when last of table row has no such attribute.

2023-12-07 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=76736

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

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

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

If you have time, please do the following:

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

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

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

Please DO NOT

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


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

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


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

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

Warm Regards,
QA Team

MassPing-UntouchedBug

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

[Bug 72442] UI: When I try to add a hyperlink to a bookmark in the same document, the list with bookmarks closes itself

2023-12-07 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=72442

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

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

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

If you have time, please do the following:

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

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

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

Please DO NOT

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


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

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


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

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

Warm Regards,
QA Team

MassPing-UntouchedBug

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

[Bug 37903] EDITING: Moving object using ALT - cursor keys also moves the object behind it

2023-12-07 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=37903

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

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

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

If you have time, please do the following:

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

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

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

Please DO NOT

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


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

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


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

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

Warm Regards,
QA Team

MassPing-UntouchedBug

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

[Bug 58270] Spaces between 'Category and Numbering' cross-references should be a non-breaking space

2023-12-07 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=58270

--- Comment #14 from QA Administrators  ---
Dear Olivier Diotte,

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

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

If you have time, please do the following:

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

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

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

Please DO NOT

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


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

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


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

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

Warm Regards,
QA Team

MassPing-UntouchedBug

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

[Bug 33154] Interaction (Execute) is generally buggy

2023-12-07 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=33154

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

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

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

If you have time, please do the following:

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

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

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

Please DO NOT

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


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

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


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

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

Warm Regards,
QA Team

MassPing-UntouchedBug

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

[Bug 139472] Adding internal hyperlinks to unnamed slides causes links to break when switching UI languages due to link anchors pointing to the localised names

2023-12-07 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=139472

--- Comment #6 from QA Administrators  ---
Dear Gael Langlais,

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

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

If you have time, please do the following:

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

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

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

Please DO NOT

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


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

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


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

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

Warm Regards,
QA Team

MassPing-UntouchedBug

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

[Bug 120310] Ambiguous error message returned when attempting to use certain special characters in field names

2023-12-07 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=120310

--- Comment #16 from QA Administrators  ---
Dear elflng.libreoffice,

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

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

If you have time, please do the following:

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

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

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

Please DO NOT

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


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

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


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

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

Warm Regards,
QA Team

MassPing-UntouchedBug

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

[Bug 119431] External database jdbc hsqldb, Crash in the case of SELECT, SQL query, access to the database

2023-12-07 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=119431

--- Comment #28 from QA Administrators  ---
Dear Krzysztof,

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

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

If you have time, please do the following:

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

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

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

Please DO NOT

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


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

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


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

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

Warm Regards,
QA Team

MassPing-UntouchedBug

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

[Bug 112059] Events fired by subform changed, when form is write-protected

2023-12-07 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=112059

--- Comment #13 from QA Administrators  ---
Dear Robert Großkopf,

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

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

If you have time, please do the following:

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

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

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

Please DO NOT

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


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

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


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

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

Warm Regards,
QA Team

MassPing-UntouchedBug

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

[Bug 114041] There is some lag around images when reducing a selection by scrolling upwards

2023-12-07 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=114041

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

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

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

If you have time, please do the following:

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

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

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

Please DO NOT

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


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

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


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

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

Warm Regards,
QA Team

MassPing-UntouchedBug

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

[Bug 107839] BeforeUpdating and AfterUpdating events are not firing when records are edited in a Table Control

2023-12-07 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=107839

--- Comment #14 from QA Administrators  ---
Dear Howard Johnson,

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

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

If you have time, please do the following:

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

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

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

Please DO NOT

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


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

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


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

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

Warm Regards,
QA Team

MassPing-UntouchedBug

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

[Bug 109326] [META] Data filter bugs and enhancements

2023-12-07 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=109326

Aron Budea  changed:

   What|Removed |Added

 Depends on||158440


Referenced Bugs:

https://bugs.documentfoundation.org/show_bug.cgi?id=158440
[Bug 158440] Filter for background should take colors in empty cells
-- 
You are receiving this mail because:
You are the assignee for the bug.

[Bug 158440] Filter for background should take colors in empty cells

2023-12-07 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=158440

Aron Budea  changed:

   What|Removed |Added

 Blocks||109326


Referenced Bugs:

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

[Bug 126084] DOCX/OOXML support of SVG images via Office Drawing extension and fallback (published schema)

2023-12-07 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=126084

--- Comment #11 from Commit Notification 
 ---
Tomaž Vajngerl committed a patch related to this issue.
It has been pushed to "master":

https://git.libreoffice.org/core/commit/a010567c2cdb8ea0fe059b0b64fd5d1f2fd99a03

tdf#126084 document OOXML SVG tests and import

It will be available in 24.2.0.

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

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

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

core.git: oox/source sd/qa sw/qa

2023-12-07 Thread Tomaž Vajngerl (via logerrit)
 oox/source/drawingml/misccontexts.cxx  |6 +-
 sd/qa/unit/export-tests.cxx|   15 +--
 sw/qa/extras/globalfilter/globalfilter.cxx |   17 +
 3 files changed, 31 insertions(+), 7 deletions(-)

New commits:
commit a010567c2cdb8ea0fe059b0b64fd5d1f2fd99a03
Author: Tomaž Vajngerl 
AuthorDate: Wed Dec 6 16:55:01 2023 +0900
Commit: Tomaž Vajngerl 
CommitDate: Fri Dec 8 03:55:42 2023 +0100

tdf#126084 document OOXML SVG tests and import

Change-Id: Ief29d04f2f0693a4cdfa44c7c100ac6164da38f0
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/160378
Tested-by: Jenkins
Reviewed-by: Tomaž Vajngerl 

diff --git a/oox/source/drawingml/misccontexts.cxx 
b/oox/source/drawingml/misccontexts.cxx
index 244d17d9fc62..93d2c8ee411b 100644
--- a/oox/source/drawingml/misccontexts.cxx
+++ b/oox/source/drawingml/misccontexts.cxx
@@ -619,20 +619,24 @@ ContextHandlerRef 
BlipExtensionContext::onCreateContext(sal_Int32 nElement, cons
 case OOX_TOKEN(a14, imgProps):
 return new ArtisticEffectContext(*this, mrBlipProps.maEffect);
 
+// Import the SVG Blip
 case OOX_TOKEN(asvg, svgBlip):
 {
 if (rAttribs.hasAttribute(R_TOKEN(embed)))
 {
-// internal picture URL
 OUString aFragmentPath = 
getFragmentPathFromRelId(rAttribs.getStringDefaulted(R_TOKEN(embed)));
 if (!aFragmentPath.isEmpty())
 {
+// Read the graphic from the fragment path
 auto xGraphic = 
getFilter().getGraphicHelper().importEmbeddedGraphic(aFragmentPath);
+
+// Overwrite the fill graphic with the one contining SVG
 mrBlipProps.mxFillGraphic = xGraphic;
 if (mpBlipFill)
 mpBlipFill->mxGraphic = xGraphic;
 }
 }
+// TODO - link
 }
 break;
 }
diff --git a/sd/qa/unit/export-tests.cxx b/sd/qa/unit/export-tests.cxx
index 92b36ecacce7..428b09e983a1 100644
--- a/sd/qa/unit/export-tests.cxx
+++ b/sd/qa/unit/export-tests.cxx
@@ -1933,10 +1933,12 @@ CPPUNIT_TEST_FIXTURE(SdExportTest, testSvgImageSupport)
 {
 // Load the original file
 createSdImpressDoc("odp/SvgImageTest.odp");
-const OString sFailedMessage = "Failed on filter: " + rFormat.toUtf8();
+// Save into the target format
 saveAndReload(rFormat);
 
-// Check whether graphic was exported well
+const OString sFailedMessage = "Failed on filter: " + rFormat.toUtf8();
+
+// Check whether SVG graphic was exported as expected
 uno::Reference 
xDrawPagesSupplier(mxComponent,

uno::UNO_QUERY_THROW);
 CPPUNIT_ASSERT_EQUAL_MESSAGE(sFailedMessage.getStr(), sal_Int32(1),
@@ -1944,15 +1946,24 @@ CPPUNIT_TEST_FIXTURE(SdExportTest, testSvgImageSupport)
 uno::Reference xDrawPage(
 xDrawPagesSupplier->getDrawPages()->getByIndex(0), uno::UNO_QUERY);
 CPPUNIT_ASSERT_MESSAGE(sFailedMessage.getStr(), xDrawPage.is());
+
+// Get the image
 uno::Reference xImage(xDrawPage->getByIndex(0), 
uno::UNO_QUERY);
 uno::Reference xPropertySet(xImage, 
uno::UNO_QUERY_THROW);
 
+// Convert to a XGraphic
 uno::Reference xGraphic;
 xPropertySet->getPropertyValue("Graphic") >>= xGraphic;
 CPPUNIT_ASSERT_MESSAGE(sFailedMessage.getStr(), xGraphic.is());
+
+// Access the Graphic
 Graphic aGraphic(xGraphic);
+
+// Check if it contian a VectorGraphicData struct
 auto pVectorGraphic = aGraphic.getVectorGraphicData();
 CPPUNIT_ASSERT_MESSAGE(sFailedMessage.getStr(), pVectorGraphic);
+
+// Which should be of type SVG, which means we have a SVG file
 CPPUNIT_ASSERT_EQUAL_MESSAGE(sFailedMessage.getStr(), 
VectorGraphicDataType::Svg,
  pVectorGraphic->getType());
 }
diff --git a/sw/qa/extras/globalfilter/globalfilter.cxx 
b/sw/qa/extras/globalfilter/globalfilter.cxx
index 3eda6b6354e8..9d7c28b83ff8 100644
--- a/sw/qa/extras/globalfilter/globalfilter.cxx
+++ b/sw/qa/extras/globalfilter/globalfilter.cxx
@@ -2225,28 +2225,37 @@ void Test::testSvgImageSupport()
 
 for (OUString const & rFilterName : aFilterNames)
 {
-// Check whether the export code swaps in the image which was swapped 
out before by auto mechanism
+// Use case to import a document containing a SVG image, export in 
target format, import and check if the
+// SVG image is present and as expected in the document
 
+// Import ODT file
 createSwDoc("SvgImageTest.odt");
 
-// Export the document and import again for a check
+// Export the document in target format and import again
 saveAndReload(rFilterName);
 
-

[Bug 158249] Document with one landscape page doesn't switch back to portrait when PRINTING.

2023-12-07 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=158249

Kira Tubo  changed:

   What|Removed |Added

Version|7.6.2.1 release |4.4.7.2 release
 CC||kira.t...@gmail.com

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

[Bug 143148] Use pragma once instead of include guards (Episode 2: Endgame)

2023-12-07 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=143148

--- Comment #113 from Commit Notification 
 ---
Kira Tubo committed a patch related to this issue.
It has been pushed to "master":

https://git.libreoffice.org/core/commit/7081b28dd6ed1ab8b8d6528d94e44e5dc3b3121d

tdf#143148 Use pragma once instead of include guards

It will be available in 24.2.0.

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

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

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

core.git: vcl/inc

2023-12-07 Thread Kira Tubo (via logerrit)
 vcl/inc/bitmap/BitmapColorizeFilter.hxx |6 +-
 1 file changed, 1 insertion(+), 5 deletions(-)

New commits:
commit 7081b28dd6ed1ab8b8d6528d94e44e5dc3b3121d
Author: Kira Tubo 
AuthorDate: Tue Dec 5 23:56:13 2023 -0800
Commit: Taichi Haradaguchi <20001...@ymail.ne.jp>
CommitDate: Fri Dec 8 03:32:20 2023 +0100

tdf#143148 Use pragma once instead of include guards

Replace include guards with #pragma once

Change-Id: Id7378d6cf43817a8501a314dd8614467fb10e33a
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/160417
Tested-by: Jenkins
Reviewed-by: Taichi Haradaguchi <20001...@ymail.ne.jp>

diff --git a/vcl/inc/bitmap/BitmapColorizeFilter.hxx 
b/vcl/inc/bitmap/BitmapColorizeFilter.hxx
index e05edf2191fb..ae511b322d0c 100644
--- a/vcl/inc/bitmap/BitmapColorizeFilter.hxx
+++ b/vcl/inc/bitmap/BitmapColorizeFilter.hxx
@@ -8,11 +8,9 @@
  *
  */
 
-#ifndef INCLUDED_VCL_INC_BITMAP_BITMAPCOLORIZEFILTER_HXX
-#define INCLUDED_VCL_INC_BITMAP_BITMAPCOLORIZEFILTER_HXX
+#pragma once
 
 #include 
-
 #include 
 
 class BitmapColorizeFilter final : public BitmapFilter
@@ -29,6 +27,4 @@ private:
 Color maColor;
 };
 
-#endif
-
 /* vim:set shiftwidth=4 softtabstop=4 expandtab: */


core.git: sc/source

2023-12-07 Thread Andrea Gelmini (via logerrit)
 sc/source/ui/optdlg/tpview.cxx |1 -
 1 file changed, 1 deletion(-)

New commits:
commit 31e6767d433eaec7dd4d72b5568015a8df3feec5
Author: Andrea Gelmini 
AuthorDate: Thu Dec 7 18:43:29 2023 +0100
Commit: Taichi Haradaguchi <20001...@ymail.ne.jp>
CommitDate: Fri Dec 8 03:31:32 2023 +0100

Remove duplicated include

Change-Id: I9c0f1e9188c731077f57b6adaf8208bc8c84d829
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/160438
Tested-by: Jenkins
Reviewed-by: Taichi Haradaguchi <20001...@ymail.ne.jp>

diff --git a/sc/source/ui/optdlg/tpview.cxx b/sc/source/ui/optdlg/tpview.cxx
index 8640e187c5f7..213d4e73eb7b 100644
--- a/sc/source/ui/optdlg/tpview.cxx
+++ b/sc/source/ui/optdlg/tpview.cxx
@@ -34,7 +34,6 @@
 #include 
 #include 
 #include 
-#include 
 
 ScTpContentOptions::ScTpContentOptions(weld::Container* pPage, 
weld::DialogController* pController, const SfxItemSet&  rArgSet)
 : SfxTabPage(pPage, pController, "modules/scalc/ui/tpviewpage.ui", 
"TpViewPage", )


core.git: Branch 'distro/mimo/mimo-6-2' - configure.ac

2023-12-07 Thread Aron Budea (via logerrit)
 configure.ac |2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

New commits:
commit a94c68a214691edf9b81bbf4edc096d3af133c13
Author: Aron Budea 
AuthorDate: Fri Dec 8 12:12:47 2023 +1030
Commit: Aron Budea 
CommitDate: Fri Dec 8 12:12:47 2023 +1030

Bump version to 6.2.8.2.M13

Change-Id: I1040187300dcb46191df3a9d5440c75c66b55c40

diff --git a/configure.ac b/configure.ac
index 58a49bbb2fe7..d71d2b3ad3c0 100644
--- a/configure.ac
+++ b/configure.ac
@@ -9,7 +9,7 @@ dnl in order to create a configure script.
 # several non-alphanumeric characters, those are split off and used only for 
the
 # ABOUTBOXPRODUCTVERSIONSUFFIX in openoffice.lst. Why that is necessary, no 
idea.
 
-AC_INIT([LibreOffice],[6.2.8.2.M12],[],[],[http://documentfoundation.org/])
+AC_INIT([LibreOffice],[6.2.8.2.M13],[],[],[http://documentfoundation.org/])
 
 AC_PREREQ([2.59])
 


core.git: Branch 'distro/mimo/mimo-6-4' - configure.ac

2023-12-07 Thread Aron Budea (via logerrit)
 configure.ac |2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

New commits:
commit 37d0d1c981820a4bb9c2dd6dcff5395b65126cc1
Author: Aron Budea 
AuthorDate: Fri Dec 8 12:08:39 2023 +1030
Commit: Aron Budea 
CommitDate: Fri Dec 8 12:08:39 2023 +1030

Bump version to 6.4.7.2.M10

Change-Id: Iee2a59a1a2387c504512374da0c5b005afef10f8

diff --git a/configure.ac b/configure.ac
index 442de0bb7f8e..8eeb0760a846 100644
--- a/configure.ac
+++ b/configure.ac
@@ -9,7 +9,7 @@ dnl in order to create a configure script.
 # several non-alphanumeric characters, those are split off and used only for 
the
 # ABOUTBOXPRODUCTVERSIONSUFFIX in openoffice.lst. Why that is necessary, no 
idea.
 
-AC_INIT([LibreOffice],[6.4.7.2.M9],[],[],[http://documentfoundation.org/])
+AC_INIT([LibreOffice],[6.4.7.2.M10],[],[],[http://documentfoundation.org/])
 
 dnl libnumbertext needs autoconf 2.68, but that can pick up autoconf268 just 
fine if it is installed
 dnl whereas aclocal (as run by autogen.sh) insists on using autoconf and fails 
hard


core.git: Branch 'distro/mimo/mimo-7-0' - configure.ac

2023-12-07 Thread Aron Budea (via logerrit)
 configure.ac |2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

New commits:
commit 58d782c16aee2779d6d85079bbfc9c3cd828a5f9
Author: Aron Budea 
AuthorDate: Fri Dec 8 12:06:18 2023 +1030
Commit: Aron Budea 
CommitDate: Fri Dec 8 12:06:18 2023 +1030

Bump version to 7.0.7.0.M14

Change-Id: Ibc8d81e161e68022077c191eb6567451cdc83221

diff --git a/configure.ac b/configure.ac
index 2b7cdabb2c49..d469483c2a1a 100644
--- a/configure.ac
+++ b/configure.ac
@@ -9,7 +9,7 @@ dnl in order to create a configure script.
 # several non-alphanumeric characters, those are split off and used only for 
the
 # ABOUTBOXPRODUCTVERSIONSUFFIX in openoffice.lst. Why that is necessary, no 
idea.
 
-AC_INIT([LibreOffice],[7.0.7.0.M13],[],[],[http://documentfoundation.org/])
+AC_INIT([LibreOffice],[7.0.7.0.M14],[],[],[http://documentfoundation.org/])
 
 dnl libnumbertext needs autoconf 2.68, but that can pick up autoconf268 just 
fine if it is installed
 dnl whereas aclocal (as run by autogen.sh) insists on using autoconf and fails 
hard


core.git: Branch 'distro/mimo/mimo-7-1' - configure.ac

2023-12-07 Thread Aron Budea (via logerrit)
 configure.ac |2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

New commits:
commit 331830262512b2a0b5fd1e1b9feb3003c6df6113
Author: Aron Budea 
AuthorDate: Fri Dec 8 12:02:27 2023 +1030
Commit: Aron Budea 
CommitDate: Fri Dec 8 12:02:27 2023 +1030

Bump version to 7.1.8.1.M6

Change-Id: Id5a7b1ac9011a56e7bd41e00d05db9ac3e3f076c

diff --git a/configure.ac b/configure.ac
index 5d55d53f14d8..77405709ee0a 100644
--- a/configure.ac
+++ b/configure.ac
@@ -9,7 +9,7 @@ dnl in order to create a configure script.
 # several non-alphanumeric characters, those are split off and used only for 
the
 # ABOUTBOXPRODUCTVERSIONSUFFIX in openoffice.lst. Why that is necessary, no 
idea.
 
-AC_INIT([LibreOffice],[7.1.8.1.M5],[],[],[http://documentfoundation.org/])
+AC_INIT([LibreOffice],[7.1.8.1.M6],[],[],[http://documentfoundation.org/])
 
 dnl libnumbertext needs autoconf 2.68, but that can pick up autoconf268 just 
fine if it is installed
 dnl whereas aclocal (as run by autogen.sh) insists on using autoconf and fails 
hard


core.git: Branch 'distro/mimo/mimo-7-2' - configure.ac

2023-12-07 Thread Aron Budea (via logerrit)
 configure.ac |2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

New commits:
commit fc8e705fc2a0b299dfcf33d21301a2a27cac5d04
Author: Aron Budea 
AuthorDate: Fri Dec 8 11:56:28 2023 +1030
Commit: Aron Budea 
CommitDate: Fri Dec 8 11:56:28 2023 +1030

Bump version to 7.2.7.2.M15

Change-Id: I176cd41c2f59c843371e0f46c1a9274908786b61

diff --git a/configure.ac b/configure.ac
index 10dd79660e42..fe45aab0dfe3 100644
--- a/configure.ac
+++ b/configure.ac
@@ -9,7 +9,7 @@ dnl in order to create a configure script.
 # several non-alphanumeric characters, those are split off and used only for 
the
 # ABOUTBOXPRODUCTVERSIONSUFFIX in openoffice.lst. Why that is necessary, no 
idea.
 
-AC_INIT([LibreOffice],[7.2.7.2.M14],[],[],[http://documentfoundation.org/])
+AC_INIT([LibreOffice],[7.2.7.2.M15],[],[],[http://documentfoundation.org/])
 
 dnl libnumbertext needs autoconf 2.68, but that can pick up autoconf268 just 
fine if it is installed
 dnl whereas aclocal (as run by autogen.sh) insists on using autoconf and fails 
hard


[Bug 66791] FORMATTING: Incorrect application of "Asian text font" for quotation marks when the paragraph contains a mixture of western and asian characters

2023-12-07 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=66791

--- Comment #29 from Kevin Suo  ---
See a related articles:

中西文混合排版中标点符号的渲染
https://blog.1a23.com/2020/06/28/zhong-xi-wen-hunhe-paiban-zhong-biaodian-fuhao-de-xuanran/

中英混排中的标点符号问题 https://www.hutrua.com/blog/2018/07/22/punctuation.html

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

[Bug 116979] [META] Regression introduced by Aw080

2023-12-07 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=116979
Bug 116979 depends on bug 122735, which changed state.

Bug 122735 Summary: Entering a group does not make the other objects paler / 
dimmed anymore
https://bugs.documentfoundation.org/show_bug.cgi?id=122735

   What|Removed |Added

 Status|VERIFIED|REOPENED
 Resolution|FIXED   |---

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

[Bug 108640] [META] Object meta bugs and enhancements

2023-12-07 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=108640
Bug 108640 depends on bug 122735, which changed state.

Bug 122735 Summary: Entering a group does not make the other objects paler / 
dimmed anymore
https://bugs.documentfoundation.org/show_bug.cgi?id=122735

   What|Removed |Added

 Status|VERIFIED|REOPENED
 Resolution|FIXED   |---

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

[Bug 137080] LibreOffice should use built-in OpenType Feature Small Capitals (smcp tag) when the typeface has it instead of simulated Small Capitals

2023-12-07 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=137080

--- Comment #4 from nj  ---
Might I bump this issue? For, if it is related to small caps in PowerPoint
files ending up always as actual capitals within Impress, then that this a
fairly serious problem. (Impress compatibility with PointPoint has come a long
away. It is a shame to let that compatibility founder on a small but important
point such as this one.)

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

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

2023-12-07 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=158590

Bug ID: 158590
   Summary: Interface design bug "Scale"  for Draw documents
   Product: LibreOffice
   Version: 3.3.0 release
  Hardware: All
OS: All
Status: UNCONFIRMED
  Severity: enhancement
  Priority: medium
 Component: Draw
  Assignee: libreoffice-bugs@lists.freedesktop.org
  Reporter: juani...@gmail.com

Description:
The basic problem is that no distinction is made between "default scale" and
"document scale".

Draw saves scales (for dimensions) on a per document basis as when re-oppened
the scale initially used for that document is used independently of my
currently set default values (a good feature). The problem is not the
behaviour, but the interface which lets me change the "options" for scale. This
means that if I want to change the scale used for the current document, I must
change the scale on the "options" dialog, and re-save the document. The problem
with this approach is that I have also effectively changed the default scale
for new documents (not necessarily an intended behaviour on the user's part).  



Steps to Reproduce:
1 Open an existing draw document with a set scale
2.Change the scale in option and save the document
3.Create a new draw document

Actual Results:
Creating a new document uses the new scale

Expected Results:
In this specific scenario the intended result was to change the scale of only
the opened document.


Reproducible: Always


User Profile Reset: No

Additional Info:
More appropriately, the scale in the "options" dialog should be reworded as
"default scale", and only affect the scale for new documents. A new "document
scale" property should be accessible (maybe through the "format page"
interface) to change the scale of the current document separately form the
"default scale".

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

[Bug 87078] Cross-reference dialogue in Sidebar

2023-12-07 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=87078

RGB  changed:

   What|Removed |Added

 CC||rgb.m...@gmail.com

--- Comment #6 from RGB  ---
(In reply to Heiko Tietze from comment #2)
> [...] But before we start with a new UI wouldn't it make sense
> to integrate the function into the navigator? For instance you right click
> the headings entry that should be inserted and below the current options
> (which should be removed by the way since none of them is not context
> sensitive) would offer 'Insert cross-reference >' with 'Page', 'Chapter',
> 'Reference' etc. below.
> 
> Would that work? [...]

Bug 36310 suggests a new "drag & drop mode" from the navigator to insert
cross-references.

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

[Bug 87078] Cross-reference dialogue in Sidebar

2023-12-07 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=87078

RGB  changed:

   What|Removed |Added

 CC||rgb.m...@gmail.com

--- Comment #6 from RGB  ---
(In reply to Heiko Tietze from comment #2)
> [...] But before we start with a new UI wouldn't it make sense
> to integrate the function into the navigator? For instance you right click
> the headings entry that should be inserted and below the current options
> (which should be removed by the way since none of them is not context
> sensitive) would offer 'Insert cross-reference >' with 'Page', 'Chapter',
> 'Reference' etc. below.
> 
> Would that work? [...]

Bug 36310 suggests a new "drag & drop mode" from the navigator to insert
cross-references.

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

[Bug 158589] Add option to save Font Replacement Table

2023-12-07 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=158589

m.a.riosv  changed:

   What|Removed |Added

   Severity|normal  |enhancement

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

[Bug 158587] Improve column/row highlighting in Calc

2023-12-07 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=158587

m.a.riosv  changed:

   What|Removed |Added

 CC||miguelangelrv@libreoffice.o
   ||rg

--- Comment #4 from m.a.riosv  ---
I'm with Ady

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

[Bug 158587] Improve column/row highlighting in Calc

2023-12-07 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=158587

m.a.riosv  changed:

   What|Removed |Added

 CC||miguelangelrv@libreoffice.o
   ||rg

--- Comment #4 from m.a.riosv  ---
I'm with Ady

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

[Bug 158584] Problem "Save As" from LibreOffice Writer to fileformat: "Word 2003 XML (.xml)" - width of table(s) decreases to 2%

2023-12-07 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=158584

m.a.riosv  changed:

   What|Removed |Added

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

--- Comment #2 from m.a.riosv  ---
Reproducible
Version: 24.2.0.0.alpha1+ (X86_64) / LibreOffice Community
Build ID: 0ddd9f7e055a0c1ecb120de3e40c3fdb8373e9dc
CPU threads: 16; OS: Windows 10.0 Build 22631; UI render: Skia/Vulkan; VCL: win
Locale: es-ES (es_ES); UI: en-US
Calc: CL threaded

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

[Bug 158581] file>properties>statistics>lines expand the line field

2023-12-07 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=158581

m.a.riosv  changed:

   What|Removed |Added

 CC||miguelangelrv@libreoffice.o
   ||rg

--- Comment #1 from m.a.riosv  ---
Please paste here the information on Menu/Help/About LibreOffice (There is an
icon to copy)

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

[Bug 158589] New: Add option to save Font Replacement Table

2023-12-07 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=158589

Bug ID: 158589
   Summary: Add option to save Font Replacement Table
   Product: LibreOffice
   Version: 7.6.4.1 release
  Hardware: All
OS: All
Status: UNCONFIRMED
  Severity: normal
  Priority: medium
 Component: LibreOffice
  Assignee: libreoffice-bugs@lists.freedesktop.org
  Reporter: j22...@gmail.com

Description:
Some users spend quite some time creating a Font Replacement Table to avoid
proprietary fonts. It would be nice to offer them the option to save the table
so they can retrieve it eg. in case of a fresh install.

Steps to Reproduce:
1. Options -> LibreOffice -> Fonts
2. Populate the Replacement Table
3. Install a fresh copy of LO


Actual Results:
You have to re-populate the Replacement Table

Expected Results:
There is a button 'Load replacement table' that populates the table.
Note I am not suggesting that the fonts have to be saved (this is obviously out
of the scope of LO), but only the replacement table. 
If you load the table and there is a font that is not installed (either in the
'Font' or 'Replace with' columns) then it could be shown in italics following
the current behavior of LO when you open a document that is supposed to be in a
font that you have not installed. Then the user can know that entry in the
Replacement Table is not going to make any difference because one or both of
those fonts need to be installed first.


Reproducible: Always


User Profile Reset: No

Additional Info:
This is an example of a very useful and rather long replacement table:

https://blog.documentfoundation.org/blog/2020/09/08/libreoffice-tt-replacing-microsoft-fonts/

It must be quite tedious to populate it one by one.

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

[Bug 158588] ODT bloats in file size by factor 4 by saving without changes, font embedding options based on two checkboxes should be redesigned

2023-12-07 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=158588

--- Comment #4 from OfficeUser  ---
I assume that all LibreOffice applications are affected by these issues. But I
only tested Writer.

Please also have a look at:
https://www.reddit.com/r/libreoffice/comments/136b8ni/fonts_embedding_what_those_options_actually_do/

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

[Bug 158588] ODT bloats in file size by factor 4 by saving without changes, font embedding options based on two checkboxes should be redesigned

2023-12-07 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=158588

OfficeUser  changed:

   What|Removed |Added

Summary|ODT bloats in file size by  |ODT bloats in file size by
   |factor 4 by saving without  |factor 4 by saving without
   |changes |changes, font embedding
   ||options based on two
   ||checkboxes should be
   ||redesigned

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

[Bug 158588] ODT bloats in file size by factor 4 by saving without changes

2023-12-07 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=158588

--- Comment #3 from OfficeUser  ---
In addition I found:

There are two checkboxed to set which fonts to embedd.

It looks like "Only embed used fonts" seems to have no effect stand-alone. It
produces the same file size as if there is non of these two checkboxes
checkedd.

This is why I ask to replace these two checkboxes by three three radio buttons.
That would lead to a clear user experience.

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

core.git: vcl/osx

2023-12-07 Thread Patrick Luby (via logerrit)
 vcl/osx/salnativewidgets.cxx |   16 
 1 file changed, 16 insertions(+)

New commits:
commit 5ff701226b00963312cb2a78e77966d012b79c82
Author: Patrick Luby 
AuthorDate: Thu Dec 7 14:20:16 2023 -0500
Commit: Patrick Luby 
CommitDate: Thu Dec 7 22:36:22 2023 +0100

Related: tdf#155266 force flush after drawing native scrollbars

When scrolling on some Intel Macs either via dragging
the scrollbar thumb or via swiping the trackpad with two
fingers, final repaint of scrollbars doesn't appear to
get flushed to the screen. It appears that scrollbars
aren't updated and repainted until after a batch of
native scroll events have been dispatched. On slower
machines, this lag is long enough that any pending
forced flushes have already been done so when the timer
that repaints scrollbars finally fires, the repainted
scrollbars won't get flushed to the native window until
the next normal flush which may not occur until seconds
later.

Change-Id: Iadef6812cd2495a28347560caae81f604c908b51
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/160440
Tested-by: Jenkins
Reviewed-by: Patrick Luby 

diff --git a/vcl/osx/salnativewidgets.cxx b/vcl/osx/salnativewidgets.cxx
index 8a7e81fd5d86..a50735bf4628 100644
--- a/vcl/osx/salnativewidgets.cxx
+++ b/vcl/osx/salnativewidgets.cxx
@@ -757,6 +757,22 @@ bool 
AquaGraphicsBackendBase::performDrawNativeControl(ControlType nType,
 
 CGContextRestoreGState(context);
 
+// Related: tdf#155266 force flush after drawing native 
scrollbars
+// When scrolling on some Intel Macs either via dragging
+// the scrollbar thumb or via swiping the trackpad with two
+// fingers, final repaint of scrollbars doesn't appear to
+// get flushed to the screen. It appears that scrollbars
+// aren't updated and repainted until after a batch of
+// native scroll events have been dispatched. On slower
+// machines, this lag is long enough that any pending
+// forced flushes have already been done so when the timer
+// that repaints scrollbars finally fires, the repainted
+// scrollbars won't get flushed to the native window until
+// the next normal flush which may not occur until seconds
+// later.
+if (mpFrame && nType == ControlType::Scrollbar)
+mpFrame->mbForceFlush = true;
+
 bOK = true;
 
 [pBar release];


[Bug 96886] Allow to change mouse pointer into a "laser pointer" during slide show

2023-12-07 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=96886

--- Comment #11 from j22...@gmail.com ---
Created attachment 191305
  --> https://bugs.documentfoundation.org/attachment.cgi?id=191305=edit
This is how it would work

Note: if you have VLC you may see an empty video. Try disabling 'hardware
decoding' or use another video player.

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

[Bug 96886] Allow to change mouse pointer into a "laser pointer" during slide show

2023-12-07 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=96886

--- Comment #10 from j22...@gmail.com ---
I add my comments here to have everything in one place. Bonus track: I show it
on a video.


Description:
It would be great if there was an option to select a "fading pen" or "laser
pointer" (not sure what the right name would be). This is simply a pen that
fades in some seconds, thus making your remark transient (and therefore not
ruining your slide if you still need to show it a bit more time).

Steps to Reproduce:
If you want to highlight/remark on something while showing a slide (maybe
replying to a question about something you did not stress in the presentation),
you have the option to mark it using the 'mouse as pen' option. You can also
use this tool while presenting for the first time, depending on your style and
choice.
However, everything that you do on the slide ends up kind of messing up the
visuals of that particular slide.

Actual Results:
At that point, you have to right-click and select "Erase all ink on slide".

There are two problems with this:
1. It is a little bit of an interruption to the flow of the talk, and 
2. you either wait until you have a lot of 'ink' on the slide and then erase
all of it, or you have to 'write and erase' many times.

Expected Results:
Both problems would be avoided if the ink disappeared by itself. This is, the
ink stays only a few seconds, long enough to be seen by the audience (and thus,
highlight your point), but at the same time it doesn't matter how much you
scribble, your slide will eventually be clean again.


Reproducible: Always


User Profile Reset: No

Additional Info:
I shamelessly took this idea from another program: a neat online whiteboard
application called ExcaliDraw (www.excalidraw.com). In that application, you
can select something called 'laser pointer' (which I think is a good name!)
which will draw a line that fades out after 2-3 seconds (and it does so very
elegantly following the same trajectory used by the pointer). You can see how
it works in the attached video. It is open source and we should give them
credit.

I think it would be a very nice addition to Impress.
Thanks for all your work and let's continue improving LO!!


Note: if you have VLC you may see an empty video. Try disabling 'hardware
decoding' or use another video player.

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

[Bug 158588] ODT bloats in file size by factor 4 by saving without changes

2023-12-07 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=158588

--- Comment #2 from OfficeUser  ---
Created attachment 191304
  --> https://bugs.documentfoundation.org/attachment.cgi?id=191304=edit
embedded fonts.png

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

[Bug 158588] ODT bloats in file size by factor 4 by saving without changes

2023-12-07 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=158588

--- Comment #1 from OfficeUser  ---
Created attachment 191303
  --> https://bugs.documentfoundation.org/attachment.cgi?id=191303=edit
File new.odt

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

[Bug 158588] New: ODT bloats in file size by factor 4 by saving without changes

2023-12-07 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=158588

Bug ID: 158588
   Summary: ODT bloats in file size by factor 4 by saving without
changes
   Product: LibreOffice
   Version: 7.6.2.1 release
  Hardware: All
OS: All
Status: UNCONFIRMED
  Severity: normal
  Priority: medium
 Component: framework
  Assignee: libreoffice-bugs@lists.freedesktop.org
  Reporter: norbert.n...@gmx.de

Created attachment 191302
  --> https://bugs.documentfoundation.org/attachment.cgi?id=191302=edit
File old.dt

I have a strange finding. After saving a odt from 2021 ("File old.odt") without
any changes in LibreOffice 7.6.2.1 the file size multiplicates ("File
new.odt").

"File old.odt": 993,2 kB
"File new.odt": 4.1 MB

After investigating the extracted content of the odt/zip files I found the
reason:
By saving without any changes in recent LibreOffice build  addiontinal fonts
have been embedded into the odt file. Why? (see "embedded fonts.png")



Version: 7.6.2.1 (X86_64) / LibreOffice Community
Build ID: 60(Build:1)
CPU threads: 8; OS: Linux 5.4; UI render: default; VCL: gtk3
Locale: de-DE (de_DE.UTF-8); UI: de-DE
Ubuntu package version: 4:7.6.2~rc1-0ubuntu0.18.04.1~lo1
Calc: threaded

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

[Bug 158578] Some PowerPoint files require extremely long loading times

2023-12-07 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=158578

--- Comment #5 from m.a.riosv  ---
I can't understand how it works in safe mode and not with a reset profile.

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

[Bug 158523] Whole pages of Comments are not PRINTING or exported to PDF in margins

2023-12-07 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=158523

--- Comment #3 from tim  ---
The attached file did not fix the problem. There are a couple of issues with
that file. If you look carefully, you will find that the file has 61 pages, but
the last page says it is page 64. So the conversion to PDF left the blank pages
out. Also, the original file had only 58 pages, including blank pages, so the
ODT file did not export properly. It looks like it changed all of the fonts.
(Note: I sent the ODT file with embedded fonts. It should have opened properly
with 58 pages, but I might have done something wrong there.)

None-the-less, you can see the problem in the file you created. You will see on
page 59 (labeled page 62) that there are no comments in the margin. There
should be three comments there. This page corresponds with the original ODT
file page 56, which has three comments. So, despite the fact that the page
numbers and fonts are mess up, you can see that the problem still exists.

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

core.git: Branch 'libreoffice-7-6' - readlicense_oo/license

2023-12-07 Thread Christian Lohmaier (via logerrit)
 readlicense_oo/license/CREDITS.fodt |13258 ++--
 1 file changed, 6726 insertions(+), 6532 deletions(-)

New commits:
commit b41d4c84d50893a90e676d873c5b81b4e725a309
Author: Christian Lohmaier 
AuthorDate: Thu Dec 7 22:03:27 2023 +0100
Commit: Christian Lohmaier 
CommitDate: Thu Dec 7 22:05:29 2023 +0100

update credits

Change-Id: I6bb7de64be70c68362169ae459cffa37478395b1
(cherry picked from commit 573f61fdb06e0824d0800dc16005c496f3c2d58f)

diff --git a/readlicense_oo/license/CREDITS.fodt 
b/readlicense_oo/license/CREDITS.fodt
index 046a641c4764..045eaad4e015 100644
--- a/readlicense_oo/license/CREDITS.fodt
+++ b/readlicense_oo/license/CREDITS.fodt
@@ -1,24 +1,24 @@
 
 
 http://www.w3.org/TR/css3-text/; 
xmlns:grddl="http://www.w3.org/2003/g/data-view#; 
xmlns:xhtml="http://www.w3.org/1999/xhtml; 
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance; 
xmlns:xsd="http://www.w3.org/2001/XMLSchema; 
xmlns:xforms="http://www.w3.org/2002/xforms; 
xmlns:dom="http://www.w3.org/2001/xml-events; 
xmlns:script="urn:oasis:names:tc:opendocument:xmlns:script:1.0" 
xmlns:form="urn:oasis:names:tc:opendocument:xmlns:form:1.0" 
xmlns:math="http://www.w3.org/1998/Math/MathML; 
xmlns:office="urn:oasis:names:tc:opendocument:xmlns:office:1.0" 
xmlns:ooo="http://openoffice.org/2004/office; 
xmlns:fo="urn:oasis:names:tc:opendocument:xmlns:xsl-fo-compatible:1.0" 
xmlns:config="urn:oasis:names:tc:opendocument:xmlns:config:1.0" 
xmlns:ooow="http://openoffice.org/2004/writer; 
xmlns:xlink="http://www.w3.org/1999/xlink; 
xmlns:drawooo="http://openoffice.org/2010/draw; 
xmlns:oooc="http://openoffice.org/2004/calc; 
xmlns:dc="http://purl.org/dc/elements/1.1/; xmlns:c
 alcext="urn:org:documentfoundation:names:experimental:calc:xmlns:calcext:1.0" 
xmlns:style="urn:oasis:names:tc:opendocument:xmlns:style:1.0" 
xmlns:text="urn:oasis:names:tc:opendocument:xmlns:text:1.0" 
xmlns:of="urn:oasis:names:tc:opendocument:xmlns:of:1.2" 
xmlns:tableooo="http://openoffice.org/2009/table; 
xmlns:draw="urn:oasis:names:tc:opendocument:xmlns:drawing:1.0" 
xmlns:dr3d="urn:oasis:names:tc:opendocument:xmlns:dr3d:1.0" 
xmlns:rpt="http://openoffice.org/2005/report; 
xmlns:formx="urn:openoffice:names:experimental:ooxml-odf-interop:xmlns:form:1.0"
 xmlns:svg="urn:oasis:names:tc:opendocument:xmlns:svg-compatible:1.0" 
xmlns:chart="urn:oasis:names:tc:opendocument:xmlns:chart:1.0" 
xmlns:officeooo="http://openoffice.org/2009/office; 
xmlns:table="urn:oasis:names:tc:opendocument:xmlns:table:1.0" 
xmlns:field="urn:openoffice:names:experimental:ooo-ms-interop:xmlns:field:1.0" 
xmlns:number="urn:oasis:names:tc:opendocument:xmlns:datastyle:1.0" 
xmlns:meta="urn:oasis:names:tc:opendocument:xmlns:
 meta:1.0" 
xmlns:loext="urn:org:documentfoundation:names:experimental:office:xmlns:loext:1.0"
 office:version="1.3" office:mimetype="application/vnd.oasis.opendocument.text">
- Credits » 
LibreOfficeCreditscontributorscodersdevelopersCredits
 for the LibreOffice 
development/coding.LibreOffice/7.4.7.2$Linux_X86_64
 
LibreOffice_project/40$Build-22012-02-20T22:17:18.06000PT14M12S3JUebjoxEpqXoQcpltWRTwzBZEEHtch3wApdhgiQPFiA
+ Credits » 
LibreOfficeCreditscontributorscodersdevelopersCredits
 for the LibreOffice 
development/coding.LibreOffice/7.6.4.1$Linux_X86_64
 
LibreOffice_project/e19e193f88cd6c0525a17fb7a176ed8e6a3e2aa12012-02-20T22:17:18.06000PT14M12S3JUebjoxEpqXoQcpltWRTwzBZEEHtch3wApdhgiQPFiA
  
   
-   1751198
+   2487
501
-   48182
-   21592
+   55167
+   26989
true
true

 
  view2
- 24075
- 1772020
+ 3649
+ 3434
  501
- 1751198
- 48682
- 1772788
+ 2487
+ 55667
+ 29475
  0
  0
  false
@@ -26,68 +26,53 @@
  false
  false
  false
+ false
+ false
+ false
 

   
   
-   false
-   false
-   false
+   true
+   false
true
-   true
+   false
true
-   true
-   true
+   false
false
0
-   false
-   false
+   false
+   false
+   false
+   false
false
-   false
+   false
true
+   true
true
-   false
false
-   false
+   
+   false
false
-   false
+   false
+   false
+   false
true
-   true
true
false
-   false
-   false
false
false
+   false
false
false
-   false
true
-   false
-   false
-   true
+   false
false
-   false
-   false
-   true
-   0
-   1
-   true
-   false
-   
-   high-resolution
-   false
-   
+   1557161
+   false
Adressen
-   false
-   false
-   true
-   false
-   false
-   true
-   true
-   false
-   true
+   true
+   false

 
  hu
@@ -97,54 +82,73 @@
  
 

-   
-   true
-   12866985
-   
-   true
-   false
+   false
+   12871163
true
-   true
-   0
-   
+   false
false
-   false
-   false
-   false
-   false
+   false
+   1
+   true
true
+   false
+   false
+   false
+   false
+   true
+   true
+   true
+   true
+   false
+   true
0
-   false
-   false
-   false
+   
+   true

core.git: readlicense_oo/license

2023-12-07 Thread Christian Lohmaier (via logerrit)
 readlicense_oo/license/CREDITS.fodt |13258 ++--
 1 file changed, 6726 insertions(+), 6532 deletions(-)

New commits:
commit 573f61fdb06e0824d0800dc16005c496f3c2d58f
Author: Christian Lohmaier 
AuthorDate: Thu Dec 7 22:03:27 2023 +0100
Commit: Christian Lohmaier 
CommitDate: Thu Dec 7 22:03:27 2023 +0100

update credits

Change-Id: I6bb7de64be70c68362169ae459cffa37478395b1

diff --git a/readlicense_oo/license/CREDITS.fodt 
b/readlicense_oo/license/CREDITS.fodt
index 046a641c4764..045eaad4e015 100644
--- a/readlicense_oo/license/CREDITS.fodt
+++ b/readlicense_oo/license/CREDITS.fodt
@@ -1,24 +1,24 @@
 
 
 http://www.w3.org/TR/css3-text/; 
xmlns:grddl="http://www.w3.org/2003/g/data-view#; 
xmlns:xhtml="http://www.w3.org/1999/xhtml; 
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance; 
xmlns:xsd="http://www.w3.org/2001/XMLSchema; 
xmlns:xforms="http://www.w3.org/2002/xforms; 
xmlns:dom="http://www.w3.org/2001/xml-events; 
xmlns:script="urn:oasis:names:tc:opendocument:xmlns:script:1.0" 
xmlns:form="urn:oasis:names:tc:opendocument:xmlns:form:1.0" 
xmlns:math="http://www.w3.org/1998/Math/MathML; 
xmlns:office="urn:oasis:names:tc:opendocument:xmlns:office:1.0" 
xmlns:ooo="http://openoffice.org/2004/office; 
xmlns:fo="urn:oasis:names:tc:opendocument:xmlns:xsl-fo-compatible:1.0" 
xmlns:config="urn:oasis:names:tc:opendocument:xmlns:config:1.0" 
xmlns:ooow="http://openoffice.org/2004/writer; 
xmlns:xlink="http://www.w3.org/1999/xlink; 
xmlns:drawooo="http://openoffice.org/2010/draw; 
xmlns:oooc="http://openoffice.org/2004/calc; 
xmlns:dc="http://purl.org/dc/elements/1.1/; xmlns:c
 alcext="urn:org:documentfoundation:names:experimental:calc:xmlns:calcext:1.0" 
xmlns:style="urn:oasis:names:tc:opendocument:xmlns:style:1.0" 
xmlns:text="urn:oasis:names:tc:opendocument:xmlns:text:1.0" 
xmlns:of="urn:oasis:names:tc:opendocument:xmlns:of:1.2" 
xmlns:tableooo="http://openoffice.org/2009/table; 
xmlns:draw="urn:oasis:names:tc:opendocument:xmlns:drawing:1.0" 
xmlns:dr3d="urn:oasis:names:tc:opendocument:xmlns:dr3d:1.0" 
xmlns:rpt="http://openoffice.org/2005/report; 
xmlns:formx="urn:openoffice:names:experimental:ooxml-odf-interop:xmlns:form:1.0"
 xmlns:svg="urn:oasis:names:tc:opendocument:xmlns:svg-compatible:1.0" 
xmlns:chart="urn:oasis:names:tc:opendocument:xmlns:chart:1.0" 
xmlns:officeooo="http://openoffice.org/2009/office; 
xmlns:table="urn:oasis:names:tc:opendocument:xmlns:table:1.0" 
xmlns:field="urn:openoffice:names:experimental:ooo-ms-interop:xmlns:field:1.0" 
xmlns:number="urn:oasis:names:tc:opendocument:xmlns:datastyle:1.0" 
xmlns:meta="urn:oasis:names:tc:opendocument:xmlns:
 meta:1.0" 
xmlns:loext="urn:org:documentfoundation:names:experimental:office:xmlns:loext:1.0"
 office:version="1.3" office:mimetype="application/vnd.oasis.opendocument.text">
- Credits » 
LibreOfficeCreditscontributorscodersdevelopersCredits
 for the LibreOffice 
development/coding.LibreOffice/7.4.7.2$Linux_X86_64
 
LibreOffice_project/40$Build-22012-02-20T22:17:18.06000PT14M12S3JUebjoxEpqXoQcpltWRTwzBZEEHtch3wApdhgiQPFiA
+ Credits » 
LibreOfficeCreditscontributorscodersdevelopersCredits
 for the LibreOffice 
development/coding.LibreOffice/7.6.4.1$Linux_X86_64
 
LibreOffice_project/e19e193f88cd6c0525a17fb7a176ed8e6a3e2aa12012-02-20T22:17:18.06000PT14M12S3JUebjoxEpqXoQcpltWRTwzBZEEHtch3wApdhgiQPFiA
  
   
-   1751198
+   2487
501
-   48182
-   21592
+   55167
+   26989
true
true

 
  view2
- 24075
- 1772020
+ 3649
+ 3434
  501
- 1751198
- 48682
- 1772788
+ 2487
+ 55667
+ 29475
  0
  0
  false
@@ -26,68 +26,53 @@
  false
  false
  false
+ false
+ false
+ false
 

   
   
-   false
-   false
-   false
+   true
+   false
true
-   true
+   false
true
-   true
-   true
+   false
false
0
-   false
-   false
+   false
+   false
+   false
+   false
false
-   false
+   false
true
+   true
true
-   false
false
-   false
+   
+   false
false
-   false
+   false
+   false
+   false
true
-   true
true
false
-   false
-   false
false
false
+   false
false
false
-   false
true
-   false
-   false
-   true
+   false
false
-   false
-   false
-   true
-   0
-   1
-   true
-   false
-   
-   high-resolution
-   false
-   
+   1557161
+   false
Adressen
-   false
-   false
-   true
-   false
-   false
-   true
-   true
-   false
-   true
+   true
+   false

 
  hu
@@ -97,54 +82,73 @@
  
 

-   
-   true
-   12866985
-   
-   true
-   false
+   false
+   12871163
true
-   true
-   0
-   
+   false
false
-   false
-   false
-   false
-   false
+   false
+   1
+   true
true
+   false
+   false
+   false
+   false
+   true
+   true
+   true
+   true
+   false
+   true
0
-   false
-   false
-   false
+   
+   true
+   true
+   false
+   false
+   
+   0
+   true
+   false
+   false
+   

[Bug 158585] add 'laser pointer' to presentations

2023-12-07 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=158585

Stéphane Guillou (stragu)  changed:

   What|Removed |Added

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

--- Comment #2 from Stéphane Guillou (stragu) 
 ---
Thanks for the suggestion. This is already tracked in bug 96886, so marking as
duplicate.
Please feel free to comment about the "trailing" aspect there if you feel it is
needed.

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

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

[Bug 96886] Allow to change mouse pointer into a "laser pointer" during slide show

2023-12-07 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=96886

Stéphane Guillou (stragu)  changed:

   What|Removed |Added

 CC||j22...@gmail.com

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

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

core.git: include/sal xmlsecurity/source

2023-12-07 Thread Michael Stahl (via logerrit)
 include/sal/log-areas.dox|1 
 xmlsecurity/source/xmlsec/nss/ciphercontext.cxx  |   63 ++-
 xmlsecurity/source/xmlsec/nss/nssinitializer.cxx |1 
 3 files changed, 43 insertions(+), 22 deletions(-)

New commits:
commit 328b135f0decbab475c16560f4b366559f2d0e66
Author: Michael Stahl 
AuthorDate: Thu Dec 7 16:00:17 2023 +0100
Commit: Michael Stahl 
CommitDate: Thu Dec 7 21:46:00 2023 +0100

xmlsecurity: check for errors in OCipherContext::Create()

If this function returns null, storing a document will proceed without
reporting an error to the user, and lose all the data.

Change-Id: I0f9fd53702321e7997b28e12eb5bed3349bbcc13
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/160435
Tested-by: Jenkins
Reviewed-by: Michael Stahl 

diff --git a/include/sal/log-areas.dox b/include/sal/log-areas.dox
index ef7d9b07363b..15cba1e538b5 100644
--- a/include/sal/log-areas.dox
+++ b/include/sal/log-areas.dox
@@ -593,6 +593,7 @@ certain functionality.
 @li @c xmlsecurity.comp - xml security component
 @li @c xmlsecurity.dialogs - xml security dialogs
 @li @c xmlsecurity.helper
+@li @c xmlsecurity.nss
 @li @c xmlsecurity.ooxml - OOXML signature support
 @li @c xmlsecurity.qa
 @li @c xmlsecurity.workben
diff --git a/xmlsecurity/source/xmlsec/nss/ciphercontext.cxx 
b/xmlsecurity/source/xmlsec/nss/ciphercontext.cxx
index 5be6eb26c6d2..bf0a16bfca38 100644
--- a/xmlsecurity/source/xmlsec/nss/ciphercontext.cxx
+++ b/xmlsecurity/source/xmlsec/nss/ciphercontext.cxx
@@ -35,31 +35,50 @@ uno::Reference< xml::crypto::XCipherContext > 
OCipherContext::Create( CK_MECHANI
 ::rtl::Reference< OCipherContext > xResult = new OCipherContext;
 
 xResult->m_pSlot = PK11_GetBestSlot( nNSSCipherID, nullptr );
-if ( xResult->m_pSlot )
+if (!xResult->m_pSlot)
 {
-SECItem aKeyItem = { siBuffer, const_cast< unsigned char* >( 
reinterpret_cast< const unsigned char* >( aKey.getConstArray() ) ), 
sal::static_int_cast( aKey.getLength() ) };
-xResult->m_pSymKey = PK11_ImportSymKey( xResult->m_pSlot, 
nNSSCipherID, PK11_OriginDerive, bEncryption ? CKA_ENCRYPT : CKA_DECRYPT, 
, nullptr );
-if ( xResult->m_pSymKey )
-{
-SECItem aIVItem = { siBuffer, const_cast< unsigned char* >( 
reinterpret_cast< const unsigned char* >( aInitializationVector.getConstArray() 
) ), sal::static_int_cast( aInitializationVector.getLength() ) };
-xResult->m_pSecParam = PK11_ParamFromIV( nNSSCipherID,  );
-if ( xResult->m_pSecParam )
-{
-xResult->m_pContext = PK11_CreateContextBySymKey( 
nNSSCipherID, bEncryption ? CKA_ENCRYPT : CKA_DECRYPT, xResult->m_pSymKey, 
xResult->m_pSecParam);
-if ( xResult->m_pContext )
-{
-xResult->m_bEncryption = bEncryption;
-xResult->m_bW3CPadding = bW3CPadding;
-xResult->m_bPadding = bW3CPadding || ( 
PK11_GetPadMechanism( nNSSCipherID ) == nNSSCipherID );
-xResult->m_nBlockSize = PK11_GetBlockSize( nNSSCipherID, 
xResult->m_pSecParam );
-if ( xResult->m_nBlockSize <= SAL_MAX_INT8 )
-return xResult;
-}
-}
-}
+SAL_WARN("xmlsecurity.nss", "PK11_GetBestSlot failed");
+throw uno::RuntimeException("PK11_GetBestSlot failed");
 }
 
-return uno::Reference< xml::crypto::XCipherContext >();
+SECItem aKeyItem = { siBuffer,
+const_cast(reinterpret_cast(aKey.getConstArray())),
+sal::static_int_cast(aKey.getLength()) };
+xResult->m_pSymKey = PK11_ImportSymKey(xResult->m_pSlot, nNSSCipherID,
+PK11_OriginDerive, bEncryption ? CKA_ENCRYPT : CKA_DECRYPT, , 
nullptr);
+if (!xResult->m_pSymKey)
+{
+SAL_WARN("xmlsecurity.nss", "PK11_ImportSymKey failed");
+throw uno::RuntimeException("PK11_ImportSymKey failed");
+}
+
+SECItem aIVItem = { siBuffer,
+const_cast(reinterpret_cast(aInitializationVector.getConstArray())),
+sal::static_int_cast(aInitializationVector.getLength()) };
+xResult->m_pSecParam = PK11_ParamFromIV(nNSSCipherID, );
+if (!xResult->m_pSecParam)
+{
+SAL_WARN("xmlsecurity.nss", "PK11_ParamFromIV failed");
+throw uno::RuntimeException("PK11_ParamFromIV failed");
+}
+
+xResult->m_pContext = PK11_CreateContextBySymKey( nNSSCipherID, 
bEncryption ? CKA_ENCRYPT : CKA_DECRYPT, xResult->m_pSymKey, 
xResult->m_pSecParam);
+if (!xResult->m_pContext)
+{
+SAL_WARN("xmlsecurity.nss", "PK11_CreateContextBySymKey failed");
+throw uno::RuntimeException("PK11_CreateContextBySymKey failed");
+}
+
+xResult->m_bEncryption = bEncryption;
+xResult->m_bW3CPadding = bW3CPadding;
+xResult->m_bPadding = bW3CPadding || ( PK11_GetPadMechanism( nNSSCipherID 
) == nNSSCipherID );
+xResult->m_nBlockSize = 

[Bug 89673] EDITING - can't use the regular context menu on misspelled words

2023-12-07 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=89673

Stéphane Guillou (stragu)  changed:

   What|Removed |Added

 CC||kaese...@gmail.com

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

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

[Bug 158567] Right-click on misspelled words only offers spelling-related functions, no formatting options

2023-12-07 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=158567

Stéphane Guillou (stragu)  changed:

   What|Removed |Added

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

--- Comment #1 from Stéphane Guillou (stragu) 
 ---
Thanks for the report. I agree this could be improved, it's very common to have
both the usual actions + the spellcheck suggestions in the one context menu
nowadays, for example in web browsers.
Issue is already tracked in bug 89673 so marking as duplicate.

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

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

[Bug 156379] Writer file properties: word count lacks space to display 4 and more digits

2023-12-07 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=156379

Rafael Lima  changed:

   What|Removed |Added

 Status|NEW |ASSIGNED
   Assignee|libreoffice-b...@lists.free |rafael.palma.l...@gmail.com
   |desktop.org |

--- Comment #6 from Rafael Lima  ---
Proposed patch here:
https://gerrit.libreoffice.org/c/core/+/160367

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

[Bug 158587] Improve column/row highlighting in Calc

2023-12-07 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=158587

--- Comment #3 from ady  ---
FWIW, the additional row+column highlighting is supposed to help in easier
location of the cell that has the current focus.

Expanding the extra row+column highlighting to cover every selected range might
be counterproductive regarding the original goal of the feature.

IMO, the new optional row+column highlighting should be relevant for cell's
_focus_, not for range _selection_, which already has its own highlight, both
on the cell/range itself and on the row/column headers.

In the "simpler range" case, the "home" cell of the selection has its
row+column highlighted, so the range is easily seen, not to mention it is all
already highlighted by itself and at the row/column headers.

What would be expected to be highlighted if there are several non-contiguous
ranges selected? IMO, that would not be useful.

BTW, as an additional help for users, the traditional Name Box shows the cell
or range (either focused or selected).

I'm not convinced that expanding the row+column highlighting to the entire
selection would be an improvement; I'm worried it would be counterproductive.

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

  1   2   3   4   >