Re: GSoC'23 project

2023-03-28 Thread Ilmari Lauhakangas

On 28.3.2023 18.20, Spruha Thorat wrote:

Hi,
I am Spruha Thorat  from IIIT Vadodara , currently studying in 2nd year 
of B.Tech in CSE.
I want to contribute to the project 'Convert Writer's Java UNO API tests 
to C++'.

I want to know if it's still open for contribution or not ?
  I would like some guidance before starting  with the project.


You can submit proposals until 4 April. Check the deadlines and remember 
to also solve a difficultyInteresting easy hack: 
https://wiki.documentfoundation.org/Development/GSoC/2023#Important_dates


You can keep submitting updated versions of your proposal until the 4 
April deadline, if you want to improve it based on feedback from mentors.


Ilmari


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

2023-03-28 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=150915
Bug 150915 depends on bug 154313, which changed state.

Bug 154313 Summary: Writer drop-down menus are colored black
https://bugs.documentfoundation.org/show_bug.cgi?id=154313

   What|Removed |Added

 Status|UNCONFIRMED |RESOLVED
 Resolution|--- |WONTFIX

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

[Libreoffice-bugs] [Bug 154313] Writer drop-down menus are colored black

2023-03-28 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=154313

V Stuart Foote  changed:

   What|Removed |Added

 Status|UNCONFIRMED |RESOLVED
 Resolution|--- |WONTFIX

--- Comment #4 from V Stuart Foote  ---
Sorry, nothing to be done for 7.4 and already corrected for LO 7.5

Upgrade to LO 7.5.2 just released.

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

[Libreoffice-ux-advise] [Bug 154429] Suggestions for Default settings for new installs

2023-03-28 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=154429

V Stuart Foote  changed:

   What|Removed |Added

 Resolution|NOTABUG |---
   Severity|normal  |enhancement
   Keywords||needsUXEval
 Status|RESOLVED|UNCONFIRMED
 CC||libreoffice-ux-advise@lists
   ||.freedesktop.org

--- Comment #4 from V Stuart Foote  ---
Sure BZ is fine for that, we'll make it an actual enhancement, A.k.a RFE as
there is no bug here, and there is literally nothing actionable in this
request!

Your specific issue was with the handling of image anchor--clearly documented,
RTM.

Flesh your suggestion out, I'm certainly not going to put any effort into what
IMHO is a complete waste of design and dev effort.

But, would strongly suggest you spend some time working in LibreOffice before
you start saying it needs to work like MS Office does, oh, and again please
RTM--there are links from the Help menu, and a useful WiKi.

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

[Libreoffice-bugs] [Bug 154429] Suggestions for Default settings for new installs

2023-03-28 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=154429

V Stuart Foote  changed:

   What|Removed |Added

 Resolution|NOTABUG |---
   Severity|normal  |enhancement
   Keywords||needsUXEval
 Status|RESOLVED|UNCONFIRMED
 CC||libreoffice-ux-advise@lists
   ||.freedesktop.org

--- Comment #4 from V Stuart Foote  ---
Sure BZ is fine for that, we'll make it an actual enhancement, A.k.a RFE as
there is no bug here, and there is literally nothing actionable in this
request!

Your specific issue was with the handling of image anchor--clearly documented,
RTM.

Flesh your suggestion out, I'm certainly not going to put any effort into what
IMHO is a complete waste of design and dev effort.

But, would strongly suggest you spend some time working in LibreOffice before
you start saying it needs to work like MS Office does, oh, and again please
RTM--there are links from the Help menu, and a useful WiKi.

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

[Libreoffice-bugs] [Bug 154438] Libreoffice headless exporting html to pdf or docx ignore canvas html element

2023-03-28 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=154438

--- Comment #3 from dspand...@outlook.com ---
Created attachment 186276
  --> https://bugs.documentfoundation.org/attachment.cgi?id=186276=edit
output generated by libre as pdf

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

[Libreoffice-bugs] [Bug 154438] Libreoffice headless exporting html to pdf or docx ignore canvas html element

2023-03-28 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=154438

--- Comment #2 from dspand...@outlook.com ---
Created attachment 186275
  --> https://bugs.documentfoundation.org/attachment.cgi?id=186275=edit
output generated by libre as docs

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

[Libreoffice-bugs] [Bug 154438] Libreoffice headless exporting html to pdf or docx ignore canvas html element

2023-03-28 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=154438

--- Comment #1 from dspand...@outlook.com ---
Created attachment 186274
  --> https://bugs.documentfoundation.org/attachment.cgi?id=186274=edit
attached sample html docs

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

[Libreoffice-bugs] [Bug 154438] Libreoffice headless exporting html to pdf or docx ignore canvas html element

2023-03-28 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=154438

dspand...@outlook.com changed:

   What|Removed |Added

 Ever confirmed|0   |1
 Status|UNCONFIRMED |NEW

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

[Libreoffice-bugs] [Bug 154438] Libreoffice headless exporting html to pdf or docx ignore canvas html element

2023-03-28 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=154438

dspand...@outlook.com changed:

   What|Removed |Added

Summary|Libreoffice headless|Libreoffice headless
   |exporting html to pdf   |exporting html to pdf or
   |ignore canvas html element  |docx ignore canvas html
   ||element

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

[Libreoffice-bugs] [Bug 154438] New: Libreoffice headless exporting html to pdf ignore canvas html element

2023-03-28 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=154438

Bug ID: 154438
   Summary: Libreoffice headless exporting html to pdf ignore
canvas html element
   Product: LibreOffice
   Version: 7.5.1.2 release
  Hardware: x86-64 (AMD64)
OS: macOS (All)
Status: UNCONFIRMED
  Severity: normal
  Priority: medium
 Component: Writer
  Assignee: libreoffice-bugs@lists.freedesktop.org
  Reporter: dspand...@outlook.com

Description:
I am trying to convert a html file into a pdf using below headless mode command
TO PDF:
soffice --headless --infilter=writerglobal8_HTML  --convert-to
pdf:"writer_pdf_Export" --outdir /Users/dspandian-rc/Downloads
/Users/dspandian-rc/Downloads/sample1.html


TO WORD:
soffice --headless --infilter=writerglobal8_HTML  --convert-to
pdf:"writer_pdf_Export" --outdir /Users/dsp/Downloads
/Users/dsp/Downloads/sample1.html

Files used are in my one drive. I attached out put files as well.

https://1drv.ms/f/s!As1jbBIP1BYU3ncBTfhSzVcbyVb6?e=0Cm88c 

Steps to Reproduce:
1. put sample1.html file in downloads folder
2. run the above command from desc 
3. open the generated output file. 

Actual Results:
Canvas not displayed

Expected Results:
Canvas should be displayed below the table. open the html in browser and you
will see canvas with border and a line drawn in web page


Reproducible: Always


User Profile Reset: Yes

Additional Info:
it ignored the canvas element. it should have rendered and created a drawing in
docx or pdf too

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

[Libreoffice-bugs] [Bug 154170] LibO on Linux makes image cropping dependent on Xorg font dpi settings.

2023-03-28 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=154170

QA Administrators  changed:

   What|Removed |Added

 Whiteboard|| QA:needsComment

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

[Libreoffice-bugs] [Bug 154187] Allow for static assignment of comment background color to a user

2023-03-28 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=154187

QA Administrators  changed:

   What|Removed |Added

 Whiteboard|| QA:needsComment

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

[Libreoffice-bugs] [Bug 154313] Writer drop-down menus are colored black

2023-03-28 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=154313

QA Administrators  changed:

   What|Removed |Added

 Ever confirmed|1   |0
 Status|NEEDINFO|UNCONFIRMED

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

[Libreoffice-bugs] [Bug 154313] Writer drop-down menus are colored black

2023-03-28 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=154313

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

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

[Libreoffice-ux-advise] [Bug 147232] Improvement of CALC diagrams

2023-03-28 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=147232

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

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

[Libreoffice-ux-advise] [Bug 147232] Improvement of CALC diagrams

2023-03-28 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=147232

QA Administrators  changed:

   What|Removed |Added

 Ever confirmed|1   |0
 Status|NEEDINFO|UNCONFIRMED

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

[Libreoffice-bugs] [Bug 147232] Improvement of CALC diagrams

2023-03-28 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=147232

QA Administrators  changed:

   What|Removed |Added

 Ever confirmed|1   |0
 Status|NEEDINFO|UNCONFIRMED

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

[Libreoffice-bugs] [Bug 147232] Improvement of CALC diagrams

2023-03-28 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=147232

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

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

[Libreoffice-bugs] [Bug 145558] reproducible Crash: VBA insert graphic, save, crash

2023-03-28 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=145558

QA Administrators  changed:

   What|Removed |Added

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

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

[Libreoffice-bugs] [Bug 144508] Detached side menu off-screen can't be returned to visible area

2023-03-28 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=144508

QA Administrators  changed:

   What|Removed |Added

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

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

[Libreoffice-bugs] [Bug 145558] reproducible Crash: VBA insert graphic, save, crash

2023-03-28 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=145558

--- Comment #7 from QA Administrators  ---
Dear daniel.heiserer,

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.

[Libreoffice-bugs] [Bug 144508] Detached side menu off-screen can't be returned to visible area

2023-03-28 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=144508

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

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.

[Libreoffice-bugs] [Bug 151098] lists from same document look different on Windows than on Linux

2023-03-28 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=151098

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

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

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

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

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

Warm Regards,
QA Team

MassPing-NeedInfo-Ping

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

[Libreoffice-bugs] [Bug 150684] Heading Hyperlinks lost when new heading added

2023-03-28 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=150684

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

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

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

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

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

Warm Regards,
QA Team

MassPing-NeedInfo-Ping

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

[Libreoffice-bugs] [Bug 97747] Writer hangs on large table copied from html page

2023-03-28 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=97747

--- Comment #9 from QA Administrators  ---
Dear Jos van den Oever,

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

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

If you have time, please do the following:

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

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

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

Please DO NOT

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


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

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


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

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

Warm Regards,
QA Team

MassPing-UntouchedBug

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

[Libreoffice-bugs] [Bug 88895] Rotated text (via Character or Paragraph Position) in table expands cell instead of flowing down

2023-03-28 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=88895

--- Comment #14 from QA Administrators  ---
Dear Timur,

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

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

If you have time, please do the following:

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

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

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

Please DO NOT

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


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

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


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

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

Warm Regards,
QA Team

MassPing-UntouchedBug

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

[Libreoffice-bugs] [Bug 84907] VIEWING: No border line to separate tab sections and slide

2023-03-28 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=84907

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

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

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

If you have time, please do the following:

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

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

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

Please DO NOT

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


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

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


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

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

Warm Regards,
QA Team

MassPing-UntouchedBug

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

[Libreoffice-bugs] [Bug 59121] Redo/Undo looses bookmark

2023-03-28 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=59121

