[Libreoffice-bugs] [Bug 153299] Add drop-down menu to "Strikethrough" options

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=153299

V Stuart Foote  changed:

   What|Removed |Added

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

--- Comment #2 from V Stuart Foote  ---
Actually we currently have a drop down, found in the 'Character' dialog ->
'Font Effects'

1. focus and select word or sentence (2 click, 3 click)
2. context menu (right mouse or keyboard)
3. character dialog
4. 'Font Effects'
5. 'Strikethrough'

But currently the only defined UNO action (as used by Toolbar, Sidebar or
Notebook Bar) is .uno:StrikeOut which applies the "Single" strikethrough
effect. So request could be for additional UNO controls to use for
customization. 

Or more simply to provide a UI control similar to the textunderlinecontrol.ui
but for the strikeouts for the Toolbar, Sidebar or Notebookbar providing more
direct access to a drop list of:

RID_SVXITEMS_STRIKEOUT_NONE
RID_SVXITEMS_STRIKEOUT_SINGLE
RID_SVXITEMS_STRIKEOUT_DOUBLE
RID_SVXITEMS_STRIKEOUT_DONTKNOW
RID_SVXITEMS_STRIKEOUT_BOLD
RID_SVXITEMS_STRIKEOUT_SLASH
RID_SVXITEMS_STRIKEOUT_X

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

[Libreoffice-bugs] [Bug 98440] Copy and Paste of table rows un-does merging

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=98440

--- Comment #6 from Anandhi k  ---
yes Reproduced

STEPS TO REPRODUCE:

1. Start Writer, insert a table with (say) 5 rows and 5 columns
2. Select two adjacent cells in a row, click the "Merge" icon (or
Table->Merge).\

   Insert unique text into every visible cell in the row

3. Select all cells in the row.  Control-C to copy
4. Select all cells in another row.  Control-P to paste

RESULTS:  The merged-ness of the copied cells is lost, and text is pasted into
the wrong cells.  Text in the first column is duplicated in the last column

EXPECTED RESULTS: The pasted-onto row should look exactly like the source row.

I had a commplicate with result if i use control-v instead of control -p in got
a excepted result 


Environment:Linux Mint 21 Cinnamon
Version: 7.6.0.0.alpha0+ (X86_64) / LibreOffice Community
Build ID: 620ad1b7ae06d6f053fb2c9b57af96b736c04e57
CPU threads: 8; OS: Linux 5.15; UI render: default; VCL: gtk3
Locale: en-IN (en_IN); UI: en-US
Calc: threaded

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

[Libreoffice-bugs] [Bug 152976] Print preview should start with right page, if document is in book view mode

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=152976

Dieter  changed:

   What|Removed |Added

Summary|Print preview should show   |Print preview should start
   |left/right pages settings   |with right page, if
   ||document is in book view
   ||mode

