[Libreoffice-bugs] [Bug 152131] Dragging document from window header bar to another location copies wrong document version

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

Buovjaga  changed:

   What|Removed |Added

 Ever confirmed|0   |1
 Status|UNCONFIRMED |NEW

--- Comment #5 from Buovjaga  ---
Status should be NEW per confirmation.

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

Re: Subject : Help regarding Bug 90341 - Clean up excessive const_cast'ing

2022-11-23 Thread Tomaž Vajngerl
Hi,

On Wed, Nov 23, 2022 at 8:37 PM Siddharth Khattar 
wrote:

> Hello all,
>
> So I was aiming to do a medium difficulty level easy hack and came
> across this one (Bug 90341) which interested me. I then studied what
> const_cast does and what was the main issue that this bug was
> addressing. As I looked into it more and ran the command " git grep
> --word-regexp --count const_cast | sort --numeric-sort --key=2
> --field-separator=: ", I got various results and decided to look into
> core/xmloff/source/style/impastpl.cxx (lines 144 & 146).
> I also decided to go through the previous commits made in the bug
> thread for ideas and help, such as these:
>
> https://git.libreoffice.org/core/+/7b152167a4e4c3eaac95aee8f282873681c90092%5E%21
> and
> https://cgit.freedesktop.org/libreoffice/core/commit/?id=4ae319ae462f3f094452046e392c8c15446736ae
> .
> I then decided to experiment with the file (impastpl.cxx) and then
> removed const & const_cast from the above-mentioned lines. Then, when
> I tried to build from source I got these errors (please see attached
> text file).
>
> I wasn't sure what to make of these errors as nothing helpful came
> when I googled them & I also am not heavily experienced in c++ coding.
> Then I started reading some documentation of the xmloff file to come
> to understand that these files were related to outputting "basic ODF
> import/export filter implementation for most applications".
>
> One of the people at LibreOffice (buovjaga) also helped me with this
> and pointed out that the any2string function in that file appeared in:
>
> https://git.libreoffice.org/core/commit/c1015fdd51909495cefdc0258c3899cd73d4d2df
> .
> I pondered about contacting the original contributor who pushed this
> commit for help but as the commit was 9+ years old I dropped that idea
> pretty quickly
> I'd really appreciate it if the dev team could help me in any way with
> this easy hack and tell me in which direction I should go!
>

It's quite simple - if a variable is const it means it should not be
changed. any.getValue() is returning such a variable (const void*), but the
variable is then put into data2string function, which accepts a non-const
variable that can be changed (void*).
So if you don't o a const_cast, the compiler will complain that you can't
put a variable that is said to be unchangeable into a function where it
requires the variable to be changeable, so it complains that it can't do
that.

This is the reason there was/is a const_cast at that place, which says that
"the compiler is dumb and doesn't know what's talking about so covert that
unchangable variable to be changeable so the compiler is silent and stops
bugging the developers".

So how to solve this - at least in this case: looking at the data2string
function the "void* data" input variable is later on cast to a const
something variable anyway, so maybe try to change the input variable type
from "void* data" to "const void* data" and fix any issues you have later
on in the body with this data variable.

Also note that in another const_cast case the situation might be different
and you must check how to solve the issue on a case by case basis (some
possible solutions are in the bug report)


> Thanking you for your time,
> Siddharth Khattar
>

Tomaž


[Libreoffice-bugs] [Bug 152198] 2 Tiles in the Win64 Start Menu have the wrong background color when set to small only.

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

--- Comment #2 from Robert Sprigg  ---
Created attachment 183749
  --> https://bugs.documentfoundation.org/attachment.cgi?id=183749=edit
Screenshot of Bug

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

[Libreoffice-commits] core.git: Branch 'libreoffice-7-4' - vcl/unx

2022-11-23 Thread Caolán McNamara (via logerrit)
 vcl/unx/gtk3/gtkframe.cxx |7 ++-
 1 file changed, 6 insertions(+), 1 deletion(-)

New commits:
commit b534ee2e972711af2dbaadf2190813054adda902
Author: Caolán McNamara 
AuthorDate: Tue Nov 22 11:33:23 2022 +
Commit: Samuel Mehrbrodt 
CommitDate: Thu Nov 24 08:28:04 2022 +0100

Resolves: tdf#152155 use gtk's knowledge of relative widget positions

rather than effectively emulate it poorly

Change-Id: If1c215892645d83937d97158a2d3f8ddac10364e
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/143104
Tested-by: Jenkins
Reviewed-by: Caolán McNamara 
(cherry picked from commit 15cdee0d846854b50dd04626b73499bef9305e00)
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/143197
Reviewed-by: Samuel Mehrbrodt 

diff --git a/vcl/unx/gtk3/gtkframe.cxx b/vcl/unx/gtk3/gtkframe.cxx
index b17614658122..3d8cce5e02b7 100644
--- a/vcl/unx/gtk3/gtkframe.cxx
+++ b/vcl/unx/gtk3/gtkframe.cxx
@@ -3688,7 +3688,12 @@ void GtkSalFrame::signalRealize(GtkWidget*, gpointer 
frame)
 
 tools::Rectangle aFloatRect = 
FloatingWindow::ImplConvertToAbsPos(pVclParent, pThis->m_aFloatRect);
 if 
(gdk_window_get_window_type(widget_get_surface(pThis->m_pParent->m_pWindow)) != 
GDK_WINDOW_TOPLEVEL)
-aFloatRect.Move(-pThis->m_pParent->maGeometry.nX, 
-pThis->m_pParent->maGeometry.nY);
+{
+// See tdf#152155 for an example
+gtk_coord nX(0), nY(0.0);
+gtk_widget_translate_coordinates(pThis->m_pParent->m_pWindow, 
widget_get_toplevel(pThis->m_pParent->m_pWindow), 0, 0, , );
+aFloatRect.Move(nX, nY);
+}
 
 GdkRectangle rect {static_cast(aFloatRect.Left()), 
static_cast(aFloatRect.Top()),
static_cast(aFloatRect.GetWidth()), 
static_cast(aFloatRect.GetHeight())};


[Libreoffice-bugs] [Bug 152198] 2 Tiles in the Win64 Start Menu have the wrong background color when set to small only.

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

Robert Sprigg  changed:

   What|Removed |Added

 Attachment #183748|image/jpeg  |image/png
  mime type||

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

[Libreoffice-bugs] [Bug 152198] 2 Tiles in the Win64 Start Menu have the wrong background color when set to small only.

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

Robert Sprigg  changed:

   What|Removed |Added

 CC||robertspr...@hotmail.com

--- Comment #1 from Robert Sprigg  ---
Created attachment 183748
  --> https://bugs.documentfoundation.org/attachment.cgi?id=183748=edit
Screenshot showing bug.

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

[Libreoffice-bugs] [Bug 152198] New: 2 Tiles in the Win64 Start Menu have the wrong background color when set to small only.

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

Bug ID: 152198
   Summary: 2 Tiles in the Win64 Start Menu have the wrong
background color when set to small only.
   Product: LibreOffice
   Version: 7.4.2.3 release
  Hardware: x86-64 (AMD64)
OS: Windows (All)
Status: UNCONFIRMED
  Severity: trivial
  Priority: medium
 Component: Draw
  Assignee: libreoffice-bugs@lists.freedesktop.org
  Reporter: robertspr...@hotmail.com

Description:
Hi, I have noticed an error in the latest version 7.4.2.3 and earlier. Two of
the tiles in the Win64 Start Menu have the wrong background color (dark) when
they are set to small only on a light background. The background color is
correct when the tile size is selected to medium which is the default. It's
Office Calc and Office Draw which are wrong. I can send a screen shot if you
like.

Steps to Reproduce:
1. Right Click on Office Calc Icon in Windows 10 Start Menu and select Pin To
Start. 
2. Right Click on Office Calc Tile in the Start Menu created by the last step
and select Resize then select Small.  
3.

Actual Results:
If the default Windows Color Scheme is set to "Light" rather than "Dark" then
the tiles background color should be light however in Office Calc and Office
Draw the background color of the tiles are "Dark". The color of the Tile
backgrounds in Office Word and Office Base are both correct. 

Expected Results:
See above


Reproducible: Always


User Profile Reset: No

Additional Info:
See above

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

[Libreoffice-commits] core.git: Branch 'distro/collabora/co-22.05' - offapi/com sw/inc sw/qa sw/source writerfilter/source

