[Libreoffice-bugs] [Bug 149036] Missing icon for "Label Field" using Breeze (dark) icon theme

2022-05-25 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=149036

Rizal Muttaqin  changed:

   What|Removed |Added

   Assignee|libreoffice-b...@lists.free |riz...@libreoffice.org
   |desktop.org |

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

[Libreoffice-bugs] [Bug 149036] Missing icon for "Label Field" using Breeze (dark) icon theme

2022-05-25 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=149036

Rizal Muttaqin  changed:

   What|Removed |Added

 Status|UNCONFIRMED |NEW
 Ever confirmed|0   |1

--- Comment #3 from Rizal Muttaqin  ---
Yes the bug is valid and the missing icons are:
breeze*/cmd/lc_insertfixedtext.png
breeze*/cmd/32/insertfixedtext.png

Version: 7.4.0.0.alpha1+ / LibreOffice Community
Build ID: 4bd8b4e469a4084eee0ec467721704ae51f82301
CPU threads: 8; OS: Linux 5.13; UI render: default; VCL: kf5 (cairo+xcb)
Locale: id-ID (id_ID.UTF-8); UI: en-US
Calc: threaded

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

[Libreoffice-bugs] [Bug 144167] exported PNG image has wrong size when page has border

2022-05-25 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=144167

