[Libreoffice-bugs] [Bug 154344] LibreOffice Writer: Track Changes edits not saved in auto recovery

[bugzilla-daemon]

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

Dieter  changed:

   What|Removed |Added

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

--- Comment #1 from Dieter  ---
Thank you for reporting the bug. Does it also happen in Safe Mode (Help ->
Restart in Safe Mode)?
=> NEEDINFO

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

[Libreoffice-bugs] [Bug 148903] Description for ”page text area” is wrong in Position and Size tab and Image - Type tab

[bugzilla-daemon]

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

BogdanB  changed:

   What|Removed |Added

   Assignee|libreoffice-b...@lists.free |buzea.bog...@libreoffice.or
   |desktop.org |g
 Status|NEW |ASSIGNED

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

[Libreoffice-bugs] [Bug 154630] PDF creation ignores selection button

[bugzilla-daemon]

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

QA Administrators  changed:

   What|Removed |Added

 Status|NEEDINFO|UNCONFIRMED
 Ever confirmed|1   |0

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

[Libreoffice-bugs] [Bug 154630] PDF creation ignores selection button

[bugzilla-daemon]

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

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

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

[Libreoffice-bugs] [Bug 154344] LibreOffice Writer: Track Changes edits not saved in auto recovery

[bugzilla-daemon]

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

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 154548] _style_list

[bugzilla-daemon]

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

QA Administrators  changed:

   What|Removed |Added

 Status|NEEDINFO|UNCONFIRMED
 Ever confirmed|1   |0

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

[Libreoffice-ux-advise] [Bug 153537] FIELD DIALOG: Add possibility to assign character style to the field

[bugzilla-daemon]

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

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

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

[Libreoffice-bugs] [Bug 154548] _style_list

[bugzilla-daemon]

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

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

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

[Libreoffice-bugs] [Bug 153537] FIELD DIALOG: Add possibility to assign character style to the field

[bugzilla-daemon]

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

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

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

[Libreoffice-bugs] [Bug 97901] paste special with transpose activated fails with "not enough space on sheet"

[bugzilla-daemon]

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

--- Comment #11 from QA Administrators  ---
Dear documentfoundation,

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 44319] EDITING: numbering with {LISTNUM LegalDefault} code field not working

[bugzilla-daemon]

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

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

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 38631] Writer IMPORT/EXPORT to doc: extra spacing gets added to an embedded table

[bugzilla-daemon]

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

--- Comment #18 from QA Administrators  ---
Dear Rad C.,

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 139681] CALC AUTOFILL EDIT applies existing pattern inconsistently when source cell range contents are formulae

[bugzilla-daemon]

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

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

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 128955] Inserted cross-reference text is disappear on exported EPUB file

[bugzilla-daemon]

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

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

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 109374] Filesave XLS: autofilter shows different items checked

[bugzilla-daemon]

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

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

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 125220] Custom-created fields do not show in exported epub document

[bugzilla-daemon]

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

--- Comment #6 from QA Administrators  ---
Dear Joachim Wesenberg,

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 114903] Used character styles for footnotes and endnotes are not considered being used in Sidebar

[bugzilla-daemon]

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

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

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

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

If you have time, please do the following:

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

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

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

Please DO NOT

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


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

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


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

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

Warm Regards,
QA Team

MassPing-UntouchedBug

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

[Libreoffice-bugs] [Bug 101393] Picture copy-pasted from web with text having wrong dimensions

[bugzilla-daemon]

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

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

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 154614] OpenType features in Writer not working on foreign scripts

[bugzilla-daemon]

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

خالد حسني  changed:

   What|Removed |Added

 Ever confirmed|0   |1
 Status|UNCONFIRMED |NEW

--- Comment #7 from خالد حسني  ---
I confirm the original issue and I think it is a bug.

When CTL and Asian font widgets are hidden, the Western font widget does not
change Asian a CTL fonts (I think there are already bug reports about this),
and similarly font features dialog is only applied to Western font.

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

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

[Laurent Balland (via logerrit)]

 svl/qa/unit/svl.cxx|   12 
 svl/source/numbers/zformat.cxx |8 +---
 2 files changed, 17 insertions(+), 3 deletions(-)

New commits:
commit 072f84001b2d28915085909a4d9a5a52bd7f6b61
Author: Laurent Balland 
AuthorDate: Sun Mar 19 21:45:52 2023 +0100
Commit: Adolfo Jayme Barrientos 
CommitDate: Fri Apr 7 03:04:50 2023 +0200

tdf#153887 Fraction number format: avoid 0/0

If round value is an integer and there is no integer part in the number
format, then nDiv was wrongly forced to 0.
Add corresponding unit tests.

Change-Id: Ib69393eca8f6c2bdda0eacfc83637ab0c971ff2d
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/149118
Tested-by: Jenkins
Reviewed-by: Eike Rathke 
(cherry picked from commit dc9b8c31aaf72812dc205f610638098898a4cde7)
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/150085
Reviewed-by: Adolfo Jayme Barrientos 

diff --git a/svl/qa/unit/svl.cxx b/svl/qa/unit/svl.cxx
index 29bbde9b999d..2b9672d7602d 100644
--- a/svl/qa/unit/svl.cxx
+++ b/svl/qa/unit/svl.cxx
@@ -1448,6 +1448,18 @@ void Test::testUserDefinedNumberFormats()
 sExpected = "-575 540/697";
 checkPreviewString(aFormatter, sCode, -575.774749601315, eLang, 
sExpected);
 }
