[Bug 115904] Auto text does not properly insert field variables

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

Andreas Heinisch  changed:

   What|Removed |Added

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

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

[Bug 135609] FILESAVE ODT: Input Field replaced with zero after save and reload

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

Andreas Heinisch  changed:

   What|Removed |Added

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

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

[Bug 158724] Conditional Formatting gets overwritten

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

--- Comment #5 from phantomlo...@t-online.de ---
i have a sheet that is used as calendar where employes enter vacation,
homeoffice, days off (flexible working) and physical presence on bridge days.
The calendar calculates all holidays, bridge days, weekends for this and every
future year. so cell formatting changes each year. If i had a checkbox to lock
cell formatting in conditional formatting this would solve the problem of
manually formatting cells every year. I know it would be faster to create such
a calendar each year manually, but this is a boring task that i want to bypass.
I want to solve this problem once and for all and never touch this thing again.
But right now the formatting is getting killed by the employees copying cells.

On the other hand it doesn't matter cause it would be enough if could lock the
formatting of the whole calendar, but only from manual changes.

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

[Bug 158724] Conditional Formatting gets overwritten

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

--- Comment #5 from phantomlo...@t-online.de ---
i have a sheet that is used as calendar where employes enter vacation,
homeoffice, days off (flexible working) and physical presence on bridge days.
The calendar calculates all holidays, bridge days, weekends for this and every
future year. so cell formatting changes each year. If i had a checkbox to lock
cell formatting in conditional formatting this would solve the problem of
manually formatting cells every year. I know it would be faster to create such
a calendar each year manually, but this is a boring task that i want to bypass.
I want to solve this problem once and for all and never touch this thing again.
But right now the formatting is getting killed by the employees copying cells.

On the other hand it doesn't matter cause it would be enough if could lock the
formatting of the whole calendar, but only from manual changes.

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

[Bug 158724] Conditional Formatting gets overwritten

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

--- Comment #4 from phantomlo...@t-online.de ---
Created attachment 191863
  --> https://bugs.documentfoundation.org/attachment.cgi?id=191863=edit
calendar with conditional formatting

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

[Bug 158724] Conditional Formatting gets overwritten

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

--- Comment #4 from phantomlo...@t-online.de ---
Created attachment 191863
  --> https://bugs.documentfoundation.org/attachment.cgi?id=191863=edit
calendar with conditional formatting

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

New Defects reported by Coverity Scan for LibreOffice

2024-01-10 Thread scan-admin
Hi,

Please find the latest report on new defect(s) introduced to LibreOffice found 
with Coverity Scan.

1 new defect(s) introduced to LibreOffice found with Coverity Scan.
19 defect(s), reported by Coverity Scan earlier, were marked fixed in the 
recent build analyzed by Coverity Scan.

New defect(s) Reported-by: Coverity Scan
Showing 1 of 1 defect(s)


** CID 1583765:  Memory - corruptions  (BAD_FREE)



*** CID 1583765:  Memory - corruptions  (BAD_FREE)
/sw/source/core/txtnode/thints.cxx: 1183 in MakeTextAttr(SwDoc &, const 
SfxItemSet &, int, int)()
1177 sal_Int32 nStt, sal_Int32 nEnd )
1178 {
1179 IStyleAccess& rStyleAccess = rDoc.GetIStyleAccess();
1180 const std::shared_ptr pAutoStyle = 
rStyleAccess.getAutomaticStyle( rSet, IStyleAccess::AUTO_STYLE_CHAR );
1181 SwFormatAutoFormat aNewAutoFormat;
1182 aNewAutoFormat.SetStyleHandle( pAutoStyle );
>>> CID 1583765:  Memory - corruptions  (BAD_FREE)
>>> "MakeTextAttr" frees address of "aNewAutoFormat".
1183 SwTextAttr* pNew = MakeTextAttr( rDoc, aNewAutoFormat, nStt, nEnd 
);
1184 return pNew;
1185 }
1186 
1187 // delete the text attribute and unregister its item at the pool
1188 void SwTextNode::DestroyAttr( SwTextAttr* pAttr )



To view the defects in Coverity Scan visit, 
https://u15810271.ct.sendgrid.net/ls/click?upn=HRESupC-2F2Czv4BOaCWWCy7my0P0qcxCbhZ31OYv50ypSs1kiFPuCn2xFdlMIFBirii0zZ9j2-2F9F2XPBcBm2BNnPiSHxWPOELPnIxzXoBNaw-3D442V_OTq2XUZbbipYjyLSo6GRo-2FpVxQ9OzkDINu9UTS-2FQhSdO0F0jQniitrGlNxDIzPJiQVe0uTPxDqiopw-2Bjnu9uM-2FuJPMryRdazLTC4bjKBq-2FvkkxrvmRJgNdX5HLVSNJONrKqpO26p6SYuP9eq5Q0iByER-2B3OlKOOMGaSzx9LSGPKPjM4Z8hAjs10HNSwvgE3ZxNmSwEGBD4JkKadw3N5hBTUdhmk8xfXAU6gOPAWgS-2BI-3D



[Bug 159050] FORMATTING Format error in paragraphs formatted with justified text

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

Mike Kaganski  changed:

   What|Removed |Added

   Assignee|libreoffice-b...@lists.free |mikekagan...@hotmail.com
   |desktop.org |
 Status|NEW |ASSIGNED

--- Comment #11 from Mike Kaganski  ---
https://gerrit.libreoffice.org/c/core/+/161910

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

[Bug 159050] FORMATTING Format error in paragraphs formatted with justified text

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

