[Libreoffice-bugs] [Bug 155942] New: Calc feature request

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

Bug ID: 155942
   Summary: Calc feature request
   Product: LibreOffice
   Version: 7.4.7.2 release
  Hardware: All
OS: Windows (All)
Status: UNCONFIRMED
  Severity: enhancement
  Priority: medium
 Component: LibreOffice
  Assignee: libreoffice-bugs@lists.freedesktop.org
  Reporter: varala...@gmail.com

Description:
Calc does not support double-click dragging to select text a whole word at a
time. This is an important feature and I think every single Windows and Mac app
in the last 30 years, including Windows and Mac OSes, have supported it.

Writer supports it beautifully, so you guys already know it's important.
But

Impress does not support it (I don't care, as I don't use presentation ware at
all);
Draw also does not;
Math doesn't, near as I can tell (never opened it until now);
Base is UNKNOWN; it needs Java to create a new database, and I'm not installing
that crap. The Base app is literally unusable for anything beyond basic tables
& queries even on a local machine. I spent years making my living building
.mdbs in MS Access, so I'm not exactly new to relational db concepts.

PLEASE add double-click drag to select text. I still find it hard to believe
that you don't.

Thanks.

Actual Results:
Requesting enhancement. Why is this field mandatory?

Expected Results:
Requesting enhancement. Why is this field mandatory?


Reproducible: Always


User Profile Reset: No

Additional Info:
Requesting enhancement. Why is this field mandatory?

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

[Libreoffice-commits] core.git: Branch 'distro/collabora/co-22.05' - desktop/source

2023-06-19 Thread Marco Cecchetti (via logerrit)
 desktop/source/lib/init.cxx |2 ++
 1 file changed, 2 insertions(+)

New commits:
commit 46ccb563a8aeb4ce16c7fd852bfae3dad825e7df
Author: Marco Cecchetti 
AuthorDate: Tue Jun 13 19:30:05 2023 +0200
Commit: Aron Budea 
CommitDate: Tue Jun 20 07:29:53 2023 +0200

lok: on switching from tabbed to compact ui 2 buttons were disabled

Number Format Increase Decimals, Number Format Decrease Decimals were
not enabled on switching ui.

Change-Id: Ia81a43ef40168dcbf071d071231b795f9bf8659e
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/153050
Reviewed-by: Gökay ŞATIR 
Tested-by: Jenkins CollaboraOffice 
(cherry picked from commit cd4ad81ca334a3d2bc90bab81502ae5350bac84d)
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/153210
Reviewed-by: Aron Budea 

diff --git a/desktop/source/lib/init.cxx b/desktop/source/lib/init.cxx
index b437735ed71b..28ddbd384896 100644
--- a/desktop/source/lib/init.cxx
+++ b/desktop/source/lib/init.cxx
@@ -3446,6 +3446,8 @@ static void doc_iniUnoCommands ()
 OUString(".uno:NumberFormatCurrency"),
 OUString(".uno:NumberFormatPercent"),
 OUString(".uno:NumberFormatDecimal"),
+OUString(".uno:NumberFormatIncDecimals"),
+OUString(".uno:NumberFormatDecDecimals"),
 OUString(".uno:NumberFormatDate"),
 OUString(".uno:EditHeaderAndFooter"),
 OUString(".uno:FrameLineColor"),


[Libreoffice-bugs] [Bug 155941] New: Calc menus periodically turn dark-mode w black text - barely readable

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

Bug ID: 155941
   Summary: Calc menus periodically turn dark-mode w black text -
barely readable
   Product: LibreOffice
   Version: 7.4.7.2 release
  Hardware: All
OS: Windows (All)
Status: UNCONFIRMED
  Severity: normal
  Priority: medium
 Component: Calc
  Assignee: libreoffice-bugs@lists.freedesktop.org
  Reporter: varala...@gmail.com

Description:
IGNORE ANY CONFIG INFO I GAVE YOUR POPUPS. This is my config:

Version: 7.4.7.2 (x64) / LibreOffice Community
Build ID: 723314e595e8007d3cf785c16538505a1c878ca5
CPU threads: 8; OS: Windows 10.0 Build 19045; UI render: default; VCL: win
Locale: en-US (en_US); UI: en-US
Calc: CL

Edition Windows 10 Home
Version 22H2
Installed on‎10/‎24/‎2022
OS build19045.3086
Experience  Windows Feature Experience Pack 1000.19041.1000.0

Device name Varaland
Processor   Intel(R) Core(TM) i7-7700HQ CPU @ 2.80GHz   2.80 GHz
Installed RAM   16.0 GB (15.9 GB usable)
Device ID   1EE5CD16-EC0C-4932-BC37-B0DB6B3028F4
Product ID  00325-96262-70554-AAOEM
System type 64-bit operating system, x64-based processor
Pen and touch   No pen or touch input is available for this display

No idea why, but periodically my Calc menus go into something like dark mode
but the text stays black, and they are extremely hard to read. This happens
regardless of whether I have Skia options ON in Settings / Libre Office / View.

All other View settings on this screen are on default.

I have to restart the app to fix this. Then in maybe a half hour - and always
without being told to change display modes - it happens again.

Thanks for looking into it.

Actual Results:
Haven't tried to reproduce it.

Expected Results:
Haven't tried to reproduce it.


Reproducible: Didn't try


User Profile Reset: No

Additional Info:
Haven't tried to reproduce it.

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

[Libreoffice-bugs] [Bug 155940] New: AutoFilter would not go away even after restart

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

Bug ID: 155940
   Summary: AutoFilter would not go away even after restart
   Product: LibreOffice
   Version: unspecified
  Hardware: All
OS: Windows (All)
Status: UNCONFIRMED
  Severity: normal
  Priority: medium
 Component: Calc
  Assignee: libreoffice-bugs@lists.freedesktop.org
  Reporter: varala...@gmail.com

Description:
IGNORE ANY CONFIG INFO I GAVE YOUR POPUPS. This is my config:

Version: 7.4.7.2 (x64) / LibreOffice Community
Build ID: 723314e595e8007d3cf785c16538505a1c878ca5
CPU threads: 8; OS: Windows 10.0 Build 19045; UI render: default; VCL: win
Locale: en-US (en_US); UI: en-US
Calc: CL

Edition Windows 10 Home
Version 22H2
Installed on‎10/‎24/‎2022
OS build19045.3086
Experience  Windows Feature Experience Pack 1000.19041.1000.0

Device name Varaland
Processor   Intel(R) Core(TM) i7-7700HQ CPU @ 2.80GHz   2.80 GHz
Installed RAM   16.0 GB (15.9 GB usable)
Device ID   1EE5CD16-EC0C-4932-BC37-B0DB6B3028F4
Product ID  00325-96262-70554-AAOEM
System type 64-bit operating system, x64-based processor
Pen and touch   No pen or touch input is available for this display

Have an .ods doc with over 18,000 records, and normally autofilter works well.
This last time I turned it on for a single column as usual, but then the app
wouldn't stop filtering even though it showed no filter was on. Wouldn't stop
filtering even after a restart of app. I was only being shown 284 records out
of 18,523. That's scary.

There were no warnings, and I didn't do anything while using the filter that I
hadn't done before. Even if I'd absently clicked another column implying that I
wanted to additionally filter the results of the last filter (doubtful but
possible), these filters still should have indicated they were ON and I should
have been able to turn them OFF.

I'm sorry that I don't know the steps to reproduce it.

Eventually I solved it by turning autofilter ON in my ID# field, set for All
records. That showed them all to me and everything seems good now.



Actual Results:
None. Couldn't reproduce.

Expected Results:
Couldn't reproduce.


Reproducible: Couldn't Reproduce


User Profile Reset: No

Additional Info:
Couldn't reproduce.

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

Week 3 Report : GSOC 2023 - Convert Writer's Java UNO API Tests to C++

2023-06-19 Thread Dipam Turkar
Hey everyone,
I want to submit the project report for Week #3.

The tests converted this week are as mentioned below
1. SwXAutoContainer.java
2. SwXAutoTextEntry.java
3. SwXAutoTextGroup.java

The converted tests will be committed soon.

Thanks and regards
Dipam Turkar


[Libreoffice-bugs] [Bug 155939] New: LibreOffice-7.5.4.2 Writer hangs when changing language of text

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

Bug ID: 155939
   Summary: LibreOffice-7.5.4.2 Writer hangs when changing
language of text
   Product: LibreOffice
   Version: 7.5.4.2 release
  Hardware: x86-64 (AMD64)
OS: Linux (All)
Status: UNCONFIRMED
  Severity: normal
  Priority: medium
 Component: Writer
  Assignee: libreoffice-bugs@lists.freedesktop.org
  Reporter: sun...@hpcl.in

Description:
Libreoffice Writer, 7.5.4.2 (x86_64), Linux Mint.
Tools -> Language -> For All text -> English(UK)
LO hangs and CPU utlised by soffice process keeps going up.
Can work only after restarting libreoffice.
Crash recovery fails for open files.

Steps to Reproduce:
1.Open a text document (.docx/.odt)
2.Tools -> Language -> For All text -> English(UK) (or any language)
3.

Actual Results:
LibreOffice hangs

Expected Results:
Dictionary selected should change to the chose one.


Reproducible: Always


User Profile Reset: Yes

Additional Info:
Resetting the profile did not help.

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

[Libreoffice-bugs] [Bug 142437] Applying autocorrect wordlist changes sub-strings for Marathi

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

--- Comment #11 from Shantanu  ---
>> Have you also asked the developer of the extension?
No. Because I am the developer! :)

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

[Libreoffice-bugs] [Bug 142437] Applying autocorrect wordlist changes sub-strings for Marathi

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

--- Comment #10 from Shantanu  ---
Expected: The second half on the third line should not be changed to 'and'. It
should remain as 'adn' because the substring 'adn' is part of a word and not a
new word, unlike what is shown on the first line.

As a result of this bug, I am unable to use autocorrect for Marathi as it is
changing certain parts of words in an unpredictable manner. This issue may also
be present for other languages, but I am unable to verify. Apply - Autocorrect
is an awesome feature that is too good to miss. Microsoft word does not support
this.

However, English does not have any problems.

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

