[Libreoffice-bugs] [Bug 151040] Logo in Start Center initially shows correctly but then only shows some pixels after returning from a LibreOffice application.

[bugzilla-daemon]

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

--- Comment #16 from Hussam Al-Tayeb  ---
(In reply to Stéphane Guillou (stragu) from comment #15)
> Can't reproduce on Ubuntu 20.04 with GNOME 3.36.8, Adwaita, and lo 7.5.2.2.
> The steps are very similar to bug 143673, which was fixed in 7.5.0.

Thanks. I fixed the title so that it better represents the issue.

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

[Libreoffice-bugs] [Bug 151040] Logo in Start Center initially shows correctly but then only shows some pixels after returning from a LibreOffice application.

[bugzilla-daemon]

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

Hussam Al-Tayeb  changed:

   What|Removed |Added

Summary|Logo in Start Center only   |Logo in Start Center
   |shows some pixels   |initially shows correctly
   ||but then only shows some
   ||pixels after returning from
   ||a LibreOffice application.

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

[Libreoffice-bugs] [Bug 147953] Autosize text frame stops working

[bugzilla-daemon]

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

Panos Stokas  changed:

   What|Removed |Added

 Status|NEW |UNCONFIRMED
 Ever confirmed|1   |0

--- Comment #11 from Panos Stokas  ---
This is the same issue with bug 151728. I have posted some useful info on
recovering a document in that bug on a comment there.

Pasting text from such applications (including even LO's formula code editor!)
will switch LO to a broken compatibility mode.

I don't know TDF's policy on marking duplicates but it's pretty certain that
either bug must be marked as a duplicate.

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

[Libreoffice-bugs] [Bug 151728] Pasting text from various programs forces Writer in a broken mode without the possibility of undoing it

[bugzilla-daemon]

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

--- Comment #7 from Panos Stokas  ---
The issue in the description can be reproduced by replacing LO's formula editor
with:

Word
Character Map
an old 8085 emulator
Sticky Notes

The only way to fix the broken format is save the document as a flat XML file
and manually edit the settings specified in my previous post:
https://bugs.documentfoundation.org/show_bug.cgi?id=151728#c2

It's a pretty big issue I think.

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

[Libreoffice-bugs] [Bug 151728] Pasting text from various programs forces Writer in a broken mode without the possibility of undoing it

[bugzilla-daemon]

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

Panos Stokas  changed:

   What|Removed |Added

Summary|Pasting formula code under  |Pasting text from various
   |a heading is breaking all   |programs forces Writer in a
   |heading styles without  |broken mode without the
   |possibility of undoing it   |possibility of undoing it

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

[Libreoffice-bugs] [Bug 151728] Pasting formula code under a heading is breaking all heading styles without possibility of undoing it

[bugzilla-daemon]

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

--- Comment #6 from Panos Stokas  ---
(In reply to lomacar from comment #5)
> There are strange similarities to bug 147953 which I am waiting to get
> fixed. https://bugs.documentfoundation.org/show_bug.cgi?id=147953
> 
> This bug and 147953 can both be triggered by pasting in any text from MS
> Word or the Windows character map.

It's the same issue. I've just copied a character from charmap.exe and my
headings broke the same way.

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

[Libreoffice-bugs] [Bug 154487] Enhancement Request: Allow LibreOffice Mail Merge to use default e-mail client

[bugzilla-daemon]

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

--- Comment #10 from Michael Weghorn  ---
(In reply to Stuart Simon from comment #8)
> [...] To personalize
> the e-mail AND the attached certificate, both of which have their personal
> name, would be a great feature to have.

Feel free to open another enhancement request for this.

I haven't used that feature myself, but the WollMux extension (
https://github.com/LibreOffice/WollMux ) provides the feature to have both a
personalized document and a personalized email message for each recipient.
WollMux might also be a helpful example for an extension that that does LO mail
merge and provides additional features, e.g. when planning to create an
extension that provides the feature to support sending the emails via specific
email clients.

> I'm wondering if there can be an extension to support popular e-mail client
> integrations for mail merge (maybe separate ones for Outlook and
> Thunderbird). Outlook does not use the same format to store mail messages as
> most other e-mail clients (Outlook format is MSG, general format is EML).
> But we don't need hundreds of mail-client Compose windows either. The
> Word/Adobe integration does not actually open Outlook. It places messages in
> Outlook's primary Outbox. The messages are sent only when the user opens
> Outlook manually if it is not already open.

Thanks for the explanation, that makes it much clearer. So IIUC, the Word/Adobe
integrations do not really interact with Outlook via any API, but by placing
the relevant files into the Outlook app data directory that are processed by
Outlook the next time it is opened.

I agree that opening a lot of compose windows doesn't sound like a great idea.

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

[Libreoffice-ux-advise] [Bug 154487] Enhancement Request: Allow LibreOffice Mail Merge to use default e-mail client

[bugzilla-daemon]

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

--- Comment #10 from Michael Weghorn  ---
(In reply to Stuart Simon from comment #8)
> [...] To personalize
> the e-mail AND the attached certificate, both of which have their personal
> name, would be a great feature to have.

Feel free to open another enhancement request for this.

I haven't used that feature myself, but the WollMux extension (
https://github.com/LibreOffice/WollMux ) provides the feature to have both a
personalized document and a personalized email message for each recipient.
WollMux might also be a helpful example for an extension that that does LO mail
merge and provides additional features, e.g. when planning to create an
extension that provides the feature to support sending the emails via specific
email clients.

> I'm wondering if there can be an extension to support popular e-mail client
> integrations for mail merge (maybe separate ones for Outlook and
> Thunderbird). Outlook does not use the same format to store mail messages as
> most other e-mail clients (Outlook format is MSG, general format is EML).
> But we don't need hundreds of mail-client Compose windows either. The
> Word/Adobe integration does not actually open Outlook. It places messages in
> Outlook's primary Outbox. The messages are sent only when the user opens
> Outlook manually if it is not already open.

Thanks for the explanation, that makes it much clearer. So IIUC, the Word/Adobe
integrations do not really interact with Outlook via any API, but by placing
the relevant files into the Outlook app data directory that are processed by
Outlook the next time it is opened.

I agree that opening a lot of compose windows doesn't sound like a great idea.

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

[Libreoffice-commits] core.git: accessibility/inc accessibility/source

[Michael Weghorn (via logerrit)]

 accessibility/inc/standard/svtaccessiblenumericfield.hxx|4 
 accessibility/source/standard/svtaccessiblenumericfield.cxx |   12 
 2 files changed, 16 insertions(+)

New commits:
commit 07f4fa7119d28ce943405ee6e7cbdf260c730357
Author: Michael Weghorn 
AuthorDate: Fri Apr 14 18:25:34 2023 +0300
Commit: Michael Weghorn 
CommitDate: Sat Apr 15 05:39:03 2023 +0200

a11y: Send VALUE_CHANGED event for FormattedField

`VCLXAccessibleEdit::ProcessWindowEvent` takes care
of sending a `TEXT_CHANGED` event. In the case of
`SVTXAccessibleNumericField`, numeric values are
handled, so send a `VALUE_CHANGED` event in addition.

This makes Orca with the qt6 VCL plugin announce
the new value when e.g. changing the page width
using the arrow up key in the "Format" -> "Page Style"
dialog.

For Accerciser, an additional fix is needed so the
value gets updated there in the interface view when
the a11y object is selected. Pending MR: [1]

[1] https://gitlab.gnome.org/GNOME/accerciser/-/merge_requests/25

Change-Id: Id911f50664df7220bc58204bc3477c5306a1da33
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/150422
Tested-by: Jenkins
Reviewed-by: Michael Weghorn 

diff --git a/accessibility/inc/standard/svtaccessiblenumericfield.hxx 
b/accessibility/inc/standard/svtaccessiblenumericfield.hxx
index 3537b9d6ef1d..29225a5c6072 100644
--- a/accessibility/inc/standard/svtaccessiblenumericfield.hxx
+++ b/accessibility/inc/standard/svtaccessiblenumericfield.hxx
@@ -20,6 +20,8 @@
 #pragma once
 
 #include 
+#include 
+
 #include 
 
 #include 
@@ -30,6 +32,8 @@ class SVTXAccessibleNumericField final
 public:
 SVTXAccessibleNumericField(VCLXWindow* pVCLXindow);
 
+virtual void ProcessWindowEvent(const VclWindowEvent& rVclWindowEvent) 
override;
+
 // XAccessibleContext
 virtual sal_Int16 SAL_CALL getAccessibleRole() override;
 
diff --git a/accessibility/source/standard/svtaccessiblenumericfield.cxx 
b/accessibility/source/standard/svtaccessiblenumericfield.cxx
index 2862a3a2b670..f3192d4212f0 100644
--- a/accessibility/source/standard/svtaccessiblenumericfield.cxx
+++ b/accessibility/source/standard/svtaccessiblenumericfield.cxx
@@ -21,6 +21,7 @@
 #include 
 #include 
 
+#include 
 #include 
 
 using namespace ::com::sun::star::accessibility;
@@ -31,6 +32,17 @@ 
SVTXAccessibleNumericField::SVTXAccessibleNumericField(VCLXWindow* pVCLWindow)
 {
 }
 
+void SVTXAccessibleNumericField::ProcessWindowEvent(const VclWindowEvent& 
rVclWindowEvent)
+{
+VCLXAccessibleEdit::ProcessWindowEvent(rVclWindowEvent);
+
+if (rVclWindowEvent.GetId() == VclEventId::EditModify)
+{
+css::uno::Any aNewValue = getCurrentValue();
+NotifyAccessibleEvent(AccessibleEventId::VALUE_CHANGED, 
css::uno::Any(), aNewValue);
+}
+}
+
 sal_Int16 SVTXAccessibleNumericField::getAccessibleRole() { return 
AccessibleRole::SPIN_BOX; }
 
 css::uno::Any SAL_CALL SVTXAccessibleNumericField::getCurrentValue()

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

[Michael Weghorn (via logerrit)]

 sfx2/source/control/thumbnailviewacc.cxx |7 +++
 1 file changed, 3 insertions(+), 4 deletions(-)

New commits:
commit 86bbf9a4eca0e96b282f656c7dc0cf11ff80c9f9
Author: Michael Weghorn 
AuthorDate: Fri Apr 14 17:33:13 2023 +0300
Commit: Michael Weghorn 
CommitDate: Sat Apr 15 05:38:19 2023 +0200

a11y: Report focusable and focused state for ThumbnailViewItem

Basically the same as
Change-Id I3f14047fe721c4a2bc0c6acb2d32f185d0eed204
"a11y: Report focusable and focused state for ValueSetItem",
but for `ThumbnailViewItemAcc`.

Makes Orca with the qt6 VCL plugin announce the selected/focused
item in the recent documents view in the LO start center.

Change-Id: I8ab259ce6649904b42367ac30e4efbd6ab62cb6e
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/150419
Tested-by: Jenkins
Reviewed-by: Michael Weghorn 

diff --git a/sfx2/source/control/thumbnailviewacc.cxx 
b/sfx2/source/control/thumbnailviewacc.cxx
index f157b155cddd..f4ec85e5a89a 100644
--- a/sfx2/source/control/thumbnailviewacc.cxx
+++ b/sfx2/source/control/thumbnailviewacc.cxx
@@ -677,15 +677,14 @@ sal_Int64 SAL_CALL 
ThumbnailViewItemAcc::getAccessibleStateSet()
 if ( !mbIsTransientChildrenDisabled )
 nStateSet |= accessibility::AccessibleStateType::TRANSIENT;
 
-// SELECTABLE
 nStateSet |= accessibility::AccessibleStateType::SELECTABLE;
-//  pStateSet->AddState( 
accessibility::AccessibleStateType::FOCUSABLE );
+nStateSet |= accessibility::AccessibleStateType::FOCUSABLE;
 
-// SELECTED
 if( mpParent->isSelected() )
 {
 nStateSet |= accessibility::AccessibleStateType::SELECTED;
-//  pStateSet->AddState( 
accessibility::AccessibleStateType::FOCUSED );
+if (mpParent->mrParent.HasChildFocus())
+nStateSet |= accessibility::AccessibleStateType::FOCUSED;
 }
 }
 

[Libreoffice-commits] core.git: 2 commits - svtools/source vcl/qt5

[Michael Weghorn (via logerrit)]

 svtools/source/control/valueacc.cxx   |8 
 vcl/qt5/QtAccessibleEventListener.cxx |   28 +---
 2 files changed, 25 insertions(+), 11 deletions(-)

New commits:
commit 0dc23570a033b69dfcaec64de18c3c0bbd2ad151
Author: Michael Weghorn 
AuthorDate: Fri Apr 14 17:22:57 2023 +0300
Commit: Michael Weghorn 
CommitDate: Sat Apr 15 05:38:12 2023 +0200

a11y: Report focusable and focused state for ValueSetItem

With this in place, Orca now also announces the selected
color when moving focus in the list of available colors
in the Writer toolbar font color popup
when using the qt6 VCL plugin.

Change-Id: I3f14047fe721c4a2bc0c6acb2d32f185d0eed204
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/150418
Tested-by: Jenkins
Reviewed-by: Michael Weghorn 

diff --git a/svtools/source/control/valueacc.cxx 
b/svtools/source/control/valueacc.cxx
index 9e496f6adcc8..1ba2c79dbbab 100644
--- a/svtools/source/control/valueacc.cxx
+++ b/svtools/source/control/valueacc.cxx
@@ -210,15 +210,15 @@ sal_Int64 SAL_CALL ValueItemAcc::getAccessibleStateSet()
 if ( !mbIsTransientChildrenDisabled )
 nStateSet |= accessibility::AccessibleStateType::TRANSIENT;
 
-// SELECTABLE
 nStateSet |= accessibility::AccessibleStateType::SELECTABLE;
-//  pStateSet->AddState( 
accessibility::AccessibleStateType::FOCUSABLE );
+nStateSet |= accessibility::AccessibleStateType::FOCUSABLE;
 
-// SELECTED
 if( mpParent->mrParent.GetSelectedItemId() == mpParent->mnId )
 {
+
 nStateSet |= accessibility::AccessibleStateType::SELECTED;
-//  pStateSet->AddState( 
accessibility::AccessibleStateType::FOCUSED );
+if (mpParent->mrParent.HasChildFocus())
+nStateSet |= accessibility::AccessibleStateType::FOCUSED;
 }
 }
 