--- Comment #3 from Dieter  ---
(In reply to Heiko Tietze from comment #2)
> We have a two-pages preview with one always on the left and a book mode that
> starts right (odd pages left). Is the problem to run the preview in the same
> mode as the editing?

Yes, print preview should start with right page, if document view is book mode

First I thought, that it would also a good idea to have print preview with
right page at the start, if document also contains left and right page styles.
But of course there might be situations, where page style aren' used correctly.
So I've changed bug summary and hope you agree.

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

[Libreoffice-bugs] [Bug 152946] when sidebar is wider that some value, most of the final row of widgets is lost below the sidebar border, and is unreadable (but not necessarily unusable)

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=152946

Dieter  changed:

   What|Removed |Added

 CC||dgp-m...@gmx.de
 Whiteboard| QA:needsComment|

--- Comment #1 from Dieter  ---
I can't confirm with

Version: 7.5.0.2 (X86_64) / LibreOffice Community
Build ID: c0dd1bc3f1a385d110b88e26ece634da94921f58
CPU threads: 4; OS: Windows 10.0 Build 19044; UI render: Skia/Raster; VCL: win
Locale: de-DE (de_DE); UI: en-GB
Calc: CL threaded

but I'm also not sure, if I've grasped the steps to reproduce. Perhaps it is
possible for you to add a screencast? Might also be relevant to know the size
and resolution of your display.

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

[Libreoffice-bugs] [Bug 153300] New: Format->Text menu name is confusing in Calc

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=153300

Bug ID: 153300
   Summary: Format->Text menu name is confusing in Calc
   Product: LibreOffice
   Version: unspecified
  Hardware: All
OS: All
Status: UNCONFIRMED
  Keywords: needsUXEval, topicUI
  Severity: normal
  Priority: medium
 Component: Calc
  Assignee: libreoffice-bugs@lists.freedesktop.org
  Reporter: mikekagan...@hotmail.com
CC: er...@redhat.com

In Calc, there is an important concept of cells' number format, which
determines both content formatting, and recognition (conversion) of newly
entered text. It is available through Format->Cells (Ctrl+1), "Numbers" tab
[1]. The number formats are divided into categories, e.g. Number, Date, Text.
The latter category, when applied to a cell, makes all following entry into the
respective cell to be not converted to numbers and formulas, which is important
for many use cases.

There is rather established, common across many spreadsheet applications, idiom
like "format cells as text". It means precisely the application of a number
format from the respective category.

In Calc, since 5.1, there is Format->Text menu [2]. It lists assorted items,
some of which apply character formatting, others may edit the cell text itself
(tdf#152197). These elements are not connected to the number formats discussed
above.

The name of the Format->Text menu creates a confusion in users [3]. People who
get an advice to format cells as text, may try the Format->Text subentries.

The proposal is to rename the Text menu name (which is common across different
modules, i.e. Writer, Draw, ...) to something else - like maybe "Text Effects",
or "String", or whatever (I realize that my wording is awful - I hope it just
gives an idea).

[1]
https://help.libreoffice.org/7.5/en-US/text/shared/01/05020300.html?DbPAR=CALC
[2]
https://help.libreoffice.org/7.5/en-US/text/shared/submenu_text.html?&DbPAR=CALC
[3] https://ask.libreoffice.org/t/keeping-zeros-infront-of-a-number/83306/3

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

[Libreoffice-bugs] [Bug 152865] FILEOPEN RTF Paragraph below frame wrapped differently than in Word

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=152865

Dieter  changed:

   What|Removed |Added

 CC||dgp-m...@gmx.de
 Whiteboard| QA:needsComment|

--- Comment #4 from Dieter  ---
I confirm it with

Version: 7.5.0.2 (X86_64) / LibreOffice Community
Build ID: c0dd1bc3f1a385d110b88e26ece634da94921f58
CPU threads: 4; OS: Windows 10.0 Build 19044; UI render: Skia/Raster; VCL: win
Locale: de-DE (de_DE); UI: en-GB
Calc: CL threaded

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

[Libreoffice-bugs] [Bug 114814] EDITING: Form Table control Field Copy disfunctional

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=114814

--- Comment #7 from Robert Großkopf  ---
Bug is still the same. "Copying" a listbox or a combobox won't copy the field
content but copies a numeric field (listbox) or a text field (combobox) with
connection to the datasource.

Tested with LO 7.4.5.1 ob OpenSUSE 15.3 64bit rpm Linux

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

[Libreoffice-bugs] [Bug 153272] Writer Macro Find with certain Search Attributes performs Replacement.

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=153272

Commit Notification  changed:

   What|Removed |Added

 Whiteboard||target:7.6.0

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

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

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=126008

--- Comment #72 from Sasikumar  ---
OS :linux mint
LIBRE OFFICE VERSION:7.3.7.2
STEPS:Description:
When I insert a row above an existing row within a table, LibreWriter reverts
the selected existing row to the default format. This is repeatable in multiple
documents and different tables. I am using LibreOffice 6.2.4.2 (x64).

Steps to Reproduce:
1.Select row (highlights the row)
2.Click Table | Insert | Rows Above
3.
RESULT:bug partially reproduce
reason:font size is automatically changed and left alignments are not changed

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

[Libreoffice-bugs] [Bug 140184] Sort changes relative references same as absolute ones

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=140184

--- Comment #9 from Saravanan U  ---
Exactly as old Bug 81633. Not present in v.6, present in v.7.
(1) open the attachment
(2) select the rows from 2 to 6
(3) sort ascending in column B (date)
The column E (each line with a relative reference to preceding line) is changed
in the same way of column F (each line with an absolute reference to preceding
column).

software:linux 5.15

status : output produce ...

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

[Libreoffice-bugs] [Bug 150451] Some text boxes in dialogs do not have borders in dark mode (kf5)

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=150451

--- Comment #22 from Michael Weghorn  ---
(In reply to Rafael Lima from comment #21)
> I have no scaling on my end. I'm using a 1080p display with 100% scaling.
> When I use QT_SCALE_FACTOR=2.0 I also get no borders.
> 
> But in my case I get no borders regardless of QT_SCALE_FACTOR.

Interesting. So there must still be some other aspect that causes this.

> BTW the best dialog to check these borders is Tools - Options - User Data,
> because it has a lot of text boxes and it makes it easier to see the results.

Here too, all textboxes have borders for me with QT_SCALE_FACTOR=1 or
QT_SCALE_FACTOR=1.25, but no textbox has borders with QT_SCALE_FACTOR=1.5 or
QT_SCALE_FACTOR=2. (The comboboxes have borders for all scale factors.)

> Yes... I'll take a look. If I can't fix it, I'll share my findings here.

Great, thanks!

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

[Libreoffice-bugs] [Bug 140184] Sort changes relative references same as absolute ones

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=140184

Saravanan U  changed:

   What|Removed |Added

 CC||saravananu4...@gmail.com

--- Comment #8 from Saravanan U  ---
Created attachment 185039
  --> https://bugs.documentfoundation.org/attachment.cgi?id=185039&action=edit
i got output ,form the bug

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

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

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=124891
Bug 124891 depends on bug 152073, which changed state.

Bug 152073 Summary: Glitch rendering line numbers in Basic IDE editor (kf5 only)
https://bugs.documentfoundation.org/show_bug.cgi?id=152073

   What|Removed |Added

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

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

[Libreoffice-bugs] [Bug 102495] [META] KDE VCL backend bugs and enhancements

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=102495
Bug 102495 depends on bug 152073, which changed state.

Bug 152073 Summary: Glitch rendering line numbers in Basic IDE editor (kf5 only)
https://bugs.documentfoundation.org/show_bug.cgi?id=152073

   What|Removed |Added

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

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

[Libreoffice-bugs] [Bug 152801] Input text for a formatted text box shows up as light gray instead of black.

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=152801

--- Comment #5 from Kate  ---
Unable to replicate (Windows 10), with or without dark mode. 

The provided PDF displayed light gray text as described (as well as appearing
oversized and inappropriately vertically aligned); however, when I exported the
provided ODT, the newly created pdf displayed black text. I also tried
following the steps as described (creating a new document/pdf) to no avail. 

Document settings of the pdfs (as provided by Adobe Acrobat Reader) displayed
similar font details for both the light gray and black results. Settings within
odt also seemed identical though, again, I was unable to replicate when
exporting so could not reliably identify potential differences.

Not sure if more screenshots of settings would be beneficial or if it could be
OS-related.

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

[Libreoffice-bugs] [Bug 130961] LibreOffice Calc - Calculations frozen after solver and lost named ranges

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=130961

--- Comment #12 from biswaranjanpatra2...@gmail.com ---
Here is the version information requested:

Version: 6.0.7.3
Build ID: 1:6.0.7-0ubuntu0.18.04.10
CPU threads: 4; OS: Linux 5.3; UI render: default; VCL: gtk3; 
Locale: en-GB (en_GB.UTF-8); Calc: group

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

[Libreoffice-bugs] [Bug 150372] Clicking on "Character..." makes application freeze for ~1 minute in Win10 (RegeneratePrintDeviceCapabilities)

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=150372

--- Comment #14 from Rahamanshariff A  ---
1-step followed 

   1. Select a word
   2. Right-click, click "Character" -> "Character..."

2-Environment

   os windows 10, 8gp ram,intel i3,64bit

3-Result 

   bug not produce

4-status
   unconfirmed

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

[Libreoffice-bugs] [Bug 153299] Add drop-down menu to "Strikethrough" options

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=153299

Wolf Icefang  changed:

   What|Removed |Added

 Status|UNCONFIRMED |NEW
 Ever confirmed|0   |1

--- Comment #1 from Wolf Icefang  ---
I'll confirm this. There is no dropdown for choosing strikethrough type no
matter what User Interface style you choose (Standard toolbar, tabbed,
groupedbar compact, etc.).

If you look in the Font Effects window
https://help.libreoffice.org/7.4/en-US/text/shared/01/05020200.html you'll find
a variety of strikethrough options.

In favor:
 1.  Adding a dropdown arrow takes up relatively little space.
 2.  Some of the strikethrough options, like / and X, are very unique.
 3.  It's not even possible to set the various strikethrough types to keyboard
shortcuts, so it's very inconvenient to use them.

Against (devil's advocate):
 1.  Setting non-standard strikethrough is a pretty niche use case that people
don't really need to discover or use.
 2.  There are quite a few extra underline types available in Font Effects...
only a select few were chosen to reside in the main UI's underline dropdown.
Which strikethrough options do we want to choose?

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

[Libreoffice-bugs] [Bug 150472] Incorrect rendering of LibreOffice Logo in StartCenter

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=150472

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 148994] Libre office writer crash on start in Windows 10

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=148994

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 148994] Libre office writer crash on start in Windows 10

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=148994

--- Comment #7 from QA Administrators  ---
Dear minimaal6tek...@gmail.com,

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 140027] EDITING inserting rows before pivot table in row 1 copies format and images from headings

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=140027

--- Comment #3 from QA Administrators  ---
Dear Robert Lacroix,

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 98972] Writer table: changing data changes cell format; changing format changes cell data

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=98972

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

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 98265] Poor formatting in Table of Contents with Multiple Fonts

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=98265

--- Comment #11 from QA Administrators  ---
Dear Tim Chambers,

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 97310] AutoCorrect Doesn't Work with Zero-width Space

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=97310

--- Comment #5 from QA Administrators  ---
Dear Nathan Wells,

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 131001] Using PDF image using shfill displays correctly, but fails to export to PDF correctly

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=131001

--- Comment #5 from QA Administrators  ---
Dear Ulrich Windl,

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 136583] Some resources from embedded PDF files (mainly those created by Scribus) disappear when exporting to PDF

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=136583

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

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 107896] MAILMERGE : "Exchange database" misses "next record" fields

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=107896

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

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 115239] BOOKMARKS: You can't delete a bookmark, if you only delete the word (without selecting something around the word)

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=115239

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

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

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

