[Libreoffice-bugs] [Bug 152247] Automatic translation does not work with our own documentation guides

2022-11-27 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=152247

Aron Budea  changed:

   What|Removed |Added

 CC||aron.bu...@gmail.com

--- Comment #3 from Aron Budea  ---
(In reply to Jean-Baptiste Faure from comment #2)
> Did you configure API URL and Authentication key in Tools > Options >
> Language Settings > DeepL Server ?
A patch so the Translate entry in Options is only enabled if both config fields
are filled:
https://gerrit.libreoffice.org/c/core/+/143359

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

[Libreoffice-bugs] [Bug 151993] The decimal comma in table formulas always changes from comma to point, resulting broken formula in documents where document locale (language) has default decimal comma

2022-11-27 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=151993

NISZ LibreOffice Team  changed:

   What|Removed |Added

 Status|RESOLVED|VERIFIED

--- Comment #5 from NISZ LibreOffice Team  ---
Verified in:
Version: 7.5.0.0.alpha1+ (X86_64) / LibreOffice Community
Build ID: 5b18eebc2c95321ce7e6edf10f4df81557382a48
CPU threads: 4; OS: Windows 10.0 Build 19044; UI render: Skia/Vulkan; VCL: win
Locale: hu-HU (hu_HU); UI: en-US
Calc: CL threaded

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

[Libreoffice-bugs] [Bug 152253] macOS Dark Mode Calc: text in Input Box unreadable (black should be white)

2022-11-27 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=152253

Sierk Bornemann  changed:

   What|Removed |Added

 Ever confirmed|0   |1
 Status|UNCONFIRMED |NEW

--- Comment #2 from Sierk Bornemann  ---
I can confirm the issue in question.


Version: 7.5.0.0.alpha1+ (AARCH64) / LibreOffice Community
Build ID: e76b1faa3326e5cffed4472fcd410b5abf273067
CPU threads: 10; OS: Mac OS X 13.0.1; UI render: Skia/Metal; VCL: osx
Locale: de-DE (de_DE.UTF-8); UI: de-DE
Calc: threaded

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

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

2022-11-27 Thread Daniel Lohmann (via logerrit)
 slideshow/source/engine/pointersymbol.cxx |4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

New commits:
commit 54681a12b38db29b4d65e3c4f4c52a12436965d0
Author: Daniel Lohmann 
AuthorDate: Sun Nov 27 11:52:56 2022 +0100
Commit: Samuel Mehrbrodt 
CommitDate: Mon Nov 28 08:47:47 2022 +0100

Presenter screen wrong position of pointer

The pointer is drawn on the presenting screen and the presenter
console. In the presenter console the position of the pointer
is not matching the position on the slide or position in the impress
remote app. This fixed by this commit.

Change-Id: I5650f62304934d2acb558e32a8e9de78a9f0a12a
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/143341
Tested-by: Jenkins
Reviewed-by: Samuel Mehrbrodt 

diff --git a/slideshow/source/engine/pointersymbol.cxx 
b/slideshow/source/engine/pointersymbol.cxx
index 50f4421add5c..00832a4edf26 100644
--- a/slideshow/source/engine/pointersymbol.cxx
+++ b/slideshow/source/engine/pointersymbol.cxx
@@ -96,8 +96,8 @@ basegfx::B2DPoint 
PointerSymbol::calcSpritePos(UnoViewSharedPtr const & rView) c
 const geometry::IntegerSize2D realTranslationOffset ( 
rView->getTranslationOffset() );
 
 return basegfx::B2DPoint(
-realTranslationOffset.Width + ((aViewArea.Width - aViewArea.X) - 2 * 
realTranslationOffset.Width) * maPos.X,
-realTranslationOffset.Height + ((aViewArea.Height - aViewArea.Y) - 2 * 
realTranslationOffset.Height) * maPos.Y);
+realTranslationOffset.Width + (aViewArea.Width * maPos.X),
+realTranslationOffset.Height + (aViewArea.Height * maPos.Y));
 }
 
 void PointerSymbol::viewAdded( const UnoViewSharedPtr& rView )


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

2022-11-27 Thread Daniel Lohmann (via logerrit)
 slideshow/source/engine/slideshowimpl.cxx |8 ++--
 1 file changed, 6 insertions(+), 2 deletions(-)

New commits:
commit 176f77607ed1001efca402d1807e12b93d914847
Author: Daniel Lohmann 
AuthorDate: Sun Nov 27 11:45:48 2022 +0100
Commit: Samuel Mehrbrodt 
CommitDate: Mon Nov 28 08:46:52 2022 +0100

Do not draw pointer on paused mode screen

If the pointer is drawn on the paused mode screen, around the pointer
the slide will be visible. Everywhere where the pointer was will the
slide is visible. Preventing to draw the pointer in the paused mode will
fix this issue.

Change-Id: Ica8fedca5710adfc79ed78a30485bd755e3b3b31
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/143340
Tested-by: Jenkins
Reviewed-by: Samuel Mehrbrodt 

diff --git a/slideshow/source/engine/slideshowimpl.cxx 
b/slideshow/source/engine/slideshowimpl.cxx
index 1cbc167a4c4d..264a4dee8217 100644
--- a/slideshow/source/engine/slideshowimpl.cxx
+++ b/slideshow/source/engine/slideshowimpl.cxx
@@ -1750,7 +1750,9 @@ sal_Bool SlideShowImpl::setProperty( beans::PropertyValue 
const& rProperty )
 if (!(rProperty.Value >>= visible))
 return false;
 
-mpPointerSymbol->setVisible(visible);
+if (!mbShowPaused)
+mpPointerSymbol->setVisible(visible);
+
 return true;
 }
 
@@ -1760,7 +1762,9 @@ sal_Bool SlideShowImpl::setProperty( beans::PropertyValue 
const& rProperty )
 if (! (rProperty.Value >>= pos))
 return false;
 
-mpPointerSymbol->viewsChanged(pos);
+if (!mbShowPaused)
+mpPointerSymbol->viewsChanged(pos);
+
 return true;
 }
 


[Libreoffice-bugs] [Bug 104597] RTL script text runs are reversed on PDF import, PDFIProcessor::mirrorString misbehaving

2022-11-27 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=104597

--- Comment #103 from Kevin Suo  ---
(In reply to Hanan Sela from comment #102)
Could you explain what is the problem in this Hebrew pdf file when open with
Draw? I tested and most of the text are shown correctly with current master
build as of Sat Nov 26 00:27:23 2022 +0300. Also, when testing please make sure
you have the correct fonts installed on your linux system (e.g. this pdf file
uses Arial font in the text مكتب on the header section so you should at least
have Arial font instaled).

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

[Libreoffice-bugs] [Bug 152256] CHAPTER NUMBERING DIALOG: Add additional option in numbering sublevels

2022-11-27 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=152256

--- Comment #2 from Dieter  ---
Additional remark: If it is also a question of campatibility, LO should provide
this function.

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

[Libreoffice-ux-advise] [Bug 152256] CHAPTER NUMBERING DIALOG: Add additional option in numbering sublevels

2022-11-27 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=152256

--- Comment #2 from Dieter  ---
Additional remark: If it is also a question of campatibility, LO should provide
this function.

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

[Libreoffice-bugs] [Bug 152256] CHAPTER NUMBERING DIALOG: Add additional option in numbering sublevels

2022-11-27 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=152256

Dieter  changed:

   What|Removed |Added

 Blocks||115121
   Keywords||needsUXEval
 CC||dgp-m...@gmx.de,
   ||libreoffice-ux-advise@lists
   ||.freedesktop.org
Summary|please add more function in |CHAPTER NUMBERING DIALOG:
   |numbering   |Add additional option in
   ||numbering sublevels

--- Comment #1 from Dieter  ---
Ali, thank you for enhancement request. I must admit, I've never seen a chapter
numbering like that and it looks wrong to me. But I believe you, that it is not
unusual in Indonesia.

Perhaps we could solve the problem with additional option in chapter numbering
dialog. But let's ask and decide design team

cc: Design-Team for further input and decision


Referenced Bugs:

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

[Libreoffice-ux-advise] [Bug 152256] CHAPTER NUMBERING DIALOG: Add additional option in numbering sublevels

2022-11-27 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=152256

Dieter  changed:

   What|Removed |Added

 Blocks||115121
   Keywords||needsUXEval
 CC||dgp-m...@gmx.de,
   ||libreoffice-ux-advise@lists
   ||.freedesktop.org
Summary|please add more function in |CHAPTER NUMBERING DIALOG:
   |numbering   |Add additional option in
   ||numbering sublevels

--- Comment #1 from Dieter  ---
Ali, thank you for enhancement request. I must admit, I've never seen a chapter
numbering like that and it looks wrong to me. But I believe you, that it is not
unusual in Indonesia.

Perhaps we could solve the problem with additional option in chapter numbering
dialog. But let's ask and decide design team

cc: Design-Team for further input and decision


Referenced Bugs:

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

[Libreoffice-bugs] [Bug 115121] [META] Chapter numbering dialog bugs and enhancements

2022-11-27 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=115121

Dieter  changed:

   What|Removed |Added

 Depends on||152256


Referenced Bugs:

https://bugs.documentfoundation.org/show_bug.cgi?id=152256
[Bug 152256] CHAPTER NUMBERING DIALOG: Add additional option in numbering
sublevels
-- 
You are receiving this mail because:
You are the assignee for the bug.

[Libreoffice-bugs] [Bug 151758] Teg w:ins & w:del

2022-11-27 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=151758

--- Comment #23 from Dieter  ---
Thank you for the test file, but I can't confirm your problem with

Version: 7.4.3.2 (x64) / LibreOffice Community
Build ID: 1048a8393ae2eeec98dff31b5c133c5f1d08b890
CPU threads: 4; OS: Windows 10.0 Build 19045; UI render: Skia/Raster; VCL: win
Locale: de-DE (de_DE); UI: en-GB
Calc: CL

Steps
1. Open attachment 183537
2. Show track changes
3. Scroll until end of document.
4. Hide track changes -> Canvas jumps to beginning of document
5. Delete, add and delete some text in some random selected table cells
6. Save document (docx-file) and close LibreOffice
7. Open document

Actual and expected result: No error message

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

[Libreoffice-bugs] [Bug 152259] New: Clear (and correct) syntax of address is needed on "Addresses and References, Absolute and Relative"

2022-11-27 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=152259

Bug ID: 152259
   Summary: Clear (and correct) syntax of address is needed on
"Addresses and References, Absolute and Relative"
   Product: LibreOffice
   Version: unspecified
  Hardware: All
OS: All
Status: UNCONFIRMED
  Severity: normal
  Priority: medium
 Component: Documentation
  Assignee: libreoffice-bugs@lists.freedesktop.org
  Reporter: mikekagan...@hotmail.com
CC: er...@redhat.com, olivier.hal...@libreoffice.org

The "Addresses and References, Absolute and Relative" help page [1] should
start with a section that would represent the full syntax of a cell address.

Some words about that are present on a neighbor page "Referencing Other Sheets"
[2]:

> The reference to a cell of another document contains the name of the other
> document in single inverted commas, then a hash #, then the name of the sheet
> of the other document, followed by a point and the name of the cell.

The problems here are:

1. The "Referencing Other Sheets" is not shows in search "address";
2. The sheet piece of the address is a part of absolute/relative addressing,
when cuboids are considered (you may reference sheets both absolutely
("specifically sheet named X") and relatively ("next/previous sheet")).
3. The information on the "Referencing Other Sheets" is not emphasized in any
way, so one needs to read carefully to find out that the syntax (telling about
order of components) is explained in plain words in one of the paragraphs of a
numbered list in the middle;
4. The information there is even wrong (what is "inverted commas"? the plain
ASCII apostrophes (U+0027) are used, not any other fancy Unicode symbols);
5. It doesn't discuss what to do when sheet names have spaces or other special
characters.

All that information is best presented on the *introductory* page of the
"References" section of the Calc help; and that introductory page is "Addresses
and References, Absolute and Relative". The name fits it all; and if it started
with a dedicated section, presenting a formal definition of the syntax, with a
legend assigning names, and showing some variations like full rows/columns, as
in A:A or 3:4, with the textual discussion that follows, it would be best and
most correct.

[1]
https://help.libreoffice.org/7.4/en-US/text/scalc/guide/relativ_absolut_ref.html?=CALC
[2]
https://help.libreoffice.org/7.4/en-US/text/scalc/guide/cellreferences.html?DbPAR=CALC

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

Re: Release Notes for LibreOffice 7.5 and new functionalities

2022-11-27 Thread Stéphane Guillou

Hi all

I will work today on updating release notes and tagging corresponding 
enhancement requests in Bugzilla with the whiteboard value 
"inReleaseNotes:*", but as Jean-Baptiste said, if there is no bug report 
linked to the new feature, it will easily pass under our radar. Good 
testing before RC does depend on those release notes a fair bit.


Thank you all!

On 27/11/22 15:32, Olivier Hallot wrote:



Em 27/11/2022 10:15, Ilmari Lauhakangas escreveu:

On 27.11.2022 11.40, Jean-Baptiste Faure wrote:

Hi developers,

It is easier for QA team to test new functionalities if you make 
them knowlegeable, for example if you describe them in the Release 
Notes.
Yesterday I discovered a new entry "Translate" in the Tools menu of 
Writer. It is a new functionality that has been recently 
(2022-10-12) added in Writer : automatic translation using DeepL. 
Commit is this one : 
https://git.libreoffice.org/core/+/e20d2de7836da52dbf9e528d1043b1e188097bfd


It was difficult to find some information about this new 
functionality, because there is no entry in the Release Notes, no 
bug report in Bugzilla and no blog post. It's a pity because this 
functionality is very useful, but need some love. It does not work 
well with our own LibreOffice guides, for example with the preface 
of the 7.3 guide : 
https://wiki.documentfoundation.org/images/9/98/GS7300-Preface.odt


I filed this bug report: 
https://bugs.documentfoundation.org/show_bug.cgi?id=152247

"Automatic translation does not work with our own documentation guides"


The help pages related to Tools menu should also be updated as well 
as a page added describing this new functionality.


Ilmari


And a documentation bug entry for new features will also be 
appreciated. It helps us to keep our records.


Some changes in features (just one line in the RN, with terse 
contents, corner cases, no images) are missing in our Help pages and 
Guides too.



--
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 104597] RTL script text runs are reversed on PDF import, PDFIProcessor::mirrorString misbehaving