commit 734d10ed3612d75edcee145475ddd0b0165efeac
Author: Michael Weghorn 
AuthorDate: Fri Apr 14 16:57:09 2023 +0300
Commit: Michael Weghorn 
CommitDate: Sat Apr 15 05:38:02 2023 +0200

qt a11y: Send QAccessible::ObjectCreated event for correct object

When an `AccessibleEventId::CHILD` event with
its s `NewValue` set is received, that means that
this a11y child object has been created, so the
`QAccessible::ObjectCreated` event needs to be
sent for the newly created object, not the accessible
interface of the listener (which is the parent).

This makes announcement of (part of) the font color popup
button in Writer's toolbar generally work with Orca and the
qt6 VCL plugin e.g. the buttons in the popup are now announced
(but the colors are not yet).

Adapting this for the case where a child has
been removed (bridged to Qt as `QAccessible::ObjectDestroyed`
event) would currently results in crashes when closing the
application e.g. after using the character font color popup in
the Writer toolbar. This needs further investigation, so don't
send the event for now, but add a `SAL_WARN`.

Also warn when receiving a `CHILD` event with neither `OldValue`
nore `NewValue` set, since that shouldn't happen,
s.a. documentation in
`offapi/com/sun/star/accessibility/AccessibleEventId.idl`.

Change-Id: I183e71de061489fdc9751620820268f280f1949f
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/150417
Tested-by: Jenkins
Reviewed-by: Michael Weghorn 

diff --git a/vcl/qt5/QtAccessibleEventListener.cxx 
b/vcl/qt5/QtAccessibleEventListener.cxx
index f9a4d7b1a2c1..59d7dd0a8717 100644
--- a/vcl/qt5/QtAccessibleEventListener.cxx
+++ b/vcl/qt5/QtAccessibleEventListener.cxx
@@ -170,7 +170,6 @@ void QtAccessibleEventListener::notifyEvent(const 
css::accessibility::Accessible
 {
 QAccessibleInterface* pQAccessibleInterface = m_pAccessibleWidget;
 
-Reference xChild;
 switch (aEvent.EventId)
 {
 case AccessibleEventId::NAME_CHANGED:
@@ -213,14 +212,29 @@ void QtAccessibleEventListener::notifyEvent(const 
css::accessibility::Accessible
 }
 case AccessibleEventId::CHILD:
 {
-QAccessible::Event event = QAccessible::InvalidEvent;
-if (aEvent.OldValue >>= xChild)
-event = QAccessible::ObjectDestroyed;
+Reference xChild;
 if (aEvent.NewValue >>= xChild)
-event = QAccessible::ObjectCreated;
-if (event != QAccessible::InvalidEvent)
+{
+QAccessible::updateAccessibility(new QAccessibleEvent(
+QtAccessibleRegistry::getQObject(xChild), 
QAccessible::ObjectCreated));
+return;
+}
+if (aEvent.OldValue >>= xChild)
+{
+// Forwarding as QAccessible::ObjectDestroyed event currently 
results in crashes on close
+// e.g. after using the character font color popup in the 

[Libreoffice-bugs] [Bug 154815] UI: Cell cursor width has increased

[bugzilla-daemon]

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

m.a.riosv  changed:

   What|Removed |Added

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

--- Comment #1 from m.a.riosv  ---
Please attach the info in Menu/Help/About LibreOffice (there is an icon to
copy)

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

[Libreoffice-bugs] [Bug 154683] XML Form Document: Named folder "Instance 1" appears as "Instance" before chosen.

[bugzilla-daemon]

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

QA Administrators  changed:

   What|Removed |Added

   Keywords||bibisectRequest

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

[Libreoffice-bugs] [Bug 154528] FILEOPEN PPTX: some bullet points show smaller than in PowerPoint

[bugzilla-daemon]

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

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 145251] Hunspell produces non-valid compounding results (for Dutch)

[bugzilla-daemon]

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

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 154503] XML Form Document: Creating of Bindings by Mouseclick on Instance Elements only shown after reopening document

[bugzilla-daemon]

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

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 154487] Enhancement Request: Allow LibreOffice Mail Merge to use default e-mail client

[bugzilla-daemon]

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

QA Administrators  changed:

   What|Removed |Added

 Ever confirmed|1   |0
 Status|NEEDINFO|UNCONFIRMED

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

[Libreoffice-bugs] [Bug 154511] In holehonnuru twon panchayth office we use property tax calaculator now we are not able to login to the property tax calaculator we want update the taxes by 3% so we n

[bugzilla-daemon]

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

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 154498] blind selected checkbox colours in configuration dialogue listboxes

[bugzilla-daemon]

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

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 154519] When in Xmind app i export powerpoint file , and i open it in impress remote dont work good , and the powerpoint distroyed.

[bugzilla-daemon]

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

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 154487] Enhancement Request: Allow LibreOffice Mail Merge to use default e-mail client

[bugzilla-daemon]

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

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

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

[Libreoffice-ux-advise] [Bug 154487] Enhancement Request: Allow LibreOffice Mail Merge to use default e-mail client

[bugzilla-daemon]

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

QA Administrators  changed:

   What|Removed |Added

 Ever confirmed|1   |0
 Status|NEEDINFO|UNCONFIRMED

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

[Libreoffice-bugs] [Bug 153777] FLUID page number indication option: on / off

[bugzilla-daemon]

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

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 154487] Enhancement Request: Allow LibreOffice Mail Merge to use default e-mail client

[bugzilla-daemon]

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

--- Comment #9 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 151555] Save As PDF fails

[bugzilla-daemon]

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

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

This bug has been in NEEDINFO status with no change for at least
6 months. Please provide the requested information as soon as
possible and mark the bug as UNCONFIRMED. Due to regular bug
tracker maintenance, if the bug is still in NEEDINFO status with
no change in 30 days the QA team will close the bug as INSUFFICIENTDATA
due to lack of needed information.

For more information about our NEEDINFO policy please read the
wiki located here:
https://wiki.documentfoundation.org/QA/Bugzilla/Fields/Status/NEEDINFO