+{  // tdf#153887: integer value without integer part displayed
+sCode = "#/?";
+sExpected = "2/1";
+checkPreviewString(aFormatter, sCode, 1.95, eLang, sExpected);
+checkPreviewString(aFormatter, sCode, 2.00, eLang, sExpected);
+checkPreviewString(aFormatter, sCode, 2.05, eLang, sExpected);
+sCode = "0/8";
+sExpected = "16/8";
+checkPreviewString(aFormatter, sCode, 1.95, eLang, sExpected);
+checkPreviewString(aFormatter, sCode, 2.00, eLang, sExpected);
+checkPreviewString(aFormatter, sCode, 2.05, eLang, sExpected);
+}
 {  // tdf#102507: left alignment of denominator
 sCode = "# ?/???";
 sExpected = "3 1/2  ";
diff --git a/svl/source/numbers/zformat.cxx b/svl/source/numbers/zformat.cxx
index eb790ee425b0..a19b08375ecd 100644
--- a/svl/source/numbers/zformat.cxx
+++ b/svl/source/numbers/zformat.cxx
@@ -2835,9 +2835,10 @@ void SvNumberformat::ImpGetFractionElements ( double& 
fNumber, sal_uInt16 nIx,
 fIntPart = floor(fNumber); // Integral part
 fNumber -= fIntPart; // Fractional part
 const ImpSvNumberformatInfo& rInfo = NumFor[nIx].Info();
-nDiv = lcl_GetDenominatorString( rInfo, NumFor[nIx].GetCount() ).toInt32();
-if( nDiv > 0 )
+sal_Int64 nForcedDiv = lcl_GetDenominatorString( rInfo, 
NumFor[nIx].GetCount() ).toInt32();
+if( nForcedDiv > 0 )
 {   // Forced Denominator
+nDiv = nForcedDiv;
 nFrac = static_cast(floor ( fNumber * nDiv ));
 double fFracNew = static_cast(nFrac) / 
static_cast(nDiv);
 double fFracNew1 = static_cast(nFrac + 1) / 
static_cast(nDiv);
@@ -2891,7 +2892,8 @@ void SvNumberformat::ImpGetFractionElements ( double& 
fNumber, sal_uInt16 nIx,
 if (nFrac >= nDiv)
 {
 ++fIntPart;
-nFrac = nDiv = 0;
+nFrac = 0;
+nDiv = ( nForcedDiv > 0 ) ? nForcedDiv : 1;
 }
 }
 

[Libreoffice-bugs] [Bug 55133] COMMENT - added comment text gets invisible when fist row is set as header (MENU WINDOW FREEZE)

[bugzilla-daemon]

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

--- Comment #22 from ady  ---
(In reply to m.a.riosv from comment #21)
> Works for me

Then comment 17 should be converted into a new bug report, because that
behavior is still relevant.

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

[Libreoffice-bugs] [Bug 59977] EDITING: Copy table from Writer should paste to Calc also table even if pasted as unformatted text

[bugzilla-daemon]

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

--- Comment #8 from m.a.riosv  ---
Still
Version: 7.6.0.0.alpha0+ (X86_64) / LibreOffice Community
Build ID: d408e940630d131ab886a1d4619671fa0299c03e
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 Jumbo

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

[Libreoffice-bugs] [Bug 59391] Naming a cell causes certain references using labeled ranges to go undefined; recalculate/autocalculate

[bugzilla-daemon]

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

--- Comment #11 from m.a.riosv  ---
Still
Version: 7.5.2.2 (X86_64) / LibreOffice Community
Build ID: 53bb9681a964705cf672590721dbc85eb4d0c3a2
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
Version: 7.6.0.0.alpha0+ (X86_64) / LibreOffice Community
Build ID: d408e940630d131ab886a1d4619671fa0299c03e
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 Jumbo

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

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

[Regis Perdreau]

So, I agree with the proposal. L8 could be seen as a new start and not an
achievement... new developers mean new functionalities, evolving
organization. I think we can build something around that. Marketed as the
mix of different knowledge as distinguishing elements.

Regards,

Régis

Le ven. 7 avr. 2023 à 00:14, Italo Vignoli  a écrit :

> I have written that developers have a different mindset from marketing
> people. I have never said that developers are dumb people, and I have
> never even thought this.
>
> On 06/04/23 23:45, Regis Perdreau wrote:
> > Hi all,
> >
> > So if i understand correctly, developers are dumb people, talking only to
> > its computer, and marketer have the privilege to speak to real user...
> > Well, all the day, i speak to real user, and all say that marketers talk
> > non sense about Microsoft compatibility...
> > I wonder how to solve daily cognitive dissonnance
> > *
> > <
> https://context.reverso.net/traduction/anglais-francais/cognitive+dissonance
> >*
> > Just kidding
> >
> > Cheers,
> > Régis Perdreau
> >
> >
> >
> > Le jeu. 6 avr. 2023 à 23:00, Gustavo Buzzatti Pacheco <
> gbpach...@gmail.com>
> > a écrit :
> >
> >> Hi, Nigel, Ben, Eyal, all!
> >>
> >>   Let me add some comments. :)
> >>
> >>   For sure, the current approach is a requirement for our internal
> >> development organization, as Ben noted. Also, it was really important in
> >> the first years of LibreOffice/TDF, when we used it to demonstrate we
> were
> >> ahead of Apache OpenOffice for the users and the strong
> project/community
> >> we were building.
> >>
> >>   On the other hand, for the current moment of LibreOffice as a project
> and
> >> product, I think we can do more or different things. Nigel wrote
> >> exactly what I mean about 'boring' from the user perspective: most of
> the
> >> users don't care about minor changes.
> >>
> >>   So, I think, now, we should decide about releases with a Marketing
> >> perspective and the number 8 could be a first step to do it, even
> without
> >> big changes.
> >>
> >>   Could it mean we will do a marketing trick?
> >>
> >>   I think no, because we will be transparent with our users as we always
> >> have been. If the release won't have big improvements, we won't talk
> about
> >> big improvements.
> >>
> >>   Why release a version without big improvements?
> >>
> >>   That is the other point: I don't think we should focus only on big
> code
> >> improvements to use major version numbers (or even version names). We
> >> aren't only a product. We are a project and community. Indeed, the
> released
> >> product is our final work but a major version can also be used to spread
> >> (or celebrate) the maturity of the product/project/community. This is a
> >> different approach than paid software/non FLOSS. This is what I mean
> with
> >> consolidation.
> >>
> >>
> >> On Thu, Apr 6, 2023 at 8:22 AM Nigel Verity 
> >> wrote:
> >>
> >>> Hi Gustavo
> >>>
> >>> This is a very good point.
> >>>
> >>> If I see that some software I use regularly has gone from 7.5 to 7.6,
> >>> say, I wouldn't rush to upgrade unless I knew it fixed a problem that
> >>> affected me. I'm pretty sure that I would upgrade from 7.5 to to 8.0
> far
> >>> more quickly, if for no other reason that the psychological one of
> wanting
> >>> to be using what my head tells me must be an improvement over my
> current
> >>> version.
> >>>
> >>> Of course release notes are available to determine what really has
> >>> changed but I rather suspect that most users never read them.
> >>>
> >>> The discussion of the different motivators for development and
> marketing
> >>> people is very interesting. When I was a developer neither I nor
> anybody in
> >>> my teams was ever let anywhere near sales activities - and I think for
> very
> >>> good reasons.
> >>>
> >>> Cheers
> >>>
> >>> Nige
> >>>
> >>>
> >>> * LibreOffice - Free and open source office suite: LibreOffice Website
> >>>  *
> >>> * Respects your privacy, and gives you back control over your data*
> >>> --
> >>> *From:* Gustavo Buzzatti Pacheco 
> >>> *Sent:* 05 April 2023 22:05
> >>> *To:* TDF Devs ; TDF Marketing <
> >>> market...@global.libreoffice.org>; TDF Design <
> >>> des...@global.libreoffice.org>
> >>> *Subject:* Re: [libreoffice-marketing] Re: [libreoffice-design] Moving
> >>> to LibreOffice 8?
> >>>
> >>> Hi Eyal, all!
> >>>
> >>>   I also respectfully disagree with you on some points. ;D
> >>>
> >>>   I like the idea to move to 8, even with no big technical innovation
> (if
> >>> we
> >>> have, for sure it will be better).
> >>>
> >>>   IMHO, long sequences of minor releases (7.6, in the current case) are
> >>> getting boring and not important for the users (for both enterprise and
> >>> individual profiles).
> >>>
> >>>   I'm not saying that we should embrace the Firefox approach, but
> thinking
> >>> about Italo's idea (8 <-> infinite), I guess the message of this
> version
> >>> 

[Libreoffice-bugs] [Bug 101216] [META] Calc comment bugs and enhancements

[bugzilla-daemon]

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

Bug 55133 Summary: COMMENT - added comment text gets invisible when fist row is 
set as header (MENU WINDOW FREEZE)
https://bugs.documentfoundation.org/show_bug.cgi?id=55133

   What|Removed |Added

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

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

[Libreoffice-bugs] [Bug 55133] COMMENT - added comment text gets invisible when fist row is set as header (MENU WINDOW FREEZE)

[bugzilla-daemon]

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

m.a.riosv  changed:

   What|Removed |Added

 CC||miguelangelrv@libreoffice.o
   ||rg
 Resolution|--- |WORKSFORME
 Status|NEW |RESOLVED

--- Comment #21 from m.a.riosv  ---
Works for me

Version: 7.5.2.2 (X86_64) / LibreOffice Community
Build ID: 53bb9681a964705cf672590721dbc85eb4d0c3a2
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

Version: 7.6.0.0.alpha0+ (X86_64) / LibreOffice Community
Build ID: d408e940630d131ab886a1d4619671fa0299c03e
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 Jumbo

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

[Libreoffice-bugs] [Bug 55131] Comments: "freeze cells" indicator line visible in comment

[bugzilla-daemon]

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

m.a.riosv  changed:

   What|Removed |Added

 CC||miguelangelrv@libreoffice.o
   ||rg

--- Comment #14 from m.a.riosv  ---
Still
Version: 7.6.0.0.alpha0+ (X86_64) / LibreOffice Community
Build ID: d408e940630d131ab886a1d4619671fa0299c03e
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 Jumbo

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

[Libreoffice-bugs] [Bug 51732] PIVOTTABLE: Formating Pivot Tables

[bugzilla-daemon]

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

--- Comment #6 from m.a.riosv  ---
Recurrent question in forum
https://ask.libreoffice.org/search?q=pivot%20table%20format

If it were at least possible, do not remove conditional formatting.

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

[Libreoffice-bugs] [Bug 154614] OpenType features in Writer not working on foreign scripts

[bugzilla-daemon]

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

--- Comment #6 from Dealey Maples  ---
Thanks, it worked!

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

[Libreoffice-bugs] [Bug 51732] PIVOTTABLE: Formating Pivot Tables

[bugzilla-daemon]

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

m.a.riosv  changed:

   What|Removed |Added

 CC||miguelangelrv@libreoffice.o
   ||rg

--- Comment #5 from m.a.riosv  ---
Still
Version: 7.6.0.0.alpha0+ (X86_64) / LibreOffice Community
Build ID: d408e940630d131ab886a1d4619671fa0299c03e
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 Jumbo

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

[Libreoffice-bugs] [Bug 154406] Euro symbol not printed

[bugzilla-daemon]

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

Dieter  changed:

   What|Removed |Added

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

--- Comment #2 from Dieter  ---
Laurens, could you please retest with LO 7.5.2? Is the bug still present there?
=> NEEDINFO

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

[Libreoffice-bugs] [Bug 154400] Manual Set Reference and insert reference is cumbersome and incomplete

[bugzilla-daemon]

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

Dieter  changed:

   What|Removed |Added

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

--- Comment #2 from Dieter  ---
Sailnfool, could people solve your problem at ask.Libreoffice.com?
=> NEEDINFO

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

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

[Italo Vignoli]

I have written that developers have a different mindset from marketing 
people. I have never said that developers are dumb people, and I have 
never even thought this.


On 06/04/23 23:45, Regis Perdreau wrote:

Hi all,

So if i understand correctly, developers are dumb people, talking only to
its computer, and marketer have the privilege to speak to real user...
Well, all the day, i speak to real user, and all say that marketers talk
non sense about Microsoft compatibility...
I wonder how to solve daily cognitive dissonnance
*
*
Just kidding

Cheers,
Régis Perdreau



Le jeu. 6 avr. 2023 à 23:00, Gustavo Buzzatti Pacheco 
a écrit :


Hi, Nigel, Ben, Eyal, all!

  Let me add some comments. :)

  For sure, the current approach is a requirement for our internal
development organization, as Ben noted. Also, it was really important in
the first years of LibreOffice/TDF, when we used it to demonstrate we were
ahead of Apache OpenOffice for the users and the strong project/community
we were building.

  On the other hand, for the current moment of LibreOffice as a project and
product, I think we can do more or different things. Nigel wrote
exactly what I mean about 'boring' from the user perspective: most of the
users don't care about minor changes.

  So, I think, now, we should decide about releases with a Marketing
perspective and the number 8 could be a first step to do it, even without
big changes.

  Could it mean we will do a marketing trick?

  I think no, because we will be transparent with our users as we always
have been. If the release won't have big improvements, we won't talk about
big improvements.

  Why release a version without big improvements?

  That is the other point: I don't think we should focus only on big code
improvements to use major version numbers (or even version names). We
aren't only a product. We are a project and community. Indeed, the released
product is our final work but a major version can also be used to spread
(or celebrate) the maturity of the product/project/community. This is a
different approach than paid software/non FLOSS. This is what I mean with
consolidation.


On Thu, Apr 6, 2023 at 8:22 AM Nigel Verity 
wrote:


Hi Gustavo

This is a very good point.

If I see that some software I use regularly has gone from 7.5 to 7.6,
say, I wouldn't rush to upgrade unless I knew it fixed a problem that
affected me. I'm pretty sure that I would upgrade from 7.5 to to 8.0 far
more quickly, if for no other reason that the psychological one of wanting
to be using what my head tells me must be an improvement over my current
version.

Of course release notes are available to determine what really has
changed but I rather suspect that most users never read them.

The discussion of the different motivators for development and marketing
people is very interesting. When I was a developer neither I nor anybody in
my teams was ever let anywhere near sales activities - and I think for very
good reasons.

Cheers

Nige


* LibreOffice - Free and open source office suite: LibreOffice Website
 *
* Respects your privacy, and gives you back control over your data*
--
*From:* Gustavo Buzzatti Pacheco 
*Sent:* 05 April 2023 22:05
*To:* TDF Devs ; TDF Marketing <
market...@global.libreoffice.org>; TDF Design <
des...@global.libreoffice.org>
*Subject:* Re: [libreoffice-marketing] Re: [libreoffice-design] Moving
to LibreOffice 8?

Hi Eyal, all!

  I also respectfully disagree with you on some points. ;D

  I like the idea to move to 8, even with no big technical innovation (if
we
have, for sure it will be better).

  IMHO, long sequences of minor releases (7.6, in the current case) are
getting boring and not important for the users (for both enterprise and
individual profiles).

  I'm not saying that we should embrace the Firefox approach, but thinking
about Italo's idea (8 <-> infinite), I guess the message of this version
could be consolidation, not exactly innovation.

Best
Gustavo


On Tue, Mar 28, 2023 at 4:23 AM Eyal Rozenberg  wrote:


I respectfully disagree with Italo.

First, about the "frame of reference". In my opinion, decisions such as
major version number bumping are not, first and foremost, marketing
decisions. That is a _consideration_, since the version number is
declarative than technical. But - such an action should be "truthful"
before being "marketable".

It is more important, in my opinion, that users and potential users
receive trustworthy signaling from the project - not just w.r.t. version
numbers, but generally - than for the media to get a gimmick for

coverage.


A second point is that bumping a version number without a major
innovation moves you a few more steps into the category of, say, Firefox
and such, where versions just increase automatically with no meaning
whatsoever. Italo, you said we are perceived as a "real innovator";

[Libreoffice-bugs] [Bug 154365] Libre Office Write 7.4.6 not fully accessing USB memory stick. Keywords :- fileopen filesave

[bugzilla-daemon]

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

Dieter  changed:

   What|Removed |Added

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

--- Comment #3 from Dieter  ---
Jon, could you please retest with LO 7.5 and also in Safe Mode?
 Thank you
=> NEEDINFO

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

[Libreoffice-bugs] [Bug 45862] [EDITING] Menu/Data/Consolidate, Only the last range to consolidate is saved in the file.

[bugzilla-daemon]

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

--- Comment #14 from m.a.riosv  ---
Still
Version: 7.6.0.0.alpha0+ (X86_64) / LibreOffice Community
Build ID: d408e940630d131ab886a1d4619671fa0299c03e
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 Jumbo

Seems nobody uses this option, me neither

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

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

[Patrick Luby (via logerrit)]

 svx/source/svdraw/svdomedia.cxx |1 -
 1 file changed, 1 deletion(-)

New commits:
commit 375f85f8518f49ce4381b6663f1e94fc02bacf93
Author: Patrick Luby 
AuthorDate: Thu Apr 6 14:44:52 2023 -0400
Commit: Patrick Luby 
CommitDate: Thu Apr 6 23:54:04 2023 +0200

Fix iOS build failure in commit a5225ba82e94a549f44420f56a7cb9d7906561cc

Change-Id: I5f4fe093c77f2faf91c6512ed5c294a4f2389757
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/150111
Tested-by: Jenkins
Reviewed-by: Patrick Luby 

diff --git a/svx/source/svdraw/svdomedia.cxx b/svx/source/svdraw/svdomedia.cxx
index 73b19ca78773..0bb99f1ae46f 100644
--- a/svx/source/svdraw/svdomedia.cxx
+++ b/svx/source/svdraw/svdomedia.cxx
@@ -258,7 +258,6 @@ void SdrMediaObj::setURL(const OUString& rURL, const 
OUString& rReferer)
 #if HAVE_FEATURE_AVMEDIA
 aURLItem.setURL( rURL, "", rReferer );
 #else
-(void) rMimeType;
 (void) rURL;
 (void) rReferer;
 #endif

[Libreoffice-bugs] [Bug 42496] Calc EDITING: improve functionality when Formula gets in a way while editing and prevents selection of the adjacent cell.

[bugzilla-daemon]

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

m.a.riosv  changed:

   What|Removed |Added

 CC||miguelangelrv@libreoffice.o
   ||rg

--- Comment #7 from m.a.riosv  ---
Still
Version: 7.6.0.0.alpha0+ (X86_64) / LibreOffice Community
Build ID: d408e940630d131ab886a1d4619671fa0299c03e
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 Jumbo

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

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

[Regis Perdreau]

Hi all,

So if i understand correctly, developers are dumb people, talking only to
its computer, and marketer have the privilege to speak to real user...
Well, all the day, i speak to real user, and all say that marketers talk
non sense about Microsoft compatibility...
I wonder how to solve daily cognitive dissonnance
*
*
Just kidding

Cheers,
Régis Perdreau



Le jeu. 6 avr. 2023 à 23:00, Gustavo Buzzatti Pacheco 
a écrit :

> Hi, Nigel, Ben, Eyal, all!
>
>  Let me add some comments. :)
>
>  For sure, the current approach is a requirement for our internal
> development organization, as Ben noted. Also, it was really important in
> the first years of LibreOffice/TDF, when we used it to demonstrate we were
> ahead of Apache OpenOffice for the users and the strong project/community
> we were building.
>
>  On the other hand, for the current moment of LibreOffice as a project and
> product, I think we can do more or different things. Nigel wrote
> exactly what I mean about 'boring' from the user perspective: most of the
> users don't care about minor changes.
>
>  So, I think, now, we should decide about releases with a Marketing
> perspective and the number 8 could be a first step to do it, even without
> big changes.
>
>  Could it mean we will do a marketing trick?
>
>  I think no, because we will be transparent with our users as we always
> have been. If the release won't have big improvements, we won't talk about
> big improvements.
>
>  Why release a version without big improvements?
>
>  That is the other point: I don't think we should focus only on big code
> improvements to use major version numbers (or even version names). We
> aren't only a product. We are a project and community. Indeed, the released
> product is our final work but a major version can also be used to spread
> (or celebrate) the maturity of the product/project/community. This is a
> different approach than paid software/non FLOSS. This is what I mean with
> consolidation.
>
>
> On Thu, Apr 6, 2023 at 8:22 AM Nigel Verity 
> wrote:
>
>> Hi Gustavo
>>
>> This is a very good point.
>>
>> If I see that some software I use regularly has gone from 7.5 to 7.6,
>> say, I wouldn't rush to upgrade unless I knew it fixed a problem that
>> affected me. I'm pretty sure that I would upgrade from 7.5 to to 8.0 far
>> more quickly, if for no other reason that the psychological one of wanting
>> to be using what my head tells me must be an improvement over my current
>> version.
>>
>> Of course release notes are available to determine what really has
>> changed but I rather suspect that most users never read them.
>>
>> The discussion of the different motivators for development and marketing
>> people is very interesting. When I was a developer neither I nor anybody in
>> my teams was ever let anywhere near sales activities - and I think for very
>> good reasons.
>>
>> Cheers
>>
>> Nige
>>
>>
>> * LibreOffice - Free and open source office suite: LibreOffice Website
>>  *
>> * Respects your privacy, and gives you back control over your data*
>> --
>> *From:* Gustavo Buzzatti Pacheco 
>> *Sent:* 05 April 2023 22:05
>> *To:* TDF Devs ; TDF Marketing <
>> market...@global.libreoffice.org>; TDF Design <
>> des...@global.libreoffice.org>
>> *Subject:* Re: [libreoffice-marketing] Re: [libreoffice-design] Moving
>> to LibreOffice 8?
>>
>> Hi Eyal, all!
>>
>>  I also respectfully disagree with you on some points. ;D
>>
>>  I like the idea to move to 8, even with no big technical innovation (if
>> we
>> have, for sure it will be better).
>>
>>  IMHO, long sequences of minor releases (7.6, in the current case) are
>> getting boring and not important for the users (for both enterprise and
>> individual profiles).
>>
>>  I'm not saying that we should embrace the Firefox approach, but thinking
>> about Italo's idea (8 <-> infinite), I guess the message of this version
>> could be consolidation, not exactly innovation.
>>
>> Best
>> Gustavo
>>
>>
>> On Tue, Mar 28, 2023 at 4:23 AM Eyal Rozenberg  wrote:
>>
>> > I respectfully disagree with Italo.
>> >
>> > First, about the "frame of reference". In my opinion, decisions such as
>> > major version number bumping are not, first and foremost, marketing
>> > decisions. That is a _consideration_, since the version number is
>> > declarative than technical. But - such an action should be "truthful"
>> > before being "marketable".
>> >
>> > It is more important, in my opinion, that users and potential users
>> > receive trustworthy signaling from the project - not just w.r.t. version
>> > numbers, but generally - than for the media to get a gimmick for
>> coverage.
>> >
>> > A second point is that bumping a version number without a major
>> > innovation moves you a few more steps into the category of, say, Firefox
>> > and such, where versions just increase automatically with no meaning

[Libreoffice-bugs] [Bug 42365] FORMATTING: some function names in Formula Editor appears in italic

[bugzilla-daemon]

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

--- Comment #12 from m.a.riosv  ---
Still
Version: 7.6.0.0.alpha0+ (X86_64) / LibreOffice Community
Build ID: d408e940630d131ab886a1d4619671fa0299c03e
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 Jumbo

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

[Libreoffice-bugs] [Bug 42261] display of selected cells incorrect after inserting row/column above/left of selection

[bugzilla-daemon]

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

--- Comment #17 from m.a.riosv  ---
Still
Version: 7.6.0.0.alpha0+ (X86_64) / LibreOffice Community
Build ID: d408e940630d131ab886a1d4619671fa0299c03e
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 Jumbo

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

[Libreoffice-bugs] [Bug 39560] UI: Columns in Format-Page-Columns-dialog are equalized in some situations

[bugzilla-daemon]

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

m.a.riosv  changed:

   What|Removed |Added

 CC||miguelangelrv@libreoffice.o
   ||rg

--- Comment #18 from m.a.riosv  ---
Still
Version: 7.5.2.2 (X86_64) / LibreOffice Community
Build ID: 53bb9681a964705cf672590721dbc85eb4d0c3a2
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
Version: 7.6.0.0.alpha0+ (X86_64) / LibreOffice Community
Build ID: d408e940630d131ab886a1d4619671fa0299c03e
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 Jumbo

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

[Libreoffice-bugs] [Bug 154525] [sample] Calc is extremely slow (3+ minutes) to open Lenovo's Accessories "Options Compatibility Matrix" spreadsheet

[bugzilla-daemon]

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

ady  changed:

   What|Removed |Added

 Status|UNCONFIRMED |NEW
 Ever confirmed|0   |1

--- Comment #7 from ady  ---
Also under Win10. > NEW.

I have not tested with other spreadsheet tools.

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

[Libreoffice-bugs] [Bug 154690] Add some Change-Case commands to the context menu for cell text

[bugzilla-daemon]

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

Eyal Rozenberg  changed:

   What|Removed |Added

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

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

[Libreoffice-bugs] [Bug 154525] [sample] Calc is extremely slow (3+ minutes) to open Lenovo's Accessories "Options Compatibility Matrix" spreadsheet

[bugzilla-daemon]

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

--- Comment #6 from Jeff Fortin Tam  ---
Not X11-specific, and potentially not graphics-stack-related: I also tested on
Wayland with an Intel Xeon W3520 CPU (8 logical CPUs) and AMD Radeon "Pitcairn"
R270 graphics, and it takes the same time to open this sheet.

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

[Libreoffice-bugs] [Bug 154551] Cutting a caption from a frame results in crash

[bugzilla-daemon]

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

--- Comment #9 from Telesto  ---
(In reply to Telesto from comment #4)
> (In reply to sdc.blanco from comment #3)
> Hmm. Still not able to repro the exact steps, however I got a crash in same
> area
> 
> 1. Insert a shape.
> 2. Select shape, right-click, choose "Insert Caption"
> 3. Press with the caption frame selected CTRL+X (or select the caption
> within the frame)
> 4. Press CTRL+F4 or Red Close LibreOffice button 
> 5. Don't save on warning -> Crash

@Buovjaga
Would you mind to try these steps too..

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

[Libreoffice-commits] core.git: include/oox include/sax oox/source sax/qa sax/source sw/source

[Mike Kaganski (via logerrit)]

 include/oox/export/vmlexport.hxx |2 
 include/sax/fastattribs.hxx  |   21 -
 include/sax/fshelper.hxx |4 
 oox/source/export/vmlexport.cxx  |6 
 sax/qa/cppunit/attributes.cxx|   14 
 sax/source/fastparser/fastparser.cxx |   57 +--
 sax/source/tools/fastattribs.cxx |   41 --
 sax/source/tools/fastserializer.cxx  |4 
 sax/source/tools/fastserializer.hxx  |2 
 sw/source/filter/ww8/docxattributeoutput.cxx |  505 ++-
 sw/source/filter/ww8/docxattributeoutput.hxx |   27 -
 sw/source/filter/ww8/docxsdrexport.cxx   |   45 +-
 sw/source/filter/ww8/docxtableexport.cxx |   45 +-
 13 files changed, 319 insertions(+), 454 deletions(-)

New commits:
commit d856be879e0b94b36c8f87817de74189a8a04121
Author: Mike Kaganski 
AuthorDate: Thu Apr 6 07:29:56 2023 +0300
Commit: Mike Kaganski 
CommitDate: Thu Apr 6 23:02:16 2023 +0200

Use more *string_view

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

diff --git a/include/oox/export/vmlexport.hxx b/include/oox/export/vmlexport.hxx
index fb53ec099f7a..f6b9869dae7a 100644
--- a/include/oox/export/vmlexport.hxx
+++ b/include/oox/export/vmlexport.hxx
@@ -158,7 +158,7 @@ protected:
 ///
 /// This should be called from within StartShape() to ensure that the
 /// added attribute is preserved.
-voidAddShapeAttribute( sal_Int32 nAttribute, const 
OString& sValue );
+void AddShapeAttribute(sal_Int32 nAttribute, std::string_view sValue);
 
 using EscherEx::StartShape;
 using EscherEx::EndShape;
diff --git a/include/sax/fastattribs.hxx b/include/sax/fastattribs.hxx
index 2dc7c3d72420..61eb048e881a 100644
--- a/include/sax/fastattribs.hxx
+++ b/include/sax/fastattribs.hxx
@@ -62,14 +62,13 @@ class SAX_DLLPUBLIC FastTokenHandlerBase :
 /**
  * Client method to attempt the use of this interface if possible.
  * @xTokenHandler - the token lookup interface
- * @pStr - string buffer to lookup
- * @nLength - optional length of chars in that buffer
+ * @str - string buffer to lookup
  *
- * @return Tokenized form of pStr
+ * @return Tokenized form of str
  */
 static sal_Int32 getTokenFromChars(
  const FastTokenHandlerBase *pTokenHandler,
- const char *pStr, size_t nLength );
+ std::string_view str );
 };
 
 
@@ -88,11 +87,17 @@ public:
 }
 void add( const FastAttributeList& );
 void add( const css::uno::Reference& );
