[Libreoffice-bugs] [Bug 152432] File > Recent Recordings displays empty list when saving document

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

--- Comment #5 from Mark C  ---
Okay.  I did the Help>Menu>Restart in safe mode.

I followed the steps I documented.   This time I used the ppt equivalent (I
think you call it Draw).

I observed EXACTLY the same issue.

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

[Libreoffice-bugs] [Bug 155726] Calc - change the location of the 'Sort by Color' option in the automatic filter menu

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

--- Comment #1 from kabilo  ---
Created attachment 187775
  --> https://bugs.documentfoundation.org/attachment.cgi?id=187775=edit
change the location of the Sort by Color option

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

[Libreoffice-bugs] [Bug 155726] New: Calc - change the location of the 'Sort by Color' option in the automatic filter menu

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

Bug ID: 155726
   Summary: Calc - change the location of the 'Sort by Color'
option in the automatic filter menu
   Product: LibreOffice
   Version: 7.6.0.0 alpha1+ Master
  Hardware: All
OS: All
Status: UNCONFIRMED
  Severity: normal
  Priority: medium
 Component: Calc
  Assignee: libreoffice-bugs@lists.freedesktop.org
  Reporter: minute.visit...@gmail.com

Description:
change the location of the 'Sort by Color' option in the automatic filter menu.
The option is located in the filter group.

Steps to Reproduce:
1. show auto filter menu


Actual Results:
The 'Sort by Color' option is located in the filter group.

Expected Results:
The 'Sort by Color' option should be displayed in the sort group


Reproducible: Always


User Profile Reset: No

Additional Info:

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

[Libreoffice-bugs] [Bug 154583] Split button Color Picker regression, attempting a color pick now opens the Line or Area object dialog

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

Aron Budea  changed:

   What|Removed |Added

 Whiteboard||target:24.2.0

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

[Libreoffice-bugs] [Bug 136991] Open RTF with colored text slower from 4.1 and 4.2

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

--- Comment #22 from BogdanB  ---
Telesto, Pit Hauge, can you test again this bug using 7.6? Maybe even using
Mac?

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

[Libreoffice-bugs] [Bug 33687] FORMATTING: index text (TOC) does not flow in linked frames

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

--- Comment #18 from markmor  ---
Means that Still reproduces on windows 7/64 & Version: 4.4.1.1
https://dynamonsworld.com I will try it.

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

[Libreoffice-bugs] [Bug 155476] 'Store on server' garbles filenames from unixoid sources (Linux & probably MacOSX, xxxBSD)

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

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 155477] outline export to xhtml fails to preserve indentation

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

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 155427] filters.add 423 property not found

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

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 155696] Clicking on selected object no longer enters rotation mode

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

QA Administrators  changed:

   What|Removed |Added

 Status|NEEDINFO|UNCONFIRMED
 Ever confirmed|1   |0

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

[Libreoffice-bugs] [Bug 155451] LibreOffice splash screen should remain active until main LibreOffice window becomes usable

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

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 155696] Clicking on selected object no longer enters rotation mode

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

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

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

[Libreoffice-bugs] [Bug 152433] wrong cross-reference

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

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

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 147038] Drag & drop behaviour is off after putting an image to different page & restoring it with undo

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

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

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 152442] Writer:: Navigator can't be pinned to the left

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

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

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 152432] File > Recent Recordings displays empty list when saving document

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

--- Comment #4 from QA Administrators  ---
Dear Mark C,

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 147036] Inconsistency deleting to character anchors in document with backspace/delete

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

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

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 61950] Change Presentation Minimizer and Report Builder from bundled extensions to plain code

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

--- Comment #39 from QA Administrators  ---
Dear Stephan Bergmann,

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 142581] Insert row in impress creates a odd row height distribution

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

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

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

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

If you have time, please do the following:

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

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

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

Please DO NOT

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


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

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


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

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

Warm Regards,
QA Team

MassPing-UntouchedBug

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

[Libreoffice-bugs] [Bug 142425] Page flow after hiding track changes differently between ODT & exported DOCX and DOC

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

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

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

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

If you have time, please do the following:

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

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

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

Please DO NOT

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


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

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


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

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

Warm Regards,
QA Team

MassPing-UntouchedBug

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

[Libreoffice-bugs] [Bug 130697] Print preview of SVG images rendered pixelated (macOS-only) and crash with LO from master branch

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

--- Comment #10 from QA Administrators  ---
Dear Thorsten Wagner,

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 117876] [EXPORT] Bad export to EPS

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

--- Comment #6 from QA Administrators  ---
Dear Olivier Hallot,

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 117510] Firebird: Migration: Data unavailable when migration is run against HSQL ODB opened in Beamer (from Writer or Calc)

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

--- Comment #9 from QA Administrators  ---
Dear Drew Jensen,

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 113029] EDITING: AutoInput doesn't recognise RC references and autocompletes with a formula

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

--- Comment #5 from QA Administrators  ---
Dear John Russell,

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 155725] spaces at end of lines don't appear on screen

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

--- Comment #1 from Telesto  ---
Sounds like bug 104683.

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