2022-11-27 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=104597

--- Comment #102 from Hanan Sela  ---
Created attachment 183844
  --> https://bugs.documentfoundation.org/attachment.cgi?id=183844=edit
screen shot of Hebrew pdf file

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

[Libreoffice-bugs] [Bug 104597] RTL script text runs are reversed on PDF import, PDFIProcessor::mirrorString misbehaving

2022-11-27 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=104597

--- Comment #101 from Hanan Sela  ---
Created attachment 183843
  --> https://bugs.documentfoundation.org/attachment.cgi?id=183843=edit
Hebrew PDF file

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

[Libreoffice-bugs] [Bug 152223] 7.4.3.2 Calc has a problem, some keys need [Alt] in quit dialog box.

2022-11-27 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=152223

--- Comment #3 from Wally  ---
I've found another problem where I need the ALT key.  I open Calc to an empty
screen.  I used to be able to just press the "O" key to open my list of files. 
I now have to use ALT+O.  I have to use the ALT key with the other options in
the list such as ALT+W for Writer, etc.
Note, also, I can make an option work by using the Tab key to highlight it,
although I have not used this function very much in the past.
Regards

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

[Libreoffice-bugs] [Bug 113789] ActiveX button's icon is not saved back to DOCX file

2022-11-27 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=113789

Hossein  changed:

   What|Removed |Added

   Keywords||needsDevEval

--- Comment #20 from Hossein  ---
The problem is still reproducible with LO 7.4:

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

Also reproducible with the latest LO 7.5 dev master:

Version: 7.5.0.0.alpha1+ (X86_64) / LibreOffice Community
Build ID: 360b5861fb46353e7a6b9f5abf13339cd719a8df
CPU threads: 8; OS: Linux 5.15; UI render: default; VCL: gtk3
Locale: en-US (en_US.UTF-8); UI: en-US
Calc: threaded

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

[Libreoffice-bugs] [Bug 151842] Font size is lost after reloading any formula (OLE object and standalone document)

2022-11-27 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=151842

Mike Kaganski  changed:

   What|Removed |Added

Summary|Font size is lost after |Font size is lost after
   |reloading the formula   |reloading any formula (OLE
   |document|object and standalone
   ||document)

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

[Libreoffice-commits] core.git: g

2022-11-27 Thread Mike Kaganski (via logerrit)
 g |   17 ++---
 1 file changed, 10 insertions(+), 7 deletions(-)

New commits:
commit 1fd42472e2b1a2169d56e62ef11aa7ee1f7815e7
Author: Mike Kaganski 
AuthorDate: Mon Nov 28 00:38:30 2022 +0300
Commit: Mike Kaganski 
CommitDate: Mon Nov 28 05:18:12 2022 +0100

Avoid refreshing all hooks in secondary worktrees

This avoids "ln: failed to access '.git/hooks/foo': Not a directory"
console noise. The primary worktree's hooks are used in secondary
worktrees anyway.

Possibly using 'git rev-parse --git-dir', and putting hooks there
would be a better fix? No idea.

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

diff --git a/g b/g
index fdf95c8278ce..b018561c6775 100755
--- a/g
+++ b/g
@@ -91,13 +91,16 @@ refresh_all_hooks()
 local hook
 
 pushd "${COREDIR?}" > /dev/null
-for hook_name in "${COREDIR?}/.git-hooks"/* ; do
-hook=".git/hooks/${hook_name##*/}"
-if [ ! -e "${hook?}" ] || [ -L "${hook?}" ] ; then
-rm -f "${hook?}"
-ln -sf "${hook_name}" "${hook?}"
-fi
-done
+# There's no ".git" e.g. in a secondary worktree
+if [ -d ".git" ]; then
+for hook_name in "${COREDIR?}/.git-hooks"/* ; do
+hook=".git/hooks/${hook_name##*/}"
+if [ ! -e "${hook?}" ] || [ -L "${hook?}" ] ; then
+rm -f "${hook?}"
+ln -sf "${hook_name}" "${hook?}"
+fi
+done
+fi
 
 for repo in ${SUBMODULES_ALL?} ; do
 refresh_submodule_hooks "$repo"


[Libreoffice-bugs] [Bug 152258] Hebrew in PDF files is presented backward when opened with Draw

2022-11-27 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=152258

--- Comment #2 from V Stuart Foote  ---
Mostly fixed at 7.4.3 release, with further improvements at 7.4.4 and for
master against a 7.5 release.

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

[Libreoffice-bugs] [Bug 104597] RTL script text runs are reversed on PDF import, PDFIProcessor::mirrorString misbehaving

2022-11-27 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=104597

V Stuart Foote  changed:

   What|Removed |Added

 CC||baruch.bern...@gmail.com

--- Comment #100 from V Stuart Foote  ---
*** Bug 152258 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 152258] Hebrew in PDF files is presented backward when opened with Draw

2022-11-27 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=152258

V Stuart Foote  changed:

   What|Removed |Added

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

--- Comment #1 from V Stuart Foote  ---


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

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

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

2022-11-27 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=113195
Bug 113195 depends on bug 149534, which changed state.

Bug 149534 Summary: Japanese character spacing does not work correctly when 
grid is enabled
https://bugs.documentfoundation.org/show_bug.cgi?id=149534

   What|Removed |Added

 Status|NEEDINFO|RESOLVED
 Resolution|--- |NOTABUG

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

[Libreoffice-bugs] [Bug 106568] [META] Text Grid Issues

2022-11-27 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=106568
Bug 106568 depends on bug 149534, which changed state.

Bug 149534 Summary: Japanese character spacing does not work correctly when 
grid is enabled
https://bugs.documentfoundation.org/show_bug.cgi?id=149534

   What|Removed |Added

 Status|NEEDINFO|RESOLVED
 Resolution|--- |NOTABUG

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

[Libreoffice-bugs] [Bug 149534] Japanese character spacing does not work correctly when grid is enabled

2022-11-27 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=149534

nnn1590+libreoff...@nnn1590.org changed:

   What|Removed |Added

 Resolution|--- |NOTABUG
 Status|NEEDINFO|RESOLVED

--- Comment #8 from nnn1590+libreoff...@nnn1590.org ---
Oh, I didn't know that.
I disabled "Snap to text grid (if active)" and the result is what I expected!
Thank you very much!

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

[Libreoffice-bugs] [Bug 151842] Font size is lost after reloading the formula document

2022-11-27 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=151842

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 151508] Not possible to add words to dictionary from context menu with LanguageTool installed

2022-11-27 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=151508

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 149872] Sidebar properties switch from what we're manipulating to the page's properties after merging two shapes

2022-11-27 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=149872

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 145563] LibreOffice and NeoOffice fail to respect each other's selections of Pfeffer Mediaeval due to a ligature in the name

2022-11-27 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=145563

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 137636] Toolbar buttons for Line and Fill Color do not work on the placeholder text boxes

2022-11-27 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=137636

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

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

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

If you have time, please do the following:

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

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

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

Please DO NOT

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


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

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


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

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

Warm Regards,
QA Team

MassPing-UntouchedBug

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

[Libreoffice-bugs] [Bug 132637] Fileopen: DOC with Lock Tracking (Protect changes) does not use password to prevent disabling track changes

2022-11-27 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=132637

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

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

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

If you have time, please do the following:

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

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

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

Please DO NOT

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


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

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


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

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

Warm Regards,
QA Team

MassPing-UntouchedBug

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

[Libreoffice-bugs] [Bug 119811] LibreOffice 6.0.6 spies on my Firefox keychain when opening MS documents

2022-11-27 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=119811

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

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 114044] Wrong copying formatting of text from heading table with one table style to heading table with another table style

2022-11-27 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=114044

--- Comment #5 from QA Administrators  ---
Dear Roman Kuznetsov,

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 112594] Mongolian letters failed to join with NNBSP sometimes

2022-11-27 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=112594

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

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 152258] New: Hebrew in PDF files is presented backward when opened with Draw

2022-11-27 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=152258

Bug ID: 152258
   Summary: Hebrew in PDF files is presented backward when opened
with Draw
   Product: LibreOffice
   Version: 7.3.7.2 release
  Hardware: All
OS: Linux (All)
Status: UNCONFIRMED
  Severity: normal
  Priority: medium
 Component: LibreOffice
  Assignee: libreoffice-bugs@lists.freedesktop.org
  Reporter: baruch.bern...@gmail.com

Description:
When PDF with hebrew every word is presented in the wrong letter order. example
in English will be if Car will be presented as raC
Hebrew is written from right to left (like Arabic) so instead of מכונית (car)
it will show as תינוכמ. 

Actual Results:
1-open with Draw PDF with hebrew words as text (not image). That is the
document I
opened-https://www.gov.il/BlobFolder/service/application_for_biometric_passport2/en/Request_passport_biometric_pass_October_2017.pdf



Expected Results:
Word written correctly.


Reproducible: Always


User Profile Reset: No

Additional Info:
N/A

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

[Libreoffice-bugs] [Bug 152246] Wrong horizontal position for the RTL content control fields in the exported PDF file

2022-11-27 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=152246

--- Comment #2 from Hossein  ---
Created attachment 183842
  --> https://bugs.documentfoundation.org/attachment.cgi?id=183842=edit
Wrong hotizontal position of the fields visible in the PDF file opened in
Firefox

This is a screenshot of the bad positioning of the fields in the PDF file,
visible when opened in Firefox. It is worth mentioning that even the positions
of the fields in the last line that seem to be OK are wrong. That is because
the place of month / year is reversed, suggesting that the calculation of the
positions should be somehow reversed for RTL.

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

[Libreoffice-bugs] [Bug 152257] Crash: Selecting an option in dropdown content control leads to unexpected exit with code 139