-void add( sal_Int32 nToken, const char* pValue );
-void add( sal_Int32 nToken, const char* pValue, size_t nValueLength );
-void add( sal_Int32 nToken, const OString& rValue );
+void add( sal_Int32 nToken, std::string_view value );
 void add( sal_Int32 nToken, std::u16string_view sValue ); // Converts to 
UTF-8
-void addNS( sal_Int32 nNamespaceToken, sal_Int32 nToken, const OString& 
rValue );
+template 
+void add( sal_Int32 nToken, rtl::StringConcat&& value) { 
add(nToken, Concat2View(value)); }
+template  0), int> = 0>
+void add( sal_Int32 nToken, Val&& val, Rest&&... rest )
+{
+add(nToken, std::forward(val));
+add(std::forward(rest)...);
+}
+void addNS( sal_Int32 nNamespaceToken, sal_Int32 nToken, std::string_view 
sValue );
 void addNS( sal_Int32 nNamespaceToken, sal_Int32 nToken, 
std::u16string_view sValue );
 // note: rQName is *namespace-prefixed*
 void addUnknown( const OUString& rNamespaceURL, const OString& rQName, 
const OString& value );
diff --git a/include/sax/fshelper.hxx b/include/sax/fshelper.hxx
index 338260861132..74e2ed4e3254 100644
--- a/include/sax/fshelper.hxx
+++ b/include/sax/fshelper.hxx
@@ -126,12 +126,8 @@ public:
 { endElement( FSNS( namespaceTokenId, elementTokenId ) ); }
 
 void singleElement(sal_Int32 elementTokenId, const 
rtl::Reference& xAttrList);
-void singleElementNS(sal_Int32 namespaceTokenId, sal_Int32 elementTokenId, 
rtl::Reference const & xAttrList)
-{ singleElement(FSNS( namespaceTokenId, elementTokenId), xAttrList); }
 
 void startElement(sal_Int32 elementTokenId, const 
rtl::Reference& xAttrList);
-void startElementNS(sal_Int32 namespaceTokenId, sal_Int32 elementTokenId, 
rtl::Reference const & xAttrList)
-{ startElement( FSNS( namespaceTokenId, elementTokenId ), xAttrList ); 
}
 
 FastSerializerHelper* write(const char* value);
 FastSerializerHelper* write(const OString& value);