--- Comment #13 from Buovjaga  ---
(In reply to Valerio Messina from comment #12)
> so seems the output image size changed from LO 7.2 to 7.4, and both are
> wrong.
> 
> Do you get the 10 mm page border in the resulting PNG?

I don't understand what you mean, so can't answer. You can test with 7.4
yourself: https://dev-builds.libreoffice.org/daily/master/current.html

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

[Libreoffice-commits] core.git: config_host.mk.in configure.ac solenv/gbuild

2022-05-25 Thread Luboš Luňák (via logerrit)
 config_host.mk.in  |2 -
 configure.ac   |   47 +
 solenv/gbuild/platform/com_GCC_defs.mk |4 +-
 3 files changed, 39 insertions(+), 14 deletions(-)

New commits:
commit d235f705b4dda23cfd7b77c500b166016633e46c
Author: Luboš Luňák 
AuthorDate: Wed May 25 17:07:17 2022 +0200
Commit: Luboš Luňák 
CommitDate: Thu May 26 07:55:50 2022 +0200

use at least assertions mode if libc++ debug mode is not usable

This way at least e.g. std::vector::operator[] will still check
bounds even though things like iterator debugging will not work.

Change-Id: If3c550cfec68eee9a19050fc8e60fca07148b4a4
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/134946
Tested-by: Jenkins
Reviewed-by: Luboš Luňák 

diff --git a/config_host.mk.in b/config_host.mk.in
index 9a2cd1343a18..019e1a65561b 100644
--- a/config_host.mk.in
+++ b/config_host.mk.in
@@ -306,7 +306,6 @@ export HAVE_GNUMAKE_FILE_FUNC=@HAVE_GNUMAKE_FILE_FUNC@
 export HAVE_LD_BSYMBOLIC_FUNCTIONS=@HAVE_LD_BSYMBOLIC_FUNCTIONS@
 export HAVE_LD_HASH_STYLE=@HAVE_LD_HASH_STYLE@
 export HAVE_LIBCPP=@HAVE_LIBCPP@
-export HAVE_LIBCPP_DEBUG=@HAVE_LIBCPP_DEBUG@
 export HAVE_LIBSTDCPP=@HAVE_LIBSTDCPP@
 export HAVE_POSIX_FALLOCATE=@HAVE_POSIX_FALLOCATE@
 export HAVE_WDEPRECATED_COPY_DTOR=@HAVE_WDEPRECATED_COPY_DTOR@
@@ -371,6 +370,7 @@ export LFS_CFLAGS=@LFS_CFLAGS@
 export LIBASSUAN_CFLAGS=$(gb_SPACE)@LIBASSUAN_CFLAGS@
 export LIBASSUAN_LIBS=$(gb_SPACE)@LIBASSUAN_LIBS@
 export LIBBASE_JAR=@LIBBASE_JAR@
+export LIBCPP_DEBUG=@LIBCPP_DEBUG@
 export LIBDIR=@LIBDIR@
 export LIBEOT_CFLAGS=$(gb_SPACE)@LIBEOT_CFLAGS@
 export LIBEOT_LIBS=$(gb_SPACE)@LIBEOT_LIBS@
diff --git a/configure.ac b/configure.ac
index bd9a1c3f8be6..d4cbd2410e0f 100644
--- a/configure.ac
+++ b/configure.ac
@@ -7423,33 +7423,58 @@ AC_LANG_POP([C++])
 AC_SUBST([HAVE_LIBSTDCPP])
 AC_SUBST([HAVE_LIBCPP])
 
-HAVE_LIBCPP_DEBUG=
+LIBCPP_DEBUG=
 if test -z "$CROSS_COMPILING" -a -n "$HAVE_LIBCPP" -a -n "$ENABLE_DBGUTIL"; 
then
-# Libc++ supports debug mode only if built for it, Mac libc++ isn't,
+# Libc++ has two levels of debug mode, assertions mode enabled with 
-D_LIBCPP_DEBUG=0,
+# and actual debug mode enabled with -D_LIBCPP_DEBUG=1 (and starting with 
LLVM15
+# assertions mode will be separate and controlled by 
-D_LIBCPP_ENABLE_ASSERTIONS=1,
+# although there will be backwards compatibility).
+# Debug mode is supported by libc++ only if built for it, e.g. Mac libc++ 
isn't,
 # and there would be undefined references to debug functions.
 # Moreover std::to_string() has a bug (https://reviews.llvm.org/D125184).
+# So check if debug mode can be used and disable or downgrade it to 
assertions
+# if needed.
 AC_MSG_CHECKING([if libc++ has a usable debug mode])
 AC_LANG_PUSH([C++])
-AC_RUN_IFELSE([AC_LANG_SOURCE([[
-#define _LIBCPP_DEBUG 1
+libcpp_debug_links=
+AC_LINK_IFELSE([AC_LANG_SOURCE([[
+#define _LIBCPP_DEBUG 0 // only assertions
+#include 
+int main()
+{
+std::vector v;
+v.push_back( 1 );
+return v[ 3 ];
+}
+]])], [libcpp_debug_links=1])
+if test -n "$libcpp_debug_links"; then
+# we can use at least assertions, check if debug mode works
+AC_RUN_IFELSE([AC_LANG_SOURCE([[
+#define _LIBCPP_DEBUG 1 // debug mode
 #include 
 #include 
 int foo(const std::vector& v) { return *v.begin(); }
 int main()
 {
-std::vector v{ 1, 2 };
+std::vector v;
+v.push_back( 1 );
 std::string s = "x" + std::to_string(10);
 return (foo(v) + s.size()) != 0 ? 0 : 1;
 }
 ]])],
-[AC_MSG_RESULT(yes)
- HAVE_LIBCPP_DEBUG=1
-],
-[AC_MSG_RESULT(no)]
-)
+[AC_MSG_RESULT(yes)
+ LIBCPP_DEBUG=-D_LIBCPP_DEBUG=1
+],
+[AC_MSG_RESULT(no, using only assertions)
+ LIBCPP_DEBUG=-D_LIBCPP_DEBUG=0
+]
+)
+else
+AC_MSG_RESULT(no)
+fi
 AC_LANG_POP([C++])
 fi
-AC_SUBST([HAVE_LIBCPP_DEBUG])
+AC_SUBST([LIBCPP_DEBUG])
 
 dnl ===
 dnl Check for gperf
diff --git a/solenv/gbuild/platform/com_GCC_defs.mk 
b/solenv/gbuild/platform/com_GCC_defs.mk
index c2db27243457..f16eb8ec282c 100644
--- a/solenv/gbuild/platform/com_GCC_defs.mk
+++ b/solenv/gbuild/platform/com_GCC_defs.mk
@@ -54,8 +54,8 @@ ifeq ($(gb_ENABLE_DBGUTIL),$(true))
 ifneq ($(HAVE_LIBSTDCPP),)
 gb_COMPILERDEFS_STDLIB_DEBUG = -D_GLIBCXX_DEBUG
 else
-ifneq ($(HAVE_LIBCPP_DEBUG),)
-gb_COMPILERDEFS_STDLIB_DEBUG = -D_LIBCPP_DEBUG=1
+ifneq ($(LIBCPP_DEBUG),)
+gb_COMPILERDEFS_STDLIB_DEBUG = $(LIBCPP_DEBUG)
 endif
 endif
 gb_COMPILERDEFS += $(gb_COMPILERDEFS_STDLIB_DEBUG)


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

2022-05-25 Thread Siddhant Chaudhary (via logerrit)
 sc/qa/unit/cond_format_merge.cxx |2 --
 1 file changed, 2 deletions(-)

New commits:
commit 43f6ca7164a9ea7c99d177d711684e25d53e8be4
Author: Siddhant Chaudhary 
AuthorDate: Thu May 26 03:34:18 2022 +0530
Commit: Hossein 
CommitDate: Thu May 26 07:51:41 2022 +0200

tdf#139734 Drop redundant asserts after MacrosTest::loadFromDesktop

Removed a redundant assert on returned value of 
`MacrosTest::loadFromDesktop`.

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

diff --git a/sc/qa/unit/cond_format_merge.cxx b/sc/qa/unit/cond_format_merge.cxx
index 56b47ac7c1a4..01cbde7359a6 100644
--- a/sc/qa/unit/cond_format_merge.cxx
+++ b/sc/qa/unit/cond_format_merge.cxx
@@ -45,8 +45,6 @@ void ScCondFormatMergeTest::testCondFormatMerge()
 createFileURL(u"cond_format_merge.ods", aFileURL);
 uno::Reference mxComponent = loadFromDesktop(aFileURL);
 
-CPPUNIT_ASSERT_MESSAGE("Component not loaded", mxComponent.is());
-
 // get the first sheet
 uno::Reference xDoc(mxComponent, 
uno::UNO_QUERY_THROW);
 uno::Reference xIndex(xDoc->getSheets(), 
uno::UNO_QUERY_THROW);


[Libreoffice-bugs] [Bug 139734] Drop redundant asserts after MacrosTest::loadFromDesktop

2022-05-25 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=139734

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

https://git.libreoffice.org/core/commit/43f6ca7164a9ea7c99d177d711684e25d53e8be4

tdf#139734 Drop redundant asserts after MacrosTest::loadFromDesktop

It will be available in 7.4.0.

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

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

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

[Libreoffice-bugs] [Bug 148755] A Quirk in the focusing property of the Navigator

2022-05-25 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=148755

--- Comment #11 from Dieter  ---
(In reply to Dieter from comment #8)
> I will file a bug report.

Bug 149301

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

[Libreoffice-bugs] [Bug 149301] HELP for Navigator: Change "Content View" to "Content Management View"

2022-05-25 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=149301

--- Comment #1 from Dieter  ---
Please take also into accont bug 178755 comment 10

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

[Libreoffice-commits] core.git: icon-themes/breeze icon-themes/breeze_dark icon-themes/breeze_dark_svg icon-themes/breeze_svg icon-themes/sifr icon-themes/sifr_dark icon-themes/sifr_dark_svg icon-them

2022-05-25 Thread Rizal Muttaqin (via logerrit)
 icon-themes/breeze/svx/res/symphony/line1.png   |binary
 icon-themes/breeze/svx/res/symphony/line10.png  |binary
 icon-themes/breeze/svx/res/symphony/line2.png   |binary
 icon-themes/breeze/svx/res/symphony/line3.png   |binary
 icon-themes/breeze/svx/res/symphony/line4.png   |binary
 icon-themes/breeze/svx/res/symphony/line5.png   |binary
 icon-themes/breeze/svx/res/symphony/line6.png   |binary
 icon-themes/breeze/svx/res/symphony/line7.png   |binary
 icon-themes/breeze/svx/res/symphony/line8.png   |binary
 icon-themes/breeze/svx/res/symphony/line9.png   |binary
 icon-themes/breeze_dark/svx/res/symphony/line1.png  |binary
 icon-themes/breeze_dark/svx/res/symphony/line10.png |binary
 icon-themes/breeze_dark/svx/res/symphony/line2.png  |binary
 icon-themes/breeze_dark/svx/res/symphony/line3.png  |binary
 icon-themes/breeze_dark/svx/res/symphony/line4.png  |binary
 icon-themes/breeze_dark/svx/res/symphony/line5.png  |binary
 icon-themes/breeze_dark/svx/res/symphony/line6.png  |binary
 icon-themes/breeze_dark/svx/res/symphony/line7.png  |binary
 icon-themes/breeze_dark/svx/res/symphony/line8.png  |binary
 icon-themes/breeze_dark/svx/res/symphony/line9.png  |binary
 icon-themes/breeze_dark_svg/svx/res/symphony/line1.svg  |1 +
 icon-themes/breeze_dark_svg/svx/res/symphony/line10.svg |1 +
 icon-themes/breeze_dark_svg/svx/res/symphony/line2.svg  |1 +
 icon-themes/breeze_dark_svg/svx/res/symphony/line3.svg  |1 +
 icon-themes/breeze_dark_svg/svx/res/symphony/line4.svg  |1 +
 icon-themes/breeze_dark_svg/svx/res/symphony/line5.svg  |1 +
 icon-themes/breeze_dark_svg/svx/res/symphony/line6.svg  |1 +
 icon-themes/breeze_dark_svg/svx/res/symphony/line7.svg  |1 +
 icon-themes/breeze_dark_svg/svx/res/symphony/line8.svg  |1 +
 icon-themes/breeze_dark_svg/svx/res/symphony/line9.svg  |1 +
 icon-themes/breeze_svg/svx/res/symphony/line1.svg   |1 +
 icon-themes/breeze_svg/svx/res/symphony/line10.svg  |1 +
 icon-themes/breeze_svg/svx/res/symphony/line2.svg   |1 +
 icon-themes/breeze_svg/svx/res/symphony/line3.svg   |1 +
 icon-themes/breeze_svg/svx/res/symphony/line4.svg   |1 +
 icon-themes/breeze_svg/svx/res/symphony/line5.svg   |1 +
 icon-themes/breeze_svg/svx/res/symphony/line6.svg   |1 +
 icon-themes/breeze_svg/svx/res/symphony/line7.svg   |1 +
 icon-themes/breeze_svg/svx/res/symphony/line8.svg   |1 +
 icon-themes/breeze_svg/svx/res/symphony/line9.svg   |1 +
 icon-themes/sifr/svx/res/symphony/line1.png |binary
 icon-themes/sifr/svx/res/symphony/line10.png|binary
 icon-themes/sifr/svx/res/symphony/line2.png |binary
 icon-themes/sifr/svx/res/symphony/line3.png |binary
 icon-themes/sifr/svx/res/symphony/line4.png |binary
 icon-themes/sifr/svx/res/symphony/line5.png |binary
 icon-themes/sifr/svx/res/symphony/line6.png |binary
 icon-themes/sifr/svx/res/symphony/line7.png |binary
 icon-themes/sifr/svx/res/symphony/line8.png |binary
 icon-themes/sifr/svx/res/symphony/line9.png |binary
 icon-themes/sifr_dark/svx/res/symphony/line1.png|binary
 icon-themes/sifr_dark/svx/res/symphony/line10.png   |binary
 icon-themes/sifr_dark/svx/res/symphony/line2.png|binary
 icon-themes/sifr_dark/svx/res/symphony/line3.png|binary
 icon-themes/sifr_dark/svx/res/symphony/line4.png|binary
 icon-themes/sifr_dark/svx/res/symphony/line5.png|binary
 icon-themes/sifr_dark/svx/res/symphony/line6.png|binary
 icon-themes/sifr_dark/svx/res/symphony/line7.png|binary
 icon-themes/sifr_dark/svx/res/symphony/line8.png|binary
 icon-themes/sifr_dark/svx/res/symphony/line9.png|binary
 icon-themes/sifr_dark_svg/svx/res/symphony/line1.svg|1 +
 icon-themes/sifr_dark_svg/svx/res/symphony/line10.svg   |1 +
 icon-themes/sifr_dark_svg/svx/res/symphony/line2.svg|1 +
 icon-themes/sifr_dark_svg/svx/res/symphony/line3.svg|1 +
 icon-themes/sifr_dark_svg/svx/res/symphony/line4.svg|1 +
 icon-themes/sifr_dark_svg/svx/res/symphony/line5.svg|1 +
 icon-themes/sifr_dark_svg/svx/res/symphony/line6.svg|1 +
 icon-themes/sifr_dark_svg/svx/res/symphony/line7.svg|1 +
 icon-themes/sifr_dark_svg/svx/res/symphony/line8.svg|1 +
 icon-themes/sifr_dark_svg/svx/res/symphony/line9.svg|1 +
 icon-themes/sifr_svg/svx/res/symphony/line1.svg |1 +
 icon-themes/sifr_svg/svx/res/symphony/line10.svg|1 +
 icon-themes/sifr_svg/svx/res/symphony/line2.svg |1 +
 icon-themes/sifr_svg/svx/res/symphony/line3.svg |1 +
 icon-themes/sifr_svg/svx/res/symphony/line4.svg |1 +
 icon-themes/sifr_svg/svx/res/symphony/line5.svg |1 +
 

[Libreoffice-bugs] [Bug 136916] Underline menu lines not visible in dark mode

2022-05-25 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=136916

Rizal Muttaqin  changed:

   What|Removed |Added

   Assignee|libreoffice-b...@lists.free |riz...@libreoffice.org
   |desktop.org |

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

[Libreoffice-bugs] [Bug 120200] [META] Update or correct help for features

2022-05-25 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=120200

Dieter  changed:

   What|Removed |Added

 Depends on||149301


Referenced Bugs:

https://bugs.documentfoundation.org/show_bug.cgi?id=149301
[Bug 149301] HELP for Navigator: Change "Content View" to "Content Management
View"
-- 
You are receiving this mail because:
You are the assignee for the bug.

[Libreoffice-bugs] [Bug 149301] HELP for Navigator: Change "Content View" to "Content Management View"

2022-05-25 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=149301

Dieter  changed:

   What|Removed |Added

 Blocks||120200


Referenced Bugs:

https://bugs.documentfoundation.org/show_bug.cgi?id=120200
[Bug 120200] [META] Update or correct help for features
-- 
You are receiving this mail because:
You are the assignee for the bug.

[Libreoffice-bugs] [Bug 149301] New: HELP for Navigator: Change "Content View" to "Content Management View"

2022-05-25 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=149301

Bug ID: 149301
   Summary: HELP for Navigator: Change "Content View" to "Content
Management View"
   Product: LibreOffice
   Version: unspecified
  Hardware: All
OS: All
Status: UNCONFIRMED
  Severity: normal
  Priority: medium
 Component: Documentation
  Assignee: libreoffice-bugs@lists.freedesktop.org
  Reporter: dgp-m...@gmx.de
CC: olivier.hal...@libreoffice.org

Follow up from bug 148755

Since LO 5.2 tooltip "Content View" is "Content Management View". Function of
this button is not self-explaining. But if you search in LO help with "Content
Management View" you get zero results, because name in help is still "Content
View" This should be changed in the following pages of LO help:


https://help.libreoffice.org/7.3/en-GB/text/swriter/01/0211.html?=Writer=WIN

https://help.libreoffice.org/7.3/en-GB/text/scalc/01/0211.html?=WRITER=WIN

https://help.libreoffice.org/7.3/en-GB/text/shared/guide/navigator.html?=WRITER=WIN

https://help.libreoffice.org/7.3/en-GB/text/swriter/guide/arrange_chapters.html?=WRITER=WIN

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

[Libreoffice-bugs] [Bug 149300] unexpected extra spaces inserted. sometimes to page margin, sometimes beyond visible, and in full-screen mode, when clicking in open space at end of paragraph

2022-05-25 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=149300

Gordon Patnude  changed:

   What|Removed |Added

 CC||gppatn...@comcast.net

--- Comment #1 from Gordon Patnude  ---
Created attachment 180392
  --> https://bugs.documentfoundation.org/attachment.cgi?id=180392=edit
File I was working in, but problem not limited to this file.

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

[Libreoffice-bugs] [Bug 146535] Mouse line goes missing when changing paragraph style

2022-05-25 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=146535

Greasya  changed:

   What|Removed |Added

  Component|LibreOffice |Writer

--- Comment #3 from Greasya  ---
Version: 7.3.0.3 / LibreOffice Community
Build ID: 0f246aa12d0eee4a0f7adcefbf7c878fc2238db3
CPU threads: 4; OS: Linux 5.4; UI render: default; VCL: gtk3
Locale: en-IN (en_IN); UI: en-US
Calc: CL


Step to reproduce:

1. open Libreoffice writer
2. Type few line of paragraph
3.change paragraph style
4. create another paragraph


Actual result:

In above version Libreoffice writer working.

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

[Libreoffice-bugs] [Bug 149288] Hide empty headings in the Navigator

2022-05-25 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=149288

Dieter  changed:

   What|Removed |Added

 CC||dgp-m...@gmx.de

--- Comment #3 from Dieter  ---
I confirm the behaviour. It is not related to docx-files. You can find it also
in every odt-file. I like it, because it gives you a very quick hint of wrong
formatting or layout in the document or superfluous paragraphs. Normally
headings have a different formatting than default style in a document (bold,
diffenret font size, paragraph spacing, ...) and so you can correct it very
fast.

For me clearly NAB.

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

[Libreoffice-bugs] [Bug 149264] assert in checkGlyphsEqual() when loading sw/qa/extras/uiwriter/data/tdf104649.docx

2022-05-25 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=149264

Luboš Luňák  changed:

   What|Removed |Added

 Resolution|--- |FIXED
 Status|UNCONFIRMED |RESOLVED

--- Comment #8 from Luboš Luňák  ---
I expect this should work now.

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

[Libreoffice-bugs] [Bug 149264] assert in checkGlyphsEqual() when loading sw/qa/extras/uiwriter/data/tdf104649.docx

2022-05-25 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=149264

--- Comment #7 from Commit Notification 
 ---
Luboš Luňák committed a patch related to this issue.
It has been pushed to "master":

https://git.libreoffice.org/core/commit/755ed6f5f062afecb157f06e6a3132873ca7b23f

do not use glyph subsets if LTR/RTL does not match (tdf#149264)

It will be available in 7.4.0.

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

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

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

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

2022-05-25 Thread Luboš Luňák (via logerrit)
 vcl/qa/cppunit/complextext.cxx |   58 -
 1 file changed, 52 insertions(+), 6 deletions(-)

New commits:
commit cb22a3f6f588323d7353990b5280f01df6e85997
Author: Luboš Luňák 
AuthorDate: Wed May 25 12:54:11 2022 +0200
Commit: Luboš Luňák 
CommitDate: Thu May 26 07:09:04 2022 +0200

unittest for SalLayoutGlyphsCache glyphs subset

Change-Id: I341871c65e63f37ffc3507daaefe035f6762e62b
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/134956
Tested-by: Jenkins
Reviewed-by: Luboš Luňák 

diff --git a/vcl/qa/cppunit/complextext.cxx b/vcl/qa/cppunit/complextext.cxx
index 6a37ed1713ad..3bf69cd3a8d4 100644
--- a/vcl/qa/cppunit/complextext.cxx
+++ b/vcl/qa/cppunit/complextext.cxx
@@ -52,12 +52,14 @@ public:
 void testKashida();
 void testTdf95650(); // Windows-only issue
 void testCaching();
+void testCachingSubstring();
 
 CPPUNIT_TEST_SUITE(VclComplexTextTest);
 CPPUNIT_TEST(testArabic);
 CPPUNIT_TEST(testKashida);
 CPPUNIT_TEST(testTdf95650);
 CPPUNIT_TEST(testCaching);
+CPPUNIT_TEST(testCachingSubstring);
 CPPUNIT_TEST_SUITE_END();
 };
 
@@ -187,15 +189,12 @@ static void checkCompareGlyphs( const SalLayoutGlyphs& 
aGlyphs1, const SalLayout
 }
 }
 
-static void testCachedGlyphs( const OUString& aText, const OUString& aFontName 
= OUString())
+static void testCachedGlyphs( const OUString& aText, const OUString& aFontName 
)
 {
 const std::string message = OUString("Font: " + aFontName + ", text: '" + 
aText + "'").toUtf8().getStr();
 ScopedVclPtrInstance pOutputDevice;
-if(!aFontName.isEmpty())
-{
-vcl::Font aFont( aFontName, Size(0, 12));
-pOutputDevice->SetFont( aFont );
-}
+vcl::Font aFont( aFontName, Size(0, 12));
+pOutputDevice->SetFont( aFont );
 SalLayoutGlyphsCache::self()->clear();
 // Get the glyphs for the text.
 std::unique_ptr pLayout1 = pOutputDevice->ImplLayout(
@@ -223,6 +222,53 @@ void VclComplexTextTest::testCaching()
 testCachedGlyphs( "test", "KacstBook" );
 }
 
+static void testCachedGlyphsSubstring( const OUString& aText, const OUString& 
aFontName, bool rtl )
+{
+const std::string prefix = OUString("Font: " + aFontName + ", text: '" + 
aText + "'").toUtf8().getStr();
+ScopedVclPtrInstance pOutputDevice;
+// BiDiStrong is needed, otherwise SalLayoutGlyphsImpl::cloneCharRange() 
will not do anything.
+vcl::text::ComplexTextLayoutFlags layoutFlags = 
vcl::text::ComplexTextLayoutFlags::BiDiStrong;
+if(rtl)
+layoutFlags |= vcl::text::ComplexTextLayoutFlags::BiDiRtl;
+pOutputDevice->SetLayoutMode( layoutFlags );
+vcl::Font aFont( aFontName, Size(0, 12));
+pOutputDevice->SetFont( aFont );
+SalLayoutGlyphsCache::self()->clear();
+// Get the glyphs for the entire text once, to ensure the cache can built 
subsets from it.
+pOutputDevice->ImplLayout( aText, 0, aText.getLength(), Point(0, 0), 0, 
{}, SalLayoutFlags::GlyphItemsOnly);
+// Now check for all subsets. Some of them possibly do not make sense in 
practice, but the code
+// should cope with them.
+for( sal_Int32 len = 1; len <= aText.getLength(); ++len )
+for( sal_Int32 pos = 0; pos < aText.getLength() - len; ++pos )
+{
+std::string message = prefix + " (" + std::to_string(pos) + "/" + 
std::to_string(len) + ")";
+std::unique_ptr pLayout1 = pOutputDevice->ImplLayout(
+aText, pos, len, Point(0, 0), 0, {}, 
SalLayoutFlags::GlyphItemsOnly);
+SalLayoutGlyphs aGlyphs1 = pLayout1->GetGlyphs();
+const SalLayoutGlyphs* aGlyphs2 = 
SalLayoutGlyphsCache::self()->GetLayoutGlyphs(
+pOutputDevice, aText, pos, len, 0);
+CPPUNIT_ASSERT_MESSAGE(message, aGlyphs2 != nullptr);
+checkCompareGlyphs(aGlyphs1, *aGlyphs2, message);
+}
+
+}
+
+// Check that SalLayoutGlyphsCache works properly when it builds a subset
+// of glyphs using SalLayoutGlyphsImpl::cloneCharRange().
+// This should preferably use fonts that come with LO.
+void VclComplexTextTest::testCachingSubstring()
+{
+// Just something basic.
+testCachedGlyphsSubstring( "test", "Dejavu Sans", false );
+// And complex arabic text, taken from tdf104649.docx .
+OUString text(u"فصل (پاره 2): درخواست حاجت از ديگران و برآوردن حاجت ديگران 
90");
+testCachedGlyphsSubstring( text, "Dejavu Sans", true );
+// The text is RTL, but Writer will sometimes try to lay it out as LTR, 
for whatever reason
+// (tdf#149264)./ So make sure that gets handled properly too 
(SalLayoutGlyphsCache should
+// not use glyph subsets in that case).
+testCachedGlyphsSubstring( text, "Dejavu Sans", false );
+}
+
 CPPUNIT_TEST_SUITE_REGISTRATION(VclComplexTextTest);
 
 /* vim:set shiftwidth=4 softtabstop=4 expandtab: */


[Libreoffice-bugs] [Bug 149264] assert in checkGlyphsEqual() when loading sw/qa/extras/uiwriter/data/tdf104649.docx

2022-05-25 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=149264

Commit Notification  changed:

   What|Removed |Added

 Whiteboard||target:7.4.0

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

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

2022-05-25 Thread Luboš Luňák (via logerrit)
 vcl/source/gdi/impglyphitem.cxx |   45 +++-
 1 file changed, 44 insertions(+), 1 deletion(-)

New commits:
commit 755ed6f5f062afecb157f06e6a3132873ca7b23f
Author: Luboš Luňák 
AuthorDate: Wed May 25 18:29:42 2022 +0200
Commit: Luboš Luňák 
CommitDate: Thu May 26 07:08:47 2022 +0200

do not use glyph subsets if LTR/RTL does not match (tdf#149264)

Writer apparently sometimes asks to lay out RTL text as LTR,
for whatever reason, and Harfbuzz in that case does not give
consistent results usable for creating subsets of glyphs (or maybe
HB_GLYPH_FLAG_UNSAFE_TO_BREAK is not reliable in that case).
I don't quite understand what the problem here is, but avoid
it by checking whether the text is LTR or RTL and simply do
not try to create a subset from the glyphs if the text does
not match the way it was asked to be laid out. I don't even
know if this is correct handling or just a workaround for something.

Change-Id: Ic77db04f529c9ca2c194893a2127e85953accf32
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/134950
Tested-by: Jenkins
Reviewed-by: Luboš Luňák 

diff --git a/vcl/source/gdi/impglyphitem.cxx b/vcl/source/gdi/impglyphitem.cxx
index bdedb263778e..39c01699ea4e 100644
--- a/vcl/source/gdi/impglyphitem.cxx
+++ b/vcl/source/gdi/impglyphitem.cxx
@@ -26,6 +26,9 @@
 #include 
 #include 
 
+#include 
+#include 
+
 // These need being explicit because of SalLayoutGlyphsImpl being private in 
vcl.
 SalLayoutGlyphs::SalLayoutGlyphs() {}
 
@@ -236,16 +239,56 @@ SalLayoutGlyphsCache* SalLayoutGlyphsCache::self()
 return cache.get();
 }
 
+static UBiDiDirection getBiDiDirection(const OUString& text, sal_Int32 index, 
sal_Int32 len)
+{
+// Return whether all character are LTR, RTL, neutral or whether it's 
mixed.
+// This is sort of ubidi_getBaseDirection() and ubidi_getDirection(),
+// but it's meant to be fast but also check all characters.
+sal_Int32 end = index + len;
+UBiDiDirection direction = UBIDI_NEUTRAL;
+while (index < end)
+{
+switch (u_charDirection(text.iterateCodePoints()))
+{
+// Only characters with strong direction.
+case U_LEFT_TO_RIGHT:
+if (direction == UBIDI_RTL)
+return UBIDI_MIXED;
+direction = UBIDI_LTR;
+break;
+case U_RIGHT_TO_LEFT:
+case U_RIGHT_TO_LEFT_ARABIC:
+if (direction == UBIDI_LTR)
+return UBIDI_MIXED;
+direction = UBIDI_RTL;
+break;
+default:
+break;
+}
+}
+return direction;
+}
+
 static SalLayoutGlyphs makeGlyphsSubset(const SalLayoutGlyphs& source,
-const OutputDevice* outputDevice, 
std::u16string_view text,
+const OutputDevice* outputDevice, 
const OUString& text,
 sal_Int32 index, sal_Int32 len)
 {
+// tdf#149264: We need to check if the text is LTR, RTL or mixed. 
Apparently
+// harfbuzz doesn't give reproducible results (or possibly 
HB_GLYPH_FLAG_UNSAFE_TO_BREAK
+// is not reliable?) when asked to lay out RTL text as LTR. So require 
that the whole
+// subset ir either LTR or RTL.
+UBiDiDirection direction = getBiDiDirection(text, index, len);
+if (direction == UBIDI_MIXED)
+return SalLayoutGlyphs();
 SalLayoutGlyphs ret;
 for (int level = 0;; ++level)
 {
 const SalLayoutGlyphsImpl* sourceLevel = source.Impl(level);
 if (sourceLevel == nullptr)
 break;
+bool sourceRtl = bool(sourceLevel->GetFlags() & 
SalLayoutFlags::BiDiRtl);
+if ((direction == UBIDI_LTR && sourceRtl) || (direction == UBIDI_RTL 
&& !sourceRtl))
+return SalLayoutGlyphs();
 SalLayoutGlyphsImpl* cloned = sourceLevel->cloneCharRange(index, len);
 // If the glyphs range cannot be cloned, bail out.
 if (cloned == nullptr)


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

2022-05-25 Thread Luboš Luňák (via logerrit)
 vcl/qa/cppunit/complextext.cxx |   45 ++---
 1 file changed, 29 insertions(+), 16 deletions(-)

New commits:
commit 13762c1ec222b6235bbef39eed9bb1037e082a1e
Author: Luboš Luňák 
AuthorDate: Wed May 25 12:14:12 2022 +0200
Commit: Luboš Luňák 
CommitDate: Thu May 26 07:08:16 2022 +0200

test also SalLayoutGlyphsCache in glyphs caching unittest

Change-Id: Ic0e5ea44525e7cf76a6de1f64f77b943b8347dfc
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/134948
Tested-by: Jenkins
Reviewed-by: Luboš Luňák 

diff --git a/vcl/qa/cppunit/complextext.cxx b/vcl/qa/cppunit/complextext.cxx
index aaea5785c2c4..6a37ed1713ad 100644
--- a/vcl/qa/cppunit/complextext.cxx
+++ b/vcl/qa/cppunit/complextext.cxx
@@ -13,6 +13,7 @@
 #include 
 #include 
 #include 
+#include 
 
 #if HAVE_MORE_FONTS
 // must be declared before inclusion of test/bootstrapfixture.hxx
@@ -160,23 +161,9 @@ void VclComplexTextTest::testTdf95650()
 pOutDev->ImplLayout(aTxt, 9, 1, Point(), 0, {}, SalLayoutFlags::BiDiRtl);
 }
 
-static void testCachedGlyphs( const OUString& aText, const OUString& aFontName 
= OUString())
+static void checkCompareGlyphs( const SalLayoutGlyphs& aGlyphs1, const 
SalLayoutGlyphs& aGlyphs2,
+const std::string& message )
 {
-const std::string message = OUString("Font: " + aFontName + ", text: '" + 
aText + "'").toUtf8().getStr();
-ScopedVclPtrInstance pOutputDevice;
-if(!aFontName.isEmpty())
-{
-vcl::Font aFont( aFontName, Size(0, 12));
-pOutputDevice->SetFont( aFont );
-}
-// Get the glyphs for the text.
-std::unique_ptr pLayout1 = pOutputDevice->ImplLayout(
-aText, 0, aText.getLength(), Point(0, 0), 0, {}, 
SalLayoutFlags::GlyphItemsOnly);
-SalLayoutGlyphs aGlyphs1 = pLayout1->GetGlyphs();
-// Reuse the cached glyphs to get glyphs again.
-std::unique_ptr pLayout2 = pOutputDevice->ImplLayout(
-aText, 0, aText.getLength(), Point(0, 0), 0, {}, 
SalLayoutFlags::GlyphItemsOnly, nullptr, );
-SalLayoutGlyphs aGlyphs2 = pLayout2->GetGlyphs();
 CPPUNIT_ASSERT_EQUAL_MESSAGE(message, aGlyphs1.IsValid(), 
aGlyphs2.IsValid());
 // And check it's the same.
 for( int level = 0; level < MAX_FALLBACK; ++level )
@@ -200,6 +187,32 @@ static void testCachedGlyphs( const OUString& aText, const 
OUString& aFontName =
 }
 }
 
+static void testCachedGlyphs( const OUString& aText, const OUString& aFontName 
= OUString())
+{
+const std::string message = OUString("Font: " + aFontName + ", text: '" + 
aText + "'").toUtf8().getStr();
+ScopedVclPtrInstance pOutputDevice;
+if(!aFontName.isEmpty())
+{
+vcl::Font aFont( aFontName, Size(0, 12));
+pOutputDevice->SetFont( aFont );
+}
+SalLayoutGlyphsCache::self()->clear();
+// Get the glyphs for the text.
+std::unique_ptr pLayout1 = pOutputDevice->ImplLayout(
+aText, 0, aText.getLength(), Point(0, 0), 0, {}, 
SalLayoutFlags::GlyphItemsOnly);
+SalLayoutGlyphs aGlyphs1 = pLayout1->GetGlyphs();
+// Reuse the cached glyphs to get glyphs again.
+std::unique_ptr pLayout2 = pOutputDevice->ImplLayout(
+aText, 0, aText.getLength(), Point(0, 0), 0, {}, 
SalLayoutFlags::GlyphItemsOnly, nullptr, );
+SalLayoutGlyphs aGlyphs2 = pLayout2->GetGlyphs();
+checkCompareGlyphs(aGlyphs1, aGlyphs2, message + " (reuse)");
+// Get cached glyphs from SalLayoutGlyphsCache.
+const SalLayoutGlyphs* aGlyphs3 = 
SalLayoutGlyphsCache::self()->GetLayoutGlyphs(
+pOutputDevice, aText, 0, aText.getLength(), 0);
+CPPUNIT_ASSERT_MESSAGE(message, aGlyphs3 != nullptr);
+checkCompareGlyphs(aGlyphs1, *aGlyphs3, message + " (cache)");
+}
+
 // Check that caching using SalLayoutGlyphs gives same results as without 
caching.
 // This should preferably use fonts that come with LO.
 void VclComplexTextTest::testCaching()


[Libreoffice-commits] core.git: vcl/inc vcl/qa

2022-05-25 Thread Luboš Luňák (via logerrit)
 vcl/inc/impglyphitem.hxx   |2 --
 vcl/qa/cppunit/complextext.cxx |5 ++---
 2 files changed, 2 insertions(+), 5 deletions(-)

New commits:
commit 28a8746ad86907491b428f5fac7e1be4f5bfcf2c
Author: Luboš Luňák 
AuthorDate: Wed May 25 12:12:32 2022 +0200
Commit: Luboš Luňák 
CommitDate: Thu May 26 07:07:41 2022 +0200

check GlyphItem equality properly in a unittest

I.e. use the existing operator==. I don't feel like writing
operator<< for it just for one unittest though.

Change-Id: I63181765a4987a5d6efedc74a1e20d56a70eaa83
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/134947
Tested-by: Jenkins
Reviewed-by: Luboš Luňák 

diff --git a/vcl/inc/impglyphitem.hxx b/vcl/inc/impglyphitem.hxx
index 7c3aa88849df..ea3b2f391334 100644
--- a/vcl/inc/impglyphitem.hxx
+++ b/vcl/inc/impglyphitem.hxx
@@ -104,7 +104,6 @@ public:
 void setLinearPos(const DevicePoint& point) { m_aLinearPos = point; }
 void setLinearPosX(double x) { m_aLinearPos.setX(x); }
 void adjustLinearPosX(double diff) { m_aLinearPos.adjustX(diff); }
-#ifdef DBG_UTIL
 bool operator==(const GlyphItem& other) const
 {
 return m_aLinearPos == other.m_aLinearPos && m_nOrigWidth == 
other.m_nOrigWidth
@@ -114,7 +113,6 @@ public:
&& m_nFlags == other.m_nFlags;
 }
 bool operator!=(const GlyphItem& other) const { return !(*this == other); }
-#endif
 };
 
 bool GlyphItem::GetGlyphBoundRect(const LogicalFontInstance* pFontInstance,
diff --git a/vcl/qa/cppunit/complextext.cxx b/vcl/qa/cppunit/complextext.cxx
index 1aed3fe7ba20..aaea5785c2c4 100644
--- a/vcl/qa/cppunit/complextext.cxx
+++ b/vcl/qa/cppunit/complextext.cxx
@@ -194,9 +194,8 @@ static void testCachedGlyphs( const OUString& aText, const 
OUString& aFontName =
 CPPUNIT_ASSERT_EQUAL_MESSAGE(messageLevel, g1->size(), g2->size());
 for( size_t i = 0; i < g1->size(); ++i )
 {
-CPPUNIT_ASSERT_EQUAL_MESSAGE(messageLevel, (*g1)[i].glyphId(), 
(*g2)[i].glyphId());
-CPPUNIT_ASSERT_EQUAL_MESSAGE(messageLevel, (*g1)[i].IsRTLGlyph(), 
(*g2)[i].IsRTLGlyph());
-CPPUNIT_ASSERT_EQUAL_MESSAGE(messageLevel, (*g1)[i].IsVertical(), 
(*g2)[i].IsVertical());
+const bool equal = (*g1)[i] == (*g2)[i];
+CPPUNIT_ASSERT_MESSAGE(messageLevel, equal);
 }
 }
 }


[Libreoffice-bugs] [Bug 149300] New: unexpected extra spaces inserted. sometimes to page margin, sometimes beyond visible, and in full-screen mode, when clicking in open space at end of paragraph

2022-05-25 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=149300

Bug ID: 149300
   Summary: unexpected extra spaces inserted. sometimes to page
margin, sometimes beyond visible, and in full-screen
mode, when clicking in open space at end of paragraph
   Product: LibreOffice
   Version: 7.3.3.2 release
  Hardware: All
OS: Windows (All)
Status: UNCONFIRMED
  Severity: normal
  Priority: medium
 Component: Writer
  Assignee: libreoffice-bugs@lists.freedesktop.org
  Reporter: gppatn...@comcast.net

Description:
This has been happening since the last update was installed.


Steps to Reproduce:
1. Open document or click in document already open
2. Scroll to position you want to work
3. Click at end of paragraph.  

Actual Results:

- these spaces before the hyphen were not here when I clicked at
end of paragraph
TABLE SAW SECRETS NOBODY WILL TALK ABOUT FROM THE GOOD OLD DAYS, C EPISODE
180

Expected Results:
don't want extra spaces inserted

I don't understand the steps below


Reproducible: Always


User Profile Reset: No



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

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

[Libreoffice-bugs] [Bug 126008] TABLES STYLES: If you insert a row or column (with cursor in a cell), the formatting of the whole table changes (steps in comment 5)

2022-05-25 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=126008

--- Comment #48 from Dieter  ---
Still present in

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

Miklos, Xisco, any chance, that this bug (with at least 12 duplicates) will get
fixed within the next months? (I know, eveyone is free to pick up a bug or
not).

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

[Libreoffice-bugs] [Bug 126008] TABLES STYLES: If you insert a row or column (with cursor in a cell), the formatting of the whole table changes (steps in comment 5)

2022-05-25 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=126008

Dieter  changed:

   What|Removed |Added

 CC||ewblen@e.email

--- Comment #47 from Dieter  ---
*** Bug 149299 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 149299] insert row clears all character formatting in table

2022-05-25 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=149299

Dieter  changed:

   What|Removed |Added

 CC||dgp-m...@gmx.de
 Resolution|--- |DUPLICATE
 Status|UNCONFIRMED |RESOLVED

--- Comment #2 from Dieter  ---
This happens, if you place cursor in a cell and add a row. This is bug 126008.

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

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

[Libreoffice-bugs] [Bug 148952] Filesave DOCX: Alt Text field of image is lost on open in LO and in MSO

2022-05-25 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=148952

Dieter  changed:

   What|Removed |Added

 Ever confirmed|0   |1
 CC||dgp-m...@gmx.de
 Blocks||104468
 Whiteboard| QA:needsComment|
 Status|UNCONFIRMED |NEW

--- Comment #1 from Dieter  ---
I confirm it with

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


Referenced Bugs:

https://bugs.documentfoundation.org/show_bug.cgi?id=104468
[Bug 104468] [META] DOCX (OOXML) image-related issues
-- 
You are receiving this mail because:
You are the assignee for the bug.

[Libreoffice-bugs] [Bug 104468] [META] DOCX (OOXML) image-related issues

2022-05-25 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=104468

Dieter  changed:

   What|Removed |Added

 Depends on||148952


Referenced Bugs:

https://bugs.documentfoundation.org/show_bug.cgi?id=148952
[Bug 148952] Filesave DOCX: Alt Text field of image is lost on open in LO and
in MSO
-- 
You are receiving this mail because:
You are the assignee for the bug.

[Libreoffice-bugs] [Bug 148011] copy-paste extreme slowness

2022-05-25 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=148011

Suthagar  changed:

   What|Removed |Added

 OS|Windows (All)   |Linux (All)

--- Comment #2 from Suthagar  ---
Version: 7.1.8.1 / LibreOffice Community
Build ID: e1f30c802c3269a1d052614453f260e49458c82c
CPU threads: 2; OS: Linux 5.4; UI render: default; VCL: gtk3
Locale: en-IN (en_IN); UI: en-US
Calc: threaded

Steps to reproduce:
1.select all contents
2.create new spreadsheet
3.paste it

its working fine, above version. linux machine.

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

[Libreoffice-bugs] [Bug 149298] LibreOffice Writer has messed up text using TrueType fonts after changes in the sentence.

2022-05-25 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=149298

--- Comment #1 from Rangarajan  ---
Version: 7.4.0.0.alpha0+ / LibreOffice Community
Build ID: 465c3ad95059f0efa13c8027f7383c4d20a5b2ff
CPU threads: 4; OS: Linux 5.4; UI render: default; VCL: gtk3
Locale: en-IN (en_IN); UI: en-US
Calc: threaded

Actual Results:
Text should be clear and legible in all parts of the lettering and during all
edits.

Expected Results:
Text should be clear and legible in all parts of the lettering and during all
edits.

No reproduce

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

[Libreoffice-bugs] [Bug 148939] Excessive mouse scroll step in the styles list using tabbed interface and kf5

2022-05-25 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=148939

QA Administrators  changed:

   What|Removed |Added

 Whiteboard|needsKDE QA:needsComment|needsKDE

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

[Libreoffice-bugs] [Bug 148859] (F1) on Outline bar in Impress gives not found

2022-05-25 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=148859

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 144168] Inconsistent ratio between Dialog.Model.Height and the height on the screen

2022-05-25 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=144168

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 149032] Unexpected selection of 2 entry's in the animation panel after drag & drop action

2022-05-25 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=149032

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 149031] UI: No visual feedback of the position of the drop when attempting to drag an animation to the bottom of the list

2022-05-25 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=149031

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 149022] Shaping of Arabic text is broken when coloring a middle character

2022-05-25 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=149022

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 148814] When editing a footer/header in Libreoffice Calc, you cannot use keyboard shortcuts (such as CTRL+C/CTRL+V/CTRL+A) in your native language. Keyboard shortcuts work only

2022-05-25 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=148814

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 139355] Libre Office not using all CPU cores

2022-05-25 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=139355

--- Comment #6 from QA Administrators  ---
Dear Mahajan Deepak,

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

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

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

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

Warm Regards,
QA Team

MassPing-NeedInfo-Ping

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

[Libreoffice-bugs] [Bug 138965] Some files saved as ".docx" give corrupted error on reopening after completely closing the applicaiton,

2022-05-25 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=138965

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

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

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

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

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

Warm Regards,
QA Team

MassPing-NeedInfo-Ping

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

[Libreoffice-bugs] [Bug 138380] Basic-IDE - Missing feature to export COLORIZED basic code in a WRITER document + Workaround

2022-05-25 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=138380

--- Comment #14 from QA Administrators  ---
Dear Hans-Werner,

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

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

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

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

Warm Regards,
QA Team

MassPing-NeedInfo-Ping

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

[Libreoffice-bugs] [Bug 90064] Top and bottom selection border shown while scrolling even when selection started earlier

2022-05-25 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=90064

--- Comment #8 from QA Administrators  ---
Dear Tobias Markus (:Tobbi),

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.

Re: Porting libreoffice to riscv64 arch

2022-05-25 Thread Bo YU

Hi,
On Tue, May 24, 2022 at 06:28:06AM +0200, Rene Engelhard wrote:

Hi,

Am 24.05.22 um 02:37 schrieb Bo YU:

Hi,
On Mon, May 23, 2022 at 06:34:38PM +0200, Rene Engelhard wrote:


You can set ENABLE_LTO=n to get it built without LTO, though.


Ok, my fix is very buggly:

```
ifeq "$(ENABLE_MERGELIBS)" "y"
# vimer: fix
 ENABLE_LTO=n
else
 ENABLE_LTO=n
endif
```


No worry, I do that in quick tests all the time :)



