[Bug 159386] Selecting all in a certain table causes assert in SfxPoolItem::SetWhich with a debug build

2024-01-26 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=159386

--- Comment #3 from Telesto  ---
FWIW: issue isn't limited to debug builds; see bug 159392. Master builds are
'unusable' for testing right now, IMHO. Future bibisects in the range with the
issue present will be quite challenging...

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

[Bug 141717] Fonts with lots of ligatures display incorrectly at big sizes

2024-01-26 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=141717

--- Comment #4 from danielkyler  ---
The paragraph you shared mentions that fonts with many ligatures will display
incorrectly when used at large sizes. Ligature is the combination of two or
more characters into a single character in a font. Improper display may occur
when the font size is large because small details of the ligature are not
displayed clearly like IQ test free - https://iqtestfree.io/. This can be a
problem when using large fonts in graphic design or printing.

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

[Bug 159196] Deleting a column of a floating table with Track changes ON and show OFF deletes the whole table and no restore with undo

2024-01-26 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=159196

--- Comment #3 from Buovjaga  ---
Hmm, what's the fix?

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

[Bug 159392] Crash: after selecting a floating table and clicking 'file' in menubar (mergedlo!SfxPoolItem::CloneSetWhich+0x25:)

2024-01-26 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=159392

Telesto  changed:

   What|Removed |Added

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

--- Comment #2 from Telesto  ---


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

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

[Bug 159386] Selecting all in a certain table causes assert in SfxPoolItem::SetWhich with a debug build

2024-01-26 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=159386

Telesto  changed:

   What|Removed |Added

 CC||tele...@surfxs.nl

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

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

[Bug 141773] Autocorrection for all languages doesn't work anymore

2024-01-26 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=141773

Stéphane Guillou (stragu)  changed:

   What|Removed |Added

   Severity|normal  |major
   Hardware|x86-64 (AMD64)  |All
  Regression By||Julien Nabet

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

[Bug 84129] SIDEBAR: Cell appearance border line styles not previewed correctly

2024-01-26 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=84129

Stéphane Guillou (stragu)  changed:

   What|Removed |Added

   Hardware|Other   |All
 CC||stephane.guillou@libreoffic
   ||e.org
   See Also||https://bugs.documentfounda
   ||tion.org/show_bug.cgi?id=15
   ||2558

--- Comment #10 from Stéphane Guillou (stragu) 
 ---
I could reproduce for Thick (2.25 pt) but not for Extra Thick (4.50 pt) in a
recent trunk build:

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

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

[Bug 152558] Calc Cell Borders are inconsistent with the drop-down graphic selector. Also, No help page for manual definitions

2024-01-26 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=152558

Stéphane Guillou (stragu)  changed:

   What|Removed |Added

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

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

[Bug 159395] LanguageTool Server: use correct default URL, when username/API key set

2024-01-26 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=159395

Stéphane Guillou (stragu)  changed:

   What|Removed |Added

 Blocks||155314
 Status|UNCONFIRMED |NEW
 CC||stephane.guillou@libreoffic
   ||e.org
Version|unspecified |7.4.0.0 beta1+
 Ever confirmed|0   |1

--- Comment #1 from Stéphane Guillou (stragu) 
 ---
Yes please!


Referenced Bugs:

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

[Bug 155314] [META] LanguageTool integration

2024-01-26 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=155314

Stéphane Guillou (stragu)  changed:

   What|Removed |Added

 Depends on||159395


Referenced Bugs:

https://bugs.documentfoundation.org/show_bug.cgi?id=159395
[Bug 159395] LanguageTool Server: use correct default URL, when username/API
key set
-- 
You are receiving this mail because:
You are the assignee for the bug.

[Bug 152558] Calc Cell Borders are inconsistent with the drop-down graphic selector. Also, No help page for manual definitions

2024-01-26 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=152558

Stéphane Guillou (stragu)  changed:

   What|Removed |Added

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

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

[Bug 146466] Inconsistent choices of borders between toolbar and sidebar

2024-01-26 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=146466

Stéphane Guillou (stragu)  changed:

   What|Removed |Added

   See Also||https://bugs.documentfounda
   ||tion.org/show_bug.cgi?id=15
   ||2558,
   ||https://bugs.documentfounda
   ||tion.org/show_bug.cgi?id=14
   ||4938

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

[Bug 144938] Writer table border styles offered are different in the toolbar button vs. Table Properties dialog

2024-01-26 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=144938

Stéphane Guillou (stragu)  changed:

   What|Removed |Added

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

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

[Bug 159395] New: LanguageTool Server: use correct default URL, when username/API key set

2024-01-26 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=159395

Bug ID: 159395
   Summary: LanguageTool Server: use correct default URL, when
username/API key set
   Product: LibreOffice
   Version: unspecified
  Hardware: All
OS: All
Status: UNCONFIRMED
  Keywords: difficultyBeginner, easyHack, skillCpp
  Severity: normal
  Priority: medium
 Component: Linguistic
  Assignee: libreoffice-bugs@lists.freedesktop.org
  Reporter: mikekagan...@hotmail.com
CC: so...@libreoffice.org

In Options->Languages and Locales->LanguageTool Server, the "Base URL" box has
the "Leave this field empty to use the free version" hint. Sometimes, people
have difficulties finding the correct URL for their paid account: see e.g.
https://ask.libreoffice.org/t/languagetool-premium-not-working/101101/11.

It is reasonable to use the correct automatic URL in case when the Username /
API key fields are set: https://api.languagetoolplus.com/v2.

Code pointer: see LANGUAGETOOL_DEFAULT_URL in
https://opengrok.libreoffice.org/xref/core/cui/source/options/optlanguagetool.cxx?r=16737129.

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

[Bug 76005] UI missing to set document properties: "TabsRelativeToIndent", "TabOverMargin"

2024-01-26 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=76005

Mike Kaganski  changed:

   What|Removed |Added

   Keywords||difficultyInteresting,
   ||easyHack, skillCpp

--- Comment #10 from Mike Kaganski  ---
A commit that adds adds another compatibility option to the dialog:
https://gerrit.libreoffice.org/c/core/+/162635

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

[Bug 153138] UI missing for IgnoreTabsAndBlanksForLineCalculation compatibility setting

2024-01-26 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=153138

Mike Kaganski  changed:

   What|Removed |Added

   Keywords||difficultyInteresting,
   ||easyHack, skillCpp

--- Comment #2 from Mike Kaganski  ---
A commit that adds adds another compatibility option to the dialog:
https://gerrit.libreoffice.org/c/core/+/162635

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

[Bug 126513] BackgroundParaOverDrawings missing in compatibility settings

2024-01-26 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=126513

Mike Kaganski  changed:

   What|Removed |Added

   Keywords||difficultyMedium, easyHack,
   ||skillCpp

--- Comment #11 from Mike Kaganski  ---
A commit that adds adds another compatibility option to the dialog:
https://gerrit.libreoffice.org/c/core/+/162635

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

[Bug 93727] Date Literal should be supported

2024-01-26 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=93727

--- Comment #22 from Luv Sharma  ---
Where can I run the given codes 1 and 2 as given in reproducible steps to
observe the behaviour?

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

[Bug 109195] [META] DOCX (OOXML) Footnote and Endnote bugs and enhancements

2024-01-26 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=109195
Bug 109195 depends on bug 159382, which changed state.

Bug 159382 Summary: DOCX import: Large space between footnote number and 
following text, when paragraph has hanging indent
https://bugs.documentfoundation.org/show_bug.cgi?id=159382

   What|Removed |Added

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

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

core.git: 2 commits - include/unotools officecfg/registry sw/inc sw/qa sw/source sw/uiconfig unotools/source writerfilter/source

2024-01-26 Thread Mike Kaganski (via logerrit)
 include/unotools/compatibility.hxx|1 
 officecfg/registry/schema/org/openoffice/Office/Compatibility.xcs |6 
 sw/inc/IDocumentSettingAccess.hxx |2 
 sw/qa/extras/odfexport/data/footnote_spacing_hanging_para.doc |binary
 sw/qa/extras/odfexport/data/footnote_spacing_hanging_para.docx|binary
 sw/qa/extras/odfexport/data/footnote_spacing_hanging_para.rtf |  209 
++
 sw/qa/extras/odfexport/odfexport2.cxx |   99 
 sw/source/core/doc/DocumentSettingManager.cxx |   12 
 sw/source/core/inc/DocumentSettingManager.hxx |1 
 sw/source/core/text/porfld.cxx|7 
 sw/source/filter/ww8/ww8par.cxx   |1 
 sw/source/ui/config/optcomp.cxx   |   19 
 sw/source/uibase/uno/SwXDocumentSettings.cxx  |   13 
 sw/uiconfig/swriter/ui/optcompatpage.ui   |1 
 unotools/source/config/compatibility.cxx  |2 
 writerfilter/source/dmapper/DomainMapper.cxx  |2 
 writerfilter/source/filter/WriterFilter.cxx   |1 
 17 files changed, 371 insertions(+), 5 deletions(-)

New commits:
commit 830a3894ac98179fb78d6f1fdb409a51faab0c95
Author: Mike Kaganski 
AuthorDate: Sat Jan 27 00:51:57 2024 +0600
Commit: Mike Kaganski 
CommitDate: Sat Jan 27 05:01:56 2024 +0100

tdf#159382: add NoSpaceAfterHangingFootnoteNumbering compat option to dialog

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

diff --git a/include/unotools/compatibility.hxx 
b/include/unotools/compatibility.hxx
index 9c2acefcf1d7..11f7d0dcfc57 100644
--- a/include/unotools/compatibility.hxx
+++ b/include/unotools/compatibility.hxx
@@ -62,6 +62,7 @@ class SvtCompatibilityEntry
 SubtractFlysAnchoredAtFlys,
 EmptyDbFieldHidesPara,
 UseVariableWidthNBSP,
+NoSpaceAfterHangingFootnoteNumbering,
 
 /// special entry: optcomp.cxx converts the other values to
 /// integers but not this one because it doesn't have its own