--- Comment #10 from QA Administrators  ---
Dear Christoph Lutz,

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

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

If you have time, please do the following:

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

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

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

Please DO NOT

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


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

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


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

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

Warm Regards,
QA Team

MassPing-UntouchedBug

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

[Libreoffice-bugs] [Bug 50504] EDITING: Can not add characters at the beginning of a cell which have a very long first line

2023-03-28 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=50504

--- Comment #10 from QA Administrators  ---
Dear pierre-louis.bonicoli,

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

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

If you have time, please do the following:

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

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

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

Please DO NOT

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


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

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


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

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

Warm Regards,
QA Team

MassPing-UntouchedBug

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

[Libreoffice-bugs] [Bug 50202] FORMATTING: Rotated RTL text mixed with numbers produces complete mess

2023-03-28 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=50202

--- Comment #15 from QA Administrators  ---
Dear Pavel R,

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

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

If you have time, please do the following:

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

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

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

Please DO NOT

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


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

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


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

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

Warm Regards,
QA Team

MassPing-UntouchedBug

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

[Libreoffice-bugs] [Bug 119976] Allow scrolling with mouse wheel while LibreOffice doesn't have focus (KDE with GTK3)

2023-03-28 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=119976

--- Comment #25 from QA Administrators  ---
Dear Manuel Vögele,

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

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

If you have time, please do the following:

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

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

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

Please DO NOT

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


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

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


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

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

Warm Regards,
QA Team

MassPing-UntouchedBug

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

[Libreoffice-bugs] [Bug 108764] LibreOffice Writer and PDF export don’t respect the SVG 'crispEdges' value for the shape-rendering attribute

2023-03-28 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=108764

--- Comment #14 from QA Administrators  ---
Dear miikka.salminen,

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

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

If you have time, please do the following:

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

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

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

Please DO NOT

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


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

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


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

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

Warm Regards,
QA Team

MassPing-UntouchedBug

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

[Libreoffice-bugs] [Bug 106620] Glued lines are not perfectly aligned

2023-03-28 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=106620

--- Comment #8 from QA Administrators  ---
Dear Martin Marmsoler,

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

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

If you have time, please do the following:

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

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

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

Please DO NOT

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


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

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


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

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

Warm Regards,
QA Team

MassPing-UntouchedBug

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

[Libreoffice-bugs] [Bug 154437] Draw rename still uses "Slide" instead of "Page"

2023-03-28 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=154437

Baole Fang  changed:

   What|Removed |Added

   Assignee|libreoffice-b...@lists.free |baole.f...@gmail.com
   |desktop.org |

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

[Libreoffice-bugs] [Bug 154437] New: Draw rename still uses "Slide" instead of "Page"

2023-03-28 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=154437

Bug ID: 154437
   Summary: Draw rename still uses "Slide" instead of "Page"
   Product: LibreOffice
   Version: unspecified
  Hardware: All
OS: All
Status: UNCONFIRMED
  Severity: minor
  Priority: medium
 Component: Draw
  Assignee: libreoffice-bugs@lists.freedesktop.org
  Reporter: baole.f...@gmail.com

Description:
In Draw, when we want to rename a page, it shouldn't be renamed to future pages
because they will be used later as a default. However, the implementation uses
old name "Slide" instead of "Page" when trying to account for this behavior.

Steps to Reproduce:
1.Open Draw
2.Rename the current page to "Slide 2" or any "Slide x" where x is a positive
integer
3.Rename the current page to "Page 2"
4.Add a page

Actual Results:
Rename is prohibitted for "Slide 2"
Rename is allowd for "Page 2"
A new page is added with duplicate name "Page 2"

Expected Results:
Rename should be valid for "Slide 2"
Rename should be prohibitted for "Page 2"
A new page should be added with name "Page 2", which should be unique


Reproducible: Always


User Profile Reset: No

Additional Info:
Version: 7.3.7.2 / LibreOffice Community
Build ID: 30(Build:2)
CPU threads: 12; OS: Linux 5.15; UI render: default; VCL: gtk3
Locale: en-US (en_US.UTF-8); UI: en-US
Ubuntu package version: 1:7.3.7-0ubuntu0.22.04.2
Calc: threaded

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

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

2023-03-28 Thread Eike Rathke (via logerrit)
 i18npool/source/localedata/data/uk_UA.xml |8 
 1 file changed, 4 insertions(+), 4 deletions(-)

New commits:
commit debd5bd5cf86a8e20754c9fa1e69455764beeedb
Author: Eike Rathke 
AuthorDate: Tue Mar 28 22:24:22 2023 +0200
Commit: Adolfo Jayme Barrientos 
CommitDate: Wed Mar 29 02:30:33 2023 +

Resolves: tdf#154433 Correct {uk-UA} quotation mark characters

Change-Id: Id5c251ee632d2da134ffbbb352844152f12c1f77
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/149654
Reviewed-by: Eike Rathke 
Tested-by: Jenkins
(cherry picked from commit 2836aaeccee092d2e809839c5d6cc7656aa2e77b)
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/149611
Reviewed-by: Adolfo Jayme Barrientos 

diff --git a/i18npool/source/localedata/data/uk_UA.xml 
b/i18npool/source/localedata/data/uk_UA.xml
index f3642004dd8e..5912691c9501 100644
--- a/i18npool/source/localedata/data/uk_UA.xml
+++ b/i18npool/source/localedata/data/uk_UA.xml
@@ -42,10 +42,10 @@
р.
 
 
-  ‘
-  ’
-  “
-  ”
+  „
+  “
+  «
+  »
 
 AM
 PM


[Libreoffice-bugs] [Bug 91130] Smaller default font name list

2023-03-28 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=91130