Well enough. Because `ENABLE_LTO` will affect LTO only in here. it would
be better to disable LTO depend on ARCH.


Yup. Or (temporarily) add a exception for risvc64 here.

We do have one already for mips64el, see

https://salsa.debian.org/libreoffice-team/libreoffice/libreoffice/-/blob/master/rules#L676 
ff.


(Strictly speaking LTO is already depending on arch, since it's only 
done when doing MERGELIBS, which means only on 64bit :-)



Luckily, We got the *bridge* part:


[...]


There we arrive in regions I cannot help with...


First thank you, Rene, I did get some *porting* work done with your
help. As you know, the bridge UNO part code will cast me more time to
understand. So I update the status about libreoffice port to riscv64 on
Debian. This is useful if anyone has interesting to try it.

To build libreoffice package on riscv64 arch, you need apply the
*patch*[0] and the d/rules that was descripted in the mail thread:

Except for the code under bridges/source/cpp_uno/gcc3_linux_riscv64/, 
other codes should be referenced. The code under 
bridges/source/cpp_uno/gcc3_linux_riscv64/ is the core of libreoffice 
supporting riscv, which will support riscv native for libreoffice.


And now I agree with John said, maye it will get more help from
libreoffice upstream. So, Rene, please do not mind if I am ccing the
libreoffice people. At least, I wish people tell me how to start it:)