diff --git a/oox/source/export/vmlexport.cxx b/oox/source/export/vmlexport.cxx
index 7cbfe1f14bfa..38d3b9feacd1 100644
--- a/oox/source/export/vmlexport.cxx
+++ b/oox/source/export/vmlexport.cxx
@@ -158,7 +158,7 @@ sal_uInt32 VMLExport::EnterGroup( const 

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

[Gustavo Buzzatti Pacheco]

Hi, Nigel, Ben, Eyal, all!

 Let me add some comments. :)

 For sure, the current approach is a requirement for our internal
development organization, as Ben noted. Also, it was really important in
the first years of LibreOffice/TDF, when we used it to demonstrate we were
ahead of Apache OpenOffice for the users and the strong project/community
we were building.

 On the other hand, for the current moment of LibreOffice as a project and
product, I think we can do more or different things. Nigel wrote
exactly what I mean about 'boring' from the user perspective: most of the
users don't care about minor changes.

 So, I think, now, we should decide about releases with a Marketing
perspective and the number 8 could be a first step to do it, even without
big changes.

 Could it mean we will do a marketing trick?

 I think no, because we will be transparent with our users as we always
have been. If the release won't have big improvements, we won't talk about
big improvements.

 Why release a version without big improvements?

 That is the other point: I don't think we should focus only on big code
improvements to use major version numbers (or even version names). We
aren't only a product. We are a project and community. Indeed, the released
product is our final work but a major version can also be used to spread
(or celebrate) the maturity of the product/project/community. This is a
different approach than paid software/non FLOSS. This is what I mean with
consolidation.


On Thu, Apr 6, 2023 at 8:22 AM Nigel Verity  wrote:

> Hi Gustavo
>
> This is a very good point.
>
> If I see that some software I use regularly has gone from 7.5 to 7.6, say,
> I wouldn't rush to upgrade unless I knew it fixed a problem that affected
> me. I'm pretty sure that I would upgrade from 7.5 to to 8.0 far more
> quickly, if for no other reason that the psychological one of wanting to be
> using what my head tells me must be an improvement over my current version.
>
> Of course release notes are available to determine what really has changed
> but I rather suspect that most users never read them.
>
> The discussion of the different motivators for development and marketing
> people is very interesting. When I was a developer neither I nor anybody in
> my teams was ever let anywhere near sales activities - and I think for very
> good reasons.
>
> Cheers
>
> Nige
>
>
> * LibreOffice - Free and open source office suite: LibreOffice Website
>  *
> * Respects your privacy, and gives you back control over your data*
> --
> *From:* Gustavo Buzzatti Pacheco 
> *Sent:* 05 April 2023 22:05
> *To:* TDF Devs ; TDF Marketing <
> market...@global.libreoffice.org>; TDF Design <
> des...@global.libreoffice.org>
> *Subject:* Re: [libreoffice-marketing] Re: [libreoffice-design] Moving to
> LibreOffice 8?
>
> Hi Eyal, all!
>
>  I also respectfully disagree with you on some points. ;D
>
>  I like the idea to move to 8, even with no big technical innovation (if we
> have, for sure it will be better).
>
>  IMHO, long sequences of minor releases (7.6, in the current case) are
> getting boring and not important for the users (for both enterprise and
> individual profiles).
>
>  I'm not saying that we should embrace the Firefox approach, but thinking
> about Italo's idea (8 <-> infinite), I guess the message of this version
> could be consolidation, not exactly innovation.
>
> Best
> Gustavo
>
>
> On Tue, Mar 28, 2023 at 4:23 AM Eyal Rozenberg  wrote:
>
> > I respectfully disagree with Italo.
> >
> > First, about the "frame of reference". In my opinion, decisions such as
> > major version number bumping are not, first and foremost, marketing
> > decisions. That is a _consideration_, since the version number is
> > declarative than technical. But - such an action should be "truthful"
> > before being "marketable".
> >
> > It is more important, in my opinion, that users and potential users
> > receive trustworthy signaling from the project - not just w.r.t. version
> > numbers, but generally - than for the media to get a gimmick for
> coverage.
> >
> > A second point is that bumping a version number without a major
> > innovation moves you a few more steps into the category of, say, Firefox
> > and such, where versions just increase automatically with no meaning
> > whatsoever. Italo, you said we are perceived as a "real innovator";
> > well, when a real innovator starts having hollow version number bumping,
> > that perception fades.
> >
> > Finally, everyone who likes the marketing potential of version 8 -
> > great, but - keep that benefit for when we have a significant step
> > forward to celebrate. Don't squander it.
> >
> >
> > Eyal
> >
> > PS:  availability on a new platform is not a reason to bump a version
> > number. It's the "same" software, but built for another target, so same
> > version as before. IMHO anyway.
> >
> >
> >
> > On 27/03/2023 20:11, Italo Vignoli wrote:
> > > Moving to 

[Libreoffice-bugs] [Bug 154690] Add some Change-Case commands to the context menu for cell text

[bugzilla-daemon]

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

m.a.riosv  changed:

   What|Removed |Added

 CC||miguelangelrv@libreoffice.o
   ||rg

--- Comment #3 from m.a.riosv  ---
We can't make an infinite context menu.

For these cases, there is the customize option.

We had better stop thinking that our interest is everyone's interest.

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

[Libreoffice-bugs] [Bug 154688] en_GB Dictionary maintainer bouncing

[bugzilla-daemon]

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

--- Comment #5 from Jonny Grant  ---
(In reply to Marco A.G.Pinto from comment #4)
> I can't remove it since he was the creator.
> 
> An admin must decide what is best.

Ah yes, ok I see.

Thank you for taking on the maintainer role.
Jonny

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

[Libreoffice-bugs] [Bug 154692] New: Dictionary maintainer links are not all working

[bugzilla-daemon]

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

Bug ID: 154692
   Summary: Dictionary maintainer links are not all working
   Product: LibreOffice
   Version: 7.6.0.0 alpha0+ Master
  Hardware: All
OS: All
Status: UNCONFIRMED
  Severity: normal
  Priority: medium
 Component: Localization
  Assignee: libreoffice-bugs@lists.freedesktop.org
  Reporter: j...@jguk.org

Dictionary maintainer links aren't all working.
https://wiki.documentfoundation.org/Development/Dictionaries


Some other links broken:

http://alioth.debian.org/projects/spell-norwegian
http://oriya.sarovar.org/hi-dict.html
http://borel.slu.edu/

http://gitorious.org/dict-sr
^ faulty certificate

This is a redirect that could be updated
https://sjp.pl/
https://github.com/thamizha/solthiruthi redirected to
https://github.com/thamizha/thamizha-solthiruthi
http://www.stavekontrolden.dk/ redirected to https://stavekontrolden.dk

http://magyarispell.sf.net/ redirected to https://magyarispell.sourceforge.net/
http://code.google.com/p/hunspell-spellcheck-vi redirected to
https://github.com/1ec5/hunspell-vi
http://code.google.com/p/spell-uk redirected to
https://code.google.com/archive/p/spell-uk
http://www.drouizig.org/ redirected to http://www.drouizig.org/index.php/br/
http://rospell.sourceforge.net/ redirected to https://rospell.sourceforge.net/

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

[Libreoffice-bugs] [Bug 154688] en_GB Dictionary maintainer bouncing

[bugzilla-daemon]

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

--- Comment #4 from Marco A.G.Pinto  ---
I can't remove it since he was the creator.

An admin must decide what is best.

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

[Libreoffice-bugs] [Bug 154691] Cycle Case command doesn't work during cell edit

[bugzilla-daemon]

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

ady  changed:

   What|Removed |Added

Summary|Cycle Case command doens't  |Cycle Case command doesn't
   |work during cell edit   |work during cell edit

--- Comment #1 from ady  ---
Even if you select specific characters within a cell, the Cycle Case command
seems to apply to the whole cell, not to the specific selected text.

Other Casing formats (e.g. UPPERCASE) can be applied to the selected text, and
the characters are still selected/highlighted after the command was applied, so
additional commands/attributes can be applied to the same selection.

In contrast, selecting specific characters within a cell, the Cycle Case
command will act on the whole cell and previously-selected text will not be
selected (highlighted) anymore.

I have not tested what exactly happens with the Casing of the whole cell
according to several possible initial combinations of upper and lower case
characters, because currently it doesn't apply to the situation presented in
comment 0.

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

[Libreoffice-bugs] [Bug 154682] AutoCaption does not apply to an Image cut and pasted within a document or pasted to another document

[bugzilla-daemon]

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

sdc.bla...@youmail.dk changed:

   What|Removed |Added

 Blocks||154686


Referenced Bugs:

https://bugs.documentfoundation.org/show_bug.cgi?id=154686
[Bug 154686] "Apply border and shadow" option should be removed from
AutoCaption dialog
-- 
You are receiving this mail because:
You are the assignee for the bug.

[Libreoffice-bugs] [Bug 154686] "Apply border and shadow" option should be removed from AutoCaption dialog

[bugzilla-daemon]

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

sdc.bla...@youmail.dk changed:

   What|Removed |Added

 Depends on||154682


Referenced Bugs:

https://bugs.documentfoundation.org/show_bug.cgi?id=154682
[Bug 154682] AutoCaption does not apply to an Image cut and pasted within a
document or pasted to another document
-- 
You are receiving this mail because:
You are the assignee for the bug.

[Libreoffice-ux-advise] [Bug 154682] AutoCaption does not apply to an Image cut and pasted within a document or pasted to another document

[bugzilla-daemon]

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

sdc.bla...@youmail.dk changed:

   What|Removed |Added

 Blocks||154686


Referenced Bugs:

https://bugs.documentfoundation.org/show_bug.cgi?id=154686
[Bug 154686] "Apply border and shadow" option should be removed from
AutoCaption dialog
-- 
You are receiving this mail because:
You are on the CC list for the bug.

[Libreoffice-bugs] [Bug 154690] Add some Change-Case commands to the context menu for cell text

[bugzilla-daemon]

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

--- Comment #2 from Eyal Rozenberg  ---
(In reply to ady from comment #1)

Hmm, yeah, sorry about that. I'll make this bug more specific (although I
realize some might not support the specific request.)

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

[Libreoffice-bugs] [Bug 154690] Add some Change-Case commands to the context menu for cell text

[bugzilla-daemon]

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

Eyal Rozenberg  changed:

   What|Removed |Added

Summary|Make Change-Case commands   |Add some Change-Case
   |more accessible in Calc |commands to the context
   |menus   |menu for cell text

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

[Libreoffice-bugs] [Bug 154688] en_GB Dictionary maintainer bouncing

[bugzilla-daemon]

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

--- Comment #3 from Jonny Grant  ---
Hi that is great the page could be updated to link to
https://proofingtoolgui.org/

I did see it still refers to "[David Bartlett]" If it is already 10 years since
he was active, is it reasonable to not have him listed?

https://wiki.documentfoundation.org/Development/Dictionaries

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

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

[Eyal Rozenberg]

To put last thing first: I'm not staunchly opposed to bumping the 
version number to 8. So think of this as a theoretical discussion.


Anyway...

Noting Italo's explanation that:
> 80% (and probably more) of what we communicate is targeted to 
"normal" software users, and not to community members or to people with 
a technical background, who are already using LibreOffice.


, it seems to me that the strongest argument in favor of 
higher-frequency major version bumps is that it can increase 
media/Internet visibility for the new version somewhat, and thus likely 
to attract the attention of more potential new users, which is a good thing.


I find other arguments, though, to undermine this position more than 
buttress it.


Nigel Verity wrote:
> If I see that some software I use regularly has gone from 7.5 to 7.6, 
say, I wouldn't rush to upgrade


Great, what's the problem? Why should we be in a rush to get existing 
users to upgrade from 7.5 to 7.6? we're not failing to meet our 
quarterly sales targets in The Big Office Corporation (TM). It's 
actually better if we don't pretend it's important to upgrade to the 
next minor version if it isn't.


Italo Vignoli wrote:
> major releases of Microsoft Office are managed by marketing

Microsoft office is a commercial product, a commodity. And the company 
developing it is a vehicle for securing profits for its investors, not 
benefit to humanity (nor the users of office productivity suites). So, 
we should be at least skeptical about copying MS behavior regarding MSO 
in which their marketing wing is calling the shots.


Moreover - MSO versioning is kind of a mess; and even though I use MSO 
quite a bit (for reasons not relevant to this email) - for the life of 
me I can't tell what exactly changes between versions and whether I 
should bother to make sure and use a newer one.


> managed by marketing and not by developers

This is a false dichotomy. I'm not an LO developer; I didn't suggest the 
developers take over the version numbering; and I don't know that that 
would be a good thing. But decisions by marketers solely may also not be 
so great.


> marketing

about that...

LibreOffice is not a commodity. We don't exchange copies or licenses to 
use LibreOffice for money. And the set of people and organizations who 
use office suites, and the office suites they use, are not a market. 
_Some_  of that space is a market, but not our part (and there's also 
the ecosystem around LO, some of which is market-ish.) And while 
marketing experience is certainly useful in promoting the adoption and 
use of LO, there are still fundamental differences between doing that 
and "marketing" it. Some of them are practical (i.e. what "works" for 
commercial software isn't exactly what "works" for pitching LibreOffice 
use) but some of them are matters of principle and the kind of 
relationship and commitments between projects/producers/developers and 
users, or even non-users.


The major version number is not some sacred part of these commitments. 
But - like Jan Dittirch says - what would our users think of us if they 
had been aware that we bump version numbers as a "stimulus-evoking 
action" to rile up some of the "animals", and have the other "herd 
animals" follow? (And yes, I know those terms have not been repeated by 
other discussants.)