diff --git a/officecfg/registry/schema/org/openoffice/Office/Compatibility.xcs 
b/officecfg/registry/schema/org/openoffice/Office/Compatibility.xcs
index 0d79fb5340f5..118a4c30108e 100644
--- a/officecfg/registry/schema/org/openoffice/Office/Compatibility.xcs
+++ b/officecfg/registry/schema/org/openoffice/Office/Compatibility.xcs
@@ -134,6 +134,12 @@
 
 false
   
+  
+
+  Do not add an extra space after number in footnotes with 
hanging first line
+
+false
+  
 
   
   
diff --git a/sw/source/core/doc/DocumentSettingManager.cxx 
b/sw/source/core/doc/DocumentSettingManager.cxx
index 5563b2f80b06..224618cb9cc0 100644
--- a/sw/source/core/doc/DocumentSettingManager.cxx
+++ b/sw/source/core/doc/DocumentSettingManager.cxx
@@ -138,6 +138,7 @@ sw::DocumentSettingManager::DocumentSettingManager(SwDoc 
)
 = 
aOptions.GetDefault(SvtCompatibilityEntry::Index::EmptyDbFieldHidesPara);
 mbUseVariableWidthNBSP
 = 
aOptions.GetDefault(SvtCompatibilityEntry::Index::UseVariableWidthNBSP);
+mbNoSpaceAfterHangingFootnoteNumbering = aOptions.GetDefault( 
SvtCompatibilityEntry::Index::NoSpaceAfterHangingFootnoteNumbering );
 }
 else
 {
diff --git a/sw/source/ui/config/optcomp.cxx b/sw/source/ui/config/optcomp.cxx
index 1393b2864d95..9d1c01190d80 100644
--- a/sw/source/ui/config/optcomp.cxx
+++ b/sw/source/ui/config/optcomp.cxx
@@ -103,7 +103,8 @@ static sal_uInt32 convertBools2Ulong_Impl
 bool _bMsWordCompTrailingBlanks,
 bool bSubtractFlysAnchoredAtFlys,
 bool bEmptyDbFieldHidesPara,
-bool bUseVariableWidthNBSP
+bool bUseVariableWidthNBSP,
+bool bNoSpaceAfterHangingFootnoteNumbering
 )
 {
 sal_uInt32 nRet = 0;
@@ -156,6 +157,9 @@ static sal_uInt32 convertBools2Ulong_Impl
 nSetBit = nSetBit << 1;
 if (bUseVariableWidthNBSP)
 nRet |= nSetBit;
+nSetBit = nSetBit << 1;
+if (bNoSpaceAfterHangingFootnoteNumbering)
+nRet |= nSetBit;
 
 return nRet;
 }
@@ -225,7 +229,9 @@ void SwCompatibilityOptPage::InitControls( const 
SfxItemSet& rSet )
 rEntry.getValue( 
SvtCompatibilityEntry::Index::MsWordTrailingBlanks ),
 rEntry.getValue( 
SvtCompatibilityEntry::Index::SubtractFlysAnchoredAtFlys ),
 rEntry.getValue( 
SvtCompatibilityEntry::Index::EmptyDbFieldHidesPara ),
-rEntry.getValue( 
SvtCompatibilityEntry::Index::UseVariableWidthNBSP ) );
+rEntry.getValue( 
SvtCompatibilityEntry::Index::UseVariableWidthNBSP ),
+rEntry.getValue( 

[Bug 159156] Enhancement request : Freeze Zoom as a global LibreOffice preference

2024-01-26 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=159156

QA Administrators  changed:

   What|Removed |Added

 Whiteboard|| QA:needsComment

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

[Bug 103170] [META] Notebookbar Contextual

2024-01-26 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=103170
Bug 103170 depends on bug 107423, which changed state.

Bug 107423 Summary: Contextual groups variant of the Notebookbar is supposed to 
work with main menu and sidebar
https://bugs.documentfoundation.org/show_bug.cgi?id=107423

   What|Removed |Added

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

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

[Bug 144938] Writer table border styles offered are different in the toolbar button vs. Table Properties dialog

2024-01-26 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=144938

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

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 134407] Too narrow preferences dialog

2024-01-26 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=134407

--- Comment #16 from QA Administrators  ---
Dear Leandro Martín Drudi,

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 159392] Crash: after selecting a floating table and clicking 'file' in menubar (mergedlo!SfxPoolItem::CloneSetWhich+0x25:)

2024-01-26 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=159392

QA Administrators  changed:

   What|Removed |Added

   Keywords||bibisectRequest

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

[Bug 159153] caught exception trying to find out if doc . is encrypted:

2024-01-26 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=159153

QA Administrators  changed:

   What|Removed |Added

 Whiteboard|| QA:needsComment

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

[Bug 107423] Contextual groups variant of the Notebookbar is supposed to work with main menu and sidebar

2024-01-26 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=107423

--- Comment #10 from QA Administrators  ---
Dear Heiko Tietze,

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 107423] Contextual groups variant of the Notebookbar is supposed to work with main menu and sidebar

2024-01-26 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=107423

QA Administrators  changed:

   What|Removed |Added

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

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

[Bug 156533] Links NOT All Functional

2024-01-26 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=156533

--- Comment #2 from QA Administrators  ---
Dear nik,

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 103183] Pasting text from OneNote 2010 fails, with 2013 and up pastes text as image by default

2024-01-26 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=103183

--- Comment #33 from QA Administrators  ---
Dear Matt,

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 156526] Crash

2024-01-26 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=156526

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

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 69977] freeze/crash when creating a diagram from many thousand cells

2024-01-26 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=69977

--- Comment #23 from QA Administrators  ---
Dear ibramlab,

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 146862] VIEWING: If document background is set to black, Formula remains black in Writer

2024-01-26 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=146862

--- Comment #12 from QA Administrators  ---
Dear Silex,

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 113050] FILEOPEN: PDF freezes Draw, one page, 19 KB file

2024-01-26 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=113050

Dave Gilbert  changed:

   What|Removed |Added

   Assignee|libreoffice-b...@lists.free |freedesk...@treblig.org
   |desktop.org |
 Status|NEW |ASSIGNED

--- Comment #23 from Dave Gilbert  ---
Getting there slowly; I have a modified wrapper on both sides enabling the
tiling call, and passing the tile to the other side.
With that in place the file loads OK, but without the offending hand!
Now, to build the structure from the imported data...

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

[Bug 159369] Cursor off screen at high document zoom level and high Gnome magnification (Wayland)

2024-01-26 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=159369

--- Comment #7 from Stéphane Guillou (stragu) 
 ---
Thank you for the analysis, Michael! Much appreciated.