If you have time, please do the following:

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

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

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

Please DO NOT

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


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

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


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

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

Warm Regards,
QA Team

MassPing-UntouchedBug

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

[Libreoffice-bugs] [Bug 114814] EDITING: Form Table control Field Copy disfunctional

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=114814

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

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

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

If you have time, please do the following:

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

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

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

Please DO NOT

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


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

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


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

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

Warm Regards,
QA Team

MassPing-UntouchedBug

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

[Libreoffice-bugs] [Bug 153299] New: Add drop-down menu to "Strikethrough" options

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=153299

Bug ID: 153299
   Summary: Add drop-down menu to "Strikethrough" options
   Product: LibreOffice
   Version: unspecified
  Hardware: All
OS: All
Status: UNCONFIRMED
  Severity: enhancement
  Priority: medium
 Component: UI
  Assignee: libreoffice-bugs@lists.freedesktop.org
  Reporter: j...@mail.ossii.com.tw

Description:
Please add drop-down menu to "Strikethrough" options, for now, we have this
feature for "Underline" options.

Steps to Reproduce:
Click "Strikethrough" options.

Actual Results:
Just add strikethrough to text.

Expected Results:
Shows drop-down menu to select detail options.


Reproducible: Always


User Profile Reset: No

Additional Info:
Version: 7.4.5.1 / LibreOffice Community
Build ID: 40(Build:1)
CPU threads: 8; OS: Linux 6.1; UI render: default; VCL: kf5 (cairo+xcb)
Locale: zh-TW (zh_TW.UTF-8); UI: zh-TW
7.4.5-1
Calc: CL

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

[Libreoffice-bugs] [Bug 66580] exported PDF is invalid because of forbidden custom keys in the trailer

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=66580

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

https://git.libreoffice.org/core/commit/9740331d8bc56a9b6fbe3e4c1b26fb97f6639cc6

tdf#66580 write more metadata to embedded and attached files

It will be available in 7.6.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 153227] TOC Dialog Does Not Fit Screen

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=153227

--- Comment #16 from m.a.riosv  ---
To me, the issue is that the window doesn't keep with a so low resolution of
1024x768.

More than a bug should be a request for enhancement to make the window
resizable, or modify their design to make it more narrow and less high, to keep
with that resolution.

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

[Libreoffice-bugs] [Bug 153141] bizarre upper-, lower-case

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=153141

m.a.riosv  changed:

   What|Removed |Added

 CC|miguelangelrv@libreoffice.o |
   |rg  |