[Libreoffice-bugs] [Bug 155692] Resizing RTL table cells is almost impossible (very tricky)

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

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 155694] Changing the direction of an RTL table causes the black borders to become garbled

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

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 155917] Writer crashes when inserting ODT file containing PDF into table in another ODT doc

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

QA Administrators  changed:

   What|Removed |Added

 Ever confirmed|1   |0
 Status|NEEDINFO|UNCONFIRMED

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

[Libreoffice-bugs] [Bug 155688] FILEOPEN DOCX loading causes RTL table to lose part of its border

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

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 155682] DOCX with big pictures causes endless loop

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

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 155691] DOC Resizing the RTL table causes it to lose parts of its border

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

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 155917] Writer crashes when inserting ODT file containing PDF into table in another ODT doc

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

--- 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 155906] Default icons are unreadable in dark mode (Xfce)

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

QA Administrators  changed:

   What|Removed |Added

 Ever confirmed|1   |0
 Status|NEEDINFO|UNCONFIRMED

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

[Libreoffice-bugs] [Bug 155905] Has been crashing on and off for 2 weeks. Randomized, no trigger as far as I can tell. It freezes up, then closes all libre office windows compeltely

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

QA Administrators  changed:

   What|Removed |Added

 Ever confirmed|1   |0
 Status|NEEDINFO|UNCONFIRMED

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

[Libreoffice-bugs] [Bug 155860] Languagetool for german does not work in Libreoffice 7.5.4 anymore, in Libreoffice 7.5.3 it does work. I use Java "Microsoft OpenJDK".

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

QA Administrators  changed:

   What|Removed |Added

 Ever confirmed|1   |0
 Status|NEEDINFO|UNCONFIRMED

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

[Libreoffice-bugs] [Bug 155906] Default icons are unreadable in dark mode (Xfce)

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

--- 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 155905] Has been crashing on and off for 2 weeks. Randomized, no trigger as far as I can tell. It freezes up, then closes all libre office windows compeltely

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

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

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

[Libreoffice-ux-advise] [Bug 155834] Unnumbered entries do not move together with their main entry, when list's "move item up / down" commands are used

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

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

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

[Libreoffice-bugs] [Bug 155860] Languagetool for german does not work in Libreoffice 7.5.4 anymore, in Libreoffice 7.5.3 it does work. I use Java "Microsoft OpenJDK".

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

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

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

[Libreoffice-bugs] [Bug 155834] Unnumbered entries do not move together with their main entry, when list's "move item up / down" commands are used

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

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

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

[Libreoffice-bugs] [Bug 152630] The Window Extends Beyond the Display

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

--- Comment #2 from QA Administrators  ---
Dear Stéphane Aulery,

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 152629] libreoffice: [GUI] Wrong file name in file windows

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

--- Comment #4 from QA Administrators  ---
Dear Stéphane Aulery,

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 152419] Grouped Objects from DOCX file corrupted when saving, including ODT

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

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

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 148028] export creates huge pdf size, by about factor 100: 10 MB instead of 100 kB.

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

--- Comment #6 from QA Administrators  ---
Dear Martin Trautmann,

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 147865] Mise à jour date et nombre de page dans un modèle

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

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

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 135462] LibreOffice 7.0.0.3 does not recognise JRE installation location at startup other than those in /Library/Java/JavaVirtualMachines/

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

--- Comment #42 from QA Administrators  ---
Dear war,

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 146759] LibreOffice crashes repeatedly using macOS 12.1 Monterey with AutoSave on, or upon default background saving

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

--- Comment #29 from QA Administrators  ---
Dear PeeWee,

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 126933] LO Writer shows some Buttons almost Unreadable when using High Contrast Theme

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

--- Comment #16 from QA Administrators  ---
Dear Adalbert Hanßen,

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 35923] Calc - Standard Filter produces wrong display (Selection range is automatically expanded)

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

--- Comment #25 from QA Administrators  ---
Dear d00m3d.olw,

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 51644] FORMATTING: text animation suddenly not possible

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

--- Comment #13 from QA Administrators  ---
Dear bugquestcontri,

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 126006] Calc with Tabbed UI crashes on Autofilter icon after File>>Reload if you had autofilter on in the old document

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

--- Comment #16 from QA Administrators  ---
Dear Doug B,

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 142928] FILEOPEN XLSX Standard filters date condition appears converted to plain number

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

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

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

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

If you have time, please do the following:

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

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

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

Please DO NOT

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


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

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


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

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

Warm Regards,
QA Team

MassPing-UntouchedBug

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

[Libreoffice-bugs] [Bug 124093] EDITING Selecting filtered cells with hidden rows in between causes a bug in filter reset.

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

--- Comment #5 from QA Administrators  ---
Dear Julian Ragan,

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 117744] Insane amount of stuff going on while user doing nothing in the Character dialog (both Linux and macOS at least)

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

--- Comment #8 from QA Administrators  ---
Dear Tor Lillqvist,

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 117328] RESET FILTER will not restore all lines of area containing empty cells

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

--- Comment #8 from QA Administrators  ---
Dear Rainer Bielefeld Retired,

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

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

If you have time, please do the following:

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

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

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

Please DO NOT

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


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

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


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

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

Warm Regards,
QA Team

MassPing-UntouchedBug

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

[Libreoffice-bugs] [Bug 111003] Unexpected file reads while closing LibO (for example reading description.xml of all the dictionaries)

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

--- Comment #8 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 155938] При скролле таблицы остается часть изображения на экране

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

--- Comment #1 from Алена  ---
Created attachment 188005
  --> https://bugs.documentfoundation.org/attachment.cgi?id=188005=edit
скриншот ошибки

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

[Libreoffice-bugs] [Bug 155938] New: При скролле таблицы остается часть изображения на экране

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

Bug ID: 155938
   Summary: При скролле таблицы остается часть изображения на
экране
   Product: LibreOffice
   Version: 3.3.0 release
  Hardware: All
OS: Linux (All)
Status: UNCONFIRMED
  Severity: normal
  Priority: medium
 Component: LibreOffice
  Assignee: libreoffice-bugs@lists.freedesktop.org
  Reporter: ku...@nso.ru

Description:
LibreOffice Calc. При скролле таблицы остается часть изображения на экране 

Steps to Reproduce:
1. печатаешь LibreOffice Calc
2. скролом вниз или вверх пролистываешь
3. часть текста изображением остается в программе, либо на самом тексте, либо
ниже него в виде изображения

Actual Results:
прокручивание скролом вниз или вверх

Expected Results:
при скроле текст в виде изображения не остается в документе


Reproducible: Always


User Profile Reset: No

Additional Info:
Version: 7.3.7.2 / LibreOffice Community
Build ID: 30(Build:2)
CPU threads: 12; OS: Linux 5.10; UI render: default; VCL: x11
Locale: ru-RU (ru_RU.UTF-8); UI: ru-RU
Calc: threaded

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

[Libreoffice-bugs] [Bug 155905] Has been crashing on and off for 2 weeks. Randomized, no trigger as far as I can tell. It freezes up, then closes all libre office windows compeltely

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

--- Comment #4 from Iza  ---
I checked all drivers on my computer and software, nothing came up as needing
updated. 
I have turned on the setting, unfortunately I have been away from my computer
all day, so I have not had a chance to check and see if the problem persists. 
I will keep you updated. Thank you. 
-Iza

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

[Libreoffice-bugs] [Bug 155937] New: UITest: frames[0] throws "index out of ranges" in close_doc() on riscv64

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

Bug ID: 155937
   Summary: UITest: frames[0] throws "index out of ranges" in
close_doc() on riscv64
   Product: LibreOffice
   Version: 7.6.0.0 beta1+
  Hardware: Other
OS: Linux (All)
Status: UNCONFIRMED
  Severity: normal
  Priority: medium
 Component: UI
  Assignee: libreoffice-bugs@lists.freedesktop.org
  Reporter: sakura...@outlook.com

Description:
I am trying to fix a uitest bug on riscv64. All the UI test failed for throwing
"IndexError: index out of range" when closing doc. Here is an example:

https://gist.github.com/Sakura286/e216f57c1a81c6dc813ac52f76479293

On x86, "bool(frames)" should be "False" and "frames[0].active" should not be
executed in uitest/uitest/test.py::close_doc(). But on riscv64, "bool(frames)"
turn out to be "True".

I looked into the code, and find that "frames.__len__()" on x86 changed from 1
to 0, but on riscv64 it changed from 270582939649 to 270582939648.

270582939648 is 0011          in binary
form (32 bit zero suffix).

Maybe this is the opening to solve the problem. But I cannot find out where the
__len__() function of the pyuno object is defined and cannot track how this
weired number value comes from. I would be appreciated if someone provide some
tips.

Steps to Reproduce:
1. Run any UI test on riscv64
2. UI test failed for "IndexError: index out of range"

Actual Results:
UItest failed for error

Expected Results:
The doc closed without exception


Reproducible: Always


User Profile Reset: No

Additional Info:
Described above.

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

Re: [Libreoffice-qa] How to link a .so library

2023-06-19 Thread Jingze Xu
Thank you very much!



At 2023-06-19 21:02:05, "Stéphane Guillou"  
wrote:

Hi Jingze,
This is the Quality Assurance mailing list. For questions and answers, please 
use https://ask.libreoffice.org/
However, given that your question is about programming, you might get more 
answers on the dev mailing list: 
https://lists.freedesktop.org/mailman/listinfo/libreoffice



Thank you!


On 19/06/2023 11:40, Jingze Xu wrote:

Dear all, 
Hi, I'm new to libreoffice and its forum. I have a question but I am not sure 
where to ask. If this is the right place, here is the question :)


-
Question:
I have successfully added a new dialog in Impress according to the steps in 
this tutorial - Development/Create new dialog in Impress - The Document 
Foundation Wiki. Now I wish to call functions in an external library in the 
dialog source file.
I have an external library libxxx containing some C++ header files and a .so 
file. I put the header files in include/ folder and .so file outside 
libreoffice directory. I include the header files of this library in dialog 
source files located in sd/source/ui/dlg. I rerun the autogen.sh with extra 
arguments, trying to let the build system know I have a .so library to link. 


./autogen.sh LDFLAGS=-L/path_to_libxxx LIBS=-lxxx