Paul Hofseth wrote:
> For Libre office number eight it might suffice to claim the usual 
"the changes will assure your improved experience and safety"


But it would be mostly a falsehood. I mean, any commit improves the 
experience of some people to some extent, but it's not true that the 
changes of 7.5 to 7.6 "assure your improved experience and safety". 
Moreover, people notice this kind of rhetoric - even non-tech-savvy 
newbies. And they realize that "Oh, so LibreOffice is another one of 
_those_ initiatives. The ones alienated and estranged from us, whose 
communiques must be carefully scrutinized for exaggerations and 
misrepresentations."


I would rather we not be that.

[Libreoffice-commits] core.git: helpcontent2

[Seth Chaiklin (via logerrit)]

 helpcontent2 |2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

New commits:
commit a82a294f4681647fa4e11d8b02147d5881d80b0a
Author: Seth Chaiklin 
AuthorDate: Thu Apr 6 22:08:16 2023 +0200
Commit: Gerrit Code Review 
CommitDate: Thu Apr 6 22:08:16 2023 +0200

Update git submodules

* Update helpcontent2 from branch 'master'
  to 18e7e5c3bf1a43e591d00ab01afa651cae12fa27
  - tdf#153242 update label changes: "Numbering separator" and "Separator"

   "Numbering separator" -> "After number"
   "Separator" -> "After caption"

Change-Id: Ib7110a73eaf9c7c48f2d47e92f8fc26b10f697d4
Reviewed-on: https://gerrit.libreoffice.org/c/help/+/150083
Tested-by: Jenkins
Reviewed-by: Seth Chaiklin 

diff --git a/helpcontent2 b/helpcontent2
index 5f36f1f9a460..18e7e5c3bf1a 16
--- a/helpcontent2
+++ b/helpcontent2
@@ -1 +1 @@
-Subproject commit 5f36f1f9a460f33cb48e50aac6f3c24b82a8ae66
+Subproject commit 18e7e5c3bf1a43e591d00ab01afa651cae12fa27

[Libreoffice-commits] help.git: source/text

[Seth Chaiklin (via logerrit)]

 source/text/shared/optionen/01041100.xhp |6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

New commits:
commit 18e7e5c3bf1a43e591d00ab01afa651cae12fa27
Author: Seth Chaiklin 
AuthorDate: Thu Apr 6 16:44:16 2023 +0200
Commit: Seth Chaiklin 
CommitDate: Thu Apr 6 22:08:16 2023 +0200

tdf#153242 update label changes: "Numbering separator" and "Separator"

   "Numbering separator" -> "After number"
   "Separator" -> "After caption"

Change-Id: Ib7110a73eaf9c7c48f2d47e92f8fc26b10f697d4
Reviewed-on: https://gerrit.libreoffice.org/c/help/+/150083
Tested-by: Jenkins
Reviewed-by: Seth Chaiklin 

diff --git a/source/text/shared/optionen/01041100.xhp 
b/source/text/shared/optionen/01041100.xhp
index 1dc0e628e9..d9f6614a34 100644
--- a/source/text/shared/optionen/01041100.xhp
+++ b/source/text/shared/optionen/01041100.xhp
@@ -59,12 +59,12 @@
   Numbering
   Specifies the type of 
numbering required.
 
-  
-  Numbering separator
+
+  After number
   Specify optional text 
characters to display between the caption number and caption category. This 
option is active only when Numbering first is selected for 
the Caption Order.
 
 
-  Separator
+  Before caption
   Define optional text 
character that appears after the caption category and caption 
number.
 
 

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

[Seth Chaiklin (via logerrit)]

 sw/uiconfig/swriter/ui/optcaptionpage.ui |5 +++--
 1 file changed, 3 insertions(+), 2 deletions(-)

New commits:
commit e131cd4cde28531e088a16a9eba1b8bc2ed067a1
Author: Seth Chaiklin 
AuthorDate: Thu Apr 6 15:30:33 2023 +0200
Commit: Seth Chaiklin 
CommitDate: Thu Apr 6 22:07:55 2023 +0200

tdf#153242 update labels for "Numbering separator" and "Separator"

   These two changes bring AutoCaption in line with the changes made
   to the Insert Caption dialog.

   "Numbering separator" -> "After number"
and tooltip added
   "Separator" -> "After caption"

Change-Id: I60bedf0e4139f9492672071cf9703cf94fcde684
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/150082
Tested-by: Seth Chaiklin 
Reviewed-by: Seth Chaiklin 

diff --git a/sw/uiconfig/swriter/ui/optcaptionpage.ui 
b/sw/uiconfig/swriter/ui/optcaptionpage.ui
index c6f4fdaf707d..1ab036da9aaf 100644
--- a/sw/uiconfig/swriter/ui/optcaptionpage.ui
+++ b/sw/uiconfig/swriter/ui/optcaptionpage.ui
@@ -85,7 +85,7 @@
   
 True
 False
-Numbering separator:
+After number:
 True
 numseparator
 0
@@ -99,7 +99,7 @@
   
 True
 False
-Separator:
+Before caption:
 True
 separator
 0
@@ -169,6 +169,7 @@
 True
 . 
 True
+For Numbering first option, 
define characters to display between caption number and caption 
category.
 
   
 For 
Numbering first option, defines the characters to be displayed between the 
caption number and the caption category.

[Libreoffice-bugs] [Bug 154678] Crash closing LibreOffice with caption frame on clipboard

[bugzilla-daemon]

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

--- Comment #5 from sdc.bla...@youmail.dk ---
(In reply to Telesto from comment #4)
> split... because unable to repro steps in bug 154551
Is the difference that you must first try to close the document before your
crash, while bug 154551 reports a crash (more or less immediately) after CTRL+X
(without having to close)?

Meanwhile -- please note bug 154551, comment 6, which gives another STR (using
CTRL+C, instead of CTRL+X) that is consistent with the bug summary for this
ticket.

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

[Libreoffice-bugs] [Bug 106040] [META] Help bugs and enhancements

[bugzilla-daemon]

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

sdc.bla...@youmail.dk changed:

   What|Removed |Added

 Depends on||154184


Referenced Bugs:

https://bugs.documentfoundation.org/show_bug.cgi?id=154184
[Bug 154184] Clarify help for "Apply to all occurrences" when changes are made
to Entry selection
-- 
You are receiving this mail because:
You are the assignee for the bug.

[Libreoffice-bugs] [Bug 106040] [META] Help bugs and enhancements

[bugzilla-daemon]

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

Bug 154184 Summary: Clarify help for "Apply to all occurrences" when changes 
are made to Entry selection
https://bugs.documentfoundation.org/show_bug.cgi?id=154184

   What|Removed |Added

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

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

[Libreoffice-bugs] [Bug 89606] [META] Table of Contents and Indexes bugs and enhancements

[bugzilla-daemon]

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

Bug 154184 Summary: Clarify help for "Apply to all occurrences" when changes 
are made to Entry selection
https://bugs.documentfoundation.org/show_bug.cgi?id=154184

   What|Removed |Added

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

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

Re: Print Dialog: Add support for the Common Print Dialog Backends (CPDB)

[Caolán McNamara]

On the technical side the things to look at might be:
a) The existing PrinterCapType::ExternalDialog "capability" which might
mesh with the concept here, which is used (in some circumstance 
apparently) on macOS; git grep ExternalDialog vcl
b) The now removed (since migration from gtk2 to gtk3) experimental
integration to use the gtk print dialog. This was removed in commit
1ae450504cf57457f9702684b1517fda1dd3c481 but might be worth a look as
something similar.

FWIW back in that experimental gtk2 print dialog, one of the nuisances
(and whose equivalent problem can be seen in a current version
gnumeric) is that for spreadsheet printing the selection of sheets to
print and/or cells couldn't be placed in proximity with the built in
page ranges. In gnumeric, using the standard gtk dialog, they are
placed a little awkwardly in a third tab, while in the LibreOffice non-
standard dialog they are grouped into the "range and copies" category.

[Libreoffice-commits] core.git: helpcontent2

[Seth Chaiklin (via logerrit)]

 helpcontent2 |2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

New commits:
commit 037177d047bfc38b7555b8ec45ceb98f35e3551c
Author: Seth Chaiklin 
AuthorDate: Thu Apr 6 21:39:31 2023 +0200
Commit: Gerrit Code Review 
CommitDate: Thu Apr 6 21:39:31 2023 +0200

Update git submodules

* Update helpcontent2 from branch 'master'
  to 5f36f1f9a460f33cb48e50aac6f3c24b82a8ae66
  - tdf#154184  clarify how "Apply to all occurrences" option works

Change-Id: Ieed042b8b6d78257b77ef61e5ab56fbbcdba27cc
Reviewed-on: https://gerrit.libreoffice.org/c/help/+/149984
Tested-by: Jenkins
Reviewed-by: Stéphane Guillou 
Reviewed-by: Seth Chaiklin 

diff --git a/helpcontent2 b/helpcontent2
index 0380b0919552..5f36f1f9a460 16
--- a/helpcontent2
+++ b/helpcontent2
@@ -1 +1 @@
-Subproject commit 0380b0919552e5409ec508aac3910a7422038311
+Subproject commit 5f36f1f9a460f33cb48e50aac6f3c24b82a8ae66

[Libreoffice-commits] help.git: source/text

[Seth Chaiklin (via logerrit)]

 source/text/swriter/01/04120100.xhp |   11 +--
 1 file changed, 5 insertions(+), 6 deletions(-)

New commits:
commit 5f36f1f9a460f33cb48e50aac6f3c24b82a8ae66
Author: Seth Chaiklin 
AuthorDate: Wed Apr 5 02:23:50 2023 +0200
Commit: Seth Chaiklin 
CommitDate: Thu Apr 6 21:39:31 2023 +0200