--- Comment #10 from stefan_lange...@t-online.de  
---
(In reply to Mike Kaganski from comment #9)
> (In reply to stefan_lange...@t-online.de from comment #4)
> > I have looket at
> > a097d6e ...
> 
> You are absolutely correct.
> One nit if I may. Please don't post shortened hashes; post them in full.
> This makes them nicely linkified - like in
> a097d6e85308f1f9dc91746e98faf46767a1531b ; and makes it easier to navigate.
> Thank you.

OK!

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

[Bug 159073] Remove status bar 'document modified' indicator

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

Samuel Mehrbrodt (allotropia)  changed:

   What|Removed |Added

 Status|NEEDINFO|UNCONFIRMED
 Ever confirmed|1   |0

--- Comment #2 from Samuel Mehrbrodt (allotropia) 
 ---
(In reply to Heiko Tietze from comment #1)
> It's a frequently asked feature, see bug 84198. 

Bug 84198 was filed before we added the modification status to the save icon.
See
https://lists.freedesktop.org/archives/libreoffice/2015-December/071519.html
for the discussion about that.
Also it complains that the status bar thing does is not visible enough, which
got solved by adding an indicator to the Save button in the toolbar.

> I'd rather make the statusbar configurable, as requested in bug 92406.

Sure, that's a valid feature request.

> Any objection to make this ticket a duplicate?

Yes :)

As this indicator serves no purpose any longer it should be completely removed
in favor of a cleaner UI.

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

[Bug 159073] Remove status bar 'document modified' indicator

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

Samuel Mehrbrodt (allotropia)  changed:

   What|Removed |Added

 Status|NEEDINFO|UNCONFIRMED
 Ever confirmed|1   |0

--- Comment #2 from Samuel Mehrbrodt (allotropia) 
 ---
(In reply to Heiko Tietze from comment #1)
> It's a frequently asked feature, see bug 84198. 

Bug 84198 was filed before we added the modification status to the save icon.
See
https://lists.freedesktop.org/archives/libreoffice/2015-December/071519.html
for the discussion about that.
Also it complains that the status bar thing does is not visible enough, which
got solved by adding an indicator to the Save button in the toolbar.

> I'd rather make the statusbar configurable, as requested in bug 92406.

Sure, that's a valid feature request.

> Any objection to make this ticket a duplicate?

Yes :)

As this indicator serves no purpose any longer it should be completely removed
in favor of a cleaner UI.

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

[Bug 159050] FORMATTING Format error in paragraphs formatted with justified text

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

--- Comment #9 from Mike Kaganski  ---
(In reply to stefan_lange...@t-online.de from comment #4)
> I have looket at
> a097d6e ...

You are absolutely correct.
One nit if I may. Please don't post shortened hashes; post them in full. This
makes them nicely linkified - like in a097d6e85308f1f9dc91746e98faf46767a1531b
; and makes it easier to navigate. Thank you.

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

[Bug 159120] New: Recent documents: Show only documents from the current module by default

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

Bug ID: 159120
   Summary: Recent documents: Show only documents from the current
module by default
   Product: LibreOffice
   Version: unspecified
  Hardware: All
OS: All
Status: UNCONFIRMED
  Severity: normal
  Priority: medium
 Component: UI
  Assignee: libreoffice-bugs@lists.freedesktop.org
  Reporter: samuel.mehrbr...@allotropia.de

Proposal: Switch the config option "ShowCurrentModuleOnly" to true by default.

Reason: We should treat individual LO modules as such.
Suggesting spreadsheets in Writer's recent document list confuses the user.

Start center shows all recent documents while the lists in Writer, Calc,
Impress, etc should only show the types supported by the current module.

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

[Bug 159120] Recent documents: Show only documents from the current module by default

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

Samuel Mehrbrodt (allotropia)  changed:

   What|Removed |Added

   Keywords||needsUXEval
 CC||libreoffice-ux-advise@lists
   ||.freedesktop.org,
   ||samuel.mehrbrodt@allotropia
   ||.de

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

[Bug 159120] Recent documents: Show only documents from the current module by default

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

Samuel Mehrbrodt (allotropia)  changed:

   What|Removed |Added

   Keywords||needsUXEval
 CC||libreoffice-ux-advise@lists
   ||.freedesktop.org,
   ||samuel.mehrbrodt@allotropia
   ||.de

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

[Bug 112970] [META] Document recovery bugs and enhancements

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

Bug 158937 Summary: Crash when pressing cancel in the insert password dialog 
when recovering a file (swlo!SwDocShell::SetModified+4b)
https://bugs.documentfoundation.org/show_bug.cgi?id=158937

   What|Removed |Added

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

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

[Bug 108914] [META] Password protected file bugs and enhancements

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

Bug 158937 Summary: Crash when pressing cancel in the insert password dialog 
when recovering a file (swlo!SwDocShell::SetModified+4b)
https://bugs.documentfoundation.org/show_bug.cgi?id=158937

   What|Removed |Added

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

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

core.git: sfx2/source

2024-01-10 Thread Matt K (via logerrit)
 sfx2/source/doc/sfxbasemodel.cxx |2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

New commits:
commit e004c9dd2cc0da7f27503d14bfc13975889eea77
Author: Matt K 
AuthorDate: Tue Jan 9 17:23:34 2024 -0600
Commit: Mike Kaganski 
CommitDate: Thu Jan 11 05:19:28 2024 +0100

tdf#158937 Allow cancel of password dialog during recovery

The problem is that when a user cancels the password dialog
during recovery, the code tries to do something with the
doc, but there is no doc yet because the file is password
protected and not opened, so it crashes.  The fix is just
to check for the absence of errors before using the doc
(canceling the password dialog is considered an abort/
general IO error).

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

diff --git a/sfx2/source/doc/sfxbasemodel.cxx b/sfx2/source/doc/sfxbasemodel.cxx
index a996259f3598..3da83626a5ea 100644
--- a/sfx2/source/doc/sfxbasemodel.cxx
+++ b/sfx2/source/doc/sfxbasemodel.cxx
@@ -2026,7 +2026,7 @@ void SAL_CALL SfxBaseModel::load(   const Sequence< 
beans::PropertyValue >& seqA
 if( m_pData->m_pObjectShell->IsAbortingImport() )
 nError = ERRCODE_ABORT;
 
-if( bSalvage )
+if (bSalvage && nError == ERRCODE_NONE)
 {
 // file recovery: restore original filter
 const SfxStringItem* pFilterItem = 
pMedium->GetItemSet().GetItem(SID_FILTER_NAME, false);


[Bug 159050] FORMATTING Format error in paragraphs formatted with justified text

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

Mike Kaganski  changed:

   What|Removed |Added

 Status|UNCONFIRMED |NEW
 Ever confirmed|0   |1

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

[Bug 159050] FORMATTING Format error in paragraphs formatted with justified text

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

--- Comment #8 from Mike Kaganski  ---
Created attachment 191862
  --> https://bugs.documentfoundation.org/attachment.cgi?id=191862=edit
Minimal reproducer

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

[Bug 159050] FORMATTING Format error in paragraphs formatted with justified text

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

--- Comment #7 from Mike Kaganski  ---
(In reply to stefan_lange...@t-online.de from comment #0)
> - Exception: In paragraph 1.1.1.1 I have formatted the coloured text part
> left aligned and the text is displayed correctly.

Ah - I missed this. Sorry.

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

[Bug 155151] something similar to a page break appears in the document and text disappears

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

--- Comment #9 from bathsheba  ---
Please don't close this! I see this problem constantly. I'm busy this second
but I will try to get you better info later.

I'm in Windows. I see this problem most frequently when pasting text. I think
it's related to outline folding because the rogue "page break" often appears
above a header, and I can sometimes get rid of it by folding or unfolding that
header.

I don't have a simple test case, I see this in documents which have many levels
of headers and have seen many changes and lots of folding and unfolding. It
starts after I've been editing for some days. Once it has started, every paste
triggers it.

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

[Bug 159119] New: Convert docx file to pdf using libreoffice, checkbox and drop-down selection contents are lost

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

Bug ID: 159119
   Summary: Convert docx file to pdf using libreoffice, checkbox
and drop-down selection contents are lost
   Product: LibreOffice
   Version: 7.5.9.2 release
  Hardware: All
OS: All
Status: UNCONFIRMED
  Severity: normal
  Priority: medium
 Component: LibreOffice
  Assignee: libreoffice-bugs@lists.freedesktop.org
  Reporter: pen...@madarame.com.cn

Description:
When using the following command to convert to a pdf file, the contents of the
checkbox and drop-down selection are lost.
soffice --headless --convert-to pdf:writer_pdf_Export --outdir xx\office
xx\aa.docx

Do I need to provide the original documents? There are no pictures to upload,
and the description may not be clear.
https://github.com/pac-madarame/Public_file

Steps to Reproduce:
1.soffice --headless --convert-to pdf:writer_pdf_Export --outdir xx\office
xx\origin_document.docx
2.open the pdf file
3.

Actual Results:
The contents of the checkbox and drop-down selection are lost.

Expected Results:
I hope that the exported pdf will be the same as the one opened with
libreoffice.


Reproducible: Always


User Profile Reset: No

Additional Info:
LibreOffice 7.5.9.2 cdeefe45c17511d326101eed8008ac4092f278a9

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

[Bug 159050] FORMATTING Format error in paragraphs formatted with justified text

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

Mike Kaganski  changed:

   What|Removed |Added

 CC||nem...@openoffice.org

--- Comment #6 from Mike Kaganski  ---
Opening "Alte Fotoapparate V6.4.2_LO_24.8_Fehler_klein_V2_markiert.odt" with
Version: 24.8.0.0.alpha0+ (X86_64) / LibreOffice Community
Build ID: 7bd7085bcfce0b32179197a14189604d4c7478e1
CPU threads: 24; OS: Windows 10.0 Build 22631; UI render: Skia/Vulkan; VCL: win
Locale: en-US (en_US); UI: en-US
Calc: CL threaded

I see the first marked region (in 1.1.1.1) shown exactly as in 7.6.4.1; while
the second marked area (in 1.1.1.2) shows wrong still.

I believe that the changed factor in the range between
c899d3608d30f3ab4c2bc193c1fcd765221614a4 and
7bd7085bcfce0b32179197a14189604d4c7478e1 was this commit from László:

d511367c102ef2ada0f73dbe81744d39865d58ba

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

[Bug 146685] LibreOffice manages to use signing certificate without knowing the certificate password.

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

QA Administrators  changed:

   What|Removed |Added

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

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

[Bug 146685] LibreOffice manages to use signing certificate without knowing the certificate password.

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

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

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 105605] [META] Digital signatures bugs and enhancements

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

Bug 146685 Summary: LibreOffice manages to use signing certificate without 
knowing the certificate password.
https://bugs.documentfoundation.org/show_bug.cgi?id=146685

   What|Removed |Added

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

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

[Bug 146211] export to PDF/A-2b removes (qualified) signature

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

--- Comment #5 from QA Administrators  ---
Dear Ralf Hauser,

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 146211] export to PDF/A-2b removes (qualified) signature

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

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 156288] Calc crashes when updating link to another spreadsheet

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

--- Comment #4 from QA Administrators  ---
Dear Michael Dewsbury,

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 155151] something similar to a page break appears in the document and text disappears

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

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

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 144658] FILEOPEN DOCX Grouped charts title font size becomes larger

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

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

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

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

If you have time, please do the following:

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

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

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

Please DO NOT

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


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

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


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

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

Warm Regards,
QA Team

MassPing-UntouchedBug

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

[Bug 108059] FILESAVE Pie and Donut charts appear mirrored in OOXML formats

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

--- Comment #15 from QA Administrators  ---
Dear Gabor Kelemen (allotropia),

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.

core.git: sw/qa sw/source

2024-01-10 Thread Mike Kaganski (via logerrit)
 sw/qa/extras/ooxmlexport/data/multi_space_url.fodt |9 ++
 sw/qa/extras/ooxmlexport/ooxmlexport20.cxx |   29 +
 sw/source/filter/ww8/wrtw8nds.cxx  |4 +-
 3 files changed, 40 insertions(+), 2 deletions(-)

New commits:
commit 7bd7085bcfce0b32179197a14189604d4c7478e1
Author: Mike Kaganski 
AuthorDate: Wed Jan 10 22:39:39 2024 +0600
Commit: Mike Kaganski 
CommitDate: Thu Jan 11 03:59:36 2024 +0100

tdf#159110: store URLs to DOCX correctly

It must not decode URLs, and must store it percent-encoded.

This was wrong since commit 7b0b5cdfeed656b279bc32cd929630d5fc25878b
(initial import, 2000-09-18).

Commit d68b1b6ae355c92e982ec845216ba459dbdd9e16 (use correct
INetURL-Decode enum, 2000-10-20) replaced incorrect "with charset"
decoding with another incorrect "unambiguous" decoding.

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

diff --git a/sw/qa/extras/ooxmlexport/data/multi_space_url.fodt 
b/sw/qa/extras/ooxmlexport/data/multi_space_url.fodt
new file mode 100644
index ..3a96582aa71f
--- /dev/null
+++ b/sw/qa/extras/ooxmlexport/data/multi_space_url.fodt
@@ -0,0 +1,9 @@
+
+
+http://www.w3.org/1999/xlink; 
xmlns:text="urn:oasis:names:tc:opendocument:xmlns:text:1.0" 
office:version="1.3" office:mimetype="application/vnd.oasis.opendocument.text">
+ 
+  
+   http://www.example.org/path%20%20with%20%20spaces; 
text:style-name="Internet_20_link" 
text:visited-style-name="Visited_20_Internet_20_Link">A sample 
hyperlink
+  
+ 
+
\ No newline at end of file
diff --git a/sw/qa/extras/ooxmlexport/ooxmlexport20.cxx 
b/sw/qa/extras/ooxmlexport/ooxmlexport20.cxx
index 5f681011eeec..be378107df04 100644
--- a/sw/qa/extras/ooxmlexport/ooxmlexport20.cxx
+++ b/sw/qa/extras/ooxmlexport/ooxmlexport20.cxx
@@ -,6 +,35 @@ CPPUNIT_TEST_FIXTURE(Test, testTdf158971)
 }
 }
 