Then I rebuild the sd module using make sd, however, it seems the functions in 
.so library is not properly linked. 


"/usr/bin/ld: 
/home/jingze_xu/office/libreoffice-7.6.0.0.beta1/workdir/CxxObject/sd/source/ui/dlg/HelloDialog.o:
 in function `sd::SdHelloDialog::OKHdl(weld::Button&)':
HelloDialog.cxx:(.text+0x36c): undefined reference to 
`Add_FileHeader(std::__cxx11::basic_string, 
std::allocator >, std::__cxx11::basic_string, std::allocator >, unsigned short)'
collect2: error: ld returned 1 exit status
make[1]: *** 
[/home/jingze_xu/office/libreoffice-7.6.0.0.beta1/sd/Library_sdui.mk:10: 
/home/jingze_xu/office/libreoffice-7.6.0.0.beta1/instdir/program/libsduilo.so] 
Error 1
make: *** [Makefile:121: sd] Error 2"


Are there some clues about linking so library in libreoffice codebase?
Thanks!
-


If this is not the right place to ask questions, I'm sorry about this and 
please tell me where to ask questions. Thanks!


Best wishes,
Jingze Xu




-- 
Stéphane Guillou
Quality Assurance Analyst | The Document Foundation

Email: stephane.guil...@libreoffice.org
Mobile (France): +33 7 79 67 18 72
Matrix: @stragu:matrix.org
Fediverse: @str...@mastodon.indie.host
Web: https://stragu.gitlab.io/

[Libreoffice-bugs] [Bug 155936] New: feedback, venting, it's a mosquito!

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

Bug ID: 155936
   Summary: feedback, venting, it's a mosquito!
   Product: LibreOffice
   Version: 7.5.1.2 release
  Hardware: All
OS: Windows (All)
Status: UNCONFIRMED
  Severity: normal
  Priority: medium
 Component: Writer
  Assignee: libreoffice-bugs@lists.freedesktop.org
  Reporter: mois...@hushmail.com

Description:
I'm updating my resume and loaded some templates. Now I can't delete the second
page, which is totally empty. I can't delete from the second page.  I can't
delete from the first page because of the template cells. Nothing works and I'm
already aggravated by all the mosquitos because I have to move next week and I
have no idea where I'm going. it would nice if the computers did as expected. 

Actual Results:
the program preferred crashing to performing.  I gave up. without Libre office,
I don't have a resume. not a resume on a template. 

Expected Results:
I don't know what info you want here and it won't allow me to leave this blank.
so I'm writing more things about the imaginary mosquitos hoping you'll forgive
the interruption and find a way for me to delete a page from the properties
menu or something along those lines. 


Reproducible: Always


User Profile Reset: No

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

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

[Libreoffice-bugs] [Bug 155893] Table cell baseline misalignment when using different fonts

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

V Stuart Foote  changed:

   What|Removed |Added

 CC||vsfo...@libreoffice.org

--- Comment #18 from V Stuart Foote  ---
(In reply to Eyal Rozenberg from comment #17)

> What about the question regarding what's being aligned? Top-of-ascenders or
> mean line? Or something else?
> 
> Also, if the original intention was mis-determined, then it's a design bug
> rather than an implementation bug...

IIUC we have never made direct use of the 0 base within a font. Rather, we take
the font's total height --between ascent top and descent bottom (font designers
choice with M hight plus any *internal* leading above or below) and that height
is what is alligned TOP, CENTER or BOTTOM.

Meaning that any two fonts with different metrics will ALWAYS allign
differently--there is no common base line extracted from font(s).

Try it with an exaggerated font like Styx Two.

Short of a rewrite of VCL font handling, don't see a bug here, it is doing what
is expected. 

While enhancement to actually align on the 0 base would be at odds with what
other word processors do, don't see much demand there.

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

[Libreoffice-ux-advise] [Bug 155893] Table cell baseline misalignment when using different fonts

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

V Stuart Foote  changed:

   What|Removed |Added

 CC||vsfo...@libreoffice.org

--- Comment #18 from V Stuart Foote  ---
(In reply to Eyal Rozenberg from comment #17)

> What about the question regarding what's being aligned? Top-of-ascenders or
> mean line? Or something else?
> 
> Also, if the original intention was mis-determined, then it's a design bug
> rather than an implementation bug...

IIUC we have never made direct use of the 0 base within a font. Rather, we take
the font's total height --between ascent top and descent bottom (font designers
choice with M hight plus any *internal* leading above or below) and that height
is what is alligned TOP, CENTER or BOTTOM.

Meaning that any two fonts with different metrics will ALWAYS allign
differently--there is no common base line extracted from font(s).

Try it with an exaggerated font like Styx Two.

Short of a rewrite of VCL font handling, don't see a bug here, it is doing what
is expected. 

While enhancement to actually align on the 0 base would be at odds with what
other word processors do, don't see much demand there.

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

[Libreoffice-commits] core.git: .git-hooks/pre-commit

2023-06-19 Thread Taichi Haradaguchi (via logerrit)
 .git-hooks/pre-commit |2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

New commits:
commit eca4e82cac2c9fea6f9bd23fb0196ee7a3016223
Author: Taichi Haradaguchi <20001...@ymail.ne.jp>
AuthorDate: Sat Jun 10 18:20:50 2023 +0900
Commit: Taichi Haradaguchi <20001...@ymail.ne.jp>
CommitDate: Tue Jun 20 02:10:44 2023 +0200

Fix typo in .git-hooks/pre-commit

...to avoid a error "Cannot run git diff-index. at .git/hooks/pre-commit 
line 51." that occures on Windows.

Change-Id: I868e87940f9fcef950970b59e8cbe747f80c7198
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/152830
Tested-by: Jenkins
Reviewed-by: Taichi Haradaguchi <20001...@ymail.ne.jp>

diff --git a/.git-hooks/pre-commit b/.git-hooks/pre-commit
index f3ea7b093895..521ed202b9ac 100755
--- a/.git-hooks/pre-commit
+++ b/.git-hooks/pre-commit
@@ -48,7 +48,7 @@ sub check_whitespaces($)
 print STDERR "$filename:$lineno:$line\n";
 }
 }
-open( FILES, "git-diff-index -p -M --cached $h |" ) ||  die "Cannot run 
git diff-index.";
+open( FILES, "git diff-index -p -M --cached $h |" ) ||  die "Cannot run 
git diff-index.";
 while ()
 {
 if (m|^diff --git a/(.*) b/\1$|)


[Libreoffice-commits] core.git: Branch 'distro/collabora/co-22.05' - bridges/source

2023-06-19 Thread Tor Lillqvist (via logerrit)
 bridges/source/cpp_uno/gcc3_ios/unwind-cxx.h |2 ++
 1 file changed, 2 insertions(+)

New commits:
commit 32b334d57970e515141a0d5b1488e72a8f3f6fd6
Author: Tor Lillqvist 
AuthorDate: Thu Apr 20 17:43:03 2023 +0300
Commit: Aron Budea 
CommitDate: Tue Jun 20 01:29:35 2023 +0200

Fix compilation with latest Xcode with iOS SDK 16.4

Alternatively we could just remove lots of stuff that we apparently
don't actually need from this file, including the problematic typedef
and its uses.

_Unwind_Exception_Class now gets typedeffed in  as
uint64_t which effectively is the same as the unsigned
__attribute__((__mode__(__DI__))) that is used here.

Change-Id: Id96d43eb481ee4ae97dd315aa2fd741e5f627916
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/150702
Reviewed-by: Patrick Luby 
Reviewed-by: Tor Lillqvist 
Tested-by: Tor Lillqvist 
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/150711
(cherry picked from commit c3f181fd2ff02bd4aeabd151e2fd79e38fa81331)
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/153305
Tested-by: Aron Budea 
Reviewed-by: Aron Budea 

diff --git a/bridges/source/cpp_uno/gcc3_ios/unwind-cxx.h 
b/bridges/source/cpp_uno/gcc3_ios/unwind-cxx.h
index 83ed084860fd..aa35a5bc75e6 100644
--- a/bridges/source/cpp_uno/gcc3_ios/unwind-cxx.h
+++ b/bridges/source/cpp_uno/gcc3_ios/unwind-cxx.h
@@ -46,7 +46,9 @@ typedef unsigned _Unwind_Word 
__attribute__((__mode__(__word__)));
 typedef signed   _Unwind_Sword __attribute__((__mode__(__word__)));
 typedef unsigned _Unwind_Word __attribute__((__mode__(__word__)));
 typedef unsigned _Unwind_Ptr __attribute__((__mode__(__pointer__)));
+#if !defined __IPHONE_16_4 || __IPHONE_OS_VERSION_MAX_ALLOWED < __IPHONE_16_4
 typedef unsigned _Unwind_Exception_Class __attribute__((__mode__(__DI__)));
+#endif
 typedef unsigned _Unwind_Internal_Ptr __attribute__((__mode__(__pointer__)));
 
 #pragma GCC visibility push(default)


[Libreoffice-commits] core.git: Branch 'distro/collabora/co-22.05' - configure.ac

2023-06-19 Thread Aron Budea (via logerrit)
 configure.ac |4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

New commits:
commit 9543e7a2366ac3ce101009ae5d20b9d4ed0e06ef
Author: Aron Budea 
AuthorDate: Tue Jun 20 01:09:29 2023 +0200
Commit: Aron Budea 
CommitDate: Tue Jun 20 01:28:37 2023 +0200

Accept iOS SDK 16.5

Change-Id: Idf53c90cc3ef5c59cc9ad6151c13cc2125daf546
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/153304
Tested-by: Aron Budea 
Reviewed-by: Aron Budea 

diff --git a/configure.ac b/configure.ac
index f83a3c7f8f6b..9802aa37a0f8 100644
--- a/configure.ac
+++ b/configure.ac
@@ -3501,8 +3501,8 @@ dnl 
===
 
 if test $_os = iOS; then
 AC_MSG_CHECKING([what iOS SDK to use])
-current_sdk_ver=16.2
-older_sdk_vers="16.1 16.0 15.6 15.5 15.4 15.2 15.0"
+current_sdk_ver=16.5
+older_sdk_vers="16.4 16.3 16.2 16.1 16.0 15.6 15.5 15.4 15.2 15.0"
 if test "$enable_ios_simulator" = "yes"; then
 platform=iPhoneSimulator
 versionmin=-mios-simulator-version-min=14.5


[Libreoffice-ux-advise] [Bug 122970] Direct cursor leaves screen trail with mouse pointer movement and no text

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

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

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

tdf#122970 Fix direct cursor leaving screen trail

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 on the CC list for the bug.

[Libreoffice-ux-advise] [Bug 122970] Direct cursor leaves screen trail with mouse pointer movement and no text

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

Commit Notification  changed:

   What|Removed |Added

 Whiteboard||target:24.2.0

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

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

2023-06-19 Thread Hossein (via logerrit)
 sw/source/uibase/docvw/edtwin.cxx   |   18 +++---
 sw/source/uibase/docvw/edtwin2.cxx  |   21 
 sw/source/uibase/inc/edtwin.hxx |1 
 sw/source/uibase/inc/shdwcrsr.hxx   |5 ---
 sw/source/uibase/utlui/shdwcrsr.cxx |   59 +---
 5 files changed, 24 insertions(+), 80 deletions(-)

New commits:
commit f9f7cfc080c3adb751ceca96be4ca5440de4a2b6
Author: Hossein 
AuthorDate: Wed Jun 14 23:55:06 2023 +0200
Commit: Hossein 
CommitDate: Tue Jun 20 01:03:55 2023 +0200

tdf#122970 Fix direct cursor leaving screen trail

Previously, an old method using RasterOp::Xor rendering (see tdf#38844)
was used to draw the extra triangle left or right of the mouse pointer
in direct cursor mode. Now, instead of drawing it manually, we change
the cursor type to somewhat similar pointer type.

There is no perfect match for the previous mouse pointer shape, so now
instead of left triangle, PointerStyle::AutoScrollW is used. Also instead
of right triangle, PointerStyle::AutoScrollE is used.

Change-Id: Iadb955f9fcee0978a190e0b8920186a2579f3a4b
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/153099
Tested-by: Jenkins
Reviewed-by: Hossein 

diff --git a/sw/source/uibase/docvw/edtwin.cxx 
b/sw/source/uibase/docvw/edtwin.cxx
index ba62bb8fa856..65ec052a 100644
--- a/sw/source/uibase/docvw/edtwin.cxx
+++ b/sw/source/uibase/docvw/edtwin.cxx
@@ -634,6 +634,14 @@ void SwEditWin::UpdatePointer(const Point , 
sal_uInt16 nModifier )
 eStyle = PointerStyle::HideWhitespace;
 }
 
+if( m_pShadCursor )
+{
+if( text::HoriOrientation::LEFT == m_eOrient )// Arrow to the 
right
+eStyle = PointerStyle::AutoScrollE;
+else// Arrow to the left
+eStyle = PointerStyle::AutoScrollW;
+}
+
 SetPointer( eStyle );
 }
 }