[Libreoffice-bugs] [Bug 68997] FILEOPEN Equation: Import from Word2010 not correctly rendered

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

Justin L  changed:

   What|Removed |Added

   Hardware|Other   |All
Summary|FILEOPEN: Import from   |FILEOPEN Equation: Import
   |Word2010 not correctly  |from Word2010 not correctly
   |rendered|rendered

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

[Libreoffice-bugs] [Bug 154583] Split button Color Picker regression, attempting a color pick now opens the Line or Area object dialog

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

Tomaz Vajngerl  changed:

   What|Removed |Added

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

--- Comment #19 from Tomaz Vajngerl  ---
Fixed with [1].. I put the duplicate bug number in the git comment by mistake. 

[1] https://gerrit.libreoffice.org/c/core/+/152713

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

[Libreoffice-bugs] [Bug 85184] [META] Color picker toolbar, dialog and sidebar drop-down widget bugs and enhancements

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

Bug 154583 Summary: Split button Color Picker regression, attempting a color 
pick now opens the Line or Area object dialog
https://bugs.documentfoundation.org/show_bug.cgi?id=154583

   What|Removed |Added

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

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

[Libreoffice-bugs] [Bug 155725] New: spaces at end of lines don't appear on screen

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

Bug ID: 155725
   Summary: spaces at end of lines don't appear on screen
   Product: LibreOffice
   Version: 7.1.3.2 release
  Hardware: Other
OS: macOS (All)
Status: UNCONFIRMED
  Severity: normal
  Priority: medium
 Component: Base
  Assignee: libreoffice-bugs@lists.freedesktop.org
  Reporter: l...@leegass.com

Beginning today, with Libre Office7.1.3.2, composing a text document a problem
started bugging me.

With one kind of writing I do, I use centred text format and create new lines
with linefeeds (return).  Normally, if I enter a space that space registers on
the screen, and that does happen within lines.  But if I add a space at the end
of a line, it doesn't register on the screen.  That means I must keep track of
how many spaces I've entered, and if I don't remember it right I either jam
words up against each other or Libre complains that I have too many spaces.

I think ensuring all spaces entered appear on the screen would save me much
time, effort, and frustration.

Thanks,
Lee Gass

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

[Libreoffice-bugs] [Bug 66458] FILEOPEN: DOCX imports 'ptab' as 'tab' instead of its own type

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

Justin L  changed:

   What|Removed |Added

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

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

[Libreoffice-bugs] [Bug 78144] FILEOPEN: WPS DOC - Incorrect alignment of page number in footer due to wrong position of tab stop (needs w:ptab equivalent)

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

Justin L  changed:

   What|Removed |Added

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

--- Comment #17 from Justin L  ---
Good information and code pointers in bug 66458.

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

[Libreoffice-bugs] [Bug 78144] FILEOPEN: WPS DOC - Incorrect alignment of page number in footer due to wrong position of tab stop (needs w:ptab equivalent)

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

Justin L  changed:

   What|Removed |Added

 CC||rattles2...@gmail.com

--- Comment #16 from Justin L  ---
*** Bug 66458 has been marked as a duplicate of this bug. ***

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

[Libreoffice-bugs] [Bug 104520] [META] DOCX (OOXML) bug tracker

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

Bug 66458 Summary: FILEOPEN: DOCX imports 'ptab' as 'tab' instead of its own 
type
https://bugs.documentfoundation.org/show_bug.cgi?id=66458

   What|Removed |Added

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

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

[Libreoffice-bugs] [Bug 66458] FILEOPEN: DOCX imports 'ptab' as 'tab' instead of its own type

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

Justin L  changed:

   What|Removed |Added

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

--- Comment #12 from Justin L  ---


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

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

[Libreoffice-bugs] [Bug 93675] FILESAVE DOCX Grouped shapes text in Word is attached to different shapes than in Writer

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

