[Libreoffice-bugs] [Bug 142446] In folding outlines, enable specifying, document-wide, the level to which text should be collapsed.
https://bugs.documentfoundation.org/show_bug.cgi?id=142446 --- Comment #8 from Jim Raykowski --- Created attachment 183037 --> https://bugs.documentfoundation.org/attachment.cgi?id=183037=edit visualization of described expectation Is what is shown in the attached screen shot what we are going for? Seems setting the 'Headings level shown' in the Navigator content tree sort of already does this. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-commits] core.git: oox/source
oox/source/drawingml/shape.cxx |6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
New commits:
commit 833825eec54718ac99ab31877fb65a83864ba049
Author: Andrea Gelmini
AuthorDate: Thu Oct 13 12:13:45 2022 +0200
Commit: Julien Nabet
CommitDate: Fri Oct 14 07:53:09 2022 +0200
Fix typo in code
Change-Id: If4cf1a77490650902d77705761b5168bdf5cece8
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/141306
Tested-by: Jenkins
Reviewed-by: Julien Nabet
diff --git a/oox/source/drawingml/shape.cxx b/oox/source/drawingml/shape.cxx
index 0369f5ff732c..e1a81c99631c 100644
--- a/oox/source/drawingml/shape.cxx
+++ b/oox/source/drawingml/shape.cxx
@@ -971,14 +971,14 @@ Reference< XShape > const & Shape::createAndInsert(
// It depends on the object rotation angle whether scaling is
applied to switched
// width and height. MSO acts strange in that case (as of May
2021).
const sal_Int32 nDeg(mnRotation / 6);
-const bool bNeedsMSOWidhtHeightToggle
+const bool bNeedsMSOWidthHeightToggle
= (nDeg >= 45 && nDeg < 135) || (nDeg >= 225 && nDeg < 315);
-if (bNeedsMSOWidhtHeightToggle)
+if (bNeedsMSOWidthHeightToggle)
lcl_doSpecialMSOWidthHeightToggle(aTransformation);
aTransformation.scale(fFactorX, fFactorY);
-if (bNeedsMSOWidhtHeightToggle)
+if (bNeedsMSOWidthHeightToggle)
{
lcl_doSpecialMSOWidthHeightToggle(aTransformation);
// In case of flip the special case needs an additional 180deg
rotation.
[Libreoffice-commits] core.git: cui/source sfx2/source
cui/source/customize/cfgutil.cxx | 83 +--
cui/source/inc/cfgutil.hxx |1
sfx2/source/appl/appserv.cxx |7 ++-
3 files changed, 52 insertions(+), 39 deletions(-)
New commits:
commit 9b227506a5fd3e84d4aa877fc6459996546348ba
Author: Stephan Bergmann
AuthorDate: Thu Oct 13 16:53:41 2022 +0200
Commit: Stephan Bergmann
CommitDate: Fri Oct 14 07:44:45 2022 +0200
Start to fix the "BASIC Macros" dialog's "Assign..." button
c79212479f42cadd39173e77acc5e6446480ff05 "Fix a misuse of two-argument std
string_view rfind" found that e.g. in Writer "Tools - Macros - Organize
Macros -
Basic...", in "Macro From" select "My Macros - Standard - Module1" and in
"Existing Macros in: Module 1" select "Main", then "Assign..." had
apparently
rotten over time and brought up the "Customize" dialog's default "Menus"
tab.
With this fix, it now brings up the "Customize" dialog's "Keyboard" tab, in
the
"Category" tree list selects the appropriate "Module1" line, and in the
"Function" list shows all the corresponding functions (just "Main" in this
case).
It doesn't yet select the appropriate line ("Main") in the "Function" list,
though. That apparently needs further fixing.
Change-Id: Ia5b9ef88d29e01f4f5e22ce3aec20f5fc22b5d45
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/141303
Tested-by: Jenkins
Reviewed-by: Stephan Bergmann
diff --git a/cui/source/customize/cfgutil.cxx b/cui/source/customize/cfgutil.cxx
index ee9d4a3fdc61..0314f1810c47 100644
--- a/cui/source/customize/cfgutil.cxx
+++ b/cui/source/customize/cfgutil.cxx
@@ -1023,23 +1023,16 @@ IMPL_LINK(CuiConfigGroupListBox, ExpandingHdl, const
weld::TreeIter&, rIter, boo
#if HAVE_FEATURE_SCRIPTING
void CuiConfigGroupListBox::SelectMacro( const SfxMacroInfoItem *pItem )
{
-SelectMacro( pItem->GetBasicManager()->GetName(),
- pItem->GetQualifiedName() );
-}
-
-void CuiConfigGroupListBox::SelectMacro( std::u16string_view rBasic,
- std::u16string_view rMacro )
-{
-const OUString aBasicName(OUString::Concat(rBasic) + " " +
xImp->m_sMacros);
-size_t nIdx {rMacro.rfind('.')};
-const std::u16string_view aMethod( rMacro.substr(nIdx ==
std::u16string_view::npos ? 0 : nIdx + 1) );
+auto const rMacro = pItem->GetQualifiedName();
+sal_Int32 nIdx {rMacro.lastIndexOf('.')};
+const std::u16string_view aMethod( rMacro.subView(nIdx + 1) );
std::u16string_view aLib;
std::u16string_view aModule;
-if ( nIdx>0 && nIdx != std::u16string_view::npos )
+if ( nIdx>0 )
{
// string contains at least 2 tokens
-nIdx = rMacro.rfind('.', nIdx - 1);
-if (nIdx != std::u16string_view::npos)
+nIdx = rMacro.lastIndexOf('.', nIdx);
+if (nIdx != -1)
{
// string contains at least 3 tokens
aLib = o3tl::getToken(rMacro, 0, '.' );
@@ -1055,45 +1048,61 @@ void CuiConfigGroupListBox::SelectMacro(
std::u16string_view rBasic,
do
{
OUString aEntryBas = m_xTreeView->get_text(*xIter);
-if (aEntryBas == aBasicName)
+if (aEntryBas == xImp->m_sDlgMacros)
{
m_xTreeView->expand_row(*xIter);
-std::unique_ptr xLibIter =
m_xTreeView->make_iterator(xIter.get());
-if (m_xTreeView->get_iter_first(*xLibIter))
+std::unique_ptr xLocationIter =
m_xTreeView->make_iterator(xIter.get());
+if (m_xTreeView->iter_children(*xLocationIter))
{
do
{
-OUString aEntryLib = m_xTreeView->get_text(*xLibIter);
-if (aEntryLib == aLib)
+m_xTreeView->expand_row(*xLocationIter);
+std::unique_ptr xLibIter =
m_xTreeView->make_iterator(xLocationIter.get());
+if (m_xTreeView->iter_children(*xLibIter))
{
-m_xTreeView->expand_row(*xLibIter);
-std::unique_ptr xModIter =
m_xTreeView->make_iterator(xLibIter.get());
-if (m_xTreeView->get_iter_first(*xModIter))
+do
{
-do
+OUString aEntryLib =
m_xTreeView->get_text(*xLibIter);
+if (aEntryLib == aLib)
{
-OUString aEntryMod =
m_xTreeView->get_text(*xModIter);
-if ( aEntryMod == aModule )
+m_xTreeView->expand_row(*xLibIter);
+std::unique_ptr xModIter =
m_xTreeView->make_iterator(xLibIter.get());
+if (m_xTreeView->iter_children(*xModIter))
{
-m_xTreeView->expand_row(*xModIter);
-
[Libreoffice-commits] core.git: Branch 'libreoffice-7-4' - vcl/source
vcl/source/filter/itiff/itiff.cxx | 20
1 file changed, 20 insertions(+)
New commits:
commit 846711ad526fcc147bb39df26bf2c2ff25a053f3
Author: Caolán McNamara
AuthorDate: Thu Oct 13 21:14:28 2022 +0100
Commit: Noel Grandin
CommitDate: Fri Oct 14 07:39:11 2022 +0200
Resolves: tdf#151468 honour tiff resolution fields
Change-Id: I57d996f49c6ae7e60991ff53eae867144b56d89d
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/141346
Tested-by: Jenkins
Reviewed-by: Noel Grandin
diff --git a/vcl/source/filter/itiff/itiff.cxx
b/vcl/source/filter/itiff/itiff.cxx
index d8895b8cff31..db30ea2cac3c 100644
--- a/vcl/source/filter/itiff/itiff.cxx
+++ b/vcl/source/filter/itiff/itiff.cxx
@@ -25,6 +25,7 @@
#include
#include
#include
+#include
#include
#include
@@ -243,6 +244,25 @@ bool ImportTiffGraphicImport(SvStream& rTIFF, Graphic&
rGraphic)
break;
}
+MapMode aMapMode;
+uint16_t ResolutionUnit = RESUNIT_NONE;
+if (TIFFGetField(tif, TIFFTAG_RESOLUTIONUNIT, ) ==
1 && ResolutionUnit != RESUNIT_NONE)
+{
+float xres = 0, yres = 0;
+
+if (TIFFGetField(tif, TIFFTAG_XRESOLUTION, ) == 1 &&
+TIFFGetField(tif, TIFFTAG_YRESOLUTION, ) == 1 &&
+xres != 0 && yres != 0)
+{
+if (ResolutionUnit == RESUNIT_INCH)
+aMapMode = MapMode(MapUnit::MapInch, Point(0,0),
Fraction(1/xres), Fraction(1/yres));
+else if (ResolutionUnit == RESUNIT_CENTIMETER)
+aMapMode = MapMode(MapUnit::MapCM, Point(0,0),
Fraction(1/xres), Fraction(1/yres));
+}
+}
+aBitmapEx.SetPrefMapMode(aMapMode);
+aBitmapEx.SetPrefSize(Size(w, h));
+
AnimationBitmap aAnimationBitmap(aBitmapEx, Point(0, 0),
aBitmapEx.GetSizePixel(),
ANIMATION_TIMEOUT_ON_CLICK,
Disposal::Back);
aAnimation.Insert(aAnimationBitmap);
[Libreoffice-commits] core.git: include/sfx2
include/sfx2/lokcomponenthelpers.hxx |4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
New commits:
commit a09c5c69e3b5fbf448cae1d6c476f39067e40023
Author: Mike Kaganski
AuthorDate: Fri Oct 14 07:40:28 2022 +0300
Commit: Mike Kaganski
CommitDate: Fri Oct 14 07:37:27 2022 +0200
This can be const
Change-Id: I5e0cb22c9276e41b0a42978a253456ebd9ebefa4
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/141356
Tested-by: Jenkins
Reviewed-by: Mike Kaganski
diff --git a/include/sfx2/lokcomponenthelpers.hxx
b/include/sfx2/lokcomponenthelpers.hxx
index 02e8750ca381..ea81ea8f87c1 100644
--- a/include/sfx2/lokcomponenthelpers.hxx
+++ b/include/sfx2/lokcomponenthelpers.hxx
@@ -66,7 +66,7 @@ public:
class SFX2_DLLPUBLIC LokStarMathHelper
{
public:
-LokStarMathHelper(SfxViewShell* pViewShell)
+LokStarMathHelper(const SfxViewShell* pViewShell)
: mpViewShell(pViewShell)
{
}
@@ -83,7 +83,7 @@ private:
css::uno::Reference& GetXController();
tools::Rectangle GetBoundingBox();
-SfxViewShell* mpViewShell;
+const SfxViewShell* mpViewShell;
css::uno::Reference mxController;
VclPtr mpGraphicWindow;
VclPtr mpWidgetWindow;
[Libreoffice-bugs] [Bug 151523] New: Margins shift left in Print, Preview, or Print to PDF
https://bugs.documentfoundation.org/show_bug.cgi?id=151523 Bug ID: 151523 Summary: Margins shift left in Print, Preview, or Print to PDF Product: LibreOffice Version: 7.4.0.3 release Hardware: All OS: macOS (All) Status: UNCONFIRMED Severity: normal Priority: medium Component: Printing and PDF export Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: dmmg_sa...@dinnerandamurder.com Created attachment 183036 --> https://bugs.documentfoundation.org/attachment.cgi?id=183036=edit 2 docs. One is Libre Office layout. Other is print. You can see it's set to the left. In Libre Office, my margins look perfectly even, yet when I either print, preview, or print to PDF, everything is shifted left quite noticeably. I first thought my printer was messed up. But then I went back in and realized the PDF was off, so I backtracked and was able to reproduce it every single time. I can select another printer and it is still off. When I open the same document in Word, it's perfectly aligned. I am attaching screenshots to show the issue. It is not printing or creating pdfs with the margins the same as those in the document. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 151521] Applying paragraph styles with sub outline-level does not become folded content
https://bugs.documentfoundation.org/show_bug.cgi?id=151521 --- Comment #1 from Jim Raykowski --- The fix for the bug patch mentioned in my last post should have been bug 151315. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-ux-advise] [Bug 67860] Auto detection of high contrast mode is easy to trigger
https://bugs.documentfoundation.org/show_bug.cgi?id=67860 V Stuart Foote changed: What|Removed |Added See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=15 ||1522 -- You are receiving this mail because: You are on the CC list for the bug.
[Libreoffice-bugs] [Bug 67860] Auto detection of high contrast mode is easy to trigger
https://bugs.documentfoundation.org/show_bug.cgi?id=67860 V Stuart Foote changed: What|Removed |Added See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=15 ||1522 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 103537] [META] High contrast mode bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=103537 V Stuart Foote changed: What|Removed |Added Depends on||151522 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=151522 [Bug 151522] Tools -> Options -> Accessibility 'Automatically detect high contrast mode' maybe needs a rework -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 151522] Tools -> Options -> Accessibility 'Automatically detect high contrast mode' maybe needs a rework
https://bugs.documentfoundation.org/show_bug.cgi?id=151522 V Stuart Foote changed: What|Removed |Added See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=67 ||860 Keywords||accessibility Summary|Tools -> Options -> |Tools -> Options -> |Accessibility |Accessibility |'Automatically detect high |'Automatically detect high |contrast mode' |contrast mode' maybe needs ||a rework Blocks||103537 CC||caol...@redhat.com, ||vstuart.fo...@utsa.edu Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=103537 [Bug 103537] [META] High contrast mode bugs and enhancements -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 149853] Impress Screensaver Activates During RDP Even With User Input
https://bugs.documentfoundation.org/show_bug.cgi?id=149853 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 145969] divide common settings from object-specific settings in 'Position And Size' dialog
https://bugs.documentfoundation.org/show_bug.cgi?id=145969 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 151224] macOS: LibreOffice doesn't open files opened via vnd.libreoffice.command
https://bugs.documentfoundation.org/show_bug.cgi?id=151224 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 151474] Allow formatting footnotes in columns or separated by spaces
https://bugs.documentfoundation.org/show_bug.cgi?id=151474 QA Administrators changed: What|Removed |Added Ever confirmed|1 |0 Status|NEEDINFO|UNCONFIRMED -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 151474] Allow formatting footnotes in columns or separated by spaces
https://bugs.documentfoundation.org/show_bug.cgi?id=151474 --- Comment #5 from QA Administrators --- [Automated Action] NeedInfo-To-Unconfirmed -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 151200] LibreOffice freezes when opening the SAVE dialog in a Text Document in Mac
https://bugs.documentfoundation.org/show_bug.cgi?id=151200 QA Administrators changed: What|Removed |Added Status|NEEDINFO|UNCONFIRMED Ever confirmed|1 |0 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 151200] LibreOffice freezes when opening the SAVE dialog in a Text Document in Mac
https://bugs.documentfoundation.org/show_bug.cgi?id=151200 --- Comment #5 from QA Administrators --- [Automated Action] NeedInfo-To-Unconfirmed -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 142783] SELECTING Date Field dropdown causes 'When losing focus' event.
https://bugs.documentfoundation.org/show_bug.cgi?id=142783 QA Administrators changed: What|Removed |Added Ever confirmed|1 |0 Status|NEEDINFO|UNCONFIRMED -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 142783] SELECTING Date Field dropdown causes 'When losing focus' event.
https://bugs.documentfoundation.org/show_bug.cgi?id=142783 --- Comment #9 from QA Administrators --- [Automated Action] NeedInfo-To-Unconfirmed -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 87838] India state names not in spelling dictionary
https://bugs.documentfoundation.org/show_bug.cgi?id=87838 --- Comment #7 from QA Administrators --- Dear Abinesh S, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 90458] FORMATTING: When a row selection includes a merged column, only border changes which are specific to the row are applied
https://bugs.documentfoundation.org/show_bug.cgi?id=90458 --- Comment #6 from QA Administrators --- Dear Matthew Millar, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 46506] Libreoffice does not install some basic help control elements with --without-help
https://bugs.documentfoundation.org/show_bug.cgi?id=46506 --- Comment #17 from QA Administrators --- Dear Tomáš Chvátal, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 35107] A hyperlink in writer document doesn't expose correct role and URL to AT-SPI.
https://bugs.documentfoundation.org/show_bug.cgi?id=35107 --- Comment #18 from QA Administrators --- Dear Dattatray Bhat, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 132917] Table doesn't split properly, if allow table to split across pages and columns disabled for embedded table
https://bugs.documentfoundation.org/show_bug.cgi?id=132917 --- Comment #3 from QA Administrators --- Dear Telesto, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 133344] Slow scrolling through preview pages with large complex file
https://bugs.documentfoundation.org/show_bug.cgi?id=133344 --- Comment #6 from QA Administrators --- Dear Telesto, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 132954] Comment point to the wrong area after undo (file reload solves the issue)
https://bugs.documentfoundation.org/show_bug.cgi?id=132954 --- Comment #5 from QA Administrators --- Dear Telesto, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 132915] Missing cell border line after deleting a row above of a row with merged cells
https://bugs.documentfoundation.org/show_bug.cgi?id=132915 --- Comment #4 from QA Administrators --- Dear Telesto, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 129701] Skip empty cells option does not work in Calc Text Import dialog
https://bugs.documentfoundation.org/show_bug.cgi?id=129701 --- Comment #12 from QA Administrators --- Dear NISZ LibreOffice Team, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 108115] Merging registry modules can overflow
https://bugs.documentfoundation.org/show_bug.cgi?id=108115 --- Comment #6 from QA Administrators --- Dear Chris Sherlock, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 107967] System path on Unix starting with double-slashes converted to single slash
https://bugs.documentfoundation.org/show_bug.cgi?id=107967 --- Comment #7 from QA Administrators --- Dear Chris Sherlock, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 107092] [crash] Writer Forms - real problems: formating text, option-checkbox, background-colours
https://bugs.documentfoundation.org/show_bug.cgi?id=107092 --- Comment #12 from QA Administrators --- Dear Thomas Krumbein, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 105980] Filter lost the Regular expression after saving
https://bugs.documentfoundation.org/show_bug.cgi?id=105980 --- Comment #6 from QA Administrators --- Dear Juergen Funk (CIB), To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 151522] New: Tools -> Options -> Accessibility 'Automatically detect high contrast mode'
https://bugs.documentfoundation.org/show_bug.cgi?id=151522 Bug ID: 151522 Summary: Tools -> Options -> Accessibility 'Automatically detect high contrast mode' Product: LibreOffice Version: 7.5.0.0 alpha0+ Master Hardware: All OS: Windows (All) Status: UNCONFIRMED Severity: normal Priority: medium Component: UI Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: vstuart.fo...@utsa.edu The Tools -> Options -> Accessibility 'Automatically detect high contrast mode of operating system' was toggled to disabled by default for bug 67860 With recent work to bring Dark color theme support to Windows builds, and improvements to the High Contrast (HC) handling, we need to ask if we are still doing the right thing for Assistive Technology by disabling the HC detection by default. As on the Linux os/DE previously, with the checkbox enabled on Windows 10 in Dark color mode the HC toggle triggers. The icon theme changes to Sifr; UI element colors are "reduced" for HC mode support. While this is the correct accommodation for HC Assistive Technology, it is not really wanted for the normal user choosing a dark os/DE. On the other hand its presence on the Tools -> Options -> Accessibility panel is not a very "discoverable" location for the user in need of Assistive Technology support. Disabling the HC detection was probably OK at the time as the Windows pool of users was not really affected. But with recent improvement, it seems our "detection" of intentional HC mode of an os/DE needs to be made more nuanced and to do a better job. And to allow the mode to be set by default, as needed for Assistive Technology, but avoid switching LO into HC mode for those not intending it to be across the os/DE. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 148459] Spreadsheet selection misbehaves after element selected from cell data-validity dropdown
https://bugs.documentfoundation.org/show_bug.cgi?id=148459 wajohn...@comcast.net changed: What|Removed |Added Status|NEW |RESOLVED Resolution|--- |FIXED --- Comment #6 from wajohn...@comcast.net --- Yes, this bug can be closed. thank you. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 103537] [META] High contrast mode bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=103537 Bug 103537 depends on bug 98032, which changed state. Bug 98032 Summary: Only partly high-contrast-mode (accessibility) support https://bugs.documentfoundation.org/show_bug.cgi?id=98032 What|Removed |Added Status|NEW |RESOLVED Resolution|--- |WORKSFORME -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 98032] Only partly high-contrast-mode (accessibility) support
https://bugs.documentfoundation.org/show_bug.cgi?id=98032 V Stuart Foote changed: What|Removed |Added Resolution|--- |WORKSFORME Status|NEW |RESOLVED --- Comment #8 from V Stuart Foote --- This is now corrected for the 7.4 release (experimental) and by default at 7.5 Run on Windows 10 or Windows 11 LibreOffice automatic color values will follow closely the WDM desktop themes, including High Contrast (#1, #2, Black & White). -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 151473] Draw PDF import: ASCII brackets (e.g. (), [] etc) are reversed when the paragraph is RTL
https://bugs.documentfoundation.org/show_bug.cgi?id=151473 --- Comment #2 from Kevin Suo --- Copy pasting my comment in https://gerrit.libreoffice.org/c/core/+/141231: ''' The issue in tdf151473 is another issue, that was in the xpdfimport part (i.e. the GPL code in sdext/source/pdfimport/xpdfwrapper, which uses the third-party library "poppler" to process the pdf and yield xpdf tokens, then the tokens are passed to the sdext/source/pdfimport/wrapper and then further to sdext/source/pdfimport/tree to generate an ODF XML tree before it appears in Draw). That bug was not caused by the reverseString code in drawtreevisiting.cxx. This can be observed when you run: $ ./instdir/program/xpdfimport sdext/source/pdfimport/test/testdocs/tdf104597_textrun.pdf -f /dev/null and you get: drawChar 145.05 709.189000 163.822000 709.189000 1.00 0.00 0.00 1.00 26.00 A drawChar 163.822000 709.189000 181.138000 709.189000 1.00 0.00 0.00 1.00 26.00 B drawChar 181.112000 709.189000 198.428000 709.189000 1.00 0.00 0.00 1.00 26.00 C drawChar 198.428000 709.189000 207.086000 709.189000 1.00 0.00 0.00 1.00 26.00 ) drawChar 207.086000 709.189000 213.586000 709.189000 1.00 0.00 0.00 1.00 26.00 drawChar 213.586000 709.189000 232.358000 709.189000 1.00 0.00 0.00 1.00 26.00 D drawChar 232.358000 709.189000 248.218000 709.189000 1.00 0.00 0.00 1.00 26.00 E drawChar 248.244000 709.189000 262.70 709.189000 1.00 0.00 0.00 1.00 26.00 F drawChar 136.10 709.189000 145.044000 709.189000 1.00 0.00 0.00 1.00 26.00 ) when sorted by the 2nd column (which is the horizontal position of the character), we get: drawChar 136.10 709.189000 145.044000 709.189000 1.00 0.00 0.00 1.00 26.00 ) drawChar 145.05 709.189000 163.822000 709.189000 1.00 0.00 0.00 1.00 26.00 A drawChar 163.822000 709.189000 181.138000 709.189000 1.00 0.00 0.00 1.00 26.00 B drawChar 181.112000 709.189000 198.428000 709.189000 1.00 0.00 0.00 1.00 26.00 C drawChar 198.428000 709.189000 207.086000 709.189000 1.00 0.00 0.00 1.00 26.00 ) drawChar 207.086000 709.189000 213.586000 709.189000 1.00 0.00 0.00 1.00 26.00 drawChar 213.586000 709.189000 232.358000 709.189000 1.00 0.00 0.00 1.00 26.00 D drawChar 232.358000 709.189000 248.218000 709.189000 1.00 0.00 0.00 1.00 26.00 E drawChar 248.244000 709.189000 262.70 709.189000 1.00 0.00 0.00 1.00 26.00 F which when combined, is: ")ABC) DEF", while we expect it to be "(ABC) DEF". In other words, the tokens returned by xpdfimport is already wrong. It is also wrong even if a paragraph is set to RTL direction with pure ASCII characters with brackets. This may due to a bug in poppler, or be a bug in the sdext/source/pdfimport/xpdfwrapper wrapper codes. Thus this should be fixed separately. ''' > We're using ICU Libs BiDi for detection of RTL to trigger collection of the > run. As far as I know, we are not using ICU's BiDi in sdext/pdfimport. > But isn't this to be expected. If we have "(ABC) DEF" shown in the PDF, then we would expect "(ABC) DEF" if open it in Draw. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 149462] Treat pure ASCII files (codes 0-127) as UTF-8 without BOM on import by default
https://bugs.documentfoundation.org/show_bug.cgi?id=149462 RezzyA changed: What|Removed |Added Status|NEW |ASSIGNED Assignee|libreoffice-b...@lists.free |bonfromag...@outlook.com |desktop.org | --- Comment #6 from RezzyA --- I am starting work on this bug. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 151521] New: Applying paragraph styles with sub outline-level does not become folded content
https://bugs.documentfoundation.org/show_bug.cgi?id=151521 Bug ID: 151521 Summary: Applying paragraph styles with sub outline-level does not become folded content Product: LibreOffice Version: 7.5.0.0 alpha0+ Master Hardware: All OS: All Status: UNCONFIRMED Severity: normal Priority: medium Component: Writer Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: rayk...@gmail.com Created attachment 183035 --> https://bugs.documentfoundation.org/attachment.cgi?id=183035=edit Steps to repro bug Ah, that's what the line of code removed by the fix for bug 151387 was there for... Steps to repro are given in the attached STR bug file. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 151474] Allow formatting footnotes in columns or separated by spaces
https://bugs.documentfoundation.org/show_bug.cgi?id=151474 --- Comment #4 from Seán Ó Séaghdha --- How will attaching a sample file help when this is something you cannot do with Writer? -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 151473] Draw PDF import: ASCII brackets (e.g. (), [] etc) are reversed when the paragraph is RTL
https://bugs.documentfoundation.org/show_bug.cgi?id=151473 V Stuart Foote changed: What|Removed |Added CC||jl...@mail.com, ||kha...@aliftype.com, ||t...@libreoffice.org, ||vstuart.fo...@utsa.edu, ||vv...@yandex.ru --- Comment #1 from V Stuart Foote --- But isn't this to be expected. We're using ICU Libs BiDi for detection of RTL to trigger collection of the run. [1] But then use no other logic to parse the weakly typed Open punctuation and Close punctuation for the rest of the run to keep it ordered when other scripts are encountered. In the example looks like we're finishing a run of RTL with closing bracket and the entering the western text, and finally entering a closing parenthesis when passing back into RTL. IIRC similar issues Open & Close punctuation in CJK runs passing between runs of Chinese and parenthetically embedded English. =-ref-= [1] https://opengrok.libreoffice.org/xref/core/sdext/source/pdfimport/tree/drawtreevisiting.cxx?r=69e9925d#108 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 151520] Context menu missing to clear recent documents
https://bugs.documentfoundation.org/show_bug.cgi?id=151520 xordevore...@gmail.com changed: What|Removed |Added OS|All |Windows (All) Hardware|All |x86-64 (AMD64) CC||xordevore...@gmail.com -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 151520] New: Context menu missing to clear recent documents
https://bugs.documentfoundation.org/show_bug.cgi?id=151520 Bug ID: 151520 Summary: Context menu missing to clear recent documents Product: LibreOffice Version: 7.5.0.0 alpha0+ Master Hardware: All OS: All Status: UNCONFIRMED Severity: normal Priority: medium Component: Draw Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: xordevore...@gmail.com Description: LO Draw's Recent Documents context menu is available in 4.x but is completely missing in the latest version of 5.x alpha. I don't want to wade through a sea of recent documents to start clearing them one by one. It's available under File... / Recent Documents / Clear list but the button the on the side panel has changed to now there's no context menu to do the same thing and instead toggles between recent documents and templates. Steps to Reproduce: 1. Launch LO draw in Microsoft Windows 2. Create and save a couple of documents 3. Examine the "Recent Documents" option on the far left of the menu. It lacks a drop-down for clearing recent documents. Actual Results: Must remove recent documents one by one because there is no longer a context menu to clear them all at once. Expected Results: Restoration of the context menu on the left side panel for Recent Documents to clear the list. Reproducible: Always User Profile Reset: No Additional Info: Version: 7.5.0.0.alpha0+ (x64) / LibreOffice Community Build ID: aca7edb4ca7fd58c50a6b64b472e80f2eb053fd5 CPU threads: 8; OS: Windows 10.0 Build 19044; UI render: Skia/Vulkan; VCL: win Locale: en-US (en_US); UI: en-US Calc: CL threaded -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 150522] default dialog box size for Options cuts off fields on the right of the dialog
https://bugs.documentfoundation.org/show_bug.cgi?id=150522 --- Comment #5 from xordevore...@gmail.com --- Created attachment 183034 --> https://bugs.documentfoundation.org/attachment.cgi?id=183034=edit Screencap Still happening in: Version: 7.5.0.0.alpha0+ (x64) / LibreOffice Community Build ID: aca7edb4ca7fd58c50a6b64b472e80f2eb053fd5 CPU threads: 8; OS: Windows 10.0 Build 19044; UI render: Skia/Vulkan; VCL: win Locale: en-US (en_US); UI: en-US Calc: CL threaded -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 151205] New Paste Special Operations: Maximum, Minimum
https://bugs.documentfoundation.org/show_bug.cgi?id=151205 --- Comment #12 from Robert Lacroix --- (In reply to Heiko Tietze from comment #10) > We discussed the topic briefly in the design meeting. > > What I understand is that you copy a range like A1:A5 and paste it onto the > same range at B1:B5 with the expectation to either use the minimum or > maximum of both. Use case is to find the minimum temperature or the highest > value of a blood pressure. > > The terms Min/Max are a bit misleading since it is an attribute of a > distribution. You rather ask for Lower/Higher, which would be unclear in > itself too. > > Putting all comments together the concerns about too many operations > predominate and the recommendation is to implement the feature via extension. > > Although I'm closing the ticket as WF please feel free to reopen. As a open > source project any volunteer is free to submit patches - and I guess it > would be accepted despite the concerns from the UX POV. "Greater of/Lesser of" might work. But that's just English semantics. I can't imagine what it would be with other locale settings. It might be very clear in some other languages. Semantics can be very challenging when context is missing. In Tagalog there are 2 different words for the English word "we": inclusive of the person being spoken to, or exclusive; it has clarity without context. If we can make things clear without regard to the language, then we have a good UX design. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-ux-advise] [Bug 151205] New Paste Special Operations: Maximum, Minimum
https://bugs.documentfoundation.org/show_bug.cgi?id=151205 --- Comment #12 from Robert Lacroix --- (In reply to Heiko Tietze from comment #10) > We discussed the topic briefly in the design meeting. > > What I understand is that you copy a range like A1:A5 and paste it onto the > same range at B1:B5 with the expectation to either use the minimum or > maximum of both. Use case is to find the minimum temperature or the highest > value of a blood pressure. > > The terms Min/Max are a bit misleading since it is an attribute of a > distribution. You rather ask for Lower/Higher, which would be unclear in > itself too. > > Putting all comments together the concerns about too many operations > predominate and the recommendation is to implement the feature via extension. > > Although I'm closing the ticket as WF please feel free to reopen. As a open > source project any volunteer is free to submit patches - and I guess it > would be accepted despite the concerns from the UX POV. "Greater of/Lesser of" might work. But that's just English semantics. I can't imagine what it would be with other locale settings. It might be very clear in some other languages. Semantics can be very challenging when context is missing. In Tagalog there are 2 different words for the English word "we": inclusive of the person being spoken to, or exclusive; it has clarity without context. If we can make things clear without regard to the language, then we have a good UX design. -- You are receiving this mail because: You are on the CC list for the bug.
[Libreoffice-ux-advise] [Bug 151205] New Paste Special Operations: Maximum, Minimum
https://bugs.documentfoundation.org/show_bug.cgi?id=151205 --- Comment #11 from Robert Lacroix --- (In reply to Cor Nouws from comment #9) > (In reply to Robert Lacroix from comment #8) > > > In exactly the same way. The operation between cells in the copied range > > (source) is performed with cells in the destination range. The dimensions of > > the source and destination ranges are the same, or the source range is a > > single cell and the destination has multiple cells. > > So I copy a value, say 3. > Then select a range with 4 cells, values 4, 6, 8, 5 > Paste > Special > Max. > > Then? After the processing is done, there is no change to the destination range, they are all already more than 3. There's nothing special about this - you would get a "no change" result if the copied value is 0 and the operation is Paste > Special > Add. -- You are receiving this mail because: You are on the CC list for the bug.
[Libreoffice-bugs] [Bug 151205] New Paste Special Operations: Maximum, Minimum
https://bugs.documentfoundation.org/show_bug.cgi?id=151205 --- Comment #11 from Robert Lacroix --- (In reply to Cor Nouws from comment #9) > (In reply to Robert Lacroix from comment #8) > > > In exactly the same way. The operation between cells in the copied range > > (source) is performed with cells in the destination range. The dimensions of > > the source and destination ranges are the same, or the source range is a > > single cell and the destination has multiple cells. > > So I copy a value, say 3. > Then select a range with 4 cells, values 4, 6, 8, 5 > Paste > Special > Max. > > Then? After the processing is done, there is no change to the destination range, they are all already more than 3. There's nothing special about this - you would get a "no change" result if the copied value is 0 and the operation is Paste > Special > Add. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 151519] New: LibreOffice Writer Ruler (set to inches) won't display sub-inch tick-marks.
https://bugs.documentfoundation.org/show_bug.cgi?id=151519 Bug ID: 151519 Summary: LibreOffice Writer Ruler (set to inches) won't display sub-inch tick-marks. Product: LibreOffice Version: 7.4.1.2 release Hardware: x86-64 (AMD64) OS: Linux (All) Status: UNCONFIRMED Severity: normal Priority: medium Component: Writer Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: gfran...@mail.com Created attachment 183033 --> https://bugs.documentfoundation.org/attachment.cgi?id=183033=edit rulers shown for writer version 6.4.7.2 and writer version 7.4.1.2 It works properly in Writer version 6.4.7.2 but not for writer version 7.4.1.2, and makes it difficult to properly set tabs visually by dragging the tab marks on the ruler. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 151504] Navigator sidebar
https://bugs.documentfoundation.org/show_bug.cgi?id=151504 Rafael Lima changed: What|Removed |Added Ever confirmed|1 |0 Status|NEEDINFO|UNCONFIRMED --- Comment #3 from Rafael Lima --- So I tested the same layout and editing the document did not change the height of the sidebar. However I'm on Linux (more specifically KDE) and this may be related to how MS Windows manage its windows. Let's wait and see if anyone else can confirm this issue. Tested with Version: 7.5.0.0.alpha0+ / LibreOffice Community Build ID: 7fc96ad09520abea4833ed7410fd3a2d1b63d7b1 CPU threads: 16; OS: Linux 5.15; UI render: default; VCL: kf5 (cairo+xcb) Locale: pt-BR (pt_BR.UTF-8); UI: en-US Calc: CL threaded -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 151518] FILEOPEN DOCX Text is wrongly placed in some SmartArt types
https://bugs.documentfoundation.org/show_bug.cgi?id=151518 Regina Henschel changed: What|Removed |Added Summary|FILEOPEN DOCX Text is |FILEOPEN DOCX Text is |wrongly plaaced in some |wrongly placed in some |SmartArt types |SmartArt types -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 151518] New: FILEOPEN DOCX Text is wrongly plaaced in some SmartArt types
https://bugs.documentfoundation.org/show_bug.cgi?id=151518 Bug ID: 151518 Summary: FILEOPEN DOCX Text is wrongly plaaced in some SmartArt types Product: LibreOffice Version: 7.4.1.2 release Hardware: x86-64 (AMD64) OS: Windows (All) Status: UNCONFIRMED Severity: normal Priority: medium Component: Writer Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: rb.hensc...@t-online.de Created attachment 183032 --> https://bugs.documentfoundation.org/attachment.cgi?id=183032=edit Example for the problem Check option "SmartArt to LibreOffice shapes or reverse" in Tools > Options > Load/Save > Microsoft Office. Open attached document. It contains a SmartArt shape and a picture, how it looks in Word. The red rectangles are semitransparent to allow to see the text of the blue shapes in case it is behind the red rectangles. The fix for bug 148321 has introduced, that the position of the text considers the special way Microsoft Office calculates it, in case a vertical distance to text is so large, that the text is outside the text area. That works fine for shapes in PowerPoint. But it conflicts with text in SmartArt in Writer. Reason is, that the calculation in TextBodyPropertiew::readjustTextDistances() uses the text area rectangle of the SdrObjCustomShape. These values are used in expressions with text distances. But in Writer text area rectangle is in Twips whereas the text distances at import time are in Hmm. So the special calculation is triggered, although in fact there is no such situation. The problem is not visible with normal shapes in Word, because Word does not allow to use so large distances. You can enter such values, but the overflowing text is not displayed in Word. SmartArts would not need this special corrections, because TextBodyProperties::pushTextDistances() already results in correct text location. Unfortunately I see no easy way to exclude SmartArt shapes in Writer from using TextBodyPropertiew::readjustTextDistances(). Effected are those SmartArt types which use the text distances to shift the text from its center position up or down. I have not inspected all types, but see the problem with types "Target List", "Nested Target", "Stacked Venn" and "Grouped List" so far. This is not a regression from the fix for bug 148321 because before the fix the text position was wrong too, albeit in a different way. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 150228] Libre office freezes and then completely shuts down
https://bugs.documentfoundation.org/show_bug.cgi?id=150228 --- Comment #2 from Rajasekaran Karunanithi --- Can't reproduce in LO 7.4.1.2 build :3c58a8f3a960df8bc8fd77b461821e42c061c5f0. Works fine. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 150776] WINDOWS .txt File —— Right-click —— Open way —— two useless icons
https://bugs.documentfoundation.org/show_bug.cgi?id=150776 Rajasekaran Karunanithi changed: What|Removed |Added Status|NEEDINFO|UNCONFIRMED Ever confirmed|1 |0 --- Comment #5 from Rajasekaran Karunanithi --- Still reproducable in LO 7.4.1.2 build:3c58a8f3a960df8bc8fd77b461821e42c061c5f0. I attached the screenshot in previous message. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 151517] [DOCX] Table that spans 2 pages in MS Word results in just one page in Writer
https://bugs.documentfoundation.org/show_bug.cgi?id=151517 Rafael Lima changed: What|Removed |Added Blocks||10 Keywords||filter:docx Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=10 [Bug 10] [META] DOCX (OOXML) table-related issues -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-commits] core.git: sc/qa
sc/qa/unit/scshapetest.cxx | 215 ++---
1 file changed, 108 insertions(+), 107 deletions(-)
New commits:
commit 8991cbb7986d3967bc6c3719d95254ff04428d1a
Author: Xisco Fauli
AuthorDate: Thu Oct 13 18:06:17 2022 +0200
Commit: Xisco Fauli
CommitDate: Fri Oct 14 00:30:40 2022 +0200
CppunitTest_sc_shapetest: use member XComponent
Change-Id: If881b238991cfce8d866edd662fb6eb70c8f29a6
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/141336
Tested-by: Jenkins
Reviewed-by: Xisco Fauli
diff --git a/sc/qa/unit/scshapetest.cxx b/sc/qa/unit/scshapetest.cxx
index 299ef1f1290e..ac01be437101 100644
--- a/sc/qa/unit/scshapetest.cxx
+++ b/sc/qa/unit/scshapetest.cxx
@@ -42,8 +42,7 @@ class ScShapeTest : public CalcUnoApiTest
{
public:
ScShapeTest();
-void saveAndReload(css::uno::Reference& xComponent,
- const OUString& rFilter);
+void saveAndReload(const OUString& rFilter);
void testTdf143619_validation_circle_pos();
void testTdf140252_DragCreateFormControl();
void testTdf134355_DragCreateCustomShape();
@@ -97,6 +96,9 @@ public:
CPPUNIT_TEST(testTdf144242_OpenBezier_noSwapWH);
CPPUNIT_TEST(testLargeAnchorOffset);
CPPUNIT_TEST_SUITE_END();
+
+private:
+uno::Reference mxComponent;
};
ScShapeTest::ScShapeTest()
@@ -104,19 +106,18 @@ ScShapeTest::ScShapeTest()
{
}
-void ScShapeTest::saveAndReload(css::uno::Reference&
xComponent,
-const OUString& rFilter)
+void ScShapeTest::saveAndReload(const OUString& rFilter)
{
utl::TempFileNamed aTempFile;
aTempFile.EnableKillingFile();
css::uno::Sequence aArgs{ comphelper::makePropertyValue("FilterName",
rFilter) }; //
e.g. "calc8"
-css::uno::Reference xStorable(xComponent,
css::uno::UNO_QUERY_THROW);
+css::uno::Reference xStorable(mxComponent,
css::uno::UNO_QUERY_THROW);
xStorable->storeAsURL(aTempFile.GetURL(), aArgs);
-css::uno::Reference xCloseable(xComponent,
css::uno::UNO_QUERY_THROW);
+css::uno::Reference xCloseable(mxComponent,
css::uno::UNO_QUERY_THROW);
xCloseable->close(true);
-xComponent = loadFromDesktop(aTempFile.GetURL(),
"com.sun.star.sheet.SpreadsheetDocument");
+mxComponent = loadFromDesktop(aTempFile.GetURL(),
"com.sun.star.sheet.SpreadsheetDocument");
}
static void lcl_AssertRectEqualWithTolerance(std::string_view sInfo,
@@ -209,11 +210,11 @@ void ScShapeTest::testTdf144242_OpenBezier_noSwapWH()
// swapped, because they report a rotation. (Rotation was introduced to
align text with curve.)
// Create a spreadsheet document with default row height and col width
-uno::Reference xComponent
+mxComponent
= loadFromDesktop("private:factory/scalc",
"com.sun.star.sheet.SpreadsheetDocument");
// Get ScDocShell
-ScDocShell* pDocSh = lcl_getScDocShellWithAssert(xComponent);
+ScDocShell* pDocSh = lcl_getScDocShellWithAssert(mxComponent);
// Insert default open Bezier curve
ScTabViewShell* pTabViewShell = lcl_getScTabViewShellWithAssert(pDocSh);
@@ -232,8 +233,8 @@ void ScShapeTest::testTdf144242_OpenBezier_noSwapWH()
tools::Rectangle aExpectRect(pObj->GetSnapRect());
// Save, reload and compare
-saveAndReload(xComponent, "Calc Office Open XML");
-pDocSh = lcl_getScDocShellWithAssert(xComponent);
+saveAndReload("Calc Office Open XML");
+pDocSh = lcl_getScDocShellWithAssert(mxComponent);
ScDocument& rDoc2 = pDocSh->GetDocument();
pObj = lcl_getSdrObjectWithAssert(rDoc2, 0);
tools::Rectangle aSnapRect(pObj->GetSnapRect());
@@ -249,11 +250,11 @@ void ScShapeTest::testTdf144242_Line_noSwapWH()
// swapped, because they report a rotation. (Rotation was introduced to
align text with line.)
// Create a spreadsheet document with default row height and col width
-uno::Reference xComponent
+mxComponent
= loadFromDesktop("private:factory/scalc",
"com.sun.star.sheet.SpreadsheetDocument");
// Get ScDocShell
-ScDocShell* pDocSh = lcl_getScDocShellWithAssert(xComponent);
+ScDocShell* pDocSh = lcl_getScDocShellWithAssert(mxComponent);
// Insert default line
ScTabViewShell* pTabViewShell = lcl_getScTabViewShellWithAssert(pDocSh);
@@ -272,8 +273,8 @@ void ScShapeTest::testTdf144242_Line_noSwapWH()
tools::Rectangle aExpectRect(pObj->GetSnapRect());
// Save, reload and compare
-saveAndReload(xComponent, "Calc Office Open XML");
-pDocSh = lcl_getScDocShellWithAssert(xComponent);
+saveAndReload("Calc Office Open XML");
+pDocSh = lcl_getScDocShellWithAssert(mxComponent);
ScDocument& rDoc2 = pDocSh->GetDocument();
pObj = lcl_getSdrObjectWithAssert(rDoc2, 0);
tools::Rectangle aSnapRect(pObj->GetSnapRect());
@@ -289,10 +290,10 @@ void ScShapeTest::testTdf143619_validation_circle_pos()
[Libreoffice-bugs] [Bug 150776] WINDOWS .txt File —— Right-click —— Open way —— two useless icons
https://bugs.documentfoundation.org/show_bug.cgi?id=150776 --- Comment #4 from Rajasekaran Karunanithi --- Created attachment 183031 --> https://bugs.documentfoundation.org/attachment.cgi?id=183031=edit Shows two Libre offices -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 104444] [META] DOCX (OOXML) table-related issues
https://bugs.documentfoundation.org/show_bug.cgi?id=10 Rafael Lima changed: What|Removed |Added Depends on||151517 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=151517 [Bug 151517] [DOCX] Table that spans 2 pages in MS Word results in just one page in Writer -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 151517] New: [DOCX] Table that spans 2 pages in MS Word results in just one page in Writer
https://bugs.documentfoundation.org/show_bug.cgi?id=151517 Bug ID: 151517 Summary: [DOCX] Table that spans 2 pages in MS Word results in just one page in Writer Product: LibreOffice Version: 7.2.7.2 release Hardware: All OS: All Status: UNCONFIRMED Severity: normal Priority: medium Component: Writer Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: rafael.palma.l...@gmail.com Created attachment 183030 --> https://bugs.documentfoundation.org/attachment.cgi?id=183030=edit DOCX file where the problem occurs Open the attached DOCX file. It has a table with many lines that require 2 pages to be fully visible. 1) Opening this file in MS Word will result in 2 pages 2) Opening this file in LO Writer will show only one page and not all table rows will be accessible. System info Version: 7.2.7.2 / LibreOffice Community Build ID: 8d71d29d553c0f7dcbfa38fbfda25ee34cce99a2 CPU threads: 16; OS: Linux 5.15; UI render: default; VCL: kf5 (cairo+xcb) Locale: pt-BR (pt_BR.UTF-8); UI: en-US Calc: CL Also repro in latest master Version: 7.5.0.0.alpha0+ / LibreOffice Community Build ID: 7fc96ad09520abea4833ed7410fd3a2d1b63d7b1 CPU threads: 16; OS: Linux 5.15; UI render: default; VCL: kf5 (cairo+xcb) Locale: pt-BR (pt_BR.UTF-8); UI: en-US Calc: CL threaded -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 151504] Navigator sidebar
https://bugs.documentfoundation.org/show_bug.cgi?id=151504 --- Comment #2 from Louise --- Created attachment 183029 --> https://bugs.documentfoundation.org/attachment.cgi?id=183029=edit Suggestion - screenshots on what is happening re navigation Hi Rafael, Thanks for you quick response. Here are comparison screenshots - I have redacted the file name for privacy. I would be so grateful if you can find a fix for this as I love having both page and style navigation open simultaneously. Note I have tried reversing the set-up - less workable for me. Best regards, Louise -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 104597] RTL script text runs are reversed on PDF import, PDFIProcessor::mirrorString misbehaving
https://bugs.documentfoundation.org/show_bug.cgi?id=104597 --- Comment #83 from Eyal Rozenberg --- (In reply to Kevin Suo from comment #78) > https://gerrit.libreoffice.org/c/core/+/141231 > > should be a fix. Could someone review and test. I will try this out when it makes a nightly. However - could you explain why this was not considered to be a fix so far? Thorsten seemed to suggest that this was more complicated than one might think because of various implications I did not have the time to ask him about. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 43808] [META] Right-To-Left and Complex Text Layout language issues (RTL/CTL)
https://bugs.documentfoundation.org/show_bug.cgi?id=43808 Eyal Rozenberg changed: What|Removed |Added Depends on||151473 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=151473 [Bug 151473] Draw PDF import: ASCII brackets (e.g. (), [] etc) are reversed when the paragraph is RTL -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 151473] Draw PDF import: ASCII brackets (e.g. (), [] etc) are reversed when the paragraph is RTL
https://bugs.documentfoundation.org/show_bug.cgi?id=151473 Eyal Rozenberg changed: What|Removed |Added Blocks||43808 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=43808 [Bug 43808] [META] Right-To-Left and Complex Text Layout language issues (RTL/CTL) -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-commits] dev-tools.git: test-bugzilla-files/new-control.py
test-bugzilla-files/new-control.py |2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
New commits:
commit e2cd0bff8726fad5c3971a00a75be628a60eeb75
Author: Gabor Kelemen
AuthorDate: Thu Oct 13 22:09:03 2022 +0200
Commit: Caolán McNamara
CommitDate: Thu Oct 13 23:49:38 2022 +0200
Use CRASHTESTDATA here as well
otherwise it does not find the files under a non-default root dir
Change-Id: I50790aa5acea8cba4484528cf3ce37b418e3699d
Reviewed-on: https://gerrit.libreoffice.org/c/dev-tools/+/141343
Reviewed-by: Caolán McNamara
Tested-by: Caolán McNamara
diff --git a/test-bugzilla-files/new-control.py
b/test-bugzilla-files/new-control.py
index 1b68127..60010ca 100644
--- a/test-bugzilla-files/new-control.py
+++ b/test-bugzilla-files/new-control.py
@@ -169,7 +169,7 @@ if __name__ == "__main__":
else:
print('%r successfully passed' % (task))
-exported_files = get_list_of_files(os.environ["CRASHTESTDATA"] +
"/current/srv/crashtestdata/files/")
+exported_files = get_list_of_files(os.environ["CRASHTESTDATA"] +
"/current/" + os.environ["CRASHTESTDATA"] + "/files/")
checkDiskSpace()
if os.getenv('SAVEPREVIOUSSTATE'):
[Libreoffice-bugs] [Bug 99746] [META] PDF import filter in Draw
https://bugs.documentfoundation.org/show_bug.cgi?id=99746 Bug 99746 depends on bug 104597, which changed state. Bug 104597 Summary: RTL script text runs are reversed on PDF import, PDFIProcessor::mirrorString misbehaving https://bugs.documentfoundation.org/show_bug.cgi?id=104597 What|Removed |Added Status|NEW |RESOLVED Resolution|--- |FIXED -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 149457] Arabic Text Scrambled and Unreadable in PDF Files Opened by LibreOffice Draw
https://bugs.documentfoundation.org/show_bug.cgi?id=149457 Bug 149457 depends on bug 104597, which changed state. Bug 104597 Summary: RTL script text runs are reversed on PDF import, PDFIProcessor::mirrorString misbehaving https://bugs.documentfoundation.org/show_bug.cgi?id=104597 What|Removed |Added Status|NEW |RESOLVED Resolution|--- |FIXED -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 43808] [META] Right-To-Left and Complex Text Layout language issues (RTL/CTL)
https://bugs.documentfoundation.org/show_bug.cgi?id=43808 Bug 43808 depends on bug 104597, which changed state. Bug 104597 Summary: RTL script text runs are reversed on PDF import, PDFIProcessor::mirrorString misbehaving https://bugs.documentfoundation.org/show_bug.cgi?id=104597 What|Removed |Added Status|NEW |RESOLVED Resolution|--- |FIXED -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 104597] RTL script text runs are reversed on PDF import, PDFIProcessor::mirrorString misbehaving
https://bugs.documentfoundation.org/show_bug.cgi?id=104597 Kevin Suo changed: What|Removed |Added Status|NEW |RESOLVED Resolution|--- |FIXED --- Comment #82 from Kevin Suo --- This is now fixed on master branch. There is another issue in bug 151473. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 149590] LibreOffice Writer 7.2.4.1 or later hangs under macOS 10.13.6 (High Sierra)
https://bugs.documentfoundation.org/show_bug.cgi?id=149590 kevbu...@gmail.com changed: What|Removed |Added Ever confirmed|1 |0 Status|NEEDINFO|UNCONFIRMED --- Comment #5 from kevbu...@gmail.com --- Alex: I have tested LO 7.4.1.2 and 7.3.6 for which I have disabled automatic backup in LO and the accessibility features zoom and mouse keys in the MacOS, but the problem persists. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 151515] Opening and scrolling ole object, affects layout in Writer
https://bugs.documentfoundation.org/show_bug.cgi?id=151515 --- Comment #1 from LeroyG --- Version: 7.2.7.2 (x64) / LibreOffice Community Build ID: 8d71d29d553c0f7dcbfa38fbfda25ee34cce99a2 CPU threads: 4; OS: Windows 10.0 Build 19043; UI render: default; VCL: win Locale: es-MX (es_ES); UI: en-US Calc: CL Actual Results: Borders move in all pages styled "My Page right" Similar if done with bordes in all pages styled "My Page left" By the way, if: 3. Double Click on the borders -> Ole Object (draw opens) 4. Zoom up down wherever Actual Results: The OLE window moves -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 151170] Need mechanism for re-centering "Slides pane" onto current slide with edit focus
https://bugs.documentfoundation.org/show_bug.cgi?id=151170 --- Comment #19 from Eyal Rozenberg --- (In reply to Heiko Tietze from comment #18) > We discussed the topic in the design meeting. I'm sorry I couldn't attend the meeting. By the way, who participated > Usually there are some indicators of the currently active slide. First of > all, the thumbnail is highlighted The thumbnail is not highlighted if the current slide is not part of the visible set of slides on the slide page - which is the scenario for which this bug was filed. > but we also show the "Page n of m" information in the left-most panel of the > statusbar. Indeed, it is possible to do some mental work, estimate the position of the slider on the scroll bar, divide N by M, and conclude whether you should scroll up or down, with a good chance of being correct. But that really is too much work, not to mention you need to scroll up by just the right amount, which, in a long slideshow is itself a bit of effort. > The proposed UNO command I did not propose an UNO command, so that's kind of a straw man. >extends the UNO API unnecessarily, and pressing > some key combinations would be quite unusual anyway. Adding a button to the > slide panel, for example next to the close button (x), has an acceptable low > impact on the UI. ... and that's what I'm asking for. There's empty screen real-estate for it as well. > But the issue actually happens when the slide loses focus, eg. by clicking > white space in the slide sorter. Then both information are gone (the slide > pane highlighting is still okay on Windows and Linux/kf5 with a clear blue > frame). No. That is, yes, if the slide also loses focus, then things are even worse, but I filed this issue even for when the slide _is_ focused on the pane - it's just that the slide may be focused, but not in view. > So what we should do is to a) always show the statusbar information what > slide is active, and b) have no white space in the slide panel. I don't know about that, and it's certainly not what I'm asking for with this issue. Please open a separate issue for avoiding loss of focus for the current slide - but it's not the problem here. > Recommendation is to change the summary into "Keep active slide in focus". Again, separate bug. > (Leaving status unconfirmed for the current "re-center the list" request > that is rather WF.) I don't believe you could seriously argue that doing integer division for estimating scrolling extents is something that "works for you". -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 151516] Date number values in .docx document change when printing.
https://bugs.documentfoundation.org/show_bug.cgi?id=151516 --- Comment #1 from tes...@2dogsplace.com --- Created attachment 183028 --> https://bugs.documentfoundation.org/attachment.cgi?id=183028=edit the document that doesnt print correctly -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 151516] New: Date number values in .docx document change when printing.
https://bugs.documentfoundation.org/show_bug.cgi?id=151516 Bug ID: 151516 Summary: Date number values in .docx document change when printing. Product: LibreOffice Version: 7.2.7.2 release Hardware: Other OS: Windows (All) Status: UNCONFIRMED Severity: normal Priority: medium Component: Writer Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: tes...@2dogsplace.com Description: In a .docx formatted document that is a calendar of events the dates change when "print" in the file menu is selected. This happens immediately upon selecting "print" as the print dialog is opening. Steps to Reproduce: 1. Open the .docx formatted write document in LibreOffice 2. Observe the calendar contents paying particular attention to the dates. 3. Go to the file menu and select "print" (alternatively click the print icon in the tool bar). 4. The print dialog opens. 5. Close the print dialog without printing. 6. Observe the calendar contents again and note that the dates have changed position and in some cases have vanished. Actual Results: The dates in the calendar change position and in some places vanish. Expected Results: Allow the document to be printed exactly as it was when opened without alteration. Reproducible: Always User Profile Reset: No OpenGL enabled: Yes Additional Info: Version: 7.2.7.2 (x64) / LibreOffice Community Build ID: 8d71d29d553c0f7dcbfa38fbfda25ee34cce99a2 CPU threads: 4; OS: Windows 10.0 Build 19044; UI render: Skia/Raster; VCL: win Locale: en-US (en_US); UI: en-US Calc: threaded HP Pavilion Desktop PC 570-p0xx Device name Mine Processor Intel(R) Core(TM) i5-7400 CPU @ 3.00GHz 3.00 GHz Installed RAM 16.0 GB Device ID D2744ECC-0DDD-4FC3-89E8-1C7288BAB216 Product ID 00325-80891-84287-AAOEM System type 64-bit operating system, x64-based processor Pen and touch No pen or touch input is available for this display Edition Windows 10 Home Version 21H2 Installed on7/12/2020 OS build19044.2130 Experience Windows Feature Experience Pack 120.2212.4180.0 Renderer: AMD Radeon R7 450 Vendor: ATI Technologies Inc. Version: 4.5.13469 Core Profile Forward-Compatible Context 21.19.512.12 Shading language version: 4.50 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 151499] Commands "Edit Diagram" and "Regenerate Diagram" do not work
https://bugs.documentfoundation.org/show_bug.cgi?id=151499 Thorsten Behrens (allotropia) changed: What|Removed |Added CC||t...@libreoffice.org --- Comment #2 from Thorsten Behrens (allotropia) --- Yep, those were supposed to be finished for 7.4 - we can remove/hide them somewhat better on that branch. For master, with the hope that implementation at some stage can continue, I'd suggest we keep them. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-commits] core.git: sc/source sc/uiconfig
sc/source/ui/formdlg/dwfunctr.cxx | 12 -
sc/source/ui/inc/dwfunctr.hxx |2
sc/uiconfig/scalc/ui/functionpanel.ui | 232 +++---
3 files changed, 111 insertions(+), 135 deletions(-)
New commits:
commit 7fc96ad09520abea4833ed7410fd3a2d1b63d7b1
Author: Rafael Lima
AuthorDate: Mon Sep 26 00:46:00 2022 +0200
Commit: Rafael Lima
CommitDate: Thu Oct 13 22:32:04 2022 +0200
tdf#150473 Wrap text and set min size for Function description
This patch does the following changes to the Functions sidebar in Calc:
1) The function description now uses a TextView instead of a Label so that
the text can now wrap. This is important because many descriptions are long and
require more than a single line of text.
2) The minimum size of the description TextView is set to 6 lines of text.
Because there's no easy way to set this minimum size (since it is inside a
Slider control), then the following rule was applied.
- If the user resizes the slider to less than 6 rows (in this case, moves
it down), the next time a new function is clicked the slider is positioned so
that 6 lines of text become visible.
- Moving the slider up, thus giving more space to the description view is
still allowed as prior to this patch.
Change-Id: I52dfa8bef52b645fdce379408e6b790f6e8e5dea
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/140507
Tested-by: Jenkins
Tested-by: Heiko Tietze
Reviewed-by: Heiko Tietze
diff --git a/sc/source/ui/formdlg/dwfunctr.cxx
b/sc/source/ui/formdlg/dwfunctr.cxx
index 424c0ee99ca8..438f8fb70e24 100644
--- a/sc/source/ui/formdlg/dwfunctr.cxx
+++ b/sc/source/ui/formdlg/dwfunctr.cxx
@@ -49,17 +49,17 @@ ScFunctionWin::ScFunctionWin(weld::Widget* pParent)
, xCatBox(m_xBuilder->weld_combo_box("category"))
, xFuncList(m_xBuilder->weld_tree_view("funclist"))
, xInsertButton(m_xBuilder->weld_button("insert"))
-, xFiFuncDesc(m_xBuilder->weld_label("funcdesc"))
+, xFiFuncDesc(m_xBuilder->weld_text_view("funcdesc"))
, xConfigListener(new
comphelper::ConfigurationListener("/org.openoffice.Office.Calc/Formula/Syntax"))
,
xConfigChange(std::make_unique(xConfigListener,
this))
, pFuncDesc(nullptr)
{
-xFuncList->set_size_request(-1, xFuncList->get_height_rows(10));
-
InitLRUList();
nArgs=0;
-xFiFuncDesc->set_size_request(-1, 5 * xFiFuncDesc->get_text_height());
+
+// Description box has a height of 8 lines of text
+xFiFuncDesc->set_size_request(-1, 8 * xFiFuncDesc->get_text_height());
xCatBox->connect_changed(LINK( this, ScFunctionWin, SelComboHdl));
xFuncList->connect_changed(LINK( this, ScFunctionWin, SelTreeHdl));
@@ -162,7 +162,7 @@ void ScFunctionWin::UpdateLRUList()
void ScFunctionWin::SetDescription()
{
-xFiFuncDesc->set_label(OUString());
+xFiFuncDesc->set_text(OUString());
const ScFuncDesc* pDesc =
weld::fromId(xFuncList->get_selected_id());
if (pDesc)
@@ -175,7 +175,7 @@ void ScFunctionWin::SetDescription()
"\n\n" +
*pDesc->mxFuncDesc;
-xFiFuncDesc->set_label(aBuf);
+xFiFuncDesc->set_text(aBuf);
}
}
diff --git a/sc/source/ui/inc/dwfunctr.hxx b/sc/source/ui/inc/dwfunctr.hxx
index eda067e0b93a..9b984b918e11 100644
--- a/sc/source/ui/inc/dwfunctr.hxx
+++ b/sc/source/ui/inc/dwfunctr.hxx
@@ -46,7 +46,7 @@ private:
std::unique_ptr xCatBox;
std::unique_ptr xFuncList;
std::unique_ptr xInsertButton;
-std::unique_ptr xFiFuncDesc;
+std::unique_ptr xFiFuncDesc;
rtl::Reference xConfigListener;
std::unique_ptr xConfigChange;
diff --git a/sc/uiconfig/scalc/ui/functionpanel.ui
b/sc/uiconfig/scalc/ui/functionpanel.ui
index 7959ffebf870..380bf7b6b651 100644
--- a/sc/uiconfig/scalc/ui/functionpanel.ui
+++ b/sc/uiconfig/scalc/ui/functionpanel.ui
@@ -1,11 +1,11 @@
-
+
True
-False
-sc/res/fx.png
+False
+sc/res/fx.png
@@ -18,184 +18,160 @@
True
-False
+False
True
True
-6
-
+
True
-False
+False
True
True
-6
-6
+6
+6
-
+
+
True
-True
+False
True
True
-vertical
-True
+6
-
+
True
-False
+False
True
-True
-6
+12
-
-
+
True
-False
-True
-12
-
-
-True
-True
-True
-
[Libreoffice-ux-advise] [Bug 138979] Dark-colored style previews lack contrast when using dark theme
https://bugs.documentfoundation.org/show_bug.cgi?id=138979 --- Comment #6 from Rafael Lima --- Created attachment 183027 --> https://bugs.documentfoundation.org/attachment.cgi?id=183027=edit Screenshot of the problem Here I changed the font color of the Adressee style to a dark gray, so it becomes barely visible over a dark background. However, my document color is white. So I wonder if we should use the document color instead. -- You are receiving this mail because: You are on the CC list for the bug.
[Libreoffice-bugs] [Bug 151511] Libreoffice 7.4.2 MacOSX Language pack does not recognize on intel mac
https://bugs.documentfoundation.org/show_bug.cgi?id=151511 --- Comment #2 from Xisco Faulí --- For some reason, there was a problem with the synchronization. This should work: https://dev-builds.libreoffice.org/pre-releases/mac/x86_64/LibreOffice_7.4.2.3_MacOS_x86-64_langpack_ja.dmg -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 138979] Dark-colored style previews lack contrast when using dark theme
https://bugs.documentfoundation.org/show_bug.cgi?id=138979 --- Comment #6 from Rafael Lima --- Created attachment 183027 --> https://bugs.documentfoundation.org/attachment.cgi?id=183027=edit Screenshot of the problem Here I changed the font color of the Adressee style to a dark gray, so it becomes barely visible over a dark background. However, my document color is white. So I wonder if we should use the document color instead. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 138979] Dark-colored style previews lack contrast when using dark theme
https://bugs.documentfoundation.org/show_bug.cgi?id=138979 Rafael Lima changed: What|Removed |Added Summary|Dark-colored style previews |Dark-colored style previews |lack contrast when using|lack contrast when using |Adwaita-dark theme |dark theme Keywords||needsUXEval Status|NEEDINFO|NEW CC||libreoffice-ux-advise@lists ||.freedesktop.org, ||rafael.palma.l...@gmail.com --- Comment #5 from Rafael Lima --- I can reproduce this problem. This is not only related to Adwaita, but also happens in KDE Plasma using Breeze. The problem is that in dark mode, the styles sidebar uses a dark color as background instead of using the document color. So if you manually set the font color to a dark color but do not change the background, then this problem will happen. Solving this issue would totally change the UX of the styles sidebar, so let's hear the opinion of the UX team. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-ux-advise] [Bug 138979] Dark-colored style previews lack contrast when using dark theme
https://bugs.documentfoundation.org/show_bug.cgi?id=138979 Rafael Lima changed: What|Removed |Added Summary|Dark-colored style previews |Dark-colored style previews |lack contrast when using|lack contrast when using |Adwaita-dark theme |dark theme Keywords||needsUXEval Status|NEEDINFO|NEW CC||libreoffice-ux-advise@lists ||.freedesktop.org, ||rafael.palma.l...@gmail.com --- Comment #5 from Rafael Lima --- I can reproduce this problem. This is not only related to Adwaita, but also happens in KDE Plasma using Breeze. The problem is that in dark mode, the styles sidebar uses a dark color as background instead of using the document color. So if you manually set the font color to a dark color but do not change the background, then this problem will happen. Solving this issue would totally change the UX of the styles sidebar, so let's hear the opinion of the UX team. -- You are receiving this mail because: You are on the CC list for the bug.
[Libreoffice-bugs] [Bug 151511] Libreoffice 7.4.2 MacOSX Language pack does not recognize on intel mac
https://bugs.documentfoundation.org/show_bug.cgi?id=151511 Xisco Faulí changed: What|Removed |Added Status|UNCONFIRMED |NEW Ever confirmed|0 |1 CC||xiscofa...@libreoffice.org --- Comment #1 from Xisco Faulí --- it seems to happens only with the japanese package. I tried with spanish and korean and it works -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 151416] [UI] Changing zoom level in one window of the same document moves the document in the other window
https://bugs.documentfoundation.org/show_bug.cgi?id=151416 Telesto changed: What|Removed |Added See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=15 ||1515 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 151515] Opening and scrolling ole object, affects layout in Writer
https://bugs.documentfoundation.org/show_bug.cgi?id=151515 Telesto changed: What|Removed |Added See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=15 ||1416 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 151515] New: Opening and scrolling ole object, affects layout in Writer
https://bugs.documentfoundation.org/show_bug.cgi?id=151515 Bug ID: 151515 Summary: Opening and scrolling ole object, affects layout in Writer Product: LibreOffice Version: 7.5.0.0 alpha0+ Master Hardware: All OS: All Status: UNCONFIRMED Severity: normal Priority: medium Component: Writer Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: tele...@surfxs.nl Description: Opening and scrolling ole object, affects layout in Writer Steps to Reproduce: 1. Open attachment 182818 2. Go to page 3 -> Look at the layout 3. Double Click the on the text -> Ole Object (draw opens) 4. Scroll/up down inside the ole object 5. Press ESC Actual Results: Borders move Expected Results: Same layout as before OLE object opening Reproducible: Always User Profile Reset: No Additional Info: Version: 7.5.0.0.alpha0+ (x64) / LibreOffice Community Build ID: 9063d99ff5ee43cc1239fc1dbb5d9897bdda1c9b CPU threads: 4; OS: Windows 6.3 Build 9600; UI render: default; VCL: win Locale: nl-NL (nl_NL); UI: en-US Calc: CL threaded -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 151468] Inserting TIFF-images will ignore dpi-information, always set to 96 dpi
https://bugs.documentfoundation.org/show_bug.cgi?id=151468 Caolán McNamara changed: What|Removed |Added Status|NEW |ASSIGNED Assignee|libreoffice-b...@lists.free |caol...@redhat.com |desktop.org | -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 144587] Tree item is inconsistent with dark theme
https://bugs.documentfoundation.org/show_bug.cgi?id=144587 Rafael Lima changed: What|Removed |Added CC||rafael.palma.l...@gmail.com Status|NEW |ASSIGNED Assignee|libreoffice-b...@lists.free |rafael.palma.l...@gmail.com |desktop.org | --- Comment #2 from Rafael Lima --- Proposed patch in Gerrit for review: https://gerrit.libreoffice.org/c/core/+/141315 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 151377] ENHANCEMENT: Collapse or hide toggle for individual effect details in animation sidebar
https://bugs.documentfoundation.org/show_bug.cgi?id=151377 --- Comment #9 from Telesto --- (In reply to Heiko Tietze from comment #8) > (In reply to Telesto from comment #6) > > * If you drag the insert animation panel down to the bottom, you can't pick > > it up anymore, if the sidebar being on minimum size (because of a horizontal > > scrollbar at the bottom). But the horizontal scrollbar shouldn't be present > > at the first place, I guess (larger minimum size of the sidebar) so maybe > > unrelated to this > > Agreed, should be fixed Check > > > * You don't need the 'Insert Effects' part of the sidebar at all, if you you > > want to rearrange the inserted effects... You don't want to reduce the size > > of the insert animation, you actually want to hide that part of the panel > > temporally. > > But you do normally switch between the two lists when adding animations to > objects. Rearranging is not the primary function. Any new animation add will but at the bottom of the list. I'm personally don't now in advance how my presentation will look like. I have some notion what I want to achieve, the core building blocks. However the details are designed along the way. You press F5, run the slide show, and thing.. well here an textbox is missing, that animation should be first etc. Same as 'improving' changing some presentation someone else build.. There is no hierarchical order of importance.. Inserting/deleting an arranging are equal functions. > > > * Sliding the panel out of sight, seems to be slightly inconsistent with the > > approach at the properties deck of the sidebar (collapse/expand). > > We could replace the slider by a collapsing section similar to the print > dialog. I personally don't care: implementation details to me.. I do prefer consistency and coherence in UI. Not sure what UI guidelines dictate. Exceptions can be made, but require some explanation. > There are some use cases where you want to maximize the lower list > of available animations and there is your rearrangement situation. Which > makes it two collapsible panels and I'm concerned about both being closed. > Would be awkward. Could be solved per code but is a special solution True > > > I admit that position the up/down buttons & delete button for sorting > > effects being a problem when considering collapsible regions. > > Better placed right hand of the list anyway. Still undecided. For sorting up/down, tend to for yes. Except it gets cramped if you set the sidebar to minimum size.. And the slide sorter bar doesn't have those buttons... > > The Slide sorter bar has no visual buttons for arranging or adding slides. > > Arranging or adding or deleting slides is done by Drag & Drop (and/or) > > Keyboard Control (and/or) Context Menu > > You need some means to pick the animation from a long list, which is not the > fact for the slide pane. Dragging items is possible as well. I have no clue what this is about. What intended to say. The Slide Sorter bar has no button controls for moving existing slides up/down. It can be done by drag & drop or cut/paste, keyboard ALT+SHIFT+PAGE UP or entry in the right click context menu. There is also no Delete Slide button. Done by keyboard delete/backspace or right click context menu. I don't see the additional value of a delete button in the animation deck of the sidebar.. A difference between slide sorter bar and the sidebar animation panel is that new slides can by added everywhere to the list. Where new animations end up at the bottom of the list by design. Consequence: A)Sorting of animations being needed more often :-( B)Greater distances to move, with long list of animations. * The ability to expand the animation list, improves drag & drop, but has still limitations with lots of animations * Allowing cut/paste of animations maybe also option (obviously only functioning within the animation panel) * Moving animations up/down with keyboard shortcut (could also have a move to top shortcut) * Making the list more compact would improve the oversight too. The old sidebar - say LibreOffice Impress 4.4.7.2 - is pretty compact. Not proposing to revert tot 4.4.7.2 layout :-). But I do ask myself, can the animation icon (say the pause button icon in case of Misc Effects, Toggle Pause) not be aligned with the on click icon. So both icons in the same row. Currently text spacing between: Shape Name & effect being pretty large. Probably because of the icon > > > And well - lets face it - the 'Add' button is on weird place anyhow... > > The described workflow with Apply/Cancel is true for dialogs when you > finalize the configuration. But I admit instead of Add it could be Insert > placed at the end of this section and with all controls enabled. Workflow > would be to set-up the animation and insert then. The Insert button could > become, or rather accomplished by, another button to Modify the selected > animation. Note: An animation gets modified straight
[Libreoffice-ux-advise] [Bug 151377] ENHANCEMENT: Collapse or hide toggle for individual effect details in animation sidebar
https://bugs.documentfoundation.org/show_bug.cgi?id=151377 --- Comment #9 from Telesto --- (In reply to Heiko Tietze from comment #8) > (In reply to Telesto from comment #6) > > * If you drag the insert animation panel down to the bottom, you can't pick > > it up anymore, if the sidebar being on minimum size (because of a horizontal > > scrollbar at the bottom). But the horizontal scrollbar shouldn't be present > > at the first place, I guess (larger minimum size of the sidebar) so maybe > > unrelated to this > > Agreed, should be fixed Check > > > * You don't need the 'Insert Effects' part of the sidebar at all, if you you > > want to rearrange the inserted effects... You don't want to reduce the size > > of the insert animation, you actually want to hide that part of the panel > > temporally. > > But you do normally switch between the two lists when adding animations to > objects. Rearranging is not the primary function. Any new animation add will but at the bottom of the list. I'm personally don't now in advance how my presentation will look like. I have some notion what I want to achieve, the core building blocks. However the details are designed along the way. You press F5, run the slide show, and thing.. well here an textbox is missing, that animation should be first etc. Same as 'improving' changing some presentation someone else build.. There is no hierarchical order of importance.. Inserting/deleting an arranging are equal functions. > > > * Sliding the panel out of sight, seems to be slightly inconsistent with the > > approach at the properties deck of the sidebar (collapse/expand). > > We could replace the slider by a collapsing section similar to the print > dialog. I personally don't care: implementation details to me.. I do prefer consistency and coherence in UI. Not sure what UI guidelines dictate. Exceptions can be made, but require some explanation. > There are some use cases where you want to maximize the lower list > of available animations and there is your rearrangement situation. Which > makes it two collapsible panels and I'm concerned about both being closed. > Would be awkward. Could be solved per code but is a special solution True > > > I admit that position the up/down buttons & delete button for sorting > > effects being a problem when considering collapsible regions. > > Better placed right hand of the list anyway. Still undecided. For sorting up/down, tend to for yes. Except it gets cramped if you set the sidebar to minimum size.. And the slide sorter bar doesn't have those buttons... > > The Slide sorter bar has no visual buttons for arranging or adding slides. > > Arranging or adding or deleting slides is done by Drag & Drop (and/or) > > Keyboard Control (and/or) Context Menu > > You need some means to pick the animation from a long list, which is not the > fact for the slide pane. Dragging items is possible as well. I have no clue what this is about. What intended to say. The Slide Sorter bar has no button controls for moving existing slides up/down. It can be done by drag & drop or cut/paste, keyboard ALT+SHIFT+PAGE UP or entry in the right click context menu. There is also no Delete Slide button. Done by keyboard delete/backspace or right click context menu. I don't see the additional value of a delete button in the animation deck of the sidebar.. A difference between slide sorter bar and the sidebar animation panel is that new slides can by added everywhere to the list. Where new animations end up at the bottom of the list by design. Consequence: A)Sorting of animations being needed more often :-( B)Greater distances to move, with long list of animations. * The ability to expand the animation list, improves drag & drop, but has still limitations with lots of animations * Allowing cut/paste of animations maybe also option (obviously only functioning within the animation panel) * Moving animations up/down with keyboard shortcut (could also have a move to top shortcut) * Making the list more compact would improve the oversight too. The old sidebar - say LibreOffice Impress 4.4.7.2 - is pretty compact. Not proposing to revert tot 4.4.7.2 layout :-). But I do ask myself, can the animation icon (say the pause button icon in case of Misc Effects, Toggle Pause) not be aligned with the on click icon. So both icons in the same row. Currently text spacing between: Shape Name & effect being pretty large. Probably because of the icon > > > And well - lets face it - the 'Add' button is on weird place anyhow... > > The described workflow with Apply/Cancel is true for dialogs when you > finalize the configuration. But I admit instead of Add it could be Insert > placed at the end of this section and with all controls enabled. Workflow > would be to set-up the animation and insert then. The Insert button could > become, or rather accomplished by, another button to Modify the selected > animation. Note: An animation gets modified straight
[Libreoffice-bugs] [Bug 151304] Cursor position error.
https://bugs.documentfoundation.org/show_bug.cgi?id=151304 --- Comment #12 from Frants <220...@mail.ru> --- (In reply to Rafael Lima from comment #11) > I still can't reproduce it. > > Maybe it's a Windows-only issue? Leroy also experienced the issue in win. Hello! So far, I've only encountered this problem on one PC. The hardware of this computer is not new. But Win10 works. What to do ... We'll have to leave it as it is. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-commits] core.git: i18npool/source
i18npool/source/localedata/data/list-dateacceptancepattern.awk |2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
New commits:
commit 2b1d34679d8a5128bc13d932466c2a6464525627
Author: Eike Rathke
AuthorDate: Thu Oct 13 18:43:32 2022 +0200
Commit: Eike Rathke
CommitDate: Thu Oct 13 21:51:53 2022 +0200
Change split regexp from \~ to ~
gawk: ./list-dateacceptancepattern.awk:70: warning: regexp escape
sequence `\~' is not a known regexp operator
Also set the executable bit again..
Change-Id: Icdf45979d6fb19d207dcf5475845767438c3ef6b
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/141340
Reviewed-by: Eike Rathke
Tested-by: Jenkins
diff --git a/i18npool/source/localedata/data/list-dateacceptancepattern.awk
b/i18npool/source/localedata/data/list-dateacceptancepattern.awk
old mode 100644
new mode 100755
index 3c86923e2b84..e47f101d4af0
--- a/i18npool/source/localedata/data/list-dateacceptancepattern.awk
+++ b/i18npool/source/localedata/data/list-dateacceptancepattern.awk
@@ -67,7 +67,7 @@ file != FILENAME {
{
formatelement = 0
split( $0, a, /<|>/ )
-split( a[3], b, /[0-9A-Za-z\[\~\]]+/ )
+split( a[3], b, /[0-9A-Za-z\[~\]]+/ )
datesep = b[2]
dateformat = a[3]
}
[Libreoffice-bugs] [Bug 137084] Some menus in Writer are not matched fully by menu help pages in Help (see comment 18)
https://bugs.documentfoundation.org/show_bug.cgi?id=137084 --- Comment #24 from Buovjaga --- (In reply to Martin Srebotnjak from comment #23) > How far are we with this issue? > Could the reporter please check what remains open (if anything at all)? Looking at Seth's summary in comment 18 and the subsequent commits, it seems Format menu needs work on submenus. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 151514] Sounds attached to Impress slides are shortened during presentation if MP3 audio quality is low
https://bugs.documentfoundation.org/show_bug.cgi?id=151514 --- Comment #4 from David F Smith --- Created attachment 183025 --> https://bugs.documentfoundation.org/attachment.cgi?id=183025=edit Great Kiskadee sound, low quality (45-85 kbps) -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 151514] Sounds attached to Impress slides are shortened during presentation if MP3 audio quality is low
https://bugs.documentfoundation.org/show_bug.cgi?id=151514 --- Comment #2 from David F Smith --- Created attachment 183023 --> https://bugs.documentfoundation.org/attachment.cgi?id=183023=edit Great Kiskadee sound, best quality (220-260 kbps) -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 151514] Sounds attached to Impress slides are shortened during presentation if MP3 audio quality is low
https://bugs.documentfoundation.org/show_bug.cgi?id=151514 --- Comment #3 from David F Smith --- Created attachment 183024 --> https://bugs.documentfoundation.org/attachment.cgi?id=183024=edit Great Kiskadee sound, medium quality (80-120 kbps) -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 151514] Sounds attached to Impress slides are shortened during presentation if MP3 audio quality is low
https://bugs.documentfoundation.org/show_bug.cgi?id=151514 --- Comment #1 from David F Smith --- Created attachment 183021 --> https://bugs.documentfoundation.org/attachment.cgi?id=183021=edit Example Impress presentation with three slides, demonstrating the problem. The three photographs in this presentation (Great Kiskadee) have attached sound files, each 12 seconds long with five songs of the Great Kiskadee. Details and results: Quality "Lame VBR quality" Impress plays 220-260 kbps 0 All five songs (12.0 sec) 80-120 kbps 7 First four songs and one note of fifth (~11.3 sec) 45-85 kbps9 First three songs (~8.3 sec) "Lame VBR quality" is as displayed by Exiftool. There are other parameters that differ between the files. The three audio files are attached separately. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 142783] SELECTING Date Field dropdown causes 'When losing focus' event.
https://bugs.documentfoundation.org/show_bug.cgi?id=142783 --- Comment #8 from David Watford --- Created attachment 183022 --> https://bugs.documentfoundation.org/attachment.cgi?id=183022=edit A sheet re-explaining the problem & a Dialog to show the problem. This is continuation of the problem when running a Date Field with a 'When loosing Focus' event set. That event should only occur when actually exiting the date field not when clicking the Dropdown! See previous comments to see when the LibreOffice version change caused me to have to amend some programs! Regards, David Watford -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 104597] RTL script text runs are reversed on PDF import, PDFIProcessor::mirrorString misbehaving
https://bugs.documentfoundation.org/show_bug.cgi?id=104597 Commit Notification changed: What|Removed |Added Whiteboard||target:7.5.0 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 104597] RTL script text runs are reversed on PDF import, PDFIProcessor::mirrorString misbehaving
https://bugs.documentfoundation.org/show_bug.cgi?id=104597 --- Comment #81 from Commit Notification --- Kevin Suo committed a patch related to this issue. It has been pushed to "master": https://git.libreoffice.org/core/commit/69e9925ded584113e52f84ef0ed7c224079fa061 sdext.pdfimport: resolves tdf#104597: RTL script text runs are reversed It will be available in 7.5.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: sdext/source
sdext/source/pdfimport/test/testdocs/tdf104597_textrun.pdf |binary
sdext/source/pdfimport/test/tests.cxx | 44 +
sdext/source/pdfimport/tree/drawtreevisiting.cxx | 17 +
sdext/source/pdfimport/tree/pdfiprocessor.cxx | 18 -
4 files changed, 48 insertions(+), 31 deletions(-)
New commits:
commit 69e9925ded584113e52f84ef0ed7c224079fa061
Author: Kevin Suo
AuthorDate: Tue Oct 11 10:04:16 2022 +0800
Commit: Thorsten Behrens
CommitDate: Thu Oct 13 21:38:12 2022 +0200
sdext.pdfimport: resolves tdf#104597: RTL script text runs are reversed
For the simple Arabic string: ٱلسَّلَامُ عَلَيْك, the xpdfimport binary
generates the
follwing (drawchar) sequences:
كَ
يْ
لَ
عَ
مُ
ا
لَ
سَّ
ل
ٱ
(i.e., in reversed order, one character by one character).
Before this patch, after pdfimport the text shows up as لَسَّلٱ كَيْلَعَ
مُا, which is reversed.
It was surposed to combine these characters into text frames in
DrawXmlOptimizer::optimizeTextElements(Element& rParent)
(sdext/source/pdfimport/\
tree/drawtreevisiting.cxx:677), but actually it was not combined
successfully there.
The single characters were then passed to
sdext/source/pdfimport/tree/drawtreevisiting\
.cxx:105, one by one, in the hope that the strings could be mirrored. The
mirroring
failed, because one single character, even after mirroring, always equals
itself.
The DrawXmlOptimizer::optimizeTextElements failed to combine the characters
into
one text frame, because the condition:
(rCurGC.Transformation == rNextGC.Transformation || notTransformed(rNextGC))
would never be true, as at least its horizontal position is different. A
further analysis
indicates that we do not need to check the transformation here at all, as
this is an
optimizer for a TextElement and in case a character is transformed then it
would already
be in a different draw element (thus will never be combined with this
TextElement).
After the fix of DrawXmlOptimizer::optimizeTextElements which now
successfully
combines the characters, there is another issue in the old
PDFIProcessor::mirrorString
function. It seems to mirror the characters within a word, but if a string
contains
two words, then the two words are not successfully switched (e.g. for
string "abc def"
it produces "cba fed" rather than "fed cba"), which is not suitable for
the case of RTL which requires all the characters been reversed. Fix this
by using
comphelper::string::reverseString.
Change-Id: Ifa210836f1ddd56205ff0d243adfb4114794
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/141231
Tested-by: Jenkins
Reviewed-by: Thorsten Behrens
diff --git a/sdext/source/pdfimport/test/testdocs/tdf104597_textrun.pdf
b/sdext/source/pdfimport/test/testdocs/tdf104597_textrun.pdf
new file mode 100644
index ..dcee96aa3169
Binary files /dev/null and
b/sdext/source/pdfimport/test/testdocs/tdf104597_textrun.pdf differ
diff --git a/sdext/source/pdfimport/test/tests.cxx
b/sdext/source/pdfimport/test/tests.cxx
index 193ec2227620..25c12a23901c 100644
--- a/sdext/source/pdfimport/test/tests.cxx
+++ b/sdext/source/pdfimport/test/tests.cxx
@@ -29,6 +29,7 @@
#include
#include
#include
+#include
#include
#include
@@ -786,6 +787,48 @@ namespace
#endif
}
+void testTdf104597_textrun()
+{
+#if HAVE_FEATURE_POPPLER
+rtl::Reference xAdaptor(new
pdfi::PDFIRawAdaptor(OUString(), getComponentContext()));
+xAdaptor->setTreeVisitorFactory(createDrawTreeVisitorFactory());
+
+OString aOutput;
+CPPUNIT_ASSERT_MESSAGE("Converting PDF to ODF XML",
+
xAdaptor->odfConvert(m_directories.getURLFromSrc(u"/sdext/source/pdfimport/test/testdocs/tdf104597_textrun.pdf"),
+new OutputWrapString(aOutput),
+nullptr));
+
+// std::cout << aOutput << std::endl;
+xmlDocUniquePtr pXmlDoc(xmlParseDoc(reinterpret_cast(aOutput.getStr(;
+
+// Test for امُ عَلَيْكَ
+// TODO: How to get the "عَلَيْكَ" in xpath, as shown after the
tag?
+OString xpath =
"//draw:frame[@draw:transform='matrix(917. 0 0 917.
14821.958333 2159.23861112778)']/draw:text-box/text:p/text:span";
+OUString sContent = getXPathContent(pXmlDoc, xpath); //
u"\nا\nُ\nم\n"
+CPPUNIT_ASSERT_EQUAL(OUString(u"اُم"), sContent.replaceAll("\n",
""));
+
+// Test for ٱلَّسَل . It appears in the 3rd frame, i.e. after the
امُ عَلَيْكَ which is in the 2nd frame (from left to right)
+// thus these two frames together appear as ٱلَّسَل امُ عَلَيْكَ
in Draw.
+xpath = "//draw:frame[@draw:transform='matrix(917. 0 0
917.