2022-11-23 Thread Miklos Vajna (via logerrit)
 offapi/com/sun/star/text/ContentControl.idl  |6 +++
 sw/inc/formatcontentcontrol.hxx  |7 
 sw/inc/unoprnms.hxx  |1 
 sw/qa/extras/ooxmlexport/data/sdt-duplicated-id.docx |binary
 sw/qa/extras/ooxmlexport/ooxmlexport18.cxx   |   15 +
 sw/source/core/txtnode/attrcontentcontrol.cxx|2 +
 sw/source/core/unocore/unocontentcontrol.cxx |   29 +++
 sw/source/core/unocore/unomap1.cxx   |1 
 sw/source/filter/ww8/docxattributeoutput.cxx |6 +++
 writerfilter/source/dmapper/DomainMapper.cxx |6 +++
 writerfilter/source/dmapper/DomainMapper_Impl.cxx|5 +++
 writerfilter/source/dmapper/SdtHelper.cxx|5 +++
 writerfilter/source/dmapper/SdtHelper.hxx|6 +++
 13 files changed, 89 insertions(+)

New commits:
commit 7baaec9e1683f8683498da7e9153e737fe111671
Author: Miklos Vajna 
AuthorDate: Tue Nov 22 14:30:08 2022 +0100
Commit: Miklos Vajna 
CommitDate: Thu Nov 24 08:10:08 2022 +0100

DOCX filter: fix  creating both grab-bag and content control for 


Exporting the DOCX bugdoc back to DOCX resulted in a document that can't
be opened in Word.

Examining the output, the problem is that the document had 2 inline
 elements with , and we mapped such  elements to
both grab-bags and content controls, leading to duplicate 
elements on export. This is schema-valid, but it goes against the
intention of the spec and Word can't open it.

The initial fix was just a writerfilter/ tweak to avoid grab-bagging
 for inline , but CppunitTest_sw_ooxmlexport4's
testSimpleSdts points out that in other cases we already require
preserving . Fix the problem by storing  in the content
control, which is essentially a subset of
.

Thanks to Justin Luth! - he prototyped the DOCX filter for .

(cherry picked from commit 100c914d44ae8f362924fe567d7d41d0033ae8ad)

Conflicts:
sw/qa/extras/ooxmlexport/ooxmlexport18.cxx

Change-Id: I9f002b770049ce8be30253d0b39410d9a58981dd
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/143139
Tested-by: Jenkins CollaboraOffice 
Reviewed-by: Miklos Vajna 

diff --git a/offapi/com/sun/star/text/ContentControl.idl 
b/offapi/com/sun/star/text/ContentControl.idl
index 7bdb39fa5101..6abcc79fd204 100644
--- a/offapi/com/sun/star/text/ContentControl.idl
+++ b/offapi/com/sun/star/text/ContentControl.idl
@@ -121,6 +121,12 @@ service ContentControl
 @since LibreOffice 7.5
 */
 [optional, property, readonly] string DateString;
+
+/** A unique numeric id, used by macros to identify a specific control.
+
+@since LibreOffice 7.5
+*/
+[optional, property] long Id;
 };
 
 
diff --git a/sw/inc/formatcontentcontrol.hxx b/sw/inc/formatcontentcontrol.hxx
index a44c8b9b5a44..9ae6205e87b3 100644
--- a/sw/inc/formatcontentcontrol.hxx
+++ b/sw/inc/formatcontentcontrol.hxx
@@ -175,6 +175,9 @@ class SW_DLLPUBLIC SwContentControl : public 
sw::BroadcastingModify
 /// The tag: just remembered.
 OUString m_aTag;
 
+/// The id: just remembered.
+sal_Int32 m_nId = 0;
+
 /// Stores a list item index, in case the doc model is not yet updated.
 std::optional m_oSelectedListItem;
 
@@ -344,6 +347,10 @@ public:
 
 const OUString& GetTag() const { return m_aTag; }
 
+void SetId(sal_Int32 nId) { m_nId = nId; }
+
+sal_Int32 GetId() const { return m_nId; }
+
 void SetReadWrite(bool bReadWrite) { m_bReadWrite = bReadWrite; }
 
 bool GetReadWrite() const { return m_bReadWrite; }
diff --git a/sw/inc/unoprnms.hxx b/sw/inc/unoprnms.hxx
index 37069b07925f..2dffbeb739af 100644
--- a/sw/inc/unoprnms.hxx
+++ b/sw/inc/unoprnms.hxx
@@ -890,6 +890,7 @@
 #define UNO_NAME_COLOR "Color"
 #define UNO_NAME_ALIAS "Alias"
 #define UNO_NAME_TAG "Tag"
+#define UNO_NAME_ID "Id"
 #define UNO_NAME_DATE_STRING "DateString"
 #endif
 
diff --git a/sw/qa/extras/ooxmlexport/data/sdt-duplicated-id.docx 
b/sw/qa/extras/ooxmlexport/data/sdt-duplicated-id.docx
new file mode 100644
index ..d21894df3007
Binary files /dev/null and 
b/sw/qa/extras/ooxmlexport/data/sdt-duplicated-id.docx differ
diff --git a/sw/qa/extras/ooxmlexport/ooxmlexport18.cxx 
b/sw/qa/extras/ooxmlexport/ooxmlexport18.cxx
index 8d647e9cf234..bc48cc158975 100644
--- a/sw/qa/extras/ooxmlexport/ooxmlexport18.cxx
+++ b/sw/qa/extras/ooxmlexport/ooxmlexport18.cxx
@@ -62,6 +62,21 @@ CPPUNIT_TEST_FIXTURE(Test, testInlineSdtHeader)
 loadAndSave("inline-sdt-header.docx");
 }
 