+CPPUNIT_TEST_FIXTURE(Test, testTdf159110)
+{
+// Given a text with an URL with multiple spaces
+loadAndReload("multi_space_url.fodt");
+
+constexpr OUString sExpectedURL = 
u"http://www.example.org/path%20%20with%20%20spaces"_ustr;
+
+// Without the fix, this would have failed with
+// - Expected: http://www.example.org/path%20%20with%20%20spaces
+// - Actual  : http://www.example.org/path with spaces
+CPPUNIT_ASSERT_EQUAL(sExpectedURL,
+ getProperty(getRun(getParagraph(1), 1), 
u"HyperLinkURL"_ustr));
+
+xmlDocUniquePtr pXmlDoc = parseExport("word/document.xml");
+OString sId
+= OUStringToOString(getXPath(pXmlDoc, 
"/w:document/w:body/w:p/w:hyperlink"_ostr, "id"_ostr),
+RTL_TEXTENCODING_UTF8);
+
+xmlDocUniquePtr pXmlRels = parseExport("word/_rels/document.xml.rels");
+
+// Without the fix, this would have failed with
+// - Expected: http://www.example.org/path%20%20with%20%20spaces
+// - Actual  : http://www.example.org/path  with  spaces
+// - In <>, attribute 'Target' of 
'/rels:Relationships/rels:Relationship[@Id='rId2']' incorrect value.
+// I.e., the spaces were stored without percent-encoding, and collapsed on 
import
+assertXPath(pXmlRels, "/rels:Relationships/rels:Relationship[@Id='"_ostr + 
sId + "']",
+"Target"_ostr, sExpectedURL);
+}
+
 } // end of anonymous namespace
 CPPUNIT_PLUGIN_IMPLEMENT();
 