--- Comment #38 from Dave Gilbert  ---
(In reply to Regina Henschel from comment #37)
> The reason of the rotation trouble is, that a shape gets attached a frame on
> import to be able to contain complex texts like char anchored images and
> tables. And these frames are not able to rotate.
> 
> At that time, when this happens, there is no simple way to detect, whether
> the contained content is a complex text or a simple text.
> 
> You will likely find other bug reports about the missing ability of frames
> to rotate.

Hi Regina,
  Thanks for the reply.  So is that a new issue? - I thought the rotation used
to work, and the screenshot from 2021-07-26 seems to suggest it did.

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

[Libreoffice-bugs] [Bug 94728] Shadow color in DOCX is different from Word

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

--- Comment #9 from Justin L  ---
repro 7.6

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

[Libreoffice-bugs] [Bug 149672] FILEOPEN DOCX IF field complex content not imported correctly

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

Justin L  changed:

   What|Removed |Added

Version|7.5.0.0 alpha0+ |unspecified

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

[Libreoffice-bugs] [Bug 135569] FILEOPEN DOCX Inner margins are rotated with textbox

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

Justin L  changed:

   What|Removed |Added

 Whiteboard|target:7.5.0 target:7.4.1   |

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

[Libreoffice-bugs] [Bug 123110] FILEOPEN DOCX Text in shape has wrong color

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

--- Comment #9 from Justin L  ---
repro 7.6

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

[Libreoffice-bugs] [Bug 138699] FILESAVE: DOCX: Drop-Down Form Field bookmark data is lost on save

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

--- Comment #5 from Justin L  ---
repro 7.6 (I think). There is no bookmark name seen in MSO when opening up the
field dialog. It should be "field1" and "field2".

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

[Libreoffice-bugs] [Bug 146383] ODT->DOCX export: Wrap triggered around image after DOCX export

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

Justin L  changed:

   What|Removed |Added

   Severity|normal  |minor
   Priority|medium  |low
Summary|DOCX export: Wrap triggered |ODT->DOCX export: Wrap
   |around image after DOCX |triggered around image
   |export  |after DOCX export
Version|7.3.0.0 alpha0+ |7.3.0.0.alpha1+

--- Comment #9 from Justin L  ---
repro 7.6

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

[Libreoffice-bugs] [Bug 138366] Vertical text position within a text box doesn't set correct spacing

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

--- Comment #6 from Justin L  ---
repro 7.6

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

[Libreoffice-bugs] [Bug 93675] FILESAVE DOCX Grouped shapes text in Word is attached to different shapes than in Writer

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

Regina Henschel  changed:

   What|Removed |Added

 CC||rb.hensc...@t-online.de

--- Comment #37 from Regina Henschel  ---
The reason of the rotation trouble is, that a shape gets attached a frame on
import to be able to contain complex texts like char anchored images and
tables. And these frames are not able to rotate.

At that time, when this happens, there is no simple way to detect, whether the
contained content is a complex text or a simple text.

You will likely find other bug reports about the missing ability of frames to
rotate.

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

[Libreoffice-bugs] [Bug 145854] Fileopen: DOCX table should still fit the page even if "Preferred width" in MSO is larger than page

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

--- Comment #7 from Justin L  ---
repro 7.6

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

[Libreoffice-bugs] [Bug 155724] -env:UserInstallation= broken on Windows

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

--- Comment #1 from Jim Avera  ---
I'm sorry (copy-paste mistake), the .ini file contains

   UserInstallation=$SYSUSERCONFIG/LibreOffice/4

Also, the batch file name should end in .bat not .bad

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

[Libreoffice-bugs] [Bug 155724] New: -env:UserInstallation= broken on Windows

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

Bug ID: 155724
   Summary: -env:UserInstallation= broken on Windows
   Product: LibreOffice
   Version: 7.5.3.2 release
  Hardware: All
OS: Windows (All)
Status: UNCONFIRMED
  Severity: normal
  Priority: medium
 Component: Installation
  Assignee: libreoffice-bugs@lists.freedesktop.org
  Reporter: jim.av...@gmail.com

The documented UserInstallation mechanism for specifying a profile directory
does not work on Windows.   I think the reason is that 'UserInstallation' is
defined in "C:\Program Files\LibreOffice\program\bootstrap.ini" and it can not
be over-ridden with an environment variable or using the documented command
line option -env:UserInstallation=file://...

Can LO be made to ignore the setting in .ini if the user explicitly over-rides
it with a command line option?

--- details ---

This prevents safely using LO as a batch tool to convert files (--convert-to
option etc.) because if the user has an interactive session running then random
aborts will occur.

https://wiki.documentfoundation.org/UserProfile says the following will start
LO with a different user profile:

  For Windows:  soffice.com -env:UserInstallation=file:///c:/my-test-profile

Initially, that fails because .../program/ was not registered by the installer
to be in PATH, so "soffice.com" is not found.

If the fully-qualified path is specified, then a pop-up error says

The application cannot be started. 
The configuration file "C:\Program Files\LibreOffice\program\bootstrap.ini" 
is corrupt.

That .ini file does contain

"C:\Program Files\LibreOffice\program\bootstrap.ini"

which seems to cause this conflict.

STEPS TO REPRODUCE:

1. Using Vim or Notepad, create a file "test.bad" containing the following two
lines (change the paths appropriately):

mkdir "C:\Users\Admin0\AppData\Local\Temp\TestProfile"

"C:\Program Files\LibreOffice\program\soffice.com"
"-env:UserInstallation=file://C:\Users\Admin0\AppData\Local\Temp\TestProfile"

2. Type the name/path of the script (e.g. "test.bat")

RESULTS: The "corrupted" error pop-up appears and LO stalls waiting for the
user to click ok.

-

Note: There is no such problem on Linux.

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

[Libreoffice-bugs] [Bug 149538] OOXML DOCX bad import, export and rendering for property "upright"

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

Justin L  changed:

   What|Removed |Added

 OS|Windows (All)   |All
   Hardware|x86-64 (AMD64)  |All
Version|7.4.0.0 alpha0+ |unspecified

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

[Libreoffice-bugs] [Bug 134670] FILEOPEN DOCX : The use of vertical and horizontal typesetting results in the loss of text content and typesetting style

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

--- Comment #5 from Justin L  ---
repro 7.6+

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

[Libreoffice-bugs] [Bug 148834] Line numbering for specific paragraphs gets lost after saving to ODT->.docx file format

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

Justin L  changed:

   What|Removed |Added

 CC||jl...@mail.com
Summary|Line numbering for specific |Line numbering for specific
   |paragraphs gets lost after  |paragraphs gets lost after
   |saving to .docx file format |saving to ODT->.docx file
   ||format
   Priority|medium  |low
Version|3.3.0 release   |Inherited From OOo
   Severity|normal  |minor

--- Comment #2 from Justin L  ---
Low priority: Things designed in Word seem to round-trip well. Things designed
in LO using simple styles seem to work well also.

MS Word has line numbering tied to a section. All paragraphs in a section
participate, and require an explicit "suppress line numbers" paragraph property
to avoid being numbered.

LO does not tie numbering to page styles or sections AFAICS. It is just on or
off for the whole document.

But that sounds like it all should work. What is the problem then? I assume
that the property  is not written when it is false.

Yup - here it is:
if ( !rNumbering.IsCount( ) )
m_pSerializer->singleElementNS(XML_w, XML_suppressLineNumbers);

Generally, that is a good thing, but not when it needs to override an inherited
value (like in this case where the style says suppress, but the direct
formatting says don't suppress).  See ExportPoolItemsToCHP for some ideas on
how to check that.

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

[Libreoffice-bugs] [Bug 155723] New: Regular Pentagon tool draws pentagons, not regular pentagons

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

Bug ID: 155723
   Summary: Regular Pentagon tool draws pentagons, not regular
pentagons
   Product: LibreOffice
   Version: 7.4.7.2 release
  Hardware: All
OS: All
Status: UNCONFIRMED
  Severity: normal
  Priority: medium
 Component: Draw
  Assignee: libreoffice-bugs@lists.freedesktop.org
  Reporter: dmatsch...@quietriding.com

The Basic Shapes toolbar has a tool named "Regular Pentagon". However, the tool
actually draws simple pentagons, not "regular" pentagons.

A pentagon is a shape with 5 sides. A regular pentagon has 5 equal sides and 5
equal angles.

For accuracy, and to avoid confusion, the name of this tool should be changed
from "Regular Pentagon" to simply "Pentagon".

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

[Libreoffice-bugs] [Bug 93675] FILESAVE DOCX Grouped shapes text in Word is attached to different shapes than in Writer

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

--- Comment #36 from Dave Gilbert  ---
Here's a diff of the (xmllint'd) word/document.xml from the unzip'd docx, other
than a one pixel shift in x coords for some wierd reason, the diff is pretty
much just the removal of that vertical line, so something in there must be
confusing the heck out of word:

[dg@dalek unpacked-diagram-2015-08-noline]$ diff
../unpacked-mod/word/document-linted.xml word/document-linted.xml
1090c1090
<   
---
>   
1094,1096c1094,1096
<   
<   
<   
---
>   
>   
>   
1100c1100
<   
---
>   
1461c1461
<   
---
>   
1464c1464
<   
---
>   
1484,1527d1483
< 
< 
<   
< 
< 
<   
<   
< 
<   
<   
< 
<   
< 
< 
<   
< 
< 
<   
<   
<   
<   
< 
< 
<   
< 
<   
< 
< 
<   
<   
< 
<   
<   
< 
< WOabcdefghijklm
<   
< 
<   
< 
< 
<   
< 
<   
<   
1724c1680
<   
---
>   
1727c1683
<   
---
>   
2235c2191
< 
---
>  path="m2794,99c2196,0,1896,300,1398,500c0,2398,1164,5990,1198,8786c1198,9185,356,9181,223,9380e"
>  stroked="t" o:allowincell="f" 
> style="position:absolute;left:1729;top:2894;width:1457;height:5272">
2387c2343
< 
---
>  path="m0,0c1397,1498,2825,1280,2825,1280l8347,1289e" stroked="t" 
> o:allowincell="f" 
> style="position:absolute;left:1373;top:5743;width:4731;height:731">
2392,2413d2347
< 
<   
< 
<   
< 
<   
<   
< 
< 
<   
< 
< 
<   
<   abcdefghijklm
< 
<   
< 
<   
<   
<   
<   
< 
2515c2449
< 
---
>  path="m0,4003c99,1709,1997,1,3100,0l8623,10e" stroked="t" o:allowincell="f" 
> style="position:absolute;left:1157;top:2670;width:4887;height:2268">

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

[Libreoffice-bugs] [Bug 93675] FILESAVE DOCX Grouped shapes text in Word is attached to different shapes than in Writer

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

--- Comment #35 from Dave Gilbert  ---
Deleting the thin line from c->b and then save-as docx gives me a file that's
displayed
with all the right text in the right place in OneDrive/word.

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

[Libreoffice-bugs] [Bug 155404] Toolbar: choosing a color in the color picker opens the Area dialog

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

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

https://git.libreoffice.org/core/commit/5a2c6f4df7149f8c1f543f120fe19bd66abfc189

tdf#155404 handle ComplexColor as JSON for XLineColor and XFillColor

It will be available in 24.2.0.

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

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

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

[Libreoffice-bugs] [Bug 155404] Toolbar: choosing a color in the color picker opens the Area dialog

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

Commit Notification  changed:

   What|Removed |Added

 Whiteboard||target:24.2.0

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

[Libreoffice-bugs] [Bug 96506] The "Use Styles From Another Document" feature doesn't work if the other document is a .fodt one

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

--- Comment #11 from Ganton  ---
The bug still exists using Libreoffice 7.5.3.2

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

[Libreoffice-bugs] [Bug 154994] Functions sidebar should be searchable as soon as it is focused

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

Stéphane Guillou (stragu)  changed:

   What|Removed |Added

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

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

[Libreoffice-bugs] [Bug 122718] Sidebar Functions panel misses search like Function Wizard

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

Stéphane Guillou (stragu)  changed:

   What|Removed |Added

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

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

[Libreoffice-bugs] [Bug 155283] Need ability to filter sidebar style list by typing

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

Stéphane Guillou (stragu)  changed:

   What|Removed |Added

 CC||libreoffice-ux-advise@lists
   ||.freedesktop.org
   See Also||https://bugs.documentfounda
   ||tion.org/show_bug.cgi?id=15
   ||4994,
   ||https://bugs.documentfounda
   ||tion.org/show_bug.cgi?id=12
   ||2718
   Keywords||needsUXEval

--- Comment #5 from Stéphane Guillou (stragu) 
 ---
(In reply to Eyal Rozenberg from comment #4)
> 1. I want this without having clicked a list item first, although that's not
> a critical part of the ask.

Reminds me of bug 154994. There's the question of "should toggling a UI element
move the keyboard focus off the page?"
As I noted in bug 154994 comment 2, the Gallery and Navigator decks already do
that.

> 2. When I click a list item and type, the list scrolls to the first match
> for what I've typed, it doesn't filter.

Similar to bug 122718 for functions.

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

[Libreoffice-bugs] [Bug 155492] .DOC and .DOCX files do not display correctly

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

Stéphane Guillou (stragu)  changed:

   What|Removed |Added

 Resolution|FIXED   |WORKSFORME

--- Comment #5 from Stéphane Guillou (stragu) 
 ---
Thanks Tim. Setting the resolution to "works for me" instead, as "fixed" is for
when a code patch fixes the issue.

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

[Libreoffice-bugs] [Bug 150419] FILESAVE ODT->DOCX page style writing direction "left-to-right (vertical)" is wrongly exported

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

Justin L  changed:

   What|Removed |Added

Summary|FILESAVE DOCX page writing  |FILESAVE ODT->DOCX page
   |direction "left-to-right|style writing direction
   |(vertical)" is wrongly  |"left-to-right (vertical)"
   |exported|is wrongly exported

--- Comment #5 from Justin L  ---
This looks like it was fixed in LO 7.5 with
commit c70ee4a6b9071468255e5d4fdb893e9c9bdf4fad
Author: Regina Henschel on Wed Aug 17 02:31:44 2022 +0200
tdf#149551 use 'WritingMode' instead of TextPreRotateAngle

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

[Libreoffice-bugs] [Bug 121508] FILESAVE ODT->DOCX Shape in frame is lost after export

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

Justin L  changed:

   What|Removed |Added

Summary|FILESAVE DOCX Shape in  |FILESAVE ODT->DOCX Shape in
   |frame is lost after export  |frame is lost after export

--- Comment #8 from Justin L  ---
I don't actually see a lost frame in Frame-Paragraph-Shape.odt (tested 7.2),
but I do see it in the duplicate www (6) (2) (5).odt (tested 7.6)

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

[Libreoffice-bugs] [Bug 134635] FILEOPEN DOCX : Set the page to a stationery grid and save docx, then open the grid line can not be aligned

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

--- Comment #5 from Justin L  ---
It looks fixed to me in LO 7.0.6 with
commit c9e5640c8fcad7beb42a66f9bee0252eee9fe323
Author: Xisco Fauli on Thu Mar 18 00:48:49 2021 +0100
tdf#118693: no need to use convertMm100ToTwip() for line shapes anymore

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

[Libreoffice-bugs] [Bug 155722] New: Footers and Pagebreaks are never saved when I edit a saved Spreadsheet

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

Bug ID: 155722
   Summary: Footers and Pagebreaks are never saved when I edit a
saved Spreadsheet
   Product: LibreOffice
   Version: 7.5.3.2 release
  Hardware: All
OS: macOS (All)
Status: UNCONFIRMED
  Severity: normal
  Priority: medium
 Component: LibreOffice
  Assignee: libreoffice-bugs@lists.freedesktop.org
  Reporter: ianjbis...@gmail.com

Description:
I have a Spreadsheet I use for work which I update every couple of weeks or so.
I'm doing small editing like adding or deleting items in the spreadsheet.
Adding and/or removing page breaks and editing the footer notes.

In the footer notes, I have the Month and Year eg:(June 2023) and the page
numbers.
I will save the spreadsheet and export a pdf which I show to clients, but if I
need to go back and edit the spreadsheet, my pagebreaks are all screwed up and
my footer notes are different. 
For example: I will save the footer as "June 2023" then when I go back into the
spreadsheet to edit again, it will say "January 2023" and this happens all the
time for some reason.

Steps to Reproduce:
1.Edit foot notes and save
2.Edit pagebreaks and save
3.Open spreadsheet and the above are not saved.

Actual Results:
The footnotes and pagebreaks are not saved.

Expected Results:
Save the exact way I left and saved the document.


Reproducible: Always


User Profile Reset: No

Additional Info:
[Information automatically included from LibreOffice]
Locale: en-US
Module: SpreadsheetDocument
[Information guessed from browser]
OS: Mac OS X (All)
OS is 64bit: no

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

[Libreoffice-bugs] [Bug 93675] FILESAVE DOCX Grouped shapes text in Word is attached to different shapes than in Writer

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

--- Comment #34 from Dave Gilbert  ---
observation on the wrong text:

  a) I confirmed that both LO and Onedrive are showing the DML/non-fallback
version of the drawing in the file

  b) It's a 'after this point' error in the output file, that is if you look at