+CPPUNIT_TEST_FIXTURE(Test, testSdtDuplicatedId)
+{
+// Given a document with 2 inline , with each a :
+// When exporting that back to DOCX:
+loadAndSave("sdt-duplicated-id.docx");
+
+// Then make sure we write 2  and no duplicates:
+xmlDocUniquePtr pXmlDoc = 

[Libreoffice-commits] core.git: 2 commits - cppcanvas/qa embeddedobj/qa filter/IwyuFilter_filter.yaml filter/qa include/vcl oox/qa oox/source sd/qa sfx2/qa svx/qa sw/inc sw/qa sw/source vcl/IwyuFilter

2022-11-23 Thread Miklos Vajna (via logerrit)
 cppcanvas/qa/extras/emfplus/emfplus.cxx   |5 
 embeddedobj/qa/cppunit/general.cxx|1 
 filter/IwyuFilter_filter.yaml |3 
 filter/qa/pdf.cxx |1 
 filter/qa/unit/svg.cxx|3 
 filter/qa/unit/textfilterdetect.cxx   |1 
 include/vcl/weld.hxx  |2 
 oox/qa/unit/drawingml.cxx |4 
 oox/qa/unit/export.cxx|6 -
 oox/qa/unit/mathml.cxx|1 
 oox/qa/unit/shape.cxx |5 
 oox/qa/unit/vml.cxx   |3 
 oox/source/shape/WpsContext.cxx   |2 
 sd/qa/filter/eppt/eppt.cxx|5 
 sfx2/qa/cppunit/doc.cxx   |1 
 sfx2/qa/cppunit/view.cxx  |1 
 svx/qa/unit/core.cxx  |1 
 svx/qa/unit/sdr.cxx   |1 
 svx/qa/unit/styles.cxx|1 
 svx/qa/unit/svdraw.cxx|4 
 svx/qa/unit/table.cxx |1 
 svx/qa/unit/unodraw.cxx   |1 
 svx/qa/unit/xml.cxx   |1 
 svx/qa/unit/xoutdev.cxx   |2 
 sw/inc/strings.hrc|3 
 sw/qa/core/crsr/crsr.cxx  |1 
 sw/qa/core/draw/draw.cxx  |2 
 sw/qa/core/text/text.cxx  |1 
 sw/qa/extras/layout/layout2.cxx   |1 
 sw/qa/extras/uiwriter/uiwriter2.cxx   |1 
 sw/qa/filter/html/html.cxx|1 
 sw/qa/unit/swmodeltestbase.cxx|7 -
 sw/source/core/crsr/crsrsh.cxx|   26 
 sw/source/core/doc/textboxhelper.cxx  |1 
 sw/source/core/unocore/unolinebreak.cxx   |1 
 sw/source/uibase/docvw/SidebarTxtControl.cxx  |6 -
 sw/source/uibase/docvw/edtwin.cxx |   18 ---
 sw/source/uibase/inc/wrtsh.hxx|3 
 sw/source/uibase/shells/textsh1.cxx   |5 
 sw/source/uibase/wrtsh/delete.cxx |8 -
 sw/source/uibase/wrtsh/wrtsh1.cxx |   53 
++
 vcl/IwyuFilter_vcl.yaml   |9 -
 vcl/qa/cppunit/gen/gen.cxx|5 
 vcl/source/filter/ipdf/pdfdocument.cxx|1 
 vcl/source/filter/ipdf/pdfread.cxx|1 
 writerfilter/qa/cppunittests/dmapper/CellColorHandler.cxx |1 
 writerfilter/qa/cppunittests/dmapper/DomainMapper.cxx |1 
 writerfilter/qa/cppunittests/dmapper/DomainMapperTableHandler.cxx |1 
 writerfilter/qa/cppunittests/dmapper/DomainMapper_Impl.cxx|1 
 writerfilter/qa/cppunittests/dmapper/GraphicImport.cxx|1 
 writerfilter/qa/cppunittests/dmapper/PropertyMap.cxx  |1 
 writerfilter/qa/cppunittests/dmapper/SdtHelper.cxx|1 
 writerfilter/qa/cppunittests/dmapper/TextEffectsHandler.cxx   |1 
 writerfilter/qa/cppunittests/rtftok/rtfdispatchsymbol.cxx |4 
 writerfilter/qa/cppunittests/rtftok/rtfdispatchvalue.cxx  |1 
 writerfilter/qa/cppunittests/rtftok/rtfdocumentimpl.cxx   |1 
 writerfilter/qa/cppunittests/rtftok/rtfsdrimport.cxx  |1 
 writerfilter/qa/cppunittests/rtftok/rtfsprm.cxx   |1 
 writerfilter/qa/cppunittests/rtftok/rtftokenizer.cxx  |1 
 writerperfect/qa/unit/EPUBExportTest.cxx  |4 
 xmloff/qa/unit/draw.cxx   |5 
 xmloff/qa/unit/style.cxx  |9 -
 xmloff/qa/unit/text.cxx   |2 
 xmlsecurity/IwyuFilter_xmlsecurity.yaml   |3 
 xmlsecurity/source/helper/documentsignaturemanager.cxx|2 
 65 files changed, 84 insertions(+), 168 deletions(-)

New commits:
commit 

[Libreoffice-bugs] [Bug 152180] Emojis not exported to PDF

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

--- Comment #6 from monochro...@gmail.com ---
I can confirm that the today's nightly (if based on master) fixes this issue on
OSX.

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

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

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

Bug 97576 Summary: INSERT: SVG font glyphs ignored
https://bugs.documentfoundation.org/show_bug.cgi?id=97576

   What|Removed |Added

 Status|NEW |RESOLVED
 Resolution|--- |WONTFIX

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

[Libreoffice-bugs] [Bug 97576] INSERT: SVG font glyphs ignored

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

خالد حسني  changed:

   What|Removed |Added

 Status|NEW |RESOLVED
 Resolution|--- |WONTFIX

--- Comment #4 from خالد حسني  ---
(In reply to Stéphane Guillou (stragu) from comment #3)
> Created attachment 183728 [details]
> corresponding font for reference
> 
> The linked specification is now obsolete:
> https://www.w3.org/TR/SVG/fonts.html
> Quoting: "The elements that were defined in this chapter are now obsolete.
> The CSS Fonts Module defines how to specify fonts for documents including
> SVG."
> 
> The example files in this report use the SVG 1.0 spec.
> 
> Does it mean we should be closing this as "Won't Fix"? Or do we still want
> to be able to be compatible?

Yes, SVG fonts are long obsolete and even browsers that supported them once
dropped such support.

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

[Libreoffice-bugs] [Bug 152197] New: UPPERCASE/lowercase/Capitalize Every Word in Format->Text menu wrongly link to font effects

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

Bug ID: 152197
   Summary: UPPERCASE/lowercase/Capitalize Every Word in
Format->Text menu wrongly link to font effects
   Product: LibreOffice
   Version: unspecified
  Hardware: All
OS: All
Status: UNCONFIRMED
  Severity: normal
  Priority: medium
 Component: Documentation
  Assignee: libreoffice-bugs@lists.freedesktop.org
  Reporter: mikekagan...@hotmail.com
CC: olivier.hal...@libreoffice.org

https://help.libreoffice.org/latest/en-US/text/shared/submenu_text.html?=WRITER#hd_id172462591626807

The "UPPERCASE", "lowercase", and "Capitalize Every Word" items of the Text
menu are links to respective section in Font Effects help page (
https://help.libreoffice.org/latest/en-US/text/shared/01/05020200.html?=WRITER#hd_id3149575
). This is wrong: these commands are implemented by replacing actual characters
in the text, not by applying a formatting. This creates a wrong expectation,
that these are formatting rather than editing commands.

Only "Small capitals" in that menu applies the respective font effect.

The wrong links should be removed from the help.

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

[Libreoffice-bugs] [Bug 152180] Emojis not exported to PDF

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

--- Comment #5 from خالد حسني  ---
(In reply to monochromec from comment #2)
> Closing this bug is in direct contradiction with
> https://bugs.documentfoundation.org/show_bug.cgi?id=129523#c55 .

Since you are on macOS, you are using Apple Color Emoji font which is
supported, that comment is irrelevant to your issue.

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

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

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

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

Bug 152180 Summary: Emojis not exported to PDF
https://bugs.documentfoundation.org/show_bug.cgi?id=152180

   What|Removed |Added

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

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

[Libreoffice-bugs] [Bug 129523] Color Emojis are not exported to PDF

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

--- Comment #57 from خالد حسني  ---
*** Bug 152180 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 152180] Emojis not exported to PDF

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

خالد حسني  changed:

   What|Removed |Added

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

--- Comment #4 from خالد حسني  ---
No further info is needed, this is a duplicate and the issue is fixed in master
and will be available in 7.5 release.

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

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

[Libreoffice-bugs] [Bug 151710] Toolbar button for enclosing text in () brackets

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

--- Comment #7 from Jim Raykowski  ---
Macro's can also be assigned to menu and toolbars. Surprise surprise. Seriously
I didn't know that until today. Way cool!

But perhaps this is an enhancement that is worthy of it's own UNO. IMHO it
would make an interesting beginners hack. I can supply code pointers if needed.

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

[Libreoffice-bugs] [Bug 118792] SVGIO: Add support for font variation settings in SVG

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

Bug 103596 Summary: Support OpenType variable font (OTVF) based text layout
https://bugs.documentfoundation.org/show_bug.cgi?id=103596

   What|Removed |Added

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

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

[Libreoffice-bugs] [Bug 71732] [META] Bugs related to text rendering, typography and font features in LO

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

Bug 103596 Summary: Support OpenType variable font (OTVF) based text layout
https://bugs.documentfoundation.org/show_bug.cgi?id=103596

   What|Removed |Added

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

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

[Libreoffice-bugs] [Bug 103596] Support OpenType variable font (OTVF) based text layout

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

خالد حسني  changed:

   What|Removed |Added

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

--- Comment #32 from خالد حسني  ---
This should be fixed now. We support variable fonts and apply variations to
text metrics and layout features properly. Support is currently limited to
named instances, to support arbitrary font variations, we will need both UI
support as well as file format support, so this should be tracked separately.

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

[Libreoffice-bugs] [Bug 35538] Handling of fonts with more than 4 styles (R/B/I/BI) is suboptimal

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

خالد حسني  changed:

   What|Removed |Added

 Blocks|103596  |


Referenced Bugs:

https://bugs.documentfoundation.org/show_bug.cgi?id=103596
[Bug 103596] Support OpenType variable font (OTVF) based text layout
-- 
You are receiving this mail because:
You are the assignee for the bug.

[Libreoffice-bugs] [Bug 103596] Support OpenType variable font (OTVF) based text layout

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

خالد حسني  changed:

   What|Removed |Added

 Depends on|35538   |


Referenced Bugs:

https://bugs.documentfoundation.org/show_bug.cgi?id=35538
[Bug 35538] Handling of fonts with more than 4 styles (R/B/I/BI) is suboptimal
-- 
You are receiving this mail because:
You are the assignee for the bug.

[Libreoffice-bugs] [Bug 141726] LO Writer - Bold not working with variable EB Garamond

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

--- Comment #8 from خالد حسني  ---


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

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

[Libreoffice-bugs] [Bug 140710] Google-Font Sora Bold not supported for PDF export or Print

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

--- Comment #24 from خالد حسني  ---


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

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

[Libreoffice-bugs] [Bug 147824] PDF export no fat text on different fonts

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

--- Comment #5 from خالد حسني  ---


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

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

[Libreoffice-bugs] [Bug 145306] Libreoffice writer does not include text while exporting to PDF.

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

--- Comment #5 from خالد حسني  ---


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

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

[Libreoffice-bugs] [Bug 146355] Text in the Cantarell font will not appear when converting to a PDF

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

--- Comment #3 from خالد حسني  ---


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

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

[Libreoffice-bugs] [Bug 149879] Cantarell font not rendered in exported PDF

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

--- Comment #2 from خالد حسني  ---


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

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

[Libreoffice-bugs] [Bug 140538] Some bold Google Fonts not exporting to PDF

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

--- Comment #13 from خالد حسني  ---


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

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

[Libreoffice-bugs] [Bug 113305] [META] Bundled fonts bugs and enhancements

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

Bug 114855 Summary: Replacing Source Sans Pro by Source Sans Variable
https://bugs.documentfoundation.org/show_bug.cgi?id=114855

   What|Removed |Added

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

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

[Libreoffice-bugs] [Bug 114855] Replacing Source Sans Pro by Source Sans Variable

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

خالد حسني  changed:

   What|Removed |Added

   Severity|normal  |enhancement
 Status|RESOLVED|NEW
 Resolution|DUPLICATE   |---

--- Comment #4 from خالد حسني  ---
I don't see why this was made a duplicate of bug 103596, as thus obe is about
replacing a font and should be judged on its own merit.

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

[Libreoffice-bugs] [Bug 152195] Instantiate OpenType variable fonts when embedding in ODF

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

خالد حسني  changed:

   What|Removed |Added

 Resolution|--- |WONTFIX
 Status|UNCONFIRMED |RESOLVED

--- Comment #1 from خالد حسني  ---
We don't subset fonts embedded in ODF files and I don't see why we should
instantiate them either. PDF is different because it is a legacy format with
lots of weird requirements and constraints.

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

[Libreoffice-commits] core.git: 2 commits - include/oox io/source jvmfwk/inc lotuswordpro/inc lotuswordpro/source oox/source

2022-11-23 Thread Noel Grandin (via logerrit)
 include/oox/helper/propertymap.hxx|2 -
 include/oox/ole/axbinaryreader.hxx|   14 +++-
 include/oox/ole/axbinarywriter.hxx|5 ++-
 include/oox/ole/olehelper.hxx |2 -
 io/source/acceptor/acceptor.hxx   |2 +
 jvmfwk/inc/vendorbase.hxx |   11 +++---
 lotuswordpro/inc/xfilter/xfparastyle.hxx  |2 -
 lotuswordpro/source/filter/explode.hxx|1 
 lotuswordpro/source/filter/lwpcelllayout.hxx  |1 
 lotuswordpro/source/filter/lwplayout.hxx  |   24 ++-
 lotuswordpro/source/filter/lwppara.hxx|2 -
 lotuswordpro/source/filter/lwprowlayout.hxx   |2 -
 lotuswordpro/source/filter/lwpsdwrect.hxx |2 -
 lotuswordpro/source/filter/lwptable.hxx   |5 ++-
 lotuswordpro/source/filter/lwptablelayout.hxx |   41 --
 oox/source/drawingml/diagram/datamodel.hxx|1 
 16 files changed, 66 insertions(+), 51 deletions(-)

New commits:
commit b1fad7043a7286d5d9bb33c9ed9235f044d92aed
Author: Noel Grandin 
AuthorDate: Wed Nov 23 16:15:17 2022 +0200
Commit: Noel Grandin 
CommitDate: Thu Nov 24 07:00:21 2022 +0100

loplugin:unusedfields make some fields private

this is one of the secondary analyses this plugin performs

Change-Id: I6fac8c926b53f1d909c5b183304744126549f2bc
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/143181
Tested-by: Jenkins
Reviewed-by: Noel Grandin 

diff --git a/include/oox/helper/propertymap.hxx 
b/include/oox/helper/propertymap.hxx
index 423bb11fcdcb..cf8031d46dd1 100644
--- a/include/oox/helper/propertymap.hxx
+++ b/include/oox/helper/propertymap.hxx
@@ -117,8 +117,6 @@ public:
 #endif
 private:
 const std::vector* mpPropNames;
-
-protected:
 std::map< sal_Int32, css::uno::Any > maProperties;
 };
 
diff --git a/include/oox/ole/axbinaryreader.hxx 
b/include/oox/ole/axbinaryreader.hxx
index eb185f235d49..e5e59b970d2f 100644
--- a/include/oox/ole/axbinaryreader.hxx
+++ b/include/oox/ole/axbinaryreader.hxx
@@ -170,8 +170,9 @@ private:
 /** Complex property for a 32-bit value pair, e.g. point or size. */
 struct PairProperty final : public ComplexProperty
 {
+private:
 AxPairData& mrPairData;
-
+public:
 explicitPairProperty( AxPairData& rPairData ) :
 mrPairData( rPairData ) {}
 virtual boolreadProperty( AxAlignedInputStream& rInStrm ) 
override;
@@ -180,9 +181,10 @@ private:
 /** Complex property for a string value. */
 struct StringProperty final : public ComplexProperty
 {
+private:
 OUString&mrValue;
 sal_uInt32  mnSize;
-
+public:
 explicitStringProperty( OUString& rValue, sal_uInt32 nSize 
) :
 mrValue( rValue ), mnSize( nSize ) {}
 virtual boolreadProperty( AxAlignedInputStream& rInStrm ) 
override;
@@ -191,8 +193,10 @@ private:
 /** Complex property for an array of strings. */
 struct ArrayStringProperty final : public ComplexProperty
 {
+private:
 AxArrayString&  mrArray;
 sal_uInt32  mnSize;
+public:
 explicitArrayStringProperty( AxArrayString& rArray, 
sal_uInt32 nSize ) :
 mrArray( rArray ), mnSize( nSize ) {}
 virtual boolreadProperty( AxAlignedInputStream& rInStrm ) 
override;
@@ -201,8 +205,10 @@ private:
 /** Complex property for a GUID value. */
 struct GuidProperty final : public ComplexProperty
 {
+private:
 OUString&mrGuid;
 
+public:
 explicitGuidProperty( OUString& rGuid ) :
 mrGuid( rGuid ) {}
 virtual boolreadProperty( AxAlignedInputStream& rInStrm ) 
override;
@@ -211,8 +217,10 @@ private:
 /** Stream property for a font structure. */
 struct FontProperty final : public ComplexProperty
 {
+private:
 AxFontData& mrFontData;
 
+public:
 explicitFontProperty( AxFontData& rFontData ) :
 mrFontData( rFontData ) {}
 virtual boolreadProperty( AxAlignedInputStream& rInStrm ) 
override;
@@ -221,8 +229,10 @@ private:
 /** Stream property for a picture or mouse icon. */
 struct PictureProperty final : public ComplexProperty
 {
+private:
 StreamDataSequence& mrPicData;
 
+public:
 explicitPictureProperty( StreamDataSequence& rPicData ) :
 mrPicData( rPicData ) {}
 virtual boolreadProperty( AxAlignedInputStream& rInStrm ) 
override;
diff --git a/include/oox/ole/axbinarywriter.hxx 
b/include/oox/ole/axbinarywriter.hxx
index eb370473aecb..d19e2ae3b3c3 100644
--- a/include/oox/ole/axbinarywriter.hxx
+++ 

[Libreoffice-bugs] [Bug 152196] Visible gaps in Arabic/Persian text with fallback font

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

افشین  changed:

   What|Removed |Added

 Ever confirmed|0   |1
 Status|UNCONFIRMED |NEW

--- Comment #1 from افشین  ---
I can reproduce this bug. 

Version: 7.4.2.3 / LibreOffice Community
Build ID: 40(Build:3)
CPU threads: 2; OS: Linux 5.15; UI render: default; VCL: gtk3
Locale: fa-IR (en_US.UTF-8); UI: en-US
Ubuntu package version: 1:7.4.2~rc3-0ubuntu0.22.04.1~lo1
Calc: threaded

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

[Libreoffice-bugs] [Bug 152196] New: Visible gaps in Arabic/Persian text with fallback font

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

Bug ID: 152196
   Summary: Visible gaps in Arabic/Persian text with fallback font
   Product: LibreOffice
   Version: 7.4.0.3 release
  Hardware: All
OS: All
Status: UNCONFIRMED
  Severity: normal
  Priority: medium
 Component: Writer
  Assignee: libreoffice-bugs@lists.freedesktop.org
  Reporter: hoss...@libreoffice.org

Created attachment 183747
  --> https://bugs.documentfoundation.org/attachment.cgi?id=183747=edit
Visible gaps in Arabic/Persian text

Description:
When copying text, or creating a new file, sometimes a fallback font is used
that does not contain characters for many languages. In this case, the
character dimensions are incorrectly calculated.

Steps to Reproduce:
1. Open attachment

Actual Results:
See the visible gaps in Arabic/Persian text. The selected font is "Lohit
Devanagari", and the fallback font is "FreeSerif". The problem disappears when
setting "FreeSerif" font for the text. The problem is not visible in the PDF
export.

Expected Results:
There should not be gaps between joined characters in Arabic/Persian text like
جمع.

Reproducible: Always


User Profile Reset: No


Additional Info:

Reproducible with the latest LO dev 7.5
Version: 7.5.0.0.alpha0+ (X86_64) / LibreOffice Community
Build ID: 651658d37bcb3f493942dd5d0b9a0d65c96f105c
CPU threads: 8; OS: Linux 5.15; UI render: default; VCL: gtk3
Locale: en-US (en_US.UTF-8); UI: en-US
Calc: threaded

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

Not reproducible with LO 7.3
Version: 7.3.6.1 / LibreOffice Community
Build ID: 92b673af3a5e8f7cf4716be88dfaca424612f244
CPU threads: 8; OS: Linux 5.15; UI render: default; VCL: x11
Locale: en-US (en_US.UTF-8); UI: en-US
Calc: threaded

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

[Libreoffice-bugs] [Bug 152195] New: Instantiate OpenType variable fonts when embedding in ODF

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

Bug ID: 152195
   Summary: Instantiate OpenType variable fonts when embedding in
ODF
   Product: LibreOffice
   Version: 7.5.0.0 alpha0+ Master
  Hardware: All
OS: All
Status: UNCONFIRMED
  Severity: normal
  Priority: medium
 Component: LibreOffice
  Assignee: libreoffice-bugs@lists.freedesktop.org
  Reporter: shanshandehongx...@outlook.com

Description:
Since bug 108497 is fixed, it's possible to convert font variation instances
into static glyphs and embed into ODF files as well. Because LibreOffice allows
to embed a font file into ODF, there is also necessary to make this mechanism
works for ODF export so make it looks as expected for many other computer
environment, and keep ODF file size smaller.

Steps to Reproduce:
-

Actual Results:
-

Expected Results:
-


Reproducible: Always


User Profile Reset: No

Additional Info:
-

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

[Libreoffice-bugs] [Bug 152166] Writer document Crashes when inserting an Index (Table of Contents, or other index)

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

--- Comment #2 from kb.cl...@gmail.com ---
Hi, thanks for the fast response.
I tried to sanitize the document as described in
https://wiki.documentfoundation.org/QA/Bugzilla/Sanitizing_Files_Before_Submission

Two massive bugs again:
1) regular expression change of all characters fails! I used "." as the regular
expression without quotation marks. And replaced by an x. Additionally I chose
format - the only font used in all document and "regular" to preserve all
captions which are in italic (nothing else is italic in the document).
This did NOT replace all characters but kept several paragraphs in its original
form, while they fully and entirely matched the search parameters. Same font,
same font attributes, same style as others, no direct formatting.

2) When I want to save the changes, LO writer again freezes.

So, sad to say that I cannot provide the file as this is extremely sensitive.

I am really worried whether changing to LO was a good move and I need to go
back to MS Office. LO is terribly unstable and full of bugs, a nightmare and I
am almost shocked that this has version 7 while being in fact a beta version.

Is there no log file, no debug file, not the slightest support for recording
failures, or debugging them? How ever do you want to make a software stable
without such features?

However, I think it does not make sense to continue this bugreport.

Thanks.

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

[Libreoffice-bugs] [Bug 103596] Support OpenType variable font (OTVF) based text layout

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

--- Comment #31 from Volga  ---
Now it's necessary to add some options to tweak variation axis.

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

[Libreoffice-bugs] [Bug 152157] Update Available icon (on menu bar) messes up ability to work with multiple Calc windows

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

Adolfo Jayme Barrientos  changed:

   What|Removed |Added

Summary|Update Available icon (on   |Update Available icon (on
   |InfoBar) messes up ability  |menu bar) messes up ability
   |to work with multiple Calc  |to work with multiple Calc
   |windows |windows

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

[Libreoffice-ux-advise] [Bug 152157] Update Available icon (on menu bar) messes up ability to work with multiple Calc windows

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

Adolfo Jayme Barrientos  changed:

   What|Removed |Added

Summary|Update Available icon (on   |Update Available icon (on
   |InfoBar) messes up ability  |menu bar) messes up ability
   |to work with multiple Calc  |to work with multiple Calc
   |windows |windows

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

[Libreoffice-bugs] [Bug 152192] Support output filepath in CLI convert

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

--- Comment #1 from Mike Kaganski  ---
Given that the --convert-to is a switch, which enables conversion mode for *any
number* of following input files, and its --outdir matches that - it looks not
easy to come with a logical CLI to specify per-file output name... any
suggestion?

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

[Libreoffice-bugs] [Bug 145820] When opening a impress document via Nautilus in Ubuntu the window is kind of minimized

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

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 145063] FILESAVE: very slow file saving in Draw, sometimes hanging

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

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 151978] Need another way to apply a style to Draw textboxes

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

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 151789] Suscript button automatically become ON when japanese character entered (or pasted) after subscript.

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

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 152110] LanguageTool ext. prevents adding words to dictionaries with 2+ dictionaries present

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

QA Administrators  changed:

   What|Removed |Added

 Status|NEEDINFO|UNCONFIRMED
 Ever confirmed|1   |0

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

[Libreoffice-bugs] [Bug 152098] Large Writer document 15x slower to open in 7.3.7.2 and does not open at last cursor position

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

QA Administrators  changed:

   What|Removed |Added

 Status|NEEDINFO|UNCONFIRMED
 Ever confirmed|1   |0

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

[Libreoffice-bugs] [Bug 152110] LanguageTool ext. prevents adding words to dictionaries with 2+ dictionaries present

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

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

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

[Libreoffice-bugs] [Bug 152098] Large Writer document 15x slower to open in 7.3.7.2 and does not open at last cursor position

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

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

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

[Libreoffice-bugs] [Bug 148605] Writer no fonts shown in drop-down box

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

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 148605] Writer no fonts shown in drop-down box

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

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

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

