[Libreoffice-bugs] [Bug 154707] Hook (by mouse on CALC) a cell for moving or coping it , only works occasionally at random .
https://bugs.documentfoundation.org/show_bug.cgi?id=154707 --- Comment #4 from ady --- (In reply to Bruno from comment #2) > I want to select the specific cell for moving or coping it to another place You click once (without releasing) and hold your mouse button. Now move slightly your mouse so the mouse pointer selects also an adjacent cell. Then move the mouse back to the original cell, so only that cell is marked/highlighted. Only now release the mouse button. The cell is now selected. You can now click the mouse again on the same cell (without releasing) and hold your mouse button. Move the mouse in order to drag the cell to the location you want. Once the cell is positioned in its new location, release the mouse button. Please confirm that this is the action you are trying to achieve and that it works by following these steps. Alternatively, please clarify what exactly is that you are trying to achieve and that is not working as expected. Up to this point, I cannot understand this bug report (if there is one at all). -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-commits] core.git: 2 commits - docmodel/source include/docmodel include/oox include/svx oox/qa oox/source sc/source sd/qa sd/source svx/source sw/qa sw/source writerfilter/source xmloff/i
docmodel/source/uno/UnoTheme.cxx |9 -
include/docmodel/uno/UnoTheme.hxx | 17 ++-
include/oox/drawingml/theme.hxx| 13 ++
include/oox/export/ThemeExport.hxx |7 +
include/svx/dialog/ThemeDialog.hxx |6 -
include/svx/svdmodel.hxx |4
include/svx/svdpage.hxx|8 -
oox/qa/unit/drawingml.cxx |9 -
oox/source/drawingml/diagram/diagramhelper.cxx |5
oox/source/drawingml/shape.cxx |4
oox/source/drawingml/theme.cxx | 68 -
oox/source/drawingml/themefragmenthandler.cxx |4
oox/source/export/ThemeExport.cxx |1
oox/source/ppt/presentationfragmenthandler.cxx |6 -
oox/source/shape/ShapeContextHandler.cxx |9 -
sc/source/filter/oox/workbookfragment.cxx | 12 +-
sd/qa/filter/eppt/eppt.cxx |7 -
sd/qa/unit/uiimpress.cxx |7 -
sd/source/filter/eppt/pptx-epptooxml.cxx |1
sd/source/ui/docshell/docshell.cxx |1
sd/source/ui/func/fuconstr.cxx |1
sd/source/ui/func/fupage.cxx |5
sd/source/ui/unoidl/unomodel.cxx |5
sd/source/ui/unoidl/unopage.cxx| 16 +--
svx/source/svdraw/svdmodel.cxx |8 -
svx/source/svdraw/svdpage.cxx |7 -
sw/qa/core/theme/ThemeTest.cxx |1
sw/source/core/model/ThemeColorChanger.cxx |1
sw/source/core/unocore/unodraw.cxx |7 -
writerfilter/source/dmapper/ThemeHandler.cxx |4
writerfilter/source/ooxml/OOXMLFastContextHandlerTheme.cxx |4
writerfilter/source/ooxml/OOXMLFastContextHandlerTheme.hxx |1
xmloff/inc/XMLThemeContext.hxx |8 +
xmloff/qa/unit/draw.cxx| 16 +--
xmloff/qa/unit/text.cxx|7 -
xmloff/source/draw/sdxmlexp.cxx|9 -
xmloff/source/style/XMLThemeContext.cxx|8 -
37 files changed, 150 insertions(+), 156 deletions(-)
New commits:
commit dad60bd52a25c1997d3724361ea81c0fe99b1872
Author: Tomaž Vajngerl
AuthorDate: Sat Feb 25 23:07:20 2023 +0900
Commit: Tomaž Vajngerl
CommitDate: Sat Apr 8 07:56:27 2023 +0200
oox: add model::Theme to oox::Theme and remove createSvxTheme
This is the start of the change where oox::Theme is only a holder
of model::Theme and not a oox structure. This is probably the
easiest way how to refactor that. In this commit only prepare that
and make the code work the same as it did before.
Change-Id: I926a35fd0db383ddb182dc83b36411b2d40b8530
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/147692
Tested-by: Jenkins
Reviewed-by: Tomaž Vajngerl
diff --git a/include/oox/drawingml/theme.hxx b/include/oox/drawingml/theme.hxx
index c2408ec1c015..84b75ea1e7a1 100644
--- a/include/oox/drawingml/theme.hxx
+++ b/include/oox/drawingml/theme.hxx
@@ -30,6 +30,7 @@
#include
#include
#include
+#include
namespace com::sun::star {
namespace drawing { class XDrawPage; }
@@ -107,9 +108,17 @@ public:
const css::uno::Reference& getFragment() const {
return mxFragment; }
void setFragment( const css::uno::Reference<
css::xml::dom::XDocument>& xRef ) { mxFragment=xRef; }
-std::shared_ptr createSvxTheme() const;
void addTheme(const css::uno::Reference&
xDrawPage) const;
+void setTheme(std::shared_ptr const& pTheme)
+{
+mpTheme = pTheme;
+}
+
+std::shared_ptr const& getTheme() const
+{
+return mpTheme;
+}
private:
OUStringmaThemeName;
OUStringmaFontSchemeName;
@@ -125,6 +134,8 @@ private:
Shape maLnDef;
Shape maTxDef;
css::uno::Reference< css::xml::dom::XDocument> mxFragment;
+
+std::shared_ptr mpTheme;
};
diff --git a/oox/source/drawingml/diagram/diagramhelper.cxx
b/oox/source/drawingml/diagram/diagramhelper.cxx
index daf3047b6433..3b25951bb910 100644
--- a/oox/source/drawingml/diagram/diagramhelper.cxx
+++ b/oox/source/drawingml/diagram/diagramhelper.cxx
@@ -251,11 +251,12 @@ const std::shared_ptr< ::oox::drawingml::Theme >&
AdvancedDiagramHelper::getOrCr
// reset local Theme ModelData *always* to get rid of former data
that would
// else be added additionally
[Libreoffice-bugs] [Bug 154572] Scroll by mouse wheel not correctly when rows are fixed
https://bugs.documentfoundation.org/show_bug.cgi?id=154572 --- Comment #7 from stefan_lange...@t-online.de --- I have tested with Version: 7.6.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: 197fc56a624714f284e3d9cb073589d79ce56ed0 CPU threads: 4; OS: Windows 10.0 Build 19045; UI render: Skia/Raster; VCL: win Locale: de-DE (de_DE); UI: de-DE Calc: CL threaded and the test was really OK: The behavior described in the bug didn't occur. I assume that it was really fixed with commit 8bec0ff56c53e80be81a9f463fd1fd21ade33151 (= fix for Bug 154679), because I could still reproduce the bug with Version: 7.6.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: 375f85f8518f49ce4381b6663f1e94fc02bacf93 CPU threads: 4; OS: Windows 10.0 Build 19045; UI render: Skia/Raster; VCL: win Locale: de-DE (de_DE); UI: de-DE Calc: CL threaded What is to do? I would set Bug 154572 to Resolved / Duplicate of Bug 154679. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 139910] Calc saving document as .XLSX messes up formula (saving as .xls works fine)
https://bugs.documentfoundation.org/show_bug.cgi?id=139910 ady changed: What|Removed |Added Version|7.0.0.3 release |3.3.0 release -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 154709] New: After saving as CSV (proceeding past the warning), there is no warning on close that unpreservable formatting or additional worskheets will be lost.
https://bugs.documentfoundation.org/show_bug.cgi?id=154709 Bug ID: 154709 Summary: After saving as CSV (proceeding past the warning), there is no warning on close that unpreservable formatting or additional worskheets will be lost. Product: LibreOffice Version: unspecified Hardware: x86-64 (AMD64) OS: Windows (All) Status: UNCONFIRMED Severity: enhancement Priority: medium Component: Calc Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: thezeu...@gmail.com Description: If I open a CSV file, the first time I try to save it I will get a warning that some formatting might not be preserved when saving as a CSV instead of ODS. There is a checkbox on this warning that says "Ask when not saving in ODF or default format", but even after keeping this checkbox checked, I do not receive a warning on subsequent saves. It is possible to close the file and permanently lose formatting without any further warnings. It is my opinion that at least one of two things should happen: 1. it should warn again on closing, to reduce the likelihood that work is lost 2. it should reload the file from disk after saving, and so not display the formatting which is already lost from the file saved on disk (which will then be permanently lost on closing anyway) -- you should immediately lose what you are going to lose, and have the ability to do ctrl-z to revert and save in a different format. The current flow has led to a lot of lost work, which is witnessed by many confused and dismayed forum threads: https://forum.openoffice.org/en/forum/viewtopic.php?f=9=58649 https://ask.libreoffice.org/t/recover-overwritten-csv-files-with-multiple-worksheets/52263 https://ask.libreoffice.org/t/saving-as-csv-no-warning-solved/45883 Steps to Reproduce: 1.open a CSV file 2.make some change 3.save (ctrl+s) 4.in warning dialogue leave "Ask when not saving in ODF or default format" checked 5. make some other change, e.g. highlight a row or add a worksheet 6. a) save (ctrl+s) again, then close -- no warning that you are about to lose work b) OR just close, now you get a warning that "Your changes will be lost if you don't save them." But actually they will be lost anyway, because it is still saving to csv Actual Results: expect to receive a warning before an action that can permanently lose my work -- expect when reopening a file, that it will look the same as it did immediately after I saved it Expected Results: receive no warning Reproducible: Always User Profile Reset: Yes Additional Info: This is a confusing UI issue especially for inexperienced computer users, has a high impact in terms of lost work, and can turn people off of libreoffice. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 139910] Calc saving document as .XLSX messes up formula (saving as .xls works fine)
https://bugs.documentfoundation.org/show_bug.cgi?id=139910
ady changed:
What|Removed |Added
Status|RESOLVED|NEW
Resolution|INSUFFICIENTDATA|---
--- Comment #13 from ady ---
Although I am not the original reporter, I believe this bug is still present in
current versions of LO (7.4 – 7.6.alpha).
STR:
1. Create 3 worksheets with space characters in their respective names.
2. In the last 2 worksheets, introduce some number in their respective cells
A1.
3. Use a 3D formula in "$'Sheet 1'.A1" such as:
=SUM($'Sheet 2'.A1:$'Sheet 3'.A1)
(note the space characters in the names of the worksheets, and the use of "$"
for absolute references for worksheets).
4. Save as ods.
5. Save as xls (97-2003) and close.
6. Open the ods file and save it as xlsx (2007-365).
7. Compare the results of the formulas:
ods and xls > =SUM($'Sheet 2'.A1:$'Sheet 3'.A1)
xlsx > =SUM('sheet 2':$'Sheet 3'.A1:A1)
Note that 'sheet 2' lacks the "$".
8. On Recalculate Hard, the xlsx file will show the #NAME? error instead of the
3D formula. The other 2 files work as expected, and the values in the
respective A1 cells can be updated and the formula will be updated; not so for
the xlsx file.
IOW, the export filter to xlsx is not producing the correct 3D formula.
Considering that others have reproduced this behavior in the past too, I am
setting this to NEW.
--
You are receiving this mail because:
You are the assignee for the bug.
[Libreoffice-bugs] [Bug 108897] [META] XLSX (OOXML) bug tracker
https://bugs.documentfoundation.org/show_bug.cgi?id=108897 Bug 108897 depends on bug 139910, which changed state. Bug 139910 Summary: Calc saving document as .XLSX messes up formula (saving as .xls works fine) https://bugs.documentfoundation.org/show_bug.cgi?id=139910 What|Removed |Added Status|RESOLVED|NEW Resolution|INSUFFICIENTDATA|--- -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 154406] Euro symbol not printed with FinePrint
https://bugs.documentfoundation.org/show_bug.cgi?id=154406 Dieter changed: What|Removed |Added Status|UNCONFIRMED |NEEDINFO Ever confirmed|0 |1 Summary|Euro symbol not printed |Euro symbol not printed ||with FinePrint --- Comment #6 from Dieter --- (In reply to Laurens from comment #4) > From LO 7.5.2.2 to: > FinePrint 6.11: Fail As far as I can see (https://fineprint.com/), version 6.11 is not the actual version. Is it possible for you, to update FinePrint and retest? => NEEDINFO -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-commits] core.git: Branch 'libreoffice-7-5' - sc/qa sc/source
sc/qa/unit/ucalc.cxx| 28
sc/source/core/tool/reffind.cxx |4 ++--
2 files changed, 30 insertions(+), 2 deletions(-)
New commits:
commit 832f91b104fe0605558748b688570f443eccce26
Author: Andreas Heinisch
AuthorDate: Thu Apr 6 17:38:52 2023 +0200
Commit: Adolfo Jayme Barrientos
CommitDate: Sat Apr 8 06:52:25 2023 +0200
tdf#113027 - Allow cycling cell reference types including whitespaces
A formula containing a remote reference to a sheet including a
whitespace in its name does not correctly handle switching from
relative to absolute cell references using the EXCEL R1C1
formular grammar.
Change-Id: I3391f4e8f57993899b5e97f0a173b624b5ef0b22
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/150109
Tested-by: Jenkins
Reviewed-by: Andreas Heinisch
Signed-off-by: Xisco Fauli
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/150130
Reviewed-by: Adolfo Jayme Barrientos
diff --git a/sc/qa/unit/ucalc.cxx b/sc/qa/unit/ucalc.cxx
index e5aa8515c663..84ffe142ef81 100644
--- a/sc/qa/unit/ucalc.cxx
+++ b/sc/qa/unit/ucalc.cxx
@@ -95,6 +95,7 @@ public:
void testInput();
void testColumnIterator();
void testTdf66613();
+void testTdf113027();
void testTdf90698();
void testTdf114406();
void testTdf93951();
@@ -246,6 +247,7 @@ public:
CPPUNIT_TEST(testInput);
CPPUNIT_TEST(testColumnIterator);
CPPUNIT_TEST(testTdf66613);
+CPPUNIT_TEST(testTdf113027);
CPPUNIT_TEST(testTdf90698);
CPPUNIT_TEST(testTdf114406);
CPPUNIT_TEST(testTdf93951);
@@ -701,6 +703,32 @@ void Test::testTdf66613()
m_pDoc->DeleteTab(nSecondTab);
}
+void Test::testTdf113027()
+{
+// Insert some sheets including a whitespace in their name and switch the
grammar to R1C1
+CPPUNIT_ASSERT(m_pDoc->InsertTab(0, "Sheet 1"));
+CPPUNIT_ASSERT(m_pDoc->InsertTab(1, "Sheet 2"));
+FormulaGrammarSwitch aFGSwitch(m_pDoc,
formula::FormulaGrammar::GRAM_ENGLISH_XL_R1C1);
+
+// Add a formula containing a remote reference, i.e., to another sheet
+const ScAddress aScAddress(0, 0, 0);
+const OUString aFormula = "='Sheet 2'!RC";
+m_pDoc->SetString(aScAddress, aFormula);
+
+// Switch from relative to absolute cell reference
+ScRefFinder aFinder(aFormula, aScAddress, *m_pDoc,
m_pDoc->GetAddressConvention());
+aFinder.ToggleRel(0, aFormula.getLength());
+
+// Without the fix in place, this test would have failed with
+// - Expected: ='Sheet 2'!R1C1
+// - Actual : ='Sheet 2'!RC
+// i.e. the cell reference was not changed from relative to absolute
+CPPUNIT_ASSERT_EQUAL(OUString("='Sheet 2'!R1C1"), aFinder.GetText());
+
+m_pDoc->DeleteTab(0);
+m_pDoc->DeleteTab(1);
+}
+
void Test::testTdf90698()
{
CPPUNIT_ASSERT(m_pDoc->InsertTab (0, "Test"));
diff --git a/sc/source/core/tool/reffind.cxx b/sc/source/core/tool/reffind.cxx
index 778d46a1de4e..c2851c7ff247 100644
--- a/sc/source/core/tool/reffind.cxx
+++ b/sc/source/core/tool/reffind.cxx
@@ -91,7 +91,7 @@ sal_Int32 FindEndPosR1C1(const sal_Unicode* p, sal_Int32
nStartPos, sal_Int32 nE
if (*p == '\'')
{
// Skip until the closing quote.
-for (; nNewEnd <= nEndPos; ++p, ++nNewEnd)
+for (++p; nNewEnd <= nEndPos; ++p, ++nNewEnd)
if (*p == '\'')
break;
if (nNewEnd > nEndPos)
@@ -100,7 +100,7 @@ sal_Int32 FindEndPosR1C1(const sal_Unicode* p, sal_Int32
nStartPos, sal_Int32 nE
else if (*p == '[')
{
// Skip until the closing bracket.
-for (; nNewEnd <= nEndPos; ++p, ++nNewEnd)
+for (++p; nNewEnd <= nEndPos; ++p, ++nNewEnd)
if (*p == ']')
break;
if (nNewEnd > nEndPos)
[Libreoffice-bugs] [Bug 154702] UI: Background Cell Color Resetting
https://bugs.documentfoundation.org/show_bug.cgi?id=154702 ady changed: What|Removed |Added See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=15 ||4270 --- Comment #1 from ady --- Are you using the Single Toolbar UI? Does this happen with other UI? Go to menu 'View > User Interface' and take note of your current UI. Then change it to some other UI and test whether the reported behavior is happening in that other UI too. Then you can return to your preferred UI by using the same menu. Please report your results. Additionally, in LO please go to Help > About and use the icon in the Version Information window to copy the information. Please paste that info in your next comment. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 154270] Colours reset to defaults with Single Toolbar UI
https://bugs.documentfoundation.org/show_bug.cgi?id=154270 ady changed: What|Removed |Added See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=15 ||4702 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 154344] LibreOffice Writer: Track Changes edits not saved in auto recovery
https://bugs.documentfoundation.org/show_bug.cgi?id=154344 QA Administrators changed: What|Removed |Added Whiteboard| QA:needsComment| -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 154368] UI: Status bar 'document modified' indicator/save button horizontal placement inconsistent
https://bugs.documentfoundation.org/show_bug.cgi?id=154368 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 154366] Fallback mechanism for hyphenation from specific to general/default language locale
https://bugs.documentfoundation.org/show_bug.cgi?id=154366 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 154355] Support a paragraph-scope line breaking algorithm
https://bugs.documentfoundation.org/show_bug.cgi?id=154355 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 154361] LibreOffice Writer does not show all text values of Sdt blocks in document Header
https://bugs.documentfoundation.org/show_bug.cgi?id=154361 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 154707] Hook (by mouse on CALC) a cell for moving or coping it , only works occasionally at random .
https://bugs.documentfoundation.org/show_bug.cgi?id=154707 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 154707] Hook (by mouse on CALC) a cell for moving or coping it , only works occasionally at random .
https://bugs.documentfoundation.org/show_bug.cgi?id=154707 --- Comment #3 from QA Administrators --- [Automated Action] NeedInfo-To-Unconfirmed -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 154406] Euro symbol not printed
https://bugs.documentfoundation.org/show_bug.cgi?id=154406 --- 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 154406] Euro symbol not printed
https://bugs.documentfoundation.org/show_bug.cgi?id=154406 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 150847] Crash on Raspberry Pi VIEWING slides that use fade transition
https://bugs.documentfoundation.org/show_bug.cgi?id=150847 --- Comment #5 from QA Administrators --- Dear Scott Inrig, Please read this message in its entirety before proceeding. Your bug report is being closed as INSUFFICIENTDATA due to inactivity and a lack of information which is needed in order to accurately reproduce and confirm the problem. We encourage you to retest your bug against the latest release. If the issue is still present in the latest stable release, we need the following information (please ignore any that you've already provided): a) Provide details of your system including your operating system and the latest version of LibreOffice that you have confirmed the bug to be present b) Provide easy to reproduce steps – the simpler the better c) Provide any test case(s) which will help us confirm the problem d) Provide screenshots of the problem if you think it might help e) Read all comments and provide any requested information Once all of this is done, please set the bug back to UNCONFIRMED and we will attempt to reproduce the issue. Please do not: a) respond via email b) update the version field in the bug or any of the other details on the top section of our bug tracker Warm Regards, QA Team MassPing-NeedInfo-FollowUp -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 108897] [META] XLSX (OOXML) bug tracker
https://bugs.documentfoundation.org/show_bug.cgi?id=108897 Bug 108897 depends on bug 139910, which changed state. Bug 139910 Summary: Calc saving document as .XLSX messes up formula (saving as .xls works fine) https://bugs.documentfoundation.org/show_bug.cgi?id=139910 What|Removed |Added Status|NEEDINFO|RESOLVED Resolution|--- |INSUFFICIENTDATA -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 150595] When editing the table, the ribbon elements disappear
https://bugs.documentfoundation.org/show_bug.cgi?id=150595 --- Comment #3 from QA Administrators --- Dear Nikita, Please read this message in its entirety before proceeding. Your bug report is being closed as INSUFFICIENTDATA due to inactivity and a lack of information which is needed in order to accurately reproduce and confirm the problem. We encourage you to retest your bug against the latest release. If the issue is still present in the latest stable release, we need the following information (please ignore any that you've already provided): a) Provide details of your system including your operating system and the latest version of LibreOffice that you have confirmed the bug to be present b) Provide easy to reproduce steps – the simpler the better c) Provide any test case(s) which will help us confirm the problem d) Provide screenshots of the problem if you think it might help e) Read all comments and provide any requested information Once all of this is done, please set the bug back to UNCONFIRMED and we will attempt to reproduce the issue. Please do not: a) respond via email b) update the version field in the bug or any of the other details on the top section of our bug tracker Warm Regards, QA Team MassPing-NeedInfo-FollowUp -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 139910] Calc saving document as .XLSX messes up formula (saving as .xls works fine)
https://bugs.documentfoundation.org/show_bug.cgi?id=139910 --- Comment #12 from QA Administrators --- Dear chaser.bruce, Please read this message in its entirety before proceeding. Your bug report is being closed as INSUFFICIENTDATA due to inactivity and a lack of information which is needed in order to accurately reproduce and confirm the problem. We encourage you to retest your bug against the latest release. If the issue is still present in the latest stable release, we need the following information (please ignore any that you've already provided): a) Provide details of your system including your operating system and the latest version of LibreOffice that you have confirmed the bug to be present b) Provide easy to reproduce steps – the simpler the better c) Provide any test case(s) which will help us confirm the problem d) Provide screenshots of the problem if you think it might help e) Read all comments and provide any requested information Once all of this is done, please set the bug back to UNCONFIRMED and we will attempt to reproduce the issue. Please do not: a) respond via email b) update the version field in the bug or any of the other details on the top section of our bug tracker Warm Regards, QA Team MassPing-NeedInfo-FollowUp -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 151439] Insert Hyperlink, file not working on exported PDF files
https://bugs.documentfoundation.org/show_bug.cgi?id=151439 --- Comment #2 from QA Administrators --- Dear Pedro, This bug has been in NEEDINFO status with no change for at least 6 months. Please provide the requested information as soon as possible and mark the bug as UNCONFIRMED. Due to regular bug tracker maintenance, if the bug is still in NEEDINFO status with no change in 30 days the QA team will close the bug as INSUFFICIENTDATA due to lack of needed information. For more information about our NEEDINFO policy please read the wiki located here: https://wiki.documentfoundation.org/QA/Bugzilla/Fields/Status/NEEDINFO If you have already provided the requested information, please mark the bug as UNCONFIRMED so that the QA team knows that the bug is ready to be confirmed. Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-NeedInfo-Ping -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 151435] tabs not spaced properly
https://bugs.documentfoundation.org/show_bug.cgi?id=151435 --- Comment #2 from QA Administrators --- Dear ID, This bug has been in NEEDINFO status with no change for at least 6 months. Please provide the requested information as soon as possible and mark the bug as UNCONFIRMED. Due to regular bug tracker maintenance, if the bug is still in NEEDINFO status with no change in 30 days the QA team will close the bug as INSUFFICIENTDATA due to lack of needed information. For more information about our NEEDINFO policy please read the wiki located here: https://wiki.documentfoundation.org/QA/Bugzilla/Fields/Status/NEEDINFO If you have already provided the requested information, please mark the bug as UNCONFIRMED so that the QA team knows that the bug is ready to be confirmed. Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-NeedInfo-Ping -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 95601] Headers in HTML document have wrong fonts
https://bugs.documentfoundation.org/show_bug.cgi?id=95601 --- Comment #7 from QA Administrators --- Dear rbruenner, 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 96706] Writer text boxes do not apply default style
https://bugs.documentfoundation.org/show_bug.cgi?id=96706 --- Comment #10 from QA Administrators --- Dear Antonello, 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 95006] EDITING: Writer fails to preserve some html
https://bugs.documentfoundation.org/show_bug.cgi?id=95006 --- Comment #8 from QA Administrators --- Dear gvaleika, 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 87765] PASTE: HTML formatted text pasted from Chromium, Midori, Opera Does Not Retain Indentation
https://bugs.documentfoundation.org/show_bug.cgi?id=87765 --- Comment #8 from QA Administrators --- Dear Yousuf Philips (jay) (retired), 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 93320] Saving bulleted lists as HTML produces empty list items and interspersed paragraphs
https://bugs.documentfoundation.org/show_bug.cgi?id=93320 --- Comment #8 from QA Administrators --- Dear Matthew Darlison, 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 69672] FILESAVE: Incorrect cell padding (Space to Content) in saved HTML Documents
https://bugs.documentfoundation.org/show_bug.cgi?id=69672 --- Comment #6 from QA Administrators --- Dear Calin Dumitrescu, 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 87418] Bad ordered list after saving ODT document as HTML.
https://bugs.documentfoundation.org/show_bug.cgi?id=87418 --- Comment #12 from QA Administrators --- Dear Piotr Orlewicz, 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 75837] XHTML Saving creates invalid id:s for headings
https://bugs.documentfoundation.org/show_bug.cgi?id=75837 --- Comment #8 from QA Administrators --- Dear Urmas, 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 51129] FORMATTING: FILEOPEN particular .doc (MSO97) shows page header internet link with too big font size (focus on comment 9)
https://bugs.documentfoundation.org/show_bug.cgi?id=51129 --- Comment #16 from QA Administrators --- Dear flyingvjlh, 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 41900] VIEWING: Extended Tips of Status Bar are Displayed "below" the Screen
https://bugs.documentfoundation.org/show_bug.cgi?id=41900 --- Comment #17 from QA Administrators --- Dear Harald Koester, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 41360] FORMATTING Problem with fontsize in style when expressed in percentage
https://bugs.documentfoundation.org/show_bug.cgi?id=41360 --- Comment #24 from QA Administrators --- Dear Paolo Benvenuto, 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 141539] First Line Inden doesn't work for paragraphs within a list item
https://bugs.documentfoundation.org/show_bug.cgi?id=141539 --- Comment #3 from QA Administrators --- Dear Jambunathan K, 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 141205] FORM CONTROLS: Saving while a text box is focused will focus the next select input
https://bugs.documentfoundation.org/show_bug.cgi?id=141205 --- Comment #5 from QA Administrators --- Dear Matheod, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 138859] FILEOPEN DOC: Font combobox always shows font as "0"
https://bugs.documentfoundation.org/show_bug.cgi?id=138859 --- Comment #4 from QA Administrators --- Dear John, 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 140728] writer crash on closing in BigPtrEntry::GetArray (this=) at ./sw/inc/bparr.hxx:105
https://bugs.documentfoundation.org/show_bug.cgi?id=140728 --- Comment #15 from QA Administrators --- Dear Pascal, 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 139083] Cell anchored shape is always resized if copy to a different sized range
https://bugs.documentfoundation.org/show_bug.cgi?id=139083 --- Comment #2 from QA Administrators --- Dear Regina Henschel, 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 120208] DOC import filter gives wrong page header size (WPS Office)
https://bugs.documentfoundation.org/show_bug.cgi?id=120208 --- Comment #7 from QA Administrators --- Dear hwm, 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 154708] New: An arrow key repeat deletes characters
https://bugs.documentfoundation.org/show_bug.cgi?id=154708 Bug ID: 154708 Summary: An arrow key repeat deletes characters Product: LibreOffice Version: 7.5.0.3 release Hardware: x86-64 (AMD64) OS: macOS (All) Status: UNCONFIRMED Severity: minor Priority: medium Component: Writer Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: ghf03...@nifty.ne.jp Description: When I keep pressing shift + one of the arrow keys to select multiple characters, the selected characters are unwillingly deleted. The deleted characters will be no longer resumed by the UNDO function. If I push-and-release these keys repeatedly, It works well. In 7.4.x or earlier, this phenomenon does not occur. Steps to Reproduce: 1.Create or open a Writer document. 2.Enter a character string, like 'ABCDEFGHIJKLMNOPQRSTUVWXYZ'. 3.Set the cursor at an arbitrary character, e.g. 'L.' 4.Press shift + right arrow (or left arrow) keys for a while to select characters (e.g. 'LMNOPORS' or 'EFGHIJKL'). Actual Results: The selected (highlighted) characters would be deleted. Expected Results: The selected characters stay highlighted. Reproducible: Sometimes User Profile Reset: Yes Additional Info: Version: 7.5.2.2 (X86_64) / LibreOffice Community Build ID: 53bb9681a964705cf672590721dbc85eb4d0c3a2 CPU threads: 8; OS: Mac OS X 10.15.7; UI render: default; VCL: osx Locale: ja-JP (ja_JP.UTF-8); UI: en-US Calc: threaded -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-commits] core.git: sc/uiconfig sw/uiconfig
sc/uiconfig/scalc/popupmenu/draw.xml|1 + sw/uiconfig/sglobal/popupmenu/draw.xml |1 + sw/uiconfig/swform/popupmenu/draw.xml |1 + sw/uiconfig/swreport/popupmenu/draw.xml |1 + sw/uiconfig/swriter/popupmenu/draw.xml |1 + sw/uiconfig/swxform/popupmenu/draw.xml |1 + 6 files changed, 6 insertions(+) New commits: commit ad5756f0529a80fbb537979bcfd9de7a83a69805 Author: Justin Luth AuthorDate: Fri Apr 7 12:38:58 2023 -0400 Commit: Justin Luth CommitDate: Sat Apr 8 02:51:43 2023 +0200 uno:TextAttributes - add to popupmenu draw.xml for textboxes Text Attributes includes margins for spacing the borders (lines) away from the text. I personally would like to see the order be Area, then lines, then textAttributes, but I suppose one could look at it as area margins instead of border margins. In any case, margins are a pretty critical piece of either lines or margins, and so should be a menu choice whenever either of these is available. Change-Id: Ifec5bbcd20dba6f42aba586bd0cd791bb9f3acae Reviewed-on: https://gerrit.libreoffice.org/c/core/+/150131 Tested-by: Jenkins Reviewed-by: Justin Luth diff --git a/sc/uiconfig/scalc/popupmenu/draw.xml b/sc/uiconfig/scalc/popupmenu/draw.xml index f8a19fe65309..41167edf00fd 100644 --- a/sc/uiconfig/scalc/popupmenu/draw.xml +++ b/sc/uiconfig/scalc/popupmenu/draw.xml @@ -19,6 +19,7 @@ + diff --git a/sw/uiconfig/sglobal/popupmenu/draw.xml b/sw/uiconfig/sglobal/popupmenu/draw.xml index 799c02cc5e2e..28c10613459e 100644 --- a/sw/uiconfig/sglobal/popupmenu/draw.xml +++ b/sw/uiconfig/sglobal/popupmenu/draw.xml @@ -18,6 +18,7 @@ + diff --git a/sw/uiconfig/swform/popupmenu/draw.xml b/sw/uiconfig/swform/popupmenu/draw.xml index 799c02cc5e2e..28c10613459e 100644 --- a/sw/uiconfig/swform/popupmenu/draw.xml +++ b/sw/uiconfig/swform/popupmenu/draw.xml @@ -18,6 +18,7 @@ + diff --git a/sw/uiconfig/swreport/popupmenu/draw.xml b/sw/uiconfig/swreport/popupmenu/draw.xml index 799c02cc5e2e..28c10613459e 100644 --- a/sw/uiconfig/swreport/popupmenu/draw.xml +++ b/sw/uiconfig/swreport/popupmenu/draw.xml @@ -18,6 +18,7 @@ + diff --git a/sw/uiconfig/swriter/popupmenu/draw.xml b/sw/uiconfig/swriter/popupmenu/draw.xml index 799c02cc5e2e..28c10613459e 100644 --- a/sw/uiconfig/swriter/popupmenu/draw.xml +++ b/sw/uiconfig/swriter/popupmenu/draw.xml @@ -18,6 +18,7 @@ + diff --git a/sw/uiconfig/swxform/popupmenu/draw.xml b/sw/uiconfig/swxform/popupmenu/draw.xml index 799c02cc5e2e..28c10613459e 100644 --- a/sw/uiconfig/swxform/popupmenu/draw.xml +++ b/sw/uiconfig/swxform/popupmenu/draw.xml @@ -18,6 +18,7 @@ +
[Libreoffice-commits] core.git: sc/source
sc/source/ui/view/tabview.cxx |2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
New commits:
commit 6b2e928450ea55cc1667631b9d8a23146906d1da
Author: Andrea Gelmini
AuthorDate: Fri Apr 7 15:23:40 2023 +0200
Commit: Adolfo Jayme Barrientos
CommitDate: Sat Apr 8 02:10:07 2023 +0200
Fix typo
Change-Id: I16044e195878c4d51a2e4a92986a1b0baf8bc2a0
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/150127
Tested-by: Jenkins
Reviewed-by: Adolfo Jayme Barrientos
diff --git a/sc/source/ui/view/tabview.cxx b/sc/source/ui/view/tabview.cxx
index 59b0154a446d..093ebe4f89c5 100644
--- a/sc/source/ui/view/tabview.cxx
+++ b/sc/source/ui/view/tabview.cxx
@@ -1187,7 +1187,7 @@ void ScTabView::ScrollHdl(ScrollAdaptor* pScroll)
// horizontal scroll wheel or trackpad swipe events, most
// vertical scroll wheel or trackpad swipe events will trigger
// the anti-jitter code because nScrollPos and nPrevDragPos
-// will be equal and nDelta will be overriden and set to zero.
+// will be equal and nDelta will be overridden and set to zero.
// So, only use the anti-jitter code for mouse drag events.
if ( eType == ScrollType::Drag )
{
[Libreoffice-bugs] [Bug 55133] COMMENT - added comment text gets invisible when fist row is set as header (MENU WINDOW FREEZE)
https://bugs.documentfoundation.org/show_bug.cgi?id=55133 Aron Budea changed: What|Removed |Added See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=12 ||6847 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 126847] Comment on frozen row is truncated
https://bugs.documentfoundation.org/show_bug.cgi?id=126847 Aron Budea changed: What|Removed |Added See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=55 ||133 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 101216] [META] Calc comment bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=101216 Bug 101216 depends on bug 126847, which changed state. Bug 126847 Summary: Comment on frozen row is truncated https://bugs.documentfoundation.org/show_bug.cgi?id=126847 What|Removed |Added Status|RESOLVED|NEW Resolution|DUPLICATE |--- -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 101216] [META] Calc comment bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=101216 Aron Budea changed: What|Removed |Added Depends on||126847 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=126847 [Bug 126847] Comment on frozen row is truncated -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 126847] Comment on frozen row is truncated
https://bugs.documentfoundation.org/show_bug.cgi?id=126847 Aron Budea changed: What|Removed |Added Resolution|DUPLICATE |--- OS|Windows (All) |All CC||aron.bu...@gmail.com Ever confirmed|0 |1 Status|RESOLVED|NEW Blocks||101216 --- Comment #2 from Aron Budea --- Bug 55133 has been closed as WFM, while this is still reproducible in 7.6.0.0.alpha0+ (250b820a24640a33d73a6e690e04e36be01cda28) / Ubuntu. Let's set it to NEW. Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=101216 [Bug 101216] [META] Calc comment bugs and enhancements -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 118061] add comment not always visible if freeze cols and rows
https://bugs.documentfoundation.org/show_bug.cgi?id=118061 Aron Budea changed: What|Removed |Added CC||aron.bu...@gmail.com Alias|Papers-Land | URL|https://www.onlinemastersco | |lleges.com/one-year-masters | |-programs-online| -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 154707] Hook (by mouse on CALC) a cell for moving or coping it , only works occasionally at random .
https://bugs.documentfoundation.org/show_bug.cgi?id=154707 --- Comment #2 from Bruno --- (In reply to m.a.riosv from comment #1) > After clicking on a cell, keeping the mouse button pressed doesn't change > anything. It is how it works. > > If you want to insert, e.g., a reference to B4 en A1. > Go to A1 > Press = or + or - > Click on B4 I want to select the specific cell for moving or coping it to another place ... is'nt that possible ? I saw that sometime it happens ,as in others spreadsheets . Referencing is something else . Bye -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-commits] core.git: helpcontent2
helpcontent2 |2 +- 1 file changed, 1 insertion(+), 1 deletion(-) New commits: commit 197fc56a624714f284e3d9cb073589d79ce56ed0 Author: Olivier Hallot AuthorDate: Fri Apr 7 20:38:40 2023 -0300 Commit: Gerrit Code Review CommitDate: Sat Apr 8 01:38:40 2023 +0200 Update git submodules * Update helpcontent2 from branch 'master' to 001bc6f839d99b51a79eb398fc9f4317ccc9c60a - Adjust table and refactor Change-Id: I477f9c35dcda50e2546c411b0a56f552e6e48ab9 Reviewed-on: https://gerrit.libreoffice.org/c/help/+/150154 Tested-by: Jenkins Reviewed-by: Olivier Hallot diff --git a/helpcontent2 b/helpcontent2 index 02f32becf3e2..001bc6f839d9 16 --- a/helpcontent2 +++ b/helpcontent2 @@ -1 +1 @@ -Subproject commit 02f32becf3e2e4238027b4ec566ac8e07c9b81eb +Subproject commit 001bc6f839d99b51a79eb398fc9f4317ccc9c60a
[Libreoffice-commits] help.git: source/text
source/text/shared/01/05020301.xhp | 1256 ++--- 1 file changed, 628 insertions(+), 628 deletions(-) New commits: commit 001bc6f839d99b51a79eb398fc9f4317ccc9c60a Author: Olivier Hallot AuthorDate: Fri Apr 7 19:12:56 2023 -0300 Commit: Olivier Hallot CommitDate: Sat Apr 8 01:38:40 2023 +0200 Adjust table and refactor Change-Id: I477f9c35dcda50e2546c411b0a56f552e6e48ab9 Reviewed-on: https://gerrit.libreoffice.org/c/help/+/150154 Tested-by: Jenkins Reviewed-by: Olivier Hallot diff --git a/source/text/shared/01/05020301.xhp b/source/text/shared/01/05020301.xhp index 6a4a4c19ad..d5e862b46d 100644 --- a/source/text/shared/01/05020301.xhp +++ b/source/text/shared/01/05020301.xhp @@ -20,14 +20,14 @@ -Number Format Codes +Number Format Codes /text/shared/01/05020301.xhp - + format codes; numbers conditions; in number formats number formats; codes @@ -47,59 +47,59 @@ mw made "time formats" a two level entry and deleted 2x "formats;" Number Format Codes -Number format codes can consist of up to four sections separated by a semicolon (;). +Number format codes can consist of up to four sections separated by a semicolon (;). -In a number format code with two sections, the first section applies to positive values and zero, and the second section applies to negative values. +In a number format code with two sections, the first section applies to positive values and zero, and the second section applies to negative values. -In a number format code with three sections, the first section applies to positive values, the second section to negative values, and the third section to the value zero. +In a number format code with three sections, the first section applies to positive values, the second section to negative values, and the third section to the value zero. -You can also assign conditions to the three sections, so that the format is only applied if a condition is met. +You can also assign conditions to the three sections, so that the format is only applied if a condition is met. -Fourth section applies if the content is not a value, but some text. Content is represented by an at sign (@). +Fourth section applies if the content is not a value, but some text. Content is represented by an at sign (@). Decimal Places and Significant Digits - Use zero (0), the number sign (#) or the question mark (?) as placeholders in your number format code to represent numbers. The # only displays significant digits, while the 0 displays zeroes if there are fewer digits in the number than in the number format. The ? works as the # but adds a space character to keep decimal alignment if there is a hidden non-significant zero. - Use question marks (?), zeroes (0) or number signs (#) to represent the number of digits to include in the numerator and the denominator of a fraction. Fractions that do not fit the pattern that you define are displayed as floating point numbers. -If a number contains more digits to the right of the decimal delimiter than there are placeholders in the format, the number is rounded accordingly. If a number contains more digits to the left of the decimal delimiter than there are placeholders in the format, the entire number is displayed. Use the following list as a guide for using placeholders when you create a number format code: + Use zero (0), the number sign (#) or the question mark (?) as placeholders in your number format code to represent numbers. The # only displays significant digits, while the 0 displays zeroes if there are fewer digits in the number than in the number format. The ? works as the # but adds a space character to keep decimal alignment if there is a hidden non-significant zero. + Use question marks (?), zeroes (0) or number signs (#) to represent the number of digits to include in the numerator and the denominator of a fraction. Fractions that do not fit the pattern that you define are displayed as floating point numbers. +If a number contains more digits to the right of the decimal delimiter than there are placeholders in the format, the number is rounded accordingly. If a number contains more digits to the left of the decimal delimiter than there are placeholders in the format, the entire number is displayed. Use the following list as a guide for using placeholders when you create a number format code: - Placeholders + Placeholders - Explanation + Explanation - # + # - Does not display extra zeros. + Does not display extra zeros. - ? + ? - Displays space characters instead of extra zeros. + Displays space characters instead of extra zeros. - 0 (Zero) + 0 (Zero)
[Libreoffice-bugs] [Bug 154697] Adding language dictionary extensions via link in Spellcheck - Options Dialog broken
https://bugs.documentfoundation.org/show_bug.cgi?id=154697 m.a.riosv changed: What|Removed |Added OS|macOS (All) |All Hardware|ARM |All -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 154697] Adding language dictionary extensions via link in Spellcheck - Options Dialog broken
https://bugs.documentfoundation.org/show_bug.cgi?id=154697 m.a.riosv changed: What|Removed |Added Ever confirmed|0 |1 CC||miguelangelrv@libreoffice.o ||rg Status|UNCONFIRMED |NEW --- Comment #4 from m.a.riosv --- Repro also with Version: 7.6.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: d408e940630d131ab886a1d4619671fa0299c03e CPU threads: 4; OS: Windows 10.0 Build 19045; UI render: Skia/Raster; VCL: win Locale: es-ES (es_ES); UI: en-US -- You are receiving this mail because: You are the assignee for the bug.
Re: MCGR repair broken offset on import
Hi Armin, Hi, On 4/5/23 13:58, Regina Henschel wrote: Hi Armin, hi all, I'm currently working on import of multicolor gradients from ODF. With my proposal for standardizing multicolor gradients the offset values would be in interval [0.0,1.0] and sorted in ascending order in a valid file markup. There is a correction in place when GradientStops are applied to the model data, so after import and transfer over UNO API (see sortAndCorrectColorStops). It sorts the elements, preserving order for GradientStops with identical StopOffset. Let's call the space between two GradientStops GradientStopSegment. Every empty (0.0 == 'width') GradientStopSegment < 0.0 or > 1.0 is discarded. A GradientStopSegment overlapping 0.0 or 1.0 is corrected by moving the value outside [0.0 .. 1.0] to 0.0 or 1.0 resp. and also linearly interpolating the color of the corrected entry to represent that translation > This is done by assuming that an overlapping entry might still contain useful color information and to get as close as possible to what the instance creating that data wanted to define. That might be optimistic, but tries to follow the principle to safe as much input data (evtl. from the user) as possible and useful - even when the definition might be not 100% correct from what we define. That is different than SVG handles this. But it is fine for me because such situation will not occur in a valid ODF document. Due to this correction it is ensured that we will (potentially) not write 'wrong' definitions since all data you can get from the model data over the UNO API will be valid in the sense of that definitions. Thus, for export, no nee to check for correctness is needed - just export it. For export I have kept a correction in the way SVG does it to be sure it will be valid in the ODF sense. Since I know no places where data from ODF is imported and not set at the model data, this would automatically correct this at load/import time and in a roundtrip, too. Thus - for simplicity - you might just import from ODF to awt::Gradient2 what is there in the order that is there and leave the corrections to the model. In import, I now take the values as they are. I have tested with offsets out of range and with offsets in wrong order. After loading, a save and reload gives the same fill as first load. So I think that works. My version is in https://gerrit.libreoffice.org/c/core/+/150060. It does not yet consider theme colors. When your part is finished, it should work with simple colors. Currently there are some unit tests, which fail. If you are curious how ODF will look, you can test it. Kind regards, Regina
[Libreoffice-bugs] [Bug 154379] [VISIO] [Fileopen] Text is not readable (missing color?)
https://bugs.documentfoundation.org/show_bug.cgi?id=154379 raal changed: What|Removed |Added Version|3.3.0 release |unspecified Component|Impress |libvisio Ever confirmed|0 |1 Status|UNCONFIRMED |NEW Product|LibreOffice |Document Liberation Project --- Comment #4 from raal --- confirm with Version: 7.6.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: 250b820a24640a33d73a6e690e04e36be01cda28 CPU threads: 4; OS: Linux 5.19; UI render: default; VCL: gtk3 Locale: cs-CZ (cs_CZ.UTF-8); UI: en-US Calc: threaded -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 154707] Hook (by mouse on CALC) a cell for moving or coping it , only works occasionally at random .
https://bugs.documentfoundation.org/show_bug.cgi?id=154707 m.a.riosv changed: What|Removed |Added Status|UNCONFIRMED |NEEDINFO CC||miguelangelrv@libreoffice.o ||rg Ever confirmed|0 |1 --- Comment #1 from m.a.riosv --- After clicking on a cell, keeping the mouse button pressed doesn't change anything. It is how it works. If you want to insert, e.g., a reference to B4 en A1. Go to A1 Press = or + or - Click on B4 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 154379] [VISIO] [Fileopen] Text is not readable (missing color?)
https://bugs.documentfoundation.org/show_bug.cgi?id=154379 raal changed: What|Removed |Added CC||r...@post.cz --- Comment #3 from raal --- Created attachment 186539 --> https://bugs.documentfoundation.org/attachment.cgi?id=186539=edit printscreen from visio -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 154706] Paste command grayed-out
https://bugs.documentfoundation.org/show_bug.cgi?id=154706 m.a.riosv changed: What|Removed |Added Ever confirmed|0 |1 CC||miguelangelrv@libreoffice.o ||rg Status|UNCONFIRMED |NEEDINFO --- Comment #1 from m.a.riosv --- Do you have a clipboard manager installed? Please test with a clean profile, Menu/Help/Restart in Safe Mode -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 154377] [VISIO] [Fileopen] Shapes are completely dissorted
https://bugs.documentfoundation.org/show_bug.cgi?id=154377 raal changed: What|Removed |Added Component|Draw|libvisio Product|LibreOffice |Document Liberation Project Version|3.3.0 release |unspecified -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 154377] [VISIO] [Fileopen] Shapes are completely dissorted
https://bugs.documentfoundation.org/show_bug.cgi?id=154377 raal changed: What|Removed |Added Ever confirmed|0 |1 Status|UNCONFIRMED |NEW --- Comment #4 from raal --- confirm with Version: 7.6.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: 250b820a24640a33d73a6e690e04e36be01cda28 CPU threads: 4; OS: Linux 5.19; UI render: default; VCL: gtk3 Locale: cs-CZ (cs_CZ.UTF-8); UI: en-US Calc: threaded -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 154377] [VISIO] [Fileopen] Shapes are completely dissorted
https://bugs.documentfoundation.org/show_bug.cgi?id=154377 raal changed: What|Removed |Added CC||r...@post.cz --- Comment #3 from raal --- Created attachment 186538 --> https://bugs.documentfoundation.org/attachment.cgi?id=186538=edit printscreen from visio -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 154705] Enhancement: Add Snap to Intersection
https://bugs.documentfoundation.org/show_bug.cgi?id=154705 raal changed: What|Removed |Added Severity|normal |enhancement CC||r...@post.cz OS|Windows (All) |All -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-commits] core.git: sw/qa writerfilter/source
sw/qa/extras/ooxmlimport/data/tdf154695-ToC_no_numbers.docx |binary
sw/qa/extras/ooxmlimport/ooxmlimport2.cxx | 78 ++--
writerfilter/source/dmapper/DomainMapper_Impl.cxx | 36 -
3 files changed, 95 insertions(+), 19 deletions(-)
New commits:
commit b6a5f16a9bf3227867bf46b88d012440138b6f24
Author: Mike Kaganski
AuthorDate: Sat Apr 8 00:03:31 2023 +0300
Commit: Mike Kaganski
CommitDate: Sat Apr 8 00:46:51 2023 +0200
tdf#154695: use Chapter Numbering Rules to confirm that ToC needs tabs
Indeed, this still can't handle it per-element, like Word does: the latter
would omit both the number and the tab for headings without numbering. But
at least the most common case should be handled better now.
Change-Id: I0be5d61a5d2cbbf778ee88a11129a6e7655593ec
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/150133
Tested-by: Jenkins
Reviewed-by: Mike Kaganski
diff --git a/sw/qa/extras/ooxmlimport/data/tdf154695-ToC_no_numbers.docx
b/sw/qa/extras/ooxmlimport/data/tdf154695-ToC_no_numbers.docx
new file mode 100644
index ..fb86250fd415
Binary files /dev/null and
b/sw/qa/extras/ooxmlimport/data/tdf154695-ToC_no_numbers.docx differ
diff --git a/sw/qa/extras/ooxmlimport/ooxmlimport2.cxx
b/sw/qa/extras/ooxmlimport/ooxmlimport2.cxx
index c201e585e997..906230ada7d4 100644
--- a/sw/qa/extras/ooxmlimport/ooxmlimport2.cxx
+++ b/sw/qa/extras/ooxmlimport/ooxmlimport2.cxx
@@ -1059,8 +1059,9 @@ CPPUNIT_TEST_FIXTURE(Test, testTdf154319)
};
// tdf#154360: check tab stops between the number and the entry text
+// The last (10th) level does not correspont to any MS level (only 9
levels there)
constexpr sal_Int32 levelTabStops[]
-= { 776, 1270, 1270, 1270, 1270, 1270, 1270, 1270, 1270, 1270 };
+= { 776, 1270, 1270, 1270, 1270, 1270, 1270, 1270, 1270, -1 };
//start with level 1, 0 is the header level
for (sal_Int32 nLevel = 1; nLevel < xLevelFormats->getCount(); ++nLevel)
@@ -1068,27 +1069,78 @@ CPPUNIT_TEST_FIXTURE(Test, testTdf154319)
css::uno::Sequence aLevel;
xLevelFormats->getByIndex(nLevel) >>= aLevel;
-CPPUNIT_ASSERT_EQUAL(sal_Int32(9), aLevel.getLength());
+sal_Int32 nTabStop = levelTabStops[nLevel - 1];
+sal_Int32 nExpectedTokens = nTabStop < 0 ? 8 : 9;
+CPPUNIT_ASSERT_EQUAL(nExpectedTokens, aLevel.getLength());
+sal_Int32 nIndex = 0;
-checkPropVal(OUString("TokenHyperlinkStart"), aLevel[0], "TokenType",
nLevel);
+checkPropVal(OUString("TokenHyperlinkStart"), aLevel[nIndex++],
"TokenType", nLevel);
-checkPropVal(OUString("TokenEntryNumber"), aLevel[1], "TokenType",
nLevel);
+checkPropVal(OUString("TokenEntryNumber"), aLevel[nIndex++],
"TokenType", nLevel);
+
+if (nTabStop >= 0)
+{
+checkPropVal(OUString("TokenTabStop"), aLevel[nIndex],
"TokenType", nLevel);
+checkPropVal(levelTabStops[nLevel - 1], aLevel[nIndex++],
"TabStopPosition", nLevel);
+}
+
+checkPropVal(OUString("TokenEntryText"), aLevel[nIndex++],
"TokenType", nLevel);
-checkPropVal(OUString("TokenTabStop"), aLevel[2], "TokenType", nLevel);
-checkPropVal(levelTabStops[nLevel - 1], aLevel[2], "TabStopPosition",
nLevel);
+checkPropVal(OUString("TokenTabStop"), aLevel[nIndex++], "TokenType",
nLevel);
+
+checkPropVal(OUString("TokenChapterInfo"), aLevel[nIndex++],
"TokenType", nLevel);
+
+checkPropVal(OUString("TokenText"), aLevel[nIndex], "TokenType",
nLevel);
+checkPropVal(OUString("\""), aLevel[nIndex++], "Text", nLevel);
+
+checkPropVal(OUString("TokenPageNumber"), aLevel[nIndex++],
"TokenType", nLevel);
+
+checkPropVal(OUString("TokenHyperlinkEnd"), aLevel[nIndex++],
"TokenType", nLevel);
+}
+}
+
+CPPUNIT_TEST_FIXTURE(Test, testTdf154695)
+{
+createSwDoc("tdf154695-ToC_no_numbers.docx");
+
+auto
xSupplier(mxComponent.queryThrow());
+auto xIndexes = xSupplier->getDocumentIndexes();
+auto
xTOCIndex(xIndexes->getByIndex(0).queryThrow());
+css::uno::Reference xLevelFormats;
+CPPUNIT_ASSERT(xTOCIndex->getPropertyValue("LevelFormat") >>=
xLevelFormats);
+CPPUNIT_ASSERT_EQUAL(sal_Int32(11), xLevelFormats->getCount());
-checkPropVal(OUString("TokenEntryText"), aLevel[3], "TokenType",
nLevel);
+const auto checkPropVal = [](const auto& expected, const
css::beans::PropertyValues& entry,
+ const OUString& name, sal_Int32 level) {
+auto it
+= std::find_if(entry.begin(), entry.end(),
+ [](const css::beans::PropertyValue& p) {
return p.Name == name; });
+OString msg = "Property: " + name.toUtf8() + ", level: " +
OString::number(level);
+CPPUNIT_ASSERT_MESSAGE(msg.getStr(), it != entry.end());
+CPPUNIT_ASSERT_EQUAL_MESSAGE(msg.getStr(),
[Libreoffice-bugs] [Bug 154707] New: Hook (by mouse on CALC) a cell for moving or coping it , only works occasionally at random .
https://bugs.documentfoundation.org/show_bug.cgi?id=154707 Bug ID: 154707 Summary: Hook (by mouse on CALC) a cell for moving or coping it , only works occasionally at random . Product: LibreOffice Version: unspecified Hardware: x86-64 (AMD64) OS: Windows (All) Status: UNCONFIRMED Severity: normal Priority: medium Component: Calc Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: bru...@outlook.it Description: Most of the times ,the pointer keeps selecting area of cells.No matter how long I keep the Mouse botton pressed ,or try re-clicking the cell. (Acer Aspire F 15 Intel Core i7-7500U Win 10 home ver. 21H2) p.s. On other spreadsheet it works so smoothly. Happens the same also on 'Open Office Calc'. Thanks Steps to Reproduce: 1.click on cell & keep pressed,wait for mouse pointer to chance (adding cell symbole) 2. 3. Actual Results: No use Expected Results: mouse pointer to chance (adding cell symbole) Reproducible: Always User Profile Reset: No Additional Info: keeps selecting area of cells.No matter how long I -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 154706] New: Paste command grayed-out
https://bugs.documentfoundation.org/show_bug.cgi?id=154706 Bug ID: 154706 Summary: Paste command grayed-out Product: LibreOffice Version: 7.5.2.2 release Hardware: All OS: Windows (All) Status: UNCONFIRMED Severity: normal Priority: medium Component: Calc Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: jassow...@att.net Description: I cannot paste a copied item Steps to Reproduce: 1.Open spreadshee 2.Paste command is grayed-out 3. Sometimes it is not grayed-out until I use the COPY command. Actual Results: I have no capability to Paste. Expected Results: PASTE is not active. Reproducible: Always User Profile Reset: No Additional Info: "About LibreOffice page can not be copied; this is a common failing -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153374] Hang using Keyboard viewer
https://bugs.documentfoundation.org/show_bug.cgi?id=153374 --- Comment #5 from bz137...@halfpi.co.uk --- I bisected https://bibisect.libreoffice.org/mac64-7.1.git 76c416a97157d788f3048dd504fcf5b97be8c027 is the first bad commit commit 76c416a97157d788f3048dd504fcf5b97be8c027 Author: libreoffice Date: Tue Dec 1 17:39:28 2020 +0100 source sha:12e30b658d0adfd00c463be8a7f0d6cf91ee0974 source sha:12e30b658d0adfd00c463be8a7f0d6cf91ee0974 LibreOffice.app/Contents/Frameworks/libsmlo.dylib | Bin 1489384 -> 1489336 bytes LibreOffice.app/Contents/Resources/setuprc| 2 +- LibreOffice.app/Contents/Resources/versionrc | 2 +- 3 files changed, 2 insertions(+), 2 deletions(-) 7.2 and 7.3 also faulty -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-commits] core.git: Branch 'libreoffice-7-4' - sd/source
sd/source/ui/view/drviews3.cxx |4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
New commits:
commit 2a7bc316c9b49e5b26fad88998c5160aa9c80c61
Author: Xisco Fauli
AuthorDate: Thu Apr 6 12:55:50 2023 +0200
Commit: Caolán McNamara
CommitDate: Fri Apr 7 22:51:28 2023 +0200
sd: fix crash in DrawViewShell::ExecCtrl
See
https://crashreport.libreoffice.org/stats/signature/sd::DrawViewShell::ExecCtrl(SfxRequest%20&)
I believe this crash is triggered with some basic code while
slideshow is running.
Anyway, if I delete the previous SlideShow::IsRunning(GetViewShellBase())
check, launch Impress and add a new slide, LibreOfice also crashes.
Change-Id: Iba40f37485a4a6815729a1a26c380b6c3fdedfd4
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/150097
Reviewed-by: Caolán McNamara
Tested-by: Jenkins
Reviewed-by: Xisco Fauli
(cherry picked from commit 6a1425c4c9595ed82629d846c9b69ed9942b2c0b)
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/150080
diff --git a/sd/source/ui/view/drviews3.cxx b/sd/source/ui/view/drviews3.cxx
index 5821168bc865..3f16136ffbe9 100644
--- a/sd/source/ui/view/drviews3.cxx
+++ b/sd/source/ui/view/drviews3.cxx
@@ -140,8 +140,8 @@ void DrawViewShell::ExecCtrl(SfxRequest& rReq)
// switch page in running slide show
if(SlideShow::IsRunning(GetViewShellBase()) && rReq.GetArgs())
{
-const SfxUInt32Item* pWhatPage =
rReq.GetArg(ID_VAL_WHATPAGE);
-
SlideShow::GetSlideShow(GetViewShellBase())->jumpToPageNumber(static_cast((pWhatPage->GetValue()-1)>>1));
+if (const SfxUInt32Item* pWhatPage =
rReq.GetArg(ID_VAL_WHATPAGE))
+
SlideShow::GetSlideShow(GetViewShellBase())->jumpToPageNumber(static_cast((pWhatPage->GetValue()-1)>>1));
}
else
{
[Libreoffice-commits] core.git: Branch 'libreoffice-7-5' - sd/source
sd/source/ui/view/drviews3.cxx |4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
New commits:
commit f7a5856a4a627548594b3d003903945a41d47e51
Author: Xisco Fauli
AuthorDate: Thu Apr 6 12:55:50 2023 +0200
Commit: Caolán McNamara
CommitDate: Fri Apr 7 22:51:17 2023 +0200
sd: fix crash in DrawViewShell::ExecCtrl
See
https://crashreport.libreoffice.org/stats/signature/sd::DrawViewShell::ExecCtrl(SfxRequest%20&)
I believe this crash is triggered with some basic code while
slideshow is running.
Anyway, if I delete the previous SlideShow::IsRunning(GetViewShellBase())
check, launch Impress and add a new slide, LibreOfice also crashes.
Change-Id: Iba40f37485a4a6815729a1a26c380b6c3fdedfd4
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/150097
Reviewed-by: Caolán McNamara
Tested-by: Jenkins
Reviewed-by: Xisco Fauli
(cherry picked from commit 6a1425c4c9595ed82629d846c9b69ed9942b2c0b)
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/150079
diff --git a/sd/source/ui/view/drviews3.cxx b/sd/source/ui/view/drviews3.cxx
index e0c0db7b7e48..b75a5d61733f 100644
--- a/sd/source/ui/view/drviews3.cxx
+++ b/sd/source/ui/view/drviews3.cxx
@@ -140,8 +140,8 @@ void DrawViewShell::ExecCtrl(SfxRequest& rReq)
// switch page in running slide show
if(SlideShow::IsRunning(GetViewShellBase()) && rReq.GetArgs())
{
-const SfxUInt32Item* pWhatPage =
rReq.GetArg(ID_VAL_WHATPAGE);
-
SlideShow::GetSlideShow(GetViewShellBase())->jumpToPageNumber(static_cast((pWhatPage->GetValue()-1)>>1));
+if (const SfxUInt32Item* pWhatPage =
rReq.GetArg(ID_VAL_WHATPAGE))
+
SlideShow::GetSlideShow(GetViewShellBase())->jumpToPageNumber(static_cast((pWhatPage->GetValue()-1)>>1));
}
else
{
[Libreoffice-commits] core.git: sfx2/source
sfx2/source/doc/iframe.cxx |5 -
1 file changed, 4 insertions(+), 1 deletion(-)
New commits:
commit 2da7cb9462a98d37191132b6eec13a3ab0da147a
Author: Caolán McNamara
AuthorDate: Fri Apr 7 16:44:39 2023 +0100
Commit: Caolán McNamara
CommitDate: Fri Apr 7 22:50:57 2023 +0200
set an InteractionHandler with the embedded frame as dialog parent
for any warning dialogs that may appear
Change-Id: Ibb8f90b60cb1af625b0dc57d2f9fd01964fa9bba
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/150128
Tested-by: Jenkins
Reviewed-by: Caolán McNamara
diff --git a/sfx2/source/doc/iframe.cxx b/sfx2/source/doc/iframe.cxx
index 8d1504979e3e..b30063ee382e 100644
--- a/sfx2/source/doc/iframe.cxx
+++ b/sfx2/source/doc/iframe.cxx
@@ -24,6 +24,7 @@
#include
#include
#include
+#include
#include
#include
#include
@@ -199,9 +200,11 @@ sal_Bool SAL_CALL IFrameObject::load(
if ( xFramesSupplier.is() )
mxFrame->setCreator( xFramesSupplier );
+uno::Reference
xInteractionHandler(task::InteractionHandler::createWithParent(mxContext,
xWin));
uno::Sequence < beans::PropertyValue > aProps{
comphelper::makePropertyValue("PluginMode", sal_Int16(2)),
-comphelper::makePropertyValue("ReadOnly", true)
+comphelper::makePropertyValue("ReadOnly", true),
+comphelper::makePropertyValue("InteractionHandler",
xInteractionHandler)
};
uno::Reference < frame::XDispatch > xDisp = mxFrame->queryDispatch(
aTargetURL, "_self", 0 );
if ( xDisp.is() )
[Libreoffice-bugs] [Bug 152537] No obvious UI to set the document default font used e.g. in Line Numbering
https://bugs.documentfoundation.org/show_bug.cgi?id=152537 --- Comment #23 from Mike Kaganski --- Created attachment 186537 --> https://bugs.documentfoundation.org/attachment.cgi?id=186537=edit A minimized FODT from a real document with non-standard default-style affecting page background The attachment contains a minimal reproducer of the same problem. Namely, in https://forumooo.ru/index.php?topic=9750, a document appeared with page background set, but not active in the text body and header/footer, despite all the properties of page, paragraphs, and characters (style and direct) do not set the white background. The problem is this: It defines the background, and it has *no* UI at all. User has no way to "fix" the document (or to set up such an effect themselves, if desired). I don't know where the problematic document came from. Maybe it is generated by another ODF generator. But the lack of UI for the wide range of settings available in those style:default-style elements is bad. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 154705] New: Enhancement: Add Snap to Intersection
https://bugs.documentfoundation.org/show_bug.cgi?id=154705 Bug ID: 154705 Summary: Enhancement: Add Snap to Intersection Product: LibreOffice Version: 7.4.6.2 release Hardware: All OS: Windows (All) Status: UNCONFIRMED Severity: normal Priority: medium Component: Draw Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: dmatsch...@quietriding.com Created attachment 186536 --> https://bugs.documentfoundation.org/attachment.cgi?id=186536=edit Pattern for drawing 7 sided regular polygon by connecting intersections of lines with circle. It would be nice to be able to snap to an intersection of two lines. For example, the intersection of the circumference of a circle and a line running from the center of the circle to a point beyond the circle. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-ux-advise] [Bug 41542] FORMATTING: Allow "Spacing to contents" for edges without a line
https://bugs.documentfoundation.org/show_bug.cgi?id=41542 Justin L changed: What|Removed |Added See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=15 ||4704 -- You are receiving this mail because: You are on the CC list for the bug.
[Libreoffice-bugs] [Bug 154704] New: Wrong section of frame area covered by paragraph background colour
https://bugs.documentfoundation.org/show_bug.cgi?id=154704 Bug ID: 154704 Summary: Wrong section of frame area covered by paragraph background colour Product: LibreOffice Version: 5.3 all versions Hardware: All OS: All Status: UNCONFIRMED Keywords: bibisected, bisected Severity: minor Priority: medium Component: Writer Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: jl...@mail.com CC: jl...@mail.com Created attachment 186535 --> https://bugs.documentfoundation.org/attachment.cgi?id=186535=edit n592908-frameC_word2010.pdf: how it looks in MS Word In attachment 186534 (From bug 154703) we have a frame with 3 paragraphs. The first two paragraphs have a different background colour specified, and the third is empty. The problem is that the second (empty) paragraph's blue band is covering a couple of lines of text from paragraph one. This is because the paragraph has a top border spacing defined, and that is applying even though the properties "merge with the next paragraph". It became visible with LO 5.3 commit 9130627e21dd7c52c5eee1acc4b71f86eb9f3118 Author: Justin Luth on Mon Oct 31 11:59:09 2016 +0300 tdf#41542 globally allow padding without borders: layout I don't think I'd call this a regression - I think it exposed an existing failure to absorb the merged spacing. Prior to this there was a "white gap" between the paragraphs - it is good that this gap at least is gone. I was not able to replicate this in a clean document though... reducing severity. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 130199] Confirm deletion of hidden sections
https://bugs.documentfoundation.org/show_bug.cgi?id=130199 Balázs Varga (allotropia) changed: What|Removed |Added Status|NEW |ASSIGNED Assignee|libreoffice-b...@lists.free |balazs.varga...@gmail.com |desktop.org | -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 104461] [META] DOCX (OOXML) frame-related issues
https://bugs.documentfoundation.org/show_bug.cgi?id=104461 Justin L changed: What|Removed |Added Depends on||154703 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=154703 [Bug 154703] META Export DOCX flies with framePr instead of DrawingDML -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 154703] New: META Export DOCX flies with framePr instead of DrawingDML
https://bugs.documentfoundation.org/show_bug.cgi?id=154703 Bug ID: 154703 Summary: META Export DOCX flies with framePr instead of DrawingDML Product: LibreOffice Version: unspecified Hardware: All OS: All Status: UNCONFIRMED Keywords: filter:docx Severity: enhancement Priority: medium Component: Writer Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: jl...@mail.com CC: jl...@mail.com Depends on: 105035 Blocks: 104461 Created attachment 186534 --> https://bugs.documentfoundation.org/attachment.cgi?id=186534=edit n592908-frameC.docx: top frame border spacing copied to paragraph border spacing Currently the only time that framePr is exported is if framePr settings are grabbaged on import. Otherwise (most) frames are exported as a DrawingML shape - which is imported as an editeng drawing object. An exploration into exporting textboxes and captions using framePr can be found at https://gerrit.libreoffice.org/c/core/+/150114. FramePr PROs: • simple xml • imports as SW native – not a synchronized editeng monstrosity, better styles, text area is already MS Word compatible. FramePr CONs • no overlap setting – layout decision to overlap sequential framePRs is somewhat arbitrary. • limited wrapping choices. No before/after/through • relatively poor export support currently – missing background/shadow/links • not allowed in header/footer (at least, that is LO export rule) • layout loops might occur: regression danger from making a change. DrawingML PROs: • encourages code improvements to editeng • full wrapping support DrawingML CONs: • LO imports as draw frame sync’d to hidden SW frame. Causes layout issues • poor anchor import - only TO-CHAR or AS-CHAR – often translates to poor placement emulation This is a META kind of report. My intention is to add documents that highlight a specific issue so that the CONs (of both types) can be alleviated. This first attachment shows top/left margins being duplicated on framePr import (I assume). It bibisects to 3.3.1 (3.3.0 was OK). [Note - prior to 4.4, you need to look at the number in the dialog box, not at the layout.]. Duplicate left/right margins tend to be (mostly) absorbed in LO for some reason, but top margins are applied twice. Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=104461 [Bug 104461] [META] DOCX (OOXML) frame-related issues https://bugs.documentfoundation.org/show_bug.cgi?id=105035 [Bug 105035] FILEOPEN DOCX changed framePr: Two frames, anchored to the same paragraph, imported as a single frame (comment 7) -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 105035] FILEOPEN DOCX changed framePr: Two frames, anchored to the same paragraph, imported as a single frame (comment 7)
https://bugs.documentfoundation.org/show_bug.cgi?id=105035 Justin L changed: What|Removed |Added Blocks||154703 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=154703 [Bug 154703] META Export DOCX flies with framePr instead of DrawingDML -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-commits] core.git: Branch 'libreoffice-7-5' - sc/source
sc/source/core/data/table6.cxx |2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
New commits:
commit f2fb7d930b10626d9987b0ed52cc8e6a281c0f0d
Author: Andreas Heinisch
AuthorDate: Mon Apr 3 12:58:27 2023 +0200
Commit: Xisco Fauli
CommitDate: Fri Apr 7 21:49:24 2023 +0200
tdf#89920 - Handle embedded newline in Calc's search cell
Update short-circuited boolean expression so the least expensive
subexpressions will be executed first
Change-Id: I8c924e00e8de809f3e6df2828f8537185e71c18c
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/149891
Tested-by: Jenkins
Reviewed-by: Andreas Heinisch
(cherry picked from commit 8fc316fb65e0d4b78ec881aa79f4184602b96f54)
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/150140
Reviewed-by: Xisco Fauli
diff --git a/sc/source/core/data/table6.cxx b/sc/source/core/data/table6.cxx
index 1ea4a5ace99d..a6b03f6b3d8d 100644
--- a/sc/source/core/data/table6.cxx
+++ b/sc/source/core/data/table6.cxx
@@ -257,7 +257,7 @@ bool ScTable::SearchCell(const SvxSearchItem& rSearchItem,
SCCOL nCol, sc::Colum
pFCell->SetMatColsRows( nMatCols, nMatRows );
aCol[nCol].SetFormulaCell(nRow, pFCell);
}
-else if (aString.indexOf('\n') != -1 && eCellType != CELLTYPE_FORMULA)
+else if (eCellType != CELLTYPE_FORMULA && aString.indexOf('\n') != -1)
{
ScFieldEditEngine& rEngine = rDocument.GetEditEngine();
rEngine.SetTextCurrentDefaults(aString);
[Libreoffice-bugs] [Bug 149100] LibreOffice crashes on startup in Fedora
https://bugs.documentfoundation.org/show_bug.cgi?id=149100 Piotr Dobrogost changed: What|Removed |Added Version|7.3.3.2 release |7.5.2.2 release -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 149100] LibreOffice crashes on startup in Fedora
https://bugs.documentfoundation.org/show_bug.cgi?id=149100 Piotr Dobrogost changed: What|Removed |Added Status|NEEDINFO|UNCONFIRMED Ever confirmed|1 |0 --- Comment #7 from Piotr Dobrogost --- (In reply to Julien Nabet from comment #5) > vvillenave indicated (reporter of tdf#151163) indicated he didn't reproduce > this with LO 7.4.1. > Piotr: would it be possible you give a try to 7.4.1? > > It could be either WFM (since it would work with 7.4.1) or NOTOURBUG since > it seems to be Fedora specific pb (perhaps a packaging/dependency pb). I've since upgraded OS to Fedora 38 thus I have LibreOffice 7.5.2.2 50(Build:2) now. Running libreoffice from the shell I get the following error in the console: - $ libreoffice LibreOffice 7.5 - Fatal Error: The application cannot be started. LibreOffice user installation could not be processed due to missing access rights. Please make sure that you have sufficient access rights for the following location and restart LibreOffice: /home/miner/.config/libreoffice/4 - cloph at #libreoffice pointed the following: "that message is generated if there's not enough diskspace or when there's no write access. https://git.libreoffice.org/core/+/master/desktop/source/app/app.cxx#866 (STR_BOOTSTRAP_ERR_NOACCESSRIGHTS)" However it's odd because I'm the owner of /home/miner and everything inside it, there is free space and access rights are normal: $ ls -ld ~/.config/libreoffice/4 drwx--. 3 miner miner 4096 kwi 3 21:44 /home/miner/.config/libreoffice/4 $ df ~ Filesystem 1K-blocks Used Available Use% Mounted on /dev/mapper/miner1_vg1-home 58249212 33688412 21569492 61% /home $ lsattr -d ~/.config/libreoffice/4 --e--- /home/miner/.config/libreoffice/4 $ getfacl ~/.config/libreoffice/4 getfacl: Removing leading '/' from absolute path names # file: home/miner/.config/libreoffice/4 # owner: miner # group: miner user::rwx group::--- other::--- $ ls -Z ~/.config/libreoffice/4 unconfined_u:object_r:config_home_t:s0 user $ rm -r /home/miner/.config/libreoffice && mkdir -p /home/miner/.config/libreoffice && ls -ld /home/miner/.config/libreoffice/ drwxr-xr-x. 2 miner miner 4096 kwi 7 21:30 /home/miner/.config/libreoffice/ The question is if the cause of this error and the cause of previous crashes is the same or in other words if we are dealing with the same problem and only symptoms changed (arguably for better as now we have clear error message at least)? I suspect that's the case as the system is still the same (albeit upgraded) and the error happens in the same phase (application's startup). -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 154551] Cutting a caption from a frame results in crash
https://bugs.documentfoundation.org/show_bug.cgi?id=154551 Buovjaga changed: What|Removed |Added OS|All |Windows (All) -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 151358] Languagetool not working in latest Libreoffice release after setup
https://bugs.documentfoundation.org/show_bug.cgi?id=151358 --- Comment #15 from Alex Thurgood --- (In reply to Alex Thurgood from comment #14) > > I hope that this helps! > > I wonder If you can point me to some tutorial explaining how to find out > > what is preventing the functioning of LT for those two languages (DE and EN) > > when I am not in safe mode. > > Unfortunately, I have no idea how it is supposed to work. > For me currently, spellchecking is broken on macOS Arm, generally, let alone > some new fangled function that received no testing on macOS before release, > as usual. Sorry, of course the LT extension has been around for a while, but I've only ever used the built in spellchecker. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 151358] Languagetool not working in latest Libreoffice release after setup
https://bugs.documentfoundation.org/show_bug.cgi?id=151358 --- Comment #14 from Alex Thurgood --- > I hope that this helps! > I wonder If you can point me to some tutorial explaining how to find out > what is preventing the functioning of LT for those two languages (DE and EN) > when I am not in safe mode. Unfortunately, I have no idea how it is supposed to work. For me currently, spellchecking is broken on macOS Arm, generally, let alone some new fangled function that received no testing on macOS before release, as usual. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 154344] LibreOffice Writer: Track Changes edits not saved in auto recovery
https://bugs.documentfoundation.org/show_bug.cgi?id=154344 documentfoundation.oy...@simplelogin.com changed: What|Removed |Added Status|NEEDINFO|UNCONFIRMED Ever confirmed|1 |0 --- Comment #2 from documentfoundation.oy...@simplelogin.com --- Was unable to reproduce bug on further testing with safe mod on or off. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 154699] UI: Add Compress image dialog to the Image properties dialog
https://bugs.documentfoundation.org/show_bug.cgi?id=154699 Telesto changed: What|Removed |Added Keywords||needsUXEval CC||libreoffice-ux-advise@lists ||.freedesktop.org -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-ux-advise] [Bug 154699] UI: Add Compress image dialog to the Image properties dialog
https://bugs.documentfoundation.org/show_bug.cgi?id=154699 Telesto changed: What|Removed |Added Keywords||needsUXEval CC||libreoffice-ux-advise@lists ||.freedesktop.org -- You are receiving this mail because: You are on the CC list for the bug.
[Libreoffice-bugs] [Bug 154702] New: UI: Background Cell Color Resetting
https://bugs.documentfoundation.org/show_bug.cgi?id=154702 Bug ID: 154702 Summary: UI: Background Cell Color Resetting Product: LibreOffice Version: 7.5.1.2 release Hardware: x86-64 (AMD64) OS: All Status: UNCONFIRMED Severity: minor Priority: medium Component: Calc Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: hegqu...@gmail.com Description: I have customized toolbar with multiple "Background Color" commands. They default to yellow but I change them to an array of colors to keep my spreadsheets organized. Since the update, they will refresh every minute or so all back to the default yellow. Steps to Reproduce: 1. Change the color of a cell to something other than the default yellow. 2. Type anything into any cell. 3. Toolbar will reset the color selection back to default yellow. Actual Results: The "Background Color" button will change from the previously selected color back to default yellow. Expected Results: Every other version of Calc has kept the color selection chosen until the program is closed. Reproducible: Always User Profile Reset: Yes Additional Info: Nothing further to add. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 154680] Typing into font family field shows autocompleted font name as missing, when multiple cells selected with different fonts
https://bugs.documentfoundation.org/show_bug.cgi?id=154680 --- Comment #8 from Commit Notification --- Caolán McNamara committed a patch related to this issue. It has been pushed to "libreoffice-7-5": https://git.libreoffice.org/core/commit/c1ab43ff9a7601998685ff4a1300d6050e0c5c92 Resolves: tdf#154680 don't mark an empty fontname as italic for "unknown" It will be available in 7.5.3. The patch should be included in the daily builds available at https://dev-builds.libreoffice.org/daily/ in the next 24-48 hours. More information about daily builds can be found at: https://wiki.documentfoundation.org/Testing_Daily_Builds Affected users are encouraged to test the fix and report feedback. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 154680] Typing into font family field shows autocompleted font name as missing, when multiple cells selected with different fonts
https://bugs.documentfoundation.org/show_bug.cgi?id=154680 Commit Notification changed: What|Removed |Added Whiteboard|target:7.6.0|target:7.6.0 target:7.5.3 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-commits] core.git: Branch 'libreoffice-7-5' - svx/source
svx/source/tbxctrls/tbcontrl.cxx | 13 ++---
1 file changed, 10 insertions(+), 3 deletions(-)
New commits:
commit c1ab43ff9a7601998685ff4a1300d6050e0c5c92
Author: Caolán McNamara
AuthorDate: Fri Apr 7 11:34:11 2023 +0100
Commit: Adolfo Jayme Barrientos
CommitDate: Fri Apr 7 20:31:00 2023 +0200
Resolves: tdf#154680 don't mark an empty fontname as italic for "unknown"
its used for 'ambigious' rather than 'unknown'
Change-Id: I1aeb2f825c5e611e0a943a6ce5f3ab58658701bf
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/150136
Tested-by: Jenkins
Reviewed-by: Adolfo Jayme Barrientos
diff --git a/svx/source/tbxctrls/tbcontrl.cxx b/svx/source/tbxctrls/tbcontrl.cxx
index b1f54a303e13..034a46645ff4 100644
--- a/svx/source/tbxctrls/tbcontrl.cxx
+++ b/svx/source/tbxctrls/tbcontrl.cxx
@@ -350,6 +350,8 @@ protected:
".uno:CharEndPreviewFontName",
aArgs );
}
+
+boolCheckFontIsAvailable(std::u16string_view fontname);
voidCheckAndMarkUnknownFont();
public:
@@ -1752,16 +1754,21 @@ void SvxFontNameBox_Base::FillList()
m_xWidget->select_entry_region(nStartPos, nEndPos);
}
+bool SvxFontNameBox_Base::CheckFontIsAvailable(std::u16string_view fontname)
+{
+lcl_GetDocFontList(, this);
+return pFontList && pFontList->IsAvailable(fontname);
+}
+
void SvxFontNameBox_Base::CheckAndMarkUnknownFont()
{
if (mbCheckingUnknownFont) //tdf#117537 block rentry
return;
mbCheckingUnknownFont = true;
OUString fontname = m_xWidget->get_active_text();
-lcl_GetDocFontList( , this );
-// If the font is unknown, show it in italic.
+// tdf#154680 If a font is set and that font is unknown, show it in italic.
vcl::Font font = m_xWidget->get_entry_font();
-if( pFontList != nullptr && pFontList->IsAvailable( fontname ))
+if (fontname.isEmpty() || CheckFontIsAvailable(fontname))
{
if( font.GetItalic() != ITALIC_NONE )
{
[Libreoffice-bugs] [Bug 154406] Euro symbol not printed
https://bugs.documentfoundation.org/show_bug.cgi?id=154406 --- Comment #4 from Laurens --- @Dieter I tested 7.5.2.2 and the result is the same, no euro symbol printed. I had time to test some further and discovered that the bug can be narrowed down to FinePrint as the euro symbol did print OK on other printers I have installed. Overlooked this as the fact that the euro symbol was printed correctly from Ms Word 2021 to FinePrint put me on the wrong track. Tested with: >From LO 7.5.2.2 to: FinePrint 6.11: Fail Brother DCP-L2550DN: OK Brother DCP-L2550DN BR-Script3: OK CutePDF Writer: OK PDF24: OK Microsoft Print to PDF: OK >From Ms Word 2021 to: FinePrint 6.11: OK Brother DCP-L2550DN: OK Brother DCP-L2550DN BR-Script3: OK CutePDF Writer: OK PDF24: OK Microsoft Print to PDF: OK So it seems FinePrint is the only printer that does not print the euro symbol. However, I still wonder why it does print it when printed from Word. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 104394] FILEOPEN DOCX: Textbox is missing
https://bugs.documentfoundation.org/show_bug.cgi?id=104394 Justin L changed: What|Removed |Added Assignee|libreoffice-b...@lists.free |jl...@mail.com |desktop.org | -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 154478] Fileopen DOCX: Comments empty after ToC
https://bugs.documentfoundation.org/show_bug.cgi?id=154478 Gabor Kelemen (allotropia) changed: What|Removed |Added CC||kelem...@ubuntu.com Regression By||Thorsten Behrens -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 154572] Scroll by mouse wheel not correctly when rows are fixed
https://bugs.documentfoundation.org/show_bug.cgi?id=154572 --- Comment #6 from stefan_lange...@t-online.de --- (In reply to Xisco Faulí from comment #5) > (In reply to Telesto from comment #4) > > @Xisco > > (In reply to stefan_lange...@t-online.de from comment #3) > > > Can it be the repository Win64-7.6 for bisect is updated not often enough? > > updated Many thanks! I have updated my cloned data and started a new bisect test. Result: I still cannot reproduce the the buggy behavior with the latest build (master)! But I have checked the information given to the BuildId 8bec0ff56c53e80be81a9f463fd1fd21ade33151 and I have seen there is a new commit (today, Fri Apr 07 2023 10:13:29) from Caolán McNamara to fix tdf#154679 "unable to scroll with mouse wheel with frozen rows". The behavior described in tdf#154679 largely corresponds to that I have described in bug 154572. Therefore I think bug 154572 is a duplicate (or a general description) of the behavior described in tdf#154679 and I will check with the next coming build of LOdev7.6 if bug 154572 is resolved too. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-commits] core.git: Branch 'libreoffice-7-5' - sw/source
sw/source/uibase/sidebar/WriterInspectorTextPanel.cxx | 18 ++
sw/source/uibase/sidebar/WriterInspectorTextPanel.hxx |5 -
2 files changed, 22 insertions(+), 1 deletion(-)
New commits:
commit 23b09987e06f637bd864f40d8cc43def8d8eaa18
Author: Caolán McNamara
AuthorDate: Thu Apr 6 12:17:10 2023 +0100
Commit: Xisco Fauli
CommitDate: Fri Apr 7 18:48:29 2023 +0200
tdf#154629 inspector sidebar panel use-after-free on switch to print preview
Change-Id: I5489cd18213d82ae4174ca8d9d00f1da5aa1091d
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/150078
Tested-by: Jenkins
Reviewed-by: Xisco Fauli
diff --git a/sw/source/uibase/sidebar/WriterInspectorTextPanel.cxx
b/sw/source/uibase/sidebar/WriterInspectorTextPanel.cxx
index 5f861000296a..8786a0390950 100644
--- a/sw/source/uibase/sidebar/WriterInspectorTextPanel.cxx
+++ b/sw/source/uibase/sidebar/WriterInspectorTextPanel.cxx
@@ -70,6 +70,10 @@
WriterInspectorTextPanel::WriterInspectorTextPanel(weld::Widget* pParent)
{
m_oldLink = m_pShell->GetChgLnk();
m_pShell->SetChgLnk(LINK(this, WriterInspectorTextPanel,
AttrChangedNotify));
+
+// tdf#154629 listen to know if the shell destructs before this panel
does,
+// which can happen on entering print preview
+m_pShell->Add(this);
}
// Update panel on start
@@ -80,10 +84,24 @@
WriterInspectorTextPanel::WriterInspectorTextPanel(weld::Widget* pParent)
updateEntries(aStore, m_nParIdx);
}
+void WriterInspectorTextPanel::SwClientNotify(const SwModify& rModify, const
SfxHint& rHint)
+{
+if (rHint.GetId() == SfxHintId::SwLegacyModify)
+{
+const sw::LegacyModifyHint& rLegacy = static_cast(rHint);
+if (rLegacy.GetWhich() == RES_OBJECTDYING)
+m_pShell = nullptr;
+}
+SwClient::SwClientNotify(rModify, rHint);
+}
+
WriterInspectorTextPanel::~WriterInspectorTextPanel()
{
if (m_pShell)
+{
m_pShell->SetChgLnk(m_oldLink);
+m_pShell->Remove(this);
+}
}
static OUString PropertyNametoRID(const OUString& rName)
diff --git a/sw/source/uibase/sidebar/WriterInspectorTextPanel.hxx
b/sw/source/uibase/sidebar/WriterInspectorTextPanel.hxx
index fae619018851..2c2df34a9400 100644
--- a/sw/source/uibase/sidebar/WriterInspectorTextPanel.hxx
+++ b/sw/source/uibase/sidebar/WriterInspectorTextPanel.hxx
@@ -19,12 +19,13 @@
#pragma once
#include
+#include
class SwWrtShell;
namespace sw::sidebar
{
-class WriterInspectorTextPanel final : public svx::sidebar::InspectorTextPanel
+class WriterInspectorTextPanel final : public
svx::sidebar::InspectorTextPanel, public SwClient
{
public:
static std::unique_ptr Create(weld::Widget* pParent);
@@ -40,6 +41,8 @@ private:
// attributes have changed
DECL_LINK(AttrChangedNotify, LinkParamNone*, void);
+
+virtual void SwClientNotify(const SwModify&, const SfxHint& rHint)
override;
};
} // end of namespace svx::sidebar
[Libreoffice-commits] core.git: Branch 'libreoffice-7-5' - sc/source
sc/source/core/tool/addincol.cxx | 54 ---
1 file changed, 45 insertions(+), 9 deletions(-)
New commits:
commit c3ab1cb764a368a8b2642e73c744dee9282cfd4b
Author: Eike Rathke
AuthorDate: Mon Apr 3 19:28:59 2023 +0200
Commit: Xisco Fauli
CommitDate: Fri Apr 7 18:46:44 2023 +0200
Resolves: tdf#154582 Obtain English DisplayName before CompatibilityName
... for Add-Ins from configuration.
Change-Id: If13d692ca7550e69d2f6e3ff72747d17aee3e7f7
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/149995
Reviewed-by: Eike Rathke
Tested-by: Jenkins
(cherry picked from commit dcb50fe7444dd746ba4d3f8476026bb997a595b5)
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/149976
Reviewed-by: Xisco Fauli
diff --git a/sc/source/core/tool/addincol.cxx b/sc/source/core/tool/addincol.cxx
index 99f8061df3d2..9ddc97f0cb5b 100644
--- a/sc/source/core/tool/addincol.cxx
+++ b/sc/source/core/tool/addincol.cxx
@@ -360,7 +360,8 @@ void ScUnoAddInCollection::ReadConfiguration()
ScAddInCfg& rAddInConfig = SC_MOD()->GetAddInCfg();
-// additional, temporary config item for the compatibility names
+// Additional, temporary config item for the display names and
+// compatibility names.
ScLinkConfigItem aAllLocalesConfig( CFGPATH_ADDINS,
ConfigItemMode::AllLocales );
// CommitLink is not used (only reading values)
@@ -441,6 +442,35 @@ void ScUnoAddInCollection::ReadConfiguration()
nCategory = lcl_GetCategory( aCategoryName );
}
+// get English display name
+
+OUString aDisplayNamePath(aFuncPropPath + CFGSTR_DISPLAYNAME);
+uno::Sequence aDisplayNamePropNames(
, 1 );
+
+uno::Sequence aDisplayNameProperties =
aAllLocalesConfig.GetProperties( aDisplayNamePropNames );
+if ( aDisplayNameProperties.getLength() == 1 )
+{
+uno::Sequence aLocalEntries;
+if ( aDisplayNameProperties[0] >>= aLocalEntries )
+{
+for ( const beans::PropertyValue& rConfig :
std::as_const(aLocalEntries) )
+{
+// PropertyValue name is the locale ("convert" from
+// string to canonicalize).
+OUString aLocale( LanguageTag( rConfig.Name,
true).getBcp47( false));
+// PropertyValue value is the localized value
(string in this case).
+OUString aName;
+rConfig.Value >>= aName;
+// Accept 'en' and 'en-...' but prefer 'en-US'.
+if (aLocale == "en-US" && !aName.isEmpty())
+aEnglishName = aName;
+else if (aEnglishName.isEmpty() && (aLocale ==
"en" || aLocale.startsWith("en-")))
+aEnglishName = aName;
+}
+}
+}
+bool bNeedEnglish = aEnglishName.isEmpty();
+
// get compatibility names
::std::vector aCompNames;
@@ -457,17 +487,23 @@ void ScUnoAddInCollection::ReadConfiguration()
for ( const beans::PropertyValue& rConfig :
std::as_const(aLocalEntries) )
{
// PropertyValue name is the locale ("convert" from
-// string to canonicalize)
+// string to canonicalize).
OUString aLocale( LanguageTag( rConfig.Name,
true).getBcp47( false));
-// PropertyValue value is the localized value
(string in this case)
+// PropertyValue value is the localized value
(string in this case).
OUString aName;
rConfig.Value >>= aName;
-aCompNames.emplace_back( aLocale, aName);
-// Accept 'en' and 'en-...' but prefer 'en-US'.
-if (aLocale == "en-US")
-aEnglishName = aName;
-else if (aEnglishName.isEmpty() && (aLocale ==
"en" || aLocale.startsWith("en-")))
-aEnglishName = aName;
+if (!aName.isEmpty())
+{
+aCompNames.emplace_back( aLocale, aName);
+if (bNeedEnglish)
+{
+// Accept 'en' and 'en-...' but prefer
'en-US'.
+if (aLocale == "en-US")
+aEnglishName = aName;
+else if