tdf#154184  clarify how "Apply to all occurrences" option works

Change-Id: Ieed042b8b6d78257b77ef61e5ab56fbbcdba27cc
Reviewed-on: https://gerrit.libreoffice.org/c/help/+/149984
Tested-by: Jenkins
Reviewed-by: Stéphane Guillou 
Reviewed-by: Seth Chaiklin 

diff --git a/source/text/swriter/01/04120100.xhp 
b/source/text/swriter/01/04120100.xhp
index cac1e9ab25..21a01c3db5 100644
--- a/source/text/swriter/01/04120100.xhp
+++ b/source/text/swriter/01/04120100.xhp
@@ -112,15 +112,14 @@
 The following three 
options are available when a text selection is loaded in Entry, 
either by selecting the text in the document and then opening the dialog, or by 
using Update entry from selection in the dialog.
 
 Apply to all other occurrences
-Automatically marks all other 
occurrences of the selected text in the document. Text in headers, footers, 
frames, and captions is not included.
-You cannot use the function for 
an Entry that you entered manually in this dialog.
-To include all occurrences of a text passage in an 
index, select the text, choose Edit - Find  Replace, and 
click Find All. Then choose Insert - Table of Contents and 
Index - Index Entry and click Insert.
+Automatically marks all other 
occurrences of the selected text in the document. For a modified entry, the 
match is conducted on the original selection, but the modified entry is 
inserted as the index entry. Text in headers, footers, and frames is not 
included.
 
-Whole words only
+Whole words only
 
 
-Match case
+Match case
 
+To include all occurrences of a text passage in an 
index, select the text, choose Edit - Find  Replace, and 
click Find All. Then choose Insert - Table of Contents and 
Index - Index Entry and click Insert.
 
 Insert
 Marks an index entry in your 
text.
@@ -185,7 +184,7 @@
 
   
 
-   Next Entry 
Icon
+   Next Entry Icon
 
 
   Next entry

[Libreoffice-bugs] [Bug 154690] Make Change-Case commands more accessible in Calc menus

[bugzilla-daemon]

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

--- Comment #1 from ady  ---
Menu Format > Text >

* UPPERCASE
* lowercase
* Cycle Case
* Sentence case
* Capitalize Every Word
* tOGGLE cASE

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

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

[Seth Chaiklin (via logerrit)]

 sw/uiconfig/swriter/ui/indexentry.ui |7 ++-
 1 file changed, 6 insertions(+), 1 deletion(-)

New commits:
commit 3b5bc5b4018ba94375ff66c381746e413af5b836
Author: Seth Chaiklin 
AuthorDate: Wed Apr 5 17:08:32 2023 +0200
Commit: Seth Chaiklin 
CommitDate: Thu Apr 6 21:38:35 2023 +0200

tdf#154184  modify/add tool/extended tip: "Apply to all other occurrences"

It is possible to modify a text selection, but the "Apply to..." option
will search only on the original selection, even while adding the
modified entry as the index entry. The tooltip is adjusted to reflect
that behavior, and an extended tip is added to explain more explicitly.

Change-Id: Ic3a9279beb696948a3b30a05a76753905b58641a
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/149988
Tested-by: Jenkins
Reviewed-by: Seth Chaiklin 

diff --git a/sw/uiconfig/swriter/ui/indexentry.ui 
b/sw/uiconfig/swriter/ui/indexentry.ui
index 0b1eca11061c..ca3f1f5da8fc 100644
--- a/sw/uiconfig/swriter/ui/indexentry.ui
+++ b/sw/uiconfig/swriter/ui/indexentry.ui
@@ -529,10 +529,15 @@
 True
 False
 True
-Add an index entry to any other 
occurrences of the selected text specified in “Entry”.
+Add an index entry to any other 
occurrences of the text selected into “Entry”.
 start
 True
 True
+
+  
+Add an index 
entry to any other occurrences of the text selected into “Entry”. For a 
modified entry, the match is conducted on the original selection, but the 
modified entry is inserted, and will appear in the index.
+  
+
   
   
 0

[Libreoffice-bugs] [Bug 154678] Crash closing LibreOffice with caption frame on clipboard

[bugzilla-daemon]

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