the order of items in the output file we have:

...
   Host 2
   More hosts
   b
FIRST MISPLACE abcdefghijklm
   Da da da de de de yabba yabba yabba
   Yabba yabba yabba
   Stuff going this way
   Data going around bend
   a

all the items upto the 'b' end up in the right place, but everything after end
up wrong.
It's the stuff that should be vertical text on the thin line between 'b' and
'c'

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

[Libreoffice-bugs] [Bug 94657] borders not visible on loading docx

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

Justin L  changed:

   What|Removed |Added

   Priority|medium  |low
   Severity|normal  |enhancement
   Hardware|Other   |All

--- Comment #14 from Justin L  ---
repro 7.6+
Yeah, LO doesn't have "art" available as a page border.

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

[Libreoffice-bugs] [Bug 132092] DOCX import: a generated document has black text highlighting, where in Word, the background is white (OK if resaved in MSO)

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

Justin L  changed:

   What|Removed |Added

Summary|DOCX import: a generated|DOCX import: a generated
   |document has black text |document has black text
   |highlighting, where in  |highlighting, where in
   |Word, the background is |Word, the background is
   |white   |white (OK if resaved in
   ||MSO)

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

[Libreoffice-bugs] [Bug 104444] [META] DOCX (OOXML) table-related issues

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