diff --git a/sw/source/filter/ww8/wrtw8nds.cxx 
b/sw/source/filter/ww8/wrtw8nds.cxx
index c70c78121b8b..39e2f885230b 100644
--- a/sw/source/filter/ww8/wrtw8nds.cxx
+++ b/sw/source/filter/ww8/wrtw8nds.cxx
@@ -1092,8 +1092,8 @@ bool AttributeOutputBase::AnalyzeURL( const OUString& 
rUrl, const OUString& /*rT
 else
 {
 INetURLObject aURL( rUrl, INetProtocol::NotValid );
-sURL = aURL.GetURLNoMark( INetURLObject::DecodeMechanism::Unambiguous 
);
-sMark = aURL.GetMark( INetURLObject::DecodeMechanism::Unambiguous );
+sURL = aURL.GetURLNoMark( INetURLObject::DecodeMechanism::NONE );
+sMark = aURL.GetMark( INetURLObject::DecodeMechanism::NONE );
 INetProtocol aProtocol = aURL.GetProtocol();
 
 if ( aProtocol == INetProtocol::File || aProtocol == 
INetProtocol::NotValid )


[Bug 159078] Support for Apache Parquet input for Calc and Base

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

--- Comment #14 from Kohei Yoshida  ---
(In reply to Kohei Yoshida from comment #13)

> Having said that, if someone wants to experiment with this, the easiest way
> to enable Parquet support is to build orcus outside of the libreoffice build
> along with all of its parquet related dependencies, and use
> --with-system-orcus to treat it as a system-provided orcus library when
> building libreoffice.

This may be a completely doable strategy for distro builds though, but I'm not
sure whether it's desirable to have the distro builds have features the TDF
build lacks.

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

[Bug 159118] New: "Export as PDF" button not showing up in Notebookbar

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

Bug ID: 159118
   Summary: "Export as PDF" button not showing up in Notebookbar
   Product: LibreOffice
   Version: 7.6.4.1 release
  Hardware: x86-64 (AMD64)
OS: Linux (All)
Status: UNCONFIRMED
  Severity: normal
  Priority: medium
 Component: LibreOffice
  Assignee: libreoffice-bugs@lists.freedesktop.org
  Reporter: dattero2...@live.it

Description:
Selecting the "Tools>Customize...>Notebookbar>LibreOffice Writer - Tabbed
(scope) / All Commands (target) / Export as PDF (Assigned Commands)" button
doesn't result in it being showed in the Notebook bar. All the other buttons,
including "Export Directly as PDF" seem to be working.

Steps to Reproduce:
Tools>Customize...>Notebookbar>LibreOffice Writer - Tabbed (scope) / All
Commands (target) / Export as PDF (Assigned Commands)

Actual Results:
"Export as PDF" doesn't show up

Expected Results:
"Export as PDF" button showing up


Reproducible: Always


User Profile Reset: No

Additional Info:
Version: 7.6.4.1 (X86_64) / LibreOffice Community
Build ID: e19e193f88cd6c0525a17fb7a176ed8e6a3e2aa1
CPU threads: 8; OS: Linux 6.1; UI render: default; VCL: gtk3
Locale: en-GB (en_GB.UTF-8); UI: en-US
Calc: threaded

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

[Bug 159078] Support for Apache Parquet input for Calc and Base

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

--- Comment #13 from Kohei Yoshida  ---
Allow me to give you guys some clarification...

In the current state on the master branch, the internal orcus is built without
the parquet filter support.  The change referenced by the commit only
introduces all necessary hooks to enable Parquet support when orcus is built
with the parquet filter enabled, but that commit itself is not adequate to load
parquet files.

Now, to enable parquet filter in orcus, you first need to build the Apache
Arrow library since that becomes orcus's new dependency.  And to build the
Apache Arrow library, you need to build the libraries that the Arrow library
itself depends on.  Depending on how many features of Parquet you want to
enable (Parquet can support multiple compression algorithms), you may need to
build a few extra libraries or even more.  So, even in a minimal configuration,
we are talking about 3-4 extra libraries that need to be built before we can
turn on the parquet filter support in orcus.

Here is the main obstacle.  Most of these libraries use CMake as their only
build system.  So if we want to build all of them as part of the regular TDF
build, we first need to find a way to either integrate CMake support into our
GNU Make based build system, or somehow have them built outside of our core
build system and only reference them (or something).

Unfortunately I was not able to come up with a good solution for integrating
these libraries, which is the reason why the internal orcus is built without
parquet support at the moment...

Having said that, if someone wants to experiment with this, the easiest way to
enable Parquet support is to build orcus outside of the libreoffice build along
with all of its parquet related dependencies, and use --with-system-orcus to
treat it as a system-provided orcus library when building libreoffice.

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

[Bug 159064] Cross reference to headings doesn't preserve superscript/subscript when selecting "Referenced text"

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

--- Comment #5 from dattero2...@live.it ---
(In reply to RGB from comment #4)
> Duplicated of Bug 77050?

Yes, definitely. My bad for not finding it. Thanks! It can be marked as
duplicate and hopefully it will be implemented soon.

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

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

2024-01-10 Thread Aron Budea (via logerrit)
 sfx2/source/view/lokhelper.cxx |5 ++---
 1 file changed, 2 insertions(+), 3 deletions(-)

New commits:
commit 1df99bcd3556162e33acc6300b7ca4b8b4c9c057
Author: Aron Budea 
AuthorDate: Thu Jan 11 10:13:42 2024 +1030
Commit: Aron Budea 
CommitDate: Thu Jan 11 01:44:54 2024 +0100

Revert "lok: Log actual differing language"

A change that fixes the same issue got merged recently.

This reverts commit 9c35edb44a82a346122e9ba762165161d1ebcf02.

Change-Id: Ib2565e41b31b7e53e423aba2bdf60d4dbb9f0da5
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/161901
Tested-by: Jenkins CollaboraOffice 
Reviewed-by: Aron Budea 

diff --git a/sfx2/source/view/lokhelper.cxx b/sfx2/source/view/lokhelper.cxx
index 0eb4a31607ac..c54551b1637f 100644
--- a/sfx2/source/view/lokhelper.cxx
+++ b/sfx2/source/view/lokhelper.cxx
@@ -192,8 +192,7 @@ void SfxLokHelper::setView(int nId)
 DisableCallbacks dc;
 
 bool bIsCurrShell = (pViewShell == SfxViewShell::Current());
-const auto aKitLang = 
comphelper::LibreOfficeKit::getLanguageTag().getBcp47();
-if (bIsCurrShell && aKitLang == 
pViewShell->GetLOKLanguageTag().getBcp47())
+if (bIsCurrShell && 
comphelper::LibreOfficeKit::getLanguageTag().getBcp47() == 
pViewShell->GetLOKLanguageTag().getBcp47())
 return;
 
 if (bIsCurrShell)
@@ -202,7 +201,7 @@ void SfxLokHelper::setView(int nId)
 // But it looks like that the language can go wrong, so we 
have to fix that.
 // This can happen, when someone sets the language or 
SfxViewShell::Current() separately.
 SAL_WARN("lok", "LANGUAGE mismatch at setView! ... old (wrong) 
lang:"
-<< aKitLang
+<< 
comphelper::LibreOfficeKit::getLanguageTag().getBcp47()
 << " new lang:" << 
pViewShell->GetLOKLanguageTag().getBcp47());
 }
 


[Bug 159089] Changing an object color in Draw or Impress crashes LO

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

Patrick Luby  changed:

   What|Removed |Added

   Assignee|libreoffice-b...@lists.free |plub...@libreoffice.org
   |desktop.org |

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

[Bug 159115] FORMATTING: pdf with incorrect location of logo

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

V Stuart Foote  changed:

   What|Removed |Added

   Keywords||filter:pdf

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

[Bug 99746] [META] PDF import filter in Draw

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

V Stuart Foote  changed:

   What|Removed |Added

 Depends on||159115


Referenced Bugs:

https://bugs.documentfoundation.org/show_bug.cgi?id=159115
[Bug 159115] FORMATTING: pdf with incorrect location of logo
-- 
You are receiving this mail because:
You are the assignee for the bug.

[Bug 159115] FORMATTING: pdf with incorrect location of logo

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

V Stuart Foote  changed:

   What|Removed |Added

  Component|Draw|filters and storage
 CC||vsfo...@libreoffice.org
 Blocks||99746

--- Comment #4 from V Stuart Foote  ---
OK, but the pdfium based filter inserts a pixel perfect rendering of the PDF.
So just the pdfio import filter using poppler/cairo calls to render elements to
Draw objects has an issue with the logo.

So, depends on what you need to do with the PDF--LibreOffice is not a PDF
editor, find a different program if that is your use case.

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


Referenced Bugs:

https://bugs.documentfoundation.org/show_bug.cgi?id=99746
[Bug 99746] [META] PDF import filter in Draw
-- 
You are receiving this mail because:
You are the assignee for the bug.

[Bug 155364] Forms - Table controls: Buttons in the Navigation bar get smaller when zooming form

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

--- Comment #7 from George  ---
Just tried LO 7.0.5.2, and you are correct. The bug does not appear in the
tables, or the Table Control in my forms. Thanks for passing on this
information.

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

[Bug 155364] Forms - Table controls: Buttons in the Navigation bar get smaller when zooming form

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

--- Comment #6 from George  ---
At least with the Navigation Bar, users can choose "large" in the Icon Size
property for the Navigation Bar control, which can compensate, somewhat.
I will try installing LO 7.0.5.2 and see how this behaves.

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

[Bug 129062] [META] Skia library bugs

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

Stéphane Guillou (stragu)  changed:

   What|Removed |Added

 Depends on||158945


Referenced Bugs:

https://bugs.documentfoundation.org/show_bug.cgi?id=158945
[Bug 158945] Calc: crash when entering text in a cell
-- 
You are receiving this mail because:
You are the assignee for the bug.

[Bug 158714] EDITING - Crash when inserting acute accent with dead key as first character in cell

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

Stéphane Guillou (stragu)  changed:

   What|Removed |Added

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

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

[Bug 158945] Calc: crash when entering text in a cell

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

Stéphane Guillou (stragu)  changed:

   What|Removed |Added

 Blocks||129062
   See Also||https://bugs.documentfounda
   ||tion.org/show_bug.cgi?id=15
   ||8714
 CC||stephane.guillou@libreoffic
   ||e.org

--- Comment #25 from Stéphane Guillou (stragu) 
 ---
Greg, did you test previous version of LO? Would for example 7.5 work as
expected?


Referenced Bugs:

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

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

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

Stéphane Guillou (stragu)  changed:

   What|Removed |Added

 Depends on||159114


Referenced Bugs:

https://bugs.documentfoundation.org/show_bug.cgi?id=159114
[Bug 159114] CRASH: inserting column and undoing
-- 
You are receiving this mail because:
You are the assignee for the bug.

[Bug 108364] [META] Table/Row/Column/Cell management function bugs and enhancements

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

Stéphane Guillou (stragu)  changed:

   What|Removed |Added

 Depends on||159114


Referenced Bugs:

https://bugs.documentfoundation.org/show_bug.cgi?id=159114
[Bug 159114] CRASH: inserting column and undoing
-- 
You are receiving this mail because:
You are the assignee for the bug.

[Bug 133092] [META] Crash bugs

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

Stéphane Guillou (stragu)  changed:

   What|Removed |Added

 Depends on||159114


Referenced Bugs:

https://bugs.documentfoundation.org/show_bug.cgi?id=159114
[Bug 159114] CRASH: inserting column and undoing
-- 
You are receiving this mail because:
You are the assignee for the bug.

[Bug 159114] CRASH: inserting column and undoing

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

Stéphane Guillou (stragu)  changed:

   What|Removed |Added

   Keywords||bibisectRequest, regression
 Blocks||133092, 105948, 108364
   Severity|normal  |critical
Crash report or||["SfxItemSet::Get(unsigned
crash signature||short, bool) const"]
 CC||stephane.guillou@libreoffic
   ||e.org
Version|24.8.0.0 alpha0+ Master |7.3.7.2 release
 Ever confirmed|0   |1
 Status|UNCONFIRMED |NEW
 OS|All |Linux (All)

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

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

Also in:
- 7.6.4.1:
https://crashreport.libreoffice.org/stats/crash_details/6f3db431-97fa-4988-981c-df13b48023f3
- 7.4.7.2:
https://crashreport.libreoffice.org/stats/crash_details/c08de567-4871-4bad-aa5c-edd6d248fb37
- 7.3.7.2:
https://crashreport.libreoffice.org/stats/crash_details/00742f45-cfbc-402e-8c71-2c5709cad5d2

Not reproduced in 7.2.0.4 -> regression.


Referenced Bugs:

https://bugs.documentfoundation.org/show_bug.cgi?id=105948
[Bug 105948] [META] Undo/Redo bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=108364
[Bug 108364] [META] Table/Row/Column/Cell management function bugs and
enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=133092
[Bug 133092] [META] Crash bugs
-- 
You are receiving this mail because:
You are the assignee for the bug.

[Bug 158841] Numbering of the chapters is wrong

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

Stéphane Guillou (stragu)  changed:

   What|Removed |Added

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

--- Comment #7 from Stéphane Guillou (stragu) 
 ---
Thanks for the report.
Are you able to provide a smaller sample file that has the same issue?
A 1.7 GB archive makes it difficult for us to test and pinpoint the issue.
Can you also please be more explicit with the steps, what is expected and what
you see instead?

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

[Bug 158858] Distorted image and incorrect size during hover over in Calc

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

--- Comment #3 from Stéphane Guillou (stragu) 
 ---
Created attachment 191861
  --> https://bugs.documentfoundation.org/attachment.cgi?id=191861=edit
test ODS with same comment duplicated: one shown, the other hidden

Steps to reproduce from scratch:

1. add comment
2. insert some text, keep comment visible
3. in next paragraph, use the toolbar to insert an image
4. right-click on image > Area > Area > Image > Options > Style: Stretched
5. resize the comment so image looks good
6. hover over cell

With attachment, hover over cell I1 and compare popup with visible comment.

In LO 7.5, popup comment would have the same size as visible comment.

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

[Bug 159089] Changing an object color in Draw or Impress crashes LO

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

Patrick Luby  changed:

   What|Removed |Added

 CC||m.wegh...@posteo.de

--- Comment #7 from Patrick Luby  ---
OK. Did a bisect and the following commit is where the crashing started. The
crash is in the macOS accessibility handling code so I'll take a look at that
commit and see if I can determine what needs to be done to fix this crash:

2f5e7a07775690e57d639eeca7a1e41733fa93a9 is the first bad commit
commit 2f5e7a07775690e57d639eeca7a1e41733fa93a9
Author: Michael Weghorn 
Date:   Thu Sep 7 08:09:31 2023 +0200

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

[Bug 159115] FORMATTING: pdf with incorrect location of logo

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

--- Comment #3 from Kurt Roeckx  ---
Firefox really does strange things to it, I've filed a bug for that at
https://bugzilla.mozilla.org/show_bug.cgi?id=1874013

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

[Bug 158858] Distorted image and incorrect size during hover over in Calc

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

Stéphane Guillou (stragu)  changed:

   What|Removed |Added

 Status|UNCONFIRMED |NEW
 Blocks||101216
 Ever confirmed|0   |1
 Whiteboard| QA:needsComment|
 OS|Windows (All)   |All
   See Also||https://bugs.documentfounda
   ||tion.org/show_bug.cgi?id=73
   ||537
 CC||momonas...@gmail.com,
   ||stephane.guillou@libreoffic
   ||e.org
Version|7.6.4.1 release |7.6.0.1 rc

--- Comment #2 from Stéphane Guillou (stragu) 
 ---
The issue is related to the differently sized popup comment, likely since the
fix for bug 73537.
The popup comment is resized to fit the authorship information, which really
becomes a problem when the comment is filled with a stretched picture, like
here.
If the image wasn't stretched, but for example centred or tiled, the aspect
ratio issue would be less of a problem (but the placement of the image would
change, potentially crop it...).

Confirming in:

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


Referenced Bugs:

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

[Bug 101216] [META] Calc comment bugs and enhancements

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

Stéphane Guillou (stragu)  changed:

   What|Removed |Added

 Depends on||158858


Referenced Bugs:

https://bugs.documentfoundation.org/show_bug.cgi?id=158858
[Bug 158858] Distorted image and incorrect size during hover over in Calc
-- 
You are receiving this mail because:
You are the assignee for the bug.

[Bug 34391] FORMATTING: Introduce table cell styles

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

--- Comment #32 from Nijineko  ---
Yes, implement a solution for this please. Last time I used LibreOffice for a
project, it had over 1000 tables.

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

[Bug 126008] TABLES STYLES: Inserting or removing a row/column changes entire table's formatting (see comment 5)

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

--- Comment #95 from Nijineko  ---
As a random user passing by, I will comment on the behavior that I expected to
see in Writer and was surprised that it did not exist. 

When I open the Styles panel, I see Paragraph, Character, Frame, Page, List,
and Table Style Icon/tabs. When I check each one, I see that I can right-click
on an existing entry and a pop-up menu gives me the options of New/Modify/Hide. 
However, when I go to the Table Styles tab and right click on the options, I am
only given the Hide menu option. 

I expected to see New and Modify menu options here as well, and expected to be
able to create and modify styles for tables the same way I can for Paragraphs,
Characters, and so forth. 

Is this possible to implement? If we can create our own styles, then it might
resolve the issue?

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

[Bug 159050] FORMATTING Format error in paragraphs formatted with justified text

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

--- Comment #5 from stefan_lange...@t-online.de  
---
To test if there is a relation of the change to fix tdf#57187 to my bug I have
tested with my test document "Alte Fotoapparate
V6.4.2_LO_24.8_Fehler_klein_V2_markiert.odt":
I have replaced the space at the end of a wrongly formatted line by Shift +
Enter (topic of tdf#57187, line break within a paragraph) and - oops - as
result the line is formatted correctly!
I think this is almost a sure indication that there is a relation!

But this (a line break instaed of space) is not a solution for me and also not
a workaround, because the line break remains when I remove the picture that
causes the line wrap or change its position.

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

[Bug 159117] New: Table of Contents tab formatting can be edited but is not applied.

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

Bug ID: 159117
   Summary: Table of Contents tab formatting can be edited but is
not applied.
   Product: LibreOffice
   Version: 7.5.9.2 release
  Hardware: All
OS: Windows (All)
Status: UNCONFIRMED
  Severity: normal
  Priority: medium
 Component: Writer
  Assignee: libreoffice-bugs@lists.freedesktop.org
  Reporter: p...@seekfirst.net

Description:
When formatting a table of contents, the 

Steps to Reproduce:
1. Start a new Text document in Writer
2. Enter two lines of text.

Line 1
Line 2

3. Press F11 to show the Styles on the right.
4. Press Ctrl+A to select both lines.  While they are selected, double-click
the  type Heading 1 which is under Heading.  Both lines will become larger and
bold.
5. Go to the top of the document (Ctrl+Home).
6. Select from the menu: Insert > Table of Contents and Index > Table of
Contents, Index, or Bibliography...
7. Select OK taking the default of all controls.

Notice the table of contents (TOC) has both lines because they are of style
'Heading 1' 

8. Click on the "Line 1" line in the TOC (not the one below).  This line has
periods going out to the page number on the right.

Notice the Style in the right side becomes "Contents 1".  This is the style of
that line.

9. Right-click in the Styles box (on the right) on "Contents 1" and select
"Modify..." to modify this style.
10. On the Paragraph Style dialog, select the "Tabs" tab.

The bug is that anything changed on this tab does not apply the way it should. 
Watch...

11. Change the fill character to None.  Click OK.

Notice the TOC has not changed.

12. Right-click the TOC and select "Update Index".

Still no change to the TOC.

13. However, right-click the TOC and select "Edit Index" and UNCHECK "Protect
against manual changes", then click OK.

14. Now put the cursor on "Line 1" in the TOC.  Note that the style is
"Contents 1".

15. Double-Click the "Contents 1" style in the list of styles on the right. 
This applies that style-- even though it is supposed to be the currently
applied style.

NOTICE the fill character becomes NONE as it should be because that is how the
style is defined.

16. Right-click the TOC and select "Update Index".

NOTICE the fill character has come back-- that's a bug.  The same thing happens
with the tabs set in the paragraph style.  It somehow reverts back to some
other style even though it says the style in the ribbon below the menu.




Actual Results:
See steps above.

Expected Results:
See steps above.


Reproducible: Always


User Profile Reset: No

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

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

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

[Bug 150245] Font size is reset to a default setting in Calc cell comment

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

Stéphane Guillou (stragu)  changed:

   What|Removed |Added

Summary|Font size is reset to a |Font size is reset to a
   |default setting in Calc |default setting in Calc
   |cell commet |cell comment

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

[Bug 117308] EDITING Comment box is not resized after Font size change after Save and Open

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

--- Comment #13 from Stéphane Guillou (stragu) 
 ---
reproduced in recent trunk build:

Version: 24.8.0.0.alpha0+ (X86_64) / LibreOffice Community
Build ID: a2ccc25ccb2e94f5990d6d413541dbcdd3a72338
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 159115] FORMATTING: pdf with incorrect location of logo

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

m_a_riosv  changed:

   What|Removed |Added

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

--- Comment #2 from m_a_riosv  ---
Reproducible.
Version: 24.8.0.0.alpha0+ (X86_64) / LibreOffice Community
Build ID: 25276df12abd9d002f7f899900434617b256f745
CPU threads: 16; OS: Windows 10.0 Build 22631; UI render: default; VCL: win
Locale: es-ES (es_ES); UI: en-US
Calc: CL threaded

BTW, pdf opens fine with Edge, but not with Firefox.

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

[Bug 159116] Translation problem in Calc - Portuguese PT

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

--- Comment #1 from paulo g.  ---
Created attachment 191860
  --> https://bugs.documentfoundation.org/attachment.cgi?id=191860=edit
Error of Translation

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

[Bug 159116] New: Translation problem in Calc - Portuguese PT

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

Bug ID: 159116
   Summary: Translation problem in Calc - Portuguese PT
   Product: LibreOffice
   Version: 6.0.7.3 release
  Hardware: x86-64 (AMD64)
OS: Linux (All)
Status: UNCONFIRMED
  Severity: normal
  Priority: medium
 Component: Calc
  Assignee: libreoffice-bugs@lists.freedesktop.org
  Reporter: paulo...@hotmail.com

Description:
Where is Freeze Rows and Collumns should be: Fixar Linhas e Colunas.
The tip of the menu is wrong, also the first line of the options, see in Actual
Results.

Actual Results:
Menu Freeze Rows and Colluns, in icons:
Freeze Rows and Collumns
Fixar Primeira Coluna
Fixar Primeira 

Expected Results:
Menu Fixar Linhas e Colunas, in icons:
Fixar Linhas e Colunas
Fixar Primeira Coluna
Fixar Primeira


Reproducible: Always


User Profile Reset: No

Additional Info:
Translation Problem

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

[Bug 55571] [META] ACCESSIBILITY: Tracking bug for issues related to the macOS Accessibility API

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

Stéphane Guillou (stragu)  changed:

   What|Removed |Added

 Depends on||158875


Referenced Bugs:

https://bugs.documentfoundation.org/show_bug.cgi?id=158875
[Bug 158875] Text Cursor (Input Caret) too thin in Writer on macOS
-- 
You are receiving this mail because:
You are the assignee for the bug.

[Bug 158875] Text Cursor (Input Caret) too thin in Writer on macOS

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

Stéphane Guillou (stragu)  changed:

   What|Removed |Added

 CC||stephane.guillou@libreoffic
   ||e.org
 Blocks||55571


Referenced Bugs:

https://bugs.documentfoundation.org/show_bug.cgi?id=55571
[Bug 55571] [META] ACCESSIBILITY: Tracking bug for issues related to the macOS
Accessibility API
-- 
You are receiving this mail because:
You are the assignee for the bug.

[Bug 158875] Text Cursor (Input Caret) too thin in Writer on macOS

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

--- Comment #4 from Stéphane Guillou (stragu) 
 ---
Created attachment 191859
  --> https://bugs.documentfoundation.org/attachment.cgi?id=191859=edit
comparison 7.6.4 vs 24.8 alpha0+ (cursor after pipe character)

Thank you for the report, Detlef.

I compared 7.6.4 and a recent trunk build but couldn't spot a difference, see
attached screenshots. 

Version: 7.6.4.1 (X86_64) / LibreOffice Community
Build ID: e19e193f88cd6c0525a17fb7a176ed8e6a3e2aa1
CPU threads: 2; OS: Mac OS X 13.2.1; UI render: Skia/Raster; VCL: osx
Locale: en-US (en_US.UTF-8); UI: en-US
Calc: threaded

Version: 24.8.0.0.alpha0+ (X86_64) / LibreOffice Community
Build ID: ef6ff2df2e1286974da2f344aa3b8e3ae9093a79
CPU threads: 2; OS: macOS 13.2.1; UI render: Skia/Raster; VCL: osx
Locale: fr-FR (fr_FR.UTF-8); UI: en-US
Calc: threaded

Are you able to provide some comparison, between LO versions and/or between LO
and other apps?

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

[Bug 159114] CRASH: inserting column and undoing

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

m_a_riosv  changed:

   What|Removed |Added

 CC||miguelangelrv@libreoffice.o
   ||rg

--- Comment #1 from m_a_riosv  ---
Doesn't crash, with/without macros.
Version: 24.8.0.0.alpha0+ (X86_64) / LibreOffice Community
Build ID: 25276df12abd9d002f7f899900434617b256f745
CPU threads: 16; OS: Windows 10.0 Build 22631; UI render: default; VCL: win
Locale: es-ES (es_ES); UI: en-US
Calc: CL threaded

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

[Bug 153293] [META] Dark Mode bugs and enhancements

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

Stéphane Guillou (stragu)  changed:

   What|Removed |Added

 Depends on|158864  |


Referenced Bugs:

https://bugs.documentfoundation.org/show_bug.cgi?id=158864
[Bug 158864] Many/most dark mode UI elements have too strong a contrast
-- 
You are receiving this mail because:
You are the assignee for the bug.

[Bug 150915] [META] Windows Dark Mode bugs and enhancements

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

Stéphane Guillou (stragu)  changed:

   What|Removed |Added

 Depends on||158864


Referenced Bugs:

https://bugs.documentfoundation.org/show_bug.cgi?id=158864
[Bug 158864] Many/most dark mode UI elements have too strong a contrast
-- 
You are receiving this mail because:
You are the assignee for the bug.

[Bug 158864] Many/most dark mode UI elements have too strong a contrast

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

Stéphane Guillou (stragu)  changed:

   What|Removed |Added

  Component|LibreOffice |UI
 Blocks|153293  |150915


Referenced Bugs:

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

[Bug 158864] Many/most dark mode UI elements have too strong a contrast

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

--- Comment #15 from Stéphane Guillou (stragu) 
 ---
Created attachment 191858
  --> https://bugs.documentfoundation.org/attachment.cgi?id=191858=edit
OnlyOffice with "Dark Interface Theme" and "Dark Document"

for another comparison, OnlyOffice. (This screenshot is on Linux but I believe
the colours are the same on Windows).

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

[Bug 159096] Comment indicator in Calc should be red, not magenta

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

--- Comment #7 from ady  ---
(In reply to Telesto from comment #6)

> Case BB appears to be inconsistent compared to all other cases; no border.
> However it does look pretty nice, IMHO. Maybe case A & B should act as BB;
> transparent line 

IMO that is not a good idea. When the cell's background color is similar to the
color of the comment indicator, then users cannot detect/see that the indicator
is there.

That situation was reported a few years ago, so the comment indicator received
its own "border" by surrounding it with a contrasting colored "line". To be
clear, the indicator's "border" should always contrast with the indicator's
color. So you could have the indicator with its own border being white while
the cell's background is also white; the indicator is visible against the
cell's background color. If the indicator has a similar color as the cell's
background, then the "border" around the indicator helps in showing it against
that similar background.

If there is some combination in which the comment indicator has no contrasting
"border", that would be a bug!


Regarding the main topic of this ticket... If the cell's background were to be
red, the comment indicator would not be so easily seen. If the font of the cell
were to be red (which is, after automatic, the default for the toolbar's icon),
then the comment indicator would be interfering with the content, making it
harder to read.

Having said that, I wouldn't care about the specific color of the comment
indicator if it was smaller, instead of bigger since LO 7.6. If it was smaller,
I wouldn't mind it being "glossy" (to use Telesto's term from comment 3). I
guess that "glossy" might bother, but maybe it contrasts with either black or
white font(?). Maybe there is some possible improvement for the indicator's
color - not convinced that red would be better. I agree with Mike in comment 1
(including the opinion regarding the size).

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

[Bug 159096] Comment indicator in Calc should be red, not magenta

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

--- Comment #7 from ady  ---
(In reply to Telesto from comment #6)

> Case BB appears to be inconsistent compared to all other cases; no border.
> However it does look pretty nice, IMHO. Maybe case A & B should act as BB;
> transparent line 

IMO that is not a good idea. When the cell's background color is similar to the
color of the comment indicator, then users cannot detect/see that the indicator
is there.

That situation was reported a few years ago, so the comment indicator received
its own "border" by surrounding it with a contrasting colored "line". To be
clear, the indicator's "border" should always contrast with the indicator's
color. So you could have the indicator with its own border being white while
the cell's background is also white; the indicator is visible against the
cell's background color. If the indicator has a similar color as the cell's
background, then the "border" around the indicator helps in showing it against
that similar background.

If there is some combination in which the comment indicator has no contrasting
"border", that would be a bug!


Regarding the main topic of this ticket... If the cell's background were to be
red, the comment indicator would not be so easily seen. If the font of the cell
were to be red (which is, after automatic, the default for the toolbar's icon),
then the comment indicator would be interfering with the content, making it
harder to read.

Having said that, I wouldn't care about the specific color of the comment
indicator if it was smaller, instead of bigger since LO 7.6. If it was smaller,
I wouldn't mind it being "glossy" (to use Telesto's term from comment 3). I
guess that "glossy" might bother, but maybe it contrasts with either black or
white font(?). Maybe there is some possible improvement for the indicator's
color - not convinced that red would be better. I agree with Mike in comment 1
(including the opinion regarding the size).

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

core.git: Branch 'libreoffice-24-2' - translations

2024-01-10 Thread Martin Srebotnjak (via logerrit)
 translations |2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

New commits:
commit 8473975ab19e5fb838c0af9fdaa1288b149dfcbb
Author: Martin Srebotnjak 
AuthorDate: Wed Jan 10 22:30:04 2024 +0100
Commit: Gerrit Code Review 
CommitDate: Wed Jan 10 22:30:04 2024 +0100

Update git submodules

* Update translations from branch 'libreoffice-24-2'
  to 0aea9b958bf6ee2150619f770e2041ca74bbde00
  - Updated Slovenian translation

Change-Id: I99b8b0cffd064360ec5b3c36671a63c5598a992f

diff --git a/translations b/translations
index 11de70239609..0aea9b958bf6 16
--- a/translations
+++ b/translations
@@ -1 +1 @@
-Subproject commit 11de70239609cfc862f169bc5065984fddcd677f
+Subproject commit 0aea9b958bf6ee2150619f770e2041ca74bbde00


translations.git: Branch 'libreoffice-24-2' - source/sl

2024-01-10 Thread Martin Srebotnjak (via logerrit)
 source/sl/helpcontent2/source/text/sbasic/shared/03.po|4 
 source/sl/helpcontent2/source/text/scalc/00.po|4 
 source/sl/helpcontent2/source/text/scalc/01.po|4 
 source/sl/helpcontent2/source/text/scalc/guide.po |4 
 source/sl/helpcontent2/source/text/sdraw/01.po|4 
 source/sl/helpcontent2/source/text/shared/00.po   |4 
 source/sl/helpcontent2/source/text/shared/01.po   |4 
 source/sl/helpcontent2/source/text/shared/guide.po|   14 +
 source/sl/helpcontent2/source/text/shared/help.po |4 
 source/sl/helpcontent2/source/text/smath/01.po|4 
 source/sl/helpcontent2/source/text/swriter.po |   10 -
 source/sl/helpcontent2/source/text/swriter/00.po  |4 
 source/sl/officecfg/registry/data/org/openoffice/Office/UI.po |8 
 source/sl/sc/messages.po  |   26 ++-
 source/sl/scp2/source/ooo.po  |   22 ++
 source/sl/sd/messages.po  |   86 +-
 source/sl/svtools/messages.po |4 
 source/sl/svx/messages.po |4 
 source/sl/uui/messages.po |4 
 19 files changed, 127 insertions(+), 91 deletions(-)

New commits:
commit 0aea9b958bf6ee2150619f770e2041ca74bbde00
Author: Martin Srebotnjak 
AuthorDate: Wed Jan 10 22:29:08 2024 +0100
Commit: Andras Timar 
CommitDate: Wed Jan 10 22:29:58 2024 +0100

Updated Slovenian translation

Change-Id: I99b8b0cffd064360ec5b3c36671a63c5598a992f

diff --git a/source/sl/helpcontent2/source/text/sbasic/shared/03.po 
b/source/sl/helpcontent2/source/text/sbasic/shared/03.po
index 0e423c8c4fc..ddd98c2f24d 100644
--- a/source/sl/helpcontent2/source/text/sbasic/shared/03.po
+++ b/source/sl/helpcontent2/source/text/sbasic/shared/03.po
@@ -3,14 +3,14 @@ msgid ""
 msgstr ""
 "Project-Id-Version: LibreOffice 24.02
"
 "Report-Msgid-Bugs-To: 
https://bugs.libreoffice.org/enter_bug.cgi?product=LibreOffice_status=UNCONFIRMED=UI
"
-"POT-Creation-Date: 2023-12-23 09:15+0100
"
+"POT-Creation-Date: 2024-01-10 16:22+0100
"
 "PO-Revision-Date: 2023-12-29 15:13+0200
"
 "Last-Translator: Martin Srebotnjak 
"
 "Language-Team: sl.libreoffice.org
"
-"Language: sl
"
 "MIME-Version: 1.0
"
 "Content-Type: text/plain; charset=UTF-8
"
 "Content-Transfer-Encoding: 8bit
"
+"Language: sl
"
 "Plural-Forms: nplurals=4; plural=(n%100==1 ? 0 : n%100==2 ? 1 : n%100==3 || 
n%100==4 ? 2 : 3);
"
 "X-Generator: Virtaal 0.7.1
"
 "X-Accelerator-Marker: ~
"
diff --git a/source/sl/helpcontent2/source/text/scalc/00.po 
b/source/sl/helpcontent2/source/text/scalc/00.po
index 05601e4f251..629e295d1f2 100644
--- a/source/sl/helpcontent2/source/text/scalc/00.po
+++ b/source/sl/helpcontent2/source/text/scalc/00.po
@@ -3,14 +3,14 @@ msgid ""
 msgstr ""
 "Project-Id-Version: LibreOffice 24.02
"
 "Report-Msgid-Bugs-To: 
https://bugs.libreoffice.org/enter_bug.cgi?product=LibreOffice_status=UNCONFIRMED=UI
"
-"POT-Creation-Date: 2023-12-23 09:15+0100
"
+"POT-Creation-Date: 2024-01-10 16:22+0100
"
 "PO-Revision-Date: 2023-12-27 23:35+0200
"
 "Last-Translator: Martin Srebotnjak 
"
 "Language-Team: sl.libreoffice.org
"
-"Language: sl
"
 "MIME-Version: 1.0
"
 "Content-Type: text/plain; charset=UTF-8
"
 "Content-Transfer-Encoding: 8bit
"
+"Language: sl
"
 "Plural-Forms: nplurals=4; plural=(n%100==1 ? 0 : n%100==2 ? 1 : n%100==3 || 
n%100==4 ? 2 : 3);
"
 "X-Generator: Virtaal 0.7.1
"
 "X-Accelerator-Marker: ~
"
diff --git a/source/sl/helpcontent2/source/text/scalc/01.po 
b/source/sl/helpcontent2/source/text/scalc/01.po
index aecb9465fdb..bd57cd6fb35 100644
--- a/source/sl/helpcontent2/source/text/scalc/01.po
+++ b/source/sl/helpcontent2/source/text/scalc/01.po
@@ -3,14 +3,14 @@ msgid ""
 msgstr ""
 "Project-Id-Version: LibreOffice 24.02
"
 "Report-Msgid-Bugs-To: 
https://bugs.libreoffice.org/enter_bug.cgi?product=LibreOffice_status=UNCONFIRMED=UI
"
-"POT-Creation-Date: 2023-12-23 09:15+0100
"
+"POT-Creation-Date: 2024-01-10 16:22+0100
"
 "PO-Revision-Date: 2023-12-28 13:25+0200
"
 "Last-Translator: Martin Srebotnjak 
"
 "Language-Team: sl.libreoffice.org
"
-"Language: sl
"
 "MIME-Version: 1.0
"
 "Content-Type: text/plain; charset=UTF-8
"
 "Content-Transfer-Encoding: 8bit
"
+"Language: sl
"
 "Plural-Forms: nplurals=4; plural=(n%100==1 ? 0 : n%100==2 ? 1 : n%100==3 || 
n%100==4 ? 2 : 3);
"
 "X-Generator: Virtaal 0.7.1
"
 "X-Accelerator-Marker: ~
"
diff --git a/source/sl/helpcontent2/source/text/scalc/guide.po 
b/source/sl/helpcontent2/source/text/scalc/guide.po
index 57e3c2e7f93..51ba92f155d 100644
--- a/source/sl/helpcontent2/source/text/scalc/guide.po
+++ b/source/sl/helpcontent2/source/text/scalc/guide.po
@@ -3,14 +3,14 @@ msgid ""
 msgstr ""
 "Project-Id-Version: LibreOffice 24.02
"
 "Report-Msgid-Bugs-To: 

core.git: translations

2024-01-10 Thread Martin Srebotnjak (via logerrit)
 translations |2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

New commits:
commit 3cb1ed4339fc9aec414c0f112a69705a7a4d9cc6
Author: Martin Srebotnjak 
AuthorDate: Wed Jan 10 22:29:15 2024 +0100
Commit: Gerrit Code Review 
CommitDate: Wed Jan 10 22:29:15 2024 +0100

Update git submodules

* Update translations from branch 'master'
  to ed9d06780a198a3532adfafadd64557a46f4da3f
  - Updated Slovenian translation

Change-Id: I99b8b0cffd064360ec5b3c36671a63c5598a992f

diff --git a/translations b/translations
index 78265f842d85..ed9d06780a19 16
--- a/translations
+++ b/translations
@@ -1 +1 @@
-Subproject commit 78265f842d856fa49ab84fa2d190323df3773d29
+Subproject commit ed9d06780a198a3532adfafadd64557a46f4da3f


translations.git: source/sl

2024-01-10 Thread Martin Srebotnjak (via logerrit)
 source/sl/helpcontent2/source/text/sbasic/shared/03.po|4 
 source/sl/helpcontent2/source/text/scalc/00.po|4 
 source/sl/helpcontent2/source/text/scalc/01.po|4 
 source/sl/helpcontent2/source/text/scalc/guide.po |4 
 source/sl/helpcontent2/source/text/sdraw/01.po|4 
 source/sl/helpcontent2/source/text/shared/00.po   |4 
 source/sl/helpcontent2/source/text/shared/01.po   |4 
 source/sl/helpcontent2/source/text/shared/guide.po|   14 +
 source/sl/helpcontent2/source/text/shared/help.po |4 
 source/sl/helpcontent2/source/text/smath/01.po|4 
 source/sl/helpcontent2/source/text/swriter.po |   10 -
 source/sl/helpcontent2/source/text/swriter/00.po  |4 
 source/sl/officecfg/registry/data/org/openoffice/Office/UI.po |8 
 source/sl/sc/messages.po  |   26 ++-
 source/sl/scp2/source/ooo.po  |   22 ++
 source/sl/sd/messages.po  |   86 +-
 source/sl/svtools/messages.po |4 
 source/sl/svx/messages.po |4 
 source/sl/uui/messages.po |4 
 19 files changed, 127 insertions(+), 91 deletions(-)

New commits:
commit ed9d06780a198a3532adfafadd64557a46f4da3f
Author: Martin Srebotnjak 
AuthorDate: Wed Jan 10 22:29:08 2024 +0100
Commit: Andras Timar 
CommitDate: Wed Jan 10 22:29:08 2024 +0100

Updated Slovenian translation

Change-Id: I99b8b0cffd064360ec5b3c36671a63c5598a992f

diff --git a/source/sl/helpcontent2/source/text/sbasic/shared/03.po 
b/source/sl/helpcontent2/source/text/sbasic/shared/03.po
index 0e423c8c4fc..ddd98c2f24d 100644
--- a/source/sl/helpcontent2/source/text/sbasic/shared/03.po
+++ b/source/sl/helpcontent2/source/text/sbasic/shared/03.po
@@ -3,14 +3,14 @@ msgid ""
 msgstr ""
 "Project-Id-Version: LibreOffice 24.02
"
 "Report-Msgid-Bugs-To: 
https://bugs.libreoffice.org/enter_bug.cgi?product=LibreOffice_status=UNCONFIRMED=UI
"
-"POT-Creation-Date: 2023-12-23 09:15+0100
"
+"POT-Creation-Date: 2024-01-10 16:22+0100
"
 "PO-Revision-Date: 2023-12-29 15:13+0200
"
 "Last-Translator: Martin Srebotnjak 
"
 "Language-Team: sl.libreoffice.org
"
-"Language: sl
"
 "MIME-Version: 1.0
"
 "Content-Type: text/plain; charset=UTF-8
"
 "Content-Transfer-Encoding: 8bit
"
+"Language: sl
"
 "Plural-Forms: nplurals=4; plural=(n%100==1 ? 0 : n%100==2 ? 1 : n%100==3 || 
n%100==4 ? 2 : 3);
"
 "X-Generator: Virtaal 0.7.1
"
 "X-Accelerator-Marker: ~
"
diff --git a/source/sl/helpcontent2/source/text/scalc/00.po 
b/source/sl/helpcontent2/source/text/scalc/00.po
index 05601e4f251..629e295d1f2 100644
--- a/source/sl/helpcontent2/source/text/scalc/00.po
+++ b/source/sl/helpcontent2/source/text/scalc/00.po
@@ -3,14 +3,14 @@ msgid ""
 msgstr ""
 "Project-Id-Version: LibreOffice 24.02
"
 "Report-Msgid-Bugs-To: 
https://bugs.libreoffice.org/enter_bug.cgi?product=LibreOffice_status=UNCONFIRMED=UI
"
-"POT-Creation-Date: 2023-12-23 09:15+0100
"
+"POT-Creation-Date: 2024-01-10 16:22+0100
"
 "PO-Revision-Date: 2023-12-27 23:35+0200
"
 "Last-Translator: Martin Srebotnjak 
"
 "Language-Team: sl.libreoffice.org
"
-"Language: sl
"
 "MIME-Version: 1.0
"
 "Content-Type: text/plain; charset=UTF-8
"
 "Content-Transfer-Encoding: 8bit
"
+"Language: sl
"
 "Plural-Forms: nplurals=4; plural=(n%100==1 ? 0 : n%100==2 ? 1 : n%100==3 || 
n%100==4 ? 2 : 3);
"
 "X-Generator: Virtaal 0.7.1
"
 "X-Accelerator-Marker: ~
"
diff --git a/source/sl/helpcontent2/source/text/scalc/01.po 
b/source/sl/helpcontent2/source/text/scalc/01.po
index aecb9465fdb..bd57cd6fb35 100644
--- a/source/sl/helpcontent2/source/text/scalc/01.po
+++ b/source/sl/helpcontent2/source/text/scalc/01.po
@@ -3,14 +3,14 @@ msgid ""
 msgstr ""
 "Project-Id-Version: LibreOffice 24.02
"
 "Report-Msgid-Bugs-To: 
https://bugs.libreoffice.org/enter_bug.cgi?product=LibreOffice_status=UNCONFIRMED=UI
"
-"POT-Creation-Date: 2023-12-23 09:15+0100
"
+"POT-Creation-Date: 2024-01-10 16:22+0100
"
 "PO-Revision-Date: 2023-12-28 13:25+0200
"
 "Last-Translator: Martin Srebotnjak 
"
 "Language-Team: sl.libreoffice.org
"
-"Language: sl
"
 "MIME-Version: 1.0
"
 "Content-Type: text/plain; charset=UTF-8
"
 "Content-Transfer-Encoding: 8bit
"
+"Language: sl
"
 "Plural-Forms: nplurals=4; plural=(n%100==1 ? 0 : n%100==2 ? 1 : n%100==3 || 
n%100==4 ? 2 : 3);
"
 "X-Generator: Virtaal 0.7.1
"
 "X-Accelerator-Marker: ~
"
diff --git a/source/sl/helpcontent2/source/text/scalc/guide.po 
b/source/sl/helpcontent2/source/text/scalc/guide.po
index 57e3c2e7f93..51ba92f155d 100644
--- a/source/sl/helpcontent2/source/text/scalc/guide.po
+++ b/source/sl/helpcontent2/source/text/scalc/guide.po
@@ -3,14 +3,14 @@ msgid ""
 msgstr ""
 "Project-Id-Version: LibreOffice 24.02
"
 "Report-Msgid-Bugs-To: 

[Bug 158878] Fillable PDF form exported from LibreOffice Writer unstable and crashes Adobe when clicked on

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

Stéphane Guillou (stragu)  changed:

   What|Removed |Added

 Status|UNCONFIRMED |NEEDINFO
 Ever confirmed|0   |1

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

[Bug 159096] Comment indicator in Calc should be red, not magenta

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

--- Comment #6 from Telesto  ---
(In reply to Heiko Tietze from comment #4)
> The border (as well the color) depend on light/dark theme. Feel free to make
> a proposal.

Regarding to the triangle line color. I observe the following

Light Mode (Tools -> Options -> Application colors -> Light)
A) Without background color: Triangle with black lines
B) With background color: Triangle with black lines

Dark-Mode (Tools -> Options -> Application colors -> Dark)
AA) Without background color: Triangle border: white line
BB) With background color: No triangle border: transparent; expected white
line)

Case BB appears to be inconsistent compared to all other cases; no border.
However it does look pretty nice, IMHO. Maybe case A & B should act as BB;
transparent line 

---
Ps. no clue how the dark-color stuff functions. Is it simply the inverse of
black? Or some complex logic? I don't really grasp why there is a difference
between case AA and BB. I would have expected white line in both cases...

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

[Bug 159096] Comment indicator in Calc should be red, not magenta

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

--- Comment #6 from Telesto  ---
(In reply to Heiko Tietze from comment #4)
> The border (as well the color) depend on light/dark theme. Feel free to make
> a proposal.

Regarding to the triangle line color. I observe the following

Light Mode (Tools -> Options -> Application colors -> Light)
A) Without background color: Triangle with black lines
B) With background color: Triangle with black lines

Dark-Mode (Tools -> Options -> Application colors -> Dark)
AA) Without background color: Triangle border: white line
BB) With background color: No triangle border: transparent; expected white
line)

Case BB appears to be inconsistent compared to all other cases; no border.
However it does look pretty nice, IMHO. Maybe case A & B should act as BB;
transparent line 

---
Ps. no clue how the dark-color stuff functions. Is it simply the inverse of
black? Or some complex logic? I don't really grasp why there is a difference
between case AA and BB. I would have expected white line in both cases...

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

[Bug 159098] Have to click twice for (second and next) border

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

--- Comment #2 from LeroyG  ---
(In reply to Jens-D Doll from comment #0)
> For removing the upper border I
> have to click only once on the line. But if I remove the right border I have
> to click twice. This is also necessary if I remove the lower border.

As a workaround, you can choose the "no border" preset button, and click on the
left border once.

Not a bug, for me.

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

[Bug 159098] Have to click twice for (second and next) border

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

LeroyG  changed:

   What|Removed |Added

Summary|Have to click twice for |Have to click twice for
   |border  |(second and next) border

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

[Bug 159104] Scrolling in Print Preview out of Order

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

LeroyG  changed:

   What|Removed |Added

 Status|UNCONFIRMED |NEEDINFO
 Ever confirmed|0   |1

--- Comment #1 from LeroyG  ---
(In reply to Jens-D Doll from comment #0)
> the page up/down keys [...] do not work at all how they should
Can you describe how do they work for you? Please share the zoom level, and how
much of the page/s do you see.
Also share your LibreOffice details (menu Help - About). After that, change the
bug status from Needinfo to Unconfirmed. Thanks.

For me, if two complete pages are previewed (45% zoom level),
- both the up/down arrows keys and page up/down keys jumps to the next pair of
pages (1-2, 3-4, etc.);
- left/right arrow keys jumps to the next page (1, 2, down to 3, 4, etc).

If the screen matches the width of two pages (80% zoom level) page up/down keys
jumps to the next screen by pair of pages (top of 1-2, bottom of 1-2 and top of
3-4, middle of 3-4, etc.).

If part of the width of two pages do not enter in the screen (100% zoom level),
- page up/down keys behave the same as described in the previous paragraph;
- down arrow key jumps following the left pages (1, 3, 5), while right pages
are partly viewed;
- up arrow key jumps following the right pages (6, 4, 2), and page 1 (from
which is seen only its right side);
- right arrow key jumps to the next page (1, 2, down to 3, 4, etc.), but even
pages (2, 4, etc.) are only partly shown;
- left arrow key jumps to the previows page (6, 5, 4, 3, etc.), but odd pages
are partly shown, including page 1 (I must to press down and up arrow keys to
see the left part of page 1).

Version: 7.5.9.2 (X86_64) / LibreOffice Community
Build ID: cdeefe45c17511d326101eed8008ac4092f278a9
CPU threads: 2; OS: Windows 10.0 Build 22621; UI render: Skia/Vulkan; VCL: win
Locale: es-ES (es_ES); UI: es-ES
Calc: CL threaded

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

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

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

Stéphane Guillou (stragu)  changed:

   What|Removed |Added

 Depends on||15


Referenced Bugs:

https://bugs.documentfoundation.org/show_bug.cgi?id=15
[Bug 15] Not able to scroll up/down with the mouse cursor hovering above a
text box form control
-- 
You are receiving this mail because:
You are the assignee for the bug.

[Bug 158888] Not able to scroll up/down with the mouse cursor hovering above a text box form control

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

Stéphane Guillou (stragu)  changed:

   What|Removed |Added

 CC||libreoffice-ux-advise@lists
   ||.freedesktop.org,
   ||stephane.guillou@libreoffic
   ||e.org
 Blocks||107742
 Status|UNCONFIRMED |NEW
 Ever confirmed|0   |1
Summary|Not able to scroll up/down  |Not able to scroll up/down
   |with the mouse cursor   |with the mouse cursor
   |hoovering above a field |hovering above a text box
   ||form control
   Keywords||needsUXEval

--- Comment #4 from Stéphane Guillou (stragu) 
 ---
Even if the Text Box control contains enough lines to overflow its height, the
scroll doesn't move the text.
So definitely something wrong here.

My expectation would be:
- if there is no content to scroll inside the text box, scroll the whole page
- if there is content to scroll inside the text box, scroll the content

A bit like web browsers do.

UX/Design team, would you agree?

Tested in 6.0.0.3 and recent trunk build:

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


Referenced Bugs:

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

[Bug 158888] Not able to scroll up/down with the mouse cursor hovering above a text box form control

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

Stéphane Guillou (stragu)  changed:

   What|Removed |Added

 CC||libreoffice-ux-advise@lists
   ||.freedesktop.org,
   ||stephane.guillou@libreoffic
   ||e.org
 Blocks||107742
 Status|UNCONFIRMED |NEW
 Ever confirmed|0   |1
Summary|Not able to scroll up/down  |Not able to scroll up/down
   |with the mouse cursor   |with the mouse cursor
   |hoovering above a field |hovering above a text box
   ||form control
   Keywords||needsUXEval

--- Comment #4 from Stéphane Guillou (stragu) 
 ---
Even if the Text Box control contains enough lines to overflow its height, the
scroll doesn't move the text.
So definitely something wrong here.

My expectation would be:
- if there is no content to scroll inside the text box, scroll the whole page
- if there is content to scroll inside the text box, scroll the content

A bit like web browsers do.

UX/Design team, would you agree?

Tested in 6.0.0.3 and recent trunk build:

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


Referenced Bugs:

https://bugs.documentfoundation.org/show_bug.cgi?id=107742
[Bug 107742] [META] Form control bugs and enhancements
-- 
You are receiving this mail because:
You are on the CC list for the bug.

[Bug 159096] Comment indicator in Calc should be red, not magenta

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

--- Comment #5 from LeroyG  ---
I think that it is good to have a contrasting border color, at least in two
sides, especially for when there is an application background color.

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

[Bug 159096] Comment indicator in Calc should be red, not magenta

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

--- Comment #5 from LeroyG  ---
I think that it is good to have a contrasting border color, at least in two
sides, especially for when there is an application background color.

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

[Bug 159086] UI Checkboxes under GTK3 not disabled when settings are locked down from config

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

--- Comment #2 from Caolán McNamara  ---
https://gerrit.libreoffice.org/c/core/+/161899 should resolve this and work as
a guide if it turns up in other places where it didn't matter until now

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

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

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

--- Comment #30 from Jim Raykowski  ---
(In reply to Heiko Tietze from comment #29)
> I suggest to change the default and have the new cross reference via plain
> DnD. Actually I wonder how the modifiers work together with the popup menu -
1:30 of attachment 191834 shows how the Shift modifier changes the DnD to a
cross-reference insert. Notice the 'default' drag is set to "Insert as Section
Link" before the drag but when the Shift modifier is used during the drag it
overrides the default to be a cross-reference insert.

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

[Bug 159086] UI Checkboxes under GTK3 not disabled when settings are locked down from config

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

Caolán McNamara  changed:

   What|Removed |Added

 Status|UNCONFIRMED |NEW
 Ever confirmed|0   |1

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

[Bug 159115] FORMATTING: pdf with incorrect location of logo

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

--- Comment #1 from Kurt Roeckx  ---
Created attachment 191857
  --> https://bugs.documentfoundation.org/attachment.cgi?id=191857=edit
pdf with problem

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

[Bug 159115] New: FORMATTING: pdf with incorrect location of logo

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

Bug ID: 159115
   Summary: FORMATTING: pdf with incorrect location of logo
   Product: LibreOffice
   Version: 7.6.4.1 release
  Hardware: All
OS: All
Status: UNCONFIRMED
  Severity: normal
  Priority: medium
 Component: Draw
  Assignee: libreoffice-bugs@lists.freedesktop.org
  Reporter: k...@roeckx.be

Description:
The PDF that I will attach shortly renders incorrectly. At least the logo is is
there 4 times instead of 1.

There is also some wrong text, but I assume that they did some weird font
thing.

Steps to Reproduce:
Open the pdf

Actual Results:
multiple logos, at wrong location

Expected Results:
only 1 logo at the correct location


Reproducible: Always


User Profile Reset: No

Additional Info:
display the logo only once at the correct location

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

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

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

Rafael Lima  changed:

   What|Removed |Added

 Depends on||158749


Referenced Bugs:

https://bugs.documentfoundation.org/show_bug.cgi?id=158749
[Bug 158749] Basic IDE should have a "Go to line" dialog when clicking the line
number in the status bar
-- 
You are receiving this mail because:
You are the assignee for the bug.

[Bug 158749] Basic IDE should have a "Go to line" dialog when clicking the line number in the status bar

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

Rafael Lima  changed:

   What|Removed |Added

 Blocks||124891


Referenced Bugs:

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

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

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

Rafael Lima  changed:

   What|Removed |Added

 Depends on||158750


Referenced Bugs:

https://bugs.documentfoundation.org/show_bug.cgi?id=158750
[Bug 158750] Basic editor should highlight the line where the cursor is
positioned
-- 
You are receiving this mail because:
You are the assignee for the bug.

  1   2   3   4   >