If you have already provided the requested information, please
mark the bug as UNCONFIRMED so that the QA team knows that the
bug is ready to be confirmed.

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

Warm Regards,
QA Team

MassPing-NeedInfo-Ping

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

[Libreoffice-bugs] [Bug 153777] FLUID page number indication option: on / off

[bugzilla-daemon]

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

--- 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 150978] Calc randomly replacing Chart Data Ranges with Data Tables

[bugzilla-daemon]

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

QA Administrators  changed:

   What|Removed |Added

 Resolution|--- |INSUFFICIENTDATA
 Status|NEEDINFO|RESOLVED

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

[Libreoffice-bugs] [Bug 151231] Change tracking formatting can't be modified

[bugzilla-daemon]

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

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

This bug has been in NEEDINFO status with no change for at least
6 months. Please provide the requested information as soon as
possible and mark the bug as UNCONFIRMED. Due to regular bug
tracker maintenance, if the bug is still in NEEDINFO status with
no change in 30 days the QA team will close the bug as INSUFFICIENTDATA
due to lack of needed information.

For more information about our NEEDINFO policy please read the
wiki located here:
https://wiki.documentfoundation.org/QA/Bugzilla/Fields/Status/NEEDINFO

If you have already provided the requested information, please
mark the bug as UNCONFIRMED so that the QA team knows that the
bug is ready to be confirmed.

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

Warm Regards,
QA Team

MassPing-NeedInfo-Ping

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

[Libreoffice-bugs] [Bug 150978] Calc randomly replacing Chart Data Ranges with Data Tables

[bugzilla-daemon]

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

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

Please read this message in its entirety before proceeding.

Your bug report is being closed as INSUFFICIENTDATA due to inactivity and
a lack of information which is needed in order to accurately
reproduce and confirm the problem. We encourage you to retest
your bug against the latest release. If the issue is still
present in the latest stable release, we need the following
information (please ignore any that you've already provided):

a) Provide details of your system including your operating
   system and the latest version of LibreOffice that you have
   confirmed the bug to be present

b) Provide easy to reproduce steps – the simpler the better

c) Provide any test case(s) which will help us confirm the problem

d) Provide screenshots of the problem if you think it might help

e) Read all comments and provide any requested information

Once all of this is done, please set the bug back to UNCONFIRMED
and we will attempt to reproduce the issue. Please do not:

a) respond via email 

b) update the version field in the bug or any of the other details
   on the top section of our bug tracker

Warm Regards,
QA Team

MassPing-NeedInfo-FollowUp

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

[Libreoffice-bugs] [Bug 142066] Writer crashes if attempt to open insert special characters

[bugzilla-daemon]

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

--- Comment #5 from QA Administrators  ---
Dear Kris Roberts,

This bug has been in NEEDINFO status with no change for at least
6 months. Please provide the requested information as soon as
possible and mark the bug as UNCONFIRMED. Due to regular bug
tracker maintenance, if the bug is still in NEEDINFO status with
no change in 30 days the QA team will close the bug as INSUFFICIENTDATA
due to lack of needed information.

For more information about our NEEDINFO policy please read the
wiki located here:
https://wiki.documentfoundation.org/QA/Bugzilla/Fields/Status/NEEDINFO

If you have already provided the requested information, please
mark the bug as UNCONFIRMED so that the QA team knows that the
bug is ready to be confirmed.

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

Warm Regards,
QA Team

MassPing-NeedInfo-Ping

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

[Libreoffice-bugs] [Bug 92164] FILESAVE XLS Excessive number of rows warning (see comment 10)

[bugzilla-daemon]

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

--- Comment #37 from QA Administrators  ---
Dear gmarco,

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 99025] [FORMATTING, FILESAVE] Table's Column break-After is not properly exported as .doc/.docx

[bugzilla-daemon]

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

--- Comment #6 from QA Administrators  ---
Dear Nicolas Mailhot,

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 90939] Editing: Footnote (only one in the doc) inserted on last line of last column in section is not visible without extra editing

[bugzilla-daemon]

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

--- Comment #8 from QA Administrators  ---
Dear Gordo,

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 45386] Column formatting not honored saving to .doc/.docx (probably because TOC is a section?)

[bugzilla-daemon]

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

--- Comment #14 from QA Administrators  ---
Dear Vadim Rutkovsky,

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 90031] Sidebar: Tab icons do not change size based on preference

[bugzilla-daemon]

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

--- Comment #11 from QA Administrators  ---
Dear Nikos Platis,

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 141029] Unable to delete form in form browser if it contain hidden field

[bugzilla-daemon]

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

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

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 134702] Additional page added after pressing undo, not there upon reopen

[bugzilla-daemon]

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

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

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

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

If you have time, please do the following:

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

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

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

Please DO NOT

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


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

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


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

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

Warm Regards,
QA Team

MassPing-UntouchedBug

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

[Libreoffice-bugs] [Bug 126239] Option “Sidebar icon size” has no Effect on Several Icons of the Sidebar

[bugzilla-daemon]

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

--- Comment #9 from QA Administrators  ---
Dear Harald Koester,

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 123729] User information (name / picture) missing

[bugzilla-daemon]

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

--- Comment #12 from QA Administrators  ---
Dear Nicolas Christener,

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 108240] Selection line around one cell invisible when cell has a black background color

[bugzilla-daemon]

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

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

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 154499] we are write two or more word local or other language word example(amma appa )in LibreOffice ignore at a time

[bugzilla-daemon]

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

Nehru  changed:

   What|Removed |Added

Summary|Accept consecutive words|we are write two or more
   |with spaces aka phrases in  |word local or other
   |spellchecker|language word example(amma
   ||appa )in LibreOffice ignore
   ||at a time

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

[Libreoffice-bugs] [Bug 154506] some fonts are removed from the system after installations (updates) of Libre Office

[bugzilla-daemon]

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

--- Comment #2 from خالد حسني  ---
If this issue is seen since 6.x then it is probably unrelated to my xhanges.

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

[Libreoffice-bugs] [Bug 151728] Pasting formula code under a heading is breaking all heading styles without possibility of undoing it

[bugzilla-daemon]

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

--- Comment #5 from loma...@gmail.com ---
There are strange similarities to bug 147953 which I am waiting to get fixed.
https://bugs.documentfoundation.org/show_bug.cgi?id=147953

This bug and 147953 can both be triggered by pasting in any text from MS Word
or the Windows character map.

I found this bug on Google by searching for "FrameAutowidthWithMorePara" which
seems to be the culprit in 147953. Not sure why it would be applicable here
though, since this is an issue with headings and indents, not frames.

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

[Libreoffice-bugs] [Bug 154817] New: Direct paragraph formatting using Paragraph dialog always adds 'Fill Gradient Name' and 'Fill Hatch Name' to paragraph direct formatting

[bugzilla-daemon]

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

Bug ID: 154817
   Summary: Direct paragraph formatting using Paragraph dialog
always adds 'Fill Gradient Name' and 'Fill Hatch Name'
to paragraph direct formatting
   Product: LibreOffice
   Version: 7.3.0.0 alpha0+
  Hardware: All
OS: All
Status: UNCONFIRMED
  Severity: normal
  Priority: medium
 Component: Writer
  Assignee: libreoffice-bugs@lists.freedesktop.org
  Reporter: rayk...@gmail.com

Steps to reproduce:

1. Open a new text document
2. Open the Styles Inspector
Ctrl+Alt+6 or Menu > View > Sidebar > Styles Inspector
3. Type a word or sentence, perhaps 'Lorem ipsum dolor'
4. Add a paragraph direct format property by using the Paragraph dialog
Menu > Format > Paragraph...
5. Change a property in the Paragraph dialog then press OK 

Results: The Styles Inspector shows 'Fill Gradient Name' and 'Fill Hatch Name'
under Paragraph Direct Formatting whenever a paragraph property is changed
using the Paragraph dialog.

Prior to  commit 3f6797c29e9672eba354400f24a669244fd746c0 'Fill Gradient Name'
and 'Fill Hatch Name' were not added.

Author: Justin Luth 
Date:   Mon Jun 21 16:56:04 2021 +0200

tdf#132776 sw UI: make unique names for custom hatch and gradient

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

[Libreoffice-bugs] [Bug 154037] MySQL/MariaDB direct connection: Deleted tables won't be deleted in content.xml, when deleted directly in MySQL

[bugzilla-daemon]

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

--- Comment #2 from flywire  ---
https://ask.libreoffice.org/t/possible-synch-error-between-mysql-and-base/88846/14

> AndrewBase 2.2.4 speaks precisely about this issue. There is a workaround 
> listed > there, which I have slightly modified, and it seems to be working 
> just fine:

sub refreshTables()
dim dbURL as string: dbURL = ConvertToURL(“C:\filename.odb”)
dim oBaseContext as object: oBaseContext =
CreateUnoService(“com.sun.star.sdb.DatabaseContext”)
dim oDB as object: oDB = oBaseContext.getByName(dbURL)
dim oDoc as object: oDoc = oDB.DatabaseDocument
dim oDisp as object: oDisp =
createUnoService(“com.sun.star.frame.DispatchHelper”)
dim oFrame as object: oFrame = oDoc.getCurrentController().getFrame()

oDisp.executeDispatch(oFrame, “.uno:DBRefreshTables”, “”, 0, Array())
end sub


Download AndrewBase from https://www.pitonyak.org/database/ - 2.2.4 Refresh the
tables

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

[Libreoffice-bugs] [Bug 108253] [META] Calc cell formula bugs and enhancements

[bugzilla-daemon]

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

Bug 138220 Summary: calc: calculation: roundup: rounddown: fail in 7.1 alpha
https://bugs.documentfoundation.org/show_bug.cgi?id=138220

   What|Removed |Added

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

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

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

[Eike Rathke (via logerrit)]

 sc/source/core/tool/interpr2.cxx |   49 +--
 1 file changed, 42 insertions(+), 7 deletions(-)

New commits:
commit 8186a01f2a26f05645a2a3c9c93b453bd35b796f
Author: Eike Rathke 
AuthorDate: Sat Apr 15 01:38:39 2023 +0200
Commit: Eike Rathke 
CommitDate: Sat Apr 15 03:40:44 2023 +0200