(In reply to Michael Weghorn from comment #4)
> That one was indeed closed as fixed now, referring to the GNOME magnifier
> commit I mentioned earlier.
Does that mean that it is recommended to test this bug with GNOME 42.2 or
above?
https://gitlab.gnome.org/GNOME/gnome-shell/-/commit/cb0c4bd1c2c19645e4cd1be9733c22e8747b07d8

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

[Bug 159394] CALC Formatting For a Particular TEXT & HEIGHT, ONLY Formats Cells thar have an ENTRY….ALL Cells should be FORMATTED!!!!!

2024-01-26 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=159394

m_a_riosv  changed:

   What|Removed |Added

 Status|UNCONFIRMED |RESOLVED
 CC||miguelangelrv@libreoffice.o
   ||rg
 Resolution|--- |DUPLICATE

--- Comment #1 from m_a_riosv  ---
Already fixed.

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

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

[Bug 159392] Crash: after selecting a floating table and clicking 'file' in menubar (mergedlo!SfxPoolItem::CloneSetWhich+0x25:)

2024-01-26 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=159392

m_a_riosv  changed:

   What|Removed |Added

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

--- Comment #1 from m_a_riosv  ---
Reproducible
Version: 24.8.0.0.alpha0+ (X86_64) / LibreOffice Community
Build ID: 566bb271b8fe5882f24fef230e06c2af4ea12b33
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

Regression from
Version: 24.2.1.0.0+ (X86_64) / LibreOffice Community
Build ID: cafcc50570f9edaaebe74d2152bae5df1cc2edfe
CPU threads: 16; OS: Windows 10.0 Build 22631; UI render: Skia/Raster; VCL: win
Locale: es-ES (es_ES); UI: en-US
Calc: CL threaded

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

[Bug 159388] Sorting function doesn't remember that a) first row contains description for columns and b) the previously used sorting priority

2024-01-26 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=159388

m_a_riosv  changed:

   What|Removed |Added

 CC||miguelangelrv@libreoffice.o
   ||rg
 Resolution|--- |DUPLICATE
 Status|UNCONFIRMED |RESOLVED

--- Comment #3 from m_a_riosv  ---
You need to create a range Menu/Data/Define range, to keep the options for that
range.

https://help.libreoffice.org/latest/en-US/text/scalc/guide/database_define.html?=CALC=WIN

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

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

[Bug 108424] Sort of anonymous ranges is saved only once per spreadsheet, even if spreadsheet contains several sorted anonymous tables

2024-01-26 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=108424

m_a_riosv  changed:

   What|Removed |Added

 CC||sagit...@gmx.de

--- Comment #6 from m_a_riosv  ---
*** Bug 159388 has been marked as a duplicate of this bug. ***

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

[Bug 159394] New: CALC Formatting For a Particular TEXT & HEIGHT, ONLY Formats Cells thar have an ENTRY….ALL Cells should be FORMATTED!!!!!

2024-01-26 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=159394

Bug ID: 159394
   Summary: CALC Formatting For a Particular TEXT & HEIGHT, ONLY
Formats Cells thar have an ENTRY….ALL Cells should be
FORMATTED!
   Product: LibreOffice
   Version: 7.6.0.3 release
  Hardware: x86 (IA32)
OS: iOS
Status: UNCONFIRMED
  Severity: normal
  Priority: medium
 Component: Calc
  Assignee: libreoffice-bugs@lists.freedesktop.org
  Reporter: n...@grumpie.ca

Description:
Selecting ALL Cells [upper Left Square} & then FORMATTING for a Particular FONT
& SIZE, results in ONLY Cells with a Entry, being FORMATTED….Empty Cells RETAIN
the Original Format.

Steps to Reproduce:
1.SEE ABOVE
2.
3.

Actual Results:
SEE Above

Expected Results:
ALL Cell Should be FORMATTED


Reproducible: Always


User Profile Reset: Yes

Additional Info:
Format ALL Cells!

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

[Bug 159364] we couldn't read math ml tags with screen readers

2024-01-26 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=159364

--- Comment #3 from Michael Weghorn  ---
(In reply to V Stuart Foote from comment #1)
> Not clear if the MathML can be directly exposed to the Assistive Technology
> of Screen Readers, which themselves would need filters to read the MathML in
> a non-HTML5 context.

A quick `git grep -i mathml` in NVDA's source code suggests that there's some
specific handling for MathML for Word and other applications, e.g. [1] for
Word.

One way to expose MathML to the a11y layer (if there's an easy way to get a
MathML representation from within Math) might be to us an a11y object
attribute, similar to what's done for formulae in Calc (e.g. a "Formula" object
attribute with value "45+12" on a cell that contains such a formula).

(Object attributes are supported by at least IAccessible2 on Windows and AT-SPI
on Linux, though currently only Gtk 3/ATK provides the API to expose custom
attributes, s.a. discussion in tdf#158030 for more details and links to Gtk 4
issue and pending Qt Gerrit changes. Not sure about macOS, but from what I've
seen so far, the API seems more strongly typed/less flexible there.)

[1]
https://github.com/nvaccess/nvda/blob/e71916d0ff6fff3949507e625559b39f00f8f7ec/source/NVDAObjects/UIA/wordDocument.py#L148

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

[Bug 159351] FILEOPEN: prompted to save changes when no change was made on ODS file with multiline cell

2024-01-26 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=159351

--- Comment #1 from Henning  ---
My observations to reproduce:

1. create a document with one multiline cell and all other cells as singleline
2. save+exit
3. open document
4. change active cell by using the cursor-keys
5. the cell that was previously selected will be changed to multiline (on cell
exit)

The undo-list now has the entry "Attribute" for every cell-change without
specifying which attribute as changed.

Other occasions where this behavior appears include copy by Ctrl+c or closing
the document.

The cells are not changed to multiline when the selected cell is changed by
using the mouse.


>From my point of view the severity should be increased because this modifies
the data unintentionally.


Version: 24.2.0~rc2 from Debian-repository (4:24.2.0~rc2-2)

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

[Bug 159331] sheet window does not refresh properly after touchpad scroll

2024-01-26 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=159331

m_a_riosv  changed:

   What|Removed |Added

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

--- Comment #14 from m_a_riosv  ---
Please understand that not what is fine for you, it's fine for others, by
having the options, makes possible to use the better for everyone.

BTW sometimes, update graphics drivers from vendor, solves issues about them.

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

core.git: sw/inc sw/source

2024-01-26 Thread Michael Weghorn (via logerrit)
 sw/inc/accmap.hxx|7 ++-
 sw/source/core/access/accmap.cxx |   17 ++---
 2 files changed, 8 insertions(+), 16 deletions(-)

New commits:
commit 2cedb1a19ad605df4e148589e9027512e4dd9265
Author: Michael Weghorn 
AuthorDate: Fri Jan 26 18:37:11 2024 +0100
Commit: Michael Weghorn 
CommitDate: Fri Jan 26 22:12:22 2024 +0100

sw a11y: Return MapMode instead of using out param

Change-Id: I116e006e3fcdb3c6993adf7c99860bdd952af6e0
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/162633
Tested-by: Jenkins
Reviewed-by: Michael Weghorn 

diff --git a/sw/inc/accmap.hxx b/sw/inc/accmap.hxx
index 9daf15b8ae07..d99d8dc16c7a 100644
--- a/sw/inc/accmap.hxx
+++ b/sw/inc/accmap.hxx
@@ -297,12 +297,9 @@ private:
 input parameter - constant reference to point to determine the mapping
 mode adjustments for page/print preview.
 
-@param _orMapMode
-output parameter - reference to the mapping mode, which is determined
-by the method
+@return mapping mode, which is determined by the method
 */
-void GetMapMode( const Point& _rPoint,
- MapMode& _orMapMode ) const;
+MapMode GetMapMode(const Point& _rPoint) const;
 public:
 virtual bool IsDocumentSelAll() override;
 };
diff --git a/sw/source/core/access/accmap.cxx b/sw/source/core/access/accmap.cxx
index aa34fdf2d568..704dac005566 100644
--- a/sw/source/core/access/accmap.cxx
+++ b/sw/source/core/access/accmap.cxx
@@ -2949,8 +2949,7 @@ Point SwAccessibleMap::LogicToPixel( const Point& rPoint 
) const
 Point aPoint = o3tl::toTwips( rPoint, o3tl::Length::mm100 );
 if (const vcl::Window* pWin = GetShell()->GetWin())
 {
-MapMode aMapMode;
-GetMapMode( aPoint, aMapMode );
+const MapMode aMapMode = GetMapMode(aPoint);
 aPoint = pWin->LogicToPixel( aPoint, aMapMode );
 aPoint = Point(pWin->OutputToAbsoluteScreenPixel( aPoint ));
 }
@@ -2963,8 +2962,7 @@ Size SwAccessibleMap::LogicToPixel( const Size& rSize ) 
const
 Size aSize( o3tl::toTwips( rSize, o3tl::Length::mm100 ) );
 if (const OutputDevice* pWin = GetShell()->GetWin()->GetOutDev())
 {
-MapMode aMapMode;
-GetMapMode( Point(0,0), aMapMode );
+const MapMode aMapMode = GetMapMode(Point(0, 0));
 aSize = pWin->LogicToPixel( aSize, aMapMode );
 }
 
@@ -3073,8 +3071,7 @@ Point SwAccessibleMap::PixelToCore( const Point& rPoint ) 
const
 Point aPoint;
 if (const OutputDevice* pWin = GetShell()->GetWin()->GetOutDev())
 {
-MapMode aMapMode;
-GetMapMode( rPoint, aMapMode );
+const MapMode aMapMode = GetMapMode(rPoint);
 aPoint = pWin->PixelToLogic( rPoint, aMapMode );
 }
 return aPoint;