Bug 134891 Summary: FILEOPEN DOCX : Compatibility problem of slash table-header
https://bugs.documentfoundation.org/show_bug.cgi?id=134891

   What|Removed |Added

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

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

[Libreoffice-bugs] [Bug 51665] Writer: support diagonal borders in tables

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

Justin L  changed:

   What|Removed |Added

 CC||leiy...@kylinos.cn

--- Comment #26 from Justin L  ---
*** Bug 134891 has been marked as a duplicate of this bug. ***

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

[Libreoffice-bugs] [Bug 134891] FILEOPEN DOCX : Compatibility problem of slash table-header

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

Justin L  changed:

   What|Removed |Added

 Resolution|--- |DUPLICATE
Version|4.4 all versions|Inherited From OOo
 Status|NEW |RESOLVED

--- Comment #4 from Justin L  ---


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

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

[Libreoffice-bugs] [Bug 104520] [META] DOCX (OOXML) bug tracker

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

Bug 36999 Summary: DOCX import: For hidden ActiveX control, the replacement wmf 
is always shown
https://bugs.documentfoundation.org/show_bug.cgi?id=36999

   What|Removed |Added

 Status|NEW |RESOLVED
 Resolution|--- |INVALID

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

[Libreoffice-bugs] [Bug 36999] DOCX import: For hidden ActiveX control, the replacement wmf is always shown

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