[Libreoffice-bugs] [Bug 148781] I have tried to open LibreOffice and it will not run. I cannot open any of my documents.

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

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 148781] I have tried to open LibreOffice and it will not run. I cannot open any of my documents.

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

--- Comment #3 from QA Administrators  ---
Dear Jason Richardson,

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 148780] UNWANTED SPACES on Entering Next Line in Writer Document

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

--- Comment #4 from QA Administrators  ---
Dear Digi Abros,

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 148780] UNWANTED SPACES on Entering Next Line in Writer Document

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

QA Administrators  changed:

   What|Removed |Added

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

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

[Libreoffice-bugs] [Bug 142397] Libreoffice 7.X freezes on search with LInux Mint 19.3

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

QA Administrators  changed:

   What|Removed |Added

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

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

[Libreoffice-bugs] [Bug 142397] Libreoffice 7.X freezes on search with LInux Mint 19.3

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

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

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 142068] EDITING Unable to add new animations to text on any slide after duplicating a slide in LibreOffice Impress

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

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 142068] EDITING Unable to add new animations to text on any slide after duplicating a slide in LibreOffice Impress

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

--- Comment #3 from QA Administrators  ---
Dear speed.toyne,

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 142034] Selecting (single left-click) cell enters edit mode directly when compose character on keyboard was struck beforehand

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