2022-11-27 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=152257

Hossein  changed:

   What|Removed |Added

Version|7.4.0.3 release |7.5.0.0 alpha0+ Master
 OS|All |Linux (All)

--- Comment #2 from Hossein  ---
The problem seems to be GTK specific. I could not reproduce it with X11, or on
Windows:

Not reproducible with X11 gen UI:

Version: 7.5.0.0.alpha1+ (X86_64) / LibreOffice Community
Build ID: cb7e6003ad06d71a27baeb435366b91f87bdeb2f
CPU threads: 8; OS: Linux 5.15; UI render: default; VCL: x11
Locale: en-US (en_US.UTF-8); UI: en-US
Calc: threaded

Also not reproducible on Windows:

Version: 7.5.0.0.alpha1+ (X86_64) / LibreOffice Community
Build ID: 360b5861fb46353e7a6b9f5abf13339cd719a8df
CPU threads: 32; OS: Windows 10.0 Build 19044; UI render: Skia/Raster; VCL: win
Locale: en-US (en_DE); UI: en-US
Calc: threaded

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

[Libreoffice-bugs] [Bug 152257] Crash: Selecting an option in dropdown content control leads to unexpected exit with code 139

2022-11-27 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=152257

Hossein  changed:

   What|Removed |Added

Summary|Crash: Selecting text in|Crash: Selecting an option
   |dropdown content control|in dropdown content control
   |sometimes lead to   |leads to unexpected exit
   |unexpected exit with code   |with code 139
   |139 |

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

[Libreoffice-bugs] [Bug 133092] [META] Crash bugs

2022-11-27 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=133092

Hossein  changed:

   What|Removed |Added

 Depends on||152257


Referenced Bugs:

https://bugs.documentfoundation.org/show_bug.cgi?id=152257
[Bug 152257] Crash: Selecting text in dropdown content control sometimes lead
to unexpected exit with code 139
-- 
You are receiving this mail because:
You are the assignee for the bug.

[Libreoffice-bugs] [Bug 152257] Crash: Selecting text in dropdown content control sometimes lead to unexpected exit with code 139

2022-11-27 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=152257

Hossein  changed:

   What|Removed |Added

 CC||hoss...@libreoffice.org,
   ||vmik...@collabora.com
 Blocks||107742, 133092
   Keywords||haveBacktrace


Referenced Bugs:

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

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

2022-11-27 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=107742

Hossein  changed:

   What|Removed |Added

 Depends on||152257


Referenced Bugs:

https://bugs.documentfoundation.org/show_bug.cgi?id=152257
[Bug 152257] Crash: Selecting text in dropdown content control sometimes lead
to unexpected exit with code 139
-- 
You are receiving this mail because:
You are the assignee for the bug.

[Libreoffice-bugs] [Bug 152257] Crash: Selecting text in dropdown content control sometimes lead to unexpected exit with code 139

2022-11-27 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=152257

--- Comment #1 from Hossein  ---
The last part should be: (a typo in replacing path)

Thread 1 "soffice.bin" received signal SIGSEGV, Segmentation fault.
0x7fffb0a6c3a8 in SwDropDownContentControlButton::LaunchPopup
(this=0x5d0499e0) at
sw/source/core/crsr/dropdowncontentcontrolbutton.cxx:83
83  m_xTreeView = m_xPopupBuilder->weld_tree_view("list");
#0  0x7fffb0a6c3a8 in SwDropDownContentControlButton::LaunchPopup()
(this=0x5d0499e0) at
sw/source/core/crsr/dropdowncontentcontrolbutton.cxx:83
#1  0x7fffb0a1f1cf in SwContentControlButton::StartPopup()
(this=0x5d0499e0) at sw/source/core/crsr/contentcontrolbutton.cxx:91
#2  0x7fffb0a1f1a2 in SwContentControlButton::MouseButtonDown(MouseEvent
const&) (this=0x5d0499e0) at
sw/source/core/crsr/contentcontrolbutton.cxx:87
#3  0x7fffeec3ba1b in ImplHandleMouseEvent(VclPtr const&,
NotifyEventType, bool, long, long, unsigned long, unsigned short,
MouseEventModifiers) (xWindow=..., nSVEvent=NotifyEventType::MOUSEBUTTONDOWN,
bMouseLeave=false, nX=671, nY=403, nMsgTime=28221840, nCode=1,
nMode=(MouseEventModifiers::SIMPLECLICK | MouseEventModifiers::SELECT)) at
vcl/source/window/winproc.cxx:707
#4  0x7fffeec425a5 in ImplHandleSalMouseButtonDown(vcl::Window*,
SalMouseEvent const*) (pWindow=0x572ebc20, pEvent=0x7fffc740) at
vcl/source/window/winproc.cxx:2340
#5  0x7fffeec43853 in ImplWindowFrameProc(vcl::Window*, SalEvent, void
const*) (_pWindow=0x572ebc20, nEvent=SalEvent::MouseButtonDown,
pEvent=0x7fffc740) at vcl/source/window/winproc.cxx:2691
#6  0x7fffe4a01f84 in SalFrame::CallCallback(SalEvent, void const*) const
(this=0x5679b150, nEvent=SalEvent::MouseButtonDown, pEvent=0x7fffc740)
at vcl/inc/salframe.hxx:306
#7  0x7fffe4a01106 in GtkSalFrame::CallCallbackExc(SalEvent, void const*)
const (this=0x5679b150, nEvent=SalEvent::MouseButtonDown,
pEvent=0x7fffc740) at vcl/unx/gtk3/gtkframe.cxx:6138
#8  0x7fffe49f9a20 in GtkSalFrame::DrawingAreaButton(SalEvent, int, int,
int, unsigned int, unsigned int) (this=0x5679b150,
nEventType=SalEvent::MouseButtonDown, nEventX=671, nEventY=403, nButton=1,
nTime=28221840, nState=16) at vcl/unx/gtk3/gtkframe.cxx:3127
#9  0x7fffe49f9da8 in GtkSalFrame::signalButton(_GtkWidget*,
_GdkEventButton*, void*) (pEvent=0x5e98b970, frame=0x5679b150) at
vcl/unx/gtk3/gtkframe.cxx:3214

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

[Libreoffice-bugs] [Bug 152257] New: Crash: Selecting text in dropdown content control sometimes lead to unexpected exit with code 139

2022-11-27 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=152257

Bug ID: 152257
   Summary: Crash: Selecting text in dropdown content control
sometimes lead to unexpected exit with code 139
   Product: LibreOffice
   Version: 7.4.0.3 release
  Hardware: All
OS: All
Status: UNCONFIRMED
  Severity: normal
  Priority: medium
 Component: Writer
  Assignee: libreoffice-bugs@lists.freedesktop.org
  Reporter: hoss...@libreoffice.org

Created attachment 183841
  --> https://bugs.documentfoundation.org/attachment.cgi?id=183841=edit
Backtrace using gdb

Description:
Selecting placeholder text in dropdown content control sometimes lead to
unexpected closing of the LibreOffice, and the exit code is 139. Backtrace
shows that this is a crash: "received signal SIGSEGV, Segmentation fault".

Steps to Reproduce:
1. Open attachment 182846 from tdf#151364
2. In page 1, click the first dropdown content control
3. Select an option by alt+down keyboard shortcut key
4. Wait for a while, for example > 10 minutes
5. Select some option from the some dropdown content control

Actual Results:
LibreOffice exits with exit code 139

Expected Results:
No exit

Reproducible: Always, one needs to wait a few minutes


User Profile Reset: No


Additional Info:
Version: 7.5.0.0.alpha1+ (X86_64) / LibreOffice Community
Build ID: cb7e6003ad06d71a27baeb435366b91f87bdeb2f
CPU threads: 8; OS: Linux 5.15; UI render: default; VCL: gtk3
Locale: en-US (en_US.UTF-8); UI: en-US
Calc: threaded

This is the example output:
$ instdir/program/soffice
warn:oox:52395:52395:oox/source/drawingml/shapecontext.cxx:127:
ShapeContext::onCreateContext: unhandled element: 4004
warn:oox:52395:52395:oox/source/drawingml/shapecontext.cxx:127:
ShapeContext::onCreateContext: unhandled element: 4004
warn:oox:52395:52395:oox/source/drawingml/shapecontext.cxx:127:
ShapeContext::onCreateContext: unhandled element: 4004
warn:oox:52395:52395:oox/source/drawingml/shapecontext.cxx:127:
ShapeContext::onCreateContext: unhandled element: 4004
warn:oox:52395:52395:oox/source/drawingml/shapecontext.cxx:127:
ShapeContext::onCreateContext: unhandled element: 4004
warn:sw.uno:52395:52395:sw/source/core/unocore/unotext.cxx:2315: Exception when
setting property: HorizontalBorder com.sun.star.lang.IllegalArgumentException
message: "at
/home/hossein/Projects/libreoffice/core/sw/source/core/unocore/unotbl.cxx:2479"
ArgumentPosition: 0
warn:sw.uno:52395:52395:sw/source/core/unocore/unotext.cxx:2315: Exception when
setting property: VerticalBorder com.sun.star.lang.IllegalArgumentException
message: "at
/home/hossein/Projects/libreoffice/core/sw/source/core/unocore/unotbl.cxx:2479"
ArgumentPosition: 0
warn:sw.uno:52395:52395:sw/source/core/unocore/unotext.cxx:2315: Exception when
setting property: BottomBorder com.sun.star.lang.IllegalArgumentException
message: "at
/home/hossein/Projects/libreoffice/core/sw/source/core/unocore/unotbl.cxx:2479"
ArgumentPosition: 0
warn:sw.uno:52395:52395:sw/source/core/unocore/unotext.cxx:2315: Exception when
setting property: CharAutoKerning com.sun.star.lang.IllegalArgumentException
message: "at
/home/hossein/Projects/libreoffice/core/sw/source/core/unocore/unotbl.cxx:2479"
ArgumentPosition: 0
warn:sw.uno:52395:52395:sw/source/core/unocore/unotext.cxx:2315: Exception when
setting property: CharFontName com.sun.star.lang.IllegalArgumentException
message: "at
/home/hossein/Projects/libreoffice/core/sw/source/core/unocore/unotbl.cxx:2479"
ArgumentPosition: 0
warn:sw.uno:52395:52395:sw/source/core/unocore/unotext.cxx:2315: Exception when
setting property: CharFontNameAsian com.sun.star.lang.IllegalArgumentException
message: "at
/home/hossein/Projects/libreoffice/core/sw/source/core/unocore/unotbl.cxx:2479"
ArgumentPosition: 0
warn:sw.uno:52395:52395:sw/source/core/unocore/unotext.cxx:2315: Exception when
setting property: CharFontNameComplex
com.sun.star.lang.IllegalArgumentException message: "at
/home/hossein/Projects/libreoffice/core/sw/source/core/unocore/unotbl.cxx:2479"
ArgumentPosition: 0
warn:sw.uno:52395:52395:sw/source/core/unocore/unotext.cxx:2315: Exception when
setting property: CharHeight com.sun.star.lang.IllegalArgumentException
message: "at
/home/hossein/Projects/libreoffice/core/sw/source/core/unocore/unotbl.cxx:2479"
ArgumentPosition: 0
warn:sw.uno:52395:52395:sw/source/core/unocore/unotext.cxx:2315: Exception when
setting property: CharHeightAsian com.sun.star.lang.IllegalArgumentException
message: "at
/home/hossein/Projects/libreoffice/core/sw/source/core/unocore/unotbl.cxx:2479"
ArgumentPosition: 0
warn:sw.uno:52395:52395:sw/source/core/unocore/unotext.cxx:2315: Exception when
setting property: CharHeightComplex com.sun.star.lang.IllegalArgumentException
message: "at
/home/hossein/Projects/libreoffice/core/sw/source/core/unocore/unotbl.cxx:2479"
ArgumentPosition: 0

[Libreoffice-bugs] [Bug 152029] Visually draw attention to in-view bookmark when selecting/hovering it in the Navigator