--- Comment #5 from m.a.riosv  ---
(In reply to TorrAB from comment #4)
> Why do I "have a direct format for 'orrens' as lowercase" ?
Only you can know.
> Style Heading1 has FontEffects>Case = Without, not UPPERCASE.
Fine
> ^m should not uppercase 'orrens'
Because it was modified applying a direct format, which have precedence over
styles.
> Why does inserting the M work differently?

BTW, enough for me.

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

[Libreoffice-bugs] [Bug 108897] [META] XLSX (OOXML) bug tracker

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=108897

Stéphane Guillou (stragu)  changed:

   What|Removed |Added

 Depends on||153241


Referenced Bugs:

https://bugs.documentfoundation.org/show_bug.cgi?id=153241
[Bug 153241] FILEOPEN: VmlDrawingsPart .emf embedded images are not shown
correctly; elements moved down on Y axis
-- 
You are receiving this mail because:
You are the assignee for the bug.

[Libreoffice-bugs] [Bug 103859] [META] EMF/WMF (Enhanced/Windows Metafile) bugs and enhancements

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=103859

Stéphane Guillou (stragu)  changed:

   What|Removed |Added

 Depends on||153241


Referenced Bugs:

https://bugs.documentfoundation.org/show_bug.cgi?id=153241
[Bug 153241] FILEOPEN: VmlDrawingsPart .emf embedded images are not shown
correctly; elements moved down on Y axis
-- 
You are receiving this mail because:
You are the assignee for the bug.

[Libreoffice-bugs] [Bug 153241] FILEOPEN: VmlDrawingsPart .emf embedded images are not shown correctly; elements moved down on Y axis

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=153241

Stéphane Guillou (stragu)  changed:

   What|Removed |Added

 Blocks||103859, 108897

--- Comment #8 from Stéphane Guillou (stragu) 
 ---
Thanks, Ilmari. You're right, what I saw in 6.2 and described at the end of
comment 1 was the impact of the famous row height recalculation commit
1e55a47e89a9d9d6cf9cb3993484022aaf2c097b. Sorry about the confusion.

Adding metas but you might be able to think of better ones.


Referenced Bugs:

https://bugs.documentfoundation.org/show_bug.cgi?id=103859
[Bug 103859] [META] EMF/WMF (Enhanced/Windows Metafile) bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=108897
[Bug 108897] [META] XLSX (OOXML) bug tracker
-- 
You are receiving this mail because:
You are the assignee for the bug.

[Libreoffice-bugs] [Bug 152346] 7.5 alpha Windows 32-bit crashes on startup

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=152346

David  changed:

   What|Removed |Added

 Ever confirmed|1   |0
 Status|NEEDINFO|UNCONFIRMED

--- Comment #5 from David  ---
(In reply to Stéphane Guillou (stragu) from comment #4)
> Which installers did you use, David? And nobu, same question?

I just tried the latest 7.5.0.3_x86 installer on both Windows 7 32 and 64-bit
machines with any previous profile directory removed and the computer rebooted.
LibreOffice still crashes on initialization. The earliest 7.5alpha that I know
I tested is dated 11-24-2022. And all the ones I've tried since then have
continued to fail. Default installations were used. KB3063858 is installed. I
have not tried it on any later versions of Windows.

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

[Libreoffice-bugs] [Bug 152738] LO75RC1: Automatic spell-check not underlining misspelled words; dialog doesn't use paragraph's language

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=152738

--- Comment #10 from Stéphane Guillou (stragu) 
 ---
Created attachment 185038
  --> https://bugs.documentfoundation.org/attachment.cgi?id=185038&action=edit
screenshot of issue in LO 7.5.0.2

This annotated screenshot shows the spellcheck dialog failing at using the
paragraph's language, French.

(Forget about that issue with whitespace inserted in the sentence, in comment
7, that must have been an error on my end. Haven't seen it again.)

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

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

[Libreoffice-bugs] [Bug 152738] LO75RC1: Automatic spell-check not underlining misspelled words; dialog doesn't use paragraph's language

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=152738

--- Comment #9 from Stéphane Guillou (stragu) 
 ---
(In reply to Stéphane Guillou (stragu) from comment #8)
> Bibisected with linux-64-7.5 repo [...]

Noel, note that I bibisected the "language is [none] in spelling dialog" issue,
as described in comment 7.

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

[Libreoffice-bugs] [Bug 153223] Red wavy lines under misspelt words disappears when viewing page at zoom factor of 160% or greater (macOS)

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=153223

Stéphane Guillou (stragu)  changed:

   What|Removed |Added

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

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

[Libreoffice-bugs] [Bug 152738] LO75RC1: Automatic spell-check not underlining misspelled words; dialog doesn't use paragraph's language

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=152738

Stéphane Guillou (stragu)  changed:

   What|Removed |Added

  Regression By||Noel Grandin
   Keywords|bibisectRequest |bibisected, bisected
   See Also||https://bugs.documentfounda
   ||tion.org/show_bug.cgi?id=15
   ||3223
 CC||noelgran...@gmail.com
Summary|LO75RC1: Automatic  |LO75RC1: Automatic
   |spell-check on macOS not|spell-check not underlining
   |underlining misspelled  |misspelled words; dialog
   |words   |doesn't use paragraph's
   ||language
   Priority|medium  |high

--- Comment #8 from Stéphane Guillou (stragu) 
 ---
To bibisect, I had to first make sure that the extra dictionary was at the
right spot. I copied it from my 7.5 installation

/opt/libreoffice7.5/share/extensions/dict-fr

and pasted in the local bibisect repo:

[...]/linux-64-7.5/instdir/share/extensions/dict-fr

Bibisected with linux-64-7.5 repo to first bad commit
84e282373a120d0a41bb96378085b253e8568e97 which points to core commit:
commit  b484e5d9e0d22b794c2d1c73741191836158a4ad[log]
author  Noel Grandin Sat Oct 08 07:54:48 2022 +0200
committer   Noel Grandin  Sun Oct 09
19:16:29 2022 +0200
treea1f8d3d3c7d0d5a01284e400f4c9d6f5d5dba260
parent  ca1378b6552251743c92a19f9ce8b3833557b548 [diff]
use more SwPosition::Assign
part of the process of hiding the internals of SwPosition
Change-Id: I20842b90d0abb4435d6b06970c2545229268e5e8
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/141097

Noel, can you please have a look?

Martin, regarding the underline issue: could you please check if it is at all
related to the zoom level you are using? See bug 153223. An annotated
screenshot of this aspect of the issue would be helpful.

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

[Libreoffice-bugs] [Bug 96000] [META] Spelling and grammar checking bugs and enhancements

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=96000
Bug 96000 depends on bug 151972, which changed state.

Bug 151972 Summary: Auto spell checker does not work
https://bugs.documentfoundation.org/show_bug.cgi?id=151972

   What|Removed |Added

 Status|NEEDINFO|RESOLVED
 Resolution|--- |DUPLICATE

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

[Libreoffice-bugs] [Bug 153223] Red wavy lines under misspelt words disappears when viewing page at zoom factor of 160% or greater (macOS)

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=153223

Stéphane Guillou (stragu)  changed:

   What|Removed |Added

 CC||woodrack...@yahoo.com

--- Comment #9 from Stéphane Guillou (stragu) 
 ---
*** Bug 151972 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 151972] Auto spell checker does not work

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=151972

Stéphane Guillou (stragu)  changed:

   What|Removed |Added

 Status|NEEDINFO|RESOLVED
 Resolution|--- |DUPLICATE

--- Comment #3 from Stéphane Guillou (stragu) 
 ---
Looking at the screenshot, it looks like a high zoom level is used.
I think it's a duplicate of bug 153223, and I'm marking as such, but David: can
you please confirm that this depends on the zoom level, i.e. that the red lines
come back at a lower zoom level?

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

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

[Libreoffice-bugs] [Bug 143781] [META] Development- and code-related bug reports and tasks

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=143781

Hossein  changed:

   What|Removed |Added

 Depends on||153294


Referenced Bugs:

https://bugs.documentfoundation.org/show_bug.cgi?id=153294
[Bug 153294] Use copy_if, find_if or remove_if to simplify loops
-- 
You are receiving this mail because:
You are the assignee for the bug.

[Libreoffice-bugs] [Bug 153294] Use copy_if, find_if or remove_if to simplify loops

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=153294

Hossein  changed:

   What|Removed |Added

 CC||mentoring@documentfoundatio
   ||n.org
Version|unspecified |4.4 all versions
   Keywords||difficultyBeginner,
   ||easyHack, skillCpp,
   ||topicCleanup
 Blocks||143781


Referenced Bugs:

https://bugs.documentfoundation.org/show_bug.cgi?id=143781
[Bug 143781] [META] Development- and code-related bug reports and tasks
-- 
You are receiving this mail because:
You are the assignee for the bug.

[Libreoffice-bugs] [Bug 125770] Smartart: Connection lines have wrong position

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=125770

--- Comment #9 from Hossein  ---
Still reproducible with the latest LO 7.6 dev master:
Version: 7.6.0.0.alpha0+ (X86_64) / LibreOffice Community
Build ID: 1af03aaa35dc9758a9702cddf48d9aad02ec7a94
CPU threads: 4; OS: Windows 10.0 Build 19045; UI render: Skia/Raster; VCL: win
Locale: fa-IR (fa_IR); UI: en-US
Calc: threaded

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

[Libreoffice-bugs] [Bug 153297] A complex formula does not work in Calc 7.4.x

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=153297

m.a.riosv  changed:

   What|Removed |Added

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

--- Comment #2 from m.a.riosv  ---
The only way, it's with a sample file to verify the issue, please attach it.

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

[Libreoffice-bugs] [Bug 153297] A complex formula does not work in Calc 7.4.x

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=153297

--- Comment #1 from m.a.riosv  ---
*** Bug 153298 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 153298] A complex formula does not work in Calc 7.4.x

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=153298

m.a.riosv  changed:

   What|Removed |Added

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

--- Comment #1 from m.a.riosv  ---


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

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

[Libreoffice-bugs] [Bug 34391] FORMATTING: Introduce table cell styles

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=34391

Hagar Delest  changed:

   What|Removed |Added

 CC||delest.ha...@gmail.com

--- Comment #30 from Hagar Delest  ---
Cell styles (primary target of this report) would also benefit the file
structure. Today, cell styles are applied inside every single table like:
...
Meaning that if cells have the same formatting in several tables, then the
"style" will be duplicated for each table.

Having cell styles recognized like character or paragraph styles would thus
optimize the XML structure.

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

[Libreoffice-bugs] [Bug 153298] New: A complex formula does not work in Calc 7.4.x

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=153298

Bug ID: 153298
   Summary: A complex formula does not work in Calc 7.4.x
   Product: LibreOffice
   Version: 7.4.5.1 release
  Hardware: x86-64 (AMD64)
OS: Windows (All)
Status: UNCONFIRMED
  Severity: normal
  Priority: medium
 Component: Calc
  Assignee: libreoffice-bugs@lists.freedesktop.org
  Reporter: yurijivanov...@gmail.com

Description:
In the Calc table of LibreOffice 7.3.7 and earlier, everything worked. In
version 7.4.0 - 7.4.5, in the automatically filled sheet "DOWN" after any
change of parameters in the sheets "LIST" ... "Ser", entries disappear.

Steps to Reproduce:
1.The error cannot be described, because it appears in a specific table.
But I don't see how to send it to you.
2.
3.

Actual Results:
When changing any parameter in the "LIST" ... "Ser" sheets, the data in the
"DOWN" sheet disappears.

Expected Results:
Data should not disappear


Reproducible: Always


User Profile Reset: No

Additional Info:
The error occurs only in version 7.4.x. When returning to Calc 7.3.7 and
earlier, the defect is absent, and then the damaged table can be restored by
recalculating the fields of the "DOWN" sheet.

The sample table is ready for you. Its size is slightly larger than 4 Mb. Where
should you send it?

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

[Libreoffice-bugs] [Bug 153297] New: A complex formula does not work in Calc 7.4.x

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=153297

Bug ID: 153297
   Summary: A complex formula does not work in Calc 7.4.x
   Product: LibreOffice
   Version: 7.4.5.1 release
  Hardware: x86-64 (AMD64)
OS: Windows (All)
Status: UNCONFIRMED
  Severity: normal
  Priority: medium
 Component: Calc
  Assignee: libreoffice-bugs@lists.freedesktop.org
  Reporter: yurijivanov...@gmail.com

Description:
In the Calc table of LibreOffice 7.3.7 and earlier, everything worked. In
version 7.4.0 - 7.4.5, in the automatically filled sheet "DOWN" after any
change of parameters in the sheets "LIST" ... "Ser", entries disappear.

Steps to Reproduce:
1.The error cannot be described, because it appears in a specific table.
But I don't see how to send it to you.
2.
3.

Actual Results:
When changing any parameter in the "LIST" ... "Ser" sheets, the data in the
"DOWN" sheet disappears.

Expected Results:
Data should not disappear


Reproducible: Always


User Profile Reset: No

Additional Info:
The error occurs only in version 7.4.x. When returning to Calc 7.3.7 and
earlier, the defect is absent, and then the damaged table can be restored by
recalculating the fields of the "DOWN" sheet.

The sample table is ready for you. Its size is slightly larger than 4 Kb. Where
should you send it?

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

[Libreoffice-bugs] [Bug 109527] [META] Spell check dialog bugs and enhancements

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=109527

Stéphane Guillou (stragu)  changed:

   What|Removed |Added

 Depends on||152738


Referenced Bugs:

https://bugs.documentfoundation.org/show_bug.cgi?id=152738
[Bug 152738] LO75RC1: Automatic spell-check on macOS not underlining misspelled
words
-- 
You are receiving this mail because:
You are the assignee for the bug.

[Libreoffice-bugs] [Bug 152738] LO75RC1: Automatic spell-check on macOS not underlining misspelled words

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=152738

Stéphane Guillou (stragu)  changed:

   What|Removed |Added

 Blocks||109527
   Keywords||bibisectRequest, regression
 Status|UNCONFIRMED |NEW
 OS|macOS (All) |All
 Ever confirmed|0   |1


Referenced Bugs:

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

[Libreoffice-bugs] [Bug 152738] LO75RC1: Automatic spell-check on macOS not underlining misspelled words

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=152738

--- Comment #7 from Stéphane Guillou (stragu) 
 ---
Created attachment 185037
  --> https://bugs.documentfoundation.org/attachment.cgi?id=185037&action=edit
test document

I think I can partially reproduce the issue.

I based this example document on the LO manual Martin linked, using page 2.
I added a paragraph in French before the original paragraph, including some
erroneous words for French: "paragraphee", "moot", "spellcheck".
These words are underlined properly. However:

1. Place cursor at beginning of document
2. Tools > Spelling

Results:
Text language is "[None]", nothing is highlighted in the current sentence, a
word is shown split, and only the "Add to dictionary" button is available.

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

No issue in 7.4, the spelling tool goes straight to the first word underlined,
buttons active, word highlighted, language correct.

Version: 7.4.5.1 / LibreOffice Community
Build ID: 9c0871452b3918c1019dde9bfac75448afc4b57f
CPU threads: 8; OS: Linux 5.15; UI render: default; VCL: gtk3
Locale: en-AU (en_AU.UTF-8); UI: en-US
Calc: threaded

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

[Libreoffice-bugs] [Bug 153281] AutoConvert inconsistent choice between TEXT, DATE, NUMBER and FRACTION cell format.

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=153281

--- Comment #3 from ady  ---
(In reply to Eike Rathke from comment #2)
> Note that the input of 1/4 getting converted to U+00BC ¼ happens already on
> editing level, hence the input the cell receives is already text.

Thank you for your reply. I still see this default behavior as non-intuitive
and goes against other methods we have know for decades (e.g. forcing it as
text by means of apostrophe). IOW, 2 inconsistencies, and very subjective
default behavior.

Users can't force each individual input to be treated as date - or as fraction.
But each input can be forced to be treated as text. So choosing to force it to
be a text by default reduces the available alternatives for users. It's a
simple logical flowchart.

When using AutoCorrect to force this input as text, the cell format should be
text, not date.

If Autocorrect is not enabled to force the input as text, then its OK for the
cell format to be a date (and the input to be treated as such too).

The current mix doesn't make sense to me, and certainly it is not intuitive or
natural.

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

[Libreoffice-bugs] [Bug 153290] Object's text box is temporarily invisible after ungrouping

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=153290

Stéphane Guillou (stragu)  changed:

   What|Removed |Added

   Keywords|bibisectRequest |bibisected, bisected
 CC||vmik...@collabora.com

--- Comment #2 from Stéphane Guillou (stragu) 
 ---
... and when I said "now", I meant "when I realise I forgot about it"! :)

Bibisected on linux-64-7.5 repo to first bad commit
6dd229bbde37ebc0cc51e2bda939249f4267ea56 which points to core commit:

commit  914d246e0edcbdfa5969b7f3eea7c67e1a5b7522
author  Miklos Vajna Wed Sep 28 08:54:06 2022 +0200
committer   Miklos Vajna Wed Sep 28 09:46:30
2022 +0200
treed3df578b72b0af615bda06e69588fac49bd1599e
parent  ada3cf7a8392c59932fc339357cda9c3dda5c33f
crashtesting: fix PDF export of fdo83057-2.docx
Change-Id: Ia03f0ec70cf67626660349accc63770fe2afef5d
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/140688

Miklos, can you please have a look?

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

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

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=150915
Bug 150915 depends on bug 122188, which changed state.

Bug 122188 Summary: Disappear table lines of XLS opened with OS dark theme 
(XLSX OK)
https://bugs.documentfoundation.org/show_bug.cgi?id=122188

   What|Removed |Added

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

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

[Libreoffice-bugs] [Bug 109072] [META] XLS (binary) format bug tracker

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=109072
Bug 109072 depends on bug 122188, which changed state.

Bug 122188 Summary: Disappear table lines of XLS opened with OS dark theme 
(XLSX OK)
https://bugs.documentfoundation.org/show_bug.cgi?id=122188

   What|Removed |Added

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

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

[Libreoffice-bugs] [Bug 143344] [META] Linux Dark Mode bugs and enhancements

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=143344
Bug 143344 depends on bug 122188, which changed state.

Bug 122188 Summary: Disappear table lines of XLS opened with OS dark theme 
(XLSX OK)
https://bugs.documentfoundation.org/show_bug.cgi?id=122188

   What|Removed |Added

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

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

[Libreoffice-bugs] [Bug 122188] Disappear table lines of XLS opened with OS dark theme (XLSX OK)

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=122188

Caolán McNamara  changed:

   What|Removed |Added

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

--- Comment #16 from Caolán McNamara  ---
no, I think I just forget about this one

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

[Libreoffice-bugs] [Bug 152770] Insert - Envelope in a new document: warnings in console with debug LO

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=152770

Caolán McNamara  changed:

   What|Removed |Added

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

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

[Libreoffice-bugs] [Bug 110434] [META] Envelope bugs and enhancements

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=110434
Bug 110434 depends on bug 152770, which changed state.

Bug 152770 Summary: Insert - Envelope in a new document: warnings in console 
with debug LO
https://bugs.documentfoundation.org/show_bug.cgi?id=152770

   What|Removed |Added

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

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

[Libreoffice-bugs] [Bug 152770] Insert - Envelope in a new document: warnings in console with debug LO

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=152770

--- Comment #17 from Commit Notification 
 ---
Caolán McNamara committed a patch related to this issue.
It has been pushed to "master":

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

tdf#152770 undo move warning about ppd with no resolution to use of resolution

It will be available in 7.6.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 153296] FILESAVE DOCX VML shapetype is not detected as preset shape by Word

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=153296

Regina Henschel  changed:

   What|Removed |Added

   Assignee|libreoffice-b...@lists.free |rb.hensc...@t-online.de
   |desktop.org |
 Ever confirmed|0   |1
 Status|UNCONFIRMED |ASSIGNED

--- Comment #2 from Regina Henschel  ---
Work has started in https://gerrit.libreoffice.org/c/core/+/146311.

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

[Libreoffice-bugs] [Bug 103202] [META] About dialog bugs and enhancements

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=103202

Sierk Bornemann  changed:

   What|Removed |Added

 Depends on||148071


Referenced Bugs:

https://bugs.documentfoundation.org/show_bug.cgi?id=148071
[Bug 148071] change about info Mac OS X to macOS
-- 
You are receiving this mail because:
You are the assignee for the bug.

[Libreoffice-bugs] [Bug 148071] change about info Mac OS X to macOS

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=148071

Sierk Bornemann  changed:

   What|Removed |Added

 Blocks||103202


Referenced Bugs:

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

[Libreoffice-bugs] [Bug 148012] Deleting sheets multiple sheet slow (6 seconds with 7.4, compared to 1 second with 7.0)

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=148012

Telesto  changed:

   What|Removed |Added

   Keywords|bibisectRequest, perf   |

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

[Libreoffice-bugs] [Bug 148012] Deleting sheets multiple sheet slow (6 seconds with 7.4, compared to 1 second with 7.0)

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=148012

Telesto  changed:

   What|Removed |Added

 Resolution|--- |WORKSFORME
 Status|NEEDINFO|RESOLVED

--- Comment #5 from Telesto  ---
Version: 7.6.0.0.alpha0+ (X86_64) / LibreOffice Community
Build ID: 37e3455a13ab5741104bf41d05a80e60a4612682
CPU threads: 4; OS: Windows 6.3 Build 9600; UI render: Skia/Raster; VCL: win
Locale: nl-NL (nl_NL); UI: en-US
Calc: CL threaded

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

[Libreoffice-bugs] [Bug 153282] Apple 'Finder' displays a 'Strange, Rainbow CD' image for my ODS files.

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=153282

Alex Thurgood  changed:

   What|Removed |Added

 Resolution|--- |WORKSFORME
 Status|NEEDINFO|RESOLVED

--- Comment #7 from Alex Thurgood  ---
Nik has found a way to correct the problem by activating native LO dialogs, so
we can mark this as WFM.

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

[Libreoffice-bugs] [Bug 153205] Selection not cleared when clicking elsewhere after copying text by ctrl-dragging

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=153205

--- Comment #17 from Buovjaga  ---
(In reply to Buovjaga from comment #9)
> Sorry, I did not notice the uncontroversial point about selection staying
> after clicking elsewhere.
> 
> Bibisected with Windows 7.2 repo to
> https://git.libreoffice.org/core/commit/
> a2f6b4e8995c149620db4fcfe7e355af4fbc869e
> tdf#88064 In add mode don't change SetCursor and KillSel functions when
> shell is popped

Just a note in case it is not obvious: the relation here is that Ctrl + left
mouse drag is a shortcut for Add mode selection.

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

[Libreoffice-bugs] [Bug 153153] Incentivize users to use the latest version via the UI

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=153153

--- Comment #4 from Maverick  ---
Wouldn't it be even great if users would be automatically updated/upgraded?

I mean, we already have a dialog for auto-updating 
(that does not work in anyway and is, IMO, giving a very negative image about
the product - it's 2023!)

So why not put some effort in that and get this work finished?

I believe it's a lot of work, but from it we could:

- Get most users on the latest version (that would eliminate old bugs being
reported)
- It would help getting the "business" version even more tested and stable
- It would provide all that a regular user is already expecting from a 2023
product (every piece of software i use auto-updates itself except for LO)
- (Other advantages...)

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

[Libreoffice-bugs] [Bug 131304] [META] MS Word compatibilityMode = 15

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=131304

Mike Kaganski  changed:

   What|Removed |Added

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

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

[Libreoffice-bugs] [Bug 153241] FILEOPEN: VmlDrawingsPart .emf embedded images are not shown correctly; elements moved down on Y axis

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=153241

Buovjaga  changed:

   What|Removed |Added

Version|6.2.0.3 release |6.0.0.3 release
   See Also||https://bugs.documentfounda
   ||tion.org/show_bug.cgi?id=11
   ||1548
   Keywords|bibisectRequest |bibisected, bisected

--- Comment #7 from Buovjaga  ---
I did a bibisect with linux-64-6.0, keeping an eye on the 1 2 3 dropping below
the white rectangle with black borders. IMPORTANT: I checked by opening the
.ods with 7.4. The file open result is different with older versions.

Result:
https://git.libreoffice.org/core/commit/286c27e805c4501451857abff19c23b3719146a3
tdf#111548: Better fix for PPTX / XLSX import of ActiveX controls

Tamás is no longer active, so I won't bother him with this.

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

[Libreoffice-bugs] [Bug 125451] The updater has never worked for me and manual updating is extremely cumbersome

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=125451

--- Comment #22 from Maverick  ---
Ain't this a duplicate of bug 74934 ?

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

[Libreoffice-bugs] [Bug 148952] Filesave DOCX: Alt Text field of image is lost on open in LO and in MSO

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=148952

Michael Stahl (allotropia)  changed:

   What|Removed |Added

 CC||michael.st...@allotropia.de
   ||, mikekagan...@hotmail.com,
   ||vasily.melenc...@cib.de,
   ||vmik...@collabora.com
   Assignee|libreoffice-b...@lists.free |michael.st...@allotropia.de
   |desktop.org |

--- Comment #3 from Michael Stahl (allotropia)  ---
we find this code in DocxAttributeOutput::FlyFrameGraphic()

if( GetExport().GetFilter().getVersion( ) != oox::core::ECMA_DIALECT )
docPrattrList->add( XML_title, OUStringToOString( pGrfNode ?
pGrfNode->GetTitle() : pOLEFrameFormat->GetObjTitle(), RTL_TEXTENCODING_UTF8
));

it turns out that in ISO 29500:2008, in ECMA-376 2nd edition, 3rd edition,
presumably up to 5th edition (yes that was released in 2021), the wp:docPr may
have a "title" attribute.

but in ECMA-376 1st edition, the wp:docPr does not have a "title" attribute.

what exactly does our "OoxmlVersion::ECMA_DIALECT" correspond to, if there are
5 editions to choose from?

saving the attached with "Office Open XML Text (Transitional)" results in:


saving the attached with "Word 2007-365" results in:


... and i've always thought the "2007-365" supports more features/extensions?

is it supposed to mean "ECMA-376 1st edition" specifically? but why is it named
"365" then?

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

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

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=137080

--- Comment #3 from nicholasj...@mailfence.com ---
Is the following further bug report closely related?
 (I apologise for
the philistine formatting - I have trouble discovering what formatting BugZilla
allows.)

Is the following germane? In some (all?) instances, _small caps in a PowerPoint
file render as all-caps in Impress_. That can wreak havoc upon a presentation.
Thus, it is a serious problem. Indeed it is almost a deal-breaker for my use of
Impress. (It is a shame that though Impress has taken strides in Microsoft
Office compatibility, this breakage remains. It is almost enough to send me
back to Windows.)

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

[Libreoffice-bugs] [Bug 145766] Print Dialog Box too long or 'print' button too low on window

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=145766

--- Comment #9 from mvarne...@yahoo.com ---
Response to Stuart Foote: On macOS, it doesn't seem possible to get scrollbars
in the Print dialog. The window cannot be manually resized. It automatically
resizes to fit the contents of whichever options pane is shown. On my system,
the default "LibreOffice" pane is the only one that causes the window to run
off the screen.
Note to Bob: You should be able to access the buttons at the bottom of the
dialog box by choosing a different options pane from the drop-down menu that
reads "LibreOffice" by default. You can also close the dialog by pressing Esc,
or commit to printing by pressing Return/Enter.
This is still a significant problem and should be fixed. I vote to have LO
provide scrollbars as the Windows version apparently did or does.

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

[Libreoffice-bugs] [Bug 150451] Some text boxes in dialogs do not have borders in dark mode (kf5)

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=150451

--- Comment #21 from Rafael Lima  ---
(In reply to Michael Weghorn from comment #20)
> @Rafael: Do you have any scaling applied as well?

I have no scaling on my end. I'm using a 1080p display with 100% scaling. When
I use QT_SCALE_FACTOR=2.0 I also get no borders.

But in my case I get no borders regardless of QT_SCALE_FACTOR.

BTW the best dialog to check these borders is Tools - Options - User Data,
because it has a lot of text boxes and it makes it easier to see the results.

> Would you be interested in looking further into that yourself?

Yes... I'll take a look. If I can't fix it, I'll share my findings here.

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

[Libreoffice-bugs] [Bug 153241] FILEOPEN: VmlDrawingsPart .emf embedded images are not shown correctly; elements moved down on Y axis

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=153241

--- Comment #6 from Stéphane Guillou (stragu) 
 ---
Created attachment 185036
  --> https://bugs.documentfoundation.org/attachment.cgi?id=185036&action=edit
test results with MS Excel and LO 7.6 alpha0+

Attached PDF shows three screenshots:
- Original XLSX displayed in MS Excel
- Original XLSX displayed in LO recent master build
- Saved as ODS and reloaded in LO recent master build

Versions:

Microsoft® Word for Microsoft 365 MSO (Version 2212 Build 16.0.15928.20196)
64-bit 

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

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

[Libreoffice-bugs] [Bug 153296] FILESAVE DOCX VML shapetype is not detected as preset shape by Word

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=153296

--- Comment #1 from Regina Henschel  ---
Created attachment 185035
  --> https://bugs.documentfoundation.org/attachment.cgi?id=185035&action=edit
ArchUpCurve

Open attached file in a current LO daily. Because it has a bitmap fill it will
be written as VML shape, when the file is saved to docx.

Save the file to docx and open the saved file in Word. Error: There is no
WordArt but a rectangle.

This is the same problem as (1). But here it is so, that no WordArt shape is
written at all.

Root cause is the same. The file "vml-shape-types" (located in the installation
directory of LO in share/filter folder) which is used for export of shapes to
VML, is not suitable for Fontwork shapes. In case of 'ArchUpCurve' the markup
is simply missing in that file. It is " 144 - textArchUp " in that file.

The file is likely neither suitable for other shapes with handles, but I have
not tested that. Other shapes than Fontwork shapes are saved as DML shape and
use the VML only as Fallback. And because current MS Word is able to read DML
shapes, it ignores the Fallback. Errors in the Fallback are only detected, when
you use a version before MS Word 2010.

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

[Libreoffice-bugs] [Bug 153010] Inconsistency and confusing strings when numeric field's numbering format is not available for a language

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=153010

Dieter  changed:

   What|Removed |Added

 OS|Linux (All) |All
 Whiteboard| QA:needsComment|
 Status|UNCONFIRMED |NEW
 CC||dgp-m...@gmx.de
 Ever confirmed|0   |1

--- Comment #1 from Dieter  ---
I confirm it with

Version: 7.5.0.2 (X86_64) / LibreOffice Community
Build ID: c0dd1bc3f1a385d110b88e26ece634da94921f58
CPU threads: 4; OS: Windows 10.0 Build 19044; UI render: Skia/Raster; VCL: win
Locale: de-DE (de_DE); UI: en-GB
Calc: CL threaded

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

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

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=150915
Bug 150915 depends on bug 153273, which changed state.

Bug 153273 Summary: Scroll bar not in dark mode when system dark mode enabled
https://bugs.documentfoundation.org/show_bug.cgi?id=153273

   What|Removed |Added

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

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

[Libreoffice-bugs] [Bug 143328] FILESAVE: All 3 form controls disappear on reopen in LO, incorrect in MSO

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=143328

--- Comment #10 from Gabor Kelemen (allotropia)  ---
Created attachment 185034
  --> https://bugs.documentfoundation.org/attachment.cgi?id=185034&action=edit
The original file and its Calc-saved version reloaded

Now some small differences also became visible:
- Button Font is changed: Courier New -> (Default); Checkbox: Segoe UI 8pt ->
(Default) 10 pt
- Checkbox background is changed: (Default) -> White - but for the checkbox,
it's retained correctly as #ECE9D8
- Push button in the original has the Printable attribute as No -> Yes (see in
Print Preview

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

[Libreoffice-bugs] [Bug 136406] [META] OOXML VML shape related issues

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=136406

Regina Henschel  changed:

   What|Removed |Added

 Depends on||153296


Referenced Bugs:

https://bugs.documentfoundation.org/show_bug.cgi?id=153296
[Bug 153296] FILESAVE DOCX VML shapetype is not detected as preset shape by
Word
-- 
You are receiving this mail because:
You are the assignee for the bug.

[Libreoffice-bugs] [Bug 128568] FILESAVE: DOCX: Fontwork broken with Word 2007-365 format

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=128568

Regina Henschel  changed:

   What|Removed |Added

 Depends on||153296


Referenced Bugs:

https://bugs.documentfoundation.org/show_bug.cgi?id=153296
[Bug 153296] FILESAVE DOCX VML shapetype is not detected as preset shape by
Word
-- 
You are receiving this mail because:
You are the assignee for the bug.

[Libreoffice-bugs] [Bug 153296] New: FILESAVE DOCX VML shapetype is not detected as preset shape by Word

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=153296

Bug ID: 153296
   Summary: FILESAVE DOCX VML shapetype is not detected as preset
shape by Word
   Product: LibreOffice
   Version: 7.6.0.0 alpha0+ Master
  Hardware: x86 (IA32)
OS: All
Status: UNCONFIRMED
  Severity: normal
  Priority: medium
 Component: Writer
  Assignee: libreoffice-bugs@lists.freedesktop.org
  Reporter: rb.hensc...@t-online.de
Blocks: 107634, 128568, 136406

Created attachment 185033
  --> https://bugs.documentfoundation.org/attachment.cgi?id=185033&action=edit
SlantUp Fontwork shape

Open attached document and save it to docx format.
Open the docx document in Microsoft Word and save it without changes.
Open the saved document in LibreOffice.

Error: LibreOffice does not show the shape. When you look in the Navigator you
see, that the shape exists.

The whole process has two main errors:
(1) LibreOffice does not write the markup in a way, that Word detects, that it
is one of the preset WordArt shapetypes.
(2) When Word saves the file it writes the shape as having a custom geometry.
But LibreOffice is not able to import custom geometry.

This bug report will track problem (1).

The shapetype "SlantUp" was chosen, because it will be exported as VML shape
and not as DML shape even in released LibreOffice.


Referenced Bugs:

https://bugs.documentfoundation.org/show_bug.cgi?id=107634
[Bug 107634] [META] Fontwork / WordArt bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=128568
[Bug 128568] FILESAVE: DOCX: Fontwork broken with Word 2007-365 format
https://bugs.documentfoundation.org/show_bug.cgi?id=136406
[Bug 136406] [META] OOXML VML shape related issues
-- 
You are receiving this mail because:
You are the assignee for the bug.

[Libreoffice-bugs] [Bug 107634] [META] Fontwork / WordArt bugs and enhancements

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=107634

Regina Henschel  changed:

   What|Removed |Added

 Depends on||153296


Referenced Bugs:

https://bugs.documentfoundation.org/show_bug.cgi?id=153296
[Bug 153296] FILESAVE DOCX VML shapetype is not detected as preset shape by
Word
-- 
You are receiving this mail because:
You are the assignee for the bug.

[Libreoffice-bugs] [Bug 143328] FILESAVE: All 3 form controls disappear on reopen in LO, incorrect in MSO

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=143328

Gabor Kelemen (allotropia)  changed:

   What|Removed |Added

 CC||jl...@mail.com,
   ||kelem...@ubuntu.com

--- Comment #9 from Gabor Kelemen (allotropia)  ---
This got better since:

https://git.libreoffice.org/core/+/d50eca2a30bdabdc1735c590d6ec1913c6dd22fd

author  Justin Luth  Thu Jan 12 11:18:55 2023 -0500
committer   Justin Luth Sun Jan 15 02:09:06 2023 +
treef8d8a738c60fa0c69954a9fbf684a2e7640d8740
parent  37e3455a13ab5741104bf41d05a80e60a4612682 [diff]

tdf#117266 sc oox: export vml button with a correct name

Now saving and reloading attachment 173557 the button and checkbox are now
visible in Calc, the scrollbar is still not.

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

[Libreoffice-bugs] [Bug 122188] Disappear table lines of XLS opened with OS dark theme (XLSX OK)

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=122188

Stéphane Guillou (stragu)  changed:

   What|Removed |Added

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

--- Comment #15 from Stéphane Guillou (stragu) 
 ---
Reproduced on Ubuntu 20.04 with GNOME 3.36.8 (dark theme) with:

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

But verified as fixed with:

Version: 7.4.5.1 / LibreOffice Community
Build ID: 9c0871452b3918c1019dde9bfac75448afc4b57f
CPU threads: 8; OS: Linux 5.15; UI render: default; VCL: gtk3
Locale: en-AU (en_AU.UTF-8); UI: en-US
Calc: threaded

Caolán, are you OK to mark this one as resolved or was there something missing?

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

[Libreoffice-bugs] [Bug 81607] UI: Unintended Collapse of Different Items when Inserting a New Item or Changing a Comment

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=81607

--- Comment #13 from Universal Pest  ---
Pest control refers to the regulation or management of a species defined as a
pest, usually because it is perceived to be detrimental to a person's health,
the ecology or the economy. Pests can be insects, rodents, birds, or other
species that cause damage to crops, structures, or human health. Pest control
methods range from cultural practices, chemical treatments, biological
controls, and mechanical devices. The goal of pest control is to reduce the
pest population to a level that does not cause harm and to prevent their
return.

https://universalpest.com/termite-inspections/

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

[Libreoffice-bugs] [Bug 150451] Some text boxes in dialogs do not have borders in dark mode (kf5)

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=150451

--- Comment #20 from Michael Weghorn  ---
I noticed that the issue is reproducible for me as well when I apply scaling,
e.g. starting LO Calc with env var QT_SCALE_FACTOR=2.0 set and then open the
conditional formatting dialog. No issue with the 100 % scaling I use otherwise.

@Rafael: Do you have any scaling applied as well?

`QtGraphics_Controls::getNativeControlRegion` and
`QtGraphics_Controls::drawNativeControl` *might* be good places to start
looking deeper into that, in particular looking into the upscale/downscale
calls in there. (Maybe some rounding issue,...?)

Would you be interested in looking further into that yourself?

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

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

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=153293

Stéphane Guillou (stragu)  changed:

   What|Removed |Added

 Depends on||153088


Referenced Bugs:

https://bugs.documentfoundation.org/show_bug.cgi?id=153088
[Bug 153088] Dark Mode: Calc: Format Cells > Font + Font Effects sample text
should be white
-- 
You are receiving this mail because:
You are the assignee for the bug.

[Libreoffice-bugs] [Bug 118017] [META] macOS Dark Mode bugs and enhancements

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=118017

Stéphane Guillou (stragu)  changed:

   What|Removed |Added

 Depends on|153088  |


Referenced Bugs:

https://bugs.documentfoundation.org/show_bug.cgi?id=153088
[Bug 153088] Dark Mode: Calc: Format Cells > Font + Font Effects sample text
should be white
-- 
You are receiving this mail because:
You are the assignee for the bug.

[Libreoffice-bugs] [Bug 120727] Excessive CPU usage under normal use (typing) see comment 33

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=120727

Stéphane Guillou (stragu)  changed:

   What|Removed |Added

   Keywords||perf

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

[Libreoffice-bugs] [Bug 120727] Excessive CPU usage under normal use (typing) see comment 33

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=120727

Stéphane Guillou (stragu)  changed:

   What|Removed |Added

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

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

[Libreoffice-bugs] [Bug 114392] MacOS: Increased CPU usage while typing

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=114392

Stéphane Guillou (stragu)  changed:

   What|Removed |Added

   See Also||https://bugs.documentfounda
   ||tion.org/show_bug.cgi?id=12
   ||0727
   Keywords||perf

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

[Libreoffice-bugs] [Bug 149506] Slow start-up and opening of files since 7.3 release

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=149506

Stéphane Guillou (stragu)  changed:

   What|Removed |Added

   Keywords||perf
 CC||stephane.guillou@libreoffic
   ||e.org

--- Comment #13 from Stéphane Guillou (stragu) 
 ---
If bunkem or Joe are able to, and the difference in performance is very
obvious, it would be great if you could bibisect the issue to determine when
exactly the degradation started.
Instructions are here: https://wiki.documentfoundation.org/QA/Bibisect/macOS
The repository you need is bibisect-mac64-7.3.
If you need assistance with the process, please contact the QA team:
https://wiki.documentfoundation.org/QA

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