QA Administrators  changed:

   What|Removed |Added

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

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

[Libreoffice-bugs] [Bug 142034] Selecting (single left-click) cell enters edit mode directly when compose character on keyboard was struck beforehand

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

--- Comment #3 from QA Administrators  ---
Dear Andrew Siplas,

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 96374] Default Asian font size of shapes in chart

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

--- Comment #5 from QA Administrators  ---
Dear HD,

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 91134] Context menu closes after hiding or making buttons on the toolbars visible

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

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

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 89673] EDITING - can't use the regular context menu on misspelled words

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

--- Comment #9 from QA Administrators  ---
Dear Octavio Alvarez,

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 62422] Incorrect word spacing and then line wrapping of .docx files with Microsoft font TNR

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

--- Comment #8 from QA Administrators  ---
Dear brian.bj.parker99,

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 138372] DDE links are always absolute

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

--- Comment #4 from QA Administrators  ---
Dear Miklos Vajna,

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 131203] In the case of import of some DOCX documents with tables with specified table column width, created with Apache POI library, LO throws an exception

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

--- Comment #12 from QA Administrators  ---
Dear Artur Linhart,

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 112604] Set a maximum width for the Calc Sort dialog

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

--- Comment #14 from QA Administrators  ---
Dear andréb,

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

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