Resolves: tdf#138220 tdf#154792 Avoid double rounding; tdf#124286 follow-up

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

diff --git a/sc/source/core/tool/interpr2.cxx b/sc/source/core/tool/interpr2.cxx
index 58b3008319ca..cf4dde09338c 100644
--- a/sc/source/core/tool/interpr2.cxx
+++ b/sc/source/core/tool/interpr2.cxx
@@ -963,20 +963,55 @@ void ScInterpreter::RoundNumber( rtl_math_RoundingMode 
eMode )
 fVal = ::rtl::math::round( GetDouble(), 0, eMode );
 else
 {
-sal_Int16 nDec = GetInt16();
-double fX = GetDouble();
+const sal_Int16 nDec = GetInt16();
+const double fX = GetDouble();
 if (nGlobalError == FormulaError::NONE)
 {
+// A quite aggressive approach with 12 significant digits.
+// However, using 14 or some other doesn't work because other
+// values may fail, like =ROUNDDOWN(2-5E-015;13) would produce
+// 2 (another example in tdf#124286).
+constexpr sal_Int16 kSigDig = 12;
+
 if ( ( eMode == rtl_math_RoundingMode_Down ||
eMode == rtl_math_RoundingMode_Up ) &&
- nDec < 12 && fmod( fX, 1.0 ) != 0.0 )
+ nDec < kSigDig && fmod( fX, 1.0 ) != 0.0 )
+
 {
-// tdf124286 : round to 12 significant digits before rounding
+// tdf124286 : round to significant digits before rounding
 // down or up to avoid unexpected rounding errors
 // caused by decimal -> binary -> decimal 
conversion
-double fRes;
-RoundSignificant( fX, 12, fRes );
-fVal = ::rtl::math::round( fRes, nDec, eMode );
+
+double fRes = fX;
+// Similar to RoundSignificant() but omitting the back-scaling
+// and interim integer rounding before the final rounding,
+// which would result in double rounding. Instead, adjust the
+// decimals and round into integer part before scaling back.
+const double fTemp = floor( log10( std::abs(fRes))) + 1.0 - 
kSigDig;
+// Avoid inaccuracy of negative powers of 10.
+if (fTemp < 0.0)
+fRes *= pow(10.0, -fTemp);
+else
+fRes /= pow(10.0, fTemp);
+if (std::isfinite(fRes))
+{
+// fRes is now at a decimal normalized scale.
+// Truncate up-rounding to opposite direction for values
+// like 0.0605 =ROUNDUP(8.06-8;2) that here now
+// is 6000.005 and otherwise would yield 0.07
+if (eMode == rtl_math_RoundingMode_Up)
+fRes = ::rtl::math::approxFloor(fRes);
+fVal = ::rtl::math::round( fRes, nDec + fTemp, eMode );
+if (fTemp < 0.0)
+fVal /= pow(10.0, -fTemp);
+else
+fVal *= pow(10.0, fTemp);
+}
+else
+{
+// Overflow. Let our round() decide if and how to round.
+fVal = ::rtl::math::round( fX, nDec, eMode );
+}
 }
 else
 fVal = ::rtl::math::round( fX, nDec, eMode );

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

[Eike Rathke (via logerrit)]

 sc/source/core/tool/interpr2.cxx |   17 +++--
 1 file changed, 15 insertions(+), 2 deletions(-)

New commits:
commit 397d12997a604730ad11316faa34cefd470ee0ff
Author: Eike Rathke 
AuthorDate: Sat Apr 15 01:01:58 2023 +0200
Commit: Eike Rathke 
CommitDate: Sat Apr 15 03:40:24 2023 +0200

ROUNDSIG() Avoid inaccuracy of pow(10,negative) tdf#138220, tdf#105931 
follow

https://bugs.documentfoundation.org/show_bug.cgi?id=138220#c6
(otherwise unrelated) has an example of
=RAWSUBTRACT(ROUNDSIG(-999.13;12);-999.13)
resulting in -0,11368684 instead of 0, due to these
0.1 ... inexact negative power of 10 values.

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

diff --git a/sc/source/core/tool/interpr2.cxx b/sc/source/core/tool/interpr2.cxx
index b8fe537ef3f9..58b3008319ca 100644
--- a/sc/source/core/tool/interpr2.cxx
+++ b/sc/source/core/tool/interpr2.cxx
@@ -1002,8 +1002,21 @@ void ScInterpreter::ScRoundUp()
 
 void ScInterpreter::RoundSignificant( double fX, double fDigits, double  )
 {
-double fTemp = ::rtl::math::approxFloor( log10( std::abs(fX) ) ) + 1.0 - 
fDigits;
-fRes = ::rtl::math::round( pow(10.0, -fTemp ) * fX ) * pow( 10.0, fTemp );
+double fTemp = floor( log10( std::abs(fX) ) ) + 1.0 - fDigits;
+double fIn = fX;
+// Avoid inaccuracy of negative powers of 10.
+if (fTemp < 0.0)
+fIn *= pow(10.0, -fTemp);
+else
+fIn /= pow(10.0, fTemp);
+// For very large fX there might be an overflow in fIn resulting in
+// non-finite. rtl::math::round() handles that and it will be propagated as
+// usual.
+fRes = ::rtl::math::round(fIn);
+if (fTemp < 0.0)
+fRes /= pow(10.0, -fTemp);
+else
+fRes *= pow(10.0, fTemp);
 }
 
 // tdf#105931

[Libreoffice-commits] core.git: Branch 'distro/cib/libreoffice-6-4' - helpcontent2

[Michael Stahl (via logerrit)]

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

New commits:
commit f6c33a29cb9091936bd113551fe0525d3d0042b6
Author: Michael Stahl 
AuthorDate: Sat Apr 15 03:22:00 2023 +0200
Commit: Gerrit Code Review 
CommitDate: Sat Apr 15 03:22:00 2023 +0200

Update git submodules

* Update helpcontent2 from branch 'distro/cib/libreoffice-6-4'
  to 92adb81e1e5ed153aac049648aec0a0a87a8768f
  - add help for Common::Load::ViewPositionForAnyUser checkbox

Change-Id: I49f0c83665955ae9db3ea9187418d0d093a88df9

diff --git a/helpcontent2 b/helpcontent2
index 5995b61e8d08..92adb81e1e5e 16
--- a/helpcontent2
+++ b/helpcontent2
@@ -1 +1 @@
-Subproject commit 5995b61e8d08489f44e0473f8d0d21e189a0b3db
+Subproject commit 92adb81e1e5ed153aac049648aec0a0a87a8768f

[Libreoffice-commits] help.git: Changes to 'distro/cib/libreoffice-6-4'

[Michael Stahl (via logerrit)]

New branch 'distro/cib/libreoffice-6-4' available with the following commits:
commit 92adb81e1e5ed153aac049648aec0a0a87a8768f
Author: Michael Stahl 
Date:   Fri Apr 14 19:08:24 2023 +0200

add help for Common::Load::ViewPositionForAnyUser checkbox

Change-Id: I49f0c83665955ae9db3ea9187418d0d093a88df9

[Libreoffice-commits] core.git: framework/source svtools/source

[Mike Kaganski (via logerrit)]

 framework/source/uielement/buttontoolbarcontroller.cxx |   15 ---
 svtools/source/uno/statusbarcontroller.cxx |   15 ---
 svtools/source/uno/toolboxcontroller.cxx   |   15 ---
 3 files changed, 12 insertions(+), 33 deletions(-)

New commits:
commit 4578ded393f8e97ae781f63c9a1cf57669409635
Author: Mike Kaganski 
AuthorDate: Sat Apr 15 01:13:22 2023 +0300
Commit: Mike Kaganski 
CommitDate: Sat Apr 15 03:05:26 2023 +0200

Simplify initialized check

The previous complexity did nothing useful; it allowed to have a single
unguarded boolean value check, for the cost of releasing and acquiring
the mutex again.

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

diff --git a/framework/source/uielement/buttontoolbarcontroller.cxx 
b/framework/source/uielement/buttontoolbarcontroller.cxx
index 4972b6da7667..d94e5b0ff25f 100644
--- a/framework/source/uielement/buttontoolbarcontroller.cxx
+++ b/framework/source/uielement/buttontoolbarcontroller.cxx
@@ -90,21 +90,14 @@ void SAL_CALL ButtonToolbarController::release() noexcept
 void SAL_CALL ButtonToolbarController::initialize(
 const css::uno::Sequence< css::uno::Any >& aArguments )
 {
-bool bInitialized( true );
-
-{
-SolarMutexGuard aSolarMutexGuard;
-
-if ( m_bDisposed )
-throw DisposedException();
+SolarMutexGuard aSolarMutexGuard;
 
-bInitialized = m_bInitialized;
-}
+if ( m_bDisposed )
+throw DisposedException();
 
-if ( bInitialized )
+if ( m_bInitialized )
 return;
 
-SolarMutexGuard aSolarMutexGuard;
 m_bInitialized = true;
 
 PropertyValue aPropValue;
diff --git a/svtools/source/uno/statusbarcontroller.cxx 
b/svtools/source/uno/statusbarcontroller.cxx
index 76387cbad0fd..6a8499a353c7 100644
--- a/svtools/source/uno/statusbarcontroller.cxx
+++ b/svtools/source/uno/statusbarcontroller.cxx
@@ -120,21 +120,14 @@ void SAL_CALL StatusbarController::release() noexcept
 
 void SAL_CALL StatusbarController::initialize( const Sequence< Any >& 
aArguments )
 {
-bool bInitialized( true );
-
-{
-SolarMutexGuard aSolarMutexGuard;
-
-if ( m_bDisposed )
-throw DisposedException();
+SolarMutexGuard aSolarMutexGuard;
 
-bInitialized = m_bInitialized;
-}
+if ( m_bDisposed )
+throw DisposedException();
 
-if ( bInitialized )
+if ( m_bInitialized )
 return;
 
-SolarMutexGuard aSolarMutexGuard;
 m_bInitialized = true;
 
 PropertyValue aPropValue;
diff --git a/svtools/source/uno/toolboxcontroller.cxx 
b/svtools/source/uno/toolboxcontroller.cxx
index 8fe4eb37c621..b592bb25b859 100644
--- a/svtools/source/uno/toolboxcontroller.cxx
+++ b/svtools/source/uno/toolboxcontroller.cxx
@@ -163,21 +163,14 @@ css::uno::Sequence 
ToolboxController::getTypes()
 
 void SAL_CALL ToolboxController::initialize( const Sequence< Any >& aArguments 
)
 {
-bool bInitialized( true );
-
-{
-SolarMutexGuard aSolarMutexGuard;
-
-if ( m_bDisposed )
-throw DisposedException();
+SolarMutexGuard aSolarMutexGuard;
 
-bInitialized = m_bInitialized;
-}
+if ( m_bDisposed )
+throw DisposedException();
 
-if ( bInitialized )
+if ( m_bInitialized )
 return;
 
-SolarMutexGuard aSolarMutexGuard;
 m_bInitialized = true;
 m_bSupportVisible = false;
 PropertyValue aPropValue;

[Libreoffice-bugs] [Bug 154703] META Export DOCX flies with framePr instead of DrawingDML

[bugzilla-daemon]

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

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

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

tdf#154703 docx export framePr: export xAlign/yAlign

It will be available in 7.6.0.

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

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

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

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

[Justin Luth (via logerrit)]

 sw/qa/extras/ooxmlexport/ooxmlexport5.cxx|2 ++
 sw/source/filter/ww8/docxattributeoutput.cxx |   15 ---
 2 files changed, 14 insertions(+), 3 deletions(-)

New commits:
commit e07d5c089ab2e8fe8a5cfa2a11cef3f1cf3afab3
Author: Justin Luth 
AuthorDate: Fri Apr 14 12:26:40 2023 -0400
Commit: Justin Luth 
CommitDate: Sat Apr 15 02:42:17 2023 +0200

tdf#154703 docx export framePr: export xAlign/yAlign

This fixes a regression in LO 4.4
from commit 1c876f5616522ab695de8c0316cdb0c601081815.

The relative positions (left,right, center, inside, outside)
(top, bottom...) were simply ignored on export.

Change-Id: Ie12eb75483fbc3f05c77e45d40e4a18a7ead5b1e
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/150430
Tested-by: Jenkins
Reviewed-by: Justin Luth 

diff --git a/sw/qa/extras/ooxmlexport/ooxmlexport5.cxx 
b/sw/qa/extras/ooxmlexport/ooxmlexport5.cxx
index 84d8b45cddf0..ef1e15eafea5 100644
--- a/sw/qa/extras/ooxmlexport/ooxmlexport5.cxx
+++ b/sw/qa/extras/ooxmlexport/ooxmlexport5.cxx
@@ -1417,6 +1417,8 @@ CPPUNIT_TEST_FIXTURE(Test, testTdf112287)
 
 assertXPath(pXmlDocument, 
"/w:document/w:body/w:p[1]/w:pPr/w:framePr","vAnchor","margin");
 assertXPath(pXmlDocument, 
"/w:document/w:body/w:p[1]/w:pPr/w:framePr","hAnchor","text");
+assertXPath(pXmlDocument, 
"/w:document/w:body/w:p[1]/w:pPr/w:framePr","xAlign","center");
+assertXPath(pXmlDocument, 
"/w:document/w:body/w:p[1]/w:pPr/w:framePr","yAlign","bottom");
 }
 
 CPPUNIT_TEST_FIXTURE(Test, testTdf112287B)
diff --git a/sw/source/filter/ww8/docxattributeoutput.cxx 
b/sw/source/filter/ww8/docxattributeoutput.cxx
index 0f34bc7b645b..d83cc1cdcc63 100644
--- a/sw/source/filter/ww8/docxattributeoutput.cxx
+++ b/sw/source/filter/ww8/docxattributeoutput.cxx
@@ -904,7 +904,9 @@ void DocxAttributeOutput::PopulateFrameProperties(const 
SwFrameFormat* pFrameFor
 {
 rtl::Reference attrList = 
FastSerializerHelper::createAttrList();
 
-awt::Point aPos(pFrameFormat->GetHoriOrient().GetPos(), 
pFrameFormat->GetVertOrient().GetPos());
+const SwFormatHoriOrient& rHoriOrient = pFrameFormat->GetHoriOrient();
+const SwFormatVertOrient& rVertOrient = pFrameFormat->GetVertOrient();
+awt::Point aPos(rHoriOrient.GetPos(), rVertOrient.GetPos());
 
 attrList->add( FSNS( XML_w, XML_w), OString::number(rSize.Width()));
 attrList->add( FSNS( XML_w, XML_h), OString::number(rSize.Height()));
@@ -920,8 +922,15 @@ void DocxAttributeOutput::PopulateFrameProperties(const 
SwFrameFormat* pFrameFor
 attrList->add(FSNS(XML_w, XML_hSpace), OString::number((nLeft + nRight) / 
2));
 attrList->add(FSNS(XML_w, XML_vSpace), OString::number((nUpper + nLower) / 
2));
 
-OString relativeFromH = convertToOOXMLHoriOrientRel( 
pFrameFormat->GetHoriOrient().GetRelationOrient() );
-OString relativeFromV = convertToOOXMLVertOrientRel( 
pFrameFormat->GetVertOrient().GetRelationOrient() );
+OString relativeFromH = 
convertToOOXMLHoriOrientRel(rHoriOrient.GetRelationOrient());
+OString relativeFromV = 
convertToOOXMLVertOrientRel(rVertOrient.GetRelationOrient());
+
+OString aXAlign = convertToOOXMLHoriOrient(rHoriOrient.GetHoriOrient(), 
/*bIsPosToggle=*/false);
+OString aYAlign = convertToOOXMLVertOrient(rVertOrient.GetVertOrient());
+if (!aXAlign.isEmpty())
+attrList->add(FSNS(XML_w, XML_xAlign), aXAlign);
+if (!aYAlign.isEmpty())
+attrList->add(FSNS(XML_w, XML_yAlign), aYAlign);
 
 switch (pFrameFormat->GetSurround().GetValue())
 {

[Libreoffice-bugs] [Bug 152827] Distance between symbol and index adjustable

[bugzilla-daemon]

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

Stéphane Guillou (stragu)  changed:

   What|Removed |Added

 CC||stephane.guillou@libreoffic
   ||e.org
 Whiteboard| QA:needsComment|
 OS|Windows (All)   |All

--- Comment #1 from Stéphane Guillou (stragu) 
 ---
It's true that Format > Spacing, using the Indexes Category, does not allow
changing the horizontal spacing.

Does using csub help?
E.g.:

T csub g

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

[Libreoffice-bugs] [Bug 153370] Language drop down menu obscured in Review panel in References screen in Collabora on iPad

[bugzilla-daemon]

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

Stéphane Guillou (stragu)  changed:

   What|Removed |Added

 CC||stephane.guillou@libreoffic
   ||e.org
 Whiteboard| QA:needsComment|
 Resolution|--- |MOVED
 Status|UNCONFIRMED |RESOLVED

--- Comment #1 from Stéphane Guillou (stragu) 
 ---
Hi Roger
As this is specific to the Collabora app (TDF does not currently provide an
iPad version), please report it on their GitHub issue tracker:
https://github.com/CollaboraOnline/online/issues
Thank you!

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

[Libreoffice-bugs] [Bug 99648] [META] Improve Layer Handling

[bugzilla-daemon]

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

Stéphane Guillou (stragu)  changed:

   What|Removed |Added

 Depends on||153432


Referenced Bugs:

https://bugs.documentfoundation.org/show_bug.cgi?id=153432
[Bug 153432] Add buttons to toggle layer visibility and locked state
-- 
You are receiving this mail because:
You are the assignee for the bug.

[Libreoffice-bugs] [Bug 99648] [META] Improve Layer Handling

[bugzilla-daemon]

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

Bug 153432 Summary: Add buttons to toggle layer visibility and locked state
https://bugs.documentfoundation.org/show_bug.cgi?id=153432

   What|Removed |Added

 Status|UNCONFIRMED |RESOLVED
 Resolution|--- |WORKSFORME

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

[Libreoffice-bugs] [Bug 153432] Add buttons to toggle layer visibility and locked state

[bugzilla-daemon]

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

Stéphane Guillou (stragu)  changed:

   What|Removed |Added

 Status|UNCONFIRMED |RESOLVED
 Blocks||99648
   See Also||https://bugs.documentfounda
   ||tion.org/show_bug.cgi?id=11
   ||3439
Version|unspecified |Inherited From OOo
 CC||stephane.guillou@libreoffic
   ||e.org
 Resolution|--- |WORKSFORME

--- Comment #4 from Stéphane Guillou (stragu) 
 ---
There is now a toggle for layer visibility in the context menu, starting in LO
7.6 (see bug 113439). I imagine this is the most commonly used setting, and
it's the one Rainer wanted easier access to.

Along with the shortcuts Regina provided, I think this can be closed as "works
for me", but feel free to set back to "new" if you disagree.


Referenced Bugs:

https://bugs.documentfoundation.org/show_bug.cgi?id=99648
[Bug 99648] [META] Improve Layer Handling
-- 
You are receiving this mail because:
You are the assignee for the bug.

[Libreoffice-bugs] [Bug 153936] Start Center application filter has missed Databases

[bugzilla-daemon]

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

Stéphane Guillou (stragu)  changed:

   What|Removed |Added

 Blocks|61914   |
   See Also|https://bugs.documentfounda |
   |tion.org/show_bug.cgi?id=80 |
   |934 |


Referenced Bugs:

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

[Libreoffice-bugs] [Bug 61914] [META] Start Center bugs and enhancements

[bugzilla-daemon]

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

Stéphane Guillou (stragu)  changed:

   What|Removed |Added

 Depends on|153936  |


Referenced Bugs:

https://bugs.documentfoundation.org/show_bug.cgi?id=153936
[Bug 153936] Start Center application filter has missed Databases
-- 
You are receiving this mail because:
You are the assignee for the bug.

[Libreoffice-bugs] [Bug 61914] [META] Start Center bugs and enhancements

[bugzilla-daemon]

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

Stéphane Guillou (stragu)  changed:

   What|Removed |Added

 Depends on||153936


Referenced Bugs:

https://bugs.documentfoundation.org/show_bug.cgi?id=153936
[Bug 153936] Start Center application filter has missed Databases
-- 
You are receiving this mail because:
You are the assignee for the bug.

[Libreoffice-bugs] [Bug 61914] [META] Start Center bugs and enhancements

[bugzilla-daemon]

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

Bug 153936 Summary: Start Center application filter has missed Databases
https://bugs.documentfoundation.org/show_bug.cgi?id=153936

   What|Removed |Added

 Status|UNCONFIRMED |RESOLVED
 Resolution|--- |DUPLICATE

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

[Libreoffice-bugs] [Bug 151803] StartCenter: Filter for shown applications - missing Databases and Formula documents

[bugzilla-daemon]

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

Stéphane Guillou (stragu)  changed:

   What|Removed |Added

 CC||jcs...@libreoffice.org

--- Comment #3 from Stéphane Guillou (stragu) 
 ---
*** Bug 153936 has been marked as a duplicate of this bug. ***

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

[Libreoffice-bugs] [Bug 153936] Start Center application filter has missed Databases

[bugzilla-daemon]

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

Stéphane Guillou (stragu)  changed:

   What|Removed |Added

 Blocks||61914
   See Also||https://bugs.documentfounda
   ||tion.org/show_bug.cgi?id=80
   ||934
 Status|UNCONFIRMED |RESOLVED
   Priority|medium  |low
 Whiteboard| QA:needsComment|
 Resolution|--- |DUPLICATE
   Severity|enhancement |trivial
 CC||heiko.tietze@documentfounda
   ||tion.org,
   ||stephane.guillou@libreoffic
   ||e.org

--- Comment #1 from Stéphane Guillou (stragu) 
 ---
Thank you JC. Already reported in bug 151803.

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


Referenced Bugs:

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

[Libreoffice-bugs] [Bug 144237] Enforce a sane minimum width on Linux

[bugzilla-daemon]

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

Stéphane Guillou (stragu)  changed:

   What|Removed |Added

 CC||stephane.guillou@libreoffic
   ||e.org
 Resolution|--- |DUPLICATE
 Status|NEW |RESOLVED

--- Comment #6 from Stéphane Guillou (stragu) 
 ---
I think we can mark this as a duplicate of bug 97894: having a minimum window
size on Linux should fix the issue described here.
Please set back to "new" if you disagree.

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

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

[Libreoffice-bugs] [Bug 97894] LibreOffice windows should have a minimum size

[bugzilla-daemon]

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

Stéphane Guillou (stragu)  changed:

   What|Removed |Added

 CC||adalbert.hans...@gmx.de

--- Comment #18 from Stéphane Guillou (stragu) 
 ---
*** Bug 144237 has been marked as a duplicate of this bug. ***

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

[Libreoffice-bugs] [Bug 153911] Warning when opening files with other files already open

[bugzilla-daemon]

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

m.a.riosv  changed:

   What|Removed |Added

 Status|UNCONFIRMED |NEEDINFO
 Ever confirmed|0   |1

--- Comment #9 from m.a.riosv  ---
Does it happen opening files in other folders?

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

Re: Extended color

[Regina Henschel]

Hi Tomaž,

Tomaž Vajngerl schrieb am 14.04.2023 um 05:25:

Hi Regina,

Sorry, I have vacation so I'm travelling again, but found some time to 
reply.


Thank you for looking at it.



On Tue, Apr 11, 2023 at 6:59 AM Regina Henschel > wrote:


Hi Tomaž,

I have currently only 'RGBHex' and 'Theme' in my ODF proposal draft.
And
I have put the color-transformations separate from the definition of
the
base color (see attachment). That was my guess from the additions to
the
RelaxNG.
Does integrating the color-transformation into my

would better fit to your intentions? I could change that.


Currently we have something like this example:
draw:fill-color="#bbc5fe" ...>

     
     
     
    
    
  
    
  

I thought to just change it to:
draw:fill-color="#bbc5fe" ...>

     
     
     
    
    
  
    
  

Do we actually need  element - couldn't we have it 
in the attributes of the parent element which would be  
fill-complexcolor, stroke-complex-color?


Yes, you are right. We can drop such element. My current version has now
a "common-enhanced-color-attributes", which is used in 
,  and 
.


I could write/read style:color-type="RGBHex" and 
style:color-value="#rrggbb" in the  element if we 
agree on that structure.



I think the transformations are fine where they are.


As the  element is gone now, they need to be child 
elements of the several  elements. I agree the 
current location is OK.


 Not sure the change

would make any difference. How the change

The ColorType 'CRGB' did not get support in the ODF TC right away,
because it is also only a variant of RGB. The same would then apply to
ColorType 'HSL'. They could be converted in the xmloff export filter.


Yes, that makes sense. HSL makes sense in some cases (tcould be easier 
to think in HSL when you later change one of H, S or L values with a 
transform) , but not sure we would use that all that often. >

Regarding ColorType 'System' and its 'SystemColorType', I don't see yet
how this can be implemented well to ODF. It would mean to have a
reference to a color table defined at the user or the user's system.
And
it is different from CSS4  [2], so specifying by
reference
to CSS4 will not work.


I think we don't need this for ODF - in OOXML we convert the colors 
using a fixed mapping function/table anyway. We don't ask the system 
(OS) for the colors.


That makes it easier.



What is ColorType 'Palette' and 'Placeholder'? Is it something, that
needs to be written to ODF markup?


Regarding "Palette" it is the prstClr element in OOXML. Maybe I should 
rename it to "Preset" too. We don't need that in ODF I think.


"Placeholder" is needed in themes, but not theme colors. Placeholder is 
replaced by a theme (scheme) color, whatever one is defined by that 
theme link (IIRC). It's used mainly in the format scheme of a theme - so 
for themes for shapes. Would be good to define it now, even when we 
won't be really using it yet.


It looks as if I need to dig into the OOXML standard to understand how 
it works. But as these drafts are for ODF 1.5 it is not urgent. With the 
structure of a pair 'style:color-type and style:color-value' any further 
color-type can be easily added.




   We could
 > make create a UNO interface for that first and a wrapper, then
use it at
 > all places where XThemeColor is used now, and also add it to the
gradient.

Having a UNO interface and integration to the gradient would allow to
develop ODF import/export parallel to other filter. Is that correct?


ODF and UNO model don't have to depend on each other because you can 
access the internal model in ODF filter too.


It would become relevant, if gradients get theme colors. The access to 
gradients goes via css::awt::Gradient2, css::awt::ColorStopSequence and 
css::awt:ColorStop.




Do you see a change to get such into LO7.6 (or maybe named LO8)? Or
should we not even try to get integration of multi-color gradient and
theme colors to LO7.6?


I think we can add all the changes that are needed for theme colors and 
multi-color gradients into LO 7.6. Maybe some things won't be completed 
yet...


The current state of my start with import and export of multi-color
gradient to ODF [3] does not consider "enhanced-color".


That's fine.


It certainly reduces stress if the integration of theme colors with 
multi-color gradients is done after the feature freeze of LO 7.6. 
However, one must always keep in mind how an integration could look like 
so that the course is set right from the start.


I wish you a relaxing vacation.  And thank you for your comments that 
you have made despite the vacation.


Kind regards,
Regina

[Libreoffice-bugs] [Bug 151040] Logo in Start Center only shows some pixels

[bugzilla-daemon]

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

Stéphane Guillou (stragu)  changed:

   What|Removed |Added

   See Also||https://bugs.documentfounda
   ||tion.org/show_bug.cgi?id=14
   ||3673
 CC||stephane.guillou@libreoffic
   ||e.org

--- Comment #15 from Stéphane Guillou (stragu) 
 ---
Can't reproduce on Ubuntu 20.04 with GNOME 3.36.8, Adwaita, and lo 7.5.2.2.
The steps are very similar to bug 143673, which was fixed in 7.5.0.

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

[Libreoffice-bugs] [Bug 148647] LO pastes previously copied content instead of what was last copied from other app (Windows 10; see comment 11)

[bugzilla-daemon]

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

Stéphane Guillou (stragu)  changed:

   What|Removed |Added

 CC||sbnsj...@gmail.com

--- Comment #15 from Stéphane Guillou (stragu) 
 ---
*** Bug 154520 has been marked as a duplicate of this bug. ***

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

[Libreoffice-bugs] [Bug 154520] Paste function fails to work after 20 or so pastings from other programs

[bugzilla-daemon]

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

Stéphane Guillou (stragu)  changed:

   What|Removed |Added

 Resolution|--- |DUPLICATE
 CC||stephane.guillou@libreoffic
   ||e.org
 Status|UNCONFIRMED |RESOLVED

--- Comment #2 from Stéphane Guillou (stragu) 
 ---
Thank you, K. I assume you are on Windows. If that's the case, I am pretty
confident this is a duplicate of bug 148647.
Please see the comments there, especially comment 10. It might be related to
opening another app while working on the document.
Feel free to set back to unconfirmed if you think it's not the same issue.

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

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

[Libreoffice-bugs] [Bug 154790] Copy and paste alter all Heading paragraph styles throughout the remainder of the document

[bugzilla-daemon]

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

--- Comment #4 from ajlittoz  ---
This bug report is a follow-on of
https://ask.libreoffice.org/t/stop-automatically-adding-a-tab-at-the-start-of-every-line-with-a-heading-style/90406/6

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

[Libreoffice-bugs] [Bug 154813] BUG in simple Division !!!

[bugzilla-daemon]

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

--- Comment #11 from ady  ---
See:

https://help.libreoffice.org/latest/en-US/text/scalc/guide/relativ_absolut_ref.html

Although I think this should not be done as a general rule, I am posting the
following link in order to hint others that they should not report "bugs"
before some minimal web search.

https://support.microsoft.com/en-us/office/switch-between-relative-absolute-and-mixed-references-dfec08cd-ae65-4f56-839e-5f0d8d0baca9

Please next time perform a web search, or go to https://ask.libreoffice.org 

This site is for bug reports. Thank you.

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

[Libreoffice-bugs] [Bug 154534] Can't view the Main menu bar, while choosing the sub design menu.

[bugzilla-daemon]

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

Dieter  changed:

   What|Removed |Added

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

--- Comment #1 from Dieter  ---
Priyanka, do you have the same problem also with actual version LO 7.5?
=> NEEDINFO

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

[Libreoffice-bugs] [Bug 154813] BUG in simple Division !!!

[bugzilla-daemon]

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

Stéphane Guillou (stragu)  changed:

   What|Removed |Added

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

--- Comment #10 from Stéphane Guillou (stragu) 
 ---
(In reply to stefan from comment #7)
> Dear Support Team,
> Thank you for the quick response. I can live with conclusion of using "$"
> but I must admit, that the MS-(exivalanet/evil/as-you-like-to-call-it) is
> somewhat more intuitive. > I will still keep with LibreOffice (thank you so
> mutch), but some people might be confused like me in the first try.

You will find that MS Excel behaves the same: dragging that cell down will
update relative references, resulting in the same values.

Closing as "not a bug".

Thank you both!

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

[Libreoffice-bugs] [Bug 154816] New: Can't refresh control after selecting it with mouse click

[bugzilla-daemon]

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

Bug ID: 154816
   Summary: Can't refresh control after selecting it with mouse
click
   Product: LibreOffice
   Version: 7.5.2.2 release
  Hardware: x86-64 (AMD64)
OS: Linux (All)
Status: UNCONFIRMED
  Severity: normal
  Priority: medium
 Component: Base
  Assignee: libreoffice-bugs@lists.freedesktop.org
  Reporter: lowell_frie...@live.com

Description:
I have a form with multiple subforms, some of which are linked to tables that
are used to populate dropdown boxes in other subforms.  After adding another
record into a tables, I need to hit "Refresh Control" in order for the new
record to appear in the drop down box and to be able to select it.  So far, so
good.  However, even when I have selected a column or cell in a subform that I
want to refresh the control for, the refresh control button is grayed out.  I
often have to click around several times in several different subforms on my
form before I can refresh the control I want to refresh.  I'm not certain this
is as much a problem with the refresh control button as it is a general problem
having to do with mouse clicks not appropriately selecting what the click is
intended to select.  My mouse clicks *appear* to select what I want them to,
but then I can't do what I want to do in that cell on the form.  Sometimes I
will have selected a cell to type something into but the text I type gets
entered into a cell on the subform I was previously working in.

Steps to Reproduce:
1.Enter data into a cell in a subform.
2.Select a cell in another subform.
3.Attempt to refresh control.

Actual Results:
The refresh control button remains greyed out.

Expected Results:
The refresh control button should be available to hit refresh.


Reproducible: Always


User Profile Reset: Yes

Additional Info:
Version: 7.5.2.2 (X86_64) / LibreOffice Community
Build ID: 50(Build:2)
CPU threads: 12; OS: Linux 5.19; UI render: default; VCL: gtk3
Locale: en-CA (en_CA.UTF-8); UI: en-US
Ubuntu package version: 4:7.5.2~rc2-0ubuntu0.22.04.1~lo1
Calc: threaded

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

[Libreoffice-bugs] [Bug 154781] Keyboard input un-does paste (if cell was previously empty)

[bugzilla-daemon]

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

--- Comment #9 from Jim Avera  ---
@ady I think we are talking past each other.

What you said about edit mode is clear.   The problem I see is that the initial
paste does not enter edit mode, but typing does.  They should (IMO) be handled
the same.

For example, if user clicks once and types "A", the "A" replaces existing
content; fine.  If the user then types "B", it is appended and does not erase
the "A", and so-forth.

In the same way, if the user clicks once and pastes "A", it replaces existing
content; fine.  But the next user input erases the "A" when it should append.

What I am saying is that pasting should have *exactly* the same effects as
typing the same content on the keyboard.   Everywhere.

-Jim

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

[Libreoffice-bugs] [Bug 154813] BUG in simple Division !!!

[bugzilla-daemon]

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

--- Comment #9 from ste...@klerx4u.de ---
Created attachment 186677
  --> https://bugs.documentfoundation.org/attachment.cgi?id=186677=edit
confusing Row "drag" calc

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

[Libreoffice-bugs] [Bug 154813] BUG in simple Division !!!

[bugzilla-daemon]

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

--- Comment #8 from ste...@klerx4u.de ---
Yust to make my confusion clear- pls see attaches screenshot

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

[Libreoffice-bugs] [Bug 154815] New: UI: Cell cursor width has increased

[bugzilla-daemon]

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

Bug ID: 154815
   Summary: UI: Cell cursor width has increased
   Product: LibreOffice
   Version: 7.4.0.0 alpha0+
  Hardware: All
OS: All
Status: UNCONFIRMED
  Severity: enhancement
  Priority: medium
 Component: Calc
  Assignee: libreoffice-bugs@lists.freedesktop.org
  Reporter: flklb-b...@t-online.de

Since 7.4.0.0 I noticed an increased frame thickness of the selected cell
cursor (2px -> 3px), which looks a bit odd to me; it also makes some cells
harder to read.

Can the thickness be configured somewhere? I cannot seem to find a setting for
this.

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

[Libreoffice-bugs] [Bug 154813] BUG in simple Division !!!

[bugzilla-daemon]

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

--- Comment #7 from ste...@klerx4u.de ---
Dear Support Team,
Thank you for the quick response. I can live with conclusion of using "$" but I
must admit, that the MS-(exivalanet/evil/as-you-like-to-call-it) is somewhat
more intuitive. > I will still keep with LibreOffice (thank you so mutch), but
some people might be confused like me in the first try.

PLS keep up the good work.

Kind Regards

S.Klerx

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

[Libreoffice-bugs] [Bug 154814] New: Animated items display in wrong order when returning to previous slide

[bugzilla-daemon]

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

Bug ID: 154814
   Summary: Animated items display in wrong order when returning
to previous slide
   Product: LibreOffice
   Version: 7.4.6.2 release
  Hardware: All
OS: All
Status: UNCONFIRMED
  Severity: normal
  Priority: medium
 Component: Impress
  Assignee: libreoffice-bugs@lists.freedesktop.org
  Reporter: rtrink...@icloud.com

Created attachment 186676
  --> https://bugs.documentfoundation.org/attachment.cgi?id=186676=edit
Test file demonstrating animation problems when returning from previous slide

When in presentation mode, animated items such as bulleted text do not display
in the correct order when the user returns to a previous slide.

Expected behavior: when returning to a previous slide by pressing backspace or
left arrow, the previous slide should appear in its "final" state, with all
animations having completed.  In my case, that means that all bulleted items
should appear. In the attached sample file, the only animations are bulleted
text items that should enter individually one at a time, one per click. 

Current behavior: when returning to a previous slide by pressing backspace or
left arrow, some animated items appear but some do not. When I proceed to press
backspace again, animated items do not disappear in order and some items.

Please see the attached file as an example.

I know that this sounds like a duplication of another bug (#137454), but that
other bug is listed as solved yet the problem persists in 7.4.6.2.

To reproduce:

1. Open attached test file. 
2. Navigate to third (last) slide.
3. Enter presentation mode with this slide (shift-F5)
4. Press backspace. The previous slide appears, but the top bullet does not
display.
5. Press backspace again. Two bullets disappear. Only the bottom bullet should
disappear.
5. Press backspace again. All bullets disappear. At this point, only two
bullets were visible, so the third (bottom visible) should disappear, leaving
the second visible.  The first bullet is never visible, but of course it should
be.

This behavior happens on most of my Impress files. As a teacher who often needs
to return to previous slides, I experience this bug daily.

(Thanks to devs for their hard work!)

My system: LO 7.6.4.2, Ubuntu Linux 22.10

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

[Libreoffice-bugs] [Bug 154813] BUG in simple Division !!!

[bugzilla-daemon]

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

--- Comment #6 from ste...@klerx4u.de ---
OK got some "hint"-
in Row H -> the usage of "$" solves the issue in some way: =$H$1/[scaling].
But the behavior is strange, as the tool does not recognize the reference point
and that every 2nd line is "0" is also irretating.

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

[Libreoffice-bugs] [Bug 154813] BUG in simple Division !!!

[bugzilla-daemon]

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

--- Comment #5 from Rafael Lima  ---
The problem here is simple. You're always dividing H1 by the values in column
C, but the value of H1 is fixed.

When you drag down the formula, H1 gets updated downwards (H2, H3, H4...) as
well as column C (C3, C4, C5...). But in the case of column H, since you want
to keep it fixed in H1, you need to lock it.

For that, replace H1 in the formula by $H$1, which locks the column/row.

Closing this as NAB.

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

[Libreoffice-bugs] [Bug 154813] BUG in simple Division !!!

[bugzilla-daemon]

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

--- Comment #4 from ste...@klerx4u.de ---
Created attachment 186675
  --> https://bugs.documentfoundation.org/attachment.cgi?id=186675=edit
screenshow - weired results

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

[Libreoffice-bugs] [Bug 154813] BUG in simple Division !!!

[bugzilla-daemon]

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

--- Comment #3 from ste...@klerx4u.de ---
As I could not reply to the request I try to fill this form (unconveinient).

Reply was: 
Sure---

try this file an drag down colum H  (h3 down to h17) - you should immedialtly
see the problem.

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

[Libreoffice-bugs] [Bug 154386] [META] XML Form

[bugzilla-daemon]

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

Bug 154734 Summary: XML Form Document: All binded fields will be shown as 
fields with wrong content - except fields, which have wrong content.
https://bugs.documentfoundation.org/show_bug.cgi?id=154734

   What|Removed |Added

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

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

[Libreoffice-bugs] [Bug 154813] BUG in simple Division !!!

[bugzilla-daemon]

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

--- Comment #2 from ste...@klerx4u.de ---
Created attachment 186674
  --> https://bugs.documentfoundation.org/attachment.cgi?id=186674=edit
simple statistic chart

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

[Libreoffice-bugs] [Bug 154813] BUG in simple Division !!!

[bugzilla-daemon]

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

Rafael Lima  changed:

   What|Removed |Added

 CC||rafael.palma.l...@gmail.com

--- Comment #1 from Rafael Lima  ---
Can you share a file with a more concrete example of what the problem is?

With your description I cannot reproduce the problem.

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

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

[Julien Nabet (via logerrit)]

 forms/source/xforms/datatypes.cxx |2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

New commits:
commit 4829a85d0753c93419bd46b1d50bcfa6f0f3f1da
Author: Julien Nabet 
AuthorDate: Fri Apr 14 21:05:06 2023 +0200
Commit: Julien Nabet 
CommitDate: Fri Apr 14 22:58:09 2023 +0200

tdf#154734: XML Form doc: all binded fields will be shown as fields...

with wrong content - except fields, which have wrong content

Regression of 14cfff500e93f0d6cbf8412065feea85c01ea81d (at 2021-08-05)
Pass context and resource string down to boost::locale separately
because this is often on a hot path, and we can avoid the splitting and
joining of strings like this.

Before the commit, it was:
return ( _validate( sValue ) == nullptr );

_validate methods return "TranslateId" variable which contain the reason 
why validity is wrong
so if this variable contains no reason it means everything is OK.

so just replace:
return bool(_validate( sValue ));
by:
return bool(!_validate( sValue ));

Change-Id: I76373d0825f86f9072217c96757252b6a891ecc4
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/150433
Reviewed-by: Julien Nabet 
Tested-by: Jenkins

diff --git a/forms/source/xforms/datatypes.cxx 
b/forms/source/xforms/datatypes.cxx
index 92e0c3ec781b..c372298f0e5f 100644
--- a/forms/source/xforms/datatypes.cxx
+++ b/forms/source/xforms/datatypes.cxx
@@ -156,7 +156,7 @@ namespace xforms
 
 sal_Bool OXSDDataType::validate( const OUString& sValue )
 {
-return bool(_validate( sValue ));
+return bool(!_validate( sValue ));
 }
 
 

[Libreoffice-bugs] [Bug 154813] New: BUG in simple Division !!!

[bugzilla-daemon]

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

Bug ID: 154813
   Summary: BUG in simple Division !!!
   Product: LibreOffice
   Version: 7.5.2.2 release
  Hardware: x86-64 (AMD64)
OS: Windows (All)
Status: UNCONFIRMED
  Severity: normal
  Priority: medium
 Component: Calc
  Assignee: libreoffice-bugs@lists.freedesktop.org
  Reporter: ste...@klerx4u.de

Description:
Dear Libre Office Team,

I found a strange behavior in when calculating a simple statistic, with a
division. When filling a Calc Chart with values and try to use a division to
get results like / power per time -> and be dragging down on a valid formula,
every second value is calculates wrong.  -> dooing this cell-by-cell works, but
is not very user frendly for a bigger number of values.

Kind Regards,

S.Klerx

Actual Results:
With manual cell-by-cell it works, but it is not userfrendly !

Expected Results:
Dragging down on a valid formula shows the correct values.


Reproducible: Always


User Profile Reset: No

Additional Info:
[Information automatically included from LibreOffice]
Locale: de
Module: SpreadsheetDocument
[Information guessed from browser]
OS: Windows (All)
OS is 64bit: yes

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

[Libreoffice-ux-advise] [Bug 154766] management of ellipsis variants

[bugzilla-daemon]

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

--- Comment #8 from toddwar...@duck.com ---
(Note, I didn't file a bug. I filed an RFE.) Anyway . . .

I am just adding this bit to clear things up though I see this as being
dismissed, but someone may find it educational someday.

1. I keep typoing. Grr. AP-style (Associated Press) is what I meant. That's the
style guide that drove the 3-dots, no-spacing-between formatting, even though
the other is more common. Coincidentally, APA-style (largely only used by the
shrink community) also adopted that style. Regardless . . .

2. I see how you're fundamentally not understanding this now. You see an
ellipsis as three dots in a row. Which it isn't. For example, at the end of a
sentence your eyes may see 4 dots, but that's not what is happening. It's an
ellipsis and a period.

An ellipsis is treated as a word. An unbreakable, single-character word.
Grammar and spell checkers and word counters see it as a word. A word that has
a meaning: an ellipsis.

As I said, I was just hoping there was a better workaround than changing up the
auto-correct to dish out a .[NBSP].[NBSP]. but perhaps I was hoping for too
much. Maybe the Unicode community will solve this for us.

Have a great weekend, folks. -t

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

[Libreoffice-bugs] [Bug 154766] management of ellipsis variants

[bugzilla-daemon]

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

--- Comment #8 from toddwar...@duck.com ---
(Note, I didn't file a bug. I filed an RFE.) Anyway . . .

I am just adding this bit to clear things up though I see this as being
dismissed, but someone may find it educational someday.

1. I keep typoing. Grr. AP-style (Associated Press) is what I meant. That's the
style guide that drove the 3-dots, no-spacing-between formatting, even though
the other is more common. Coincidentally, APA-style (largely only used by the
shrink community) also adopted that style. Regardless . . .

2. I see how you're fundamentally not understanding this now. You see an
ellipsis as three dots in a row. Which it isn't. For example, at the end of a
sentence your eyes may see 4 dots, but that's not what is happening. It's an
ellipsis and a period.

An ellipsis is treated as a word. An unbreakable, single-character word.
Grammar and spell checkers and word counters see it as a word. A word that has
a meaning: an ellipsis.

As I said, I was just hoping there was a better workaround than changing up the
auto-correct to dish out a .[NBSP].[NBSP]. but perhaps I was hoping for too
much. Maybe the Unicode community will solve this for us.

Have a great weekend, folks. -t

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

[Libreoffice-bugs] [Bug 154756] Vertical text direction results in rotation, not vertical text direction

[bugzilla-daemon]

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

--- Comment #8 from Eyal Rozenberg  ---
(In reply to Regina Henschel from comment #7)
> LibreOffice renders it in one way, when you set the text direction. Thereby
> the text direction is often inherit from the layout environment of an object.

I'm not sure I understand this sentence.

> If you need a different glyph orientation for a portion of text, you can use
> the settings in the 'Position' tab of the character properties.

I need LO to do what I told it to do, which is render my English text in
vertical writing mode.

Now, given the information at the links - if the larger-piece-of-text is in a
CJK language/script but contains a smaller-piece-of-text in Western script, or
even in a Western language - then it would be acceptable for LO to diverge from
literal conformance to the settings made. But even then, the default should
probably be some kind of reasonable heuristic. An override of the heuristic
should not necessitate setting a value for each and every stretch of
Western-script text in a CJK document - that is very cumbersome.

> Implementation of a "stacked" writing-mode for paragraphs and for frames is
> missing. If you want such, please write an enhancement request.

LO claims to offer vertical writing mode, and instead rotates. Fixing this is
fixing a bug, not making an enhancement. It is also may be considered kind of a
bug to conflate rotation of stretches of text with the writing direction, but I
don't have a strong opinion on that.

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

[Libreoffice-bugs] [Bug 154790] Copy and paste alter all Heading paragraph styles throughout the remainder of the document

[bugzilla-daemon]

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

--- Comment #3 from Dale  ---
See attachments for a sample of what happens when the user pastes from Sql
Server Management Studio

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

[Libreoffice-bugs] [Bug 154790] Copy and paste alter all Heading paragraph styles throughout the remainder of the document

[bugzilla-daemon]

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

--- Comment #2 from Dale  ---
Created attachment 186672
  --> https://bugs.documentfoundation.org/attachment.cgi?id=186672=edit
Document prior to the paste

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

[Libreoffice-bugs] [Bug 154812] New: Unable to click on the left side of a formula when it is centered in a cell

[bugzilla-daemon]

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

Bug ID: 154812
   Summary: Unable to click on the left side of a formula when it
is centered in a cell
   Product: LibreOffice
   Version: 7.6.0.0 alpha0+ Master
  Hardware: All
OS: All
Status: UNCONFIRMED
  Severity: normal
  Priority: medium
 Component: Calc
  Assignee: libreoffice-bugs@lists.freedesktop.org
  Reporter: rafael.palma.l...@gmail.com

When you open a formula that is centered in a cell and it extends beyond the
column width, it is not possible to click the formula text to the left of the
cell. It is however possible to click the text to the right of the cell.

Steps to reproduce:
0) Create a blank Calc document
1) Enter a long formula text on a cell, f.i.
=SUMPRODUCT(C10:C16;D10:D16)-SUMPRODUCT(F11:F15;G11:G15)
2) Do not change its alignment for now... simply double-click the cell and
notice that the formula text will align to the left edge of the column where it
is located, and all formula text is clickable (this is OK).
3) Now click outside the cell to stop editing the formula. Use the toolbar to
center the cell contents
4) Double-click the cell. The formula text will be centered and the formula
text that goes beyond the left column edge is not clickable (Not OK). The
formula text to the right is clickable as expected.

>From my testing, it happens in gtk3, kf5 and gen.

System info

Version: 7.5.2.2 (X86_64) / LibreOffice Community
Build ID: 50(Build:2)
CPU threads: 16; OS: Linux 5.19; UI render: default; VCL: kf5 (cairo+xcb)
Locale: pt-BR (pt_BR.UTF-8); UI: en-US
Ubuntu package version: 4:7.5.2~rc2-0ubuntu0.22.10.1~lo1
Calc: threaded

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

[Libreoffice-bugs] [Bug 154790] Copy and paste alter all Heading paragraph styles throughout the remainder of the document

[bugzilla-daemon]

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

--- Comment #1 from Dale  ---
Created attachment 186671
  --> https://bugs.documentfoundation.org/attachment.cgi?id=186671=edit
Document state after the paste from SSMS

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

[Libreoffice-bugs] [Bug 154202] Annoying extension icon (MultiSave) on standard toolbar (Win8.1)

[bugzilla-daemon]

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

--- Comment #8 from teodorko...@yahoo.com ---
Okay, thanks!
You can close the issue.

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

[Libreoffice-bugs] [Bug 143754] No Help page for Tools > Options… > Language settings > English Sentence Checking

[bugzilla-daemon]

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

--- Comment #14 from Olivier Hallot  ---
This English Sentence Checking feature is actually a set of python regex run by
LightProof grammar checker, and are part of the bundled extensions released
with LibreOffice.

https://cgit.freedesktop.org/libreoffice/lightproof

The English set of rules is configurable in the dialog.

However, other languages such as pt-BR has another set of rules and the
settings dialog is different, with some ad-hoc linguistic rules and different
grammar checking. The Sentence checking is in the dictionaries/
submodule.

Since the grammar checking varies per language, I find strange to create a Help
page translatable with Portuguese rules on a English UI.

But the dialog created by the extension could have a Help button to open a wiki
page with the rules explained in the user or document language.

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