Justin L  changed:

   What|Removed |Added

 Status|NEW |RESOLVED
 Resolution|--- |INVALID

--- Comment #22 from Justin L  ---
bug document no longer available from link - access denied.

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

[Libreoffice-bugs] [Bug 155434] Several Calc menu commands are available in Read-Only mode

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

ady  changed:

   What|Removed |Added

   Keywords||needsUXEval

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

[Libreoffice-bugs] [Bug 51665] Writer: support diagonal borders in tables

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

Justin L  changed:

   What|Removed |Added

   See Also|https://bugs.documentfounda |
   |tion.org/show_bug.cgi?id=14 |
   |5945|
 CC||jl...@mail.com
Summary|Support diagonal borders in |Writer: support diagonal
   |TABLEs  |borders in tables

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

[Libreoffice-bugs] [Bug 145945] FILEOPEN DOCX: diagonal borders isn't displayed on the table.

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

Justin L  changed:

   What|Removed |Added

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

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

[Libreoffice-bugs] [Bug 104444] [META] DOCX (OOXML) table-related issues

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

Bug 145945 Summary: FILEOPEN DOCX: diagonal borders isn't displayed on the 
table.
https://bugs.documentfoundation.org/show_bug.cgi?id=145945

   What|Removed |Added

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

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

[Libreoffice-bugs] [Bug 51665] Support diagonal borders in TABLEs

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

