[Libreoffice-bugs] [Bug 56126] EDITING: Conditional field and vertical separator
https://bugs.documentfoundation.org/show_bug.cgi?id=56126 --- Comment #11 from Paul Monnerat --- Bug persistant Version: 6.1.6.3 (x64) Build ID: 5896ab1714085361c45cf540f76f60673dd96a72 Threads CPU : 8; OS : Windows 10.0; UI Render : par défaut; Locale : fr-CH (fr_CH); Calc: group threaded -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 124936] Help->About LibreOffice dialog does not specify whether 32 or 64 bit is installed
https://bugs.documentfoundation.org/show_bug.cgi?id=124936 --- Comment #10 from Takeshi Abe --- (In reply to MM from comment #9) Uploaded a patch: https://gerrit.libreoffice.org/#/c/73211/ -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-commits] core.git: Branch 'distro/collabora/cp-6.0' - chart2/source
chart2/source/view/main/ChartView.cxx |4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
New commits:
commit dc4f3a6b13035d70ecd2f8d7ccc937afec7e5564
Author: Tamás Zolnai
AuthorDate: Tue May 28 17:32:44 2019 +0200
Commit: Andras Timar
CommitDate: Fri May 31 07:35:24 2019 +0200
tdf#122765: Legend interferes with pie chart after pptx import, second part
Revert of:
2903c5f59d257b6ab94f32df64513f2edf94fb0b
Reverting this commit does not lead to the original bug
to come back, so we can revert it without a problem.
Change-Id: I244a6b9451c47e1094db8a77c71b6696e0c464cc
Reviewed-on: https://gerrit.libreoffice.org/73139
Reviewed-by: Tamás Zolnai
Tested-by: Tamás Zolnai
(cherry picked from commit 63d17d01da0f9e3a7554e4327244ee4457b7188d)
Reviewed-on: https://gerrit.libreoffice.org/73160
Reviewed-by: Andras Timar
Tested-by: Andras Timar
diff --git a/chart2/source/view/main/ChartView.cxx
b/chart2/source/view/main/ChartView.cxx
index 49c598709280..ec2c62c823fc 100644
--- a/chart2/source/view/main/ChartView.cxx
+++ b/chart2/source/view/main/ChartView.cxx
@@ -1619,7 +1619,6 @@ awt::Rectangle ChartView::impl_createDiagramAndContent(
const CreateShapeParam2D
uno::Reference< drawing::XShapes > xSeriesTargetInFrontOfAxis(nullptr);
uno::Reference< drawing::XShapes > xSeriesTargetBehindAxis(nullptr);
VDiagram aVDiagram(xDiagram, aPreferredAspectRatio, nDimensionCount);
-bool bIsPieOrDonut = lcl_IsPieOrDonut(xDiagram);
{//create diagram
aVDiagram.init(rParam.mxDiagramWithAxesShapes, m_xShapeFactory);
aVDiagram.createShapes(
@@ -1628,7 +1627,7 @@ awt::Rectangle ChartView::impl_createDiagramAndContent(
const CreateShapeParam2D
xSeriesTargetInFrontOfAxis = aVDiagram.getCoordinateRegion();
// It is preferable to use full size than minimum for pie charts
-if (!bIsPieOrDonut && !rParam.mbUseFixedInnerSize)
+if (!rParam.mbUseFixedInnerSize)
aVDiagram.reduceToMimimumSize();
}
@@ -1656,6 +1655,7 @@ awt::Rectangle ChartView::impl_createDiagramAndContent(
const CreateShapeParam2D
//use first coosys only so far; todo: calculate for more than one coosys
if we have more in future
//todo: this is just a workaround at the moment for pie and donut labels
+bool bIsPieOrDonut = lcl_IsPieOrDonut(xDiagram);
if( !bIsPieOrDonut && (!rVCooSysList.empty()) )
{
VCoordinateSystem* pVCooSys = rVCooSysList[0];
___
Libreoffice-commits mailing list
libreoffice-comm...@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice-commits
[Libreoffice-commits] core.git: Branch 'distro/collabora/cp-6.0' - chart2/qa
chart2/qa/extras/chart2dump/chart2dump.cxx|1 chart2/qa/extras/chart2dump/data/tdf118150.xlsx |binary chart2/qa/extras/chart2dump/reference/axislabeltest/tdf118150.txt | 216 ++ 3 files changed, 217 insertions(+) New commits: commit 81b3245fb2834c0da61ba8ca6f9245847345b749 Author: Tamás Zolnai AuthorDate: Tue May 21 12:05:33 2019 +0200 Commit: Andras Timar CommitDate: Fri May 31 07:34:16 2019 +0200 Add unit test for tdf#118150. Change-Id: Icea2c8aacb36e843dad67a056d07d6495fbbb17a Reviewed-on: https://gerrit.libreoffice.org/72678 Tested-by: Jenkins Reviewed-by: Tamás Zolnai (cherry picked from commit a703b4d8842261f55f489c28352df1f53a9b070a) Reviewed-on: https://gerrit.libreoffice.org/72766 Reviewed-by: Andras Timar Tested-by: Andras Timar diff --git a/chart2/qa/extras/chart2dump/chart2dump.cxx b/chart2/qa/extras/chart2dump/chart2dump.cxx index c852446efe7e..90daeef87e1f 100644 --- a/chart2/qa/extras/chart2dump/chart2dump.cxx +++ b/chart2/qa/extras/chart2dump/chart2dump.cxx @@ -648,6 +648,7 @@ DECLARE_DUMP_TEST(AxisLabelTest, Chart2DumpTest, false) "rotated_axis_labels.odp", "formated_axis_labels.odp", "percent_stacked_column_chart.odp", +"tdf118150.xlsx", }; for (const OUString& sTestFile : aTestFiles) diff --git a/chart2/qa/extras/chart2dump/data/tdf118150.xlsx b/chart2/qa/extras/chart2dump/data/tdf118150.xlsx new file mode 100644 index ..f29b9a1c2e66 Binary files /dev/null and b/chart2/qa/extras/chart2dump/data/tdf118150.xlsx differ diff --git a/chart2/qa/extras/chart2dump/reference/axislabeltest/tdf118150.txt b/chart2/qa/extras/chart2dump/reference/axislabeltest/tdf118150.txt new file mode 100644 index ..fabf4acac67b --- /dev/null +++ b/chart2/qa/extras/chart2dump/reference/axislabeltest/tdf118150.txt @@ -0,0 +1,216 @@ +/// CID/D=0:CS=0:Axis=0,0 +// nAxisLabelsCount +28 +// xLabel->getString() +Sep 2013 +// static_cast(aLabelFontColor) +0 +// fLabelFontHeight +10 +// xLabel->getString() +Oct 2013 +// static_cast(aLabelFontColor) +0 +// fLabelFontHeight +10 +// xLabel->getString() +Nov 2013 +// static_cast(aLabelFontColor) +0 +// fLabelFontHeight +10 +// xLabel->getString() +Dec 2013 +// static_cast(aLabelFontColor) +0 +// fLabelFontHeight +10 +// xLabel->getString() +Jan 2014 +// static_cast(aLabelFontColor) +0 +// fLabelFontHeight +10 +// xLabel->getString() +Feb 2014 +// static_cast(aLabelFontColor) +0 +// fLabelFontHeight +10 +// xLabel->getString() +Mar 2014 +// static_cast(aLabelFontColor) +0 +// fLabelFontHeight +10 +// xLabel->getString() +Apr 2014 +// static_cast(aLabelFontColor) +0 +// fLabelFontHeight +10 +// xLabel->getString() +May 2014 +// static_cast(aLabelFontColor) +0 +// fLabelFontHeight +10 +// xLabel->getString() +Jun 2014 +// static_cast(aLabelFontColor) +0 +// fLabelFontHeight +10 +// xLabel->getString() +Jul 2014 +// static_cast(aLabelFontColor) +0 +// fLabelFontHeight +10 +// xLabel->getString() +Aug 2014 +// static_cast(aLabelFontColor) +0 +// fLabelFontHeight +10 +// xLabel->getString() +Sep 2014 +// static_cast(aLabelFontColor) +0 +// fLabelFontHeight +10 +// xLabel->getString() +Oct 2014 +// static_cast(aLabelFontColor) +0 +// fLabelFontHeight +10 +// xLabel->getString() +Nov 2014 +// static_cast(aLabelFontColor) +0 +// fLabelFontHeight +10 +// xLabel->getString() +Dec 2014 +// static_cast(aLabelFontColor) +0 +// fLabelFontHeight +10 +// xLabel->getString() +Jan 2015 +// static_cast(aLabelFontColor) +0 +// fLabelFontHeight +10 +// xLabel->getString() +Feb 2015 +// static_cast(aLabelFontColor) +0 +// fLabelFontHeight +10 +// xLabel->getString() +Mar 2015 +// static_cast(aLabelFontColor) +0 +// fLabelFontHeight +10 +// xLabel->getString() +Apr 2015 +// static_cast(aLabelFontColor) +0 +// fLabelFontHeight +10 +// xLabel->getString() +May 2015 +// static_cast(aLabelFontColor) +0 +// fLabelFontHeight +10 +// xLabel->getString() +Jun 2015 +// static_cast(aLabelFontColor) +0 +// fLabelFontHeight +10 +// xLabel->getString() +Jul 2015 +// static_cast(aLabelFontColor) +0 +// fLabelFontHeight +10 +// xLabel->getString() +Aug 2015 +// static_cast(aLabelFontColor) +0 +// fLabelFontHeight +10 +// xLabel->getString() +Sep 2015 +// static_cast(aLabelFontColor) +0 +// fLabelFontHeight +10 +// xLabel->getString() +Oct 2015 +// static_cast(aLabelFontColor) +0 +// fLabelFontHeight +10 +// xLabel->getString() +Nov 2015 +// static_cast(aLabelFontColor) +0 +// fLabelFontHeight +10 +// xLabel->getString() +Dec 2015 +// static_cast(aLabelFontColor) +0 +// fLabelFontHeight +10 +/// CID/D=0:CS=0:Axis=1,0 +// nAxisLabelsCount +7 +// xLabel->getString() +0.00 +// static_cast(aLabelFontColor) +0 +// fLabelFontHeight +10 +// xLabel->getString() +2.00 +// static_cast(aLabelFontColor) +0 +// fLabelFontHeight +10 +// xLabel->getString() +4.00 +// static_cast(aLabelFontColor) +0 +// fLabelFontHeight +10 +//
[Libreoffice-commits] core.git: Branch 'distro/collabora/cp-6.0' - chart2/qa oox/source
chart2/qa/extras/chart2import.cxx | 23 +++
chart2/qa/extras/data/pptx/tdf122765.pptx |binary
oox/source/drawingml/chart/titleconverter.cxx |1 -
3 files changed, 23 insertions(+), 1 deletion(-)
New commits:
commit 771f2c368d85e7e46c6bd2a0f9d764954781416b
Author: Tamás Zolnai
AuthorDate: Tue May 21 12:50:31 2019 +0200
Commit: Andras Timar
CommitDate: Fri May 31 07:34:37 2019 +0200
tdf#122765: Legend interferes with pie chart after pptx import
Revert the commit caused this regression:
0fc41c53dfbd21e526fb0ad68a6651693c4a2ecd
The original issue does not come back with
reverting this commit.
Reviewed-on: https://gerrit.libreoffice.org/72679
Tested-by: Jenkins
Reviewed-by: Tamás Zolnai
(cherry picked from commit 10609749126ca76eaf12904d4cce9cc5a16d8405)
Change-Id: I666c4f92e3b70b416ec6da7a704298d207451649
Reviewed-on: https://gerrit.libreoffice.org/72767
Reviewed-by: Andras Timar
Tested-by: Andras Timar
diff --git a/chart2/qa/extras/chart2import.cxx
b/chart2/qa/extras/chart2import.cxx
index 428f3f801a53..1de330ec62dc 100644
--- a/chart2/qa/extras/chart2import.cxx
+++ b/chart2/qa/extras/chart2import.cxx
@@ -110,6 +110,7 @@ public:
void testTdf115107(); // import complex data point labels
void testTdf115107_2(); // import complex data point labels in cobo charts
with multiple data series
void testTdf121205();
+void testTdf122765();
CPPUNIT_TEST_SUITE(Chart2ImportTest);
CPPUNIT_TEST(Fdo60083);
@@ -174,6 +175,7 @@ public:
CPPUNIT_TEST(testTdf115107);
CPPUNIT_TEST(testTdf115107_2);
CPPUNIT_TEST(testTdf121205);
+CPPUNIT_TEST(testTdf122765);
CPPUNIT_TEST_SUITE_END();
@@ -1583,6 +1585,27 @@ void Chart2ImportTest::testTdf121205()
}
+void Chart2ImportTest::testTdf122765()
+{
+// The horizontal position of the slices was wrong.
+load("/chart2/qa/extras/data/pptx/", "tdf122765.pptx");
+Reference xChartDoc(getChartDocFromDrawImpress(0,
0), UNO_QUERY);
+Reference xDrawPageSupplier(xChartDoc,
UNO_QUERY_THROW);
+Reference xDrawPage(xDrawPageSupplier->getDrawPage(),
UNO_SET_THROW);
+Reference xShapes(xDrawPage->getByIndex(0),
UNO_QUERY_THROW);
+Reference xSeriesSlices(getShapeByName(xShapes,
"CID/D=0:CS=0:CT=0:Series=0"),
+ UNO_SET_THROW);
+
+Reference xIndexAccess(xSeriesSlices,
UNO_QUERY_THROW);
+CPPUNIT_ASSERT_EQUAL(sal_Int32(9), xIndexAccess->getCount());
+Reference xSlice(xIndexAccess->getByIndex(0),
UNO_QUERY_THROW);
+
+// Check position of the first slice, all slices move together, so enough
to check only one.
+// Wrong poisition was around 5856.
+awt::Point aSlicePosition = xSlice->getPosition();
+CPPUNIT_ASSERT_GREATER(sal_Int32(7000), aSlicePosition.X);
+}
+
CPPUNIT_TEST_SUITE_REGISTRATION(Chart2ImportTest);
CPPUNIT_PLUGIN_IMPLEMENT();
diff --git a/chart2/qa/extras/data/pptx/tdf122765.pptx
b/chart2/qa/extras/data/pptx/tdf122765.pptx
new file mode 100644
index ..948190c30b55
Binary files /dev/null and b/chart2/qa/extras/data/pptx/tdf122765.pptx differ
diff --git a/oox/source/drawingml/chart/titleconverter.cxx
b/oox/source/drawingml/chart/titleconverter.cxx
index a4bb1ec70944..8109ca8a3235 100644
--- a/oox/source/drawingml/chart/titleconverter.cxx
+++ b/oox/source/drawingml/chart/titleconverter.cxx
@@ -238,7 +238,6 @@ void LegendConverter::convertFromModel( const Reference<
XDiagram >& rxDiagram )
// manual size needs ChartLegendExpansion_CUSTOM and
LegendPosition_CUSTOM (tdf#118150)
if( aLayoutConv.convertFromModel( aPropSet ) )
{
-eLegendPos = cssc2::LegendPosition_CUSTOM;
eLegendExpand = cssc::ChartLegendExpansion_CUSTOM;
}
bManualLayout = !aLayoutConv.getAutoLayout();
___
Libreoffice-commits mailing list
libreoffice-comm...@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice-commits
[Libreoffice-commits] core.git: Branch 'libreoffice-6-2' - chart2/source
chart2/source/view/main/ChartView.cxx |4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
New commits:
commit 42d27ed5c07f829dab1d5b663fc14cf1b61061b4
Author: Tamás Zolnai
AuthorDate: Tue May 28 17:32:44 2019 +0200
Commit: Andras Timar
CommitDate: Fri May 31 07:33:15 2019 +0200
tdf#122765: Legend interferes with pie chart after pptx import, second part
Revert of:
2903c5f59d257b6ab94f32df64513f2edf94fb0b
Reverting this commit does not lead to the original bug
to come back, so we can revert it without a problem.
Change-Id: I244a6b9451c47e1094db8a77c71b6696e0c464cc
Reviewed-on: https://gerrit.libreoffice.org/73139
Reviewed-by: Tamás Zolnai
Tested-by: Tamás Zolnai
(cherry picked from commit 63d17d01da0f9e3a7554e4327244ee4457b7188d)
Reviewed-on: https://gerrit.libreoffice.org/73159
Tested-by: Jenkins
Reviewed-by: Andras Timar
diff --git a/chart2/source/view/main/ChartView.cxx
b/chart2/source/view/main/ChartView.cxx
index 02ad8a90720c..37f4811c658f 100644
--- a/chart2/source/view/main/ChartView.cxx
+++ b/chart2/source/view/main/ChartView.cxx
@@ -1499,7 +1499,6 @@ awt::Rectangle ChartView::impl_createDiagramAndContent(
const CreateShapeParam2D
uno::Reference< drawing::XShapes > xSeriesTargetInFrontOfAxis;
uno::Reference< drawing::XShapes > xSeriesTargetBehindAxis;
VDiagram aVDiagram(xDiagram, aPreferredAspectRatio, nDimensionCount);
-bool bIsPieOrDonut = lcl_IsPieOrDonut(xDiagram);
{//create diagram
aVDiagram.init(rParam.mxDiagramWithAxesShapes, m_xShapeFactory);
aVDiagram.createShapes(
@@ -1508,7 +1507,7 @@ awt::Rectangle ChartView::impl_createDiagramAndContent(
const CreateShapeParam2D
xSeriesTargetInFrontOfAxis = aVDiagram.getCoordinateRegion();
// It is preferable to use full size than minimum for pie charts
-if (!bIsPieOrDonut && !rParam.mbUseFixedInnerSize)
+if (!rParam.mbUseFixedInnerSize)
aVDiagram.reduceToMimimumSize();
}
@@ -1536,6 +1535,7 @@ awt::Rectangle ChartView::impl_createDiagramAndContent(
const CreateShapeParam2D
//use first coosys only so far; todo: calculate for more than one coosys
if we have more in future
//todo: this is just a workaround at the moment for pie and donut labels
+bool bIsPieOrDonut = lcl_IsPieOrDonut(xDiagram);
if( !bIsPieOrDonut && (!rVCooSysList.empty()) )
{
VCoordinateSystem* pVCooSys = rVCooSysList[0].get();
___
Libreoffice-commits mailing list
libreoffice-comm...@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice-commits
[Libreoffice-commits] core.git: Branch 'libreoffice-6-2' - chart2/qa oox/source
chart2/qa/extras/chart2dump/chart2dump.cxx|1 chart2/qa/extras/chart2dump/data/tdf118150.xlsx |binary chart2/qa/extras/chart2dump/reference/axislabeltest/tdf118150.txt | 216 ++ chart2/qa/extras/chart2import.cxx | 23 + chart2/qa/extras/data/pptx/tdf122765.pptx |binary oox/source/drawingml/chart/titleconverter.cxx |3 6 files changed, 241 insertions(+), 2 deletions(-) New commits: commit 7ea8112e33761f947635c0ce8b93f583c88c1e8e Author: Tamás Zolnai AuthorDate: Tue May 21 12:05:33 2019 +0200 Commit: Andras Timar CommitDate: Fri May 31 07:32:24 2019 +0200 tdf#122765: Legend interferes with pie chart after pptx import Revert the commit caused this regression: 0fc41c53dfbd21e526fb0ad68a6651693c4a2ecd The original issue does not come back with reverting this commit. Reviewed-on: https://gerrit.libreoffice.org/72679 Tested-by: Jenkins Reviewed-by: Tamás Zolnai (cherry picked from commit 10609749126ca76eaf12904d4cce9cc5a16d8405) Add unit test for tdf#118150. Reviewed-on: https://gerrit.libreoffice.org/72678 Tested-by: Jenkins Reviewed-by: Tamás Zolnai (cherry picked from commit a703b4d8842261f55f489c28352df1f53a9b070a) Fix outdated comment. Reviewed-on: https://gerrit.libreoffice.org/72697 Reviewed-by: Tamás Zolnai Tested-by: Tamás Zolnai (cherry picked from commit c43534d5e8d33f73ee4ba70867065be675302579) Change-Id: I666c4f92e3b70b416ec6da7a704298d207451649 cea2c8aacb36e843dad67a056d07d6495fbbb17a 1be6e4cf52ccd385d59f85d9d5fa5b8a47caf4f1 Reviewed-on: https://gerrit.libreoffice.org/72761 Reviewed-by: Xisco Faulí Tested-by: Xisco Faulí Tested-by: Jenkins Reviewed-by: Andras Timar diff --git a/chart2/qa/extras/chart2dump/chart2dump.cxx b/chart2/qa/extras/chart2dump/chart2dump.cxx index e06ce2f76415..39495fa621e3 100644 --- a/chart2/qa/extras/chart2dump/chart2dump.cxx +++ b/chart2/qa/extras/chart2dump/chart2dump.cxx @@ -638,6 +638,7 @@ DECLARE_DUMP_TEST(AxisLabelTest, Chart2DumpTest, false) "rotated_axis_labels.odp", "formated_axis_labels.odp", "percent_stacked_column_chart.odp", +"tdf118150.xlsx", }; for (const OUString& sTestFile : aTestFiles) diff --git a/chart2/qa/extras/chart2dump/data/tdf118150.xlsx b/chart2/qa/extras/chart2dump/data/tdf118150.xlsx new file mode 100644 index ..f29b9a1c2e66 Binary files /dev/null and b/chart2/qa/extras/chart2dump/data/tdf118150.xlsx differ diff --git a/chart2/qa/extras/chart2dump/reference/axislabeltest/tdf118150.txt b/chart2/qa/extras/chart2dump/reference/axislabeltest/tdf118150.txt new file mode 100644 index ..fabf4acac67b --- /dev/null +++ b/chart2/qa/extras/chart2dump/reference/axislabeltest/tdf118150.txt @@ -0,0 +1,216 @@ +/// CID/D=0:CS=0:Axis=0,0 +// nAxisLabelsCount +28 +// xLabel->getString() +Sep 2013 +// static_cast(aLabelFontColor) +0 +// fLabelFontHeight +10 +// xLabel->getString() +Oct 2013 +// static_cast(aLabelFontColor) +0 +// fLabelFontHeight +10 +// xLabel->getString() +Nov 2013 +// static_cast(aLabelFontColor) +0 +// fLabelFontHeight +10 +// xLabel->getString() +Dec 2013 +// static_cast(aLabelFontColor) +0 +// fLabelFontHeight +10 +// xLabel->getString() +Jan 2014 +// static_cast(aLabelFontColor) +0 +// fLabelFontHeight +10 +// xLabel->getString() +Feb 2014 +// static_cast(aLabelFontColor) +0 +// fLabelFontHeight +10 +// xLabel->getString() +Mar 2014 +// static_cast(aLabelFontColor) +0 +// fLabelFontHeight +10 +// xLabel->getString() +Apr 2014 +// static_cast(aLabelFontColor) +0 +// fLabelFontHeight +10 +// xLabel->getString() +May 2014 +// static_cast(aLabelFontColor) +0 +// fLabelFontHeight +10 +// xLabel->getString() +Jun 2014 +// static_cast(aLabelFontColor) +0 +// fLabelFontHeight +10 +// xLabel->getString() +Jul 2014 +// static_cast(aLabelFontColor) +0 +// fLabelFontHeight +10 +// xLabel->getString() +Aug 2014 +// static_cast(aLabelFontColor) +0 +// fLabelFontHeight +10 +// xLabel->getString() +Sep 2014 +// static_cast(aLabelFontColor) +0 +// fLabelFontHeight +10 +// xLabel->getString() +Oct 2014 +// static_cast(aLabelFontColor) +0 +// fLabelFontHeight +10 +// xLabel->getString() +Nov 2014 +// static_cast(aLabelFontColor) +0 +// fLabelFontHeight +10 +// xLabel->getString() +Dec 2014 +// static_cast(aLabelFontColor) +0 +// fLabelFontHeight +10 +// xLabel->getString() +Jan 2015 +// static_cast(aLabelFontColor) +0 +// fLabelFontHeight +10 +// xLabel->getString() +Feb 2015 +// static_cast(aLabelFontColor) +0 +// fLabelFontHeight +10 +// xLabel->getString() +Mar 2015 +// static_cast(aLabelFontColor) +0 +// fLabelFontHeight +10 +// xLabel->getString() +Apr 2015 +// static_cast(aLabelFontColor) +0 +// fLabelFontHeight +10 +// xLabel->getString() +May 2015 +//
[Libreoffice-bugs] [Bug 117888] UI: List Box mouse wheel scroll behavior cannot be changed
https://bugs.documentfoundation.org/show_bug.cgi?id=117888 --- Comment #3 from Robert Großkopf --- Nothing changed here. Bug still exists in LO 6.2.4.2 on OpenSUSE 15 64bit rpm Linux. -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 125062] Export as PNG with transparency changes shape of objects radically
https://bugs.documentfoundation.org/show_bug.cgi?id=125062 --- Comment #5 from James Gimbel --- Thanks for reminding me. I'm starting to work on it. Get fix all email bugs at email help desk. fix AOL email bugs at https://www.emailhelpdesk.us/support-for-aol.html fix Gmail bugs at https://www.emailhelpdesk.us/support-for-gmail.html fix HughesNet email bugs at https://www.emailhelpdesk.us/support-for-hughesnet.html fix Roadrunner email bugs at https://www.emailhelpdesk.us/support-for-Roadrunner.html -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 113984] Content of a sub-table in another table is hidden by page footer when breaking across pages
https://bugs.documentfoundation.org/show_bug.cgi?id=113984 --- Comment #10 from Kieran Grant --- Version: 6.2.4.2 Build ID: 2412653d852ce75f65fbfa83fb7e7b669a126d64 CPU threads: 16; OS: Linux 4.15; UI render: default; VCL: gtk3; Locale: en-AU (en_AU.UTF-8); UI-Language: en-US Calc: threaded -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 32281] Export a log of emails not sent in 'Sending e-mail messages' dialog
https://bugs.documentfoundation.org/show_bug.cgi?id=32281 --- Comment #8 from James Gimbel --- This issue is an enhancement and still valid to LibreOffice 3.5.0 Beta2. https://www.emailhelpdesk.us/support-for-hotmail.html https://www.emailhelpdesk.us/support-for-msn.html https://www.emailhelpdesk.us/support-for-Livemail.html https://www.emailhelpdesk.us/support-for-Outlook.html -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 32281] Export a log of emails not sent in 'Sending e-mail messages' dialog
https://bugs.documentfoundation.org/show_bug.cgi?id=32281 James Gimbel changed: What|Removed |Added URL||https://www.emailhelpdesk.u ||s/support-for-Outlook.html -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[no subject]
You frauding me ___ LibreOffice mailing list LibreOffice@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice
[Libreoffice-bugs] [Bug 125601] Legacy background extension does not work again
https://bugs.documentfoundation.org/show_bug.cgi?id=125601 Volga changed: What|Removed |Added See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=12 ||0718 -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 125601] New: Legacy background extension does not work again
https://bugs.documentfoundation.org/show_bug.cgi?id=125601 Bug ID: 125601 Summary: Legacy background extension does not work again Product: LibreOffice Version: 6.2.4.2 release Hardware: All OS: All Status: UNCONFIRMED Severity: normal Priority: medium Component: Extensions Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: shanshandehongx...@outlook.com Description: In LibreOffice 6.2.4.2, the Legacy background extension failed to insert any images, showing “Read error” instead, no matter drag-and-drop, copy-and-paste. Steps to Reproduce: 1. Download & install Legacy Backgrounds extension v1.1 2. Open LibreOffice Writer, click click “Gallery” in the side bar 3. Insert an image from Legacy Backgrounds Actual Results: It could not insert the background image into the main part Expected Results: It should work Reproducible: Always User Profile Reset: No Additional Info: 版本: 6.2.4.2 (x64) Build ID: 2412653d852ce75f65fbfa83fb7e7b669a126d64 CPU 线程: 4; 操作系统: Windows 10.0; UI 渲染: 默认; VCL: win; 区域语言: zh-CN (zh_CN); UI 语言: zh-CN Calc: threaded -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 125597] LibreOffice-Writer-Properties-General- the Modified field remains blank after saving blank file
https://bugs.documentfoundation.org/show_bug.cgi?id=125597 raal changed: What|Removed |Added OS|Windows (All) |All CC||r...@post.cz --- Comment #1 from raal --- Confirm with Version: 6.3.0.0.alpha1+ Build ID: 53325b40b557cc84d8d21c1baa0ef8d3bfc00ab8 CPU threads: 4; OS: Linux 4.15; UI render: default; VCL: gtk3; doesn't confirm > -Workaround: if you "Save" the file again, the "Modified" field do change. not sure if it's a bug, leaving unconfirmed. -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 121944] New install of Ubuntu 18.10. LO Writer Found format\character\font arial style in Greek, Czech, Slovak for Normal, Bold, Italics, and Bold Italics.
https://bugs.documentfoundation.org/show_bug.cgi?id=121944 raal changed: What|Removed |Added Status|UNCONFIRMED |NEW Ever confirmed|0 |1 Version|6.1.2.1 release |4.1.0.4 release CC||r...@post.cz --- Comment #5 from raal --- Confirm with Version: 6.0.7.3 Build ID: 1:6.0.7-0ubuntu0.18.04.6 CPU threads: 4; OS: Linux 4.15; UI render: default; VCL: gtk3; Locale: cs-CZ (cs_CZ.UTF-8); Calc: group and Version: 6.3.0.0.alpha1+ Build ID: 53325b40b557cc84d8d21c1baa0ef8d3bfc00ab8 CPU threads: 4; OS: Linux 4.15; UI render: default; VCL: gtk3; Locale: cs-CZ (cs_CZ.UTF-8); UI-Language: en-US and Version 4.1.0.0.alpha0+ (Build ID: efca6f15609322f62a35619619a6d5fe5c9bd5a) Ubuntu 18.04 -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 125584] Foreign language displays in English font selection for Arial font
https://bugs.documentfoundation.org/show_bug.cgi?id=125584 raal changed: What|Removed |Added Status|NEW |RESOLVED Resolution|--- |DUPLICATE --- Comment #5 from raal --- *** This bug has been marked as a duplicate of bug 121944 *** -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 121944] New install of Ubuntu 18.10. LO Writer Found format\character\font arial style in Greek, Czech, Slovak for Normal, Bold, Italics, and Bold Italics.
https://bugs.documentfoundation.org/show_bug.cgi?id=121944 raal changed: What|Removed |Added CC||j...@cjsa.com --- Comment #4 from raal --- *** Bug 125584 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 125584] Foreign language displays in English font selection for Arial font
https://bugs.documentfoundation.org/show_bug.cgi?id=125584 raal changed: What|Removed |Added Ever confirmed|0 |1 CC||r...@post.cz Summary|Foreign language displays |Foreign language displays |in English font selection |in English font selection ||for Arial font Version|6.1.6.3 release |4.1.0.4 release Status|UNCONFIRMED |NEW --- Comment #4 from raal --- Confirm with Version: 6.0.7.3 Build ID: 1:6.0.7-0ubuntu0.18.04.6 CPU threads: 4; OS: Linux 4.15; UI render: default; VCL: gtk3; Locale: cs-CZ (cs_CZ.UTF-8); Calc: group and Version: 6.3.0.0.alpha1+ Build ID: 53325b40b557cc84d8d21c1baa0ef8d3bfc00ab8 CPU threads: 4; OS: Linux 4.15; UI render: default; VCL: gtk3; Locale: cs-CZ (cs_CZ.UTF-8); UI-Language: en-US and Version 4.1.0.0.alpha0+ (Build ID: efca6f15609322f62a35619619a6d5fe5c9bd5a) Ubuntu 18.04 -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 114334] Yi characters clipped in vertical layout (Nuosu SIL)
https://bugs.documentfoundation.org/show_bug.cgi?id=114334 Volga 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 mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 114334] Yi characters clipped in vertical layout (Nuosu SIL)
https://bugs.documentfoundation.org/show_bug.cgi?id=114334 --- Comment #10 from Volga --- Created attachment 151793 --> https://bugs.documentfoundation.org/attachment.cgi?id=151793=edit Snapshot on LODev 6.3.0.0.alpha1+ Yes, the problem is still there. Version: 6.3.0.0.alpha1+ (x64) Build ID: 3a0ca1bff25d6c2bbc5bf8684eefd67956c2db95 CPU threads: 4; OS: Windows 10.0; UI render: default; VCL: win; TinderBox: Win-x86_64@42, Branch:master, Time: 2019-05-31_01:26:46 Locale: zh-CN (zh_CN); UI-Language: en-US Calc: threaded -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 125598] calc scrollbars don't save correctly in ms formats
https://bugs.documentfoundation.org/show_bug.cgi?id=125598 raal changed: What|Removed |Added Status|UNCONFIRMED |NEEDINFO Ever confirmed|0 |1 CC||r...@post.cz --- Comment #2 from raal --- Hello, Thank you for filing the bug. Please send us a sample document, as this makes it easier for us to verify the bug. I have set the bug's status to 'NEEDINFO', so please do change it back to 'UNCONFIRMED' once you have attached a document. (Please note that the attachment will be public, remove any sensitive information before attaching it.) How can I eliminate confidential data from a sample document? https://wiki.documentfoundation.org/QA/FAQ#How_can_I_eliminate_confidential_data_from_a_sample_document.3F Thank you -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 125594] Bounding box not rotated when image "as character" anchor mode
https://bugs.documentfoundation.org/show_bug.cgi?id=125594 raal changed: What|Removed |Added Summary|Bounding box not rotated|Bounding box not rotated |when image is |when image "as character" ||anchor mode CC||armin.le.gr...@me.com, ||r...@post.cz Status|UNCONFIRMED |NEW Ever confirmed|0 |1 --- Comment #1 from raal --- Confirm with Version: 6.3.0.0.alpha1+ Build ID: 53325b40b557cc84d8d21c1baa0ef8d3bfc00ab8 CPU threads: 4; OS: Linux 4.15; UI render: default; VCL: gtk3; Feature added in https://wiki.documentfoundation.org/ReleaseNotes/6.0#Images_rotation , add Armin to cc -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 125588] EDITING: Wrong formula computed values and crash with formulas pasted on whole columns
https://bugs.documentfoundation.org/show_bug.cgi?id=125588 raal changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |WORKSFORME CC||r...@post.cz --- Comment #9 from raal --- Thank you for testing. According to https://wiki.documentfoundation.org/ReleasePlan/6.1 , the 6.1.6 is last version, so we can close the bug - it's fixed in 6.2 -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 125286] FIREBIRD - Base not usable under Windows account with Chinese user name (UTF character support)
https://bugs.documentfoundation.org/show_bug.cgi?id=125286 QA Administrators changed: What|Removed |Added Whiteboard|| QA:needsComment -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 125320] combination of autocalculate and shared formulae still broken in 6.3.0.0.alpha1+ with threaded off
https://bugs.documentfoundation.org/show_bug.cgi?id=125320 QA Administrators changed: What|Removed |Added Whiteboard|| QA:needsComment -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 121806] Sheet tabs appear too small Ubuntu 18
https://bugs.documentfoundation.org/show_bug.cgi?id=121806 --- Comment #7 from QA Administrators --- Dear Andrew Hughes, 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 mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 125580] Wrong value when adding two dates
https://bugs.documentfoundation.org/show_bug.cgi?id=125580 QA Administrators changed: What|Removed |Added Keywords||bibisectRequest -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 125588] EDITING: Wrong formula computed values and crash with formulas pasted on whole columns
https://bugs.documentfoundation.org/show_bug.cgi?id=125588 --- Comment #8 from QA Administrators --- [Automated Action] NeedInfo-To-Unconfirmed -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 56126] EDITING: Conditional field and vertical separator
https://bugs.documentfoundation.org/show_bug.cgi?id=56126 --- Comment #10 from QA Administrators --- Dear Paul Monnerat, 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 http://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://kiwiirc.com/nextclient/irc.freenode.net/#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 mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 125588] EDITING: Wrong formula computed values and crash with formulas pasted on whole columns
https://bugs.documentfoundation.org/show_bug.cgi?id=125588 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 mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 94735] Transparent gradient of kind draw:style="square" is rendered wrong in presentation mode
https://bugs.documentfoundation.org/show_bug.cgi?id=94735 --- Comment #4 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 http://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://kiwiirc.com/nextclient/irc.freenode.net/#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 mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 57663] [EDITING] Base Point always returns to top left (and it's anoying)
https://bugs.documentfoundation.org/show_bug.cgi?id=57663 --- Comment #5 from QA Administrators --- Dear Edson Brusque, 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 http://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://kiwiirc.com/nextclient/irc.freenode.net/#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 mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 55705] EDITING: Unable to draw lines after Row and Column width modified version Version 3.6.2.2 (Build ID: da8c1e6)
https://bugs.documentfoundation.org/show_bug.cgi?id=55705 --- Comment #12 from QA Administrators --- Dear mr.david.mitchell, 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 http://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://kiwiirc.com/nextclient/irc.freenode.net/#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 mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 105438] Gradient fill is wrong in slide show, but correct in edit mode, for shape "quad-bevel"
https://bugs.documentfoundation.org/show_bug.cgi?id=105438 --- Comment #4 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 http://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://kiwiirc.com/nextclient/irc.freenode.net/#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 mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 56612] EDITING - Base problem with boolean field that defaults to unintended value
https://bugs.documentfoundation.org/show_bug.cgi?id=56612 --- Comment #11 from QA Administrators --- Dear Emanuele Gissi, 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 http://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://kiwiirc.com/nextclient/irc.freenode.net/#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 mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 90036] FORMATTING: Cannot reset numbering in bullets/numbers
https://bugs.documentfoundation.org/show_bug.cgi?id=90036 --- Comment #12 from QA Administrators --- Dear cytan299, 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 http://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://kiwiirc.com/nextclient/irc.freenode.net/#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 mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 111857] FILESAVE: errors when saving to PPTX - TABs lost
https://bugs.documentfoundation.org/show_bug.cgi?id=111857 --- Comment #6 from QA Administrators --- Dear Elmar, 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 http://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://kiwiirc.com/nextclient/irc.freenode.net/#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 mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 104945] Problems copying paragraphs, like the questions of an examination
https://bugs.documentfoundation.org/show_bug.cgi?id=104945 --- Comment #16 from QA Administrators --- Dear Ganton, 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 http://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://kiwiirc.com/nextclient/irc.freenode.net/#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 mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 113228] Gallery category/folder names not localized
https://bugs.documentfoundation.org/show_bug.cgi?id=113228 --- Comment #5 from QA Administrators --- Dear tagezi, 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 http://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://kiwiirc.com/nextclient/irc.freenode.net/#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 mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 103909] macOS: Start Center doesn't open on top - doesn't receive focus
https://bugs.documentfoundation.org/show_bug.cgi?id=103909 --- Comment #10 from QA Administrators --- Dear Telesto, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from http://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://kiwiirc.com/nextclient/irc.freenode.net/#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 mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 113984] Content of a sub-table in another table is hidden by page footer when breaking across pages
https://bugs.documentfoundation.org/show_bug.cgi?id=113984 --- Comment #9 from QA Administrators --- Dear Kieran Grant, 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 http://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://kiwiirc.com/nextclient/irc.freenode.net/#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 mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 117764] using context menu item "Conditional formatting" opens dialogue "Conditional formatting for ..." with wrong cell range
https://bugs.documentfoundation.org/show_bug.cgi?id=117764 --- Comment #6 from QA Administrators --- Dear kompilainenn, 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 http://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://kiwiirc.com/nextclient/irc.freenode.net/#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 mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 103916] UI An added / modified gradient (dialog Page Background) is not available in other documents
https://bugs.documentfoundation.org/show_bug.cgi?id=103916 --- Comment #5 from QA Administrators --- Dear Cor Nouws, 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 http://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://kiwiirc.com/nextclient/irc.freenode.net/#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 mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 117769] Graphic Corruption on slideshow with Gradient and Animations
https://bugs.documentfoundation.org/show_bug.cgi?id=117769 --- Comment #5 from QA Administrators --- Dear Luke, 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 http://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://kiwiirc.com/nextclient/irc.freenode.net/#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 mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 117888] UI: List Box mouse wheel scroll behavior cannot be changed
https://bugs.documentfoundation.org/show_bug.cgi?id=117888 --- Comment #2 from QA Administrators --- Dear Balint Fodor, 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 http://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://kiwiirc.com/nextclient/irc.freenode.net/#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 mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 117665] Sidebar becomes nonfunctional after removing all category buttons and closing it when undocked.
https://bugs.documentfoundation.org/show_bug.cgi?id=117665 --- Comment #5 from QA Administrators --- Dear Herman Tafintsev, 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 http://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://kiwiirc.com/nextclient/irc.freenode.net/#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 mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 125600] New: Calc spellcheck does not recognize correct spelling
https://bugs.documentfoundation.org/show_bug.cgi?id=125600 Bug ID: 125600 Summary: Calc spellcheck does not recognize correct spelling Product: LibreOffice Version: 6.2.3.2 release Hardware: All OS: Windows (All) Status: UNCONFIRMED Severity: normal Priority: medium Component: Calc Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: tdfpu...@gmail.com Description: OS: Win 10 Home OS Build: 17134.765 LibreOffice: Version: 6.2.3.2 (x64) Build ID: aecc05fe267cc68dde00352a451aa867b3b546ac I am producing an energy use calculator in LibreOffice Calc. The sheet makes frequent use of standard acronyms such as KWh (kilowatt-hour). Every time this acronym is used, Calc changes it to Kwh. (Both KWh and Kwh get a red underline indicating a misspelling.) I tried to manually fix this several times by entering the correct format directly in the input line. But Calc kept reverting. Until I inadvertently typed Ctrl+Z. When I noticed this, I hit Enter and the text stayed as I had typed it. However, KWh still had it's red line. I then ran spell check and found that while it is identifying KWh as a misspelled word, it also suggesting KWh as the correct spelling. I clicked Correct All and the same problem remained. I tried this three times without success. I then tried adding KWh to the dictionary. The first two times this did not work. On the third attempt it... sort of worked. KWh still has the red line indicating a misspelled word. However, running spell check no longer finds any problems. Next, I saved the sheet in ODF and reopened it. Now all the identified misspellings are gone. Steps to Reproduce: 1. Type "KWh". Red line appears under "KWh" 2. Ran spell check. Acronym still identified as misspelling. 3. Clicked suggested correction "KWh". 4. Clicked "Correct All" 5. Closed Spell Check. 6. Reopened Spell Check and added KWh to the dictionary. 7. Saved document as a new doc and in the ODF fie format. (Original was based on .csv) 8. Reopened the new doc and the red lines were gone. 9. Reran spell check. No identified misspellings. Actual Results: Spell check could not identify correct spelling of KWh even though it was included in Spell Check's own suggestion box. Only saving the sheet as a new doc resolved the problem. Expected Results: Spell Check should correctly identify misspelling and auto correct only when there is a correct spelling entry in it's database. In addition, auto correct should not be persistent. When I tell Spell Check to undo it's correction, it should do as it's told. Reproducible: Always User Profile Reset: No Additional Info: Version: 6.2.3.2 (x64) Build ID: aecc05fe267cc68dde00352a451aa867b3b546ac CPU threads: 8; OS: Windows 10.0; UI render: default; VCL: win; Locale: en-US (en_US); UI-Language: en-US Calc: CL While filling out this bug report, I have opened and closed LibreOffice and the relevant docs several times. Now I can no longer reproduce the error. I am not sure if it is worth submitting this report or not. -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
Re: Using Amazon Corretto as Oracle JDK replacement for building LibreOffice on Windows
Hi, On Thu, May 30, 2019 at 9:46 PM Kaganski Mike wrote: > Hi, > So this is just to let you know in case you need an alternative JRE. > > Another alternative is Red Hat OpenJDK [1] (which is probably more or less identical to Amazon Corretto). I didn't try it however, but probably will the next time I boot to Windows and need to build LO. [1] https://developers.redhat.com/products/openjdk/download/ Regard, Tomaž ___ LibreOffice mailing list LibreOffice@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice
Re: Using Amazon Corretto as Oracle JDK replacement for building LibreOffice on Windows
Hi, On 30/05/2019 14.46, Kaganski Mike wrote: > Since Oracle JDK versions prior to 12 are now unavailable from the > official site [1] for unregistered users (and version 12 is said to > still have problems/needs workarounds [2]), I decided to give Amazon > Corretto [3] a try. As a side note, AdoptOpenJDK [1] also worked fine for a master build when I tried recently (that was on a 64bit Windows). [1] https://adoptopenjdk.net/ signature.asc Description: OpenPGP digital signature ___ LibreOffice mailing list LibreOffice@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice
[Libreoffice-bugs] [Bug 125599] New: Installing most recent version ended up removing the program and reported an error that installation couldn't complete this is under Windows 7 professional 64k
https://bugs.documentfoundation.org/show_bug.cgi?id=125599 Bug ID: 125599 Summary: Installing most recent version ended up removing the program and reported an error that installation couldn't complete this is under Windows 7 professional 64k Product: LibreOffice Version: 6.2.2.2 release Hardware: x86-64 (AMD64) OS: Windows (All) Status: UNCONFIRMED Severity: normal Priority: medium Component: LibreOffice Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: alasta...@electricscotland.com Description: Using LibreOffice v 6.2.1 it works fine. However I did an update on that version which I guess is v 6.2.3 it ended up uninstalling the program but then couldn't install the new version. I didn't actually notice that had happened and was trying to load the program today and couldn't find it on my computer. I then went to download the latest version which is v 6.2.4 but noticed it couldn't complete the install. I thus went back to v 6.1.2. which installed fine. I am running under Windows 7 Professional 64 bit. So just thought I'd let you know. Actual Results: Just installing the program first by doing an update then trying a brand new install. Expected Results: It couldn't install the program and left me a message saying that. Reproducible: Didn't try User Profile Reset: No Additional Info: It should have installed the software -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 125506] Helplines and snap guides no longer visible on macOS (antialising)
https://bugs.documentfoundation.org/show_bug.cgi?id=125506 --- Comment #8 from Thorsten Wagner --- Now there is a strange effect concerning selected icons of toolbars (see screenshot). -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 125506] Helplines and snap guides no longer visible on macOS (antialising)
https://bugs.documentfoundation.org/show_bug.cgi?id=125506 --- Comment #7 from Thorsten Wagner --- Created attachment 151792 --> https://bugs.documentfoundation.org/attachment.cgi?id=151792=edit Screenshot of Impress toolbar -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 125506] Helplines and snap guides no longer visible on macOS (antialising)
https://bugs.documentfoundation.org/show_bug.cgi?id=125506 --- Comment #6 from Thorsten Wagner --- Helplines as well as snap guides are back using the patch. -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 125506] Helplines and snap guides no longer visible on macOS (antialising)
https://bugs.documentfoundation.org/show_bug.cgi?id=125506 Thorsten Wagner changed: What|Removed |Added Summary|Helplines and Snap Guides |Helplines and snap guides |no longer visible on macOS |no longer visible on macOS |(antialising) |(antialising) -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 78916] Custom page size missing from print dialog
https://bugs.documentfoundation.org/show_bug.cgi?id=78916 --- Comment #32 from Tylla --- @Heiko: you can never know what the "average printer" for the "average user" means. Maybe s/he is trying to print some custom labels (where 2"x2" can be perfectly valid), or maybe s/he has got some insane custom-sized paper which is only a few mm smaller than the well known A4 but which is really hard to position if it is printed as A4. And maybe the PDF printing workaround doesn't work either because it has to be printed as a brochure which the "Export as PDF..." function doesn't support. (yes, this is my current problem) @Cor: lots of printers allow defining custom page sizes on its configuration pages, some drivers even allow this from client side. The point is that it is OK to use a custom print dialog on such OS's where this adds or brings back some functionality, but if this hides some really useful functionality then it should be considered a bug. Even more if it is an OOo legacy. So please accept this as a bug, and try to give some priority to it. PS: I'm using LO v5.2.7.2 on Debian -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-ux-advise] [Bug 78916] Custom page size missing from print dialog
https://bugs.documentfoundation.org/show_bug.cgi?id=78916 --- Comment #32 from Tylla --- @Heiko: you can never know what the "average printer" for the "average user" means. Maybe s/he is trying to print some custom labels (where 2"x2" can be perfectly valid), or maybe s/he has got some insane custom-sized paper which is only a few mm smaller than the well known A4 but which is really hard to position if it is printed as A4. And maybe the PDF printing workaround doesn't work either because it has to be printed as a brochure which the "Export as PDF..." function doesn't support. (yes, this is my current problem) @Cor: lots of printers allow defining custom page sizes on its configuration pages, some drivers even allow this from client side. The point is that it is OK to use a custom print dialog on such OS's where this adds or brings back some functionality, but if this hides some really useful functionality then it should be considered a bug. Even more if it is an OOo legacy. So please accept this as a bug, and try to give some priority to it. PS: I'm using LO v5.2.7.2 on Debian -- You are receiving this mail because: You are on the CC list for the bug. ___ Libreoffice-ux-advise mailing list Libreoffice-ux-advise@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-ux-advise
[Libreoffice-commits] core.git: Branch 'libreoffice-6-2' - avmedia/source
avmedia/source/gstreamer/gstplayer.cxx | 26 +-
avmedia/source/gstreamer/gstplayer.hxx |2 ++
2 files changed, 27 insertions(+), 1 deletion(-)
New commits:
commit 474bef8e06ee514c4ff751b64ef395a54987bd7d
Author: Mark Hung
AuthorDate: Mon Feb 18 21:51:57 2019 +0800
Commit: Mark Hung
CommitDate: Fri May 31 01:16:22 2019 +0200
avmedia: set gstreamer gst_video_overlay size and position.
Have video fit to the media object size on the slide,
allow more complicated interactions.
---
This also backports the relevant part from commit
bbe1ede0fada499fd49b60bdc7964e311b331454
("tdf#124027: use ID of the embedded window and fix
position of overlay") namely to make translation
gtk3-specific, to fix a regression, as mentioned in
its commmit message:
> 2) the position of the embedded window for video overlay has already
> been translated relative to the top-left corner of the slide (see
> bugfix of tdf#42873 how) in gen, gtk and kde5 vclplugs. So let's limit
> translating it 2nd time only to gtk3 vclplug which for some reason
> behaves differently
> (regression from 18138417485aeba6c52d935c616dba829b24ffd8)
Reviewed-on: https://gerrit.libreoffice.org/67978
Tested-by: Jenkins
Reviewed-by: Caolán McNamara
Tested-by: Caolán McNamara
(cherry picked from commit 18138417485aeba6c52d935c616dba829b24ffd8)
Change-Id: Ice1fa4b521176ad7ed7f7d1d2b13e617e8282390
Reviewed-on: https://gerrit.libreoffice.org/73199
Tested-by: Jenkins
Reviewed-by: Mark Hung
diff --git a/avmedia/source/gstreamer/gstplayer.cxx
b/avmedia/source/gstreamer/gstplayer.cxx
index 37c638a6bd01..fb2193b3f67d 100644
--- a/avmedia/source/gstreamer/gstplayer.cxx
+++ b/avmedia/source/gstreamer/gstplayer.cxx
@@ -513,7 +513,13 @@ GstBusSyncReply Player::processSyncMessage( GstMessage
*message )
mpXOverlay = GST_VIDEO_OVERLAY( GST_MESSAGE_SRC( message ) );
g_object_ref( G_OBJECT ( mpXOverlay ) );
if ( mnWindowID != 0 )
+{
gst_video_overlay_set_window_handle( mpXOverlay, mnWindowID );
+
+if (maArea.Width > 0 && maArea.Height > 0)
+gst_video_overlay_set_render_rectangle(mpXOverlay,
maArea.X, maArea.Y, maArea.Width, maArea.Height);
+}
+
return GST_BUS_DROP;
}
#ifndef AVMEDIA_GST_0_10
@@ -928,7 +934,12 @@ uno::Reference< ::media::XPlayerWindow > SAL_CALL
Player::createPlayerWindow( co
::osl::MutexGuard aGuard(m_aMutex);
uno::Reference< ::media::XPlayerWindow >xRet;
-awt::Size aSize(
getPreferredPlayerWindowSize() );
+awt::Size aSize;
+
+if (rArguments.getLength() > 1 && (rArguments[1] >>= maArea))
+aSize = awt::Size(maArea.Width, maArea.Height);
+else
+aSize = getPreferredPlayerWindowSize();
if( mbFakeVideo )
preparePlaybin( maURL, nullptr );
@@ -953,6 +964,19 @@ uno::Reference< ::media::XPlayerWindow > SAL_CALL
Player::createPlayerWindow( co
OUString aToolkit =
OUString::createFromAscii(pEnvData->pToolkit);
OUString aPlatform =
OUString::createFromAscii(pEnvData->pPlatformName);
+// tdf#124027: the position of embedded window is identical w/
the position
+// of media object in all other vclplugs (gtk, kde5, gen), in
gtk3 w/o gtksink it
+// needs to be translated
+if (aToolkit == "gtk3")
+{
+if (pParentWindow)
+{
+Point aPoint = pParentWindow->GetPosPixel();
+maArea.X = aPoint.getX();
+maArea.Y = aPoint.getY();
+}
+}
+
GstElement *pVideosink = nullptr;
#if defined(ENABLE_GTKSINK)
pVideosink = (aToolkit == "gtk3") ?
diff --git a/avmedia/source/gstreamer/gstplayer.hxx
b/avmedia/source/gstreamer/gstplayer.hxx
index 6db9bc586575..c57f60a7802f 100644
--- a/avmedia/source/gstreamer/gstplayer.hxx
+++ b/avmedia/source/gstreamer/gstplayer.hxx
@@ -102,6 +102,8 @@ private:
int mnWidth;
int mnHeight;
+css::awt::Rectangle maArea; // Area of the player window.
+
guint mnWatchID;
boolmbWatchID;
___
Libreoffice-commits mailing list
libreoffice-comm...@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice-commits
[Libreoffice-bugs] [Bug 125512] Coordinates to close to next element within Impress' status bar
https://bugs.documentfoundation.org/show_bug.cgi?id=125512 Thorsten Wagner changed: What|Removed |Added Assignee|libreoffice-b...@lists.free |thorsten.wagne...@gmail.com |desktop.org | Status|NEW |ASSIGNED -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 125506] Helplines and Snap Guides no longer visible on macOS (antialising)
https://bugs.documentfoundation.org/show_bug.cgi?id=125506 --- Comment #5 from Xisco Faulí --- Patch in gerrit: https://gerrit.libreoffice.org/#/c/73226/ -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 125506] Helplines and Snap Guides no longer visible on macOS (antialising)
https://bugs.documentfoundation.org/show_bug.cgi?id=125506 Xisco Faulí changed: What|Removed |Added Summary|Helplines and Snap Guides |Helplines and Snap Guides |no longer visible on macOS |no longer visible on macOS ||(antialising) --- Comment #4 from Xisco Faulí --- Only happening with antialising -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 125531] Empty CMIS properties dialog
https://bugs.documentfoundation.org/show_bug.cgi?id=125531 Thorsten Wagner changed: What|Removed |Added Resolution|--- |WORKSFORME Status|NEW |RESOLVED --- Comment #5 from Thorsten Wagner --- Scroll bar artefact has been replaced by a right handed full size scroll bar. Setting status to resolved / works for me. -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 125513] White rendering artefacts between Writer pages on macOS
https://bugs.documentfoundation.org/show_bug.cgi?id=125513 --- Comment #5 from Thorsten Wagner --- Yes, in the case shown by screenshot there is one thin white line. Depending on scrolling there are situations with two or three of such lines too. -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-commits] core.git: Branch 'distro/lhm/libreoffice-5-2+backports' - sw/qa sw/source
sw/qa/extras/ooxmlexport/data/textinput.odt |binary
sw/qa/extras/ooxmlexport/ooxmlexport7.cxx | 11 +++
sw/source/filter/ww8/docxexport.cxx |7 +--
3 files changed, 16 insertions(+), 2 deletions(-)
New commits:
commit d179d77b6743ffb7d77bb3671b3e49ee19d76ba3
Author: Ilhan Yesil
AuthorDate: Thu May 23 17:52:04 2019 +0200
Commit: Thorsten Behrens
CommitDate: Fri May 31 00:41:14 2019 +0200
tdf#125103 Writer: input fields will be exported to docx
Changed the solution https://gerrit.libreoffice.org/#/c/70786/
of Vasily sligthly, so MS Office can recognize fields still
as fields.
ooxmlexport13 is not present in the 5.2 branch, so test case
is merged into ooxmlexport7.
Reviewed-on: https://gerrit.libreoffice.org/72868
Tested-by: Jenkins
Reviewed-by: Vasily Melenchuk
(cherry picked from commit 62d156ef0daccd2680161ef8b9b99d8a7bc0)
Change-Id: Id45330a96dfe002685c6ef3dc62e408c5f9f46c4
Reviewed-on: https://gerrit.libreoffice.org/73079
Reviewed-by: Thorsten Behrens
Tested-by: Thorsten Behrens
diff --git a/sw/qa/extras/ooxmlexport/data/textinput.odt
b/sw/qa/extras/ooxmlexport/data/textinput.odt
new file mode 100644
index ..04b8d054c354
Binary files /dev/null and b/sw/qa/extras/ooxmlexport/data/textinput.odt differ
diff --git a/sw/qa/extras/ooxmlexport/ooxmlexport7.cxx
b/sw/qa/extras/ooxmlexport/ooxmlexport7.cxx
index 4b3f0f1acf03..cfe5dd9c13fe 100644
--- a/sw/qa/extras/ooxmlexport/ooxmlexport7.cxx
+++ b/sw/qa/extras/ooxmlexport/ooxmlexport7.cxx
@@ -1910,6 +1910,17 @@ DECLARE_OOXMLEXPORT_TEST(testSignatureLineShape,
"signature-line-all-props-set.d
CPPUNIT_ASSERT_EQUAL(OUString("Check the machines!"),
aSigningInstructions);
}
+DECLARE_OOXMLEXPORT_TEST(testTextInput, "textinput.odt")
+{
+xmlDocPtr pXmlDoc = parseExport("word/document.xml");
+if (!pXmlDoc)
+return;
+// Ensure we have a formfield
+assertXPathContent(pXmlDoc, "/w:document/w:body/w:p/w:r[3]/w:instrText", "
FILLIN \"\"");
+// and it's content is not gone
+assertXPathContent(pXmlDoc, "/w:document/w:body/w:p/w:r[5]/w:t",
"SomeText");
+}
+
CPPUNIT_PLUGIN_IMPLEMENT();
/* vim:set shiftwidth=4 softtabstop=4 expandtab: */
diff --git a/sw/source/filter/ww8/docxexport.cxx
b/sw/source/filter/ww8/docxexport.cxx
index 2abbe899f130..063b76b2e90a 100644
--- a/sw/source/filter/ww8/docxexport.cxx
+++ b/sw/source/filter/ww8/docxexport.cxx
@@ -365,9 +365,12 @@ void DocxExport::DoComboBox(const OUString& rName,
m_pDocumentFS->endElementNS( XML_w, XML_ffData );
}
-void DocxExport::DoFormText(const SwInputField* /*pField*/)
+void DocxExport::DoFormText(const SwInputField* pField)
{
-OSL_TRACE( "TODO DocxExport::ForFormText()" );
+
+assert(pField);
+const OUString sStr = FieldString(ww::eFILLIN) + "\"" + pField->GetPar2()
+ "\"";
+OutputField(pField, ww::eFILLIN, sStr);
}
OString DocxExport::OutputChart( uno::Reference< frame::XModel >& xModel,
sal_Int32 nCount, ::sax_fastparser::FSHelperPtr m_pSerializer )
___
Libreoffice-commits mailing list
libreoffice-comm...@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice-commits
[Libreoffice-commits] online.git: Branch 'libreoffice-6-2' - wsd/ClientSession.cpp
wsd/ClientSession.cpp |6 --
1 file changed, 4 insertions(+), 2 deletions(-)
New commits:
commit 56dd06f2cf30de858e800a81f83437ae83f38070
Author: Michael Meeks
AuthorDate: Thu May 23 17:55:01 2019 +0100
Commit: Thorsten Behrens
CommitDate: Fri May 31 00:35:54 2019 +0200
Make renamefile more careful.
Change-Id: If39353fc01ea48d8e0077b228a6281839dde5c87
Reviewed-on: https://gerrit.libreoffice.org/72877
Reviewed-by: Thorsten Behrens
Tested-by: Thorsten Behrens
diff --git a/wsd/ClientSession.cpp b/wsd/ClientSession.cpp
index 9797d73bb..a1e6c9319 100644
--- a/wsd/ClientSession.cpp
+++ b/wsd/ClientSession.cpp
@@ -217,8 +217,10 @@ bool ClientSession::_handleInput(const char *buffer, int
length)
return true;
}
-else if (tokens[0] == "versionrestore") {
-if (tokens[1] == "prerestore") {
+else if (tokens[0] == "versionrestore")
+{
+if (tokens.size() > 1 && tokens[1] == "prerestore")
+{
// green signal to WOPI host to restore the version *after* saving
// any unsaved changes, if any, to the storage
docBroker->closeDocument("versionrestore: prerestore_ack");
___
Libreoffice-commits mailing list
libreoffice-comm...@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice-commits
[Libreoffice-commits] core.git: sw/qa
sw/qa/extras/ooxmlexport/ooxmlexport10.cxx |2 +- 1 file changed, 1 insertion(+), 1 deletion(-) New commits: commit 3a0ca1bff25d6c2bbc5bf8684eefd67956c2db95 Author: Andrea Gelmini AuthorDate: Thu May 30 09:44:22 2019 + Commit: Jens Carl CommitDate: Fri May 31 00:29:18 2019 +0200 Fix typo I don't understand if the right one is: raising is greater, then 100% or raising is greater than 100% Change-Id: I0bd4b297214f423ce0e3bb5223e0e2edee2a30e9 Reviewed-on: https://gerrit.libreoffice.org/73222 Tested-by: Jenkins Reviewed-by: Jens Carl diff --git a/sw/qa/extras/ooxmlexport/ooxmlexport10.cxx b/sw/qa/extras/ooxmlexport/ooxmlexport10.cxx index 9cb85a8d11f0..089e6cd666d3 100644 --- a/sw/qa/extras/ooxmlexport/ooxmlexport10.cxx +++ b/sw/qa/extras/ooxmlexport/ooxmlexport10.cxx @@ -210,7 +210,7 @@ DECLARE_OOXMLEXPORT_TEST(testFontEsc, "test_tdf120412.docx") return; // don't lose the run with superscript formatting assertXPath(pXmlDoc, "/w:document/w:body/w:p/w:r", 2); -// raising is greater, than 100% +// raising is greater than 100% assertXPath(pXmlDoc, "/w:document/w:body/w:p/w:r[2]/w:rPr/w:position","val", "24"); } ___ Libreoffice-commits mailing list libreoffice-comm...@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-commits
[Libreoffice-bugs] [Bug 125401] FILESAVE: Saving a document creates a new file (new inode number) thereby messing-up with the creation time of the document
https://bugs.documentfoundation.org/show_bug.cgi?id=125401 --- Comment #12 from Alex --- Ah, no. I just realized that timestamps attributes are independent of extended attributes. This was a false lead, sorry. -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 76324] CALC becomes very slow with 5000+ comments
https://bugs.documentfoundation.org/show_bug.cgi?id=76324 --- Comment #72 from b. --- pls. read comment https://bugs.documentfoundation.org/show_bug.cgi?id=125545#c10 -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 125545] performance issue caused by comments?
https://bugs.documentfoundation.org/show_bug.cgi?id=125545 --- Comment #10 from b. --- sorry for continuing here, the other thread is too long that anybody will read through it ... three observations: 1.) high cpu load is already triggered on hovering with the mouse / touchpad through the screen , you need not click anywhere, 2.) it is also triggered while hovering over an empty area of the screen, without any data or comments inside or belonging to the visible cells, 3.) things behave better - significantly better but far far away from fine! - when you save the file as 'fods', (Flat XML ODF spreadsheet), it's using plenty time the disk space but produces fewer delays / hangs / crashes or can handle singnificantly more cells and comments than with compression normally used for the file, one assumption: !!! it is only an assumption !!! might it be the case that comments are implemented as something like a 'one way referenced list', not having them inside the structure of the cells, but as a 'separate list', and with references which comment belongs to which cell only! in that list, but not having a reference at the cells where to look for the related comment? would be 'bad programming practice', even worse if the list is not sorted. that could explain plenty issues to me, everthing will work well while you have no or few comments, it's already a waste of ressources to check through that list on every mousemove, but it's done quickly and nobody complains about, once you have too many comments you have to check a long list ... on every mousemove!!! because you miss the path 'from coordinate to knowledge' and do a time consuming search instead, once the saved format is compressed that becomes very cpu-load-intense ... and one thought beyond the normal view: this issue is an ecological mess!!! besides wasting the time of plenty users in plenty plenty plenty little slices it's producing plenty plenty plenty plenty unneccessary cpu load on every mousemove of every calc user worldwide working in a file with commenst! and that wastes small but measureable pieces of energy, and plenty plenty plenty of them do! have an impact on global energy waste and thus contribute to ecological problems and climate change ... just my two cents, anybody laughing at me because he knows better ... should not laugh!!! - but share his knowledge where theese annoying performance impacts result from. -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 125598] calc scrollbars don't save correctly in ms formats
https://bugs.documentfoundation.org/show_bug.cgi?id=125598 --- Comment #1 from ffs --- FWIW it seems to work ok in writer fr both doc and docx -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 122200] kde5: Crash when navigating tree in accerciser (Accessibility Explorer)
https://bugs.documentfoundation.org/show_bug.cgi?id=122200 Michael Weghorn changed: What|Removed |Added Status|NEW |ASSIGNED Assignee|libreoffice-b...@lists.free |m.wegh...@posteo.de |desktop.org | -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 125598] New: calc scrollbars don't save correctly in ms formats
https://bugs.documentfoundation.org/show_bug.cgi?id=125598 Bug ID: 125598 Summary: calc scrollbars don't save correctly in ms formats Product: LibreOffice Version: 6.0.7.3 release Hardware: All OS: Linux (All) Status: UNCONFIRMED Severity: normal Priority: medium Component: Calc Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: dav1dblunk...@hotmail.com Description: Obviously a pita but I need to create a form in calc that is shared with excel users and it needs to have a scroll bar. If I save a scrollbar in LO and reload it: - .xls format: the scrollbar is there but the min and max values are 0,0 so it doesn't scroll. If I put them back to 0,100 and save/reload it is back to 0,0. - .xlsx format: the scrollbar is simply missing. Steps to Reproduce: Create a spreadsheet with a scroll bar save as .xls or .xlsx, reload and the scrollbar is broken or absent Actual Results: .xls :scrollbar is present but has incorrect range .xlsx: scrollbar is absernt Expected Results: scrollbar should be there and working Reproducible: Always User Profile Reset: No Additional Info: [Information automatically included from LibreOffice] Locale: en-GB Module: SpreadsheetDocument [Information guessed from browser] OS: Linux (All) OS is 64bit: yes -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 123542] Document with comments has a high memory usage after saving file
https://bugs.documentfoundation.org/show_bug.cgi?id=123542 --- Comment #4 from b. --- @xisco: reg. comment #3: 1. rise the number of comments and you'll produce freezes, crashes and so on as many as you like, 2. the bug 'performance issues caused by comments' is 5 years old now, imho after that time it's critical to delay further as 'low priority', 3. see list below ... there is a list of 121 bugs for comments in META #101216, 90 of them unresolved, 31 'resolved', the following are related to performance, https://bugs.documentfoundation.org/show_bug.cgi?id=60418 Bug 60418 - FILEOPEN and EDITING particular .odt with excessive lots of Comments causes heavy CPU and memory load, can crash on saving (edit) https://bugs.documentfoundation.org/show_bug.cgi?id=76324 Bug 76324 - CALC becomes very slow with 5000+ comments (edit) https://bugs.documentfoundation.org/show_bug.cgi?id=88070 Bug 88070 - FILESAVE: "The File could not be written" unable to save file with 3200+ comments https://bugs.documentfoundation.org/show_bug.cgi?id=88194 Bug 88194 - freeze when paste into lots of cells (cell with comment) (edit) https://bugs.documentfoundation.org/show_bug.cgi?id=97698 Bug 97698 - Calc very slows when spreadsheet has many notes (comments) and LO crash (edit) https://bugs.documentfoundation.org/show_bug.cgi?id=105499 Bug 105499 - Editing of .ods calc document with many comments causes high CPU load, can crash on saving (edit) https://bugs.documentfoundation.org/show_bug.cgi?id=106385 Bug 106385 - FILEOPEN: Crash when clicking on a spreadsheet with many comments (edit) https://bugs.documentfoundation.org/show_bug.cgi?id=113599 Bug 113599 - calc hangs when dealing with too many comments (edit) https://bugs.documentfoundation.org/show_bug.cgi?id=114377 Bug 114377 - Crash if pasting/copying calc cells with comments (5000 lines) (edit) https://bugs.documentfoundation.org/show_bug.cgi?id=119075 Bug 119075 - Slow scrolling after saving a document and switching sheets back and forth https://bugs.documentfoundation.org/show_bug.cgi?id=119636 Bug 119636 - XLSX file with 1500 comments in cells opens slow (edit) https://bugs.documentfoundation.org/show_bug.cgi?id=119650 Bug 119650 - FILESAVE: It takes >2:40 to save a small spreadsheet with comments and more than 400Mb in extra memory usage https://bugs.documentfoundation.org/show_bug.cgi?id=123417 Bug 123417 - File with lots of comments opens slower compared to LibO 4.4.7.2 (edit) https://bugs.documentfoundation.org/show_bug.cgi?id=123418 Bug 123418 - Showing all comments takes longer compared with 4.4.7.2 (edit) https://bugs.documentfoundation.org/show_bug.cgi?id=123419 Bug 123419 - Scrolling around in a document with lots of comment shown very slow compared to 4.4.7.2 (edit) https://bugs.documentfoundation.org/show_bug.cgi?id=123529 Bug 123529 - High CPU when scrolling in a calc sheet with lots of comment indicators (edit) https://bugs.documentfoundation.org/show_bug.cgi?id=123542#add_comment Bug 123542 - Document with comments has a high memory usage after saving file (edit) https://bugs.documentfoundation.org/show_bug.cgi?id=124692 Bug 124692 - 6.3.0.0.alpha0+ calc slow in reaction on mouseclicks, editing (edit) https://bugs.documentfoundation.org/show_bug.cgi?id=125545 Bug 125545 - performance issue caused by comments? (edit) inherited from OO3.x, results from calculating text boxes, how it feels to be an open source project maintainer -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 123529] High CPU when scrolling in a calc sheet with lots of comment indicators
https://bugs.documentfoundation.org/show_bug.cgi?id=123529 --- Comment #4 from b. --- @xisco: reg. comment #3 xisco, are you kidding? this user has about 5,2k comments in the demo, it's know since 2014! that calc has massive performance problems with comments, see #76324, wouldn't it be fair to tell affected users: - yes: we know there are massive performance issues with comments in calc, no: we didn't find time to fix it yet, no: we can't raise the priority or work on it while we have few programmers and bigger issues, workaround: avoid or reduce the use of comments - -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 123417] File with lots of comments opens slower compared to LibO 4.4.7.2
https://bugs.documentfoundation.org/show_bug.cgi?id=123417 --- Comment #6 from b. --- i doubt anything around comments is 'fine', you have about 6k long comments in the sheet, up from 200 you get measureable cpu load, up from 10k drastic delays and freezes - depends on system and version of course - , see #76324 and plenty subsequent reports reg. 'calc' and 'slow', there is! big performance impact by too many comments, it looks to be very difficult, otherwise someone would have fixed it in the past 5 years ... -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 125584] Foreign language displays in English font selection
https://bugs.documentfoundation.org/show_bug.cgi?id=125584 --- Comment #3 from Jeffery Small --- Pleas ignore my question about installing LibreOffice in a custom location. I found some instructions for doing this and installed 6.2.4.2. This version also displays the foreign characters as shown in the attached image. -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 125341] Crash upon exporting a document to PDF
https://bugs.documentfoundation.org/show_bug.cgi?id=125341 --- Comment #14 from raal --- no crash with Version: 6.3.0.0.alpha1+ (x64) Build ID: 2574ce0f2dc711e71b4799bbd76d5d8b6ec04300 CPU threads: 1; OS: Windows 10.0; UI render: default; VCL: win; TinderBox: Win-x86_64@62-TDF, Branch:master, Time: 2019-05-29_22:36:58 -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 119636] XLSX file with 1500 comments in cells opens slow
https://bugs.documentfoundation.org/show_bug.cgi?id=119636 --- Comment #10 from b. --- comments are slow in calc anyway, since 'inherited from OO', and reported since #76324 and plenty subsequent, i - assume - your problem is not a single special bug, but just a facet of the / one major problem in design ... at least it's helpless to work on it while the main issue remains, as the results would be covered by the overall delays. -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 106844] [Calc] Comparative summary of scenarios
https://bugs.documentfoundation.org/show_bug.cgi?id=106844 raal changed: What|Removed |Added Ever confirmed|0 |1 Status|UNCONFIRMED |NEW --- Comment #5 from raal --- setting as new -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 113599] calc hangs when dealing with too many comments
https://bugs.documentfoundation.org/show_bug.cgi?id=113599 --- Comment #4 from b. --- in response to Comment #3: yes: it is! a bug, yes: it is still in the program in ver: Version: 6.3.0.0.alpha1+ (x64) Build ID: 63b39fe87644587210214198fb67d6b3fb3343c5 CPU threads: 8; OS: Windows 6.1; UI render: default; VCL: win; TinderBox: Win-x86_64@42, Branch:master, Time: 2019-05-27_03:06:43 Locale: de-DE (de_DE); UI-Language: en-US Calc: *unthreaded* yes: imho it's a clear duplicate of 76324, yes: i'd like the importance raised, it's monstering around for more than 5 years now, yes: i tested AOO 4.1.6, it has similar problems, performing much better with a big number of comments - 30k?, but crash when expanding to 90k. as - in many comments - assorted as 'inherited from OO', perhaps an idea to form a combined team? -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 124795] Scrolling: Writer 100% CPU on specific docx (with table structure)
https://bugs.documentfoundation.org/show_bug.cgi?id=124795 kkivi changed: What|Removed |Added CC||konstantin.k...@gmail.com --- Comment #12 from kkivi --- Created attachment 151789 --> https://bugs.documentfoundation.org/attachment.cgi?id=151789=edit screenshot 100% CPU This is 100% CPU screenshot from Linux. We use different operating systems, so there may be a difference in details. I cannot work with this (short) file. Can you? -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 125597] New: LibreOffice-Writer-Properties-General- the Modified field remains blank after saving blank file
https://bugs.documentfoundation.org/show_bug.cgi?id=125597 Bug ID: 125597 Summary: LibreOffice-Writer-Properties-General- the Modified field remains blank after saving blank file Product: LibreOffice Version: 6.1.3.2 release Hardware: All OS: Windows (All) Status: UNCONFIRMED Severity: minor Priority: medium Component: Writer Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: topaz...@gmail.com Description: You open "LibreOffice" and after saving a blank file, the "Modified" field in the "General" tab is not updated and remain blanked. Setup: Windows 10 LibreOffice 6.1.3.2 Scenario: Open "Writer" Save the file (blank file-no content) Open General Steps to Reproduce: 1.Open "Writer" 2."Save" the file (blank file-no content) 3.Open "General" Actual Results: Only the "Created" field changed, the "Modified" field remains blank. Expected Results: Both "Created" & "Modified" fields should be updated according to when file was saved. Reproducible: Always User Profile Reset: Yes OpenGL enabled: Yes Additional Info: Note: -This happened with "LibreOffice" version 6.1.6 as well. -Workaround: if you "Save" the file again, the "Modified" field do change. -if you "Save" the file & replace it with a file with the same name (which is also blank file), the "Modified" field does change. -If you add content to the file before saving, for example, "Character(s)", the "Modified" field does change, even if you delete all the content you added before saving. -Happened with "Save as" and "CTRL+S" as well -I did try to resetting "UserProfile", the same result. -This is the information from "Help"-"About LibreOffice": Version: 6.2.4.2 (x64) Build ID: 2412653d852ce75f65fbfa83fb7e7b669a126d64 CPU threads: 8; OS: Windows 10.0; UI render: GL; VCL: win; Locale: en-US (he_IL); UI-Language: en-GB Calc: CL -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 106844] [Calc] Comparative summary of scenarios
https://bugs.documentfoundation.org/show_bug.cgi?id=106844 --- Comment #4 from gmoll...@us.es --- Yes, it is. -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 106844] [Calc] Comparative summary of scenarios
https://bugs.documentfoundation.org/show_bug.cgi?id=106844 --- Comment #3 from raal --- Do you mean something like this https://support.office.com/en-us/article/switch-between-various-sets-of-values-by-using-scenarios-2068afb1-ecdf-4956-9822-19ec479f55a2 -> Scenario summary reports ? -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 125584] Foreign language displays in English font selection
https://bugs.documentfoundation.org/show_bug.cgi?id=125584 Jeffery Small changed: What|Removed |Added Ever confirmed|1 |0 Status|NEEDINFO|UNCONFIRMED --- Comment #2 from Jeffery Small --- I checked this on version 6.2.0.3 which I have installed here and it shows the same foreign language as seen in the attached image from 6.1.6.3. I would like to install 6.2.4, but when I go to the download site, all I can find are deb and rpm packages. In the past I was able to download tar packages which let me manually install LibreOffice in a custom location and create by own links to the binaries, but I can no longer locate these. I don't want to override the standard package from the repository, but let it update naturally. If you can point me to the current location where I can find a tarball, I will install and check it. Thanks. -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-commits] core.git: sax/source
sax/source/tools/fastserializer.cxx | 43 +++-
1 file changed, 33 insertions(+), 10 deletions(-)
New commits:
commit f677885fec59f252f36673ee4d8c0b4863625a4d
Author: Eike Rathke
AuthorDate: Wed May 29 21:08:38 2019 +0200
Commit: Eike Rathke
CommitDate: Thu May 30 19:21:56 2019 +0200
Resolves: tdf#125279 do not double _x005F_ escapement
Reading OOXML _x005F_ escaped content may not get unescaped, so
when writing back to OOXML do not attempt to escape it again, i.e.
write _x005F_x_ as is and not as _x005F_x005F_x_.
This is more a workaround, the proper fix would be to unescape
_x005F_ content upon read. But then the entire "invalid XML
character" escapement and handling control characters rat tail
would come into play.
Change-Id: I3d31dc84a362753c23a8c89f7a5d7bfd06e4367b
Reviewed-on: https://gerrit.libreoffice.org/73187
Tested-by: Jenkins
Reviewed-by: Eike Rathke
diff --git a/sax/source/tools/fastserializer.cxx
b/sax/source/tools/fastserializer.cxx
index 1a422ad8239a..70a359b1c5ee 100644
--- a/sax/source/tools/fastserializer.cxx
+++ b/sax/source/tools/fastserializer.cxx
@@ -199,6 +199,7 @@ namespace sax_fastparser {
default:
if (mbXescape)
{
+char c1, c2, c3, c4;
// Escape characters not valid in XML 1.0 as
// _x_. A literal "_x_" has to be
// escaped as _x005F_x_ (effectively
@@ -209,22 +210,44 @@ namespace sax_fastparser {
if (c == '_' && i >= nNextXescape && i <= nLen
- kXescapeLen &&
pStr[i+6] == '_' &&
((pStr[i+1] | 0x20) == 'x') &&
-isHexDigit( pStr[i+2] ) &&
-isHexDigit( pStr[i+3] ) &&
-isHexDigit( pStr[i+4] ) &&
-isHexDigit( pStr[i+5] ))
+isHexDigit( c1 = pStr[i+2] ) &&
+isHexDigit( c2 = pStr[i+3] ) &&
+isHexDigit( c3 = pStr[i+4] ) &&
+isHexDigit( c4 = pStr[i+5] ))
{
// OOXML has the odd habit to write some
// names using this that when re-saving
// should *not* be escaped, specifically
// _x0020_ for blanks in w:xpath values.
-if (strncmp( pStr+i+2, "0020", 4) != 0)
+if (!(c1 == '0' && c2 == '0' && c3 == '2'
&& c4 == '0'))
{
-writeBytes( "_x005F_", kXescapeLen);
-// Remember this escapement so in
-// _x_x_ only the first '_' is
-// escaped.
-nNextXescape = i + kXescapeLen;
+// When encountering "_x005F_x_"
+// assume that is an already escaped
+// sequence that was not unescaped and
+// shall be written as is, to not end
+// up with "_x005F_x005F_x_" and
+// repeated..
+if (c1 == '0' && c2 == '0' && c3 ==
'5' && (c4 | 0x20) == 'f' &&
+i + kXescapeLen <= nLen - 6 &&
+pStr[i+kXescapeLen+5] == '_' &&
+((pStr[i+kXescapeLen+0] |
0x20) == 'x') &&
+isHexDigit(
pStr[i+kXescapeLen+1] ) &&
+isHexDigit(
pStr[i+kXescapeLen+2] ) &&
+isHexDigit(
pStr[i+kXescapeLen+3] ) &&
+isHexDigit(
pStr[i+kXescapeLen+4] ))
+{
+writeBytes( , 1 );
+// Remember this fake escapement.
+nNextXescape = i + kXescapeLen + 6;
+}
+else
+{
+
[Libreoffice-commits] core.git: sax/source
sax/source/tools/fastserializer.cxx | 16
sax/source/tools/fastserializer.hxx |3 +++
2 files changed, 19 insertions(+)
New commits:
commit 63c4e82c910422f928c8e0bcbb82b6c43d4d5557
Author: Eike Rathke
AuthorDate: Tue May 14 16:32:12 2019 +0200
Commit: Eike Rathke
CommitDate: Thu May 30 19:21:33 2019 +0200
Reintroduce mbXescape that got overaggressively removed
with
commit d4d37662b090cb237585156a47cd8e1f1cbe2656
CommitDate: Fri Oct 12 12:46:45 2018 +0200
loplugin:constfields in reportdesign,sal,sax
which killed also the bGood checking and later because that wasn't
used anymore also the SAL_WARN_IF() was eliminated with
commit 41eeaace84b45c803fff3ebd5ab981f0ad09393b
CommitDate: Mon Oct 29 15:12:26 2018 +0100
loplugin:oncevar
The mbXescape variable will be used, as the TODO said..
Change-Id: I11091379c27cf0222677595eb723b61ad3ebe4e8
Reviewed-on: https://gerrit.libreoffice.org/72302
Tested-by: Jenkins
Reviewed-by: Eike Rathke
diff --git a/sax/source/tools/fastserializer.cxx
b/sax/source/tools/fastserializer.cxx
index 4a4091438a40..1a422ad8239a 100644
--- a/sax/source/tools/fastserializer.cxx
+++ b/sax/source/tools/fastserializer.cxx
@@ -59,6 +59,7 @@ namespace sax_fastparser {
, mbMarkStackEmpty(true)
, mpDoubleStr(nullptr)
, mnDoubleStrCapacity(RTL_STR_MAX_VALUEOFDOUBLE)
+, mbXescape(true)
{
rtl_string_new_WithLength(, mnDoubleStrCapacity);
mxFastTokenHandler = css::xml::sax::FastTokenHandler::create(
@@ -135,6 +136,7 @@ namespace sax_fastparser {
return;
}
+bool bGood = true;
const sal_Int32 kXescapeLen = 7;
char bufXescape[kXescapeLen+1];
sal_Int32 nNextXescape = 0;
@@ -195,6 +197,7 @@ namespace sax_fastparser {
}
break;
default:
+if (mbXescape)
{
// Escape characters not valid in XML 1.0 as
// _x_. A literal "_x_" has to be
@@ -239,10 +242,23 @@ namespace sax_fastparser {
* scanning for both encoded sequences and
* write as _x_? */
}
+#if OSL_DEBUG_LEVEL > 0
+else
+{
+if (bGood && invalidChar(pStr[i]))
+{
+bGood = false;
+// The SAL_WARN() for the single character
is
+// issued in writeBytes(), just gather for
the
+// SAL_WARN_IF() below.
+}
+}
+#endif
writeBytes( , 1 );
break;
}
}
+SAL_WARN_IF( !bGood && nLen > 1, "sax", "in '" <<
OString(pStr,std::min(nLen,42)) << "'");
}
void FastSaxSerializer::endDocument()
diff --git a/sax/source/tools/fastserializer.hxx
b/sax/source/tools/fastserializer.hxx
index b00ccf0923df..e3aa17a78f91 100644
--- a/sax/source/tools/fastserializer.hxx
+++ b/sax/source/tools/fastserializer.hxx
@@ -228,6 +228,9 @@ private:
rtl_String *mpDoubleStr;
sal_Int32 mnDoubleStrCapacity;
TokenValueList maTokenValues;
+bool mbXescape; ///< whether to escape invalid XML characters as
_x_ in write(const char*,sal_Int32,true)
+/* TODO: make that configurable from the outside for
+ * some specific cases? */
#ifdef DBG_UTIL
std::stack m_DebugStartedElements;
___
Libreoffice-commits mailing list
libreoffice-comm...@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice-commits
[Libreoffice-bugs] [Bug 125401] FILESAVE: Saving a document creates a new file (new inode number) thereby messing-up with the creation time of the document
https://bugs.documentfoundation.org/show_bug.cgi?id=125401 --- Comment #11 from Alex --- I also found some additional information in this Q: https://unix.stackexchange.com/questions/118840/preserving-extended-attributes-with-cp-rsync/119980#119980 By the way, thanks for having a look into this. -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 125596] DOCX: Writer misidentify text language (and appropriate font) in MS Word file (MSO2019)
https://bugs.documentfoundation.org/show_bug.cgi?id=125596 --- Comment #1 from Ratchanan Srirattanamet --- Created attachment 151788 --> https://bugs.documentfoundation.org/attachment.cgi?id=151788=edit All screenshots from MS Office 2019 and LibreOffice 6.4.2.4 -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 125596] New: DOCX: Writer misidentify text language (and appropriate font) in MS Word file (MSO2019)
https://bugs.documentfoundation.org/show_bug.cgi?id=125596
Bug ID: 125596
Summary: DOCX: Writer misidentify text language (and
appropriate font) in MS Word file (MSO2019)
Product: LibreOffice
Version: 6.0.7.3 release
Hardware: x86-64 (AMD64)
OS: All
Status: UNCONFIRMED
Severity: normal
Priority: medium
Component: Writer
Assignee: libreoffice-bugs@lists.freedesktop.org
Reporter: p...@peat-network.xyz
Created attachment 151787
--> https://bugs.documentfoundation.org/attachment.cgi?id=151787=edit
The DOCX file which has the problem
Step to reproduce:
1. Download the font "TH Sarabun New" from [1]. The font is licensed under GPL
2.0 + font exception.
2. Open the attached DOCX document. The text is configured to use "TH Sarabun
New" as the complex (Thai) font, and "Liberation Sans" as the western font.
Both of them are 16 pt.
Expectation: The Thai text (the word "ไทย") and most of the dots (".") are
displayed using "TH Sarabun New", while the English text (the word "English")
and the dots between the pipes ("|", including the pipes themselves) are
displayed using "Liberation Sans". The whole text is fit within one line. MS
Word 2019 shows this expected behavior. (See the screenshots.)
Actual result: The Thai text is displayed using "TH Sarabun New", while the
English text, all dots, and the pipes are displayed using "Liberation Sans".
The whole text is not fit within one line.
The problem is reproducible on:
- LO 6.0.7-0ubuntu0.18.04.6 from Ubuntu 18.04.
- LO 6.2.4.2 on Ubuntu 18.04, Snap and AppImage.
- LO 6.2.4.2 on Windows 10 version 1903 (build 18326.86)
The reason this is important is that most of the Thai fonts use the different
font metrics then western fonts. For historical reason [2], Thai fonts consider
that point-size means "line-height". As Thai symbols contain the symbol above
and below the character, Thai fonts are usually 30% smaller than western fonts
at the same point-size. [3]
Adding to this problem, MS Word considers the language of the text using the
keyboard layout when it's typed, not actual text. For example, typing a dot
(".") while using a Thai keyboard layout will make that dot Thai while typing a
dot while using an English keyboard layout will make that dot English. MS Word
seems to record this information in the file, which LO seems to be unable to
read. So, when LO opens the file, LO displays the text using the wrong font
with different font metric, causing the document's layout to changes.
[1] http://mdresearch.kku.ac.th/files/font/THSarabunNew.zip
[2] http://thep.blogspot.com/2016/02/thai-font-metrics.html (In Thai)
[3] However, some Thai fonts, mostly fonts from Thai Linux Working Group
(TLWG), now uses the new metric which considers point-size to be character
size. This makes those fonts have the same size as western fonts. See [2].
--
You are receiving this mail because:
You are the assignee for the bug.___
Libreoffice-bugs mailing list
Libreoffice-bugs@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-commits] core.git: sw/source
sw/source/filter/xml/xmlfmte.cxx |2 -- 1 file changed, 2 deletions(-) New commits: commit 1376bb3e44c4b9eb15cf788df04f7cc0bba8cb09 Author: Miklos Vajna AuthorDate: Thu May 30 17:40:14 2019 +0200 Commit: Miklos Vajna CommitDate: Thu May 30 18:42:07 2019 +0200 ODT export: remove leftover debug include And if I'm at it, IWYU pointed one more unused one. Change-Id: I978e0bbf281bebc3da574a8a857167b18a540f0a Reviewed-on: https://gerrit.libreoffice.org/73215 Reviewed-by: Miklos Vajna Tested-by: Jenkins diff --git a/sw/source/filter/xml/xmlfmte.cxx b/sw/source/filter/xml/xmlfmte.cxx index 737f0e7ed8c9..642e9d1d93fd 100644 --- a/sw/source/filter/xml/xmlfmte.cxx +++ b/sw/source/filter/xml/xmlfmte.cxx @@ -33,13 +33,11 @@ #include #include #include -#include #include #include #include "xmlexp.hxx" #include #include -#include using namespace ::com::sun::star::beans; using namespace ::com::sun::star::uno; ___ Libreoffice-commits mailing list libreoffice-comm...@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-commits
[Libreoffice-bugs] [Bug 109530] [META] File opening issues
https://bugs.documentfoundation.org/show_bug.cgi?id=109530 Roman Kuznetsov <79045_79...@mail.ru> changed: What|Removed |Added Depends on||125372 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=125372 [Bug 125372] FILEOPEN: LibreOffice freeze opening document -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 125372] FILEOPEN: LibreOffice freeze opening document
https://bugs.documentfoundation.org/show_bug.cgi?id=125372 Roman Kuznetsov <79045_79...@mail.ru> changed: What|Removed |Added Blocks||109530 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=109530 [Bug 109530] [META] File opening issues -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 125398] Shadow shows on inserted images in doc/pdf files
https://bugs.documentfoundation.org/show_bug.cgi?id=125398 --- Comment #6 from griffi...@gmail.com --- I did. In my previous message. attachment 151637 I don't know what more I can do to demonstrate it. Really, you need to create an image (save selection). Then in LibreWriter new document. Insert the image. Then play around with Zoom levels - at some level(s) you will see the bug. If my attachment was no use - that is what you need to do. -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-commits] core.git: sw/inc sw/source
sw/inc/txatbase.hxx |6 +++---
sw/source/core/access/accpara.cxx |6 +++---
sw/source/core/crsr/findattr.cxx| 10 +-
sw/source/core/doc/docruby.cxx |4 ++--
sw/source/core/fields/reffld.cxx|2 +-
sw/source/core/text/itratr.cxx | 10 +-
sw/source/core/text/pormulti.cxx|8
sw/source/core/text/txtfld.cxx |4 ++--
sw/source/core/text/txtfrm.cxx |4 ++--
sw/source/core/tox/ToxTextGenerator.cxx |2 +-
sw/source/core/txtnode/ndhints.cxx | 18 +-
sw/source/core/undo/rolbck.cxx |8
sw/source/core/unocore/unoportenum.cxx |2 +-
sw/source/filter/ww8/wrtw8nds.cxx |2 +-
14 files changed, 43 insertions(+), 43 deletions(-)
New commits:
commit 2eebd9119bebb94f9c9f2bf718f5321511276a84
Author: Noel Grandin
AuthorDate: Sat May 25 14:52:57 2019 +0200
Commit: Noel Grandin
CommitDate: Thu May 30 18:22:42 2019 +0200
GetAnyEnd does not need to return a pointer
Change-Id: I1350a340eddad180447c46175b6b21ce787802f3
Reviewed-on: https://gerrit.libreoffice.org/72952
Tested-by: Jenkins
Reviewed-by: Noel Grandin
diff --git a/sw/inc/txatbase.hxx b/sw/inc/txatbase.hxx
index 0e2aebdb846f..90509a929309 100644
--- a/sw/inc/txatbase.hxx
+++ b/sw/inc/txatbase.hxx
@@ -86,7 +86,7 @@ public:
virtual void SetEnd(sal_Int32);
inline const sal_Int32* End() const;
/// end (if available), else start
-inline const sal_Int32* GetAnyEnd() const;
+inline sal_Int32 GetAnyEnd() const;
inline void SetDontExpand( bool bDontExpand );
bool DontExpand() const { return m_bDontExpand; }
@@ -150,10 +150,10 @@ inline const sal_Int32* SwTextAttr::End() const
return GetEnd();
}
-inline const sal_Int32* SwTextAttr::GetAnyEnd() const
+inline sal_Int32 SwTextAttr::GetAnyEnd() const
{
const sal_Int32* pEnd = End();
-return pEnd ? pEnd : _nStart;
+return pEnd ? *pEnd : m_nStart;
}
inline const SfxPoolItem& SwTextAttr::GetAttr() const
diff --git a/sw/source/core/access/accpara.cxx
b/sw/source/core/access/accpara.cxx
index dc87d1ebe943..31d00a30021e 100644
--- a/sw/source/core/access/accpara.cxx
+++ b/sw/source/core/access/accpara.cxx
@@ -2776,7 +2776,7 @@ const SwTextAttr *SwHyperlinkIter_Impl::next(SwTextNode
const** ppNode)
if (RES_TXTATR_INETFMT == pHt->Which())
{
const TextFrameIndex nHtStt(m_rFrame.MapModelToView(pNode,
pHt->GetStart()));
-const TextFrameIndex nHtEnd(m_rFrame.MapModelToView(pNode,
*pHt->GetAnyEnd()));
+const TextFrameIndex nHtEnd(m_rFrame.MapModelToView(pNode,
pHt->GetAnyEnd()));
if (nHtEnd > nHtStt &&
((nHtStt >= m_nStt && nHtStt < m_nEnd) ||
(nHtEnd > m_nStt && nHtEnd <= m_nEnd)))
@@ -2839,7 +2839,7 @@ uno::Reference< XAccessibleHyperlink > SAL_CALL
if (!xRet.is())
{
TextFrameIndex const
nHintStart(pTextFrame->MapModelToView(pNode, pHt->GetStart()));
-TextFrameIndex const
nHintEnd(pTextFrame->MapModelToView(pNode, *pHt->GetAnyEnd()));
+TextFrameIndex const
nHintEnd(pTextFrame->MapModelToView(pNode, pHt->GetAnyEnd()));
const sal_Int32 nTmpHStt =
GetPortionData().GetAccessiblePosition(
max(aHIter.startIdx(), nHintStart));
const sal_Int32 nTmpHEnd =
GetPortionData().GetAccessiblePosition(
@@ -2891,7 +2891,7 @@ sal_Int32 SAL_CALL
SwAccessibleParagraph::getHyperLinkIndex( sal_Int32 nCharInde
SwTextNode const* pNode(nullptr);
const SwTextAttr *pHt = aHIter.next();
while (pHt && !(nIdx >= pTextFrame->MapModelToView(pNode,
pHt->GetStart())
- && nIdx < pTextFrame->MapModelToView(pNode,
*pHt->GetAnyEnd(
+ && nIdx < pTextFrame->MapModelToView(pNode,
pHt->GetAnyEnd(
{
pHt = aHIter.next();
nPos++;
diff --git a/sw/source/core/crsr/findattr.cxx b/sw/source/core/crsr/findattr.cxx
index d826878b4e23..c77dc2065979 100644
--- a/sw/source/core/crsr/findattr.cxx
+++ b/sw/source/core/crsr/findattr.cxx
@@ -339,7 +339,7 @@ lcl_IsAttributeIgnorable(sal_Int32 const nNdStart,
sal_Int32 const nNdEnd,
bool SwAttrCheckArr::SetAttrFwd( const SwTextAttr& rAttr )
{
-SwSrchChrAttr aTmp( rAttr.GetAttr(), rAttr.GetStart(), *rAttr.GetAnyEnd()
);
+SwSrchChrAttr aTmp( rAttr.GetAttr(), rAttr.GetStart(), rAttr.GetAnyEnd() );
// ignore all attributes not in search range
if (lcl_IsAttributeIgnorable(m_nNodeStart, m_nNodeEnd, aTmp))
@@ -493,7 +493,7 @@ bool SwAttrCheckArr::SetAttrFwd( const SwTextAttr& rAttr )
bool SwAttrCheckArr::SetAttrBwd( const SwTextAttr& rAttr )
{
-SwSrchChrAttr aTmp( rAttr.GetAttr(), rAttr.GetStart(), *rAttr.GetAnyEnd()
);
+SwSrchChrAttr aTmp( rAttr.GetAttr(),
[Libreoffice-commits] core.git: sw/source
sw/source/core/doc/docbm.cxx |4
1 file changed, 4 deletions(-)
New commits:
commit 79b233be14e75157aecd97179c568baad0a60016
Author: Noel Grandin
AuthorDate: Thu May 30 16:03:13 2019 +0200
Commit: Noel Grandin
CommitDate: Thu May 30 18:19:41 2019 +0200
"more than USHRT_MAX marks" seems to be fine now
Change-Id: Iccd87324b56fb7ff003f028330758024e47f3f26
Reviewed-on: https://gerrit.libreoffice.org/73207
Tested-by: Jenkins
Reviewed-by: Noel Grandin
diff --git a/sw/source/core/doc/docbm.cxx b/sw/source/core/doc/docbm.cxx
index 283585c7aa2c..096c6ab29549 100644
--- a/sw/source/core/doc/docbm.cxx
+++ b/sw/source/core/doc/docbm.cxx
@@ -421,10 +421,6 @@ namespace sw { namespace mark
pPos2->nContent.GetIndex());
}
#endif
-// see for example _SaveContentIdx, Shells
-OSL_PRECOND(m_vAllMarks.size() < USHRT_MAX,
-"MarkManager::makeMark(..)"
-" - more than USHRT_MAX marks are not supported correctly");
// There should only be one CrossRefBookmark per Textnode per Type
if ((eType == MarkType::CROSSREF_NUMITEM_BOOKMARK || eType ==
MarkType::CROSSREF_HEADING_BOOKMARK)
&& (lcl_FindMarkAtPos(m_vBookmarks, *rPaM.Start(), eType) !=
m_vBookmarks.end()))
___
Libreoffice-commits mailing list
libreoffice-comm...@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice-commits
[Libreoffice-bugs] [Bug 125595] FORMATTING: Validity cell range with invisible characters (e.g. newline) stripped
https://bugs.documentfoundation.org/show_bug.cgi?id=125595 --- Comment #1 from Teraslilja --- Created attachment 151786 --> https://bugs.documentfoundation.org/attachment.cgi?id=151786=edit Demonstrating the issues -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 125595] New: FORMATTING: Validity cell range with invisible characters (e.g. newline) stripped
https://bugs.documentfoundation.org/show_bug.cgi?id=125595 Bug ID: 125595 Summary: FORMATTING: Validity cell range with invisible characters (e.g. newline) stripped Product: LibreOffice Version: 6.0.7.3 release Hardware: All OS: All Status: UNCONFIRMED Severity: normal Priority: medium Component: Calc Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: m-matti-a.lehto...@iki.fi Description: When there is defined a validity check with cell range and those cells contain invisible characters, especially newline character there are multiple issues. 1) The selection menu has stripped the invisible characters e.g. newline 2) When the value selected to cell, the invisible characters e.g. newline are stripped (visually). How ever vlookup() finds correctly 3) When opening document, then the vlookup() fails, and is fixed after reselection Steps to Reproduce: 1. Fill several cells with normal text and newline characters 2. Set a validity for some cell with the cells as a range above 3. Have at another cell a vlookup() to verify validity of selected value 4. save, close and reopen the document 5. Notice the vlookup() to fail Actual Results: 1. After selection newline characters have no effect of causing a visual new line 2. vlookup() fails after loading document Expected Results: 1. Pulldown menu can have a fixed height cells for value selection 2. When a value is selected, newlines work as expected 3. after loading a document, vlookup() do not fail Reproducible: Always User Profile Reset: No OpenGL enabled: Yes Additional Info: Version: 6.0.7.3 Build ID: 1:6.0.7-0ubuntu0.18.04.5 CPU threads: 4; OS: Linux 4.15; UI render: default; VCL: gtk3; Locale: en-CA (en_CA.UTF-8); Calc: group -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 108075] [META] Scrolling and Page up/down issues
https://bugs.documentfoundation.org/show_bug.cgi?id=108075 Dieter Praas changed: What|Removed |Added Depends on||124795 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=124795 [Bug 124795] Scrolling: Writer 100% CPU on specific docx (with table structure) -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