Bo,

[0]: 
https://github.com/yuzibo/debian_dev/blob/main/0004-libreoffice-add_support_riscv64.diff


You are the porter. ;-)


Regards,


Rene




--
Best Regards,



signature.asc
Description: PGP signature


[Libreoffice-bugs] [Bug 143651] Calc fails to fill-in default value from prior rows

2022-05-25 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=143651

MR Zenwiz  changed:

   What|Removed |Added

 Status|RESOLVED|CLOSED

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

[Libreoffice-bugs] [Bug 149276] Assertion failed: (dynamic_cast(static_cast(pOldValue)->pChangedFormat)), function TriggerNodeUpdate, file ndtxt.cxx, line

2022-05-25 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=149276

Telesto  changed:

   What|Removed |Added

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

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

[Libreoffice-bugs] [Bug 149268] FILEOPEN: particular document will CRASH after opening the navigator

2022-05-25 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=149268

Telesto  changed:

   What|Removed |Added

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

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

[Libreoffice-bugs] [Bug 149276] Assertion failed: (dynamic_cast(static_cast(pOldValue)->pChangedFormat)), function TriggerNodeUpdate, file ndtxt.cxx, line

2022-05-25 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=149276

Telesto  changed:

   What|Removed |Added

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

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

[Libreoffice-bugs] [Bug 149296] Crash libswlo.dylib`SwNodeIndex::GetNode(this=0x0000000000000000) const at ndindex.hxx:119:39

2022-05-25 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=149296

Telesto  changed:

   What|Removed |Added

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

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

[Libreoffice-commits] core.git: Branch 'distro/collabora/cp-6.4' - filter/source

2022-05-25 Thread Marco Cecchetti (via logerrit)
 filter/source/svg/presentation_engine.js |   68 +++
 1 file changed, 61 insertions(+), 7 deletions(-)

New commits:
commit 4f23a82ccc2582ff127007672bd5d1860ddbafbf
Author: Marco Cecchetti 
AuthorDate: Fri May 20 11:35:57 2022 +0200
Commit: Aron Budea 
CommitDate: Thu May 26 03:51:47 2022 +0200

svg filter: support for emphasis spin animation

Partial support for transform animations.
At present only rotate is supported.

Change-Id: If9ba69ec0b74bc3b527a963cb0c0bf3a7bfa5220
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/134624
Tested-by: Jenkins CollaboraOffice 
Reviewed-by: Aron Budea 

diff --git a/filter/source/svg/presentation_engine.js 
b/filter/source/svg/presentation_engine.js
index 0babb0083cc8..de73ab9710bd 100644
--- a/filter/source/svg/presentation_engine.js
+++ b/filter/source/svg/presentation_engine.js
@@ -11574,6 +11574,59 @@ PropertyAnimationNode.prototype.createActivity = 
function()
 
 
 
+function isValidTransformation( sType )
+{
+return ( sType === 'translate' || sType === 'scale' || sType === 'rotate'
+  || sType === 'skewX' || sType === 'skewY' );
+}
+
+function AnimationTransformNode(  aAnimElem, aParentNode, aNodeContext )
+{
+AnimationTransformNode.superclass.constructor.call( this, aAnimElem, 
aParentNode, aNodeContext );
+
+this.sClassName = 'AnimationTransformNode';
+}
+extend( AnimationTransformNode, AnimationBaseNode3 );
+
+
+AnimationTransformNode.prototype.parseElement = function()
+{
+var bRet = AnimationTransformNode.superclass.parseElement.call(this);
+
+var aAnimElem = this.aElement;
+
+// transformation type
+var sTransformType = aAnimElem.getAttribute( 'svg:type' );
+if( !isValidTransformation( sTransformType ) )
+{
+this.eCurrentState = INVALID_NODE;
+log( 'AnimationTransformNode.parseElement: transformation type not 
found: ' + sTransformType );
+}
+else
+{
+this.sAttributeName = sTransformType;
+}
+
+return bRet;
+}
+
+AnimationTransformNode.prototype.createActivity = function()
+{
+var aActivityParamSet = this.fillActivityParams();
+var aAnimation;
+
+aAnimation = createPropertyAnimation( this.getAttributeName(),
+  this.getAnimatedElement(),
+  this.aNodeContext.aSlideWidth,
+  this.aNodeContext.aSlideHeight );
+
+var aInterpolator = null;  // createActivity will compute it;
+return createActivity( aActivityParamSet, this, aAnimation, aInterpolator 
);
+};
+
+
+
+
 function AnimationSetNode(  aAnimElem, aParentNode, aNodeContext )
 {
 AnimationSetNode.superclass.constructor.call( this, aAnimElem, 
aParentNode, aNodeContext );
@@ -11872,10 +11925,8 @@ function createAnimationNode( aElement, aParentNode, 
aNodeContext )
 aCreatedNode = new AnimationColorNode( aElement, aParentNode, 
aNodeContext );
 break;
 case ANIMATION_NODE_ANIMATETRANSFORM:
-//aCreatedNode = new AnimationTransformNode( aElement, 
aParentNode, aNodeContext );
-//break;
-log( 'createAnimationNode: ANIMATETRANSFORM not implemented' );
-return null;
+aCreatedNode = new AnimationTransformNode( aElement, aParentNode, 
aNodeContext );
+break;
 case ANIMATION_NODE_TRANSITIONFILTER:
 aCreatedNode = new AnimationTransitionFilterNode( aElement, 
aParentNode, aNodeContext );
 break;
@@ -17934,9 +17985,12 @@ function evalValuesAttribute( aValueList, aValueSet, 
aBBox, nSlideWidth, nSlideH
 for( var i = 0; i < aValueSet.length; ++i )
 {
 var sValue = aValueSet[i];
-sValue = sValue.replace(reMath, 'Math.$&');
-sValue = sValue.replace(/pi(?!\w)/g, 'Math.PI');
-sValue = sValue.replace(/e(?!\w)/g, 'Math.E');
+if(sValue)
+{
+sValue = sValue.replace(reMath, 'Math.$&');
+sValue = sValue.replace(/pi(?!\w)/g, 'Math.PI');
+sValue = sValue.replace(/e(?!\w)/g, 'Math.E');
+}
 var aValue =  eval( sValue );
 aValueList.push( aValue );
 }


[Libreoffice-bugs] [Bug 149268] FILEOPEN: particular document will CRASH after opening the navigator

2022-05-25 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=149268

Telesto  changed:

   What|Removed |Added

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

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

[Libreoffice-bugs] [Bug 149296] Crash libswlo.dylib`SwNodeIndex::GetNode(this=0x0000000000000000) const at ndindex.hxx:119:39