Justin L  changed:

   What|Removed |Added

 CC||20001...@ymail.ne.jp

--- Comment #25 from Justin L  ---
*** Bug 145945 has been marked as a duplicate of this bug. ***

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

[Libreoffice-bugs] [Bug 145945] FILEOPEN DOCX: diagonal borders isn't displayed on the table.

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

Justin L  changed:

   What|Removed |Added

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

--- Comment #9 from Justin L  ---


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

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

[Libreoffice-bugs] [Bug 69515] FILEOPEN: Table in DOCX floating frame wrongly positioned (framePr ignored, regression)

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

Gabor Kelemen (allotropia)  changed:

   What|Removed |Added

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

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

[Libreoffice-bugs] [Bug 137788] FILEOPEN DOCX: wrongly positioned block Table (not wrapped in w:p) framed via framePr with another paragraph

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

Gabor Kelemen (allotropia)  changed:

   What|Removed |Added

 CC||kelem...@ubuntu.com
   See Also||https://bugs.documentfounda
   ||tion.org/show_bug.cgi?id=69
   ||515

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

[Libreoffice-bugs] [Bug 155721] [FILEOPEN] ODS office:annotation color

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

SheetJS  changed:

   What|Removed |Added

 Status|UNCONFIRMED |RESOLVED
 Resolution|--- |FIXED

--- Comment #3 from SheetJS  ---
7.6.0 alpha1 uses the correct color

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

[Libreoffice-bugs] [Bug 155713] Text position in Dimension line dialog does not work as expected

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

Regina Henschel  changed:

   What|Removed |Added

 Ever confirmed|0   |1
 Status|UNCONFIRMED |NEW
 CC||rb.hensc...@t-online.de

--- Comment #1 from Regina Henschel  ---
I confirm the problem exists in Version: 7.6.0.0.alpha1+ (X86_64) / LibreOffice
Community
Build ID: 70fd835b4cf75e386ee115c705241a4059fb68a8
CPU threads: 8; OS: Windows 10.0 Build 19045; UI render: default; VCL: win
Locale: en-US (en_US); UI: en-US
Calc: CL threaded.

I know that the problem exists in older versions, but I have currently no time
to look for the oldest one.

I could not find an existing bug report.

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

[Libreoffice-bugs] [Bug 97161] Size of Dimension line objects in small scales are buggy

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

--- Comment #10 from Regina Henschel  ---
An option is missing to set the two reference points of the dimension line is
missing.

Bug 145969 contains a proposal how to change and extend the "Position and Size"
dialog to allow setting object specific values.

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

[Libreoffice-bugs] [Bug 97161] Size of Dimension line objects in small scales are buggy

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

Regina Henschel  changed:

   What|Removed |Added

 CC||ville...@t-online.de

--- Comment #9 from Regina Henschel  ---
*** Bug 141382 has been marked as a duplicate of this bug. ***

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

[Libreoffice-bugs] [Bug 141382] Dimension line width is displayed incorrectly in Position and Size dialog after using the dialog to adjust it

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

--- Comment #6 from Regina Henschel  ---


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

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

[Libreoffice-bugs] [Bug 141382] Dimension line width is displayed incorrectly in Position and Size dialog after using the dialog to adjust it

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

Regina Henschel  changed:

   What|Removed |Added

 CC||rb.hensc...@t-online.de
 Resolution|--- |DUPLICATE
 Status|NEW |RESOLVED

--- Comment #5 from Regina Henschel  ---
The 'Position and Size' dialog does not show the distance between the reference
points of the dimension line but the position and size of the bounding box of
the object, including the text. An option to set the reference points directly
is missing.

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

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

[Libreoffice-bugs] [Bug 135431] Position and Size of dimension lines depend on each other

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

Regina Henschel  changed:

   What|Removed |Added

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

--- Comment #7 from Regina Henschel  ---
I collect all similar reports to bug 97161 to make the problem better visible.

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

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

[Libreoffice-bugs] [Bug 97161] Size of Dimension line objects in small scales are buggy

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

--- Comment #8 from Regina Henschel  ---
*** Bug 135431 has been marked as a duplicate of this bug. ***

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

[Libreoffice-bugs] [Bug 155721] [FILEOPEN] ODS office:annotation color

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

Maxim Monastirsky  changed:

   What|Removed |Added

 CC||momonas...@gmail.com

--- Comment #2 from Maxim Monastirsky  ---
Should be fixed already by commit 0ee9501c0b7dc1a291715fff9c1934b1c08cb654.
Please retest with a recent 7.6/master build.

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

[Libreoffice-bugs] [Bug 155721] [FILEOPEN] ODS office:annotation color

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

--- Comment #1 from SheetJS  ---
Created attachment 187774
  --> https://bugs.documentfoundation.org/attachment.cgi?id=187774=edit
specimen

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

[Libreoffice-bugs] [Bug 155721] New: [FILEOPEN] ODS office:annotation color

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

Bug ID: 155721
   Summary: [FILEOPEN] ODS office:annotation color
   Product: LibreOffice
   Version: 7.5.4.2 release
  Hardware: All