@@ -4537,16 +4545,16 @@ void SwEditWin::MouseMove(const MouseEvent& _rMEvt)
 !rSh.HasSelection() && !GetOutDev()->GetConnectMetaFile() )
 {
 SwRect aRect;
-sal_Int16 eOrient;
+
 SwFillMode eMode = 
rSh.GetViewOptions()->GetShdwCursorFillMode();
-if( rSh.GetShadowCursorPos( aDocPt, eMode, aRect, eOrient 
))
+if( rSh.GetShadowCursorPos( aDocPt, eMode, aRect, 
m_eOrient ))
 {
 if( !m_pShadCursor )
 m_pShadCursor.reset( new SwShadowCursor( *this,
 rSh.GetViewOptions()->GetDirectCursorColor() ) 
);
-if( text::HoriOrientation::RIGHT != eOrient && 
text::HoriOrientation::CENTER != eOrient )
-eOrient = text::HoriOrientation::LEFT;
-m_pShadCursor->SetPos( aRect.Pos(), aRect.Height(), 
static_cast< sal_uInt16 >(eOrient) );
+if( text::HoriOrientation::RIGHT != m_eOrient && 
text::HoriOrientation::CENTER != m_eOrient )
+m_eOrient = text::HoriOrientation::LEFT;
+m_pShadCursor->SetPos( aRect.Pos(), aRect.Height(), 
static_cast< sal_uInt16 >(m_eOrient) );
 bDelShadCursor = false;
 }
 }
diff --git a/sw/source/uibase/docvw/edtwin2.cxx 
b/sw/source/uibase/docvw/edtwin2.cxx
index bafd9570a726..6e09ffd19b45 100644
--- a/sw/source/uibase/docvw/edtwin2.cxx
+++ b/sw/source/uibase/docvw/edtwin2.cxx
@@ -660,24 +660,6 @@ void SwEditWin::Paint(vcl::RenderContext& rRenderContext, 
const tools::Rectangle
 SwWrtShell* pWrtShell = GetView().GetWrtShellPtr();
 if(!pWrtShell)
 return;
-bool bPaintShadowCursor = false;
-if( m_pShadCursor )
-{
-tools::Rectangle aRect( m_pShadCursor->GetRect());
-// fully resides inside?
-if( rRect.Contains( aRect ) )
-{
-// then cancel
-m_pShadCursor.reset();
-}
-else if( rRect.Overlaps( aRect ))
-{
-// resides somewhat above, then everything is clipped outside
-// and we have to make the "inner part" at the end of the
-// Paint visible again. Otherwise Paint errors occur!
-bPaintShadowCursor = true;
-}
-}
 
 if ( GetView().GetVisArea().GetWidth()  <= 0 ||
   GetView().GetVisArea().GetHeight() <= 0 )
@@ -698,9 +680,6 @@ void SwEditWin::Paint(vcl::RenderContext& rRenderContext, 
const tools::Rectangle
 }
 pWrtShell->setOutputToWindow(false);
 }
-
-if( bPaintShadowCursor )
-m_pShadCursor->Paint();
 }
 
 /* vim:set shiftwidth=4 softtabstop=4 expandtab: */
diff --git a/sw/source/uibase/inc/edtwin.hxx b/sw/source/uibase/inc/edtwin.hxx
index aac86d4f8807..714e6bcc3be0 100644
--- a/sw/source/uibase/inc/edtwin.hxx
+++ 

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

2023-06-19 Thread Henry Castro (via logerrit)
 sfx2/source/control/unoctitm.cxx |   10 --
 1 file changed, 8 insertions(+), 2 deletions(-)

New commits:
commit 71e5f7e43471cc479ea1e818c813170a389964e6
Author: Henry Castro 
AuthorDate: Thu Jun 1 11:04:13 2023 -0400
Commit: Henry Castro 
CommitDate: Tue Jun 20 00:41:35 2023 +0200

lok: sfx2: fix change state "SheetRightToLeft"

The UNO command "SheetRightToLeft" can be disabled

Signed-off-by: Henry Castro 
Change-Id: I54742c9d52eb52e36154e0aac2cdf440771eb177
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/152502
Tested-by: Caolán McNamara 
Reviewed-by: Caolán McNamara 
(cherry picked from commit fc8270f06eca5ba2ba25673a424b36d9e352f62a)
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/152546
Tested-by: Jenkins CollaboraOffice 
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/153267
Tested-by: Jenkins