--- Comment #48 from Arlene  ---
(In reply to Ole Tange from comment #46)
> > Feel free to comment on this post about how you(every user of LO) would 
> > like some customization of the font selector.

> On my machine I have not actively added fonts. I have ~250 fonts installed.
Thank you Ole for providing those great ideas!

> When selecting a font I sometimes know what I am looking for. Maybe I know
> it is called something with "Gothic", but I cannot remember that it is
> really called "MS Gothic". In this case it is important for me, that I can
> find the font if I know parts of the name. In other words: Sorting will not
> help me here, because I will be looking under 'G' when I should be looking
> under 'M'. Substring search would be preferably.
Yes! I agree that Substring search would be very useful for users. It is common
that users only remember part of the name of fonts and want to use that memory
to find the font they want. I feel this feature would need to talk with develop
team to see their ideas or constraints in it.

> Other times I am looking for a special look of the font, but have no idea
> what it might be called. For this I need a way to see as many font samples
> on the screen as possible.
It is really great that now LO has this preview feature. Do you have any ideas
in improving it?

> If I write in Thai, it would be important to me that I could choose to only
> show fonts that had Thai letters. I imagine this is a problem for languages,
> too. It would be OK, if this filtering is a bit harder to do (E.g. behind an
> "Advanced" button).
I found several comments in here and other similar bugs that talk about this
feature. A filter or sorting feature can let LO be customized in some certain
way for users. That would be great. Maybe we could welcome more users to
comment here about their ideas for the filter/Sort feature of the font
selector.

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

[Libreoffice-bugs] [Bug 91130] Smaller default font name list

2023-03-28 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=91130

--- Comment #47 from Arlene  ---
(In reply to Heiko Tietze from comment #45)
> (In reply to Arlene from comment #43)
> > 1. More Fonts (thinking...)
> What is this about?
I was thinking about putting the Sort/Filter feature after people click on
this, advanced users can better find what they are looking for. But I am still
in the ideation process and need feedback and ideas.

> > 2. Theme Fonts (3-5 most users familiar fonts)
> The term "Theme" is occupied as a collection of design elements around a
> document. If that's your idea I wonder how to manipulate it.
I think calling it "Popular Fonts" could be less confusing.

> > 3. All Fonts (display alphabetically)
> > 4. Recent Fonts (Only after users have used at least one font will it appear
> > in the font selector. Max 5 most recent fonts here)
> It's most likely that you pick one from the favorite fonts. Would show this
> on top (and All on bottom)
Do you mean "Recent Fonts" at the top, "Favorite Fonts (Popular Fonts)" in the
middle, and "All Fonts" at the bottom?


> In general, the duplication of items (Arial, for instance, is listed in
> Recent, Theme, and All) in the categories bloats the list. Would show it
> only once.
Good point. I understand this would not make users not see the same font repeat
in multiple categories. But my point is the "Recent Fonts" would have only
displayed the most recently used 5 fonts and is in changing with users'
behavior. For example, when a user first used Arial font and then used another
5 fonts, then Arial would not appear on "Recent Fonts" anymore, so I am
thinking about whether it is good that we still keep Arial in both "Recent
Fonts" and "All Fonts" at the same time as "Recent Fonts" list is always
changing.

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

[Libreoffice-bugs] [Bug 150477] "Slide 1 of 1" instead of "Page" in the bottom bar of Draw

2023-03-28 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=150477

Baole Fang  changed:

   What|Removed |Added

 Status|NEW |ASSIGNED
   Assignee|libreoffice-b...@lists.free |baole.f...@gmail.com
   |desktop.org |

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

[Libreoffice-bugs] [Bug 153628] Spellcheck now does not work v7.5.0.3 X86_64

2023-03-28 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=153628

--- Comment #22 from John Glennie  ---
Spellcheck bug now resolved as tests OK

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

[Libreoffice-bugs] [Bug 153628] Spellcheck now does not work v7.5.0.3 X86_64

2023-03-28 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=153628

--- Comment #21 from John Glennie  ---
Created attachment 186273
  --> https://bugs.documentfoundation.org/attachment.cgi?id=186273=edit
version tests OK

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

[Libreoffice-bugs] [Bug 154436] New: Drag the outer circle in the circle diagram at Libre office impress-text is going outside of the circle

2023-03-28 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=154436

Bug ID: 154436
   Summary: Drag the outer circle in the circle diagram at Libre
office impress-text is going outside of the circle
   Product: LibreOffice
   Version: 7.3.7.2 release
  Hardware: All
OS: Linux (All)
Status: UNCONFIRMED
  Severity: normal
  Priority: medium
 Component: LibreOffice
  Assignee: libreoffice-bugs@lists.freedesktop.org
  Reporter: r.sangeetha2...@gmail.com

Description:
when I dragged a circle in the Libre office impress Gallery the outer circle
text is going outiside

Steps to Reproduce:
1.Go to Libre Office impress and open the file.
2.select the circle image in the gallery
3.Drag that circle in the Libre office impress.If you drag the outer circle the
text is going outside of the circle

Actual Results:
select circle image in the gallery the outer circle text appear at the outside
of the circle

Expected Results:
Text should be appear inside he circle


Reproducible: Always


User Profile Reset: No

Additional Info:
Have to fix that text to be place inside the circle

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

[Libreoffice-bugs] [Bug 147149] VIEWING: In a .docx file, cannot open embedded .ppsx file

2023-03-28 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=147149

--- Comment #6 from measrasy  ---
Thank you for reporting the issue. Please provide us a sample document so that
we can more easily check the bug. https://retrotecmobowl.com

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

[Libreoffice-bugs] [Bug 154416] Words disappear inside shapes

2023-03-28 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=154416

--- Comment #5 from marcgene...@gmail.com ---
Ok, I installed the 7.4.6 version of LibreOffice, and the bug vanished.
No idea what was going on, though...

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

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

2023-03-28 Thread Eike Rathke (via logerrit)
 i18npool/source/localedata/data/uk_UA.xml |8 
 1 file changed, 4 insertions(+), 4 deletions(-)

New commits:
commit 002f941ec20e594e9702c39fab9cf9f4cc392dab
Author: Eike Rathke 
AuthorDate: Tue Mar 28 22:24:22 2023 +0200
Commit: Eike Rathke 
CommitDate: Tue Mar 28 23:11:32 2023 +

Resolves: tdf#154433 Correct {uk-UA} quotation mark characters

Change-Id: Id5c251ee632d2da134ffbbb352844152f12c1f77
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/149654
Reviewed-by: Eike Rathke 
Tested-by: Jenkins

diff --git a/i18npool/source/localedata/data/uk_UA.xml 
b/i18npool/source/localedata/data/uk_UA.xml
index f3642004dd8e..5912691c9501 100644
--- a/i18npool/source/localedata/data/uk_UA.xml
+++ b/i18npool/source/localedata/data/uk_UA.xml
@@ -42,10 +42,10 @@
р.
 
 
-  ‘
-  ’
-  “
-  ”
+  „
+  “
+  «
+  »
 
 AM
 PM


GSoC'23 project

2023-03-28 Thread Spruha Thorat
Hi,
I am Spruha Thorat  from IIIT Vadodara , currently studying in 2nd year of
B.Tech in CSE.
I want to contribute to the project  'Convert Writer's Java UNO API tests
to C++'.
I want to know if it's still open for contribution or not ?
 I would like some guidance before starting  with the project.

Thanks and Regards,
Spruha Thorat.


Re: [libreoffice-marketing] Re: [libreoffice-design] Moving to LibreOffice 8?

2023-03-28 Thread Jorge E. Restrepo
Gentlemen & Gentlewomen...

It's easy to assume a passive role, sit, watch and criticize...

All LibreOffice contributors have been doing more than an extraordinary
job. Lets not cloud our minds with trivial issues. Let's continue moving
forward.

All the best to all...

--
Jorge E. Restrepo

On Tue, Mar 28, 2023, 03:37 Csongor Halmai  wrote:

> I totally understand Italo's frustration. I also hate when I am expected
> to make a decision and people, who were absolutely silent and
> indifferent before, suddenly start to verbalise their opinion, which
> "happens to be" different from mine.
>
> Regarding the version number, I think people who liked 7.x, will continue
> to like 8.x too. The rest may find the big jump attractive enough
> to try it but I believe most of the articles would emphasize "Hey people,
> here is the new version but there is nothing remarkably new in
> it". Which erodes the reputation of the product.
>
> Therefore, I second Eyal's suggestion. Let's keep the new major version
> number for something really big jump.
>
>
> Such a big jump could be an AI integration (like ChatGPT). It could really
> change how people use LO (at least, Writer and Impress)
>
> Csongor
>
>
>
>
>
>
> On 28/03/2023 20:43, Italo Vignoli wrote:
> > I have been asked to provide my opinion by developers, who seem to think
> that the change of version has to be a marketing decision. As I have said
> quite clearly, I am pissed off by the current situation, where I am asked
> to take a decision and then I am blamed because I take one. I leave the
> decision to the community.
> >
> > 28 Mar 2023 08:18:13 Eyal Rozenberg:
> >
> >> I respectfully disagree with Italo.
> >>
> >> First, about the "frame of reference". In my opinion, decisions such as
> major version number bumping are not, first and foremost, marketing
> decisions. That is a _consideration_, since the version number is
> declarative than technical. But - such an action should be "truthful"
> before being "marketable".
> >>
> >> It is more important, in my opinion, that users and potential users
> receive trustworthy signaling from the project - not just w.r.t. version
> numbers, but generally - than for the media to get a gimmick for coverage.
> >>
> >> A second point is that bumping a version number without a major
> innovation moves you a few more steps into the category of, say, Firefox
> and such, where versions just increase automatically with no meaning
> whatsoever. Italo, you said we are perceived as a "real innovator"; well,
> when a real innovator starts having hollow version number bumping, that
> perception fades.
> >>
> >> Finally, everyone who likes the marketing potential of version 8 -
> great, but - keep that benefit for when we have a significant step forward
> to celebrate. Don't squander it.
> >>
> >>
> >> Eyal
> >>
> >> PS:  availability on a new platform is not a reason to bump a version
> number. It's the "same" software, but built for another target, so same
> version as before. IMHO anyway.
> >>
> >>
> >>
> >> On 27/03/2023 20:11, Italo Vignoli wrote:
> >>> Moving to LibreOffice 8 (instead of 7.6) makes sense for marketing
> purposes, as media is looking at LibreOffice as the real innovator in the
> open source office suite market, and the feeling of journalists is that we
> are forever stuck at 7.x.
> >>> We all know that the next version will not include any significant
> innovation which can justify the change of version, apart from the new
> build system for Windows and the availability of LibreOffice for Arm
> processors on Windows (which has not been announced).
> >>> Playing with the number 8, which can be rotated 90° to become the
> "infinite" symbol, we can frame the next version as LibreOffice for an
> infinite number of users, as we cover all hardware platforms and all
> operating systems for personal productivity.
> >>> This is my opinion. If the community wants to stick with 7.6, I won't
> insist. I have received enough insults both public and private for the
> marketing plan, and I am still receiving them from a few people, that I am
> not willing to enter into that process again (even if the decision on the
> "community" tag has not been mine, but it looks like people have a very
> short memory).
> >>> Looking forward to your thoughts.
> >> --
> >> To unsubscribe e-mail to:design+unsubscr...@global.libreoffice.org
> >> Problems?
> https://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/
> >> Posting guidelines + more:
> https://wiki.documentfoundation.org/Netiquette
> >> List archive:https://listarchives.libreoffice.org/global/design/
> >> Privacy Policy:https://www.documentfoundation.org/privacy
> --
> To unsubscribe e-mail to: marketing+unsubscr...@global.libreoffice.org
> Problems?
> https://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/
> Posting guidelines + more: https://wiki.documentfoundation.org/Netiquette
> List archive: https://listarchives.libreoffice.org/global/marketing/
> 

[Libreoffice-bugs] [Bug 154435] In libreoffice calc 7.5.1.2, when exporting a graph image in png format (XY-scatter), the resulting image has captions to the coordinate axes.

2023-03-28 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=154435

Stéphane Guillou (stragu)  changed:

   What|Removed |Added

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

--- Comment #1 from Stéphane Guillou (stragu) 
 ---
This is most likely a duplicate of bug 153672, which is fixed in 7.5.2.
Please test and let us know if it is resolved for you too:
https://www.libreoffice.org/download/download-libreoffice/?type=deb-x86_64=7.5.2=en-US

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

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

[Libreoffice-bugs] [Bug 154434] Writer loses HTML style formating

2023-03-28 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=154434

Shmuel (Seymour J.) Metz  changed:

   What|Removed |Added

   Keywords||filter:html

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

[Libreoffice-bugs] [Bug 154434] Writer loses HTML style formating

2023-03-28 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=154434

--- Comment #2 from Shmuel (Seymour J.) Metz  ---
Created attachment 186272
  --> https://bugs.documentfoundation.org/attachment.cgi?id=186272=edit
Layout in Writer

This is how the HTML file appears when I open it in LibreOffice.

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

[Libreoffice-bugs] [Bug 154434] Writer loses HTML style formating

2023-03-28 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=154434

Shmuel (Seymour J.) Metz  changed:

   What|Removed |Added

 CC||sme...@gmu.edu

--- Comment #1 from Shmuel (Seymour J.) Metz  ---
Created attachment 186271
  --> https://bugs.documentfoundation.org/attachment.cgi?id=186271=edit
Layout in browser

This is how the HTML file displays in Firefox. The images are contained in
../Images, a sibling directory to the one containg the HTML.

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

[Libreoffice-qa] ESC meeting agenda: 2023-03-30 16:00 CET

2023-03-28 Thread Miklos Vajna

Hi,

The prototype agenda is below. Extra items are appreciated either in
this document or as a reply to this mail:

https://pad.documentfoundation.org/p/esc

You can join using Jitsi here:

https://jitsi.documentfoundation.org/esc

Regards,

Miklos

---

* Present:
+

* Completed Action Items:

* Pending Action Items:
  + get marketing to announce the “next version is 8.0” decision on their 
mailing list (Heiko)
  + take the list of certified developers to Italo (Stephan)
  + file an easy hack for faster ui tests (Xisco)

* Release Engineering update (Cloph)
+ 7.5 status: 7.5.2
+ 7.4 status: 7.4.7 rc1 in 3 weeks?

* Documentation (Olivier)
+ Bugzilla Documentation statistics
262(262) bugs open
+ Updates:
BZ changes   1 week1 month3 months   12 months
   created  8(-7) 46(-18)   117(2)  318(0)
 commented 13(-24)   119(-28)   310(10)1091(10)
  resolved  3(0)  15(-12)56(3)  193(1)
+ top 10 contributors:
  Seth Chaiklin made 86 changes in 1 month, and 490 changes in 1 year
  Olivier Hallot made 53 changes in 1 month, and 493 changes in 1 year
  Stéphane Guillou made 29 changes in 1 month, and 155 changes in 1 year
  Kaganski, Mike made 9 changes in 1 month, and 115 changes in 1 year
  Heiko Tietze made 7 changes in 1 month, and 100 changes in 1 year
  Adolfo Jayme Barrientos made 6 changes in 1 month, and 47 changes in 
1 year
  Vernon, Stuart Foote made 6 changes in 1 month, and 39 changes in 1 
year
  Dieter made 5 changes in 1 month, and 71 changes in 1 year
  Vladimir Sokolinskiy made 4 changes in 1 month, and 7 changes in 1 
year
  ady made 3 changes in 1 month, and 5 changes in 1 year

* UX Update (Heiko)
+ Bugzilla (topicUI) statistics
277(277) (topicUI) bugs open, 91(91) (needsUXEval) needs to be 
evaluated by the UXteam
+ Updates:
BZ changes   1 week   1 month   3 months   12 months
 added  8(-2)31(-2)45(-2)  81(-3)
 commented 82(-6)   341(5)714(6) 2290(14)
   removed  2(0)  6(2)  6(2)   29(-1)
  resolved  8(-2)35(-2)94(3)  289(3)
+ top 10 contributors:
  Heiko Tietze made 218 changes in 1 month, and 1447 changes in 1 year
  Eyal Rozenberg made 90 changes in 1 month, and 312 changes in 1 year
  Vernon, Stuart Foote made 63 changes in 1 month, and 262 changes in 1 
year
  Dieter made 57 changes in 1 month, and 219 changes in 1 year
  Ilmari Lauhakangas made 56 changes in 1 month, and 227 changes in 1 
year
  Stéphane Guillou made 48 changes in 1 month, and 201 changes in 1 year
  Rafael Lima made 21 changes in 1 month, and 268 changes in 1 year
  Telesto made 19 changes in 1 month, and 118 changes in 1 year
  Eivind Samseth made 18 changes in 1 month, and 18 changes in 1 year
  Roman Kuznetsov made 16 changes in 1 month, and 179 changes in 1 year

* Crash Testing (Caolan)
+ 78(+43) import failure, 44(+42) export failures
+ ??? coverity issues
+ Google / ossfuzz: ?? fuzzers active now

* Crash Reporting (Xisco)
+ 7.4.6.21323(+674)
+ 7.5.0.2155(+7)
+ 7.5.0.320961(+1935)
+ 7.5.1.26294(+2586)

* Mentoring (Hossein)
  committer...   1 week 1 month 3 months12 months
  open  97(12) 158(11) 167(-4)  173(-4)
   reviews 376(-44)   1530(-68)   3608(96)11764(-10)
merged 308(-1)1419(-60)   3923(110)   14769(72)
 abandoned  28(17)  75(14) 196(24)  723(-99)
   own commits 208(8)  990(-39)   2702(95)10737(25)
review commits  65(-41)397(-14)845(30) 2894(19)
contributor...   1 week 1 month 3 months12 months
  open  21(-12)192(-32)230(1)   239(1)
   reviews 842(2) 3592(-78)   8680(258)   31502(-320)
merged  13(-7)  94(-1) 181(9)   732(6)
 abandoned   6(-2)  33(-6)  88(5)   538(-47)
   own commits  24(-31)172(-1) 329(12)  909(18)
review commits   0(0)0(0)0(0) 0(0)
+ easyHack statistics:
   needsDevEval 9(9)   needsUXEval 1(1)   cleanup_comments 322(322)
   total 385(385)   assigned 26(26)   open 332(332)
+ top 10 contributors:
  Sophia Schroeder made 30 patches in 1 month, and 36 patches in 1 year
  Baole Fang made 8 patches in 1 month, and 8 patches in 1 year
  Armin Le Grand (allotropia) made 8 patches in 1 month, and 51 patches 
in 1 year
  Colomban Wendling made 7 patches in 1 month, and 20 patches in 1 year
  Galdam Jitsu made 5 patches in 1 month, and 10 patches in 1 year
  

ESC meeting agenda: 2023-03-30 16:00 CET

2023-03-28 Thread Miklos Vajna

Hi,

The prototype agenda is below. Extra items are appreciated either in
this document or as a reply to this mail:

https://pad.documentfoundation.org/p/esc

You can join using Jitsi here:

https://jitsi.documentfoundation.org/esc

Regards,

Miklos

---

* Present:
+

* Completed Action Items:

* Pending Action Items:
  + get marketing to announce the “next version is 8.0” decision on their 
mailing list (Heiko)
  + take the list of certified developers to Italo (Stephan)
  + file an easy hack for faster ui tests (Xisco)

* Release Engineering update (Cloph)
+ 7.5 status: 7.5.2
+ 7.4 status: 7.4.7 rc1 in 3 weeks?

* Documentation (Olivier)
+ Bugzilla Documentation statistics
262(262) bugs open
+ Updates:
BZ changes   1 week1 month3 months   12 months
   created  8(-7) 46(-18)   117(2)  318(0)
 commented 13(-24)   119(-28)   310(10)1091(10)
  resolved  3(0)  15(-12)56(3)  193(1)
+ top 10 contributors:
  Seth Chaiklin made 86 changes in 1 month, and 490 changes in 1 year
  Olivier Hallot made 53 changes in 1 month, and 493 changes in 1 year
  Stéphane Guillou made 29 changes in 1 month, and 155 changes in 1 year
  Kaganski, Mike made 9 changes in 1 month, and 115 changes in 1 year
  Heiko Tietze made 7 changes in 1 month, and 100 changes in 1 year
  Adolfo Jayme Barrientos made 6 changes in 1 month, and 47 changes in 
1 year
  Vernon, Stuart Foote made 6 changes in 1 month, and 39 changes in 1 
year
  Dieter made 5 changes in 1 month, and 71 changes in 1 year
  Vladimir Sokolinskiy made 4 changes in 1 month, and 7 changes in 1 
year
  ady made 3 changes in 1 month, and 5 changes in 1 year

* UX Update (Heiko)
+ Bugzilla (topicUI) statistics
277(277) (topicUI) bugs open, 91(91) (needsUXEval) needs to be 
evaluated by the UXteam
+ Updates:
BZ changes   1 week   1 month   3 months   12 months
 added  8(-2)31(-2)45(-2)  81(-3)
 commented 82(-6)   341(5)714(6) 2290(14)
   removed  2(0)  6(2)  6(2)   29(-1)
  resolved  8(-2)35(-2)94(3)  289(3)
+ top 10 contributors:
  Heiko Tietze made 218 changes in 1 month, and 1447 changes in 1 year
  Eyal Rozenberg made 90 changes in 1 month, and 312 changes in 1 year
  Vernon, Stuart Foote made 63 changes in 1 month, and 262 changes in 1 
year
  Dieter made 57 changes in 1 month, and 219 changes in 1 year
  Ilmari Lauhakangas made 56 changes in 1 month, and 227 changes in 1 
year
  Stéphane Guillou made 48 changes in 1 month, and 201 changes in 1 year
  Rafael Lima made 21 changes in 1 month, and 268 changes in 1 year
  Telesto made 19 changes in 1 month, and 118 changes in 1 year
  Eivind Samseth made 18 changes in 1 month, and 18 changes in 1 year
  Roman Kuznetsov made 16 changes in 1 month, and 179 changes in 1 year

* Crash Testing (Caolan)
+ 78(+43) import failure, 44(+42) export failures
+ ??? coverity issues
+ Google / ossfuzz: ?? fuzzers active now

* Crash Reporting (Xisco)
+ 7.4.6.21323(+674)
+ 7.5.0.2155(+7)
+ 7.5.0.320961(+1935)
+ 7.5.1.26294(+2586)

* Mentoring (Hossein)
  committer...   1 week 1 month 3 months12 months
  open  97(12) 158(11) 167(-4)  173(-4)
   reviews 376(-44)   1530(-68)   3608(96)11764(-10)
merged 308(-1)1419(-60)   3923(110)   14769(72)
 abandoned  28(17)  75(14) 196(24)  723(-99)
   own commits 208(8)  990(-39)   2702(95)10737(25)
review commits  65(-41)397(-14)845(30) 2894(19)
contributor...   1 week 1 month 3 months12 months
  open  21(-12)192(-32)230(1)   239(1)
   reviews 842(2) 3592(-78)   8680(258)   31502(-320)
merged  13(-7)  94(-1) 181(9)   732(6)
 abandoned   6(-2)  33(-6)  88(5)   538(-47)
   own commits  24(-31)172(-1) 329(12)  909(18)
review commits   0(0)0(0)0(0) 0(0)
+ easyHack statistics:
   needsDevEval 9(9)   needsUXEval 1(1)   cleanup_comments 322(322)
   total 385(385)   assigned 26(26)   open 332(332)
+ top 10 contributors:
  Sophia Schroeder made 30 patches in 1 month, and 36 patches in 1 year
  Baole Fang made 8 patches in 1 month, and 8 patches in 1 year
  Armin Le Grand (allotropia) made 8 patches in 1 month, and 51 patches 
in 1 year
  Colomban Wendling made 7 patches in 1 month, and 20 patches in 1 year
  Galdam Jitsu made 5 patches in 1 month, and 10 patches in 1 year
  

[Libreoffice-bugs] [Bug 154115] A useless Text Field shows up when typing with Option menu open. prevents Options menu from closing the

2023-03-28 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=154115

Caolán McNamara  changed:

   What|Removed |Added

   Assignee|libreoffice-b...@lists.free |caol...@redhat.com
   |desktop.org |
 Status|NEW |ASSIGNED

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

[Libreoffice-bugs] [Bug 154184] Deactivate "Apply to all similar texts" when changes are made to Entry selection

2023-03-28 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=154184

Stéphane Guillou (stragu)  changed:

   What|Removed |Added

 CC||stephane.guillou@libreoffic
   ||e.org
Version|7.6.0.0 alpha0+ Master  |Inherited From OOo

--- Comment #1 from Stéphane Guillou (stragu) 
 ---
Testing with:

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

I think we need to instead clarify the documentation.

When selecting some text, then modifying the entry and ticking the "Apply to
all other occurrences", it works: all other occurrences of the originally
selected text are indexed at once, and the entry in the index is the one that
was manually changed.

However, when opening the dialog without selected text, that's when the option
is greyed out.

So maybe the documentation should say something like "You cannot use the
function without an associated text selection."

Corresponding help page:
https://help.libreoffice.org/7.6/en-US/text/swriter/01/04120100.html

Same thing in OOo 3.3.0.

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

Re: Bringing theme colors to ODF

2023-03-28 Thread Regina Henschel

Hi Tomaž.

Tomaž Vajngerl schrieb am 25.03.2023 um 11:10:

Hi Regina,

On Thu, Mar 23, 2023 at 6:57 AM Regina Henschel > wrote:


Hi Tomaž, hi all,

I have started with creating a proposal to extend ODF with theme
colors.
The first draft is attached.

Tomaž, could you please look whether it fits to what you have intended.


Yes, looks fine on a quick glance but maybe renaming some things would 
make sense. Mainly the "color-table" would probably be better as 
"color-scheme" or something like that, as this is more in-line with 
OOXML terminology and we don't need to deviate from that just for the 
sake of it


I have an additional question about this.
OOXML has file theme1.xml It has
  

That could become in ODF an element
  

The OOXMML has the child elemnts e.g.
   ...
  ...
   ...

Will all three become a child element of a new  element in ODF?

[The namespace in  is not clear yet, might be  
as well. It is loext anyway now.]


OTOH it probably makes sense to rename dk1, lt1, dk2, lt2, hlink, 
folHlink to the full names dark1, light1, ... , hyperlink, 
followed-hyperlink - which is inline with ODF style to not to abbreviate 
things. I planned to do that change but other things have priority 
currently.


Yes other things are more important, especially UI. I had a talk with 
Heiko about that at the German Community Meeting last weekend. Please 
contact him.


And some bugs have to be fixed.

Kind regards,
Regina


[Libreoffice-bugs] [Bug 42082] [META] Make LibreOffice shine and glow on macOS

2023-03-28 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=42082
Bug 42082 depends on bug 114027, which changed state.

Bug 114027 Summary: [META] LibreOffice from Mac App Store bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=114027

   What|Removed |Added

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

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

[Libreoffice-bugs] [Bug 114027] [META] LibreOffice from Mac App Store bugs and enhancements

2023-03-28 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=114027

Stéphane Guillou (stragu)  changed:

   What|Removed |Added

 CC|stephane.guillou@libreoffic |
   |e.org   |
 Resolution|WONTFIX |---
Summary|[META] Libreoffice Vanilla  |[META] LibreOffice from Mac
   |(Mac Appstore version) bugs |App Store bugs and
   |and enhancements|enhancements
  Alias||Mac-AppStore
 Status|RESOLVED|NEW

--- Comment #3 from Stéphane Guillou (stragu) 
 ---
(In reply to Dennis Roczek from comment #2)
> @stéphane: shouldn't we simply rename it to MacOs Store Version? The same
> problems apply, or?

That's a good point! Let's do that.

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

[Libreoffice-bugs] [Bug 80649] Frame context menu appears on picture when anchored as character, when context menu is started immediately after another picture was selected

2023-03-28 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=80649

--- Comment #18 from Thomas Lendo  ---
Still repro with

Version: 7.3.2.2 / LibreOffice Community
Build ID: 49f2b1bff42cfccbd8f788c8dc32c1c309559be0
CPU threads: 4; OS: Linux 4.15; UI render: default; VCL: gtk3

and

Version: 7.5.1.2 (X86_64) / LibreOffice Community
Build ID: fcbaee479e84c6cd81291587d2ee68cba099e129
CPU threads: 4; OS: Linux 4.15; UI render: default; VCL: gtk3

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

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

2023-03-28 Thread Noel Grandin (via logerrit)
 chart2/source/controller/chartapiwrapper/Chart2ModelContact.cxx  |
3 +-
 chart2/source/controller/chartapiwrapper/Chart2ModelContact.hxx  |
2 -
 chart2/source/controller/chartapiwrapper/WrappedNumberFormatProperty.cxx |
4 ++-
 chart2/source/controller/inc/AxisItemConverter.hxx   |
4 +--
 chart2/source/controller/itemsetwrapper/AxisItemConverter.cxx|
4 +--
 chart2/source/inc/AxisHelper.hxx |
5 
 chart2/source/inc/chartview/ExplicitValueProvider.hxx|
4 +--
 chart2/source/tools/AxisHelper.cxx   |   
11 --
 chart2/source/view/main/ExplicitValueProvider.cxx|
2 -
 9 files changed, 13 insertions(+), 26 deletions(-)

New commits:
commit 90baab0f50bcf35ae29f1841509ecdace9be77db
Author: Noel Grandin 
AuthorDate: Tue Mar 28 14:38:49 2023 +0200
Commit: Noel Grandin 
CommitDate: Tue Mar 28 19:52:51 2023 +

use more concrete types in chart2

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

diff --git a/chart2/source/controller/chartapiwrapper/Chart2ModelContact.cxx 
b/chart2/source/controller/chartapiwrapper/Chart2ModelContact.cxx
index b9ba429433e2..f3ea07e23a3a 100644
--- a/chart2/source/controller/chartapiwrapper/Chart2ModelContact.cxx
+++ b/chart2/source/controller/chartapiwrapper/Chart2ModelContact.cxx
@@ -26,6 +26,7 @@
 #include 
 #include 
 #include 
+#include 
 #include 
 #include 
 #include 
@@ -151,7 +152,7 @@ void Chart2ModelContact::getExplicitValuesForAxis(
 }
 
 sal_Int32 Chart2ModelContact::getExplicitNumberFormatKeyForAxis(
-const Reference< chart2::XAxis >& xAxis )
+const rtl::Reference< ::chart::Axis >& xAxis )
 {
 rtl::Reference< BaseCoordinateSystem > xCooSys(
 AxisHelper::getCoordinateSystemOfAxis(
diff --git a/chart2/source/controller/chartapiwrapper/Chart2ModelContact.hxx 
b/chart2/source/controller/chartapiwrapper/Chart2ModelContact.hxx
index 7a89fb7dd06d..505bc1e144e6 100644
--- a/chart2/source/controller/chartapiwrapper/Chart2ModelContact.hxx
+++ b/chart2/source/controller/chartapiwrapper/Chart2ModelContact.hxx
@@ -75,7 +75,7 @@ public:
 ExplicitIncrementData & rOutExplicitIncrement );
 
 sal_Int32 getExplicitNumberFormatKeyForAxis(
-const css::uno::Reference< css::chart2::XAxis >& xAxis );
+const rtl::Reference< ::chart::Axis >& xAxis );
 
 static sal_Int32 getExplicitNumberFormatKeyForSeries(
 const css::uno::Reference< css::chart2::XDataSeries >& xSeries );
diff --git 
a/chart2/source/controller/chartapiwrapper/WrappedNumberFormatProperty.cxx 
b/chart2/source/controller/chartapiwrapper/WrappedNumberFormatProperty.cxx
index ad8d1c942f4f..971e69a585e4 100644
--- a/chart2/source/controller/chartapiwrapper/WrappedNumberFormatProperty.cxx
+++ b/chart2/source/controller/chartapiwrapper/WrappedNumberFormatProperty.cxx
@@ -19,6 +19,7 @@
 
 #include "WrappedNumberFormatProperty.hxx"
 #include "Chart2ModelContact.hxx"
+#include 
 #include 
 #include 
 #include 
@@ -68,7 +69,8 @@ Any WrappedNumberFormatProperty::getPropertyValue( const 
Reference< beans::XProp
 nKey = Chart2ModelContact::getExplicitNumberFormatKeyForSeries( 
xSeries );
 else
 {
-Reference< chart2::XAxis > xAxis( xInnerPropertySet, 
uno::UNO_QUERY );
+rtl::Reference< Axis > xAxis = 
dynamic_cast(xInnerPropertySet.get());
+assert(xAxis || !xInnerPropertySet);
 nKey = m_spChart2ModelContact->getExplicitNumberFormatKeyForAxis( 
xAxis );
 }
 aRet <<= nKey;
diff --git a/chart2/source/controller/inc/AxisItemConverter.hxx 
b/chart2/source/controller/inc/AxisItemConverter.hxx
index cbb75d2a1db6..c9f3049356a0 100644
--- a/chart2/source/controller/inc/AxisItemConverter.hxx
+++ b/chart2/source/controller/inc/AxisItemConverter.hxx
@@ -27,6 +27,7 @@ namespace com::sun::star::awt { struct Size; }
 namespace com::sun::star::beans { class XPropertySet; }
 namespace com::sun::star::chart2 { class XAxis; }
 namespace com::sun::star::chart2 { class XChartDocument; }
+namespace chart { class Axis; }
 namespace chart { struct ExplicitIncrementData; }
 namespace chart { struct ExplicitScaleData; }
 namespace chart { class ChartModel; }
@@ -60,8 +61,7 @@ protected:
 
 private:
 std::vector< std::unique_ptr >  m_aConverters;
-css::uno::Reference<
-css::chart2::XAxis >  m_xAxis;
+rtl::Reference<::chart::Axis>  m_xAxis;
 
 rtl::Reference<::chart::ChartModel>m_xChartDoc;
 
diff --git a/chart2/source/controller/itemsetwrapper/AxisItemConverter.cxx 
b/chart2/source/controller/itemsetwrapper/AxisItemConverter.cxx
index 20ad1504f018..436e6e29b71e 100644
--- 

[Libreoffice-bugs] [Bug 153422] Writer Table Formula Evaluation Errors

2023-03-28 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=153422

David Alden  changed:

   What|Removed |Added

 Ever confirmed|1   |0
 Status|NEEDINFO|UNCONFIRMED

--- Comment #6 from David Alden  ---
Dear Libre Office Writer QA Administrators,
 Thanks for following up with this bug report.  I'm sorry the explanatory
material included in the attachment was not sufficiently clear.  The attachment
provided (TableDemo1.odt) was derived from an attempt to use the capability of
LO Writer to compute formulas according to US Federal and State income tax
worksheets within tables and fields in an ODF text document.  The income tax
worksheets often require conditional computation of values dependent on other
entered or computed values.  In an attempt to use the LO Writer table formula
capabilities for this purpose, anomalous results were observed from properly
constructed formulas in all currently available versions of LO.  Rows 4-9 in
Table1 of TableDemo1.odt provide examples of both correct and anomalous formula
evaluations each with a brief note  as to what the  value or
formula is intended to demonstrate ( is editable but  are fixed). 
The Table1 formulas in  and  evaluate correctly for all values entered
in , specifically the integers -2, -1, 0, 1, or 2 for demonstration
purposes.  These are the simple  formula: "=+*" and the
conditional  formula "=max((*+)*(g 0)) | (*(leq
0)*3/4)" as shown in the rightmost column at the bottom of the attachment
(TableDemo1.odt) [these active formulas can be verified by hovering the pointer
over the appropriate cells in Table1 ( or )].  The simple  formula
is provided just to demonstrate that common algebraic logic (e.g.,
multiplication has computational precedence over addition) is correctly
implemented without the need for parentheses.  The conditional  formula is
provided to demonstrate that such conditional computation can evaluate
correctly if exhaustive parentheses (i.e., none are left out) are included in
the formula.  The  formula evaluates correctly to either the same value as
 or *3/4 (4258.5) depending on whether cell  is greater than (g)
zero or less than or equal to (leq) zero respectively.  They are shown in the
rightmost column of lines marked 4. and 5. at the bottom of the attachment
document along with the correct expected values (columns 2-6) these formulas
produce for the above mentioned values of  without any highlighted (i.e.,
no anomalies).  So far so good.  However, the exhaustive parentheses should not
be necessary to correctly evaluate the formula in  and when they are
removed, anomalous evaluations of the formula  and  are observed
(expected results are highlighted in yellow at the bottom of the document in
the row labeled 6.).  Note that the "(g 0)" condition has also been removed
for the  and  formulas along with most of the parentheses included in
the  formula to simplify the expression to "=max +* |
*(leq 0)*3/4".  For the two negative values of  and zero, the left
component of the max function will be either 3210,  or 5678 respectively
compared to 4258.5 on the right of the pipe (element separator).  But the 
formula actually evaluates to 9936.5 instead for all three (note that this
value shouldn't even occur at all).  For the two positive values of , the
right hand component of the max function should be zero so only the left hand
component should matter with values 6912 and 8946 respectively but the function
actually evaluates to 5678 instead.  The  function simply reverses the
order of the left hand arithmetic expression, *+ instead of
+*, and the results are even stranger: 1790.5, 3024.5, 4258.5, 1234
and 2468 instead of the expected 4258.5, , 5678, 6912 and 8946 for  -2,
-1, 0, 1 and 2 respectively.  {At this point, please accept my apologies for
the confusion resulting from my copy/paste and editing failure error caused by
playing around with the  and  formulas and neglecting to fix the
results that originally included the (g 0) condition as a part of the left
max component after having removed it from both  and  formulas.  I have
fixed the expected values in the corresponding lines in the replacement
TableDemo1.odt attached below.}  In other words, even without parentheses, the
arithmetic, operator and/or function calculations between the list separators
(pipe characters) should be completed first regardless of how many there are
before evaluating the max function or other functions that take lists (all the
LO Writer "statistical functions", e.g. "=product (min 1|2|3) | (mean 2|4) |
(max 1|3|5|7)" should compute 1*3*7=21 but produces 8 instead--weird 
[generally, the parentheses would usually be necessary to indicate which list
separator goes with which function when the formula contains multiple separate
lists]).  This reasonable expectation is apparently not what 

[Libreoffice-bugs] [Bug 154433] Auto-Replacement gets Ukrainian Quotation Marks wrong

2023-03-28 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=154433

Eike Rathke  changed:

   What|Removed |Added

Version|7.3.2.2 release |Inherited From OOo
   Assignee|libreoffice-b...@lists.free |er...@redhat.com
   |desktop.org |
 Ever confirmed|0   |1
 Status|UNCONFIRMED |ASSIGNED

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

[Libreoffice-bugs] [Bug 117789] Sidebar: New Shapes deck isn't scrollable with touchpad (and maybe mouse wheel)

2023-03-28 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=117789

Thomas Lendo  changed:

   What|Removed |Added

 Status|NEW |RESOLVED
 Resolution|--- |WORKSFORME

--- Comment #4 from Thomas Lendo  ---
Tested now with Version: 7.3.2.2 / LibreOffice Community
Build ID: 49f2b1bff42cfccbd8f788c8dc32c1c309559be0
CPU threads: 4; OS: Linux 4.15; UI render: default; VCL: gtk3

and no problem anymore with a touchpad.

So, closing as Worksforme.

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

[Libreoffice-bugs] [Bug 87643] SIDEBAR: New Shapes Tab and content panels

2023-03-28 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=87643
Bug 87643 depends on bug 117789, which changed state.

Bug 117789 Summary: Sidebar: New Shapes deck isn't scrollable with touchpad 
(and maybe mouse wheel)
https://bugs.documentfoundation.org/show_bug.cgi?id=117789

   What|Removed |Added

 Status|NEW |RESOLVED
 Resolution|--- |WORKSFORME

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

[Libreoffice-ux-advise] [Bug 87643] SIDEBAR: New Shapes Tab and content panels

2023-03-28 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=87643
Bug 87643 depends on bug 117789, which changed state.

Bug 117789 Summary: Sidebar: New Shapes deck isn't scrollable with touchpad 
(and maybe mouse wheel)
https://bugs.documentfoundation.org/show_bug.cgi?id=117789

   What|Removed |Added

 Status|NEW |RESOLVED
 Resolution|--- |WORKSFORME

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

[Libreoffice-bugs] [Bug 154385] Form controls: "automatic" order does not work

2023-03-28 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=154385

--- Comment #7 from Robert Großkopf  ---
(In reply to shoe200 from comment #6)Hi Frank,
> 
> "Set the position for this one field manually in the dialog and all will
> work well for you." - In most cases that doesn't work, a few times it does.
> I couldn't find a rule. In my eyes the handling needs to be improved, it is
> hard to understand. What number do you give to a control between no. 15 and
> no. 16?

There is the dialog for setting "automatic order". In this dialog you could
move elements up and down. You could see many listboxes in this dialog,
followed by check boxes. And then one field, which is numeric. Click on this
numeric field. Press button "move up" for setting this numeric field.

You won't need to switch all this tabs manually.

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

[Libreoffice-bugs] [Bug 153422] Writer Table Formula Evaluation Errors

2023-03-28 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=153422

David Alden  changed:

   What|Removed |Added

 Attachment #185240|0   |1
is obsolete||

--- Comment #5 from David Alden  ---
Created attachment 186270
  --> https://bugs.documentfoundation.org/attachment.cgi?id=186270=edit
Corrected LO Writer formula evaluation demo document

Corrected LO Writer demo document attachment.  Sorry for any confusion.

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

[Libreoffice-bugs] [Bug 154435] New: In libreoffice calc 7.5.1.2, when exporting a graph image in png format (XY-scatter), the resulting image has captions to the coordinate axes.

2023-03-28 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=154435

Bug ID: 154435
   Summary: In libreoffice calc 7.5.1.2, when exporting a graph
image in png format (XY-scatter), the resulting image
has captions to the coordinate axes.
   Product: LibreOffice
   Version: 7.5.1.2 release
  Hardware: All
OS: Linux (All)
Status: UNCONFIRMED
  Severity: minor
  Priority: medium
 Component: Calc
  Assignee: libreoffice-bugs@lists.freedesktop.org
  Reporter: androm...@yandex.ru

Description:
In libreoffice calc 7.5.1.2, when exporting a graph image in png format
(XY-scatter), the resulting image has captions to the coordinate axes.

Steps to Reproduce:
1.create graph in libreoffice calc
2.click right mouse button on the graph and select "export image"
3.choose format PNG

Actual Results:
I got a picture with the coordinate axes gone

Expected Results:
I got a normal picture of the graph


Reproducible: Always


User Profile Reset: No

Additional Info:
...

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

[Libreoffice-bugs] [Bug 154429] Suggestions for Default settings for new installs

2023-03-28 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=154429

--- Comment #3 from markbal...@gmail.com ---
There was no other option to submit a suggestion except to log a bug, I"m not
sure how you get feedback from the public to make the product better, maybe its
not something you do?

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

[Libreoffice-bugs] [Bug 154429] Suggestions for Default settings for new installs

2023-03-28 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=154429

--- Comment #2 from markbal...@gmail.com ---
So you have no track for improvements?

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

[Libreoffice-bugs] [Bug 154434] New: Writer loses HTML style formating

2023-03-28 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=154434

Bug ID: 154434
   Summary: Writer loses HTML style formating
   Product: LibreOffice
   Version: 7.5.1.2 release
  Hardware: All
OS: All
Status: UNCONFIRMED
  Severity: normal
  Priority: medium
 Component: Writer
  Assignee: libreoffice-bugs@lists.freedesktop.org
  Reporter: sme...@gmu.edu

Created attachment 186269
  --> https://bugs.documentfoundation.org/attachment.cgi?id=186269=edit
File wih styles for image amd text placement

I open the attached file and Writer loses the formatting. The images are not
properly placed or scaled and the text is not centered. I haven't checked
whether the hyperlinks are intact.

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

[Libreoffice-bugs] [Bug 154313] Writer drop-down menus are colored black

2023-03-28 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=154313

--- Comment #2 from solis  ---
I am working on Windows 10 with libreoffice 7.4.6.2 (in principle more stable
version). 
My path is a bit different: tools, options, advanced, enable experimental
settings, check the box.
I restart LO, in this case writer works in dark mode. As I prefer not to have
experimental settings enabled, I disable it again.
I restart LO and it opens in classic mode. After several days without problems,
the drop-down menus have a black background again and so do the letters. I
restart LO and it is fixed, but I can't locate the action that leads to this
problem in the colors.
Maybe it can influence (I have not checked it): locale Spanish but libreoffice
texts in English; this leads me to sometimes press Ctrl-N instead of Crl-B.
Well, if you can give me some advice, I'd appreciate it. Otherwise I will be
patient and wait for the next releases.
You will notice that I don't speak English, sorry for the additional difficulty
for you.

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

[Libreoffice-bugs] [Bug 154433] New: Auto-Replacement gets Ukrainian Quotation Marks wrong

2023-03-28 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=154433

Bug ID: 154433
   Summary: Auto-Replacement gets Ukrainian Quotation Marks wrong
   Product: LibreOffice
   Version: 7.3.2.2 release
  Hardware: All
OS: All
Status: UNCONFIRMED
  Severity: minor
  Priority: medium
 Component: Localization
  Assignee: libreoffice-bugs@lists.freedesktop.org
  Reporter: linus.sturm.git...@hotmail.com

Description:
According to both the German (*) and English (†) Wikipedia articles, the
quotation marks used in the Ukrainian language are like the French one (but
without the space), so like this: «word». But LibreOffice's automatic quotation
mark placement system places English-style quotation marks like “”. This has
actually been asked on AskLibreoffice (‡) about seven years ago, but the user
who solved the problem just explained how to change the default setting for the
replacement, and further states that "it is not possible to set a second (or
even third if needed - according to typographic rules in my country) level of
quotation marks in Autocorrect", although (afaik) LibreOffice replaces " with
the respective primary and ' with the respective secondary quotation marks, so
while tertiary marks aren't possible, secondary ones are.

P.S.: I know that Wikipedia can be wrong, but the AskLibreoffice question
stated the exact same facts, and I also know that the Russian language (which
at least has similarities to Ukrianian) also uses the «» type marks (which are
btw correctly replaced by LO). I also tested the replacement in Word Online, it
seems to have the wrong way of replacing them as well.

--
Links:
*: https://de.wikipedia.org/wiki/Anf%C3%BChrungszeichen#Andere_Sprachen (scroll
down the grid until you reach "Ukrainisch")
†:
https://en.wikipedia.org/wiki/Quotation_mark#Belarusian,_Russian,_and_Ukrainian
‡: https://ask.libreoffice.org/t/quote-marks-autocorrect-for-ukrainian/19573

Steps to Reproduce:
1. Set document language to Ukrainian
2. Press the " key to place the language-specific starting quotation mark.
3. Type some text
4. Press the " key again to place the language-specific ending quotation mark

Actual Results:
LibreOffice places “” quotation marks (as customary e.g. in English).

Expected Results:
LibreOffice should place the appropiate Ukrainian quotation marks, «».


Reproducible: Always


User Profile Reset: Yes

Additional Info:
Version: 7.3.2.2 (x64) / LibreOffice Community
Build ID: 49f2b1bff42cfccbd8f788c8dc32c1c309559be0
CPU threads: 4; OS: Windows 10.0 Build 19044; UI render: Skia/Raster; VCL: win
Locale: de-DE (de_DE); UI: en-GB
Calc: threaded

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

[Libreoffice-bugs] [Bug 154385] Form controls: "automatic" order does not work

2023-03-28 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=154385

--- Comment #6 from shoe...@gmx.de ---
Dear Robert, 

"Set the position for this one field manually in the dialog and all will work
well for you." - In most cases that doesn't work, a few times it does. I
couldn't find a rule. In my eyes the handling needs to be improved, it is hard
to understand. What number do you give to a control between no. 15 and no. 16?
I spent hours to get the controls done, sorting 30 times automatically and 5
times manually one by one.

> controls create identical names if you copy them
> thanks for your advice, but I didn't succeed to select a line and edit the 
> size of all controls in that line at one time, nor could I select several 
> controls via CMD key (Mac).
> It is hard work to put all controls on exact the same y-position and give 
> them all the same height.
> from user's point of view automatical sorting doesn't hit the expectations.

I think you need to work a while with the controls to find all this out. You
can close the incident if you think the findings are not bugs.

Thanks for trying!
Frank

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

[Libreoffice-bugs] [Bug 154432] Typical installation (update) changes my file icons without asking

2023-03-28 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=154432

--- Comment #1 from davidhaj...@gmail.com ---
Created attachment 186268
  --> https://bugs.documentfoundation.org/attachment.cgi?id=186268=edit
.doc icons

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

[Libreoffice-bugs] [Bug 154432] New: Typical installation (update) changes my file icons without asking

2023-03-28 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=154432

Bug ID: 154432
   Summary: Typical installation (update) changes my file icons
without asking
   Product: LibreOffice
   Version: 7.5.1.2 release
  Hardware: All
OS: Windows (All)
Status: UNCONFIRMED
  Severity: normal
  Priority: medium
 Component: Installation
  Assignee: libreoffice-bugs@lists.freedesktop.org
  Reporter: davidhaj...@gmail.com

Description:
I don't know if it's a bug, or if I should make a complaint about Libreoffice's
installation behabiour. I've updated Libreoffice with Typical installation
option, and it has changed the icons if my files. My father needs the Office
icons back to be able to identify the files. Libreoffice should have asked if I
wanted to replace the icons.

Steps to Reproduce:
1.Update Libreoffice
2.Chosse Typical installation
3.Find the file icons changed.

Actual Results:
Not apply

Expected Results:
Not apply


Reproducible: Always


User Profile Reset: No

Additional Info:
To ask if I want it. OR remember last choice (maybe I used Custom installation,
I don't remember)

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

[Libreoffice-bugs] [Bug 154426] [META] Steps to work with Base without needing Java

2023-03-28 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=154426

Sierk Bornemann  changed:

   What|Removed |Added

 Ever confirmed|0   |1
 Status|UNCONFIRMED |NEW

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

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

2023-03-28 Thread Noel Grandin (via logerrit)
 chart2/source/controller/dialogs/tp_3D_SceneGeometry.cxx |3 
 chart2/source/inc/Diagram.hxx|2 
 chart2/source/inc/ThreeDHelper.hxx   |3 
 chart2/source/model/main/Diagram.cxx |   27 
 chart2/source/tools/ThreeDHelper.cxx |  101 ---
 5 files changed, 31 insertions(+), 105 deletions(-)

New commits:
commit ef1f51571654d6449c6ce2872a4bc2bc2475585d
Author: Noel Grandin 
AuthorDate: Tue Mar 28 13:51:47 2023 +0200
Commit: Noel Grandin 
CommitDate: Tue Mar 28 17:14:42 2023 +

move switchRightAngledAxes from ThreeDHelper to Diagram

so we can use the get/setFastPropertyValue methods

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

diff --git a/chart2/source/controller/dialogs/tp_3D_SceneGeometry.cxx 
b/chart2/source/controller/dialogs/tp_3D_SceneGeometry.cxx
index fb05bfde0dbf..138952775e1e 100644
--- a/chart2/source/controller/dialogs/tp_3D_SceneGeometry.cxx
+++ b/chart2/source/controller/dialogs/tp_3D_SceneGeometry.cxx
@@ -249,7 +249,8 @@ IMPL_LINK_NOARG(ThreeD_SceneGeometry_TabPage, 
RightAngledAxesToggled, weld::Togg
 m_xMFZRotation->set_value(m_nZRotation, FieldUnit::DEGREE);
 }
 
-ThreeDHelper::switchRightAngledAxes( m_xDiagram, 
m_xCbxRightAngledAxes->get_active() );
+if (m_xDiagram)
+m_xDiagram->switchRightAngledAxes( m_xCbxRightAngledAxes->get_active() 
);
 }
 
 } //namespace chart
diff --git a/chart2/source/inc/Diagram.hxx b/chart2/source/inc/Diagram.hxx
index 2365d167c6a2..874e8e904e5d 100644
--- a/chart2/source/inc/Diagram.hxx
+++ b/chart2/source/inc/Diagram.hxx
@@ -350,6 +350,8 @@ public:
 
 void setDefaultRotation( bool bPieOrDonut );
 
+void switchRightAngledAxes( bool bRightAngledAxes );
+
 private:
 //  XModifyListener 
 virtual void SAL_CALL modified(
diff --git a/chart2/source/inc/ThreeDHelper.hxx 
b/chart2/source/inc/ThreeDHelper.hxx
index 1969b2305f6f..a8fc1d63fb40 100644
--- a/chart2/source/inc/ThreeDHelper.hxx
+++ b/chart2/source/inc/ThreeDHelper.hxx
@@ -59,9 +59,6 @@ public:
  */
 static css::drawing::CameraGeometry getDefaultCameraGeometry( bool 
bPie=false );
 
-static void switchRightAngledAxes( const rtl::Reference< Diagram >& 
xSceneProperties
-, bool bRightAngledAxes );
-
 static void adaptRadAnglesForRightAngledAxes( double& rfXAngleRad, double& 
rfYAngleRad );
 static double getXDegreeAngleLimitForRightAngledAxes() { return 90.0; }
 static double getYDegreeAngleLimitForRightAngledAxes() { return 45.0; }
diff --git a/chart2/source/model/main/Diagram.cxx 
b/chart2/source/model/main/Diagram.cxx
index 8cbdda41422a..1522d168c542 100644
--- a/chart2/source/model/main/Diagram.cxx
+++ b/chart2/source/model/main/Diagram.cxx
@@ -2231,6 +2231,33 @@ void Diagram::setDefaultRotation( bool bPieOrDonut )
 uno::Any( BaseGFXHelper::B3DHomMatrixToHomogenMatrix( aSceneRotation 
)));
 }
 
+void Diagram::switchRightAngledAxes( bool bRightAngledAxes )
+{
+try
+{
+bool bOldRightAngledAxes = false;
+getFastPropertyValue( PROP_DIAGRAM_RIGHT_ANGLED_AXES ) >>= 
bOldRightAngledAxes; // "RightAngledAxes"
+if( bOldRightAngledAxes!=bRightAngledAxes)
+{
+setFastPropertyValue( PROP_DIAGRAM_RIGHT_ANGLED_AXES, uno::Any( 
bRightAngledAxes ));
+if(bRightAngledAxes)
+{
+::basegfx::B3DHomMatrix aInverseRotation( 
lcl_getInverseRotationMatrix( *this ) );
+lcl_rotateLights( aInverseRotation, *this );
+}
+else
+{
+::basegfx::B3DHomMatrix aCompleteRotation( 
lcl_getCompleteRotationMatrix( *this ) );
+lcl_rotateLights( aCompleteRotation, *this );
+}
+}
+}
+catch( const uno::Exception & )
+{
+DBG_UNHANDLED_EXCEPTION("chart2");
+}
+}
+
 } //  namespace chart
 
 extern "C" SAL_DLLPUBLIC_EXPORT css::uno::XInterface *