If you have time, please do the following:

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

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

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

Please DO NOT

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


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

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


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

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

Warm Regards,
QA Team

MassPing-UntouchedBug

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

[Libreoffice-bugs] [Bug 151710] Toolbar button for enclosing text in () brackets

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

--- Comment #6 from Jim Raykowski  ---
I just today discovered that macros can be assigned shortcuts :-)

Menu > Tools > Customize > Keyboard
Category -> Application Macros

FWIW here is a Basic macro that will place () around selected text.
Disclaimer: I'm no basic macro expert so YMMV.

Sub Parenthesize
  Dim oCurrentSelection as Object
  oCurrentSelection = thisComponent.getCurrentSelection()
  if oCurrentSelection.supportsService("com.sun.star.text.TextRanges") then
nCount = oCurrentSelection.Count
if nCount = 1 then
  oTextRange = oCurrentSelection.getByIndex(0)
  oTextRange.String = "(" + oTextRange.String + ")"
else
  for i = 1 to nCount - 1
oTextRange = oCurrentSelection.getByIndex(i)
oTextRange.String = "(" + oTextRange.String + ")"
  next
end if
  end if
End Sub

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

[Libreoffice-bugs] [Bug 152194] LibreOffice GUI Start as a very tiny window

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

--- Comment #1 from CharlieRamirez  ---
Created attachment 183746
  --> https://bugs.documentfoundation.org/attachment.cgi?id=183746=edit
Tiny Libreoffice windows Over terminal

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

[Libreoffice-bugs] [Bug 152194] New: LibreOffice GUI Start as a very tiny window

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

Bug ID: 152194
   Summary: LibreOffice GUI Start as a very tiny window
   Product: LibreOffice
   Version: 7.4.2.3 release
  Hardware: x86-64 (AMD64)
OS: Linux (All)
Status: UNCONFIRMED
  Severity: normal
  Priority: medium
 Component: UI
  Assignee: libreoffice-bugs@lists.freedesktop.org
  Reporter: todo.ciencia.y.electron...@gmail.com

Description:
Libreoffice in all programs tends to Start as a very small window (ONLY THE
CLOSE BUTTON AND LOGO IS VISIBLE) in the upper right corner that is impossible
to click until you give it a little resized by dragging its corner.
since the last updates of the Debian Testing for Libreoffice repository This
tends to Start as a very small window (ONLY THE CLOSE BUTTON AND LOGO IS
VISIBLE) in the upper right corner that is impossible to click until you give
it a little resized by dragging its corner.

Reading in the Manjaro and Linux mint groups, there are ubuntu and debian users
who seem to be repeating this problem since last year with various desktops.

So far I have only found one Solution by a manjaro user (applicable to debian)
by checking and editing some Window values using the terminal (some users on
ubuntu have resorted to using macros to resize on open.) but so far At the
moment I have not found if the problem resides entirely in libreoffice or the
desktop managers (since some users report that it changes between machines that
share a desktop or systems)

See Related to bug:
https://forum.manjaro.org/t/libre-office-weird-small-windows-in-plasma-issue/122403
https://forums.linuxmint.com/viewtopic.php?f=47=355433
https://forum.manjaro.org/t/libreoffice-calc-does-not-open-correctly-after-recent-testing-update/122084/4
https://github.com/QubesOS/qubes-issues/issues/3281
https://groups.google.com/g/qubes-users/c/GA21ZTGWWBA/m/2ATd3VhmAgAJ?pli=1

Steps to Reproduce:
1. Using a Debian installation with plasma environment Testing repositories
Enabled and up-to-date updates for system and libreoffice Version: 7.4.2.3
[Apparently it can also happen with manjaro, Mint Qubes OS and ubuntu with
Plasma and xFce4 environments]
2.Open and close LibreOffice resize and drag window as normaly... in one of
these open app process a very tiny window would appear
3. Open terminal and run 
grep ooSetupFactoryWindowAttributes
~/.config/libreoffice/4/user/registrymodifications.xcu

Return values will be near to 0,00 [the bug itself].

in my case
0,0,1,1;5;0,0,0,0;
31,50,1245,718;1;0,0,0,0;
-1121821488,2056420896,-1097813872,616144784;5;0,0,0,0;
0,0,1,1;5;0,0,0,0;

-Accrding a MAnjaro User changing the values or compairing. values will be near
to:
grep ooSetupFactoryWindowAttributes
~/.config/libreoffice/4/user/registrymodifications.xcu 
1024,24,39,32;5;1024,24,1680,1025;
1024,24,39,32;5;1024,32,1680,1017;
0,51,4,4;5;0,51,1024,1228; 

These paremeters are:
x-pos,y-pos,width,height ; window-state ;
maximized-x-pos,maximized-y-pos,maximized-width,maximized-height ;

Actual Results:
Libreoffice in any of its programs (Calc,writer etc.) starts as an extremely
small window in which only the close button is visible and the user must
rearrange and resize the window by manual dragging at each start

Expected Results:
Libreoffice should either remember its previously used window size or start at
a default minimum window size


Reproducible: Always


User Profile Reset: No

Additional Info:
Version: 7.4.2.3 / LibreOffice Community
Build ID: 40(Build:3)
CPU threads: 8; OS: Linux 6.0; UI render: default; VCL: kf5 (cairo+xcb)
Locale: es-MX (es_MX.UTF-8); UI: es-ES
Debian package version: 1:7.4.2-3
Calc: threaded

Posted as Libreoffice unespicified (Bugzilla dont allow me to post as GUI
7.4.2.3)

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

[Libreoffice-bugs] [Bug 148435] LibreOffice on macOS hangs on using window snapping / window manager (BetterTouchTool, Rectangle, Raycast, Amethyst, ...) or any other redraw, context switch, etc, from

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

--- Comment #49 from steve  ---
Are there builds available to test? For all I know todays main build still
crashes.

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

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

[Libreoffice-bugs] [Bug 152193] the printout of the document has sections of text missing

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

--- Comment #2 from ella.me...@gmail.com ---
Created attachment 183745
  --> https://bugs.documentfoundation.org/attachment.cgi?id=183745=edit
.ODT printout photo

example

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

[Libreoffice-bugs] [Bug 152193] the printout of the document has sections of text missing

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

--- Comment #1 from ella.me...@gmail.com ---
Created attachment 183744
  --> https://bugs.documentfoundation.org/attachment.cgi?id=183744=edit
.ODT

example

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

[Libreoffice-bugs] [Bug 120941] PPTX with dashed line exported to a large size SVG

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

Rajasekaran Karunanithi  changed:

   What|Removed |Added

 CC||rajasekara...@gmail.com

--- Comment #13 from Rajasekaran Karunanithi  ---
Exported into pdf and svg formats,line element was same in both formats. pdf
size: 1.56kb and svg size:482kb.So still reproducable in LO 7.4.2.3 under
Windows 10(x64).

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

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

[Libreoffice-bugs] [Bug 152193] New: the printout of the document has sections of text missing

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

Bug ID: 152193
   Summary: the printout of the document has sections of text
missing
   Product: LibreOffice
   Version: 7.3.7.2 release
  Hardware: All
OS: Linux (All)
Status: UNCONFIRMED
  Severity: normal
  Priority: medium
 Component: Writer
  Assignee: libreoffice-bugs@lists.freedesktop.org
  Reporter: ella.me...@gmail.com

Description:
I wrote a document with headings and bulleted/numbered lists. The printout of
the document has sections of text missing.

Actual Results:
Prints only partial text.

Expected Results:
Print full text.


Reproducible: Always


User Profile Reset: Yes

Additional Info:
n/a

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

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

2022-11-23 Thread Caolán McNamara (via logerrit)
 vcl/source/outdev/text.cxx |4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

New commits:
commit 651658d37bcb3f493942dd5d0b9a0d65c96f105c
Author: Caolán McNamara 
AuthorDate: Wed Nov 23 20:07:20 2022 +
Commit: Caolán McNamara 
CommitDate: Thu Nov 24 00:16:17 2022 +0100