diff --git a/sfx2/source/control/unoctitm.cxx b/sfx2/source/control/unoctitm.cxx
index 1b0d1223a3b7..4495873a89af 100644
--- a/sfx2/source/control/unoctitm.cxx
+++ b/sfx2/source/control/unoctitm.cxx
@@ -938,8 +938,14 @@ static void InterceptLOKStateChangeEvent(sal_uInt16 nSID, 
SfxViewFrame* pViewFra
 aEvent.FeatureURL.Path == "SpacePara2")
 {
 bool bTemp = false;
-aEvent.State >>= bTemp;
-aBuffer.append(bTemp);
+
+if (aEvent.IsEnabled)
+{
+aEvent.State >>= bTemp;
+aBuffer.append(bTemp);
+}
+else
+aBuffer.append("disabled");
 }
 else if (aEvent.FeatureURL.Path == "CharFontName")
 {


[Libreoffice-bugs] [Bug 155893] Table cell baseline misalignment when using different fonts

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

--- Comment #17 from Eyal Rozenberg  ---
(In reply to ⁨خالد حسني⁩ from comment #15)
> I don’t really have anything more to added. This is a feature request since
> the current behavior is working as intended.

What about the question regarding what's being aligned? Top-of-ascenders or
mean line? Or something else?

Also, if the original intention was mis-determined, then it's a design bug
rather than an implementation bug...

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

[Libreoffice-ux-advise] [Bug 155893] Table cell baseline misalignment when using different fonts

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

--- Comment #17 from Eyal Rozenberg  ---
(In reply to ⁨خالد حسني⁩ from comment #15)
> I don’t really have anything more to added. This is a feature request since
> the current behavior is working as intended.

What about the question regarding what's being aligned? Top-of-ascenders or
mean line? Or something else?

Also, if the original intention was mis-determined, then it's a design bug
rather than an implementation bug...

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

[Libreoffice-bugs] [Bug 155893] Table cell baseline misalignment when using different fonts

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

Eyal Rozenberg  changed:

   What|Removed |Added

 Ever confirmed|1   |0
 Status|NEEDINFO|UNCONFIRMED

--- Comment #16 from Eyal Rozenberg  ---
(In reply to ⁨خالد حسني⁩ from comment #15)
> I don’t really have anything more to added. This is a feature request since
> the current behavior is working as intended.

But if the intention is wrong, then it's a bug.

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

[Libreoffice-ux-advise] [Bug 155893] Table cell baseline misalignment when using different fonts

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

Eyal Rozenberg  changed:

   What|Removed |Added

 Ever confirmed|1   |0
 Status|NEEDINFO|UNCONFIRMED

--- Comment #16 from Eyal Rozenberg  ---
(In reply to ⁨خالد حسني⁩ from comment #15)
> I don’t really have anything more to added. This is a feature request since
> the current behavior is working as intended.

But if the intention is wrong, then it's a bug.

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

[Libreoffice-bugs] [Bug 155917] Writer crashes when inserting ODT file containing PDF into table in another ODT doc

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

--- Comment #4 from konsultor  ---
There was no crash report dialog like those that I've seen ask to use debug
procedures and files. 
Repeated the paste actions several more times without a crash;  can't reproduce
again at this time.
OpenSuse is due for a major update in a few weeks which I expect to bring LO
7.5.  Will try again then.
Thanks for your prompt attention.

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

[Libreoffice-bugs] [Bug 155935] New: When typing multiple spaces, cursor does not go to next line. It continues off the page and off the screen

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

Bug ID: 155935
   Summary: When typing multiple spaces, cursor does not go to
next line.  It continues off the page and off the
screen
   Product: LibreOffice
   Version: 7.5.4.2 release
  Hardware: x86-64 (AMD64)
OS: Linux (All)
Status: UNCONFIRMED
  Severity: minor
  Priority: medium
 Component: Writer
  Assignee: libreoffice-bugs@lists.freedesktop.org
  Reporter: jma...@gmail.com

Description:
When typing spaces, the cursor continues out of the typing area and even off
the screen.  Type a non-white space character brings the cursor to the
beginning of the next line.  The still exists off the page and if you
backspace, the cursor will leave the page again.

Steps to Reproduce:
1. Repeatedly press the space button
2.
3.

Actual Results:
Cursor continues off the screen.

Expected Results:
Cursor should go to next line once it reaches the end of the page.


Reproducible: Always


User Profile Reset: No

Additional Info:
Version: 7.5.4.2 (X86_64) / LibreOffice Community
Build ID: 50(Build:2)
CPU threads: 12; OS: Linux 6.2; UI render: default; VCL: kf5 (cairo+xcb)
Locale: en-US (en_US.UTF-8); UI: en-US
Ubuntu package version: 4:7.5.4-0ubuntu0.23.04.1
Calc: threaded

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

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

2023-06-19 Thread Henry Castro (via logerrit)
 sc/source/filter/oox/condformatbuffer.cxx |   17 +
 1 file changed, 9 insertions(+), 8 deletions(-)

New commits:
commit 3a827ee8f05a5188eebda90d0e306cc90ee28638
Author: Henry Castro 
AuthorDate: Mon Jun 19 11:41:52 2023 -0400
Commit: Henry Castro 
CommitDate: Mon Jun 19 23:27:51 2023 +0200

sc: filter: oox: fix setting value to color scale

The COLORSCALE_VALUE setValue method reset the mpCell
that contains formula.

Signed-off-by: Henry Castro 
Change-Id: Idbbfcdc5bce78542ce671753d9a70dcd375e7966
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/153281
Tested-by: Jenkins

diff --git a/sc/source/filter/oox/condformatbuffer.cxx 
b/sc/source/filter/oox/condformatbuffer.cxx
index 046f37d2c4aa..75171441c23d 100644
--- a/sc/source/filter/oox/condformatbuffer.cxx
+++ b/sc/source/filter/oox/condformatbuffer.cxx
@@ -1486,16 +1486,17 @@ void ExtCfDataBarRule::finalizeImport()
 else if (maModel.maColorScaleType == "formula")
 pEntry->SetType(COLORSCALE_FORMULA);
 else if (maModel.maColorScaleType == "num")
-pEntry->SetType(COLORSCALE_VALUE);
-
-if (!maModel.msScaleTypeValue.isEmpty())
 {
-sal_Int32 nSize = 0;
-rtl_math_ConversionStatus eStatus = 
rtl_math_ConversionStatus_Ok;
-double fValue = 
rtl::math::stringToDouble(maModel.msScaleTypeValue, '.', '\0', , 
);
-if (eStatus == rtl_math_ConversionStatus_Ok && nSize == 
maModel.msScaleTypeValue.getLength())
+pEntry->SetType(COLORSCALE_VALUE);
+if (!maModel.msScaleTypeValue.isEmpty())
 {
-pEntry->SetValue(fValue);
+sal_Int32 nSize = 0;
+rtl_math_ConversionStatus eStatus = 
rtl_math_ConversionStatus_Ok;
+double fValue = 
rtl::math::stringToDouble(maModel.msScaleTypeValue, '.', '\0', , 
);
+if (eStatus == rtl_math_ConversionStatus_Ok && nSize == 
maModel.msScaleTypeValue.getLength())
+{
+pEntry->SetValue(fValue);
+}
 }
 }
 break;


[Libreoffice-commits] core.git: Branch 'distro/collabora/co-23.05' - sc/source

2023-06-19 Thread Henry Castro (via logerrit)
 sc/source/filter/oox/condformatbuffer.cxx |   17 +
 1 file changed, 9 insertions(+), 8 deletions(-)

New commits:
commit f451e05d997870bf5eb250bc9d4dc8c39ce1aa85
Author: Henry Castro 
AuthorDate: Mon Jun 19 11:41:52 2023 -0400
Commit: Henry Castro 
CommitDate: Mon Jun 19 23:27:05 2023 +0200

sc: filter: oox: fix setting value to color scale

The COLORSCALE_VALUE setValue method reset the mpCell
that contains formula.

Signed-off-by: Henry Castro 
Change-Id: Idbbfcdc5bce78542ce671753d9a70dcd375e7966
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/153280
Tested-by: Jenkins CollaboraOffice 

diff --git a/sc/source/filter/oox/condformatbuffer.cxx 
b/sc/source/filter/oox/condformatbuffer.cxx
index 42d932908191..17747df22461 100644
--- a/sc/source/filter/oox/condformatbuffer.cxx
+++ b/sc/source/filter/oox/condformatbuffer.cxx
@@ -1486,16 +1486,17 @@ void ExtCfDataBarRule::finalizeImport()
 else if (maModel.maColorScaleType == "formula")
 pEntry->SetType(COLORSCALE_FORMULA);
 else if (maModel.maColorScaleType == "num")
-pEntry->SetType(COLORSCALE_VALUE);
-
-if (!maModel.msScaleTypeValue.isEmpty())
 {
-sal_Int32 nSize = 0;
-rtl_math_ConversionStatus eStatus = 
rtl_math_ConversionStatus_Ok;
-double fValue = 
rtl::math::stringToDouble(maModel.msScaleTypeValue, '.', '\0', , 
);
-if (eStatus == rtl_math_ConversionStatus_Ok && nSize == 
maModel.msScaleTypeValue.getLength())
+pEntry->SetType(COLORSCALE_VALUE);
+if (!maModel.msScaleTypeValue.isEmpty())
 {
-pEntry->SetValue(fValue);
+sal_Int32 nSize = 0;
+rtl_math_ConversionStatus eStatus = 
rtl_math_ConversionStatus_Ok;
+double fValue = 
rtl::math::stringToDouble(maModel.msScaleTypeValue, '.', '\0', , 
);
+if (eStatus == rtl_math_ConversionStatus_Ok && nSize == 
maModel.msScaleTypeValue.getLength())
+{
+pEntry->SetValue(fValue);
+}
 }
 }
 break;


[Libreoffice-bugs] [Bug 141692] When Tabbed interface is applied to all apps, you still have to enter each app to turn on or off the MenuBar individually instead of applying to all.

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

Justin L  changed:

   What|Removed |Added

 Attachment #187946|0   |1
is obsolete||

--- Comment #9 from Justin L  ---
Created attachment 188004
  --> https://bugs.documentfoundation.org/attachment.cgi?id=188004=edit
wasta-TabbedUIwithMenu.oxt: version 1.0.1 includes fixes for bug 126095

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

[Libreoffice-bugs] [Bug 155893] Table cell baseline misalignment when using different fonts

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

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

   What|Removed |Added

 CC|kha...@libreoffice.org  |

--- Comment #15 from ⁨خالد حسني⁩  ---
I don’t really have anything more to added. This is a feature request since the
current behavior is working as intended.

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

[Libreoffice-ux-advise] [Bug 155893] Table cell baseline misalignment when using different fonts

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

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

   What|Removed |Added

 CC|kha...@libreoffice.org  |

--- Comment #15 from ⁨خالد حسني⁩  ---
I don’t really have anything more to added. This is a feature request since the
current behavior is working as intended.

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

[Libreoffice-commits] core.git: svgio/qa svgio/source

2023-06-19 Thread Xisco Fauli (via logerrit)
 svgio/qa/cppunit/SvgImportTest.cxx|   19 ++-
 svgio/qa/cppunit/data/tdf145896.svg   |   12 
 svgio/source/svgreader/svgdocumenthandler.cxx |   17 +++--
 svgio/source/svgreader/svgstylenode.cxx   |6 +++---
 4 files changed, 36 insertions(+), 18 deletions(-)

New commits:
commit 08a6ca6d426280f9ce225d9f25694c43e7ab810f
Author: Xisco Fauli 
AuthorDate: Mon Jun 19 16:17:00 2023 +0200
Commit: Xisco Fauli 
CommitDate: Mon Jun 19 23:04:46 2023 +0200

tdf#145896: set style to 'text/css' by default

This is a regression from 4c31a0be1d8048bf3340acbb59248185e4b93041
"Resolves: #i125326# accept CssStyles with missing type attribute"

Calling setTextCss(true) when there are no attributes is wrong,
since it might have attributes like 'id'.
The unittest added also covers i125326 is still fixed

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

diff --git a/svgio/qa/cppunit/SvgImportTest.cxx 
b/svgio/qa/cppunit/SvgImportTest.cxx
index c9ec752d882a..43dde4da9997 100644
--- a/svgio/qa/cppunit/SvgImportTest.cxx
+++ b/svgio/qa/cppunit/SvgImportTest.cxx
@@ -302,9 +302,26 @@ CPPUNIT_TEST_FIXTURE(Test, testFontsizeRelative)
 assertXPath(pDocument, "/primitive2D/transform/textsimpleportion[2]", 
"familyname", "serif");
 }
 
+CPPUNIT_TEST_FIXTURE(Test, testTdf145896)
+{
+Primitive2DSequence aSequence = 
parseSvg(u"/svgio/qa/cppunit/data/tdf145896.svg");
+CPPUNIT_ASSERT_EQUAL(1, static_cast(aSequence.getLength()));
+
+drawinglayer::Primitive2dXmlDump dumper;
+xmlDocUniquePtr pDocument = dumper.dumpAndParse(aSequence);
+
+CPPUNIT_ASSERT (pDocument);
+
+// Without the fix in place, this test would have failed with
+// - Expected: #00
+// - Actual  : #00
+assertXPath(pDocument, "/primitive2D/transform/polypolygoncolor[1]", 
"color", "#00");
+assertXPath(pDocument, "/primitive2D/transform/polypolygoncolor[2]", 
"color", "#008000");
+assertXPath(pDocument, "/primitive2D/transform/polypolygoncolor[3]", 
"color", "#ff");
+}
+
 CPPUNIT_TEST_FIXTURE(Test, testTdf97717)
 {
-//Check when font-size uses relative units (em,ex) and it's based on its 
parent's font-size
 Primitive2DSequence aSequence = 
parseSvg(u"/svgio/qa/cppunit/data/tdf97717.svg");
 CPPUNIT_ASSERT_EQUAL(1, static_cast(aSequence.getLength()));
 
diff --git a/svgio/qa/cppunit/data/tdf145896.svg 
b/svgio/qa/cppunit/data/tdf145896.svg
new file mode 100644
index ..d434a961b9d0
--- /dev/null
+++ b/svgio/qa/cppunit/data/tdf145896.svg
@@ -0,0 +1,12 @@
+http://www.w3.org/2000/svg; 
xmlns:xlink="http://www.w3.org/1999/xlink; viewBox="-0 0 300 300">
+
+
+.st0{fill:yellow;}.st1{fill:green;}
+
+
+.st2{fill:red;}
+
+
+
+
+
diff --git a/svgio/source/svgreader/svgdocumenthandler.cxx 
b/svgio/source/svgreader/svgdocumenthandler.cxx
index 43151253aacc..e26312d43163 100644
--- a/svgio/source/svgreader/svgdocumenthandler.cxx
+++ b/svgio/source/svgreader/svgdocumenthandler.cxx
@@ -302,21 +302,10 @@ namespace
 {
 SvgStyleNode* pNew = new SvgStyleNode(maDocument, 
mpTarget);
 mpTarget = pNew;
-const sal_uInt32 nAttributes(xAttribs->getLength());
 
-if(0 == nAttributes)
-{
-// #i125326# no attributes, thus also no 
type="text/css". This is allowed to be missing,
-// thus do mark this style as CssStyle. This is 
required to read the contained
-// text (which defines the css style)
-pNew->setTextCss(true);
-}
-else
-{
-// #i125326# there are attributes, read them. This 
will set isTextCss to true if
-// a type="text/css" is contained as exact match, else 
not
-mpTarget->parseAttributes(xAttribs);
-}
+// #i125326# there are attributes, read them. This will 
set isTextCss to false if
+// type attibute is different to "text/css"
+mpTarget->parseAttributes(xAttribs);
 
 if(pNew->isTextCss())
 {
diff --git a/svgio/source/svgreader/svgstylenode.cxx 
b/svgio/source/svgreader/svgstylenode.cxx
index ef25e6a83b47..b11f7129e0b3 100644
--- a/svgio/source/svgreader/svgstylenode.cxx
+++ b/svgio/source/svgreader/svgstylenode.cxx
@@ -28,7 +28,7 @@ namespace svgio::svgreader
 SvgDocument& rDocument,
 SvgNode* pParent)
 :   SvgNode(SVGToken::Style, rDocument, pParent),
-mbTextCss(false)
+mbTextCss(true)
 {
 }
 
@@ -57,9 +57,9 @@ 

[Libreoffice-bugs] [Bug 113195] [META] Japanese language-specific CJK issues

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

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

   What|Removed |Added

 Depends on|115321  |


Referenced Bugs:

https://bugs.documentfoundation.org/show_bug.cgi?id=115321
[Bug 115321] Vertical Japanese text lines with emphasis mark above in odt
exported to PDF is shown a quarter font height lower than the normal lines, and
no emphasis mark is shown
-- 
You are receiving this mail because:
You are the assignee for the bug.

[Libreoffice-bugs] [Bug 106045] [META] Vertical and rotated text direction issues

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

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

   What|Removed |Added

 Depends on||115321


Referenced Bugs:

https://bugs.documentfoundation.org/show_bug.cgi?id=115321
[Bug 115321] Vertical Japanese text lines with emphasis mark above in odt
exported to PDF is shown a quarter font height lower than the normal lines, and
no emphasis mark is shown
-- 
You are receiving this mail because:
You are the assignee for the bug.

[Libreoffice-bugs] [Bug 115321] Vertical Japanese text lines with emphasis mark above in odt exported to PDF is shown a quarter font height lower than the normal lines, and no emphasis mark is shown

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

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

   What|Removed |Added

 Blocks|113195  |106045
 CC||kha...@libreoffice.org


Referenced Bugs:

https://bugs.documentfoundation.org/show_bug.cgi?id=106045
[Bug 106045] [META] Vertical and rotated text direction issues
https://bugs.documentfoundation.org/show_bug.cgi?id=113195
[Bug 113195] [META] Japanese language-specific CJK issues
-- 
You are receiving this mail because:
You are the assignee for the bug.

[Libreoffice-bugs] [Bug 103378] [META] PDF export bugs and enhancements

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

Bug 139065 Summary: PDF Export: Emphasis Mark not shown in the exported PDF
https://bugs.documentfoundation.org/show_bug.cgi?id=139065

   What|Removed |Added

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

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

[Libreoffice-bugs] [Bug 139065] PDF Export: Emphasis Mark not shown in the exported PDF

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

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

   What|Removed |Added

 Status|NEW |RESOLVED
 Resolution|--- |FIXED
 CC||kha...@libreoffice.org

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

[Libreoffice-bugs] [Bug 131751] Character emphasis is not rendered correctly in print and export

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

--- Comment #11 from ⁨خالد حسني⁩  ---


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

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

[Libreoffice-bugs] [Bug 139065] PDF Export: Emphasis Mark not shown in the exported PDF

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

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

   What|Removed |Added

 CC||khanson...@gmail.com

--- Comment #8 from ⁨خالد حسني⁩  ---
*** Bug 131751 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 107657] [META] Font effects bugs and enhancements

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

Bug 131751 Summary: Character emphasis is not rendered correctly in print and 
export
https://bugs.documentfoundation.org/show_bug.cgi?id=131751

   What|Removed |Added

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

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

[Libreoffice-bugs] [Bug 83066] [META] CJK (Chinese, Japanese, Korean, and Vietnamese) language issues

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

Bug 131751 Summary: Character emphasis is not rendered correctly in print and 
export
https://bugs.documentfoundation.org/show_bug.cgi?id=131751

   What|Removed |Added

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

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

[Libreoffice-bugs] [Bug 115321] Vertical Japanese text lines with emphasis mark above in odt exported to PDF is shown a quarter font height lower than the normal lines, and no emphasis mark is shown

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

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

   What|Removed |Added

 CC||khanson...@gmail.com

--- Comment #11 from ⁨خالد حسني⁩  ---
*** Bug 131751 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 131751] Character emphasis is not rendered correctly in print and export

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

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

   What|Removed |Added

 Resolution|--- |DUPLICATE
 Status|NEW |RESOLVED
 CC||kha...@libreoffice.org

--- Comment #10 from ⁨خالد حسني⁩  ---


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

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

[Libreoffice-bugs] [Bug 83066] [META] CJK (Chinese, Japanese, Korean, and Vietnamese) language issues

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

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

   What|Removed |Added

 Blocks|155820  |
 Depends on||155820


Referenced Bugs:

https://bugs.documentfoundation.org/show_bug.cgi?id=155820
[Bug 155820] isCJKIVSCharacter needs to support CJK Unified Ideographs
Extension Block C to H for Unicode15
-- 
You are receiving this mail because:
You are the assignee for the bug.

[Libreoffice-bugs] [Bug 155820] isCJKIVSCharacter needs to support CJK Unified Ideographs Extension Block C to H for Unicode15

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

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

   What|Removed |Added

 Depends on|83066   |
 Blocks||83066


Referenced Bugs:

https://bugs.documentfoundation.org/show_bug.cgi?id=83066
[Bug 83066] [META] CJK (Chinese, Japanese, Korean, and Vietnamese) language
issues
-- 
You are receiving this mail because:
You are the assignee for the bug.

[Libreoffice-bugs] [Bug 105966] Preset of area style does not respect automatic increment

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

Regina Henschel  changed:

   What|Removed |Added

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

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

[Libreoffice-bugs] [Bug 107787] Gradients steps don't save

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

Regina Henschel  changed:

   What|Removed |Added

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

--- Comment #31 from Regina Henschel  ---
The problem with the 'Increments' field and check box is related to the fix for
bug 105966. That fix changes the initial value from the XATTR_GRADIENTSTEPCOUNT
property in the property-set of the SvxGradientTabPage to the StepCount
component of the gradient definition.

But the gradient definitions in file markup have no information about step
count, because step count is part of the graphic style of objects and not of
gradient definitions. So the value for StepCount is always 0 (which means
"automatic") when you use an initial gradient. And that means that the checkbox
'automatic' is marked regardless of the actual step count of the shape.

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

[Libreoffice-bugs] [Bug 103610] [META] Slide show (presentation mode) bugs and enhancements

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

Bug 43671 Summary: VIEWING: CJK Emphasis marks not showing in slideshow
https://bugs.documentfoundation.org/show_bug.cgi?id=43671

   What|Removed |Added

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

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

[Libreoffice-bugs] [Bug 83066] [META] CJK (Chinese, Japanese, Korean, and Vietnamese) language issues

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

Bug 43671 Summary: VIEWING: CJK Emphasis marks not showing in slideshow
https://bugs.documentfoundation.org/show_bug.cgi?id=43671

   What|Removed |Added

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

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

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

2023-06-19 Thread Khaled Hosny (via logerrit)
 canvas/source/cairo/cairo_canvasfont.cxx|9 +++--
 canvas/source/cairo/cairo_canvasfont.hxx|3 +++
 canvas/source/cairo/cairo_canvashelper_text.cxx |3 +++
 3 files changed, 13 insertions(+), 2 deletions(-)

New commits:
commit 35803990c9b1881074460659acdac6b2799c99ee
Author: Khaled Hosny 
AuthorDate: Mon Jun 19 21:19:46 2023 +0300
Commit: خالد حسني 
CommitDate: Mon Jun 19 22:51:03 2023 +0200

tdf#43671: Pass through emphasis mark setting with cairo canvas

Other canvas implementations passed it through, but cairo canvas was
not.

Change-Id: I9b4cc500998635568c095866f9099f83bf1c984e
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/153299
Tested-by: Jenkins
Reviewed-by: خالد حسني 

diff --git a/canvas/source/cairo/cairo_canvasfont.cxx 
b/canvas/source/cairo/cairo_canvasfont.cxx
index 16af11838a91..82f300e8a205 100644
--- a/canvas/source/cairo/cairo_canvasfont.cxx
+++ b/canvas/source/cairo/cairo_canvasfont.cxx
@@ -27,6 +27,8 @@
 #include 
 #include 
 
+#include 
+
 #include "cairo_canvasfont.hxx"
 #include "cairo_textlayout.hxx"
 
@@ -36,15 +38,18 @@ namespace cairocanvas
 {
 
 CanvasFont::CanvasFont( const rendering::FontRequest&   
rFontRequest,
-const uno::Sequence< beans::PropertyValue >&
/*rExtraFontProperties*/,
+const uno::Sequence< beans::PropertyValue >&
rExtraFontProperties,
 const geometry::Matrix2D&   
rFontMatrix,
 SurfaceProviderRef  
rDevice ) :
 maFont( vcl::Font( rFontRequest.FontDescription.FamilyName,
   rFontRequest.FontDescription.StyleName,
   Size( 0, ::basegfx::fround(rFontRequest.CellSize) ) ) ),
 maFontRequest( rFontRequest ),
-mpRefDevice(std::move( rDevice ))
+mpRefDevice(std::move( rDevice )),
+mnEmphasisMark(0)
 {
+::canvas::tools::extractExtraFontProperties(rExtraFontProperties, 
mnEmphasisMark);
+
 maFont->SetAlignment( ALIGN_BASELINE );
 maFont->SetCharSet( 
(rFontRequest.FontDescription.IsSymbolFont==css::util::TriState_YES) ? 
RTL_TEXTENCODING_SYMBOL : RTL_TEXTENCODING_UNICODE );
 maFont->SetVertical( 
rFontRequest.FontDescription.IsVertical==css::util::TriState_YES );
diff --git a/canvas/source/cairo/cairo_canvasfont.hxx 
b/canvas/source/cairo/cairo_canvasfont.hxx
index e510f420c437..d5e015006c98 100644
--- a/canvas/source/cairo/cairo_canvasfont.hxx
+++ b/canvas/source/cairo/cairo_canvasfont.hxx
@@ -70,10 +70,13 @@ namespace cairocanvas
 
 vcl::Font const & getVCLFont() const;
 
+sal_uInt32 getEmphasisMark() const { return mnEmphasisMark; }
+
 private:
 ::canvas::vcltools::VCLObject maFont;
 css::rendering::FontRequest  maFontRequest;
 SurfaceProviderRef   mpRefDevice;
+sal_uInt32   mnEmphasisMark;
 };
 
 }
diff --git a/canvas/source/cairo/cairo_canvashelper_text.cxx 
b/canvas/source/cairo/cairo_canvashelper_text.cxx
index 6973607d4824..c8498bddf3b7 100644
--- a/canvas/source/cairo/cairo_canvashelper_text.cxx
+++ b/canvas/source/cairo/cairo_canvashelper_text.cxx
@@ -190,6 +190,9 @@ namespace cairocanvas
 aVCLFont.SetColor( aColor );
 aVCLFont.SetFillColor( aColor );
 
+if (pFont->getEmphasisMark())
+
aVCLFont.SetEmphasisMark(FontEmphasisMark(pFont->getEmphasisMark()));
+
 // no need to replicate this for mp2ndOutDev, we're modifying only 
aVCLFont here.
 if( !setupFontTransform( rOutDev, o_rOutPos, aVCLFont, viewState, 
renderState ) )
 return false;


[Libreoffice-bugs] [Bug 155934] FORMATTING: LibreOffice Calc does not apply HH:MM:SS time format to displayed value in Input Line

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

Eike Rathke  changed:

   What|Removed |Added

 Status|RESOLVED|CLOSED

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

[Libreoffice-bugs] [Bug 155934] FORMATTING: LibreOffice Calc does not apply HH:MM:SS time format to displayed value in Input Line

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

Eike Rathke  changed:

   What|Removed |Added

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

--- Comment #1 from Eike Rathke  ---
This is not a bug. Presented is the locale's time edit format, which for en-US
(and very few others) happens to be the AM/PM one.

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

[Libreoffice-bugs] [Bug 155901] MCGR: Adding gradient to user palette or setting a border changes last stop offset to 1

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

--- Comment #4 from Regina Henschel  ---
While working on problems with the 'Increment' setting in die Gradient dialog
(e.g. bug 107787) I stumble across a possible for this issue.

The member m_aColorStops of SvxGradientTabPage is used so that it only carries
the inner stops of a multicolor gradient. When building a basegfx::BGradient,
then the first and last color is taken from the color fields of the dialog and
forced to offset 0 and 1 respectively and only the intermediate stops are taken
from m_aColorStops. That is likely a leftover. With current implementation
basegfx::BGradient is used in the first place, and start and end color are
derived from it.

The relevant locations are in the various versions of createColorStops()
method. For example from tpgradnt.cxx:
640  basegfx::BColorStops SvxGradientTabPage::createColorStops()
641  {
642  basegfx::BColorStops aColorStops;
643  
644  aColorStops.emplace_back(0.0,
m_xLbColorFrom->GetSelectEntryColor().getBColor());
645  
646  if(!m_aColorStops.empty())
647  {
648  aColorStops.insert(aColorStops.begin(), m_aColorStops.begin(),
m_aColorStops.end());
649  }
650  
651  aColorStops.emplace_back(1.0,
m_xLbColorTo->GetSelectEntryColor().getBColor());
652  
653  return aColorStops;
654  }

All uses of m_aColorStops have to be changed so that is contains the entire
gradient. The dialog fields are only relevant for the color of the first and
last stops, but not for their offsets.

Armin, is my observation correct?

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

[Libreoffice-bugs] [Bug 126095] NB toolbars visible which should be hidden

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

--- Comment #9 from Justin L  ---
In sfx2/source/appl/appserv.cxx SID_TOOLBAR_MODE, it saves the current list of
toolbars into UserToolbars, and disables all toolbars - BUT ONLY FOR THE
CURRENT APPLICATION. This is why the Draw/Impress toolbars are not disabled
during "Apply to All"

private:resource/toolbar/toolbar is a UserToolbar that is configured by default
as true in
officecfg/registry/data/org/openoffice/Office/UI/ImpressWindowState.xcu

So that is why the long toolbar shows up by default. Also DrawWindowState.xcu. 

The 4-button presentation toolbar shows up because
DrawViewShell::ChangeEditMode turns it on for Impress when not in Master or
Handout mode.

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

[Libreoffice-bugs] [Bug 155933] LibreOffice Writer doesn't save docx file format properly(saves a compressed archive file instead), when i try to save it to cloud storage

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

Justin L  changed:

   What|Removed |Added

Version|7.5.1.2 release |unspecified
   Hardware|x86-64 (AMD64)  |All

--- Comment #1 from Justin L  ---
A DOCX file is just a zip file. What do you mean by "it is just a compressed
archive file"? What happens if you copy that file from your google drive
locally? Can you upload a broken docx to this bug report?

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

[Libreoffice-bugs] [Bug 155930] Writer doesn't always let you set the language of text to Hebrew

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

--- Comment #2 from Coburn Ingram  ---
Thanks, CTL resolved my issue.

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

[Libreoffice-bugs] [Bug 155934] New: FORMATTING: LibreOffice Calc does not apply HH:MM:SS time format to displayed value in Input Line

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

Bug ID: 155934
   Summary: FORMATTING: LibreOffice Calc does not apply HH:MM:SS
time format to displayed value in Input Line
   Product: LibreOffice
   Version: 7.5.4.2 release
  Hardware: x86-64 (AMD64)
OS: Windows (All)
Status: UNCONFIRMED
  Severity: minor
  Priority: medium
 Component: Calc
  Assignee: libreoffice-bugs@lists.freedesktop.org
  Reporter: acr...@cyber-wizard.com

Description:
LibreOffice Calc does not apply HH:MM:SS time format value to value displayed
in Input Line.

If one or more cells are formatted with the Time format "HH:MM:SS" (24-hour
clock), the value in the Input Line is displayed using the "HH:MM:SS AM/PM"
(12-hour clock) format.

Value in cell shows correctly UNLESS the Input Line is selected (in which case
it shows the incorrect (12-hour) formatting).

Steps to Reproduce:
1. Open LibreOffice Calc
2. Select a column OR select a cell
3. Right click
4. Select "Format Cells..."
5. Select Category: Time
6. Select Format HH:MM:SS
7. Select Language English - USA
8. Click OK
9. Click formatted cell
10. Enter "00:02:30" (for 00h 02m 30s)
11. Click off cell
12. Click back on cell and examine Input Line value

Actual Results:
12:02:30 AM

Expected Results:
00:02:30


Reproducible: Always


User Profile Reset: No

Additional Info:
Can duplicate under 7.5.4.2 (X86_64)/Build 36fd35 under Windows 10.0 Build
16299.

Can duplicate under Build ID 6.4.7.2-5.fc32 under Linux 5.11.

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

[Libreoffice-commits] core.git: include/vcl include/xmloff vcl/source writerfilter/source xmloff/source

2023-06-19 Thread Khaled Hosny (via logerrit)
 include/vcl/embeddedfontshelper.hxx  |4 ++--
 include/xmloff/xmlimp.hxx|2 +-
 vcl/source/gdi/embeddedfontshelper.cxx   |8 
 writerfilter/source/dmapper/FontTable.cxx|   14 +++---
 writerfilter/source/dmapper/FontTable.hxx|6 +++---
 xmloff/source/core/xmlimp.cxx|2 +-
 xmloff/source/style/XMLFontStylesContext.cxx |4 ++--
 7 files changed, 20 insertions(+), 20 deletions(-)

New commits:
commit d80d89d98183ee0c1a232b975107c319001f3fbc
Author: Khaled Hosny 
AuthorDate: Mon Jun 19 17:08:45 2023 +0300
Commit: خالد حسني 
CommitDate: Mon Jun 19 21:52:25 2023 +0200

embeddedfontshelper: use u16string_view instead of char pointer

Change-Id: I7a6088c570ebd0680cc1b2603b946192a19bef26
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/153268
Tested-by: Jenkins
Reviewed-by: خالد حسني 

diff --git a/include/vcl/embeddedfontshelper.hxx 
b/include/vcl/embeddedfontshelper.hxx
index 4802c13a2d8d..cbf91ee7f09b 100644
--- a/include/vcl/embeddedfontshelper.hxx
+++ b/include/vcl/embeddedfontshelper.hxx
@@ -65,7 +65,7 @@ public:
   @param eot whether the data is compressed in Embedded OpenType format
 */
 bool addEmbeddedFont( const css::uno::Reference< css::io::XInputStream >& 
stream,
-const OUString& fontName, const char* extra,
+const OUString& fontName, std::u16string_view extra,
 std::vector< unsigned char > const & key, bool eot = false);
 
 /**
@@ -76,7 +76,7 @@ public:
   @param fontName name of the font (e.g. 'Times New Roman')
   @param extra additional text to use for name (e.g. to distinguish 
regular from bold, italic,...), "?" for unique
 */
-static OUString fileUrlForTemporaryFont( const OUString& fontName, const 
char* extra );
+static OUString fileUrlForTemporaryFont( const OUString& fontName, 
std::u16string_view extra );
 
 /**
   Adds the accumulated fonts to the list of known fonts. The fonts are 
used only until application
diff --git a/include/xmloff/xmlimp.hxx b/include/xmloff/xmlimp.hxx
index 3287911f1112..fda180bb7837 100644
--- a/include/xmloff/xmlimp.hxx
+++ b/include/xmloff/xmlimp.hxx
@@ -582,7 +582,7 @@ public:
 
 // see EmbeddedFontsHelper::addEmbeddedFont
 bool addEmbeddedFont( const css::uno::Reference< css::io::XInputStream >& 
stream,
-const OUString& fontName, const char* extra,
+const OUString& fontName, std::u16string_view extra,
 std::vector< unsigned char > const & key, bool eot);
 
 virtual void NotifyContainsEmbeddedFont() {}
diff --git a/vcl/source/gdi/embeddedfontshelper.cxx 
b/vcl/source/gdi/embeddedfontshelper.cxx
index b5aa00aafebe..a8a4f7e983ba 100644
--- a/vcl/source/gdi/embeddedfontshelper.cxx
+++ b/vcl/source/gdi/embeddedfontshelper.cxx
@@ -66,7 +66,7 @@ void EmbeddedFontsHelper::clearTemporaryFontFiles()
 }
 
 bool EmbeddedFontsHelper::addEmbeddedFont( const uno::Reference< 
io::XInputStream >& stream, const OUString& fontName,
-const char* extra, std::vector< unsigned char > const & key, bool eot )
+std::u16string_view extra, std::vector< unsigned char > const & key, bool 
eot )
 {
 OUString fileUrl = EmbeddedFontsHelper::fileUrlForTemporaryFont( fontName, 
extra );
 osl::File file( fileUrl );
@@ -189,7 +189,7 @@ void EmbeddedFontsHelper::activateFonts()
 m_aAccumulatedFonts.clear();
 }
 
-OUString EmbeddedFontsHelper::fileUrlForTemporaryFont( const OUString& 
fontName, const char* extra )
+OUString EmbeddedFontsHelper::fileUrlForTemporaryFont( const OUString& 
fontName, std::u16string_view extra )
 {
 OUString path = "${$BRAND_BASE_DIR/" LIBO_ETC_FOLDER "/" SAL_CONFIGFILE( 
"bootstrap") "::UserInstallation}";
 rtl::Bootstrap::expandMacros( path );
@@ -197,10 +197,10 @@ OUString EmbeddedFontsHelper::fileUrlForTemporaryFont( 
const OUString& fontName,
 osl::Directory::createPath( path );
 OUString filename = fontName;
 static int uniqueCounter = 0;
-if( strcmp( extra, "?" ) == 0 )
+if( extra == u"?" )
 filename += OUString::number( uniqueCounter++ );
 else
-filename += OStringToOUString( extra, RTL_TEXTENCODING_ASCII_US );
+filename += extra;
 filename += ".ttf"; // TODO is it always ttf?
 return path + filename;
 }
diff --git a/writerfilter/source/dmapper/FontTable.cxx 
b/writerfilter/source/dmapper/FontTable.cxx
index d7c6b4fe3f5b..3ddebaedf419 100644
--- a/writerfilter/source/dmapper/FontTable.cxx
+++ b/writerfilter/source/dmapper/FontTable.cxx
@@ -119,10 +119,10 @@ void FontTable::lcl_sprm(Sprm& rSprm)
 if( pProperties )
 {
 EmbeddedFontHandler handler(*this, 
m_pImpl->pCurrentEntry->sFontName,
-nSprmId == NS_ooxml::LN_CT_Font_embedRegular ? ""
-: nSprmId == NS_ooxml::LN_CT_Font_embedBold ? "b"
-: nSprmId == NS_ooxml::LN_CT_Font_embedItalic ? "i"
-   

[Libreoffice-bugs] [Bug 155933] New: LibreOffice Writer doesn't save docx file format properly(saves a compressed archive file instead), when i try to save it to cloud storage

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

Bug ID: 155933
   Summary: LibreOffice Writer doesn't save docx file format
properly(saves a compressed archive file instead),
when i try to save it to cloud storage
   Product: LibreOffice
   Version: 7.5.1.2 release
  Hardware: x86-64 (AMD64)
OS: Linux (All)
Status: UNCONFIRMED
  Severity: normal
  Priority: medium
 Component: LibreOffice
  Assignee: libreoffice-bugs@lists.freedesktop.org
  Reporter: anil...@yaani.com

Description:
Hi, I'm using LibreOffice on a Debian based 64bit Linux workstation with GNOME
interface (distro called as "Pardus 21.5")
When i try to save my document as docx file to local/portable drive everything
works well. But when i try to save it to google drive by choosing the folder
via nautilius file explorer  it saves it as a compressed archive file.
It's impossible to open this file except using Libreoffice. But i don't
experience this fault on my Windows 11 installed workstation with the same
version of LibreOffice. I appreciate your help in advance.

Actual Results:
When i try to save my document as docx file to local/portable drive everything
works well. But when i try to save it to google drive by choosing the folder
via nautilius file explorer  it saves it as a compressed archive file.
It's impossible to open this file except using Libreoffice.

Expected Results:
In the given workstation above, LibreOffice Writer module should save my
document to cloud storage as docx file format without corrupting the file, so
that it can be readable by other word editor/viewer programs.


Reproducible: Always


User Profile Reset: No

Additional Info:
But i don't experience this fault on my Windows 11 installed workstation with
the same version of LibreOffice. I appreciate your help in advance.

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

[Libreoffice-bugs] [Bug 155920] IMPRESS: presentation doesn't end normally when displayed on two screens

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

dldld  changed:

   What|Removed |Added

   Assignee|libreoffice-b...@lists.free |daniel-...@web.de
   |desktop.org |
 Status|NEW |ASSIGNED

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

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

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

Xisco Faulí  changed:

   What|Removed |Added

 Depends on||155932


Referenced Bugs:

https://bugs.documentfoundation.org/show_bug.cgi?id=155932
[Bug 155932] SVG: g with clipPath doesn't work
-- 
You are receiving this mail because:
You are the assignee for the bug.

[Libreoffice-bugs] [Bug 155932] SVG: g with clipPath doesn't work

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

Xisco Faulí  changed:

   What|Removed |Added

 CC||xiscofa...@libreoffice.org
 Blocks||88278
   Keywords||bibisected, bisected,
   ||regression
   Assignee|libreoffice-b...@lists.free |xiscofa...@libreoffice.org
   |desktop.org |
 Status|UNCONFIRMED |ASSIGNED
 Ever confirmed|0   |1


Referenced Bugs:

https://bugs.documentfoundation.org/show_bug.cgi?id=88278
[Bug 88278] [META] SVG import image filter (all modules)
-- 
You are receiving this mail because:
You are the assignee for the bug.

[Libreoffice-bugs] [Bug 155932] New: SVG: g with clipPath doesn't work

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

Bug ID: 155932
   Summary: SVG: g with clipPath doesn't work
   Product: LibreOffice
   Version: 24.2.0.0 alpha0+ Master
  Hardware: All
OS: All
Status: UNCONFIRMED
  Severity: normal
  Priority: medium
 Component: filters and storage
  Assignee: libreoffice-bugs@lists.freedesktop.org
  Reporter: xiscofa...@libreoffice.org

Created attachment 188003
  --> https://bugs.documentfoundation.org/attachment.cgi?id=188003=edit
sample file

This is a regression from d47b37eea9779e3c354e6c19a7211a306965b7ef "tdf#97717:
do not call add_postProcess from g element" which arose another existing issue

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

[Libreoffice-ux-advise] [Bug 155893] Table cell baseline misalignment when using different fonts

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

--- Comment #14 from Eyal Rozenberg  ---
Created attachment 188002
  --> https://bugs.documentfoundation.org/attachment.cgi?id=188002=edit
Screenshot of behavior in MS Word 16

The behavior in MS Word 16 is similar to our current behavior, apparently.

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

[Libreoffice-bugs] [Bug 155893] Table cell baseline misalignment when using different fonts

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

--- Comment #14 from Eyal Rozenberg  ---
Created attachment 188002
  --> https://bugs.documentfoundation.org/attachment.cgi?id=188002=edit
Screenshot of behavior in MS Word 16

The behavior in MS Word 16 is similar to our current behavior, apparently.

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

[Libreoffice-ux-advise] [Bug 155893] Table cell baseline misalignment when using different fonts

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

Eyal Rozenberg  changed:

   What|Removed |Added

 Attachment #187979|Screenshot  |Screenshot of attachment
description||187957

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

  1   2   3   4   5   >