OS: All
Status: UNCONFIRMED
  Severity: normal
  Priority: medium
 Component: Calc
  Assignee: libreoffice-bugs@lists.freedesktop.org
  Reporter: d...@sheetjs.com

Description:
When reading ODS files, a blue background is incorrectly applied to visible
notes.  It is not applied to hidden notes.

Steps to Reproduce:
1. Open attachment
2. Right-click cell A3 > "Show Comment"

Actual Results:
Visible comment has blue fill, hidden comment has yellow fill when revealed

Expected Results:
Both comments should be the default yellow


Reproducible: Always


User Profile Reset: Yes

Additional Info:
Neither annotation style specifies a fill color:

```xml

  


  

```

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

[Libreoffice-bugs] [Bug 146986] Expanding the caption frame increases image size, but not at DOCX export

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

--- Comment #7 from Justin L  ---
repro 7.6+

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

[Libreoffice-bugs] [Bug 155199] LO inconsistently renders Calibri font ligatures (11pt, zoom 100% or 110%) on Linux w gtk3

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

Eyal Rozenberg  changed:

   What|Removed |Added

 Status|RESOLVED|VERIFIED

--- Comment #13 from Eyal Rozenberg  ---
Ok, verifying.

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

[Libreoffice-bugs] [Bug 100524] [FILEOPEN] nested if fields lose spaces between page number/count fields lost on import of specific DOCX

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

Justin L  changed:

   What|Removed |Added

 OS|Linux (All) |All

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

[Libreoffice-bugs] [Bug 100524] [FILEOPEN] nested if fields lose spaces between page number/count fields lost on import of specific DOCX

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

Justin L  changed:

   What|Removed |Added

Summary|[FILEOPEN] Spaces between   |[FILEOPEN] nested if fields
   |page number/count fields|lose spaces between page
   |lost on import of specific  |number/count fields lost on
   |DOCX|import of specific DOCX

--- Comment #8 from Justin L  ---
repro 7.6+, including the superfluous 6.
This is a multiple "if" fields combining to form one output.
  if DOCPROPERTY mailing-aan = 1 "" "if NUMPAGES 1 == 1 "" "DOCPROPERTY _pagina
 Pagina PAGE 1 DOCPROPERTY _van van NUMPAGES 5"

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

[Libreoffice-bugs] [Bug 104832] CRASH when selecting OLE (Visio?) object (in a DOC file)

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

--- Comment #14 from Hossein  ---
What do you mean by "selecting"? Just select the object using a single click?
For me LO 7.6 dev master didn't crash. Also, by double clicking on the object I
can edit that in LibreOffice Draw without problem.

Not reproducible with LO 7.6 dev master:

Version: 7.6.0.0.alpha1+ (X86_64) / LibreOffice Community
Build ID: 52f70f04bdc586a072141e069d451a979c5f4cb7
CPU threads: 20; OS: Windows 10.0 Build 22621; UI render: Skia/Vulkan; VCL: win
Locale: en-US (en_DE); UI: en-US
Calc: CL threaded

I also don't have Visio installed.

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

[Libreoffice-bugs] [Bug 155001] Lost or malformed spellcheck underlines in rotated shapes

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

⁨خالد حسني⁩  changed:

   What|Removed |Added

 OS|Linux (All) |All
   Hardware|x86-64 (AMD64)  |All

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

[Libreoffice-bugs] [Bug 155199] LO inconsistently renders Calibri font ligatures (11pt, zoom 100% or 110%) on Linux w gtk3

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

--- Comment #12 from ⁨خالد حسني⁩  ---
You can control any font feature including ligatures from the font features
dialog.

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

[Libreoffice-bugs] [Bug 107407] DOCX: Shadow, emboss and engrave text effects not imported correctly

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

--- Comment #9 from Justin L  ---
repro 7.6+

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

[Libreoffice-bugs] [Bug 155719] Simple option to reinterpret data as numbers when they have wrong decimal separator

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

--- Comment #1 from Eike Rathke  ---
(In reply to Yann Salmon from comment #0)
> In locales where the decimal separator is not the dot, it is not infrequent
> to be confronted with documents where some or all numbers have been written
> with a dot instead of the traditional separator.
> 
> They are thus treated as text by LO.
That's not true. If they were entered as numeric values before then they stay
numeric, regardless of the locale they are displayed in. Separators and formats
of the current locale are used, unless a fixed locale's attribution was
assigned. But cell content does not change to text just because a different
locale's separator is used for display.

However, see
https://wiki.documentfoundation.org/Faq/Calc/How_to_convert_number_text_to_numeric_data

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

[Libreoffice-bugs] [Bug 155199] LO inconsistently renders Calibri font ligatures (11pt, zoom 100% or 110%) on Linux w gtk3

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

--- Comment #11 from Eyal Rozenberg  ---
(In reply to ⁨خالد حسني⁩ from comment #10)
> No idea what we should do here then, we are respecting the font and the
> settings.

Well, if we don't do something automatically, we should at least let the user
disable ligatures on a per-document-and-font-family/font-family-variant basis.

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

  1   2   3   >