--- Comment #4 from Telesto  ---
(In reply to sdc.blanco from comment #3)
> Repro (with simpler STR)
> 
> 1. Insert Frame.
> 2. Right-click on selected frame, choose "Insert Caption"
> 3. Type some caption. Say AAA & press OK
> 4. CTRL+X (on frame) (or select the caption within the frame and Ctrl+X)
> (sometimes need to wait a little).
> Crash

I split it to a different bug, because I'm unable to repro the steps in bug
154551
And is it possible to use WinDbg for some backtrace.. makes it easier to
compare + finding the cause.

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

[Libreoffice-bugs] [Bug 148903] Description for ”page text area” is wrong in Position and Size tab and Image - Type tab

[bugzilla-daemon]

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

--- Comment #20 from sdc.bla...@youmail.dk ---
(In reply to BogdanB from comment #18)
> I attached another example:
The attachment uses "Entire Paragraph Area" (that is bug 149252), but this
ticket is "Page Text Area".  (but I have converted the "to" option to "Page
text area", so no need to upload a new version of the test document).

Please do not use "From left" in your test document.  This is what is creating
the confusion. It is true that you can position an object beyond the boundaries
of the region. (just as a negative paragraph indent can place text beyond a
page margin), but this is not relevant for the help page.

The purpose of the help for "page text area" is to identify the region being
used for the positioning.  As suggested before, use only "Left" and "Right" in
your Horizontal option, and you will see the boundaries of the region.

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

[Libreoffice-commits] core.git: sc/README.md

[Eike Rathke (via logerrit)]

 sc/README.md |4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

New commits:
commit 471e177658761a0c492a56d17de5ea40cfa741f2
Author: Eike Rathke 
AuthorDate: Thu Apr 6 17:53:09 2023 +0200
Commit: Eike Rathke 
CommitDate: Thu Apr 6 21:30:39 2023 +0200

Update ODFF link

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

diff --git a/sc/README.md b/sc/README.md
index b28b1b769c71..826bb71a9e9b 100644
--- a/sc/README.md
+++ b/sc/README.md
@@ -51,8 +51,8 @@ extra list of the Help system, functions that support 
Wildcards or Regular
 Expressions *and* depend on the setting under
 Tools -> Options -> Calc -> Calculate are those that in ODF OpenFormula (ODFF)
 are defined to depend on the HOST-USE-REGULAR-EXPRESSIONS or HOST-USE-WILDCARDS
-properties, see
-https://docs.oasis-open.org/office/v1.2/os/OpenDocument-v1.2-os-part2.html
+properties, see ODF v1.3 part4 3.4 Host-Defined Behaviors
+https://docs.oasis-open.org/office/OpenDocument/v1.3/os/part4-formula/OpenDocument-v1.3-os-part4-formula.html#__RefHeading__1017868_715980110
 
 * Database Functions
   * DAVERAGE

[Libreoffice-bugs] [Bug 89263] Fit object to paper format does not work when changing orientation to landscape

[bugzilla-daemon]

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

Buovjaga  changed:

   What|Removed |Added

   Severity|normal  |minor

--- Comment #8 from Buovjaga  ---
No problem(In reply to Buovjaga from comment #1)
> Reproduced.
> 
> English steps:
> 1. Draw a shape.
> 2. Right-click - Page - Page setup
> 3. Format - A0
> 4. Orientation - Landscape
> 5. Observe horrific stretching of shape

Still repro. I had forgotten to add before step 5, activate the option "Fit
object to paper format" (even though it's in the summary

Arch Linux 64-bit, X11
Version: 7.6.0.0.alpha0+ (X86_64) / LibreOffice Community
Build ID: 74f398bb58510087cc4a11bb2253715771a2c6b2
CPU threads: 8; OS: Linux 6.2; UI render: default; VCL: kf5 (cairo+xcb)
Locale: fi-FI (fi_FI.UTF-8); UI: en-US
Calc: threaded
Built on 22 March 2023

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

[Libreoffice-commits] core.git: Branch 'distro/cib/libreoffice-6-4' - cui/source cui/uiconfig officecfg/registry sw/source

[Michael Stahl (via logerrit)]

 cui/source/options/optsave.cxx |   12 ++
 cui/source/options/optsave.hxx |1 
 cui/uiconfig/ui/optsavepage.ui |   15 +
 officecfg/registry/schema/org/openoffice/Office/Common.xcs |8 ++
 sw/source/uibase/uiview/view.cxx   |4 +++
 5 files changed, 40 insertions(+)

New commits:
commit 45e66d20380e9facff62e8a504c8b54f49ebbefe
Author: Michael Stahl 
AuthorDate: Thu Apr 6 20:56:00 2023 +0200
Commit: Michael Stahl 
CommitDate: Thu Apr 6 21:27:30 2023 +0200

officecfg,cui,sw: add Common::Load::ViewPositionForAnyUser

Add setting Office::Common::Load::ViewPositionForAnyUser which if
enabled skips the user name matching against meta.xml that sw does
before restoring a view position stored as ViewTop/ViewLeft/etc. in
settings.xml in an ODF file.

This is particularly useful if the user disables the "ApplyUserData"
in Document->Properties->General, which made restoring view position
impossible.

Change-Id: Ie3ced3c4ad20a35eb8453ad1521c787b0b0c8458

diff --git a/cui/source/options/optsave.cxx b/cui/source/options/optsave.cxx
index 72f736ce406b..2ce16aa16de8 100644
--- a/cui/source/options/optsave.cxx
+++ b/cui/source/options/optsave.cxx
@@ -29,6 +29,7 @@
 #include 
 #include 
 #include 
+#include 
 #include 
 #include 
 #include 
@@ -69,6 +70,7 @@ SvxSaveTabPage_Impl::SvxSaveTabPage_Impl() : bInitialized( 
false )
 SvxSaveTabPage::SvxSaveTabPage(weld::Container* pPage, weld::DialogController* 
pController, const SfxItemSet& rCoreSet)
 : SfxTabPage( pPage, pController, "cui/ui/optsavepage.ui", "OptSavePage", 
 )
 , pImpl(new SvxSaveTabPage_Impl)
+, m_xLoadViewPosAnyUserCB(m_xBuilder->weld_check_button("load_anyuser"))
 , m_xLoadUserSettingsCB(m_xBuilder->weld_check_button("load_settings"))
 , m_xLoadDocPrinterCB(m_xBuilder->weld_check_button("load_docprinter"))
 , m_xDocInfoCB(m_xBuilder->weld_check_button("docinfo"))
@@ -215,6 +217,13 @@ bool SvxSaveTabPage::FillItemSet( SfxItemSet* rSet )
 {
 bool bModified = false;
 SvtSaveOptions aSaveOpt;
+if (m_xLoadViewPosAnyUserCB->get_state_changed_from_saved())
+{
+std::shared_ptr pBatch(
+comphelper::ConfigurationChanges::create());
+
officecfg::Office::Common::Load::ViewPositionForAnyUser::set(m_xLoadViewPosAnyUserCB->get_active(),
 pBatch);
+pBatch->commit();
+}
 if(m_xLoadUserSettingsCB->get_state_changed_from_saved())
 {
 aSaveOpt.SetLoadUserSettings(m_xLoadUserSettingsCB->get_active());
@@ -353,6 +362,9 @@ static bool isODFFormat( const OUString& sFilter )
 void SvxSaveTabPage::Reset( const SfxItemSet* )
 {
 SvtSaveOptions aSaveOpt;
+
m_xLoadViewPosAnyUserCB->set_active(officecfg::Office::Common::Load::ViewPositionForAnyUser::get());
+m_xLoadViewPosAnyUserCB->save_state();
+
m_xLoadViewPosAnyUserCB->set_sensitive(!officecfg::Office::Common::Load::ViewPositionForAnyUser::isReadOnly());
 m_xLoadUserSettingsCB->set_active(aSaveOpt.IsLoadUserSettings());
 m_xLoadUserSettingsCB->save_state();
 
m_xLoadUserSettingsCB->set_sensitive(!aSaveOpt.IsReadOnly(SvtSaveOptions::EOption::UseUserData));
diff --git a/cui/source/options/optsave.hxx b/cui/source/options/optsave.hxx
index 4314bdda1ddf..f412054ae600 100644
--- a/cui/source/options/optsave.hxx
+++ b/cui/source/options/optsave.hxx
@@ -45,6 +45,7 @@ class SvxSaveTabPage : public SfxTabPage
 private:
 std::unique_ptrpImpl;
 
+std::unique_ptr m_xLoadViewPosAnyUserCB;
 std::unique_ptr m_xLoadUserSettingsCB;
 std::unique_ptr m_xLoadDocPrinterCB;
 std::unique_ptr m_xDocInfoCB;
diff --git a/cui/uiconfig/ui/optsavepage.ui b/cui/uiconfig/ui/optsavepage.ui
index e9a090d45091..c95efcfc68cc 100644
--- a/cui/uiconfig/ui/optsavepage.ui
+++ b/cui/uiconfig/ui/optsavepage.ui
@@ -61,6 +61,21 @@
 0
   
 
+
+  
+Load view position with the document even if 
it was saved by a different user
+True
+True
+False
+True
+0
+True
+  
+  
+0
+2
+  
+
   
 
   
diff --git a/officecfg/registry/schema/org/openoffice/Office/Common.xcs 
b/officecfg/registry/schema/org/openoffice/Office/Common.xcs
index f04172b3ef6d..3fdf08d9e19a 100644
--- a/officecfg/registry/schema/org/openoffice/Office/Common.xcs
+++ b/officecfg/registry/schema/org/openoffice/Office/Common.xcs
@@ -2503,6 +2503,14 @@
 
 true
   
+  
+
+  Determines if the view position of the document is loaded with
+  a document even if it was saved by a different 

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

[Bogdan B (via logerrit)]

 sw/uiconfig/swriter/ui/mmresultemaildialog.ui |2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

New commits:
commit 3a8f1069a9041c2a999d5287f474ac2dd703ecde
Author: Bogdan B 
AuthorDate: Thu Apr 6 19:27:34 2023 +0200
Commit: Adolfo Jayme Barrientos 
CommitDate: Thu Apr 6 21:23:15 2023 +0200

tdf#154164 Remove "Adobe" referring to PDF document

Change-Id: Ib9676b01c288518f74c01b41300ebc427f5c3109
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/150086
Reviewed-by: Vernon, Stuart Foote 
Tested-by: Jenkins
Reviewed-by: Adolfo Jayme Barrientos 

diff --git a/sw/uiconfig/swriter/ui/mmresultemaildialog.ui 
b/sw/uiconfig/swriter/ui/mmresultemaildialog.ui
index dcf78573eecf..07727249b5b9 100644
--- a/sw/uiconfig/swriter/ui/mmresultemaildialog.ui
+++ b/sw/uiconfig/swriter/ui/mmresultemaildialog.ui
@@ -213,7 +213,7 @@
 True
 
   OpenDocument Text
-  Adobe PDF-Document
+  PDF Document
   Microsoft Word Document
   HTML Message
   Plain Text

[Libreoffice-bugs] [Bug 154691] New: Cycle Case command doens't work during cell edit

[bugzilla-daemon]

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

Bug ID: 154691
   Summary: Cycle Case command doens't work during cell edit
   Product: LibreOffice
   Version: 7.5.1.2 release
  Hardware: All
OS: All
Status: UNCONFIRMED
  Severity: normal
  Priority: medium
 Component: Calc
  Assignee: libreoffice-bugs@lists.freedesktop.org
  Reporter: eyalr...@gmx.com

Suppose I've added the "Cycle Case" command to the Cell Edit context menu in
Calc. Now, in a new document, I enter some text into a cell, and in edit mode,
select one of the characters, right click, and select Cycle Case repeatedly.

I see different behaviors, most of them wrong:

* Case cycled for entire cell contents, edit mode exited
* Nothing happens on repeated Cycle-Case commands
* The selected character is deleted

I think the cycling of the whole cell contents is characteristic of selecting
the last character.

Anyway, it doesn't consistently behave like I expected too.

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

[Libreoffice-bugs] [Bug 154690] New: Make Change-Case commands more accessible in Calc menus

[bugzilla-daemon]

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

Bug ID: 154690
   Summary: Make Change-Case commands more accessible in Calc
menus
   Product: LibreOffice
   Version: 7.5.1.2 release
  Hardware: All
OS: All
Status: UNCONFIRMED
  Severity: enhancement
  Priority: medium
 Component: Calc
  Assignee: libreoffice-bugs@lists.freedesktop.org
  Reporter: eyalr...@gmx.com

Sometimes, you want to change the case of one or multiple characters of text
you're editing in a Calc Cell. However - that command appears nowhere (?) on
the menus, nor on the right-click context menu. I think the command(s) for
changing case should be more accessible by default.

Note: I realize one can customize and add them; this is a suggestion to improve
default accessibility.

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

[Libreoffice-bugs] [Bug 148903] Description for ”page text area” is wrong in Position and Size tab and Image - Type tab

[bugzilla-daemon]

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

--- Comment #19 from BogdanB  ---
Created attachment 186524
  --> https://bugs.documentfoundation.org/attachment.cgi?id=186524=edit
demo document

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

[Libreoffice-bugs] [Bug 148903] Description for ”page text area” is wrong in Position and Size tab and Image - Type tab

[bugzilla-daemon]

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

--- Comment #18 from BogdanB  ---
(In reply to sdc.blanco from comment #17)
> @Bogdan -- your hard work has helped me to understand that for "Horizontal"
> page text area could be described as follows:
> 
> page text area: the object is positioned between the inner edge of the left
> page padding and the inner edge of the right page padding.
> 
> 
> Maybe you would like to submit that change?

But it is NOT correct.
I tried what you have said earlier, and I minimized the image, and IF the image
is starting with positive numbers (from zero above) it's correct to be "inner
edge of the left page padding", but otherwise, IF I set minus 2 cm to a small
image I can move the image to the left margin of the page.

When talking about the right limit, I don't agree with "inner edge of the right
page padding". The image is moving more beyond that.

I attached another example:
there are 4 images:
- minus 5 cm from left
- zero cm
- plus 5 cm
- 25 cm

They can be from the left page margin to the right page margin IF we take
positive or negative value.

They can be from the inner edge of the left page padding to the right page
margin if just positive value.

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

[Libreoffice-bugs] [Bug 106040] [META] Help bugs and enhancements

[bugzilla-daemon]

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

sdc.bla...@youmail.dk changed:

   What|Removed |Added

 Depends on||154689


Referenced Bugs:

https://bugs.documentfoundation.org/show_bug.cgi?id=154689
[Bug 154689] The "to" option for Horizontal position should refer to "region or
reference line" not "point"
-- 
You are receiving this mail because:
You are the assignee for the bug.

[Libreoffice-bugs] [Bug 154689] The "to" option for Horizontal position should refer to "region or reference line" not "point"

[bugzilla-daemon]

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

sdc.bla...@youmail.dk changed:

   What|Removed |Added

 Blocks||106040
Summary|The "to" option for |The "to" option for
   |Horizontal position should  |Horizontal position should
   |refer to "region or line"   |refer to "region or
   |not "point" |reference line" not "point"


Referenced Bugs:

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

[Libreoffice-bugs] [Bug 154689] New: The "to" option for Horizontal position should refer to "region or line" not "point"

[bugzilla-daemon]

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

Bug ID: 154689
   Summary: The "to" option for Horizontal position should refer
to "region or line" not "point"
   Product: LibreOffice
   Version: 7.2.7.2 release
  Hardware: All
OS: All
Status: UNCONFIRMED
  Severity: normal
  Priority: medium
 Component: Documentation
  Assignee: libreoffice-bugs@lists.freedesktop.org
  Reporter: sdc.bla...@youmail.dk
CC: olivier.hal...@libreoffice.org

1. The "to" option (in the Position section with "Horizontal") in [1] reads:

"Select the reference point for the selected horizontal alignment option. The
following options are available:"

"reference point" should be "region or reference line"


2.  The relation between the "Horizontal" option and the "to" option could be
explained better by adding the following sentence (after the first sentence)
for "Horizontal":

The selection specifies the position of the object relative to the region or
reference line selected in the to dropdown list. 


[1] https://help.libreoffice.org/7.6/en-US/text/swriter/01/05060100.html

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

Re: Print Dialog: Add support for the Common Print Dialog Backends (CPDB)

[Till Kamppeter]

On 06/04/2023 20:36, Till Kamppeter wrote:
To step up, please tell me your full name and e-mail address, so that I 
can invite you and you can register in Google's web app. Only condition 
is that you do not participate as a contributor/student in this year's 
GSoC.




Please contact me by e-mail (and not by IRC, my client connection is 
flaky) if you want to help mentoring.


   Till

[Libreoffice-bugs] [Bug 148903] Description for ”page text area” is wrong in Position and Size tab and Image - Type tab

[bugzilla-daemon]

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

--- Comment #17 from sdc.bla...@youmail.dk ---
@Bogdan -- your hard work has helped me to understand that for "Horizontal"
page text area could be described as follows:

page text area: the object is positioned between the inner edge of the left
page padding and the inner edge of the right page padding.


Maybe you would like to submit that change?

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

Re: Print Dialog: Add support for the Common Print Dialog Backends (CPDB)

[Till Kamppeter]

Ilmari, thank you very much for taking this into the Engineering 
Steering Committee (ESC) meeeting today! And buovjaga to suggest this on 
IRC.


Thorsten, thank you very much for your detailed meeting minutes and the 
quick posting of them.


Heiko, there will be no UI change at all. The changes are only how the 
dialog gets


- The list of available printers
- For a printer selected by the user
   o The list of user-settable options with the available choices for
 each option (like Media Source: Tray 1, Tray 2, Bypass Tray, ...)
   o The list of all page sizes with unprintable margins, for correct
 previews
   o A job sent to the printer

This will not done any more by the dialog directly talking to CUPS. but 
to the CPDB libraries. What the user sees and how they operate it will 
not change.


This should not really be "massive" changes. As an example, here is the 
Merge Request for the CPDB support om the GTK dialog:


https://gitlab.gnome.org/GNOME/gtk/-/merge_requests/4930

And the commit on LibreOffice back in 2017, with the very first version 
of CPDB:


https://gerrit.libreoffice.org/#/c/40565

Heiko, and thanks for stepping up to help mentoring on the UI/UX side, 
so if there is a change on the UI needed (low probablility) or the 
switch to CPDB would help for a better UI, your insight would help us a lot!


Heiko, could you provide me your full name and e-mail address, so that I 
can invite you?


Generally, we can invite and line up mentors at any time until the end 
of the coding, but I would appreciate a lot for anyone to step up before 
the ranking deadline, as the higher our number of mentors lined up, the 
higher the chances that we get our requested slot count, and so assure 
that very project we want to run will actually take place.


Also the sooner we get someone stepping up, the sooner Kushagra can 
start working and has someone to talk to on the LibreOffice side.


To step up, please tell me your full name and e-mail address, so that I 
can invite you and you can register in Google's web app. Only condition 
is that you do not participate as a contributor/student in this year's GSoC.


I hope we will have a great collaboration here.

   Till


On 06/04/2023 18:16, Thorsten Behrens wrote:

[...]

> * GSoC (Ilmari)
>+ Who wants to join OpenPrinting as a mentor: 
https://lists.freedesktop.org/archives/libreoffice/2023-April/090210.html
>  + Till Kamppeter's proposal for collaboration on adding support 
for the Common Print Dialog Backends (CPDB)

>
>+ mostly co-mentoring & backup, navigating LibO code
>
>+ will check (Hossein)
>
>+ slighty concerned with UI changing via openprinting (Heiko)
>
>+ careful to change things massively... (Heiko)
>
>+ willing to co-mentor for UI/UX too (Heiko)
>
>+ AI interested mentors, please poke Till!
>
>   + timeline: 27th of April ranking needs to be done
>   + mentors being invited, joining the org

[...]


On 04/04/2023 19:33, Till Kamppeter wrote:
LibreOffice is one of the few applications which have their own print 
dialog, and do not use one of the desktop environment toolkit's (GTK/Qt) 
ones primarily (AFAIR one can use the GTK one optionally, selecting in 
the settings).


[...]

As this is most probably not the last major change needed and also for 
print dialogs to support other print technologies than CUPS, for example 
cloud printing services, I have created already 5 years ago, the concept 
of the Common Print Dialog Backends (CPDB):


https://openprinting.github.io/achievements/#common-print-dialog-backends



[...]

[Libreoffice-bugs] [Bug 89263] Fit object to paper format does not work when changing orientation to landscape

[bugzilla-daemon]

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

BogdanB  changed:

   What|Removed |Added

 CC||buzea.bog...@libreoffice.or
   ||g

--- Comment #7 from BogdanB  ---
Buovjaga, please retest.

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

[Libreoffice-bugs] [Bug 154678] Crash closing LibreOffice with caption frame on clipboard

[bugzilla-daemon]

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

sdc.bla...@youmail.dk changed:

   What|Removed |Added

 CC||sdc.bla...@youmail.dk

--- Comment #3 from sdc.bla...@youmail.dk ---
Repro (with simpler STR)

1. Insert Frame.
2. Right-click on selected frame, choose "Insert Caption"
3. Type some caption. Say AAA & press OK
4. CTRL+X (on frame) (or select the caption within the frame and Ctrl+X)
(sometimes need to wait a little).
Crash

Version: 7.6.0.0.alpha0+ (X86_64) / LibreOffice Community
Build ID: 1e9f4de320f67d1218c710bcee1969a2324c6888
CPU threads: 8; OS: Windows 10.0 Build 19044; UI render: Skia/Vulkan; VCL: win
Locale: da-DK (da_DK); UI: en-US
Calc: CL threaded

But this ticket seems a duplicate of bug 154551

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

[Libreoffice-bugs] [Bug 103494] [META] Textbox bugs and enhancements

[bugzilla-daemon]

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

BogdanB  changed:

   What|Removed |Added

 Depends on||102354


Referenced Bugs:

https://bugs.documentfoundation.org/show_bug.cgi?id=102354
[Bug 102354] Text auto-fit / de-composition - hyper expensive ...
-- 
You are receiving this mail because:
You are the assignee for the bug.

[Libreoffice-bugs] [Bug 137892] Automatic color text have different color when Autofit enabled

[bugzilla-daemon]

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

BogdanB  changed:

   What|Removed |Added

 CC||buzea.bog...@libreoffice.or
   ||g
 Blocks||103494


Referenced Bugs:

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

[Libreoffice-bugs] [Bug 103494] [META] Textbox bugs and enhancements

[bugzilla-daemon]

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

BogdanB  changed:

   What|Removed |Added

 Depends on||137892


Referenced Bugs:

https://bugs.documentfoundation.org/show_bug.cgi?id=137892
[Bug 137892] Automatic color text have different color when Autofit enabled
-- 
You are receiving this mail because:
You are the assignee for the bug.

[Libreoffice-bugs] [Bug 103494] [META] Textbox bugs and enhancements

[bugzilla-daemon]

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

BogdanB  changed:

   What|Removed |Added

 Depends on||148816


Referenced Bugs:

https://bugs.documentfoundation.org/show_bug.cgi?id=148816
[Bug 148816] Fit height to text is turned ON for AutoLayout object area in
Normal mode, however not working. also turned off in Master slide mode
-- 
You are receiving this mail because:
You are the assignee for the bug.

[Libreoffice-bugs] [Bug 148816] Fit height to text is turned ON for AutoLayout object area in Normal mode, however not working. also turned off in Master slide mode

[bugzilla-daemon]

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

BogdanB  changed:

   What|Removed |Added

 CC||buzea.bog...@libreoffice.or
   ||g
 Blocks||103494


Referenced Bugs:

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

[Libreoffice-ux-advise] [Bug 154682] AutoCaption does not apply to an Image cut and pasted within a document or pasted to another document

[bugzilla-daemon]

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

--- Comment #2 from sdc.bla...@youmail.dk ---
(In reply to m.a.riosv from comment #1)
> Because you are copying the image not the Frame with the image
The question though is whether AutoCaption should be applied to a copied image.

> b) Also, Menu/Insert/Image adds the frame with their caption.
Correct. Also my experience and consistent with current help page.

> If you copy the frame, the caption is applied, 
Do not repro.  
1. Turn off AutoCaption for Frames.
2. Insert a frame.
3. Turn on AutoCaption for Frames.
4. Copy and paste frame.

Actual:  No caption applied to pasted frame.

> if you copy only the image, not, 
Which is the claim in the OP.

> Pasting from spreadsheets doesn't the caption.
Bug 61222

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

[Libreoffice-bugs] [Bug 154682] AutoCaption does not apply to an Image cut and pasted within a document or pasted to another document

[bugzilla-daemon]

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

--- Comment #2 from sdc.bla...@youmail.dk ---
(In reply to m.a.riosv from comment #1)
> Because you are copying the image not the Frame with the image
The question though is whether AutoCaption should be applied to a copied image.

> b) Also, Menu/Insert/Image adds the frame with their caption.
Correct. Also my experience and consistent with current help page.

> If you copy the frame, the caption is applied, 
Do not repro.  
1. Turn off AutoCaption for Frames.
2. Insert a frame.
3. Turn on AutoCaption for Frames.
4. Copy and paste frame.

Actual:  No caption applied to pasted frame.

> if you copy only the image, not, 
Which is the claim in the OP.

> Pasting from spreadsheets doesn't the caption.
Bug 61222

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

[Libreoffice-bugs] [Bug 136372] [META] PPTX shape related issues

[bugzilla-daemon]

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

BogdanB  changed:

   What|Removed |Added

 Depends on||127392


Referenced Bugs:

https://bugs.documentfoundation.org/show_bug.cgi?id=127392
[Bug 127392] "Autofit text" reacts wrongly for custom shapes
-- 
You are receiving this mail because:
You are the assignee for the bug.

[Libreoffice-bugs] [Bug 127392] "Autofit text" reacts wrongly for custom shapes

[bugzilla-daemon]

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

BogdanB  changed:

   What|Removed |Added

 CC||buzea.bog...@libreoffice.or
   ||g
 Blocks||136372


Referenced Bugs:

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

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

[Jim Raykowski (via logerrit)]

 sw/qa/uitest/data/tdf154212.odt |binary
 sw/qa/uitest/navigator/tdf154212.py |   86 +++
 sw/source/uibase/utlui/content.cxx  |  277 +---
 3 files changed, 156 insertions(+), 207 deletions(-)

New commits:
commit e27b936fe864cdd2753470e0fef1e3cb1f891555
Author: Jim Raykowski 
AuthorDate: Sat Apr 1 19:16:47 2023 -0800
Commit: Jim Raykowski 
CommitDate: Thu Apr 6 20:02:05 2023 +0200

tdf#154212 SwNavigator: Fix outline up/down handling

Fixes incorrect move outline up results and crashes related to
headings in frames being placed in order of document appearance in
the Navigator content tree, commit
c81f4a4ecbfa7dc97d8c28b5ec5f00d1d561b6bb.

It appears a significant amount of the existing code for handling
outline up/down movement isn't needed.

Change-Id: I9701b6d74dfa06f526f206fc2d250c4183ce4b2d
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/149944
Tested-by: Jenkins
Reviewed-by: Jim Raykowski 

diff --git a/sw/qa/uitest/data/tdf154212.odt b/sw/qa/uitest/data/tdf154212.odt
new file mode 100644
index ..1d07cd4aa08a
Binary files /dev/null and b/sw/qa/uitest/data/tdf154212.odt differ
diff --git a/sw/qa/uitest/navigator/tdf154212.py 
b/sw/qa/uitest/navigator/tdf154212.py
new file mode 100644
index ..e7222b3d9097
--- /dev/null
+++ b/sw/qa/uitest/navigator/tdf154212.py
@@ -0,0 +1,86 @@
+# -*- tab-width: 4; indent-tabs-mode: nil; py-indent-offset: 4 -*-
+#
+# This file is part of the LibreOffice project.
+#
+# This Source Code Form is subject to the terms of the Mozilla Public
+# License, v. 2.0. If a copy of the MPL was not distributed with this
+# file, You can obtain one at http://mozilla.org/MPL/2.0/.
+#
+
+from uitest.framework import UITestCase
+from libreoffice.uno.propertyvalue import mkPropertyValues
+from uitest.uihelper.common import get_state_as_dict, get_url_for_data_file
+import time
+
+class tdf154212(UITestCase):
+
+def test_tdf154212(self):
+
+with self.ui_test.load_file(get_url_for_data_file('tdf154212.odt')):
+xWriterDoc = self.xUITest.getTopFocusWindow()
+xWriterEdit = xWriterDoc.getChild('writer_edit')
+
+self.xUITest.executeCommand('.uno:Sidebar')
+xWriterEdit.executeAction('SIDEBAR', mkPropertyValues({'PANEL': 
'SwNavigatorPanel'}))
+
+# wait until the navigator panel is available
+xNavigatorPanel = 
self.ui_test.wait_until_child_is_available('NavigatorPanel')
+
+# HACK, see the `m_aUpdTimer.SetTimeout(1000)` in the 
SwContentTree ctor in
+# sw/source/uibase/utlui/content.cxx, where that m_aUpdTimer is 
started by
+# SwContentTree::ShowTree triggered from the SIDEBAR action above, 
and which can
+# invalidate the TreeListEntryUIObjects used by the below code (see
+# 2798430c8a711861fdcdfbf9ac00a0527abd3bfc "Mark the uses of 
TreeListEntryUIObject as
+# dubious"); lets double that 1000 ms timeout value here to 
hopefully be on the safe
+# side:
+time.sleep(2)
+
+xNavigatorPanelContentTree = 
xNavigatorPanel.getChild("contenttree")
+
+xNavigatorPanelContentTreeHeadings = 
xNavigatorPanelContentTree.getChild('0')
+xNavigatorPanelContentTreeHeadings.executeAction("EXPAND", tuple())
+
+xHeadingsChild0 = xNavigatorPanelContentTreeHeadings.getChild('0')
+xHeadingsChild0.executeAction("EXPAND", tuple())
+
+xHeadingsChild0Child2 = xHeadingsChild0.getChild('2')
+self.assertEqual(get_state_as_dict(xHeadingsChild0Child2)["Text"], 
"MOVE THIS Heading level 2")
+
+# double click on the entry to select and set focus
+xHeadingsChild0Child2.executeAction("DOUBLECLICK", tuple())
+
+# click on the 'move chapter down' button in the Navigator tool box
+xNavigatorPanel = xWriterEdit.getChild("NavigatorPanel")
+xToolBarContent6 = xNavigatorPanel.getChild("content6")
+xToolBarContent6.executeAction("CLICK", mkPropertyValues({"POS": 
"5"}))
+
+
self.ui_test.wait_until_property_is_updated(xNavigatorPanelContentTree, 
"SelectEntryText", "MOVE THIS Heading level 2")
+
+xNavigatorPanelContentTreeHeadings = 
xNavigatorPanelContentTree.getChild('0')
+
+xHeadingsChild0 = xNavigatorPanelContentTreeHeadings.getChild('0')
+
+xHeadingsChild0Child4 = xHeadingsChild0.getChild('4')
+self.assertEqual(get_state_as_dict(xHeadingsChild0Child4)["Text"], 
"MOVE THIS Heading level 2")
+
+# click on the 'move chapter up' button in the Navigator tool box
+xNavigatorPanel = xWriterEdit.getChild("NavigatorPanel")
+xToolBarContent6 = xNavigatorPanel.getChild("content6")
+xToolBarContent6.executeAction("CLICK", mkPropertyValues({"POS": 
"4"}))
+
+

[Libreoffice-bugs] [Bug 154688] en_GB Dictionary maintainer bouncing

[bugzilla-daemon]

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

Buovjaga  changed:

   What|Removed |Added

 Status|UNCONFIRMED |RESOLVED
 CC||ilmari.lauhakangas@libreoff
   ||ice.org
 Resolution|--- |FIXED

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