diff --git a/chart2/source/tools/ThreeDHelper.cxx 
b/chart2/source/tools/ThreeDHelper.cxx
index 13c4ca47af3b..5733c6f44ba2 100644
--- a/chart2/source/tools/ThreeDHelper.cxx
+++ b/chart2/source/tools/ThreeDHelper.cxx
@@ -65,77 +65,6 @@ bool lcl_isRightAngledAxesSetAndSupported( const 
rtl::Reference< Diagram >& xDia
 return false;
 }
 
-void lcl_RotateLightSource( const Reference< beans::XPropertySet >& 
xSceneProperties
-   , const OUString& rLightSourceDirection
-   , const OUString& rLightSourceOn
-   , const ::basegfx::B3DHomMatrix& rRotationMatrix )
-{
-if( !xSceneProperties.is() )
-return;
-
-bool bLightOn = false;
-if( !(xSceneProperties->getPropertyValue( rLightSourceOn ) >>= bLightOn) )
-return;
-
-if( bLightOn )
-{
-

[Libreoffice-commits] core.git: sc/qa

2023-03-28 Thread Andrea Gelmini (via logerrit)
 0 files changed

New commits:
commit 983456a42dd2a5a08d7d053f8e3069fbd8c9777d
Author: Andrea Gelmini 
AuthorDate: Tue Mar 28 12:12:10 2023 +0200
Commit: Julien Nabet 
CommitDate: Tue Mar 28 17:14:04 2023 +

Removed executable bits on ods file

Change-Id: I9a43b02caaad389d8f67a2d2d43ad555d131edf7
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/149645
Tested-by: Jenkins
Reviewed-by: Julien Nabet 

diff --git a/sc/qa/extras/testdocuments/tdf142391.ods 
b/sc/qa/extras/testdocuments/tdf142391.ods
old mode 100755
new mode 100644


[Libreoffice-ux-advise] [Bug 147232] Improvement of CALC diagrams

2023-03-28 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=147232

--- Comment #8 from shoe...@gmx.de ---
Created attachment 186267
  --> https://bugs.documentfoundation.org/attachment.cgi?id=186267=edit
3_final result: this is the result of my work, scale = exactly 1:1

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

[Libreoffice-bugs] [Bug 147232] Improvement of CALC diagrams

2023-03-28 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=147232

--- Comment #8 from shoe...@gmx.de ---
Created attachment 186267
  --> https://bugs.documentfoundation.org/attachment.cgi?id=186267=edit
3_final result: this is the result of my work, scale = exactly 1:1

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

[Libreoffice-ux-advise] [Bug 147232] Improvement of CALC diagrams

2023-03-28 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=147232

--- Comment #7 from shoe...@gmx.de ---
Created attachment 186266
  --> https://bugs.documentfoundation.org/attachment.cgi?id=186266=edit
2_equal axis scale --> this is the option I wish

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

[Libreoffice-bugs] [Bug 147232] Improvement of CALC diagrams

2023-03-28 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=147232

--- Comment #7 from shoe...@gmx.de ---
Created attachment 186266
  --> https://bugs.documentfoundation.org/attachment.cgi?id=186266=edit
2_equal axis scale --> this is the option I wish

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

[Libreoffice-ux-advise] [Bug 147232] Improvement of CALC diagrams

2023-03-28 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=147232

shoe...@gmx.de changed:

   What|Removed |Added

 Attachment #186265|refers to comment from  |1_unequal axis scale
description|2023-03-28  |

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

[Libreoffice-bugs] [Bug 147232] Improvement of CALC diagrams

2023-03-28 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=147232

shoe...@gmx.de changed:

   What|Removed |Added

 Attachment #186265|refers to comment from  |1_unequal axis scale
description|2023-03-28  |

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

[Libreoffice-ux-advise] [Bug 147232] Improvement of CALC diagrams

2023-03-28 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=147232

--- Comment #6 from shoe...@gmx.de ---
Created attachment 186265
  --> https://bugs.documentfoundation.org/attachment.cgi?id=186265=edit
refers to comment from 2023-03-28

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

[Libreoffice-bugs] [Bug 147232] Improvement of CALC diagrams

2023-03-28 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=147232

--- Comment #6 from shoe...@gmx.de ---
Created attachment 186265
  --> https://bugs.documentfoundation.org/attachment.cgi?id=186265=edit
refers to comment from 2023-03-28

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

[Libreoffice-bugs] [Bug 154419] Csv import window doesn't appear on taskbar

2023-03-28 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=154419

V Stuart Foote  changed:

   What|Removed |Added

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

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

[Libreoffice-bugs] [Bug 154429] Suggestions for Default settings for new installs

2023-03-28 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=154429

V Stuart Foote  changed:

   What|Removed |Added

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

--- Comment #1 from V Stuart Foote  ---
"... should be a project to better mirror out of the box experience that MS
Word users get ..."

Hmm, not seeing an advantage or need to doing anything more for folks coming
from MS Office Desktop apps, or their O365 cloud flavors.

Specific behavior you describe is "anchoring", LibreOffice and ODF specs handle
differently in UI and document structure to MS's implementation for OOXML.

We very much expect users to RTM, especially necessary for folks crossing over
from the MS UIs.

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

[Libreoffice-ux-advise] [Bug 147232] Improvement of CALC diagrams

2023-03-28 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=147232

--- Comment #5 from shoe...@gmx.de ---
Dear all,
it seems everybody thinks different about the meaning of "scale", it is
strictly geometrical. I attached 3 images for demo. I need a diagram with
identical scale in x and y axis, see the files:

1_unequal axis scale = this is the standard setting in CALC, both of the axis
scales fit to the length and width of the diagram. In consequence each axes'
scale shrinks or expands, so that they fit to the diagram size. The diagram is
distorted.

2_equal axis scale = this is my request, I need to export the diagram with
exactly identical scaling in x and y axis. In consequence the diagram size
changes if the values change, the scales are identical and fix. Although it is
irritating if the diagram size changes permanently, it would be an option just
to implement this feature in the export workflow, like an option "export
undistorted".

3_final result = a file which is automatically generated by CALC - except the
scaling. Actually I need to export the diagram and do the scaling manually with
Libre Office DRAW.

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

[Libreoffice-bugs] [Bug 147232] Improvement of CALC diagrams

2023-03-28 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=147232

--- Comment #5 from shoe...@gmx.de ---
Dear all,
it seems everybody thinks different about the meaning of "scale", it is
strictly geometrical. I attached 3 images for demo. I need a diagram with
identical scale in x and y axis, see the files:

1_unequal axis scale = this is the standard setting in CALC, both of the axis
scales fit to the length and width of the diagram. In consequence each axes'
scale shrinks or expands, so that they fit to the diagram size. The diagram is
distorted.

2_equal axis scale = this is my request, I need to export the diagram with
exactly identical scaling in x and y axis. In consequence the diagram size
changes if the values change, the scales are identical and fix. Although it is
irritating if the diagram size changes permanently, it would be an option just
to implement this feature in the export workflow, like an option "export
undistorted".

3_final result = a file which is automatically generated by CALC - except the
scaling. Actually I need to export the diagram and do the scaling manually with
Libre Office DRAW.

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

[Libreoffice-bugs] [Bug 154419] Csv import window doesn't appear on taskbar

2023-03-28 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=154419

V Stuart Foote  changed:

   What|Removed |Added

 CC||vsfo...@libreoffice.org

--- Comment #2 from V Stuart Foote  ---
Why would it? The Text import dialog parent process is soffice.bin

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

[Libreoffice-bugs] [Bug 140032] Double-line cell borders not exported to XLSX and XLS

2023-03-28 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=140032

--- Comment #14 from ady  ---
Creating an ods file with:
Version: 7.6.0.0.alpha0+ (X86_64) / LibreOffice Community
Build ID: 67bb7f71b785d3d831ffaa47262b6cbd84e71c42
CPU threads: 4; OS: Windows 10.0 Build 19044; UI render: Skia/Raster; VCL: win
Locale: en-US (es_AR); UI: en-US
Calc: threaded
Built 2023-03-25

...containing cells with double border style and width of 1.5pt, and then
saving this ods file as xlsx, reopening the ods file and saving it as xls, all
three files are shown correctly in LO and in Excel online in terms of style.

There _seems_ to be some minor difference in color. I have not tested / checked
border colors, only the "double" style.

I have not tested different thickness / border widths.

I have not tested the previously-attached files.


Warning / note:

Exporting from LO as xml and opening it in LO and in Excel online > both show
the xml file incorrectly, especially when testing a range of contiguous cells
(as opposed to testing one cell alone, which fails too).

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

[Libreoffice-bugs] [Bug 154431] New: Bad management of hidden text in Writer | Editing, fotmatting, viewing, UI

2023-03-28 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=154431

Bug ID: 154431
   Summary: Bad management of hidden text in Writer | Editing,
fotmatting, viewing, UI
   Product: LibreOffice
   Version: unspecified
  Hardware: x86-64 (AMD64)
OS: Windows (All)
Status: UNCONFIRMED
  Severity: normal
  Priority: medium
 Component: Writer
  Assignee: libreoffice-bugs@lists.freedesktop.org
  Reporter: apprendista.programmatore+bugzi...@gmail.com

Description:
I have some hidden text in this file. I tried to make it visible followed the
instructions of
https://help.libreoffice.org/latest/en-US/text/swriter/guide/hidden_text_display.html
but it still does not show. In Word, the hidden text can be displayed.
I want paragraphs to be visible only in Writer but hidden when I export to pdf.
https://we.tl/t-GovczbEXzw
I cannot use the method described in
https://help.libreoffice.org/latest/en-US/text/swriter/guide/hidden_text.html
because it still leaves an ugly grey rectangle when I create the variable that
I would like to avoid seeing. Furthermore, I would like to set a paragraph
style that is only visible in Writer, which is much quicker to enter and better
distinguishes visible text from hidden text.
Same behavior in Windows 10 and in Fedora.

Steps to Reproduce:
1. Create a paragraph
2. Assign it a style
3. Edit the style by putting it hidden text
4. Try recueprating that text, if you can

Actual Results:
The hidden text seems lost forever

Expected Results:
I would like, as is the case in MS Word, that when I set to display hidden text
it is shown.


Reproducible: Always


User Profile Reset: Yes

Additional Info:
The linked file contains this information

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

[Libreoffice-bugs] [Bug 154430] New: User-friendly name of the document not used when accessing files on google drive via GIO

2023-03-28 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=154430

Bug ID: 154430
   Summary: User-friendly name of the document not used when
accessing files on google drive via GIO
   Product: LibreOffice
   Version: 7.4.5.1 release
  Hardware: All
OS: All
Status: UNCONFIRMED
  Severity: normal
  Priority: medium
 Component: LibreOffice
  Assignee: libreoffice-bugs@lists.freedesktop.org
  Reporter: bi...@bigon.be

Hello,

With GNOME, I'm accessing files on google drive via GIO

When opening a file via either nautilus/file browser or via the Open menu of
LO, the name displayed above is not the name of the document but some random
string (with the word "remote" in parenthesis).

The weird part is that the code seems to call the
g_file_info_get_display_name() function

For what I can see the build in debian unstable is properly built with GIO
support

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

[Libreoffice-bugs] [Bug 153431] PostgreSQL native connector: Field Memo [Text] is filled with 0 instead of character content where postgres server version is greater than or equal to 13

2023-03-28 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=153431

--- Comment #15 from Alex Thurgood  ---
@Stephane - probably because I couldn't reproduce the buggy behaviour against a
pg10 instance, cf. comment 5.

It was only when I tried against a pg13 instance and later that I saw the
problem.

I thought that it might possibly be down to a change introduced in the TEXT
datatype in pg13, but couldn't see anything in the release notes that might be
indicative of such a change.

I can't test any 6.x on macOS Arm, they refuse to run.

Ideally, someone should test with a 6.x against at least a pg13 instance on
Linux.

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

[Libreoffice-bugs] [Bug 154429] Suggestions for Default settings for new installs

2023-03-28 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=154429

markbal...@gmail.com changed:

   What|Removed |Added

Summary|Suggestions for Default |Suggestions for Default
   |settings for new installed  |settings for new installs

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

[Libreoffice-bugs] [Bug 154429] New: Suggestions for Default settings for new installed

2023-03-28 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=154429

Bug ID: 154429
   Summary: Suggestions for Default settings for new installed
   Product: LibreOffice
   Version: 7.5.1.2 release
  Hardware: All
OS: Windows (All)
Status: UNCONFIRMED
  Severity: normal
  Priority: medium
 Component: Writer
  Assignee: libreoffice-bugs@lists.freedesktop.org
  Reporter: markbal...@gmail.com

Description:
I have just installed LibreOffice after a long time away.  So as to make out of
the box experience better for those users trying LibreOffice for the first time
and coming from a MS Word environment, there should be a project to better
mirror out of the box experience that MS Word users get from a new install of
MS Word as many will not make preference changes and become indoctrinated into
that navigational paradigm.  I am suggesting this as my first usages caused me
to stumble around because of default settings.  

Steps to Reproduce:
1.New file
2.Paste text
3. Paste image
4. attempt to adjust image on page and use returns to push image down page to
adjust placement, as is common in MS Word

Actual Results:
1. Place cursor after image and return, image moves down page instead of line
returns inserting new rows for new input.
2. Image format default is text around image, where as image format default in
MS Word is text above and below image. 

Expected Results:
If i place cursor after an object I expect object to remain in place, not
follow character returns down page.  Encountered difficulty in simply movement
of page objects as my user experience paradigm comes form MS Word. 


Reproducible: Always


User Profile Reset: No

Additional Info:
I recommend that you start a new team effort to map navigation patterns and set
defaulting install behaviors to match that of MS Word.  I know many on team
will say, Our defaulting behavior are better, but the reality is , you want to
make new users as comfortable as possible with their initial onboarding to OL.
There are many many projects and companies out there that make this critical
mistake and it is usually driven by senior ego's, not an attitude of let's win
this game.

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

[Libreoffice-bugs] [Bug 62867] Word wrap does not work properly when image is left of the left margin.

2023-03-28 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=62867

Justin L  changed:

   What|Removed |Added

Version|4.0.1.2 release |Inherited From OOo

--- Comment #14 from Justin L  ---
The same thing happens in OOo 3.3 with Anne.odt.

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

  1   2   3   4   >