2022-11-27 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=152029

V Stuart Foote  changed:

   What|Removed |Added

 CC||vsfo...@libreoffice.org

--- Comment #7 from V Stuart Foote  ---
(In reply to Jim Raykowski from comment #4)
> Here is a patch that does the bookmark part of this request:
> https://gerrit.libreoffice.org/c/core/+/143357
> 
> Basically it creates a selection over a bookmark's start and end position if
> the start position of the bookmark is in the visible view. Bookmarks having
> the same start and end position are selected as the start position + 1
> character.

So requires cursor movement through the SB Navigator in 'Bookmarks' mode,
highlighting but not selecting the bookmark as visible on canvas.  Assume an
actual click selection on any bookmark in SB would reposition the document
viewport to that bookmark dropping any active cursor selection.

So not clear we've got exactly the ask, of a visual indication of each of the
bookmarks visible in the viewport activating its object on the Navigator
Bookmarks mode. 

But if that is too much, maybe an addition/alternative. Could we more simply
flash visible all the bookmarks the current view port, both the document canvas
and the SB? 

The change to field shading color (bug 144677) from NPC makes the bookmark on
canvas (bug 45589)  a bit hard to spot--the flash of highlight all of them in
view might be useful.

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

[Libreoffice-ux-advise] [Bug 152029] Visually draw attention to in-view bookmark when selecting/hovering it in the Navigator

2022-11-27 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=152029

V Stuart Foote  changed:

   What|Removed |Added

 CC||vsfo...@libreoffice.org

--- Comment #7 from V Stuart Foote  ---
(In reply to Jim Raykowski from comment #4)
> Here is a patch that does the bookmark part of this request:
> https://gerrit.libreoffice.org/c/core/+/143357
> 
> Basically it creates a selection over a bookmark's start and end position if
> the start position of the bookmark is in the visible view. Bookmarks having
> the same start and end position are selected as the start position + 1
> character.

So requires cursor movement through the SB Navigator in 'Bookmarks' mode,
highlighting but not selecting the bookmark as visible on canvas.  Assume an
actual click selection on any bookmark in SB would reposition the document
viewport to that bookmark dropping any active cursor selection.

So not clear we've got exactly the ask, of a visual indication of each of the
bookmarks visible in the viewport activating its object on the Navigator
Bookmarks mode. 

But if that is too much, maybe an addition/alternative. Could we more simply
flash visible all the bookmarks the current view port, both the document canvas
and the SB? 

The change to field shading color (bug 144677) from NPC makes the bookmark on
canvas (bug 45589)  a bit hard to spot--the flash of highlight all of them in
view might be useful.

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

[Libreoffice-bugs] [Bug 92924] Export to PDF loses transparency

2022-11-27 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=92924

Rajasekaran Karunanithi  changed:

   What|Removed |Added

 CC||rajasekara...@gmail.com

--- Comment #22 from Rajasekaran Karunanithi  ---
Still reproducable in LO 7.4.3.2  under Windows 10(x64).

Version: 7.4.3.2 (x64) / LibreOffice Community
Build ID: 1048a8393ae2eeec98dff31b5c133c5f1d08b890
CPU threads: 4; OS: Windows 10.0 Build 19044; UI render: Skia/Raster; VCL: win
Locale: ta-IN (en_IN); UI: en-US
Calc: threaded

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

[Libreoffice-bugs] [Bug 151756] Menu text almost invisible in Windows 10 dark mode (after sleep or when display connected) (see comment 9)

2022-11-27 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=151756

--- Comment #21 from tor...@yahoo.com ---
Created attachment 183840
  --> https://bugs.documentfoundation.org/attachment.cgi?id=183840=edit
tabStops in DarkMode

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

[Libreoffice-bugs] [Bug 151756] Menu text almost invisible in Windows 10 dark mode (after sleep or when display connected) (see comment 9)

2022-11-27 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=151756

--- Comment #20 from tor...@yahoo.com ---
Created attachment 183839
  --> https://bugs.documentfoundation.org/attachment.cgi?id=183839=edit
tabStops in LightMode

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

[Libreoffice-bugs] [Bug 151756] Menu text almost invisible in Windows 10 dark mode (after sleep or when display connected) (see comment 9)

2022-11-27 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=151756

--- Comment #19 from tor...@yahoo.com ---
(In reply to V Stuart Foote from comment #1)
> Please enable "Experimental features" and retest.  The checkbox Tools ->
> Options -> Advanced panel, and restart.

Great! Thank you.
Except that tabStops are almost invisible in DarkMode —2 screenshots

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

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

2022-11-27 Thread Caolán McNamara (via logerrit)
 sw/uiconfig/swriter/ui/autotext.ui |  267 ++---
 1 file changed, 132 insertions(+), 135 deletions(-)

New commits:
commit 360b5861fb46353e7a6b9f5abf13339cd719a8df
Author: Caolán McNamara 
AuthorDate: Sun Nov 27 21:16:38 2022 +
Commit: Caolán McNamara 
CommitDate: Mon Nov 28 00:28:55 2022 +0100

resave with latest glade

Change-Id: Ie8e640365eb2882f07a485f27b777383c5982a2b
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/143356
Tested-by: Jenkins
Reviewed-by: Caolán McNamara 

diff --git a/sw/uiconfig/swriter/ui/autotext.ui 
b/sw/uiconfig/swriter/ui/autotext.ui
index 65dca13a9d17..ce59f4b19ade 100644
--- a/sw/uiconfig/swriter/ui/autotext.ui
+++ b/sw/uiconfig/swriter/ui/autotext.ui
@@ -1,16 +1,16 @@
 
-
+
 
   
   
 True
-False
+False
 
   
 True
-False
+False
 _New
-True
+True
 
   
 Creates a new AutoText 
category using the name that you entered in the Name box.
@@ -21,9 +21,9 @@
 
   
 True
-False
+False
 New (text only)
-True
+True
 
   
 Creates a new 
AutoText entry only from the text in the selection that you made in the current 
document. Graphics, tables and other objects are not included. You must first 
enter a name before you see this command.
@@ -34,9 +34,9 @@
 
   
 True
-False
+False
 _Copy
-True
+True
 
   
 Copies the selected 
AutoText to the clipboard.
@@ -47,9 +47,9 @@
 
   
 True
-False
+False
 Replace
-True
+True
 
   
 Replaces the 
contents of the selected AutoText entry with the selection that was made in the 
current document.
@@ -60,17 +60,17 @@
 
   
 True
-False
+False
 Rep_lace (text only)
-True
+True
   
 
 
   
 True
-False
+False
 Rename...
-True
+True
 
   
 Changes the name of 
the selected AutoText category to the name that you enter in the Name 
box.
@@ -81,23 +81,23 @@
 
   
 True
-False
+False
 _Delete
-True
+True
   
 
 
   
 True
-False
+False
   
 
 
   
 True
-False
+False
 _Edit
-True
+True
 
   
 Opens the selected 
AutoText entry for editing in a separate document. Make the changes that you 
want, choose File - Save AutoText, and then choose File - Close.
@@ -108,15 +108,15 @@
 
   
 True
-False
+False
   
 
 
   
 True
-False
+False
 _Macro...
-True
+True
 
   
 Opens the Assign Macro 
dialog, where you attach a macro to the selected AutoText entry.
@@ -127,15 +127,15 @@
 
   
 True
-False
+False
   
 
 
   
 True
-False
+False
 _Import...
-True
+True
 
   
 Opens a dialog where 
you can select the 97/2000/XP Word document or template, containing the 
AutoText entries that you want to import.
@@ -153,30 +153,30 @@
 
   
   
-False
-6
+False
+6
 AutoText
 True
-0
-0
-dialog
+0
+0
+dialog
 
   
-False
+False
 vertical
 12
 
   
-False
-end
+False
+end
 
   
 AutoTe_xt
 True
-True
-True
-True
-True
+True
+True
+True
+True
 editmenu
 
   
@@ -197,9 +197,9 @@
   
 Cat_egories...
 True
-True
-True
-True
+True
+True
+True
 
   
 Adds, renames, or 
deletes AutoText categories.
@@ -216,9 +216,9 @@
   
 _Path...
 True
-True
-True
-True
+True
+True
+True
 
   
 Opens the Edit Paths 
dialog, where you can select the directory to store AutoText.
@@ -235,8 +235,8 @@
   
 _Close
 True
-True
-True
+True
+True
 

[Libreoffice-ux-advise] [Bug 152029] Visually draw attention to in-view bookmark when selecting/hovering it in the Navigator

2022-11-27 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=152029

--- Comment #6 from Jim Raykowski  ---
Created attachment 183838
  --> https://bugs.documentfoundation.org/attachment.cgi?id=183838=edit
visually draw attention to in-view bookmark demo1

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

[Libreoffice-bugs] [Bug 152029] Visually draw attention to in-view bookmark when selecting/hovering it in the Navigator

2022-11-27 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=152029

--- Comment #6 from Jim Raykowski  ---
Created attachment 183838
  --> https://bugs.documentfoundation.org/attachment.cgi?id=183838=edit
visually draw attention to in-view bookmark demo1

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

[Libreoffice-bugs] [Bug 152256] New: please add more function in numbering

2022-11-27 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=152256

Bug ID: 152256
   Summary: please add more function in numbering
   Product: LibreOffice
   Version: 7.3.6.2 release
  Hardware: All
OS: All
Status: UNCONFIRMED
  Severity: enhancement
  Priority: medium
 Component: Writer
  Assignee: libreoffice-bugs@lists.freedesktop.org
  Reporter: fayerdra...@gmail.com

Description:
when I try to give suggestion feedback from
https://www.libreoffice.org/get-help/feedback/ somehow I end up here. I didn't
find any bugs, but just want to give suggestions to enhance LibreOffice.

in the country i am from (indonesia) it's common to make papers and books with
chapter name in roman while subchapter in arabic numbers. while its possible to
do this in microsoft word with only one list. In libreoffice writer i need to
differentiate the lists to make similar result which is quiet a hassle. after
all if there is 12 chapters, i need to make at least 13 lists to make similar
results. 

Steps to Reproduce:
1. choosing roman in first level number in numbering and chapters
2. choosing Arabic numbers in the second level number in numbering and chapters
3. add previous level numbers in numbering and chapters

Actual Results:
roman and Arabic numbers both show up in numbering and chapters.
example : 
chapter I
subchapter I.1
subchapter I.2
chapter II
subchapter II.1
subchapter II.2

Expected Results:
only use one type, either roman or Arabic numbers
example :
chapter I
subchapter 1.1
subcahpter 1.2
chapter II
subchapter 2.1
subchapter 2.2


Reproducible: Couldn't Reproduce


User Profile Reset: Yes

Additional Info:
with more button in multilevel numbering in microsoft word, its possible to
make this with only one line. but such kind of feature didn't exist in libre
office. i have also try to open docx file with that numbering in libreoffice,
but the result still combining between roman and arabic numbers.

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

Re: Crash test update

2022-11-27 Thread Dr. David Alan Gilbert
* crashtest (nore...@documentfoundation.org) wrote:
> Hi,
> 
> New crashtest update available at 
> .

Are there any docs on this script? It would be nice if 
this mail included a pointer to:
  a) The script
  b) The test documents (some are easier to find than others)
  c) Some pointers to how to debug, if those pointers exist.

I was looking through the backtraces/ dir and other than
looking through the backtrace for the name of the doc file
it's not obvious how to associate them.

Is this test run with --enable-debug builds? If so it would
be nice to capture diag from failed runs.

(Out of the 3 I've tried so far, only one fails for me locally,
the import from ooo 84576/laisvos_programos-vaiku_lavinimui.odt
dies from command line, gives a pretty error from the gui, and either
way gives 'MarkManager::makeMark(..) - refusing to create mark on non-textnode' 
)

Dave

> 38 files have crashed during import.
> 
> 16 files have crashed during export.
> 
> 0 files have differences compared to the baseline, which is core.git commit .
> (17764 files are excluded.)
> 
> - Your friendly crashtest bot





-- 
 -Open up your eyes, open up your mind, open up your code ---   