@@ -3118,8 +3115,7 @@ tools::Rectangle SwAccessibleMap::CoreToPixel( const 
SwRect& rRect ) const
 tools::Rectangle aRect;
 if (const OutputDevice* pWin = GetShell()->GetWin()->GetOutDev())
 {
-MapMode aMapMode;
-GetMapMode( rRect.TopLeft(), aMapMode );
+const MapMode aMapMode = GetMapMode(rRect.TopLeft());
 aRect = pWin->LogicToPixel( rRect.SVRect(), aMapMode );
 
 tools::Rectangle aTmpRect = pWin->PixelToLogic( aRect, aMapMode );
@@ -3137,8 +3133,7 @@ tools::Rectangle SwAccessibleMap::CoreToPixel( const 
SwRect& rRect ) const
 output device for mapping logic document positions to page preview window
 positions and vice versa and doesn't take care to recover its changes.
 */
-void SwAccessibleMap::GetMapMode( const Point& _rPoint,
-  MapMode& _orMapMode ) const
+MapMode SwAccessibleMap::GetMapMode(const Point& _rPoint) const
 {
 MapMode aMapMode = GetShell()->GetWin()->GetMapMode();
 if( GetShell()->IsPreview() )
@@ -3146,7 +3141,7 @@ void SwAccessibleMap::GetMapMode( const Point& _rPoint,
 assert(mpPreview != nullptr);
 mpPreview->AdjustMapMode( aMapMode, _rPoint );
 }
-_orMapMode = aMapMode;
+return aMapMode;
 }
 
 Size SwAccessibleMap::GetPreviewPageSize(sal_uInt16 const nPreviewPageNum) 
const


[Bug 108746] [META] Page number field bugs and enhancements

2024-01-26 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=108746

BogdanB  changed:

   What|Removed |Added

 Depends on||159328


Referenced Bugs:

https://bugs.documentfoundation.org/show_bug.cgi?id=159328
[Bug 159328] Page number field shows up like plain text (no grayish background)
-- 
You are receiving this mail because:
You are the assignee for the bug.

[Bug 140544] FORMATTING: Some existing writer paragraph styles may be more efficiently grouped in a new hierarchy named "Letter"

2024-01-26 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=140544

--- Comment #8 from cpmonger  ---
Hello!

May I please request a review of this issue (enhancement)? It does not appear
to be either implemented or WONTFIX, thus not technically resolved as "FIXED."

(Ubuntu package version: 4:7.5.9.2-0ubuntu023.04.1)

Please also consider that there are other style hierarchy issues, as mentioned
in the issue description, paragraph 7. Should this enhancement be accepted and
implemented I would be willing to help propose, research, draft, and follow a
deeper review of Writer style hierarchies. Unfortunately, I am not skilled in
code work.

Thank you.

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

[Bug 159294] Not all active Page Styles show in Applied Styles filter

2024-01-26 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=159294

BogdanB  changed:

   What|Removed |Added

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

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

[Bug 159393] Writer shutdown after a Ctrl-Enter for new page in document

2024-01-26 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=159393

BogdanB  changed:

   What|Removed |Added

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

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

[Bug 159393] Writer shutdown after a Ctrl-Enter for new page in document

2024-01-26 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=159393

BogdanB  changed:

   What|Removed |Added

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

--- Comment #1 from BogdanB  ---
When trying to bibisect another bug but with a similar task (Ctrl+Enter), I
notice the same behavior.

In my case on linux, with 24.2
linux-64-24.2

See: https://bugs.documentfoundation.org/show_bug.cgi?id=159294 comment 2.

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

[Bug 159386] Selecting all in a certain table causes assert in SfxPoolItem::SetWhich with a debug build

2024-01-26 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=159386

Julien Nabet  changed:

   What|Removed |Added

 CC||armin.le.gr...@me.com,
   ||serval2...@yahoo.fr
 Status|UNCONFIRMED |NEW
 Ever confirmed|0   |1

--- Comment #1 from Julien Nabet  ---
On pc Debian x86-64 with master sources updated today, I could reproduce this.

Armin: one for you?

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

[Bug 159366] List styles add paragraph direct formatting on loading Writer document

2024-01-26 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=159366

BogdanB  changed:

   What|Removed |Added

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


Referenced Bugs:

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

[Bug 107832] [META] Writer list style bugs and enhancements

2024-01-26 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=107832

BogdanB  changed:

   What|Removed |Added

 Depends on||159366


Referenced Bugs:

https://bugs.documentfoundation.org/show_bug.cgi?id=159366
[Bug 159366] List styles add paragraph direct formatting on loading Writer
document
-- 
You are receiving this mail because:
You are the assignee for the bug.

[Bug 109195] [META] DOCX (OOXML) Footnote and Endnote bugs and enhancements

2024-01-26 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=109195

BogdanB  changed:

   What|Removed |Added

 Depends on||159382


Referenced Bugs:

https://bugs.documentfoundation.org/show_bug.cgi?id=159382
[Bug 159382] DOCX import: Large space between footnote number and following
text, when paragraph has hanging indent
-- 
You are receiving this mail because:
You are the assignee for the bug.

core.git: desktop/Executable_soffice_bin.mk desktop/util

2024-01-26 Thread Patrick Luby (via logerrit)
 desktop/Executable_soffice_bin.mk  |   23 +++
 desktop/util/macos/__objc_fork_ok_data.txt |binary
 2 files changed, 23 insertions(+)

New commits:
commit c6652e280b0690497abf27380dd064898f91db32
Author: Patrick Luby 
AuthorDate: Fri Jan 26 12:19:17 2024 -0500
Commit: Patrick Luby 
CommitDate: Fri Jan 26 21:44:05 2024 +0100

tdf#152524 Add a __objc_fork_ok data section for Mac Intel executable

This attempts to fix a particularly difficult to debug crash due to
memory corruption when gpgme tries to fork and exec a gpg command.
For more background, see the following bug comment:

  https://bugs.documentfoundation.org/show_bug.cgi?id=152524#c39

This data section is only added in Mac Intel builds as it is a
controversial approach and I have not seen any reports of this bug
on Mac Silicon yet. So limit the fix only to Mac Intel in the hope
that this controversial approach will automatically phase itself
out when Apple eventually stops releasing new versions of macOS
for Mac Intel.

Note: the Objective C runtime doesn't appear to check the value of
this data section, but set it to 1 in case that changes in the future.

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

diff --git a/desktop/Executable_soffice_bin.mk 
b/desktop/Executable_soffice_bin.mk
index c2d811c2e86c..fbdf07a5e531 100644
--- a/desktop/Executable_soffice_bin.mk
+++ b/desktop/Executable_soffice_bin.mk
@@ -58,4 +58,27 @@ $(eval $(call gb_Executable_add_ldflags,soffice_bin,\
 
 endif
 
+ifeq ($(OS),MACOSX)
+ifeq ($(CPUNAME),X86_64)
+
+# tdf#152524 Add a __objc_fork_ok data section for Mac Intel executable
+# This attempts to fix a particularly difficult to debug crash due to
+# memory corruption when gpgme tries to fork and exec a gpg command.
+# For more background, see the following bug comment:
+#   https://bugs.documentfoundation.org/show_bug.cgi?id=152524#c39
+# This data section is only added in Mac Intel builds as it is a
+# controversial approach and I have not seen any reports of this bug
+# on Mac Silicon yet. So limit the fix only to Mac Intel in the hope
+# that this controversial approach will automatically phase itself
+# out when Apple eventually stops releasing new versions of macOS
+# for Mac Intel.
+# Note: the Objective C runtime doesn't appear to check the value of
+# this data section, but set it to 1 in case that changes in the future.
+$(eval $(call gb_Executable_add_ldflags,soffice_bin,\
+-sectcreate __DATA __objc_fork_ok 
$(SRCDIR)/desktop/util/macos/__objc_fork_ok_data.txt \
+))
+
+endif
+endif
+
 # vim: set ts=4 sw=4 et:
diff --git a/desktop/util/macos/__objc_fork_ok_data.txt 
b/desktop/util/macos/__objc_fork_ok_data.txt
new file mode 100644
index ..f66c9cf4c967
Binary files /dev/null and b/desktop/util/macos/__objc_fork_ok_data.txt differ


[Bug 158112] Sidebar pane shortcuts conflict with Alt+NumPad input (comment 5, comment 9)

2024-01-26 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=158112

V Stuart Foote  changed:

   What|Removed |Added

 CC||j...@vansomeren.co.uk

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

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

[Bug 159389] UI. Recently I can no longer use the Alt key and four digits to enter an ASCII character

2024-01-26 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=159389

V Stuart Foote  changed:

   What|Removed |Added

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

--- Comment #1 from V Stuart Foote  ---
Thanks for filing but please review the cause and solution on the duplicate
bug.

Alt + Numpad code entry will be restored/enhanced at the 24.2 release. Both the
3-digit OEM flavor and the Windows 4-digit flavor you note. Enhanced now to
offer the full Unicode SMB (via decimal values) as Alt + codes via the keyboard
Numpad. While the  + keyboard numbers will deliver the Sidebar short cuts.

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

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

[Bug 91739] nvda can not read documents from top to bottom.

2024-01-26 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=91739

--- Comment #19 from V Stuart Foote  ---
(In reply to QA Administrators from comment #18)

This is still an issue, no change supporting structural navigation by page top
to bottom with current release or on master. NVDA screen reader exhausts buffer
and stalls.

Version: 7.6.4.1 (X86_64) / LibreOffice Community
Build ID: e19e193f88cd6c0525a17fb7a176ed8e6a3e2aa1
CPU threads: 8; OS: Windows 10.0 Build 19045; UI render: Skia/Vulkan; VCL: win
Locale: en-US (en_US); UI: en-US
Calc: CL threaded

or

Version: 24.8.0.0.alpha0+ (X86_64) / LibreOffice Community
Build ID: 566bb271b8fe5882f24fef230e06c2af4ea12b33
CPU threads: 8; OS: Windows 10.0 Build 19045; UI render: Skia/Vulkan; VCL: win
Locale: en-US (en_US); UI: en-US
Calc: CL threaded

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

[Bug 159391] Libreoffice Writer crashes when changing the Area of a Shape

2024-01-26 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=159391

--- Comment #2 from ro...@rogercalvert.me.uk ---
I have confirmed that this bug also exists in Draw, including Safe Mode.

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

[Bug 159393] New: Writer shutdown after a Ctrl-Enter for new page in document

2024-01-26 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=159393

Bug ID: 159393
   Summary: Writer shutdown after a Ctrl-Enter for new page in
document
   Product: LibreOffice
   Version: 7.5.7.1 release
  Hardware: x86-64 (AMD64)
OS: Windows (All)
Status: UNCONFIRMED
  Severity: normal
  Priority: medium
 Component: Writer
  Assignee: libreoffice-bugs@lists.freedesktop.org
  Reporter: fauln...@gmail.com

Description:
While working in a Writer document and attempting to press Ctrl-Enter to create
a page break, Libre Office presents a screen stating it encountered an error
and would I like to Debug or Close Program. This happens regularly. I will try
to use a menu option next time to see if the problem continues.

Steps to Reproduce:
1.Create document using Writer
2.Type some dummy words. I happen to be one line below a Bulleted list
3.Press Ctrl-Enter to create page break. My assumption is Writer has same
Microsoft functionality

Actual Results:
On my other monitor I receive a message box stating Libre Office has
encountered an error. I am to choose whether to Debug or Close Program.  Libre
Office does not respond to me trying to click on Save or other menu options -
total lockup.

Expected Results:
New page with items below where my cursor is located to be moved to the top of
a new page.


Reproducible: Always


User Profile Reset: No

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

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

[Bug 159197] Font becomes bold when applying highlighting to a table with track changes ON

2024-01-26 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=159197

--- Comment #3 from Telesto  ---
(In reply to Buovjaga from comment #2)
> I was guessing the file would be attachment 191950 [details], but maybe not
> as I can't reproduce. So you could attach the test document :)

yes, that's the file, indeed. I have to re-check. I couldn't reproduce it on
the fly. LO is quite unstable at this point: bug 159392 (probably caused by the
pool refactor)

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

[Bug 159392] New: Crash: after selecting a floating table and clicking 'file' in menubar (mergedlo!SfxPoolItem::CloneSetWhich+0x25:)

2024-01-26 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=159392

Bug ID: 159392
   Summary: Crash: after selecting a floating table and clicking
'file' in menubar
(mergedlo!SfxPoolItem::CloneSetWhich+0x25:)
   Product: LibreOffice
   Version: 24.8.0.0 alpha0+ Master
  Hardware: All
OS: All
Status: UNCONFIRMED
  Severity: normal
  Priority: medium
 Component: Writer
  Assignee: libreoffice-bugs@lists.freedesktop.org
  Reporter: tele...@surfxs.nl

Description:
Crash: after selecting a floating table and clicking 'file' in menubar

Steps to Reproduce:
1. Open attachment 191950 (bug 159195)
2. Hoover over the top of the table (black arrow appears)
3. left Click to select
4. Left click on 'File' in the menubar


Actual Results:
Crash

Expected Results:
No crash


Reproducible: Always


User Profile Reset: No

Additional Info:
Version: 24.8.0.0.alpha0+ (X86_64) / LibreOffice Community
Build ID: 566bb271b8fe5882f24fef230e06c2af4ea12b33
CPU threads: 4; OS: Windows 6.3 Build 9600; UI render: Skia/Raster; VCL: win
Locale: nl-NL (nl_NL); UI: en-US
Calc: CL threaded

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

[Bug 159391] Libreoffice Writer crashes when changing the Area of a Shape

2024-01-26 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=159391

Xisco Faulí  changed:

   What|Removed |Added

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

--- Comment #1 from Xisco Faulí  ---
it looks like a duplicate of bug 157203

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

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

[Bug 157203] CRASH when reset Drawing Background Color to NONE (with tabbed interface active)

2024-01-26 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=157203

Xisco Faulí  changed:

   What|Removed |Added

 CC||ro...@rogercalvert.me.uk

--- Comment #13 from Xisco Faulí  ---
*** Bug 159391 has been marked as a duplicate of this bug. ***

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

[Bug 136897] Convergence check in iteration prevents lots of uses of iteration (anti-feature)

2024-01-26 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=136897

--- Comment #13 from hardcoder  ---
(In reply to LizaVersy from comment #12)
> Thanks for reporting this issue.
> A new major release of LibreOffice is available since this bug was reported.
> Could you please try to reproduce it with the latest version of LibreOffice
> from https://litaviser.com/
> I have set the bug's status to 'NEEDINFO'. Please change it back to
> 'UNCONFIRMED' if the bug is still present in the latest version.
litaviser.com? I visited the site, and looks like an empty landing site
offering itself for sale (possibly expired). I have LO 24.2.0.2 on my Win11
laptop, downloaded from
https://downloadarchive.documentfoundation.org/libreoffice/old/ .

Short answer: nothing changed, except for a subtle behavior regarding iterated
strings (see below).

Revising bug claims:
> - Err:523 hiding the results (anti-feature).
Still there, whenever Calc judges the variation is too large, a simple but
limiting "convergence" check that MS Excel and other software don't have.

> - For strings, Err:523 when it grows or shrinks in length, only not when the 
> length doesn't vary. String content seems to be irrelevant in this aspect.
When doing iterated string concatenation, now sometimes Err:523 sticks and
hides the result even when the added string is blank and the accumulated string
isn't growing anymore (worse than before). But if you go to Options dialog and
change the "Minimum change" field to whatever else, Err:523 is a string cell
gets inhibited in case the value is not changing (head-scratcher).

> - For numbers, the number of iterations is 3 at the first time, then 2 
> (except if the number of iterations is set to 1).
Still there, apparently like before.

> - When the formula is NOT converging, the correct number of iterations (set 
> in Options) is applied (this can't be directly seen; only when the value is 
> not changing anymore).
Still there, apparently like before.

> - All the iteration steps are calculated at a time for a cell, then for other 
> cell, and so on (incompatible behavior). In MS Excel, an iteration is 
> calculated for all cells (apparently even those in other workbooks, as long 
> as they are open), then another iteration, etc. (The Excel behavior is more 
> useful IMHO.)
Still there. You can confirm that with:
A1: 0
A2: =A2+A1
A3: =A3+A2
Always take note of the value of A3 before recalc'ing. Then change A1 to 1; A2
will change a repeated number of times, all BEFORE updating A3 with
intermediate values of A2. Only later, A3 is updated based on the last value of
A2. MS Excel has a different behaviour, like I said.

> Even another cell referencing the value (e.g. =A2) also splashes Err:523.
Still there, apparently like before.

Also: In Calc, iterative cells are kind of "non-volatile"; if you simply throw
a recalc, they are not updated unless selected. If you do a "recalc hard", they
are all updated. (Same behaviour as before.)


Version: 24.2.0.2 (X86_64) / LibreOffice Community
Build ID: b1fd3a6f0759c6f806568e15c957f97194bbec8f
CPU threads: 8; OS: Windows 10.0 Build 22621; UI render: Skia/Raster; VCL: win
Locale: en-US (C); UI: en-US
Calc: threaded

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

[Bug 159196] Deleting a column of a floating table with Track changes ON and show OFF deletes the whole table and no restore with undo

2024-01-26 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=159196

Telesto  changed:

   What|Removed |Added

 Resolution|--- |FIXED
   See Also||https://bugs.documentfounda
   ||tion.org/show_bug.cgi?id=15
   ||9107
 Status|NEW |RESOLVED

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

[Bug 83946] [META] Tracking changes issues

2024-01-26 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=83946
Bug 83946 depends on bug 159196, which changed state.

Bug 159196 Summary: Deleting a column of a floating table with Track changes ON 
and show OFF deletes the whole table and no restore with undo
https://bugs.documentfoundation.org/show_bug.cgi?id=159196

   What|Removed |Added

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

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

[Bug 159195] Undo doesn't restore deletion of floating table with Track changes ON and show OFF

2024-01-26 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=159195

Telesto  changed:

   What|Removed |Added

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

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

[Bug 159331] sheet window does not refresh properly after touchpad scroll

2024-01-26 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=159331

--- Comment #13 from Phil  ---
worked pretty hard. seems to be definite.


Tried clicking Skia and force Skia and deselect Skia so the force skia is
checked and grayed out and Skia is unchecked.

result: problem persisted, seems horizontal is the problem. Again.  2finger
swipe sheet to the right and then to the left makes all rows above the row
above the focused cell does not return to the correct columns.

deselecting Skia and the force skia option does not cure problem


selecting SKia and unchecking 'force SKIA' sub-option fixes the problem

unless there is some other reason for having the force Skia option, like maybe
in the other LibreOffice modules then I say remove that option from next
release

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

core.git: chart2/source

2024-01-26 Thread Justin Luth (via logerrit)
 chart2/source/view/charttypes/PieChart.cxx |7 +--
 1 file changed, 5 insertions(+), 2 deletions(-)

New commits:
commit 87facad88d565e8e9fe21d04897058cca0ea55cd
Author: Justin Luth 
AuthorDate: Fri Jan 26 10:46:37 2024 -0500
Commit: Justin Luth 
CommitDate: Fri Jan 26 19:58:20 2024 +0100

tdf#134121 pie chart2: fix missing leaderLines at top/bottom of 3D ovals

Yeah, it took me a while to clue in that this is no longer
a circle, so we can't apply circle logic to it any more.

Change-Id: I00f8b95cc75311342b9abd8c522ed06ca343a566
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/162630
Reviewed-by: Justin Luth 
Tested-by: Jenkins

diff --git a/chart2/source/view/charttypes/PieChart.cxx 
b/chart2/source/view/charttypes/PieChart.cxx
index 68e65b15d949..b9dd0517cf1f 100644
--- a/chart2/source/view/charttypes/PieChart.cxx
+++ b/chart2/source/view/charttypes/PieChart.cxx
@@ -520,11 +520,14 @@ void PieChart::createTextLabelShape(
 else if (nY1 > aRect.getMaxY())
 nY2 = aRect.getMaxY();
 
-sal_Int32 nSquaredDistanceFromOrigin
+const sal_Int32 nLabelSquaredDistanceFromOrigin
 = (nX2 - aOrigin.X) * (nX2 - aOrigin.X) + (nY2 - aOrigin.Y) * 
(nY2 - aOrigin.Y);
+// can't use fSquaredPieRadius for 3D charts, since no longer a 
true circle
+const sal_Int32 nPieEdgeSquaredDistanceFromOrigin
+= (nX1 - aOrigin.X) * (nX1 - aOrigin.X) + (nY1 - aOrigin.Y) * 
(nY1 - aOrigin.Y);
 
 // tdf#138018 Don't show leader line when custom positioned data 
label is inside pie chart
-if (nSquaredDistanceFromOrigin > fSquaredPieRadius)
+if (nLabelSquaredDistanceFromOrigin > 
nPieEdgeSquaredDistanceFromOrigin)
 {
 //when the line is very short compared to the page size don't 
create one
 ::basegfx::B2DVector aLength(nX1 - nX2, nY1 - nY2);


[Bug 146756] FILEOPEN PPTX: labels of pie chart wrap much too aggressively (compared to 365) as well as too conservatively

2024-01-26 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=146756

--- Comment #7 from Justin L  ---
Created attachment 192188
  --> https://bugs.documentfoundation.org/attachment.cgi?id=192188=edit
piechartformat_mso2010.pdf: not particularly great in earlier versions of MS
either.

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

[Bug 34142] Calc language identification should be similar to Writer's

2024-01-26 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=34142

--- Comment #15 from Commit Notification 
 ---
Henry Castro committed a patch related to this issue.
It has been pushed to "master":

https://git.libreoffice.org/core/commit/966f075a332b38a2689dad317d5d3c3fa61a1efb

tdf#34142: update status language after the cell format language change

It will be available in 24.8.0.

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

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

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

[Bug 159391] New: Libreoffice Writer crashes when changing the Area of a Shape

2024-01-26 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=159391

Bug ID: 159391
   Summary: Libreoffice Writer crashes when changing the Area of a
Shape
   Product: LibreOffice
   Version: 7.5.9.2 release
  Hardware: x86-64 (AMD64)
OS: Windows (All)
Status: UNCONFIRMED
  Severity: normal
  Priority: medium
 Component: Writer
  Assignee: libreoffice-bugs@lists.freedesktop.org
  Reporter: ro...@rogercalvert.me.uk

Description:
Writer crashes when the Area of a shape is changed from the default Colour to
None, Gradient or Image

Steps to Reproduce:
1.Open Writer
2.Create a shape - for example a circle
3.Right click on the shape and select Area
4.On the options, click on None

Actual Results:
Writer crashes

Expected Results:
The area would be cleared


Reproducible: Always


User Profile Reset: Yes

Additional Info:
Started happening consistently a few days ago, but it may be some months since
I last used this option.
Discovered on 7.5.7.1, continues on 7.1.9.2

Confirmed in Safe Mode on both versions

Version: 7.5.9.2 (X86_64) / LibreOffice Community
Build ID: cdeefe45c17511d326101eed8008ac4092f278a9
CPU threads: 8; OS: Windows 10.0 Build 22621; UI render: Skia/Raster; VCL: win
Locale: en-GB (en_GB); UI: en-GB
Calc: threaded

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

core.git: framework/source sc/source

2024-01-26 Thread Henry Castro (via logerrit)
 framework/source/uielement/langselectionstatusbarcontroller.cxx |5 -
 sc/source/ui/docshell/docsh4.cxx|   45 
++
 2 files changed, 33 insertions(+), 17 deletions(-)

New commits:
commit 64e1a5916367644ad3883a24ab1630d1340603b3
Author: Henry Castro 
AuthorDate: Wed Jan 17 16:25:41 2024 -0400
Commit: Henry Castro 
CommitDate: Fri Jan 26 19:41:14 2024 +0100

tdf#127856: fix setting "None" in cell format language

Change-Id: I94dc0b1e7f0a52e8fb6da1f9b80456cec696a727
Signed-off-by: Henry Castro 
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/162244
Tested-by: Jenkins
Reviewed-by: Caolán McNamara 

diff --git a/framework/source/uielement/langselectionstatusbarcontroller.cxx 
b/framework/source/uielement/langselectionstatusbarcontroller.cxx
index 2d56c4186883..f5730ae7ee54 100644
--- a/framework/source/uielement/langselectionstatusbarcontroller.cxx
+++ b/framework/source/uielement/langselectionstatusbarcontroller.cxx
@@ -190,7 +190,10 @@ void LangSelectionStatusbarController::LangMenu(
 }
 else
 {
-xPopupMenu->insertItem( MID_LANG_DEF_NONE,  
FwkResId(STR_LANGSTATUS_NONE), 0, MID_LANG_DEF_NONE );
+if (bCalc)
+xPopupMenu->insertItem( MID_LANG_SEL_NONE,  
FwkResId(STR_LANGSTATUS_NONE), 0, MID_LANG_SEL_NONE );
+else
+xPopupMenu->insertItem( MID_LANG_DEF_NONE,  
FwkResId(STR_LANGSTATUS_NONE), 0, MID_LANG_DEF_NONE );
 if ( sNone == m_aCurLang )
 xPopupMenu->checkItem( MID_LANG_DEF_NONE, true );
 xPopupMenu->insertItem( MID_LANG_DEF_RESET, 
FwkResId(STR_RESET_TO_DEFAULT_LANGUAGE), 0, MID_LANG_DEF_RESET );
diff --git a/sc/source/ui/docshell/docsh4.cxx b/sc/source/ui/docshell/docsh4.cxx
index 82b874391f38..34e69724742c 100644
--- a/sc/source/ui/docshell/docsh4.cxx
+++ b/sc/source/ui/docshell/docsh4.cxx
@@ -1301,28 +1301,41 @@ void ScDocShell::Execute( SfxRequest& rReq )
 if (bSelection)
 {
 ScTabViewShell* pViewShell = GetBestViewShell();
-const LanguageType nLangType = 
SvtLanguageTable::GetLanguageType(aLangText);
-const SvtScriptType nScriptType = 
SvtLanguageOptions::GetScriptTypeOfLanguage(nLangType);
-
 if (pViewShell)
 {
 const ScPatternAttr* pSelAttrs = 
pViewShell->GetSelectionPattern();
 if (pSelAttrs)
 {
 const SfxItemSet& rOldSet = 
pSelAttrs->GetItemSet();
+SfxItemPool* pItemPool = rOldSet.GetPool();
 auto pNewSet = 
std::make_shared(rOldSet);
 
-if (nScriptType == SvtScriptType::LATIN)
-pNewSet->Put(SvxLanguageItem(nLangType,
- 
rOldSet.GetPool()->GetWhich(SID_ATTR_CHAR_LANGUAGE)));
-if (nScriptType == SvtScriptType::COMPLEX)
-pNewSet->Put(SvxLanguageItem(nLangType,
- 
rOldSet.GetPool()->GetWhich(SID_ATTR_CHAR_CTL_LANGUAGE)));
-if (nScriptType == SvtScriptType::ASIAN)
-pNewSet->Put(SvxLanguageItem(nLangType,
- 
rOldSet.GetPool()->GetWhich(SID_ATTR_CHAR_CJK_LANGUAGE)));
-
+if (aLangText == "LANGUAGE_NONE")
+{
+pNewSet->Put(SvxLanguageItem(LANGUAGE_NONE,
+ 
pItemPool->GetWhich(SID_ATTR_CHAR_LANGUAGE)));
+pNewSet->Put(SvxLanguageItem(LANGUAGE_NONE,
+ 
pItemPool->GetWhich(SID_ATTR_CHAR_CJK_LANGUAGE)));
+pNewSet->Put(SvxLanguageItem(LANGUAGE_NONE,
+ 
pItemPool->GetWhich(SID_ATTR_CHAR_CTL_LANGUAGE)));
+}
+else
+{
+const LanguageType nLangType = 
SvtLanguageTable::GetLanguageType(aLangText);
+const SvtScriptType nScriptType =
+
SvtLanguageOptions::GetScriptTypeOfLanguage(nLangType);
+if (nScriptType == SvtScriptType::LATIN)
+pNewSet->Put(SvxLanguageItem(nLangType,
+ 
pItemPool->GetWhich(SID_ATTR_CHAR_LANGUAGE)));
+if (nScriptType == SvtScriptType::COMPLEX)
+pNewSet->Put(SvxLanguageItem(nLangType,
+   

[Bug 34142] Calc language identification should be similar to Writer's

2024-01-26 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=34142

--- Comment #14 from Commit Notification 
 ---
Henry Castro committed a patch related to this issue.
It has been pushed to "master":

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

tdf#34142: fix cell language status

It will be available in 24.8.0.

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

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

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

core.git: framework/source sc/source

2024-01-26 Thread Henry Castro (via logerrit)
 framework/source/uielement/langselectionstatusbarcontroller.cxx |5 
 sc/source/ui/docshell/docsh4.cxx|   11 
--
 2 files changed, 6 insertions(+), 10 deletions(-)

New commits:
commit 966f075a332b38a2689dad317d5d3c3fa61a1efb
Author: Henry Castro 
AuthorDate: Wed Jan 24 09:51:17 2024 -0400
Commit: Henry Castro 
CommitDate: Fri Jan 26 19:40:54 2024 +0100

tdf#34142: update status language after the cell format language change

Change-Id: Ieb97515cee469a54c5b28ac4477c9d0d78e2974c
Signed-off-by: Henry Castro 
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/162243
Tested-by: Jenkins
Reviewed-by: Caolán McNamara 

diff --git a/framework/source/uielement/langselectionstatusbarcontroller.cxx 
b/framework/source/uielement/langselectionstatusbarcontroller.cxx
index 169583a76fcd..2d56c4186883 100644
--- a/framework/source/uielement/langselectionstatusbarcontroller.cxx
+++ b/framework/source/uielement/langselectionstatusbarcontroller.cxx
@@ -244,10 +244,7 @@ void LangSelectionStatusbarController::LangMenu(
 }
 else if (nId == MID_LANG_DEF_MORE)
 {
-if (bCalc)
-aBuff.append( ".uno:FormatCellDialog" );
-else
-aBuff.append( ".uno:LanguageStatus?Language:string=*" );
+aBuff.append( ".uno:LanguageStatus?Language:string=*" );
 }
 else if (MID_LANG_PARA_1 <= nId && nId <= MID_LANG_PARA_9)
 {
diff --git a/sc/source/ui/docshell/docsh4.cxx b/sc/source/ui/docshell/docsh4.cxx
index 813d86785a7a..82b874391f38 100644
--- a/sc/source/ui/docshell/docsh4.cxx
+++ b/sc/source/ui/docshell/docsh4.cxx
@@ -1252,12 +1252,11 @@ void ScDocShell::Execute( SfxRequest& rReq )
 sal_Int32 nPos = 0;
 if ( aLangText == "*" )
 {
-SfxAbstractDialogFactory* pFact = 
SfxAbstractDialogFactory::Create();
-ScTabViewShell* pSh = GetBestViewShell();
-ScopedVclPtr 
pDlg(pFact->CreateVclDialog(pSh ? pSh->GetDialogParent() : nullptr, 
SID_LANGUAGE_OPTIONS));
-pDlg->Execute();
-
-rDoc.GetLanguage( eLang, eCjk, eCtl );
+if (ScTabViewShell* pSh = GetBestViewShell())
+{
+pSh->ExecuteCellFormatDlg(rReq, "font");
+pBindings->Invalidate(SID_LANGUAGE_STATUS);
+}
 }
 else if ( (nPos = aLangText.indexOf(aDocLangPrefix)) != -1 )
 {


core.git: sc/source

2024-01-26 Thread Henry Castro (via logerrit)
 sc/source/ui/docshell/docsh4.cxx |   51 +++
 sc/source/ui/view/tabview3.cxx   |2 +
 2 files changed, 49 insertions(+), 4 deletions(-)

New commits:
commit b8bc9518d523cff59e238f1eefc4ce7e7c844196
Author: Henry Castro 
AuthorDate: Mon Jan 15 13:50:41 2024 -0400
Commit: Henry Castro 
CommitDate: Fri Jan 26 19:40:36 2024 +0100

tdf#34142: fix cell language status

Now the status bar will show the current cell
language instead of the document language.

Change-Id: I8b6d17b37e7c7bd69abd949a901499613f100649
Signed-off-by: Henry Castro 
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/162123
Reviewed-by: Caolán McNamara 
Tested-by: Jenkins

diff --git a/sc/source/ui/docshell/docsh4.cxx b/sc/source/ui/docshell/docsh4.cxx
index 9396b59518fe..813d86785a7a 100644
--- a/sc/source/ui/docshell/docsh4.cxx
+++ b/sc/source/ui/docshell/docsh4.cxx
@@ -2207,16 +2207,59 @@ void ScDocShell::GetState( SfxItemSet  )
 
 case SID_LANGUAGE_STATUS:
 {
-LanguageType eLatin, eCjk, eCtl;
+OUString sLanguage;
+sal_uInt16 nLangWhich = 0;
+LanguageType eLatin = LANGUAGE_DONTKNOW, eCjk = 
LANGUAGE_DONTKNOW,
+eCtl = LANGUAGE_DONTKNOW;
+
+if (comphelper::LibreOfficeKit::isActive())
+{
+GetDocument().GetLanguage( eLatin, eCjk, eCtl );
+sLanguage = 
SvtLanguageTable::GetLanguageString(eLatin);
 
-GetDocument().GetLanguage( eLatin, eCjk, eCtl );
-OUString sLanguage = 
SvtLanguageTable::GetLanguageString(eLatin);
-if (comphelper::LibreOfficeKit::isActive()) {
 if (eLatin == LANGUAGE_NONE)
 sLanguage += ";-";
 else
 sLanguage += ";" + 
LanguageTag(eLatin).getBcp47(false);
 }
+else if (ScTabViewShell* pViewShell = GetBestViewShell())
+{
+ScMarkData aMark = 
pViewShell->GetViewData().GetMarkData();
+SCCOL  nCol = pViewShell->GetViewData().GetCurX();
+SCROW  nRow = pViewShell->GetViewData().GetCurY();
+SCTAB  nTab = pViewShell->GetViewData().GetTabNo();
+
+aMark.SetMarkArea(ScRange(nCol, nRow, nTab));
+const ScPatternAttr* pSelAttrs = 
GetDocument().GetSelectionPattern(aMark);
+if (pSelAttrs)
+{
+const SfxItemSet& rItemSet = 
pSelAttrs->GetItemSet();
+nLangWhich = 
rItemSet.GetPool()->GetWhich(SID_ATTR_CHAR_LANGUAGE);
+if (SfxItemState::SET == 
rItemSet.GetItemState(nLangWhich))
+eLatin = static_cast(rItemSet.Get(nLangWhich)).GetLanguage();
+
+nLangWhich = 
rItemSet.GetPool()->GetWhich(SID_ATTR_CHAR_CJK_LANGUAGE);
+if (SfxItemState::SET == 
rItemSet.GetItemState(nLangWhich))
+eCjk = static_cast(rItemSet.Get(nLangWhich)).GetLanguage();
+
+nLangWhich = 
rItemSet.GetPool()->GetWhich(SID_ATTR_CHAR_CTL_LANGUAGE);
+if (SfxItemState::SET == 
rItemSet.GetItemState(nLangWhich))
+eCtl = static_cast(rItemSet.Get(nLangWhich)).GetLanguage();
+
+if (eLatin != LANGUAGE_NONE && eLatin != 
LANGUAGE_DONTKNOW)
+sLanguage = 
SvtLanguageTable::GetLanguageString(eLatin);
+if (eCjk != LANGUAGE_NONE && eCjk != 
LANGUAGE_DONTKNOW)
+sLanguage = 
SvtLanguageTable::GetLanguageString(eCjk);
+if (eCtl != LANGUAGE_NONE && eCtl != 
LANGUAGE_DONTKNOW)
+sLanguage = 
SvtLanguageTable::GetLanguageString(eCtl);
+
+if (sLanguage.isEmpty())
+{
+GetDocument().GetLanguage(eLatin, eCjk, eCtl);
+sLanguage = 
SvtLanguageTable::GetLanguageString(eLatin);
+}
+}
+}
 rSet.Put(SfxStringItem(nWhich, sLanguage));
 }
 break;
diff --git a/sc/source/ui/view/tabview3.cxx b/sc/source/ui/view/tabview3.cxx
index fe78ab3e8385..7de940ce24a9 100644
--- a/sc/source/ui/view/tabview3.cxx
+++ b/sc/source/ui/view/tabview3.cxx
@@ -621,6 +621,8 @@ void ScTabView::SelectionChanged(bool bFromPaste)
 rBindings.Invalidate( SID_SORT_ASCENDING );
 rBindings.Invalidate( SID_SORT_DESCENDING );
 

[Bug 34142] Calc language identification should be similar to Writer's

2024-01-26 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=34142

Commit Notification  changed:

   What|Removed |Added

 Whiteboard||target:24.8.0

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

[Bug 159331] sheet window does not refresh properly after touchpad scroll

2024-01-26 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=159331

--- Comment #12 from Phil  ---
Tried disabling skia. no change
tried other of the graphics options, hardware acc, antiialiasing. seemes the
antialiasing off makes the problem show in intact rows but still displaced.
with antialiasing I can get a half a row displaced but all of those problem
could be just the in exact nature of 2 finger swiping on the trackpad.

however, so far turning on Skia with force Skia option disabled seems to have
cured the problem. Not sure if it will return I will keep trying for the error.

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

[Bug 88278] [META] SVG import image filter (all modules)

2024-01-26 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=88278
Bug 88278 depends on bug 158445, which changed state.

Bug 158445 Summary: SVG file not imported correctly
https://bugs.documentfoundation.org/show_bug.cgi?id=158445

   What|Removed |Added

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

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

core.git: svgio/inc svgio/qa svgio/source

2024-01-26 Thread Xisco Fauli (via logerrit)
 svgio/inc/svgsymbolnode.hxx  |   15 
 svgio/qa/cppunit/SvgImportTest.cxx   |   15 
 svgio/qa/cppunit/data/tdf158445.svg  |5 +
 svgio/source/svgreader/svgsymbolnode.cxx |   94 ++-
 4 files changed, 128 insertions(+), 1 deletion(-)

New commits:
commit e7186b49a9a0b24ddc3b1c5384b5d9facb03518c
Author: Xisco Fauli 
AuthorDate: Fri Jan 26 15:10:58 2024 +0100
Commit: Xisco Fauli 
CommitDate: Fri Jan 26 19:31:03 2024 +0100

tdf#158445: support viewBox in symbol elements

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

diff --git a/svgio/inc/svgsymbolnode.hxx b/svgio/inc/svgsymbolnode.hxx
index 7a19b335b7b5..e82f75a7671c 100644
--- a/svgio/inc/svgsymbolnode.hxx
+++ b/svgio/inc/svgsymbolnode.hxx
@@ -29,6 +29,12 @@ namespace svgio::svgreader
 /// use styles
 SvgStyleAttributes  maSvgStyleAttributes;
 
+SvgNumber   maX;
+SvgNumber   maY;
+SvgNumber   maWidth;
+SvgNumber   maHeight;
+
+std::unique_ptr mpViewBox;
 SvgAspectRatio  maSvgAspectRatio;
 
 public:
@@ -39,6 +45,15 @@ namespace svgio::svgreader
 
 virtual const SvgStyleAttributes* getSvgStyleAttributes() const 
override;
 virtual void parseAttribute(SVGToken aSVGToken, const OUString& 
aContent) override;
+virtual void 
decomposeSvgNode(drawinglayer::primitive2d::Primitive2DContainer& rTarget, bool 
bReferenced) const override;
+
+/// viewBox content
+const basegfx::B2DRange* getViewBox() const { return 
mpViewBox.get(); }
+void setViewBox(const basegfx::B2DRange* pViewBox) { 
mpViewBox.reset(); if(pViewBox) mpViewBox.reset( new 
basegfx::B2DRange(*pViewBox) ); }
+
+/// SvgAspectRatio content
+const SvgAspectRatio& getSvgAspectRatio() const { return 
maSvgAspectRatio; }
+
 };
 
 } // end of namespace svgio::svgreader
diff --git a/svgio/qa/cppunit/SvgImportTest.cxx 
b/svgio/qa/cppunit/SvgImportTest.cxx
index 1b0be44177fe..d99e56bfef35 100644
--- a/svgio/qa/cppunit/SvgImportTest.cxx
+++ b/svgio/qa/cppunit/SvgImportTest.cxx
@@ -1591,6 +1591,21 @@ CPPUNIT_TEST_FIXTURE(Test, testTdf155733)
 assertXPath(pDocument, 
"/primitive2D/transform/transform/unifiedtransparence"_ostr, 
"transparence"_ostr, "50");
 }
 
+CPPUNIT_TEST_FIXTURE(Test, testTdf158445)
+{
+Primitive2DSequence aSequence = 
parseSvg(u"/svgio/qa/cppunit/data/tdf158445.svg");
+CPPUNIT_ASSERT_EQUAL(1, static_cast(aSequence.getLength()));
+
+drawinglayer::Primitive2dXmlDump dumper;
+xmlDocUniquePtr pDocument = 
dumper.dumpAndParse(Primitive2DContainer(aSequence));
+
+CPPUNIT_ASSERT (pDocument);
+
+assertXPath(pDocument, 
"/primitive2D/transform/transform/transform/transform/polypolygoncolor"_ostr, 
"color"_ostr, "#00");
+assertXPath(pDocument, 
"/primitive2D/transform/transform/transform/transform/polypolygoncolor/polypolygon"_ostr,
 "height"_ostr, "8.052");
+assertXPath(pDocument, 
"/primitive2D/transform/transform/transform/transform/polypolygoncolor/polypolygon"_ostr,
 "width"_ostr, "5.328");
+}
+
 CPPUNIT_TEST_FIXTURE(Test, testTdf97663)
 {
 Primitive2DSequence aSequence = 
parseSvg(u"/svgio/qa/cppunit/data/em_units.svg");
diff --git a/svgio/qa/cppunit/data/tdf158445.svg 
b/svgio/qa/cppunit/data/tdf158445.svg
new file mode 100644
index ..20e084dd05e5
--- /dev/null
+++ b/svgio/qa/cppunit/data/tdf158445.svg
@@ -0,0 +1,5 @@
+http://www.w3.org/2000/svg; 
viewBox="-0.376 -26.625 160.353 30.488">
+
+
+
+
diff --git a/svgio/source/svgreader/svgsymbolnode.cxx 
b/svgio/source/svgreader/svgsymbolnode.cxx
index 6e18d4bca049..f86dd27bb3a0 100644
--- a/svgio/source/svgreader/svgsymbolnode.cxx
+++ b/svgio/source/svgreader/svgsymbolnode.cxx
@@ -18,6 +18,8 @@
  */
 
 #include 
+#include 
+#include 
 
 namespace svgio::svgreader
 {
@@ -54,9 +56,60 @@ namespace svgio::svgreader
 readLocalCssStyle(aContent);
 break;
 }
+case SVGToken::X:
+{
+SvgNumber aNum;
+
+if(readSingleNumber(aContent, aNum))
+{
+maX = aNum;
+}
+break;
+}
+case SVGToken::Y:
+{
+SvgNumber aNum;
+
+if(readSingleNumber(aContent, aNum))
+{
+maY = aNum;
+}
+break;
+}
+case SVGToken::Width:
+{
+SvgNumber aNum;
+
+if(readSingleNumber(aContent, aNum))
+{
+   

[Bug 159383] Crash if I use SF_Calc CopyToRange

2024-01-26 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=159383

Julien Nabet  changed:

   What|Removed |Added

 Status|UNCONFIRMED |NEW
 Ever confirmed|0   |1

--- Comment #3 from Julien Nabet  ---
Thank you for the feedback, I could reproduce this.

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

[Bug 159383] Crash if I use SF_Calc CopyToRange

2024-01-26 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=159383

Julien Nabet  changed:

   What|Removed |Added

 OS|Windows (All)   |All

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

[Bug 146756] FILEOPEN PPTX: labels of pie chart wrap much too aggressively (compared to 365) as well as too conservatively

2024-01-26 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=146756

--- Comment #6 from Justin L  ---
The two document here are quite different beasts.

piechartformat.pptx (comment 0) defines a custom (relative-to-what?) X/Y
position as well as a size. The W/H were not imported or considered.
https://gerrit.libreoffice.org/c/core/+/162590

aroundboxlines.pptx (comment 4) defines custom (relative) X/Y positions, but no
size. Well, that certainly isn't very helpful. What do we do with that? Is it
supposed to still try to fit inside a slice? (We are left to guess - which
seems to be standard fare for all things chart-related.)

Unfortunately, there doesn't seem to be a "correct answer" for anything here.

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

[Bug 159388] Sorting function doesn't remember that a) first row contains description for columns and b) the previously used sorting priority

2024-01-26 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=159388

--- Comment #2 from ady  ---
Please attach a sample document, as this makes it easier for us to verify the
bug.

Please note that the attachment will be public; remove any sensitive
information before attaching it.

See


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

[Bug 159387] After formatting a complete table as 'vertically centered' and entering data into empty cells it is not shown vertically centered

2024-01-26 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=159387

ady  changed:

   What|Removed |Added

 Resolution|--- |DUPLICATE
 Status|UNCONFIRMED |RESOLVED

--- Comment #2 from ady  ---
Most probably a duplicate of tdf#153527. If it is, then the next release (7.6.5
and/or 24.2) should solve the problem, but not retroactively (i.e. using the
new LO version, you will have to select the range of cells and apply the
desired attribute, and _all_ selected cells should get it).

If for some reason the new release will not solve the problem, then please
reopen the report and comment what is not working as expected with that new
version.

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

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

[Bug 159383] Crash if I use SF_Calc CopyToRange

2024-01-26 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=159383

Carel  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 159383] Crash if I use SF_Calc CopyToRange

2024-01-26 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=159383

--- Comment #2 from Carel  ---
Created attachment 192187
  --> https://bugs.documentfoundation.org/attachment.cgi?id=192187=edit
Calc document that triggers the bub

I have made a short sketch that triggers the bug.
It's a Calc document with macro's
The code also shows on the sheet.
Just push the button and see what happens.

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

[Bug 159220] Issue with LanguageTool add-on and LibreOffice 24.2.0.1

2024-01-26 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=159220

Dieter  changed:

   What|Removed |Added

 Blocks||155314


Referenced Bugs:

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

[Bug 155314] [META] LanguageTool integration

2024-01-26 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=155314

Dieter  changed:

   What|Removed |Added

 Depends on||159220


Referenced Bugs:

https://bugs.documentfoundation.org/show_bug.cgi?id=159220
[Bug 159220] Issue with LanguageTool add-on and LibreOffice 24.2.0.1
-- 
You are receiving this mail because:
You are the assignee for the bug.

[Bug 159208] add "portrait" page style for manual page break

2024-01-26 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=159208

Dieter  changed:

   What|Removed |Added

 CC||dgp-m...@gmx.de
 Status|UNCONFIRMED |RESOLVED
 Resolution|--- |NOTABUG

--- Comment #2 from Dieter  ---
Not a bug. There is no page style "Portrait" by default. Please have a look at
list of page styles in sidebar. "Default Page Style" has portrait orientation.
And of course you can create your own page style and name it "Portrait"
=> RESOLVED NOTABUG

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

[Bug 159390] when a comment box is made very wide, then it does not print properly,

2024-01-26 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=159390

--- Comment #2 from vena.c...@virgin.net  ---
Created attachment 192186
  --> https://bugs.documentfoundation.org/attachment.cgi?id=192186=edit
This is a odt file. The comment box is made extra wide when exported to PDF.

Use this file to export to PDF.

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

[Bug 159176] Marking of text passages by pressing mouse button and moving arrow has become very slow

2024-01-26 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=159176

Dieter  changed:

   What|Removed |Added

 CC||dgp-m...@gmx.de
 Ever confirmed|0   |1
 Status|UNCONFIRMED |NEEDINFO

--- Comment #1 from Dieter  ---
Thnak you for reporting the bug. Is it document specific or does it happen with
ervery document? Could you pleae also test with LO 7.6 or 24.2? Thank you

=> NEEDINFO

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

[Bug 159390] when a comment box is made very wide, then it does not print properly,

2024-01-26 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=159390

--- Comment #1 from vena.c...@virgin.net  ---
Created attachment 192185
  --> https://bugs.documentfoundation.org/attachment.cgi?id=192185=edit
This is a PDF file. The right side of comment boxes is missing.

This is a PDF file. The right side of comment boxes is missing.

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

[Bug 129661] [META] Right-To-Left (RTL) user interface issues

2024-01-26 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=129661
Bug 129661 depends on bug 153853, which changed state.

Bug 153853 Summary: Basic IDE line numbering column (and breakpoints column) 
position should not be flipped with RTL UI
https://bugs.documentfoundation.org/show_bug.cgi?id=153853

   What|Removed |Added

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

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

[Bug 124891] [META] Basic IDE bugs and enhancements

2024-01-26 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=124891
Bug 124891 depends on bug 153853, which changed state.

Bug 153853 Summary: Basic IDE line numbering column (and breakpoints column) 
position should not be flipped with RTL UI
https://bugs.documentfoundation.org/show_bug.cgi?id=153853

   What|Removed |Added

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

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

[Bug 159390] New: when a comment box is made very wide, then it does not print properly,

2024-01-26 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=159390

Bug ID: 159390
   Summary: when a comment box is made very wide, then it does not
print properly,
   Product: LibreOffice
   Version: 24.8.0.0 alpha0+ Master
  Hardware: x86-64 (AMD64)
OS: Windows (All)
Status: UNCONFIRMED
  Severity: normal
  Priority: medium
 Component: Writer
  Assignee: libreoffice-bugs@lists.freedesktop.org
  Reporter: vena.c...@virgin.net

Description:
as above

Steps to Reproduce:
1.  make a comment box and write in it.
2.  make the comment box wide by extending its right side
3.  export as PDF using the dropdown box after clicking "file"
4.  view the PDF file and the right side of the comment box is missing. There
is no warning of that this is goes off the page

Actual Results:
The resulting PDF file shows comment boxes with the right side truncated (off
the right side of the print area)

Expected Results:
I would have expected to see all of the comment box, but the right side of the
comment box including writing on the right side of the comment box is missing.


Reproducible: Always


User Profile Reset: No

Additional Info:
Use the most up-to-date version of 24.8.
I do not know how long the bug has existed

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

[Bug 141773] Autocorrection for all languages doesn't work anymore

2024-01-26 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=141773

--- Comment #24 from Vincent Boudry  ---
Still present in 

Version: 24.2.1.0.0+ (X86_64) / LibreOffice Community
Build ID: 753981dd0cbbdedeca4fa95681f6d65d370a758f
CPU threads: 8; OS: macOS 14.3; UI render: Skia/Metal; VCL: osx
Locale: fr-FR (fr_FR.UTF-8); UI: en-US
Calc: threaded

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

[Bug 159389] New: UI. Recently I can no longer use the Alt key and four digits to enter an ASCII character

2024-01-26 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=159389

Bug ID: 159389
   Summary: UI. Recently I can no longer use the Alt key and four
digits to enter an ASCII character
   Product: LibreOffice
   Version: 7.6.4.1 release
  Hardware: All
OS: Windows (All)
Status: UNCONFIRMED
  Severity: normal
  Priority: medium
 Component: Writer
  Assignee: libreoffice-bugs@lists.freedesktop.org
  Reporter: j...@vansomeren.co.uk

Description:
I often use Alt0233 to type é. The Alt Key is held down while the four digits
are keyed and then Alt is released.  It works fine on this web page! My
Logitech keyboard has a separate 10-key pad and the system boots up with Num
Lock on ( this is my assumption: it generates digits, but Logitech has not
provided a light for any of the three Lock keys. G.)

I have been using this facility for several years (including lots and lots of
times in 2023), but not needed it until recently. Now, The Alt 0 does nothing,
the 2 opens the Styles pane and the Alt 3 opens the Gallery pane. This is a
pain.

Steps to Reproduce:
1.Use a keyboard with a 10 key pad to the right of the typewriter keyboard.
Make sure Num Lock is on and confirm (using any program) that the 10-key pad
generates digits.
2.Start a new LO Writer document and type half a dozen digits on the 10-key pad
to make sure that it is generating digits as expected.
3. Press and hold the Alt key (I use the one to the left of the space bar)
4. Type 0233 on the 10 key pad and release the Alt key
5. Expect to see é

I have reset my user profile and the fault remains.

3.

Actual Results:
My version ignores the Alt key, ignores the 0, senses the 2 and opens the
Styles pane and senses the 3, replacing the styles pane with the Gallery pane.


Expected Results:
é

The Alt key and 10-key pad still respond as usual in all other Windows programs
(I just tried SQL Server Management Studio, Excel and TeamViewer. All three of
these generate the é character)


Reproducible: Always


User Profile Reset: Yes

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

gerrit.libreoffice.org / core / e19e193f88cd6c0525a17fb7a176ed8e6a3e2aa1
e19e193 Version 7.6.4.1, tag libreoffice-7.6.4.1 by Xisco Fauli · 8 weeks ago
libreoffice-7.6.4.1

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

[Bug 159369] Cursor off screen at high document zoom level and high Gnome magnification (Wayland)

2024-01-26 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=159369

--- Comment #6 from Michael Weghorn  ---
There's a useful script to highlight the current caret position attached to
https://bugreports.qt.io/browse/QTBUG-95725 . That works on X11 as is, but not
on Wayland, since getting/setting window positions isn't easily possible any
more...

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

[Bug 159369] Cursor off screen at high document zoom level and high Gnome magnification (Wayland)

2024-01-26 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=159369

--- Comment #5 from Michael Weghorn  ---
When using the qt6 VCL plugin (with current dev branch of qtbase) in a GNOME
Wayland session, the situation is a bit better, but the menu bar also seems to
be an issue.

With the menu bar enabled, the caret keeps being at the very bottom right edge
of the screen. With the Tabbed interface, the cursor is more in the centre and
further up, much closer to what it should be and generally usable from what I
can say.

Note however that focus handling only worked when I started the Orca screen
reader before starting LO, since it seems that a11y is otherwise not enabled by
default in Qt and the object:caret-changed events otherwise don't get sent to
notify about the new cursor position.

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

  1   2   3   >