2022-05-25 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=149296

Telesto  changed:

   What|Removed |Added

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

--- Comment #3 from Telesto  ---
(In reply to Rafael Lima from comment #2)
> When I try to open the file LO crashes immediately.
> 
> System info:
> Version: 7.4.0.0.alpha1+ / LibreOffice Community
> Build ID: ad6905f9a09c63712ba0aaffc700923246d21e55
> CPU threads: 16; OS: Linux 5.13; UI render: default; VCL: kf5 (cairo+xcb)
> Locale: pt-BR (pt_BR.UTF-8); UI: en-US
> Calc: CL

Sorry, I should have mentioned that: see bug 149268

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

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

2022-05-25 Thread Marco Cecchetti (via logerrit)
 filter/source/svg/presentation_engine.js |   68 +++
 1 file changed, 61 insertions(+), 7 deletions(-)

New commits:
commit 41ba315f27f93ffae14e2071dafff79260994d7f
Author: Marco Cecchetti 
AuthorDate: Fri May 20 11:35:57 2022 +0200
Commit: Aron Budea 
CommitDate: Thu May 26 03:51:29 2022 +0200

svg filter: support for emphasis spin animation

Partial support for transform animations.
At present only rotate is supported.

Change-Id: If9ba69ec0b74bc3b527a963cb0c0bf3a7bfa5220
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/134625
Tested-by: Jenkins CollaboraOffice 
Reviewed-by: Aron Budea 

diff --git a/filter/source/svg/presentation_engine.js 
b/filter/source/svg/presentation_engine.js
index 0a8eb73e7c12..201aab2dcf8e 100644
--- a/filter/source/svg/presentation_engine.js
+++ b/filter/source/svg/presentation_engine.js
@@ -11574,6 +11574,59 @@ PropertyAnimationNode.prototype.createActivity = 
function()
 
 
 
+function isValidTransformation( sType )
+{
+return ( sType === 'translate' || sType === 'scale' || sType === 'rotate'
+  || sType === 'skewX' || sType === 'skewY' );
+}
+
+function AnimationTransformNode(  aAnimElem, aParentNode, aNodeContext )
+{
+AnimationTransformNode.superclass.constructor.call( this, aAnimElem, 
aParentNode, aNodeContext );
+
+this.sClassName = 'AnimationTransformNode';
+}
+extend( AnimationTransformNode, AnimationBaseNode3 );
+
+
+AnimationTransformNode.prototype.parseElement = function()
+{
+var bRet = AnimationTransformNode.superclass.parseElement.call(this);
+
+var aAnimElem = this.aElement;
+
+// transformation type
+var sTransformType = aAnimElem.getAttribute( 'svg:type' );
+if( !isValidTransformation( sTransformType ) )
+{
+this.eCurrentState = INVALID_NODE;
+log( 'AnimationTransformNode.parseElement: transformation type not 
found: ' + sTransformType );
+}
+else
+{
+this.sAttributeName = sTransformType;
+}
+
+return bRet;
+}
+
+AnimationTransformNode.prototype.createActivity = function()
+{
+var aActivityParamSet = this.fillActivityParams();
+var aAnimation;
+
+aAnimation = createPropertyAnimation( this.getAttributeName(),
+  this.getAnimatedElement(),
+  this.aNodeContext.aSlideWidth,
+  this.aNodeContext.aSlideHeight );
+
+var aInterpolator = null;  // createActivity will compute it;
+return createActivity( aActivityParamSet, this, aAnimation, aInterpolator 
);
+};
+
+
+
+
 function AnimationSetNode(  aAnimElem, aParentNode, aNodeContext )
 {
 AnimationSetNode.superclass.constructor.call( this, aAnimElem, 
aParentNode, aNodeContext );
@@ -11872,10 +11925,8 @@ function createAnimationNode( aElement, aParentNode, 
aNodeContext )
 aCreatedNode = new AnimationColorNode( aElement, aParentNode, 
aNodeContext );
 break;
 case ANIMATION_NODE_ANIMATETRANSFORM:
-//aCreatedNode = new AnimationTransformNode( aElement, 
aParentNode, aNodeContext );
-//break;
-log( 'createAnimationNode: ANIMATETRANSFORM not implemented' );
-return null;
+aCreatedNode = new AnimationTransformNode( aElement, aParentNode, 
aNodeContext );
+break;
 case ANIMATION_NODE_TRANSITIONFILTER:
 aCreatedNode = new AnimationTransitionFilterNode( aElement, 
aParentNode, aNodeContext );
 break;
@@ -17934,9 +17985,12 @@ function evalValuesAttribute( aValueList, aValueSet, 
aBBox, nSlideWidth, nSlideH
 for( var i = 0; i < aValueSet.length; ++i )
 {
 var sValue = aValueSet[i];
-sValue = sValue.replace(reMath, 'Math.$&');
-sValue = sValue.replace(/pi(?!\w)/g, 'Math.PI');
-sValue = sValue.replace(/e(?!\w)/g, 'Math.E');
+if(sValue)
+{
+sValue = sValue.replace(reMath, 'Math.$&');
+sValue = sValue.replace(/pi(?!\w)/g, 'Math.PI');
+sValue = sValue.replace(/e(?!\w)/g, 'Math.E');
+}
 var aValue =  eval( sValue );
 aValueList.push( aValue );
 }


[Libreoffice-bugs] [Bug 149299] insert row clears all character formatting in table

2022-05-25 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=149299

--- Comment #1 from ewblen@e.email ---
Created attachment 180391
  --> https://bugs.documentfoundation.org/attachment.cgi?id=180391=edit
Document that has the problem

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

[Libreoffice-bugs] [Bug 149299] New: insert row clears all character formatting in table

2022-05-25 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=149299

Bug ID: 149299
   Summary: insert row clears all character formatting in table
   Product: LibreOffice
   Version: 6.4.7.2 release
  Hardware: All
OS: All
Status: UNCONFIRMED
  Severity: normal
  Priority: medium
 Component: Writer
  Assignee: libreoffice-bugs@lists.freedesktop.org
  Reporter: ewblen@e.email

Description:
Create a table, and formatted the header as bold, a subheading in the second
row as italic, and then a number of data rows unformatted.
Repeat subheading and data a couple of times
Then invoke "Insert row below" - a row is inserted, but the bold and italic
formatting disappear.

This happens on another person's laptop, but I couldn't reproduce it on mine.

Steps to Reproduce:
Create a table, and formatted the header as bold, a subheading in the second
row as italic, and then a number of data rows unformatted.
Repeat subheading and data a couple of times
Then invoke "Insert row below" 


Actual Results:
a row is inserted, but the bold and italic formatting disappear.

Expected Results:
- a row is inserted, no other change


Reproducible: Couldn't Reproduce


User Profile Reset: No



Additional Info:
V6.4.7.2

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

[Libreoffice-bugs] [Bug 107158] [META] Notebookbar Groupedbar

2022-05-25 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=107158

Rafael Lima  changed:

   What|Removed |Added

 Depends on||149289


Referenced Bugs:

https://bugs.documentfoundation.org/show_bug.cgi?id=149289
[Bug 149289] Icons disappear using Groupedbar Compact UI variant when
alternating between documents using Alt+Tab
-- 
You are receiving this mail because:
You are the assignee for the bug.

[Libreoffice-bugs] [Bug 149289] Icons disappear using Groupedbar Compact UI variant when alternating between documents using Alt+Tab

2022-05-25 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=149289

Rafael Lima  changed:

   What|Removed |Added

 Blocks||107158


Referenced Bugs:

https://bugs.documentfoundation.org/show_bug.cgi?id=107158
[Bug 107158] [META] Notebookbar Groupedbar
-- 
You are receiving this mail because:
You are the assignee for the bug.

[Libreoffice-bugs] [Bug 147740] Lower icons disappear in groupedbar compact user interface

2022-05-25 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=147740

Rafael Lima  changed:

   What|Removed |Added

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

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

[Libreoffice-bugs] [Bug 149289] Icons disappear using Groupedbar Compact UI variant when alternating between documents using Alt+Tab

2022-05-25 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=149289

Rafael Lima  changed:

   What|Removed |Added

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

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

[Libreoffice-bugs] [Bug 149289] Icons disappear using Groupedbar Compact UI variant when alternating between documents using Alt+Tab

2022-05-25 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=149289

Rafael Lima  changed:

   What|Removed |Added

 CC||rafael.palma.l...@gmail.com
Summary|Libreoffice UI crash|Icons disappear using
   ||Groupedbar Compact UI
   ||variant when alternating
   ||between documents using
   ||Alt+Tab

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

[Libreoffice-bugs] [Bug 149289] Libreoffice UI crash

2022-05-25 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=149289

Rafael Lima  changed:

   What|Removed |Added

 Ever confirmed|0   |1
 Status|UNCONFIRMED |NEW

--- Comment #4 from Rafael Lima  ---
I can confirm this bug. Open two documents using the "Groupedbar Compact"
interface and use Alt-Tab to alternate between them. The icons in the toolbar
will disappear.

System info:
Version: 7.4.0.0.alpha1+ / LibreOffice Community
Build ID: ad6905f9a09c63712ba0aaffc700923246d21e55
CPU threads: 16; OS: Linux 5.13; UI render: default; VCL: kf5 (cairo+xcb)
Locale: pt-BR (pt_BR.UTF-8); UI: en-US
Calc: CL

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

[Libreoffice-bugs] [Bug 149036] Missing icon for "Label Field" using Breeze (dark) icon theme

2022-05-25 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=149036

--- Comment #2 from Rafael Lima  ---
(In reply to Rizal Muttaqin from comment #1)
> Could you provide step by step to reproduce the issue?

You have to open the Dialog Editor.

For that, go to Tools - Macros - Organize Dialogs. This will open the "Basic
Macro Organizer".

In the "Dialogs" tab, select the Standard library and click New and then give a
name to the dialog (f.i. "MyDialog").

Now select the dialog you've just created and click Edit. This will open the
Dialog Editor. The toolbar with the missing icon will be at the bottom of the
screen.

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

[Libreoffice-bugs] [Bug 149296] Crash libswlo.dylib`SwNodeIndex::GetNode(this=0x0000000000000000) const at ndindex.hxx:119:39

2022-05-25 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=149296

--- Comment #2 from Rafael Lima  ---
When I try to open the file LO crashes immediately.

System info:
Version: 7.4.0.0.alpha1+ / LibreOffice Community
Build ID: ad6905f9a09c63712ba0aaffc700923246d21e55
CPU threads: 16; OS: Linux 5.13; UI render: default; VCL: kf5 (cairo+xcb)
Locale: pt-BR (pt_BR.UTF-8); UI: en-US
Calc: CL

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

[Libreoffice-bugs] [Bug 149293] CRASH: Opening the navigator

2022-05-25 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=149293

--- Comment #3 from Rafael Lima  ---
I could reproduce this with:

Version: 7.4.0.0.alpha1+ / LibreOffice Community
Build ID: ad6905f9a09c63712ba0aaffc700923246d21e55
CPU threads: 16; OS: Linux 5.13; UI render: default; VCL: kf5 (cairo+xcb)
Locale: pt-BR (pt_BR.UTF-8); UI: en-US
Calc: CL

In LO 7.3.3 this bug is not present.

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

[Libreoffice-bugs] [Bug 143651] Calc fails to fill-in default value from prior rows

2022-05-25 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=143651

Aron Budea  changed:

   What|Removed |Added

 CC||aron.bu...@gmail.com
 Resolution|--- |WORKSFORME
 Status|UNCONFIRMED |RESOLVED

--- Comment #10 from Aron Budea  ---
Great, let's close as WFM, thanks for the update.

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

[Libreoffice-bugs] [Bug 137440] [EMF] FILEOPEN: Wrong text due to missing ETO_GLYPH_INDEX option from EMR_EXTTEXTOUTW record

2022-05-25 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=137440

--- Comment #6 from Bartosz  ---
More information:
https://docs.microsoft.com/en-us/typography/opentype/spec/cmap

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

[Libreoffice-bugs] [Bug 141784] Writer documents with Formulas getting flagged as grammar/spelling error

2022-05-25 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=141784

--- Comment #6 from Rafael Lima  ---
(In reply to Buovjaga from comment #5)
> I installed Vero 3.2.15 and I confirm the issue with the example pt-BR file.
> Rafael: will you discuss this with Vero developers?

I'm guessing this is caused by Bug 65323, since Equation objects are not being
treated as characters even though they're anchored as characters.

Hence, when we add an equation in a paragraph, a grammar error is triggered
because the grammar checker thinks there are two consecutive blank spaces.

A fix for bug 65323 will also fix this bug. At least partially, because other
grammar errors could be triggered depending on which character the equation
ends up being represented by.

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

[Libreoffice-bugs] [Bug 142007] [EMF] AngleArc is not supported

2022-05-25 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=142007

Bartosz  changed:

   What|Removed |Added

 CC||gan...@poczta.onet.pl

--- Comment #4 from Bartosz  ---
More information:
https://docs.microsoft.com/en-us/openspecs/windows_protocols/ms-emf/3b04a2e2-9ba5-477f-b79c-5710635d04b9

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

[Libreoffice-bugs] [Bug 141784] Writer documents with Formulas getting flagged as grammar/spelling error

2022-05-25 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=141784

Rafael Lima  changed:

   What|Removed |Added

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

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

[Libreoffice-bugs] [Bug 65323] Objects anchored as characters aren't treated as characters

2022-05-25 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=65323

Rafael Lima  changed:

   What|Removed |Added

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

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

[Libreoffice-bugs] [Bug 149273] Clicking on 'Entries' tab when inserting/editing an index crashes Writer (Mac OS)

2022-05-25 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=149273

--- Comment #9 from SK  ---
The only lead that I can think of now is that after running the 7.2.7.2 release
on the same user profile, the 7.3 cannot even open the 'Table of Contents,
Index, or Bibliography' dialogue without crashing. For the moment, I will use
7.2.

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

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

2022-05-25 Thread Eike Rathke (via logerrit)
 i18nlangtag/source/isolang/isolang.cxx |   10 ++
 1 file changed, 10 insertions(+)

New commits:
commit fd45045cc3029b41c02a2634e6fe2e5456f716ad
Author: Eike Rathke 
AuthorDate: Wed May 25 20:26:28 2022 +0200
Commit: Eike Rathke 
CommitDate: Thu May 26 01:48:31 2022 +0200

convertLanguageToLocaleImpl() speed-up a gazillion en-US fallback cases

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

diff --git a/i18nlangtag/source/isolang/isolang.cxx 
b/i18nlangtag/source/isolang/isolang.cxx
index d374bcd62213..1e967015b285 100644
--- a/i18nlangtag/source/isolang/isolang.cxx
+++ b/i18nlangtag/source/isolang/isolang.cxx
@@ -952,6 +952,16 @@ IsoLangOtherEntry const aImplPrivateUseEntries[] =
 void MsLangId::Conversion::convertLanguageToLocaleImpl( LanguageType nLang,
 css::lang::Locale & rLocale, bool bIgnoreOverride )
 {
+if (nLang == LANGUAGE_ENGLISH_US)
+{
+// Speed-up a gazillion fallback cases, not iterating through
+// aImplBcp47CountryEntries nor aImplIsoLangScriptEntries.
+rLocale.Language = "en";
+rLocale.Country = "US";
+rLocale.Variant.clear();
+return;
+}
+
 const Bcp47CountryEntry* pBcp47EntryOverride = nullptr;
 const IsoLanguageScriptCountryEntry* pScriptEntryOverride = nullptr;
 const IsoLanguageCountryEntry* pEntryOverride = nullptr;


[Libreoffice-bugs] [Bug 149036] Missing icon for "Label Field" using Breeze (dark) icon theme

2022-05-25 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=149036

Rizal Muttaqin  changed:

   What|Removed |Added

 CC||riz...@libreoffice.org

--- Comment #1 from Rizal Muttaqin  ---
Hi Rafael, thanks for the report!!


Could you provide step by step to reproduce the issue?

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

[Libreoffice-bugs] [Bug 143651] Calc fails to fill-in default value from prior rows

2022-05-25 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=143651

MR Zenwiz  changed:

   What|Removed |Added

 Status|NEEDINFO|UNCONFIRMED
 Ever confirmed|1   |0

--- Comment #9 from MR Zenwiz  ---
I can no longer reproduce the problem with 7.3.3.

Thank you for your attention.

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

[Libreoffice-commits] core.git: instsetoo_native/CustomTarget_install.mk

2022-05-25 Thread Thorsten Behrens (via logerrit)
 instsetoo_native/CustomTarget_install.mk |3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

New commits:
commit aee953d7b66c02bbd7034cbf8991e3748dc3794a
Author: Thorsten Behrens 
AuthorDate: Wed May 25 13:21:26 2022 +0200
Commit: Thorsten Behrens 
CommitDate: Thu May 26 01:09:55 2022 +0200

Reduce cmd line length for make_installer calls

Seems on Windows, we're hitting the 8k character max cmd line length,
on setups with slightly deeper src tree path locations. Shorten length
of expanded call_installer calls by putting shell script into PATH
locally.

Change-Id: If1cddab9e4e07a7c5ebfae7a4e88e43b1bc8b907
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/134938
Tested-by: Jenkins
Reviewed-by: Thorsten Behrens 

diff --git a/instsetoo_native/CustomTarget_install.mk 
b/instsetoo_native/CustomTarget_install.mk
index 47b2ffe1a262..37b177ab94c2 100644
--- a/instsetoo_native/CustomTarget_install.mk
+++ b/instsetoo_native/CustomTarget_install.mk
@@ -71,8 +71,9 @@ $(if $(GNUPARALLEL), \
 , \
 $(call gb_Helper_print_on_error, \
 cd $(dir $@) \
+&& PATH="$(SRCDIR)/solenv/bin:$$PATH" \
 $(foreach curpkg,$(1),\
-&& $(SRCDIR)/solenv/bin/call_installer.sh $(if $(verbose),-verbose,-quiet) 
$(curpkg) \
+&& call_installer.sh $(if $(verbose),-verbose,-quiet) $(curpkg) \
 ),$@.log))
 endef
 


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

2022-05-25 Thread Caolán McNamara (via logerrit)
 vcl/source/filter/itiff/itiff.cxx |2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

New commits:
commit 50d0beecf23468e3f9a7090e2723e9bbf94b30bf
Author: Caolán McNamara 
AuthorDate: Wed May 25 09:07:16 2022 +0100
Commit: Caolán McNamara 
CommitDate: Thu May 26 00:21:00 2022 +0200

ofz#47617 don't skip TIFFClose on error condition

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

diff --git a/vcl/source/filter/itiff/itiff.cxx 
b/vcl/source/filter/itiff/itiff.cxx
index 41255140617a..6eac698121f0 100644
--- a/vcl/source/filter/itiff/itiff.cxx
+++ b/vcl/source/filter/itiff/itiff.cxx
@@ -132,7 +132,7 @@ bool ImportTiffGraphicImport(SvStream& rTIFF, Graphic& 
rGraphic)
 if (TIFFTileSize64(tif) > MAX_SIZE)
 {
 SAL_WARN("filter.tiff", "skipping large tiffs");
-return false;
+break;
 }
 }
 


[Libreoffice-bugs] [Bug 149293] CRASH: Opening the navigator

2022-05-25 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=149293

Julien Nabet  changed:

   What|Removed |Added

 CC||serval2...@yahoo.fr

--- Comment #2 from Julien Nabet  ---
Created attachment 180390
  --> https://bugs.documentfoundation.org/attachment.cgi?id=180390=edit
bt with debug symbols

On pc Debian x86-64 with master sources updated today, I could reproduce this.

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

[Libreoffice-bugs] [Bug 149294] [UI] Function "Select to End of Word" (.uno:WordRightSel) must be renamed, because it also selects spaces and tabs at the right side of word

2022-05-25 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=149294

LeroyG  changed:

   What|Removed |Added

Summary|Select to End of Word   |[UI] Function "Select to
   |(.uno:WordRightSel) also|End of Word"
   |selects spaces and tabs at  |(.uno:WordRightSel) must be
   |the right side of word  |renamed, because it also
   ||selects spaces and tabs at
   ||the right side of word

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

[Libreoffice-bugs] [Bug 149298] New: LibreOffice Writer has messed up text using TrueType fonts after changes in the sentence.

2022-05-25 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=149298

Bug ID: 149298
   Summary: LibreOffice Writer has messed up text using TrueType
fonts after changes in the sentence.
   Product: LibreOffice
   Version: 7.3.2.2 release
  Hardware: x86-64 (AMD64)
OS: Windows (All)
Status: UNCONFIRMED
  Severity: trivial
  Priority: medium
 Component: Writer
  Assignee: libreoffice-bugs@lists.freedesktop.org
  Reporter: polarbear20...@gmail.com

Description:
As I type my text in Writer (Version: 7.3.2.2 (x64) / LibreOffice Community)
and performs edits I have observed that text is messed up at the tops of each
line at each letter and leaving artifacts of previous or deleted letters,
numbers, and symbols. Sometimes scrolling up and down will refresh the lines
and view as it is supposed to and sometimes not. If I send this to the printer,
the artifacts print. If I save the file and reopen it after reopening Writer,
there are no artifacts. If I export to PDF or Epub, there are no artifacts.

I generally use TrueType fonts, but this is also seen with OpenType and
standard system fonts. This is distracting, more than anything else, and it
makes for a usability issue as it tends to add up over lines and makes for
readability issues then.

Steps to Reproduce:
1. Type something in a long sentence with 10+ words.
2. Go back and edit by changing words, spaces, punctuation, symbols and so on.
3. Observe.

Actual Results:
The top quarters of the text are obfuscated and doesn't print on the screen as
expected.

Expected Results:
Text should be clear and legible in all parts of the lettering and during all
edits.


Reproducible: Always


User Profile Reset: Yes


OpenGL enabled: Yes

Additional Info:
Version: 7.3.2.2 (x64) / LibreOffice Community
Build ID: 49f2b1bff42cfccbd8f788c8dc32c1c309559be0
CPU threads: 2; OS: Windows 10.0 Build 19044; UI render: Skia/Raster; VCL: win
Locale: en-US (en_US); UI: en-US
Calc: threaded

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

[Libreoffice-bugs] [Bug 149296] Crash libswlo.dylib`SwNodeIndex::GetNode(this=0x0000000000000000) const at ndindex.hxx:119:39

2022-05-25 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=149296

MM  changed:

   What|Removed |Added

 Ever confirmed|0   |1
 Status|UNCONFIRMED |NEW
Version|7.4.0.0 alpha0+ Master  |7.3.3.2 release

--- Comment #1 from MM  ---
Confirmed on windows 10 x64 with Version: 7.3.3.2 (x64) / LibreOffice Community
Build ID: d1d0ea68f081ee2800a922cac8f79445e4603348
CPU threads: 12; OS: Windows 10.0 Build 19043; UI render: Skia/Vulkan; VCL: win
Calc: CL

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

[Libreoffice-bugs] [Bug 149273] Clicking on 'Entries' tab when inserting/editing an index crashes Writer (Mac OS)

2022-05-25 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=149273

Julien Nabet  changed:

   What|Removed |Added

 Ever confirmed|1   |0
 Status|NEEDINFO|UNCONFIRMED

--- Comment #8 from Julien Nabet  ---
Thank you for your new feedback.
I must recognize I'm stuck.
Since I don't have more question, I'll put back to UNCONFIRMED.

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

[Libreoffice-bugs] [Bug 149297] New: EDITING: Text selection in vertical text positioned incorrectly

2022-05-25 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=149297

Bug ID: 149297
   Summary: EDITING: Text selection in vertical text positioned
incorrectly
   Product: LibreOffice
   Version: 7.2.7.2 release
  Hardware: All
OS: macOS (All)
Status: UNCONFIRMED
  Severity: normal
  Priority: medium
 Component: Writer
  Assignee: libreoffice-bugs@lists.freedesktop.org
  Reporter: libreoff...@herouth-maoz.name

When attempting to select CJK in a page with vertical layout, the edges of
selection are positioned incorrectly. If the text is copied to clipboard, the
copied text is off by a character.

The same text behaves normally if laid horizontally.

Version: 7.2.7.2 / LibreOffice Community
Build ID: 8d71d29d553c0f7dcbfa38fbfda25ee34cce99a2
CPU threads: 8; OS: Mac OS X 10.14.6; UI render: default; VCL: osx
Locale: en-US (en_IL.UTF-8); UI: en-US
Calc: threaded

To reproduce:

1. Copy some CJK text. For example,

しかし、通常、上位力士とは当たらない平幕の下位力士が、終盤まで優勝争いに絡んできた場合には横綱・大関との取組を組み、本来組まれるはずの横綱対大関・大関同士・大関対関脇などの対戦を消滅させることがある。

(Arbitrary text from JA Wikipedia)

2. Create a new Writer document and paste the text without formatting

3. Go to Format->Page Style, and choose Text direction: Right-to-left
(vertical)

4. Try to select some text, positioning the cursor right on the edge of a
character.

Result: The selection starts slightly lower.
Expected result: The entire character should be selected

5. Copy the selected text, and paste it in some text box or another document.

Result: The selection does not include the character before which the cursor
was placed.
Expected result: The selection should include the nearest below the cursor at
the time of selection.

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

[Libreoffice-bugs] [Bug 149273] Clicking on 'Entries' tab when inserting/editing an index crashes Writer (Mac OS)

2022-05-25 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=149273

--- Comment #7 from SK  ---
Yes, one more thing. I removed the user profile completely together with the
existing versions of LO.

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

[Libreoffice-bugs] [Bug 149273] Clicking on 'Entries' tab when inserting/editing an index crashes Writer (Mac OS)

2022-05-25 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=149273

--- Comment #6 from SK  ---
Created attachment 180389
  --> https://bugs.documentfoundation.org/attachment.cgi?id=180389=edit
Crash log after fresh installation of LO

This is the crash immediately following a clean installation of LO on a new
document.

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

[Libreoffice-bugs] [Bug 149273] Clicking on 'Entries' tab when inserting/editing an index crashes Writer (Mac OS)

2022-05-25 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=149273

--- Comment #5 from SK  ---
I only installed the 7.2.7.2 version after seeing the crash. So now I have
completely removed all versions of LO and once more downloaded the 7.3.3 from
the official link (I did that initially, as well). I checked the SHA hash to
make sure that the image was not corrupt. I then copied LO to the Applications
folder and only did the following: started LO, created a new Writer document,
clicked 'Insert|Table of Contents and Index|Table of Contents, Index, or
Bibliography' and then clicked the 'Entries' tab. It crashed as before. I am
attaching a new crash log after this comment.

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

[Libreoffice-bugs] [Bug 149290] Impress crash on second presentation with Presenter Console

2022-05-25 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=149290

Julien Nabet  changed:

   What|Removed |Added

   Keywords||haveBacktrace

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

[Libreoffice-bugs] [Bug 149290] Impress crash on second presentation with Presenter Console

2022-05-25 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=149290

Julien Nabet  changed:

   What|Removed |Added

 CC||serval2...@yahoo.fr

--- Comment #3 from Julien Nabet  ---
Created attachment 180388
  --> https://bugs.documentfoundation.org/attachment.cgi?id=180388=edit
bt with debug symbols

On pc Debian x86-64 with master sources updated today, I could reproduce this.

I noticed these on console:
warn:vcl.layout:945226:945226:vcl/source/window/layout.cxx:288: nExtraSpace
went negative, setting to zero for VclBox: 
warn:sd:945226:945226:sd/source/ui/framework/tools/FrameworkHelper.cxx:209:
DBG_UNHANDLED_EXCEPTION in lcl_getViewShell exception:
com.sun.star.uno.RuntimeException message: "unsatisfied query for interface of
type com.sun.star.lang.XUnoTunnel! at
/home/julien/lo/libreoffice/include/com/sun/star/uno/Reference.hxx:83"
warn:sd:945226:945226:sd/source/ui/framework/tools/FrameworkHelper.cxx:209:
DBG_UNHANDLED_EXCEPTION in lcl_getViewShell exception:
com.sun.star.uno.RuntimeException message: "unsatisfied query for interface of
type com.sun.star.lang.XUnoTunnel! at
/home/julien/lo/libreoffice/include/com/sun/star/uno/Reference.hxx:83"
warn:vcl.layout:945226:945226:vcl/source/window/layout.cxx:288: nExtraSpace
went negative, setting to zero for VclBox: 
warn:sd:945226:945226:sd/source/ui/framework/tools/FrameworkHelper.cxx:209:
DBG_UNHANDLED_EXCEPTION in lcl_getViewShell exception:
com.sun.star.uno.RuntimeException message: "unsatisfied query for interface of
type com.sun.star.lang.XUnoTunnel! at
/home/julien/lo/libreoffice/include/com/sun/star/uno/Reference.hxx:83"
warn:sd:945226:945226:sd/source/ui/framework/tools/FrameworkHelper.cxx:209:
DBG_UNHANDLED_EXCEPTION in lcl_getViewShell exception:
com.sun.star.uno.RuntimeException message: "unsatisfied query for interface of
type com.sun.star.lang.XUnoTunnel! at
/home/julien/lo/libreoffice/include/com/sun/star/uno/Reference.hxx:83"
warn:legacy.tools:945226:945226:svx/source/form/fmshimp.cxx:1801: only to be
used in alive mode
soffice.bin: /home/julien/lo/libreoffice/include/rtl/ref.hxx:216:
reference_type
*rtl::Reference::operator->() const
[reference_type = sdext::presenter::PresenterWindowManager]: Assertion `m_pBody
!= NULL' failed.

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

Re: Question about Libreoffice Draw

2022-05-25 Thread Eike Rathke
Hi Intissar,

On Tuesday, 2022-05-17 13:47:12 +0200, Intissar Mortadi wrote:

> I want to create a tool using Libreoffixe and I need it to intereact with
> the user,

Best direct your question with details to our Ask site
https://ask.libreoffice.org/

  Eike

-- 
GPG key 0x6A6CD5B765632D3A - 2265 D7F3 A7B0 95CC 3918  630B 6A6C D5B7 6563 2D3A


signature.asc
Description: PGP signature


[Libreoffice-bugs] [Bug 149284] LO Base freeze when using a form with macro to enter MySQL data

2022-05-25 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=149284

Julien Nabet  changed:

   What|Removed |Added

   Severity|enhancement |normal

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

[Libreoffice-bugs] [Bug 144060] Writer process hangs sometimes on macOS 11.4 on MacBook Air M1 (Intel version, Zotero uninstalled)

2022-05-25 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=144060

--- Comment #22 from Julien Nabet  ---
(In reply to David Snow from comment #21)
> Your idea of copying the whole document and pasting it into a new one has
> some bad consequences!  Page sizes and margins are not copied for all page
> types!
> I do not know what else is randomly lost in the process. Since I only 6 page
> styles this won't take too long to fix. But locating any other parameters
> that get lost might take a while ;=}

I understand but perhaps there's something buggy in the styles in the original
file.
Just for curiosity, even if you won't use it, do you also have hangs with the
new file?

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

[Libreoffice-bugs] [Bug 149273] Clicking on 'Entries' tab when inserting/editing an index crashes Writer (Mac OS)

2022-05-25 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=149273

--- Comment #4 from Julien Nabet  ---
The bt shows a kind of never ending recursive call but I don't see the origin
of it.

Did you retrieve LO from official website
(https://www.libreoffice.org/download/download/)?

Anyway, since you talked about parallel versions, I think you should first
uninstall all the LO versions you have.
Then, rename your LO directory profile (see
https://wiki.documentfoundation.org/QA/FirstSteps#Corrupted_user_profile)

Once done, install 7.3.3 from official website.

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

[Libreoffice-bugs] [Bug 149273] Clicking on 'Entries' tab when inserting/editing an index crashes Writer (Mac OS)

2022-05-25 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=149273

--- Comment #3 from SK  ---
Hi Julien,

Thank you for you reply. I am running Mac OS 10.13.6 on a MacBookPro11,3. I did
not install any fonts through LibreOffice. I did install a couple of dictionary
packs (hyphenation, thesaurus). I tried running LibreOffice in safe mode with
identical results. I tried disabling the installed extensions, which did not
change the behaviour (see attached). I proceeded to completely remove the user
profile and the change was that now I could once more bring up the 'Table of
Contents, Index, or Bibliography' dialogue (it was not possible since I ran the
7.2.7.2 release in parallel). However, clicking on the 'Entries' tab continues
to crash Writer as it did initially.

Further on, I tried the same steps on a different computer similar to mine, but
somewhat newer (MacBookPro11,5) and, indeed, the crash does not happen at all
on that one.

Unfortunately, I don't have access to an identical MacBook to see if the crash
is specific to this particular model.

Let me know if I can do anything else to identify the cause of this crash.

Serge.

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

[Libreoffice-bugs] [Bug 149254] Make the selection behavior when double-clicking a word a user preference.

2022-05-25 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=149254

--- Comment #9 from Chris  ---
(In reply to Rafael Lima from comment #5)
> Created attachment 180386 [details]
> Another example in Google Docs
> 
> This is a bit weird. See in my screenshot that double-clicking a word in
> Google Docs only selects the word (not the trailing spaces).
> 
> What operating system are you using? What Web browser do you use with Google
> Docs?

I'm in Windows 10 and using Brave browser.  The behavior is consistent from one
browser to another for me.  As noted, there may be a regional component to
this.

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

[Libreoffice-bugs] [Bug 149254] Make the selection behavior when double-clicking a word a user preference.

2022-05-25 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=149254

--- Comment #8 from Chris  ---
I see from your examples that perhaps there is a regional component to this. 
For me that is all the more reason to have the behavior be user-selectable.  

Thank you for taking an interest.  I hope we can find a way to make this
improvement to Writer!

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

[Libreoffice-bugs] [Bug 65323] Objects anchored as characters aren't treated as characters

2022-05-25 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=65323

Mike Kaganski  changed:

   What|Removed |Added

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

--- Comment #14 from Mike Kaganski  ---
*** Bug 149295 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 149295] Characters near Math Equations should be considered in paragraph flow

2022-05-25 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=149295

Mike Kaganski  changed:

   What|Removed |Added

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

--- Comment #2 from Mike Kaganski  ---


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

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

[Libreoffice-bugs] [Bug 149254] Make the selection behavior when double-clicking a word a user preference.

2022-05-25 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=149254

Rafael Lima  changed:

   What|Removed |Added

 Status|NEEDINFO|UNCONFIRMED
   Keywords|topicDesign, topicUI|needsUXEval
 Ever confirmed|1   |0

--- Comment #7 from Rafael Lima  ---
As a follow-up to Comment 5, when I double-click a word in Google Docs, indeed
just the word gets selected.

However, if I press delete only one space is left between both words, which is
very handy and prevents the user from making the mistake of leaving two
consecutive blank spaces.

LibreOffice Writer would have left two consecutive blank spaces in this case,
which is indeed not a great experience. I myself have made a few mistakes in
documents due to this behavior.

IMO when we select a word and delete it, only one blank space should be left,
as MS Word and Google Docs do. Let's hear the UX team's opinion on this.

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

[Libreoffice-bugs] [Bug 149254] Make the selection behavior when double-clicking a word a user preference.

2022-05-25 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=149254

--- Comment #6 from Chris  ---
Created attachment 180387
  --> https://bugs.documentfoundation.org/attachment.cgi?id=180387=edit
Double-Click Behavior Bugzilla

This selection shows several spaces beyond a double-clicked word being
selected.

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

[Libreoffice-bugs] [Bug 149254] Make the selection behavior when double-clicking a word a user preference.

2022-05-25 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=149254

--- Comment #5 from Rafael Lima  ---
Created attachment 180386
  --> https://bugs.documentfoundation.org/attachment.cgi?id=180386=edit
Another example in Google Docs

This is a bit weird. See in my screenshot that double-clicking a word in Google
Docs only selects the word (not the trailing spaces).

What operating system are you using? What Web browser do you use with Google
Docs?

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

[Libreoffice-bugs] [Bug 92717] Impress Internet Presentation with 1 monitor and having 2 windows (1 for the presentation and 1 for the console)

2022-05-25 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=92717

--- Comment #7 from Óvári  ---
(In reply to Timur from comment #6)
> Should be tested with other sharing software.
Jami: https://jami.net/
Jitsi Meet: https://meet.jit.si/

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

[Libreoffice-bugs] [Bug 149254] Make the selection behavior when double-clicking a word a user preference.

2022-05-25 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=149254

--- Comment #4 from Chris  ---
Created attachment 180385
  --> https://bugs.documentfoundation.org/attachment.cgi?id=180385=edit
Double-Click Behavior Google Docs

Google Docs emulates the behavior of MS Word (and this editor) by selecting the
text string plus the trailing space.

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

  1   2   3   4   5   >