/ Dr. David Alan Gilbert|   Running GNU/Linux   | Happy  \ 
\dave @ treblig.org |   | In Hex /
 \ _|_ http://www.treblig.org   |___/


[Libreoffice-bugs] [Bug 139902] [META] PPTX Image issues

2022-11-27 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=139902

Gabor Kelemen (allotropia)  changed:

   What|Removed |Added

 Depends on||152069


Referenced Bugs:

https://bugs.documentfoundation.org/show_bug.cgi?id=152069
[Bug 152069] Export failure: The background parameters changed after export
-- 
You are receiving this mail because:
You are the assignee for the bug.

[Libreoffice-bugs] [Bug 139902] [META] PPTX Image issues

2022-11-27 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=139902

Gabor Kelemen (allotropia)  changed:

   What|Removed |Added

 Depends on||152070


Referenced Bugs:

https://bugs.documentfoundation.org/show_bug.cgi?id=152070
[Bug 152070] Import failure: The background parameters do not set up the same
way as in Powerpoint
-- 
You are receiving this mail because:
You are the assignee for the bug.

[Libreoffice-bugs] [Bug 152029] Visually draw attention to in-view bookmark when selecting/hovering it in the Navigator

2022-11-27 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=152029

--- Comment #5 from Eyal Rozenberg  ---
(In reply to Jim Raykowski from comment #4)
> Here is a patch that does the bookmark part of this request:
> https://gerrit.libreoffice.org/c/core/+/143357
> 
> Basically it creates a selection over a bookmark's start and end position if
> the start position of the bookmark is in the visible view. Bookmarks having
> the same start and end position are selected as the start position + 1
> character.

Could I trouble you to post a screenshot of how this looks? I don't think I
understand exactly. Also, does this actually select the bookmark, de-selecting
an existing selection? I don't think that's a good idea, especially since that
functionality is what a double-click does.

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

[Libreoffice-ux-advise] [Bug 152029] Visually draw attention to in-view bookmark when selecting/hovering it in the Navigator

2022-11-27 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=152029

--- Comment #5 from Eyal Rozenberg  ---
(In reply to Jim Raykowski from comment #4)
> Here is a patch that does the bookmark part of this request:
> https://gerrit.libreoffice.org/c/core/+/143357
> 
> Basically it creates a selection over a bookmark's start and end position if
> the start position of the bookmark is in the visible view. Bookmarks having
> the same start and end position are selected as the start position + 1
> character.

Could I trouble you to post a screenshot of how this looks? I don't think I
understand exactly. Also, does this actually select the bookmark, de-selecting
an existing selection? I don't think that's a good idea, especially since that
functionality is what a double-click does.

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

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

2022-11-27 Thread Stephan Bergmann (via logerrit)
 external/redland/UnpackedTarball_raptor.mk|1 +
 external/redland/raptor/Wint-conversion.patch |   22 ++
 2 files changed, 23 insertions(+)

New commits:
commit 84ce65ebf1fb7b1fd8945b42ae588a505a50bb89
Author: Stephan Bergmann 
AuthorDate: Wed Aug 3 17:08:35 2022 +0200
Commit: Tor Lillqvist 
CommitDate: Sun Nov 27 23:31:31 2022 +0100

external/redland: Fix -Wint-conversion

...with recent Clang 16 trunk since


"Strengthen -Wint-conversion to default to an error", causing

> raptor_parse.c:260:66: error: incompatible pointer to integer conversion 
returning 'void *' from a function with result type 'int' [-Wint-conversion]
>   RAPTOR_ASSERT_OBJECT_POINTER_RETURN_VALUE(world, raptor_world, NULL);
>  ^~~~

and

> raptor_serialize.c:243:66: error: incompatible pointer to integer 
conversion returning 'void *' from a function with result type 'int' 
[-Wint-conversion]
>   RAPTOR_ASSERT_OBJECT_POINTER_RETURN_VALUE(world, raptor_world, NULL);
>  ^~~~

Change-Id: I2c1083b78777589b992c180d8759e2313bf2fe42
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/137756
Tested-by: Jenkins
Reviewed-by: Stephan Bergmann 
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/143331
Tested-by: Jenkins CollaboraOffice 
Reviewed-by: Tor Lillqvist 

diff --git a/external/redland/UnpackedTarball_raptor.mk 
b/external/redland/UnpackedTarball_raptor.mk
index fbdc8b6f5510..619116c3380c 100644
--- a/external/redland/UnpackedTarball_raptor.mk
+++ b/external/redland/UnpackedTarball_raptor.mk
@@ -30,6 +30,7 @@ $(eval $(call gb_UnpackedTarball_add_patches,raptor,\

external/redland/raptor/0001-Calcualte-max-nspace-declarations-correctly-for-XML-.patch.1
 \

external/redland/raptor/0001-CVE-2020-25713-raptor2-malformed-input-file-can-lead.patch.1
 \
external/redland/raptor/libtool.patch \
+   external/redland/raptor/Wint-conversion.patch \
 ))
 
 # vim: set noet sw=4 ts=4:
diff --git a/external/redland/raptor/Wint-conversion.patch 
b/external/redland/raptor/Wint-conversion.patch
new file mode 100644
index ..fb85f4f13518
--- /dev/null
+++ b/external/redland/raptor/Wint-conversion.patch
@@ -0,0 +1,22 @@
+--- src/raptor_parse.c
 src/raptor_parse.c
+@@ -257,7 +257,7 @@
+ int
+ raptor_world_get_parsers_count(raptor_world* world)
+ {
+-  RAPTOR_ASSERT_OBJECT_POINTER_RETURN_VALUE(world, raptor_world, NULL);
++  RAPTOR_ASSERT_OBJECT_POINTER_RETURN_VALUE(world, raptor_world, 0);
+ 
+   raptor_world_open(world);
+ 
+--- src/raptor_serialize.c
 src/raptor_serialize.c
+@@ -240,7 +240,7 @@
+ int
+ raptor_world_get_serializers_count(raptor_world* world)
+ {
+-  RAPTOR_ASSERT_OBJECT_POINTER_RETURN_VALUE(world, raptor_world, NULL);
++  RAPTOR_ASSERT_OBJECT_POINTER_RETURN_VALUE(world, raptor_world, 0);
+ 
+   raptor_world_open(world);
+ 


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

2022-11-27 Thread Stephan Bergmann (via logerrit)
 external/coinmp/UnpackedTarball_coinmp.mk |1 
 external/coinmp/bind2nd.patch.1   |   87 ++
 2 files changed, 88 insertions(+)

New commits:
commit 58ca773fb97c3a0005397a45d2ce18396dbc136a
Author: Stephan Bergmann 
AuthorDate: Wed Sep 14 14:36:40 2022 +0200
Commit: Tor Lillqvist 
CommitDate: Sun Nov 27 23:31:14 2022 +0100

external/coinmp: Adapt to std::bind2nd gone from C++17

...which started to be an issue when building with recent Clang 16 trunk 
after


"C++/ObjC++: switch to gnu++17 as the default standard" against libc++.  
(Recent
versions of GCC similarly default to C++17, but libstdc++ by default still
provides bind2nd even for C++17.)  Alternatively, we could define
_LIBCPP_ENABLE_CXX17_REMOVED_BINDERS to work around this.  But as these 
appear
to be the only leftover occurrence of bind2nd across all of the code base, 
and
all but one of them have already been addressed upstream, lets address it 
for
good with this little patch.  (Where the last remaining occurrence not yet
addressed upstream is fixed in the same way as the other upstream fixes, 
using a
loop rather than e.g. a lambda that would force us to start to pass
CXXFLAGS_CXX11 into ExternalProejct_coinmp.)

Change-Id: Iddc22ea4c6d537b64bf2cf0b887d11da162f
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/139931
Tested-by: Jenkins
Reviewed-by: Stephan Bergmann 
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/143330
Tested-by: Jenkins CollaboraOffice 
Reviewed-by: Tor Lillqvist 

diff --git a/external/coinmp/UnpackedTarball_coinmp.mk 
b/external/coinmp/UnpackedTarball_coinmp.mk
index 0764d428aace..b874f2b290f3 100644
--- a/external/coinmp/UnpackedTarball_coinmp.mk
+++ b/external/coinmp/UnpackedTarball_coinmp.mk
@@ -47,6 +47,7 @@ $(eval $(call gb_UnpackedTarball_add_patches,coinmp,\
external/coinmp/register.patch \
external/coinmp/configure-exit.patch \
external/coinmp/pedantic-errors.patch \
+   external/coinmp/bind2nd.patch.1 \
 ))
 
 # vim: set noet sw=4 ts=4:
diff --git a/external/coinmp/bind2nd.patch.1 b/external/coinmp/bind2nd.patch.1
new file mode 100644
index ..5b3222eea9a0
--- /dev/null
+++ b/external/coinmp/bind2nd.patch.1
@@ -0,0 +1,87 @@
+--- a/Osi/src/OsiCommonTest/OsiSolverInterfaceTest.cpp
 b/Osi/src/OsiCommonTest/OsiSolverInterfaceTest.cpp
+@@ -1313,8 +1313,8 @@
+   int rows_to_delete_arr[] = { 0 } ;
+   si->deleteRows(1,rows_to_delete_arr) ;
+ 
+-  std::transform(objective,objective+4,objective,
+-   std::bind2nd(std::plus(),0.15)) ;
++  for (int i = 0; i != 4; ++i)
++objective[i] += 0.15;
+   si->setObjective(objective) ;
+   si->resolve() ;
+   OSIUNITTEST_ASSERT_ERROR(si->isProvenOptimal(),  return false, *si, 
"test16SebastianNowozin second resolve");
+
+The below is an excerpt from
+
 "make c++17
+compatible":
+
+diff --git a/CoinUtils/src/CoinPackedMatrix.cpp 
b/CoinUtils/src/CoinPackedMatrix.cpp
+index c7631289..0b103159 100644
+--- a/CoinUtils/src/CoinPackedMatrix.cpp
 b/CoinUtils/src/CoinPackedMatrix.cpp
+@@ -1490,11 +1490,11 @@ CoinPackedMatrix::minorAppendSameOrdered(const 
CoinPackedMatrix& matrix)
+ 
+// now insert the entries of matrix
+for (i = majorDim_ - 1; i >= 0; --i) {
+-  const int l = matrix.length_[i];
+-  std::transform(matrix.index_ + matrix.start_[i],
+-  matrix.index_ + (matrix.start_[i] + l),
+-  index_ + (start_[i] + length_[i]),
+-  std::bind2nd(std::plus(), minorDim_));
++  int l = matrix.length_[i];
++  CoinBigIndex put = start_[i]+length_[i];
++  const CoinBigIndex get = matrix.start_[i];
++  for (int j=0;j(), value) );
++  for (int i=0 ; i < nElements_; i++)
++elements_[i] += value;
+ }
+ 
+ 
//-
+@@ -293,8 +293,8 @@ CoinPackedVector::operator+=(double value)
+ void
+ CoinPackedVector::operator-=(double value) 
+ {
+-   std::transform(elements_, elements_ + nElements_, elements_,
+-std::bind2nd(std::minus(), value) );
++  for (int i=0 ; i < nElements_; i++)
++elements_[i] -= value;
+ }
+ 
+ 
//-
+@@ -302,8 +302,8 @@ CoinPackedVector::operator-=(double value)
+ void
+ CoinPackedVector::operator*=(double value) 
+ {
+-   std::transform(elements_, elements_ + nElements_, elements_,
+-std::bind2nd(std::multiplies(), value) );
++  for (int i=0 ; i < nElements_; i++)
++elements_[i] *= value;
+ }
+ 
+ 
//-
+@@ -311,8 +311,8 @@ CoinPackedVector::operator*=(double value)
+ void
+ 

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

2022-11-27 Thread Stephan Bergmann (via logerrit)
 external/coinmp/UnpackedTarball_coinmp.mk |1 +
 external/coinmp/pedantic-errors.patch |   11 +++
 2 files changed, 12 insertions(+)

New commits:
commit 9d0c46276e71cf8edabe617d4e3f47c296afd655
Author: Stephan Bergmann 
AuthorDate: Tue May 17 15:06:40 2022 +0200
Commit: Tor Lillqvist 
CommitDate: Sun Nov 27 23:30:54 2022 +0100

external/coinmp: Avoid -Werror,-Wc++2b-extensions

> ClpSimplex.cpp:6038:2: error: use of a '#elifdef' directive is a C++2b 
extension [-Werror,-Wc++2b-extensions]
> #elifdef COIN_HAS_MUMPS
>  ^

seen with Clang 15 trunk since


"Warn if using `elifdef` & `elifndef` in not C2x & C++2b mode" (and which is
turned into an error because External_coinmp builds with --pedantic-errors)

Change-Id: I1db213aec91bc17c720fd58270eab452b2e4e0f5
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/134478
Tested-by: Jenkins
Reviewed-by: Stephan Bergmann 
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/143329
Tested-by: Jenkins CollaboraOffice 
Reviewed-by: Tor Lillqvist 

diff --git a/external/coinmp/UnpackedTarball_coinmp.mk 
b/external/coinmp/UnpackedTarball_coinmp.mk
index 0784bbde1ac1..0764d428aace 100644
--- a/external/coinmp/UnpackedTarball_coinmp.mk
+++ b/external/coinmp/UnpackedTarball_coinmp.mk
@@ -46,6 +46,7 @@ $(eval $(call gb_UnpackedTarball_add_patches,coinmp,\
external/coinmp/Wnon-c-typedef-for-linkage.patch \
external/coinmp/register.patch \
external/coinmp/configure-exit.patch \
+   external/coinmp/pedantic-errors.patch \
 ))
 
 # vim: set noet sw=4 ts=4:
diff --git a/external/coinmp/pedantic-errors.patch 
b/external/coinmp/pedantic-errors.patch
new file mode 100644
index ..2cf86b7e0ef4
--- /dev/null
+++ b/external/coinmp/pedantic-errors.patch
@@ -0,0 +1,11 @@
+--- Clp/src/ClpSimplex.cpp
 Clp/src/ClpSimplex.cpp
+@@ -6035,7 +6035,7 @@
+  assert (!doKKT);
+  ClpCholeskyTaucs * cholesky = new ClpCholeskyTaucs();
+  barrier.setCholesky(cholesky);
+-#elifdef COIN_HAS_MUMPS
++#elif defined COIN_HAS_MUMPS
+  if (!doKKT) {
+   ClpCholeskyMumps * cholesky = new ClpCholeskyMumps();
+   barrier.setCholesky(cholesky);


[Libreoffice-bugs] [Bug 152029] Visually draw attention to in-view bookmark when selecting/hovering it in the Navigator

2022-11-27 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=152029

Jim Raykowski  changed:

   What|Removed |Added

 Ever confirmed|0   |1
 Status|UNCONFIRMED |NEW

--- Comment #4 from Jim Raykowski  ---
Here is a patch that does the bookmark part of this request:
https://gerrit.libreoffice.org/c/core/+/143357

Basically it creates a selection over a bookmark's start and end position if
the start position of the bookmark is in the visible view. Bookmarks having the
same start and end position are selected as the start position + 1 character.

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

[Libreoffice-ux-advise] [Bug 152029] Visually draw attention to in-view bookmark when selecting/hovering it in the Navigator

2022-11-27 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=152029

Jim Raykowski  changed:

   What|Removed |Added

 Ever confirmed|0   |1
 Status|UNCONFIRMED |NEW

--- Comment #4 from Jim Raykowski  ---
Here is a patch that does the bookmark part of this request:
https://gerrit.libreoffice.org/c/core/+/143357

Basically it creates a selection over a bookmark's start and end position if
the start position of the bookmark is in the visible view. Bookmarks having the
same start and end position are selected as the start position + 1 character.

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

[Libreoffice-bugs] [Bug 139898] [META] PPTX Master slides / notes / handouts related issues

2022-11-27 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=139898
Bug 139898 depends on bug 142047, which changed state.

Bug 142047 Summary: Loss of image quality converting ODP to PPTX
https://bugs.documentfoundation.org/show_bug.cgi?id=142047

   What|Removed |Added

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

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

[Libreoffice-bugs] [Bug 142047] Loss of image quality converting ODP to PPTX

2022-11-27 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=142047

Gabor Kelemen (allotropia)  changed:

   What|Removed |Added

 Resolution|--- |DUPLICATE
 CC||kelem...@ubuntu.com,
   ||nagy.tib...@nisz.hu,
   ||nem...@numbertext.org
 Status|NEW |RESOLVED

--- Comment #9 from Gabor Kelemen (allotropia)  ---
Thanks Tibor for fixing this one too :)

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

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

[Libreoffice-bugs] [Bug 142047] Loss of image quality converting ODP to PPTX

2022-11-27 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=142047

--- Comment #8 from Gabor Kelemen (allotropia)  ---
Created attachment 183835
  --> https://bugs.documentfoundation.org/attachment.cgi?id=183835=edit
The example file and its PPTX version in Impress, smaller image

Looks much better now in

Version: 7.5.0.0.alpha1+ (X86_64) / LibreOffice Community
Build ID: 8c6a9daaf99830e1a2a560a9dd0abf3c1e4cfa48
CPU threads: 16; OS: Linux 5.4; UI render: default; VCL: gtk3
Locale: hu-HU (hu_HU.UTF-8); UI: en-US
Calc: threaded

The images Width, Height and Position are now correctly saved and reloaded in
PPTX.

Presumably after 
https://git.libreoffice.org/core/+/3f70375cf160841b6140f5f1b2b79af3652897f8%5E%21

author  Tibor Nagy Fri Nov 18 12:06:59 2022 +0100
committer   László NémethThu Nov 24 16:56:38
2022 +0100

tdf#152069 tdf#108356 PPTX export: fix missing tile properties

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

[Libreoffice-bugs] [Bug 149872] Sidebar properties switch from what we're manipulating to the page's properties after merging two shapes

2022-11-27 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=149872

csyu@gmail.com changed:

   What|Removed |Added

 CC||csyu@gmail.com

--- Comment #2 from csyu@gmail.com ---
I was able to reproduce the bug in the unstable and stable build:

Version: 7.5.0.0.alpha0+ (x64) / LibreOffice Community
Build ID: 5a1f41a0d3aab15c113651f2edc9d4137ae99063
CPU threads: 8; OS: Windows 10.0 Build 19044; UI render: Skia/Raster; VCL: win
Locale: en-US (en_US); UI: en-US
Calc: threaded

Version: 7.4.2.3 (x64) / LibreOffice Community
Build ID: 382eef1f22670f7f4118c8c2dd222ec7ad009daf
CPU threads: 8; OS: Windows 10.0 Build 19044; UI render: Skia/Vulkan; VCL: win
Locale: en-US (en_US); UI: en-US
Calc: CL

However, I'm wondering if this is actually a bug because once I click on the
shape, it reverts back to properties of the shape we're manipulating. I'll
leave it as unconfirmed

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

[Libreoffice-bugs] [Bug 152254] Writer and calc files take almost a minute to open

2022-11-27 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=152254

m.a.riosv  changed:

   What|Removed |Added

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

--- Comment #1 from m.a.riosv  ---
Please test with a clean profile, Menu/Help/Restart in Safe Mode

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

[Libreoffice-bugs] [Bug 152251] Option Button does not work in CALC and WRITER

2022-11-27 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=152251

m.a.riosv  changed:

   What|Removed |Added

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

--- Comment #1 from m.a.riosv  ---
Please, can you attach a sample file with the issue.

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

[Libreoffice-bugs] [Bug 152250] Copying conditional formatting creates unmodifiable styles (save/load fixes it)

2022-11-27 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=152250

m.a.riosv  changed:

   What|Removed |Added

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

--- Comment #1 from m.a.riosv  ---
I can't repro
Version: 7.4.3.2 (x64) / LibreOffice Community
Build ID: 1048a8393ae2eeec98dff31b5c133c5f1d08b890
CPU threads: 4; OS: Windows 10.0 Build 19045; UI render: Skia/Raster; VCL: win
Locale: es-ES (es_ES); UI: en-US Calc: CL
Version: 7.5.0.0.alpha1+ (X86_64) / LibreOffice Community
Build ID: 5b18eebc2c95321ce7e6edf10f4df81557382a48
CPU threads: 4; OS: Windows 10.0 Build 19045; UI render: Skia/Raster; VCL: win
Locale: es-ES (es_ES); UI: en-US Calc: CL threaded

Please test with a clean profile, Menu/Help/Restart in Safe Mode

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

[Libreoffice-bugs] [Bug 147203] drag and drop between AutoText categories does not work on Writer

2022-11-27 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=147203

Caolán McNamara  changed:

   What|Removed |Added

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

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

[Libreoffice-bugs] [Bug 152255] New: Crash in: ImpEditView::dragDropEnd(com::sun::star::datatransfer::dnd::DragSourceDropEvent const &)

2022-11-27 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=152255

Bug ID: 152255
   Summary: Crash in:
ImpEditView::dragDropEnd(com::sun::star::datatransfer:
:dnd::DragSourceDropEvent const &)
   Product: LibreOffice
   Version: 7.3.3.2 release
  Hardware: All
OS: All
Status: UNCONFIRMED
  Severity: normal
  Priority: medium
 Component: Impress
  Assignee: libreoffice-bugs@lists.freedesktop.org
  Reporter: colinz...@icloud.com

This bug was filed from the crash reporting server and is
br-06435b9b-b9b9-41bc-ba39-543ca23e41de.
=

I copied the content of one field of a table using Ctrl+C.
When trying to insert it in another field using Ctrl+V, Impress crashed.

After restoring the file, the text was inserted as a seperate text field over
the table.

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

[Libreoffice-bugs] [Bug 147203] drag and drop between AutoText categories does not work on Writer

2022-11-27 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=147203

raal  changed:

   What|Removed |Added

   Keywords|bibisectRequest |bibisected, bisected
  Regression By||Caolán McNamara
 CC||caol...@redhat.com,
   ||r...@post.cz

--- Comment #2 from raal  ---
This seems to have begun at the below commit.
Adding Cc: to Caolán McNamara; Could you possibly take a look at this one?
Thanks

aac54a91708b8eaa0fab21b5bcea480fbceda999 is the first bad commit
commit aac54a91708b8eaa0fab21b5bcea480fbceda999
Author: Jenkins Build User 
Date:   Fri May 31 21:12:43 2019 +0200

source sha:4830a1bae89a8ed60696503e315ffd42c70dff74

https://git.libreoffice.org/core/+/4830a1bae89a8ed60696503e315ffd42c70dff74

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

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

2022-11-27 Thread Eike Rathke (via logerrit)
 i18npool/source/localedata/data/pt_AO.xml |   40 +++---
 1 file changed, 20 insertions(+), 20 deletions(-)

New commits:
commit eac36cde95002c89649c5de0e13864789618b075
Author: Eike Rathke 
AuthorDate: Sun Nov 27 18:20:57 2022 +0100
Commit: Adolfo Jayme Barrientos 
CommitDate: Sun Nov 27 21:19:47 2022 +0100

{pt-AO} change to untranslated YY, keywords, translated AA never worked

Apparently copied from {pt-PT} year AA and  format codes
should not had made it across but also never worked as
LANGUAGE_USER_PORTUGUESE_ANGOLA was missing in
ImpSvNumberformatScan::SetDependentKeywords() so date codes
displayed literal AA instead. Seems no one is using that locale
with dates..

Since

commit 5d833d37851597c1fb9076710d9eb03e4c94ca07
CommitDate: Fri Apr 8 20:51:13 2011 +0200

add pt_AO locale data (edited version of Mandrake's patch)

Change-Id: Icd5f81d0a49462ad2514655742d6c05f069f55fc
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/143354
Reviewed-by: Eike Rathke 
Tested-by: Jenkins
(cherry picked from commit 0deb57a1e8d5e85a364fdb5678b46f6fdd7d345b)
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/143270
Reviewed-by: Adolfo Jayme Barrientos 

diff --git a/i18npool/source/localedata/data/pt_AO.xml 
b/i18npool/source/localedata/data/pt_AO.xml
index 24d7bf2c1685..730b937def9e 100644
--- a/i18npool/source/localedata/data/pt_AO.xml
+++ b/i18npool/source/localedata/data/pt_AO.xml
@@ -54,13 +54,13 @@
   
 D-M
 
-  DD-MM-
+  DD-MM-
 
 
-  NN DD-MMM AA
+  NN DD-MMM YY
 
 
-  MM-AA
+  MM-YY
 
 
   DD-MMM
@@ -69,49 +69,49 @@
   
 
 
-  QQ AA
+  QQ YY
 
 
-  DD-MM-
+  DD-MM-
 
 
-  DD-MM-AA
+  DD-MM-YY
 
 
-  D "de"  "de" 
+  D "de"  "de" 
 
 
-  D "de" MMM "de" AA
+  D "de" MMM "de" YY
 
 
-  D "de" MMM "de" 
+  D "de" MMM "de" 
 
 
-  D "de"  "de" 
+  D "de"  "de" 
 
 
-  NN, D "de" MMM "de" AA
+  NN, D "de" MMM "de" YY
 
 
-  NN, D "de"  "de" 
+  NN, D "de"  "de" 
 
 
-  D "de"  "de" 
+  D "de"  "de" 
 
 
-  D. MMM. 
+  D. MMM. 
 
 
-  D.  
+  D.  
 
 
   MM-DD
 
 
-  AA-MM-DD
+  YY-MM-DD
 
 
-  -MM-DD
+  -MM-DD
   ISO 8601 (EN 28601)
 
 
@@ -139,13 +139,13 @@
   [HH]:MM:SS,00
 
 
-  DD-MM-AA HH:MM
+  DD-MM-YY HH:MM
 
 
-  DD-MM- HH:MM:SS
+  DD-MM- HH:MM:SS
 
 
-  DD-MM- HH:MM
+  DD-MM- HH:MM
 
 
   Geral


[Libreoffice-bugs] [Bug 152249] Calc's "formula Box" is too big

2022-11-27 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=152249

V Stuart Foote  changed:

   What|Removed |Added

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

--- Comment #4 from V Stuart Foote  ---
Looks to be issue of bug 150664, already patched for 7.4.3.2 but apparently
still needs additional work for scaled UI.

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

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

[Libreoffice-bugs] [Bug 152254] New: Writer and calc files take almost a minute to open

2022-11-27 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=152254

Bug ID: 152254
   Summary: Writer and calc files take almost a minute to open
   Product: LibreOffice
   Version: 6.2 all versions
  Hardware: All
OS: Windows (All)
Status: UNCONFIRMED
  Severity: normal
  Priority: medium
 Component: Writer
  Assignee: libreoffice-bugs@lists.freedesktop.org
  Reporter: nyrk...@gmail.com

Description:
First it started suddenly happening only with calc files but after some time,
even writer files started taking almost a minute to open (does not happen when
creating a new empty file). Before they open, the window freezes and is not
responding. I thought it was because I was using an older version (6.2 I think)
but after installing the newest version (7.4), the problem was not resolved.
LibreOffice itself can be opened just fine. I tried opening files in safe mode
which worked once, but second time I could only open an empty file without
problems, but opening my own files resulted in window freezing and waiting some
time for it to open again.

Steps to Reproduce:
1. Open an existing file

Actual Results:
Window freezing and file taking about a minute to open.

Expected Results:
Open the file within a short amount of time (a few seconds at maximum,
depending on the size of the file).


Reproducible: Always


User Profile Reset: No

Additional Info:
Version: 7.4.2.3 (x64) / LibreOffice Community
Build ID: 382eef1f22670f7f4118c8c2dd222ec7ad009daf
CPU threads: 8; OS: Windows 10.0 Build 19045; UI render: Skia/Vulkan; VCL: win
Locale: cs-CZ (cs_CZ); UI: cs-CZ
Calc: threaded

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

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

2022-11-27 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=118017

steve  changed:

   What|Removed |Added

 Depends on||152253


Referenced Bugs:

https://bugs.documentfoundation.org/show_bug.cgi?id=152253
[Bug 152253] macOS Dark Mode Calc: text in Input Box unreadable (black should
be white)
-- 
You are receiving this mail because:
You are the assignee for the bug.

[Libreoffice-bugs] [Bug 152253] macOS Dark Mode Calc: text in Input Box unreadable (black should be white)

2022-11-27 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=152253

steve  changed:

   What|Removed |Added

 CC||caol...@redhat.com
 Blocks||118017


Referenced Bugs:

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

[Libreoffice-bugs] [Bug 152253] macOS Dark Mode Calc: text in Input Box unreadable (black should be white)

2022-11-27 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=152253

--- Comment #1 from steve  ---
Created attachment 183834
  --> https://bugs.documentfoundation.org/attachment.cgi?id=183834=edit
2022-11-27 screenshot input box wrong text color dark mode

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

[Libreoffice-bugs] [Bug 152253] New: macOS Dark Mode Calc: text in Input Box unreadable (black should be white)

2022-11-27 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=152253

Bug ID: 152253
   Summary: macOS Dark Mode Calc: text in Input Box unreadable
(black should be white)
   Product: LibreOffice
   Version: 7.5.0.0 alpha0+ Master
  Hardware: All
OS: macOS (All)
Status: UNCONFIRMED
  Severity: normal
  Priority: medium
 Component: UI
  Assignee: libreoffice-bugs@lists.freedesktop.org
  Reporter: l...@disr.it

Description:
see screenshot, text in Input Box is unreadable in dark mode

Steps to Reproduce:
input any text into a cell and select cell
look at input box

Actual Results:
black text in input box

Expected Results:
white text in input box


Reproducible: Always


User Profile Reset: No

Additional Info:
Version: 7.5.0.0.alpha1+ (X86_64) / LibreOffice Community
Build ID: 5b18eebc2c95321ce7e6edf10f4df81557382a48
CPU threads: 8; OS: Mac OS X 13.0.1; UI render: default; VCL: osx
Locale: de-DE (en_DE.UTF-8); UI: en-US
Calc: threaded

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

[Libreoffice-bugs] [Bug 150638] Autotext not working (Display remainder of name as suggestion …. not showing)

2022-11-27 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=150638

Dieter  changed:

   What|Removed |Added

 CC||dgp-m...@gmx.de
 Ever confirmed|0   |1
 Status|UNCONFIRMED |NEW

--- Comment #5 from Dieter  ---
(In reply to Gowrishankar from comment #4)
> REPRODUCED

=> Status NEW

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

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

2022-11-27 Thread Eike Rathke (via logerrit)
 i18npool/source/localedata/data/hr_HR.xml |5 ++---
 1 file changed, 2 insertions(+), 3 deletions(-)

New commits:
commit 5c876d62f1a36305ffd6e59bd53a18673bb1a34d
Author: Eike Rathke 
AuthorDate: Sun Nov 27 17:11:49 2022 +0100
Commit: Adolfo Jayme Barrientos 
CommitDate: Sun Nov 27 20:38:08 2022 +0100

Resolves: tdf#150011 Switch default currency HRK Croatian Kuna to EUR Euro

HR will join Euro area on 2023-01-01.

Change-Id: I3836804ff68419550091826ea2414bc0edd55a84
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/143346
Reviewed-by: Eike Rathke 
Tested-by: Jenkins
(cherry picked from commit c58bc31ece80ccdfc88bd043787869c5e460dbd8)
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/143269
Reviewed-by: Adolfo Jayme Barrientos 

diff --git a/i18npool/source/localedata/data/hr_HR.xml 
b/i18npool/source/localedata/data/hr_HR.xml
index 4de83e5535cd..1d29f1f2e0e6 100644
--- a/i18npool/source/localedata/data/hr_HR.xml
+++ b/i18npool/source/localedata/data/hr_HR.xml
@@ -414,15 +414,14 @@
 
   
   
-
+
   HRK
   kn
   HRK
   Hrvatska Kuna
   2
 
-
-
+
   EUR
   €
   EUR


[Libreoffice-commits] core.git: vcl/headless

2022-11-27 Thread Caolán McNamara (via logerrit)
 vcl/headless/CairoCommon.cxx |2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

New commits:
commit cb7e6003ad06d71a27baeb435366b91f87bdeb2f
Author: Caolán McNamara 
AuthorDate: Sun Nov 27 15:12:37 2022 +
Commit: Caolán McNamara 
CommitDate: Sun Nov 27 20:33:10 2022 +0100

cid#1517054 Logically dead code

Change-Id: I0ea48d79d32920cf5f5ab2b11a5b4f53ddae0dc7
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/143345
Tested-by: Jenkins
Reviewed-by: Caolán McNamara 

diff --git a/vcl/headless/CairoCommon.cxx b/vcl/headless/CairoCommon.cxx
index 401571a7625c..322b1e838463 100644
--- a/vcl/headless/CairoCommon.cxx
+++ b/vcl/headless/CairoCommon.cxx
@@ -630,8 +630,8 @@ bool CairoCommon::drawPolyLine(cairo_t* cr, 
basegfx::B2DRange* pExtents, const C
 {
 SAL_WARN("vcl.gdi", "drawPolyLine, skipping suspicious range of: "
 << aRange << " for fuzzing performance");
+return true;
 }
-return true;
 }
 
 // need to check/handle LineWidth when ObjectToDevice transformation is 
used


[Libreoffice-bugs] [Bug 133245] Collabora Office Android 9 opens file read only from Samsung My Files, R/W OK from Collabora file browser.

2022-11-27 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=133245

--- Comment #6 from Aron Budea  ---
Thanks for retesting and for the feedback, Glenn!

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

[Libreoffice-bugs] [Bug 133245] Collabora Office Android 9 opens file read only from Samsung My Files, R/W OK from Collabora file browser.

2022-11-27 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=133245

Glenn Talbott  changed:

   What|Removed |Added

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

--- Comment #5 from Glenn Talbott  ---
I got an e-mail from bugzilla requesting I re-verify this bug with the latest
version of LibreOffice (Collabora Office Android). Here are the results:

1. As I no longer have Android 9, I retested Collabora version 4.2.3.3 in
Android 11. I found the opening a MS Office file (or a .ods file) from "My
Files" still opens the file read-only. HOWEVER, opening it from Collabora file
browser ALSO opens the file read-only, but with out a read-only warning.

2. I installed Collabora version 21.11.6.1 from the Google Store, and found
that opening MS Office files from both "My Files" and the Collabora file
browser the files are opened read-only, with warning but the blue Edit button
is now visible. Attempting to edit, gives you a file selection menu to create
and save a copy for editing.

Since the operation between "My Files" and the Collabora browser is now
consistant (sub optimal, but consistant), and a Google search shows that the
"open read-only" problem for MS Office and ODT/ODS files has spread beyond
Collabora to other Android apps and beyond Android to ChromeOS, I'm going to
assume there isn't much the LibreOffice developers can do about it. Therefore I
am marking the status as RESOLVED - WORKSFORME as requested.

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

[Libreoffice-bugs] [Bug 64679] [META] Printer settings related issues

2022-11-27 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=64679

Roman Kuznetsov <79045_79...@mail.ru> changed:

   What|Removed |Added

 Depends on||100359


Referenced Bugs:

https://bugs.documentfoundation.org/show_bug.cgi?id=100359
[Bug 100359] No option available to reset "File > Printer Settings" to default
printer
-- 
You are receiving this mail because:
You are the assignee for the bug.

[Libreoffice-bugs] [Bug 100359] No option available to reset "File > Printer Settings" to default printer

2022-11-27 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=100359

Roman Kuznetsov <79045_79...@mail.ru> changed:

   What|Removed |Added

 Blocks||64679


Referenced Bugs:

https://bugs.documentfoundation.org/show_bug.cgi?id=64679
[Bug 64679] [META] Printer settings related issues
-- 
You are receiving this mail because:
You are the assignee for the bug.

[Libreoffice-bugs] [Bug 133092] [META] Crash bugs

2022-11-27 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=133092

Roman Kuznetsov <79045_79...@mail.ru> changed:

   What|Removed |Added

 Depends on||146989


Referenced Bugs:

https://bugs.documentfoundation.org/show_bug.cgi?id=146989
[Bug 146989] Crash in: ssp2mu.dll
-- 
You are receiving this mail because:
You are the assignee for the bug.

[Libreoffice-bugs] [Bug 64679] [META] Printer settings related issues

2022-11-27 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=64679

Roman Kuznetsov <79045_79...@mail.ru> changed:

   What|Removed |Added

 Depends on||146989


Referenced Bugs:

https://bugs.documentfoundation.org/show_bug.cgi?id=146989
[Bug 146989] Crash in: ssp2mu.dll
-- 
You are receiving this mail because:
You are the assignee for the bug.

[Libreoffice-bugs] [Bug 146989] Crash in: ssp2mu.dll

2022-11-27 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=146989

Roman Kuznetsov <79045_79...@mail.ru> changed:

   What|Removed |Added

 Blocks||64679, 133092


Referenced Bugs:

https://bugs.documentfoundation.org/show_bug.cgi?id=64679
[Bug 64679] [META] Printer settings related issues
https://bugs.documentfoundation.org/show_bug.cgi?id=133092
[Bug 133092] [META] Crash bugs
-- 
You are receiving this mail because:
You are the assignee for the bug.

[Libreoffice-bugs] [Bug 108663] [META] AutoText bugs and enhancements

2022-11-27 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=108663

Roman Kuznetsov <79045_79...@mail.ru> changed:

   What|Removed |Added

 Depends on||150638


Referenced Bugs:

https://bugs.documentfoundation.org/show_bug.cgi?id=150638
[Bug 150638] Autotext not working (Display remainder of name as suggestion ….
not showing)
-- 
You are receiving this mail because:
You are the assignee for the bug.

[Libreoffice-bugs] [Bug 150638] Autotext not working (Display remainder of name as suggestion …. not showing)

2022-11-27 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=150638

Roman Kuznetsov <79045_79...@mail.ru> changed:

   What|Removed |Added

 Blocks||108663


Referenced Bugs:

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

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

2022-11-27 Thread Caolán McNamara (via logerrit)
 sw/source/ui/vba/vbacontentcontrols.cxx |4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

New commits:
commit 31d4db12d91d26f245ac40fc0adbb27ff1f93d6f
Author: Caolán McNamara 
AuthorDate: Sun Nov 27 16:40:38 2022 +
Commit: Caolán McNamara 
CommitDate: Sun Nov 27 20:16:42 2022 +0100

cid#1517059 disentangle Improper use of negative value

Change-Id: I907f54cd93d78fe3638e407c70253b94f849eac3
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/143351
Tested-by: Jenkins
Reviewed-by: Caolán McNamara 

diff --git a/sw/source/ui/vba/vbacontentcontrols.cxx 
b/sw/source/ui/vba/vbacontentcontrols.cxx
index c33b80bb4264..4ef73f5d196e 100644
--- a/sw/source/ui/vba/vbacontentcontrols.cxx
+++ b/sw/source/ui/vba/vbacontentcontrols.cxx
@@ -41,10 +41,10 @@ lcl_getContentControl(std::u16string_view sName, 
std::u16string_view sTag,
 SwTextContentControl* pControl = nullptr;
 std::vector vElementNames;
 SwContentControlManager& rManager = pDoc->GetContentControlManager();
-size_t i = static_cast(rIndex);
 const size_t nLen = rManager.GetCount();
 if (!pElementNames && rIndex > 0 && sName.empty() && sTag.empty() && 
sTitle.empty())
 {
+size_t i = static_cast(rIndex);
 // This is the normal get-by-index/getCount mode - no need for fancy 
filtering.
 if (i < nLen)
 pControl = rManager.Get(i);
@@ -55,7 +55,7 @@ lcl_getContentControl(std::u16string_view sName, 
std::u16string_view sTag,
 {
 // loop through everything collecting names, filtering by Tag/Title
 sal_Int32 nCounter = 0;
-for (i = 0; i < nLen; ++i)
+for (size_t i = 0; i < nLen; ++i)
 {
 pControl = rManager.Get(i);
 if (!sTag.empty()


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

2022-11-27 Thread Caolán McNamara (via logerrit)
 cui/source/customize/cfgutil.cxx |2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

New commits:
commit 026d6e08fada78f095cd32a580f3debe20708982
Author: Caolán McNamara 
AuthorDate: Sun Nov 27 16:31:32 2022 +
Commit: Caolán McNamara 
CommitDate: Sun Nov 27 20:15:47 2022 +0100

cid#1517060 Unchecked return value

Change-Id: Ic11f632270c65d5c4446771336e3bc509617
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/143350
Tested-by: Jenkins
Reviewed-by: Caolán McNamara 

diff --git a/cui/source/customize/cfgutil.cxx b/cui/source/customize/cfgutil.cxx
index 621238da0cb8..7746333fe796 100644
--- a/cui/source/customize/cfgutil.cxx
+++ b/cui/source/customize/cfgutil.cxx
@@ -1349,7 +1349,7 @@ SvxScriptSelectorDialog::LoadLastUsedMacro()
 nOpenedNodes++;
 }
 if (xCategories.iter_has_child(*xIter))
-xCategories.iter_children(*xIter);
+(void)xCategories.iter_children(*xIter);
 else if (nOpenedNodes < nInfoParts - 1)
 // If the number of levels in the tree is smaller than the
 // number of parts in the macro info string, then return


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

2022-11-27 Thread Caolán McNamara (via logerrit)
 sw/source/core/crsr/bookmark.cxx |3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

New commits:
commit cf636728b6bfbd8f5992e5a4393496fb411c5b8c
Author: Caolán McNamara 
AuthorDate: Sun Nov 27 16:29:51 2022 +
Commit: Caolán McNamara 
CommitDate: Sun Nov 27 20:14:52 2022 +0100

cid#1517056 Dereference after null check

Change-Id: I9615e8a762b646d9b9567db56c0d59c61daa010f
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/143349
Tested-by: Jenkins
Reviewed-by: Caolán McNamara 

diff --git a/sw/source/core/crsr/bookmark.cxx b/sw/source/core/crsr/bookmark.cxx
index a05e4024db9c..feb7e77a3163 100644
--- a/sw/source/core/crsr/bookmark.cxx
+++ b/sw/source/core/crsr/bookmark.cxx
@@ -821,7 +821,8 @@ namespace sw::mark
 aList.insert(aList.begin() + nNewPos, rText);
 else
 {
-*pIndex = nLen;
+if (pIndex)
+*pIndex = nLen;
 aList.push_back(rText);
 }
 


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

2022-11-27 Thread Caolán McNamara (via logerrit)
 sdext/source/pdfimport/tree/drawtreevisiting.cxx |2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

New commits:
commit cea9ca3b77ef7f8f11c3eae0786986028161301c
Author: Caolán McNamara 
AuthorDate: Sun Nov 27 16:23:10 2022 +
Commit: Caolán McNamara 
CommitDate: Sun Nov 27 20:14:07 2022 +0100

cid#982469 Unchecked dynamic_cast

Change-Id: I48904acdd34d7b546a8099f265693e2d46c5d2aa
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/143347
Tested-by: Jenkins
Reviewed-by: Caolán McNamara 

diff --git a/sdext/source/pdfimport/tree/drawtreevisiting.cxx 
b/sdext/source/pdfimport/tree/drawtreevisiting.cxx
index 2356ddc254c4..2e56bb449662 100644
--- a/sdext/source/pdfimport/tree/drawtreevisiting.cxx
+++ b/sdext/source/pdfimport/tree/drawtreevisiting.cxx
@@ -706,7 +706,7 @@ void DrawXmlOptimizer::optimizeTextElements(Element& 
rParent)
 )
 {
 pCur->updateGeometryWith( pNext );
-if (pPara->bRtl)
+if (pPara && pPara->bRtl)
 {
 // Tdf#152083: If RTL, reverse the text in pNext so 
that its correct order is
 // restored when the combined text is reversed in 
DrawXmlEmitter::visit.


[Libreoffice-bugs] [Bug 108663] [META] AutoText bugs and enhancements

2022-11-27 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=108663

Roman Kuznetsov <79045_79...@mail.ru> changed:

   What|Removed |Added

 Depends on||150510


Referenced Bugs:

https://bugs.documentfoundation.org/show_bug.cgi?id=150510
[Bug 150510] Inserting table with autotext changes the next paragraph style to
"default paragraph style"
-- 
You are receiving this mail because:
You are the assignee for the bug.

[Libreoffice-bugs] [Bug 150510] Inserting table with autotext changes the next paragraph style to "default paragraph style"

2022-11-27 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=150510

Roman Kuznetsov <79045_79...@mail.ru> changed:

   What|Removed |Added

 Blocks||108663


Referenced Bugs:

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

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

2022-11-27 Thread Eike Rathke (via logerrit)
 i18npool/source/localedata/data/pt_AO.xml |   40 +++---
 1 file changed, 20 insertions(+), 20 deletions(-)

New commits:
commit 0deb57a1e8d5e85a364fdb5678b46f6fdd7d345b
Author: Eike Rathke 
AuthorDate: Sun Nov 27 18:20:57 2022 +0100
Commit: Eike Rathke 
CommitDate: Sun Nov 27 20:10:17 2022 +0100

{pt-AO} change to untranslated YY, keywords, translated AA never worked

Apparently copied from {pt-PT} year AA and  format codes
should not had made it across but also never worked as
LANGUAGE_USER_PORTUGUESE_ANGOLA was missing in
ImpSvNumberformatScan::SetDependentKeywords() so date codes
displayed literal AA instead. Seems no one is using that locale
with dates..

Since

commit 5d833d37851597c1fb9076710d9eb03e4c94ca07
CommitDate: Fri Apr 8 20:51:13 2011 +0200

add pt_AO locale data (edited version of Mandrake's patch)

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

diff --git a/i18npool/source/localedata/data/pt_AO.xml 
b/i18npool/source/localedata/data/pt_AO.xml
index 138c401a6659..2ad917a1d622 100644
--- a/i18npool/source/localedata/data/pt_AO.xml
+++ b/i18npool/source/localedata/data/pt_AO.xml
@@ -66,13 +66,13 @@
   [NatNum12 upper CURRENCY]0,00
 
 
-  DD-MM-
+  DD-MM-
 
 
-  NN DD-MMM AA
+  NN DD-MMM YY
 
 
-  MM-AA
+  MM-YY
 
 
   DD-MMM
@@ -81,49 +81,49 @@
   
 
 
-  QQ AA
+  QQ YY
 
 
-  DD-MM-
+  DD-MM-
 
 
-  DD-MM-AA
+  DD-MM-YY
 
 
-  D "de"  "de" 
+  D "de"  "de" 
 
 
-  D "de" MMM "de" AA
+  D "de" MMM "de" YY
 
 
-  D "de" MMM "de" 
+  D "de" MMM "de" 
 
 
-  D "de"  "de" 
+  D "de"  "de" 
 
 
-  NN, D "de" MMM "de" AA
+  NN, D "de" MMM "de" YY
 
 
-  NN, D "de"  "de" 
+  NN, D "de"  "de" 
 
 
-  D "de"  "de" 
+  D "de"  "de" 
 
 
-  D. MMM. 
+  D. MMM. 
 
 
-  D.  
+  D.  
 
 
   MM-DD
 
 
-  AA-MM-DD
+  YY-MM-DD
 
 
-  -MM-DD
+  -MM-DD
   ISO 8601 (EN 28601)
 
 
@@ -151,13 +151,13 @@
   [HH]:MM:SS,00
 
 
-  DD-MM-AA HH:MM
+  DD-MM-YY HH:MM
 
 
-  DD-MM- HH:MM:SS
+  DD-MM- HH:MM:SS
 
 
-  DD-MM- HH:MM
+  DD-MM- HH:MM
 
 
   Geral


  1   2   3   >