ofz#53673 Integer-overflow LogicWidthToDeviceCoordinate takes Long anyway

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

diff --git a/vcl/source/outdev/text.cxx b/vcl/source/outdev/text.cxx
index 3e86ab61d19f..7b9dde2a94a8 100644
--- a/vcl/source/outdev/text.cxx
+++ b/vcl/source/outdev/text.cxx
@@ -1793,8 +1793,8 @@ void OutputDevice::ImplDrawText( OutputDevice& 
rTargetDevice, const tools::Recta
 {
 std::unique_ptr const pCaretXArray(new sal_Int32[2 * 
aStr.getLength()]);
 /*sal_Bool bRet =*/ _rLayout.GetCaretPositions( aStr, 
pCaretXArray.get(), 0, aStr.getLength() );
-sal_Int32 lc_x1 = pCaretXArray[2*nMnemonicPos];
-sal_Int32 lc_x2 = pCaretXArray[2*nMnemonicPos+1];
+tools::Long lc_x1 = pCaretXArray[2*nMnemonicPos];
+tools::Long lc_x2 = pCaretXArray[2*nMnemonicPos+1];
 nMnemonicWidth = rTargetDevice.LogicWidthToDeviceCoordinate( 
std::abs(lc_x1 - lc_x2) );
 
 Point aTempPos = rTargetDevice.LogicToPixel( aPos );


[Libreoffice-bugs] [Bug 142341] F4 shortcut for switching between relative and absolute cell references doesn't work in range pickers

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

--- Comment #3 from Olivier Hallot  ---
*Not* confirmed in Windows 10 with 

Version: 7.4.2.3 (x64) / LibreOffice Community
Build ID: 382eef1f22670f7f4118c8c2dd222ec7ad009daf
CPU threads: 8; OS: Windows 10.0 Build 19045; UI render: Skia/Raster; VCL: win
Locale: pt-BR (pt_BR); UI: pt-BR
Calc: CL

Step to confirm

Place formula in B1: "=a1", and cycle with F4.

I get: A1, $A1, A$1, and $A$1.

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

[Libreoffice-bugs] [Bug 64891] FORMATTING: Bibliography styles are forgotten on Writer restart

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

--- Comment #14 from Amalia Olive  ---
(so it's a regression, but not new; and also has nothing to do with gtk,
because reproducible on Windows). Possibly you www.bestassignmentwriters.co.uk
had used OS/WM dialogs previously, and so didn't experience the problem.

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

[Libreoffice-bugs] [Bug 64891] FORMATTING: Bibliography styles are forgotten on Writer restart

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

--- Comment #13 from Amalia Olive  ---
(so it's a regression, but not new; and also has nothing to do with gtk,
because reproducible on Windows). Possibly visit this
www.bestassignmentwriters.co.uk you had used OS/WM dialogs previously, and so
didn't experience the problem.

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

[Libreoffice-bugs] [Bug 152192] New: Support output filepath in CLI convert

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

Bug ID: 152192
   Summary: Support output filepath in CLI convert
   Product: LibreOffice
   Version: 7.4.2.3 release
  Hardware: All
OS: All
Status: UNCONFIRMED
  Severity: enhancement
  Priority: medium
 Component: LibreOffice
  Assignee: libreoffice-bugs@lists.freedesktop.org
  Reporter: a...@sa.dk

Description:
Command line interface convert using --convert-to does not support specifying
an output filepath. It supports specifying an output folder --outdir.

This makes using LibreOffice for workflow conversion in foreach loops using
input and output filepaths cumbersome. You need extra code to circumvent for
instance, if you want to rename your output file. This means after conversion
you have to write code to search for the converted file and then rename it, not
really having full control of the workflow.

Adding support for output filepaths would be great!

Actual Results:
At the moment, you can only set an output folder.

Expected Results:
Possibility to set output filepath in LibreOffice CLI.
There should be a check to make sure the extension of output filepath is
identical to set --convert-to extension.
There should be a check to make sure that both output filepath and output
folder is not set at the same time.


Reproducible: Always


User Profile Reset: No

Additional Info:
Thanks for making it possible to use LibreOffice in CLI mode to convert files.

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

[Libreoffice-bugs] [Bug 152118] Dates imported erroneously from Calc to a Firebird database table

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

--- Comment #13 from jcs...@libreoffice.org ---
(In reply to Eike Rathke from comment #12)
> The SQL statement outputs the raw data formatted as date, which is stored in
> the proleptic Gregorian calendar, and apparently dates before 0001-01-01
> (i.e. negative dates or dates BCE) can not be stored in the database (if
> they could in Firebird then someone would have to implement that). The table
> grid view displays data in the locale's calendar.
> 
> > I was supposed to use proleptic Gregorian calendar in Calc
> Calc does not use the proleptic Gregorian calendar. It uses the locale's
> default calendar. As explained in bug 152114 that usually is (does not have
> to be) the Gregorian calendar after the Gregorian cut-off date, and Julian
> calendar before that. If the cut-off date is 1582-10-15 (Gregorian) then
> subtracting 1 from that date yields 1582-10-04 (Julian). Btw, also for Calc
> .ods and other ODF file formats, dates are always stored in the proleptic
> Gregorian calendar.
> 

Now the light has come on and I'm beginning to understand all this mess

But in any case, it seems to me that most users don't know about calendars and
don't care. I myself was unaware of it and, as you can see, I'm still confused.

But me, and I think most of the users, expect the same data in every place
whatever the calendar is, and whatever was the application that stored the
data.

On the other hand, I think it makes no sense that three dates that are
different in the source (0001-01-01, 0001-01-02 and 0001-01-03) are all stored
as the same date (0001-01-01) instead of showing an error in case the
conversion produces invalid dates for the database.

> To solve this (expectation of display being what's stored) it would need an
> option to force the proleptic Gregorian calendar for display.

That could be a solution, especially in Base, since most databases, it seems,
use the Gregorian proleptic calendar

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

[Libreoffice-bugs] [Bug 145820] When opening a impress document via Nautilus in Ubuntu the window is kind of minimized

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

raal  changed:

   What|Removed |Added

 CC||r...@post.cz

--- Comment #1 from raal  ---
No repro with Version: 7.3.7.2 / LibreOffice Community
Build ID: 30(Build:2)
CPU threads: 4; OS: Linux 5.15; UI render: default; VCL: gtk3
Locale: cs-CZ (cs_CZ.UTF-8); UI: cs-CZ
Ubuntu package version: 1:7.3.7-0ubuntu0.22.04.1
Calc: threaded

Ubuntu 22.04

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

[Libreoffice-bugs] [Bug 152131] Dragging document from window header bar to another location copies wrong document version

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

--- Comment #4 from Mike Little  ---
I have chosen the NEEDINFO  status, as I believe this will need to be escalated
to development.

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

[Libreoffice-bugs] [Bug 145573] QR code insert don't work (Fedora)

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

raal  changed:

   What|Removed |Added

 Status|UNCONFIRMED |NEEDINFO
 Ever confirmed|0   |1
 CC||r...@post.cz

--- Comment #5 from raal  ---
Please test with TDF's packages:
https://www.libreoffice.org/download/download-libreoffice/

Works for me with Version: 7.5.0.0.alpha0+ (X86_64) / LibreOffice Community
Build ID: 7b23c53232245a1f61c3e8ddff59d049a49fe975
CPU threads: 4; OS: Linux 5.15; UI render: default; VCL: gtk3
Locale: cs-CZ (cs_CZ.UTF-8); UI: en-US
Calc: threaded

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

[Libreoffice-bugs] [Bug 146133] No access to file "Il Regno dei Funghi.doc" after an update

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

raal  changed:

   What|Removed |Added

 Status|UNCONFIRMED |NEEDINFO
 Ever confirmed|0   |1
 CC||r...@post.cz

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

[Libreoffice-bugs] [Bug 145063] FILESAVE: very slow file saving in Draw, sometimes hanging

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

raal  changed:

   What|Removed |Added

 Status|UNCONFIRMED |NEEDINFO
 CC||r...@post.cz
 Ever confirmed|0   |1

--- Comment #3 from raal  ---
No repro with Version: 7.5.0.0.alpha0+ (X86_64) / LibreOffice Community
Build ID: 7b23c53232245a1f61c3e8ddff59d049a49fe975
CPU threads: 4; OS: Linux 5.15; UI render: default; VCL: gtk3
Locale: cs-CZ (cs_CZ.UTF-8); UI: en-US
Calc: threaded

Please attach test file, thank you.

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

[Libreoffice-bugs] [Bug 152131] Dragging document from window header bar to another location copies wrong document version

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

--- Comment #3 from Mike Little  ---
Hello Andrew, thank you for the screen shots.. they really helped me understand
the problem and the expected behaviour… 

OK…
Version: 7.4.2.3 / LibreOffice Community
Build ID: 382eef1f22670f7f4118c8c2dd222ec7ad009daf
CPU threads: 4; OS: Mac OS X 13.0; UI render: default; VCL: osx
Locale: en-AU (en_AU.UTF-8); UI: en-US
Calc: threaded

See my comments, “MJL>>” below…


1. I'm starting with Writer not running.

MJL>> Done

2. Open Writer, and click on "Create:/ Writer Document" on the sidebar of the
window which opens.

MJL>> Done

3. A window opens with Untitled 1 in the title bar

MJL>> I observed this, Confirmed.

4. I type "This is the original document" into the new document. 
(See: https://cloud.orcro.eu/s/ySaEMLWcqKTP6pd for screenshot)

MJL>> Done.

5. I select File/Save As... and save as Test.odt. The directory is my default
Document directory. 

MJL>> Done.


6. Note that there is no draggable icon next to "Test.odt" on the title bar
(see screenshot). You'll note that the "unsaved" indicator (black dot) in the
red window control button (top left corner) is NOT showing (i.e. indicating
that the document is saved)

MJL>> I observed this, Confirmed.


7. I type "And this is an amendment" into the document. The black dot
("unsaved" indicator (correctly) shows). 

MJL>> Done.


8. I select "File/Save As..." and save the document as Test001.odt. The icon is
now showing.
See https://cloud.orcro.eu/s/eX8BZAcN5ktgrTB for screenshot) 

MJL>> I observed this, Confirmed.



9. I drag the icon next to Test001.odt in the title bar onto the desktop. As
the icon leaves the document window and hovers over the desktop, the name of
the file changes to "Test.odt". If I open that file, it contains the content of
Test.odt. The same behaviour occurs if I drag it into a Finder window
displaying the content of a different directory. 
For screenshot, see: https://cloud.orcro.eu/s/spef8mosdsg89yE

MJL>> I observed this, Confirmed.


10. If I try to repeat the drag operation, I get an error box saying document
drag error.
For screenshot see https://cloud.orcro.eu/s/YAHGBq683fgwYNY

MJL>> I observed this, Confirmed.


CONCLUSION: THIS BEHAVIOR IS CONFIRMED, AND I WOULD CONSIDER IT A DEFECT.

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

[Libreoffice-commits] core.git: Changes to 'refs/tags/cp-21.06.35-2'

2022-11-23 Thread Andras Timar (via logerrit)
Tag 'cp-21.06.35-2' created by Andras Timar  at 
2022-11-23 21:52 +

cp-21.06.35-2

Changes since cp-21.06.35-1-1:
---
 0 files changed
---


[Libreoffice-commits] translations.git: Changes to 'refs/tags/cp-21.06.35-2'

2022-11-23 Thread Andras Timar (via logerrit)
Tag 'cp-21.06.35-2' created by Andras Timar  at 
2022-11-23 21:52 +

cp-21.06.35-2

Changes since cp-21.06.13-1-1:
---
 0 files changed
---


[Libreoffice-commits] dictionaries.git: Changes to 'refs/tags/cp-21.06.35-2'

2022-11-23 Thread Andras Timar (via logerrit)
Tag 'cp-21.06.35-2' created by Andras Timar  at 
2022-11-23 21:52 +

cp-21.06.35-2

Changes since libreoffice-7-1-branch-point-5:
---
 0 files changed
---


[Libreoffice-commits] help.git: Changes to 'refs/tags/cp-21.06.35-2'

2022-11-23 Thread Adolfo Jayme Barrientos (via logerrit)
Tag 'cp-21.06.35-2' created by Andras Timar  at 
2022-11-23 21:52 +

cp-21.06.35-2

Changes since co-2021-branch-point-10:
---
 0 files changed
---


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

2022-11-23 Thread Andras Timar (via logerrit)
 configure.ac |2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

New commits:
commit 76e5d30264b2b1408c6ecfd6600ecbaf6f885b5b
Author: Andras Timar 
AuthorDate: Wed Nov 23 22:52:09 2022 +0100
Commit: Andras Timar 
CommitDate: Wed Nov 23 22:52:09 2022 +0100

Bump version to 21.06.35.2

Change-Id: I012a5211b5b6a8f1773a70e651c39ac307e2553d

diff --git a/configure.ac b/configure.ac
index 0709b28fab3a..e82845bcbc83 100644
--- a/configure.ac
+++ b/configure.ac
@@ -9,7 +9,7 @@ dnl in order to create a configure script.
 # several non-alphanumeric characters, those are split off and used only for 
the
 # ABOUTBOXPRODUCTVERSIONSUFFIX in openoffice.lst. Why that is necessary, no 
idea.
 
-AC_INIT([Collabora Office],[21.06.35.1],[],[],[https://collaboraoffice.com/])
+AC_INIT([Collabora Office],[21.06.35.2],[],[],[https://collaboraoffice.com/])
 
 dnl libnumbertext needs autoconf 2.68, but that can pick up autoconf268 just 
fine if it is installed
 dnl whereas aclocal (as run by autogen.sh) insists on using autoconf and fails 
hard


[Libreoffice-bugs] [Bug 152141] Category's Labels don't work

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

raal  changed:

   What|Removed |Added

Version|7.3.2.2 release |4.1.0.4 release

--- Comment #11 from raal  ---
repro Version 4.1.0.0.alpha0+ (Build ID:
efca6f15609322f62a35619619a6d5fe5c9bd5a)

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

[Libreoffice-bugs] [Bug 152141] Category's Labels don't work

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

raal  changed:

   What|Removed |Added

 Ever confirmed|0   |1
 Status|UNCONFIRMED |NEW
   Keywords||filter:xls
Version|unspecified |7.3.2.2 release
 CC||r...@post.cz

--- Comment #10 from raal  ---
I can confirm with Version: 7.5.0.0.alpha0+ (X86_64) / LibreOffice Community
Build ID: 7b23c53232245a1f61c3e8ddff59d049a49fe975
CPU threads: 4; OS: Linux 5.15; UI render: default; VCL: gtk3
Locale: cs-CZ (cs_CZ.UTF-8); UI: en-US
Calc: threaded

I recommend using .ods format.

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

[Libreoffice-bugs] [Bug 151618] Colorbar gradient from an imported SVG is wrongly displayed

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

Rafael Lima  changed:

   What|Removed |Added

   Assignee|rafael.palma.l...@gmail.com |libreoffice-b...@lists.free
   ||desktop.org

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

[Libreoffice-bugs] [Bug 143846] Create separate help pages for each function in the "Text Functions" page

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

Rafael Lima  changed:

   What|Removed |Added

   Assignee|rafael.palma.l...@gmail.com |libreoffice-b...@lists.free
   ||desktop.org

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

[Libreoffice-bugs] [Bug 152190] Libre Impress - Text in tables once created cannot be deleted

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

raal  changed:

   What|Removed |Added

 Ever confirmed|0   |1
 CC||r...@post.cz
 Status|UNCONFIRMED |NEEDINFO

--- Comment #1 from raal  ---
No repro with Version: 7.5.0.0.alpha0+ (X86_64) / LibreOffice Community
Build ID: 7b23c53232245a1f61c3e8ddff59d049a49fe975
CPU threads: 4; OS: Linux 5.15; UI render: default; VCL: gtk3
Locale: cs-CZ (cs_CZ.UTF-8); UI: en-US
Calc: threaded

Please share your file, thank you

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

[Libreoffice-bugs] [Bug 152110] LanguageTool ext. prevents adding words to dictionaries with 2+ dictionaries present

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

--- Comment #2 from Marcin Segit  ---
(In reply to Stéphane Guillou (stragu) from comment #1)
> I tested with up to two extra dictionaries on top of the "standard.dic" one.
> Are your steps different in any way?

The bug is related to LanguageTool extension (v5.9.1 and lower) so you have to
install the extension, not to activate the remote solution:
https://extensions.libreoffice.org/en/extensions/show/languagetool.

LT team is aware of the issue (reported in Oct). In their opinion this is LO
bug and they came up with a workaround for future LT 6.0:
https://github.com/languagetool-org/languagetool/issues/7298.

With the remote solution I'm experiencing yet another issue that words are
added to any dictionary but are not recognized afterwards but this is something
for another bug report.

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

  1   2   3   4   >