[Libreoffice-commits] core.git: scp2/source
scp2/source/ooo/file_ooo.scp |1 + scp2/source/ooo/module_lang_template.scp |1 + 2 files changed, 2 insertions(+) New commits: commit a36a3f65d19497a0f6f13780b8e2bf0068c94c18 Author: Kelemen Gábor AuthorDate: Thu Dec 5 15:37:25 2019 +0100 Commit: Andras Timar CommitDate: Fri Dec 6 08:57:30 2019 +0100 tdf#126192 tdf#126030 (related) Package translations of oox Now that there are some available, new mo files need to be added to the installer. Tested with Spanish on Windows to work. Change-Id: Id70305fa5a674bc9e302aa6937a03c4573888da4 Reviewed-on: https://gerrit.libreoffice.org/84569 Tested-by: Jenkins Reviewed-by: Andras Timar diff --git a/scp2/source/ooo/file_ooo.scp b/scp2/source/ooo/file_ooo.scp index 0f34c027d85d..50d5b1a0fdf7 100644 --- a/scp2/source/ooo/file_ooo.scp +++ b/scp2/source/ooo/file_ooo.scp @@ -191,6 +191,7 @@ MO_FILELIST_ALL_LANG(for) MO_FILELIST_ALL_LANG(fps) MO_FILELIST_ALL_LANG(frm) MO_FILELIST_ALL_LANG(fwk) +MO_FILELIST_ALL_LANG(oox) MO_FILELIST_ALL_LANG(pcr) MO_FILELIST_ALL_LANG(rpt) MO_FILELIST_ALL_LANG(sb) diff --git a/scp2/source/ooo/module_lang_template.scp b/scp2/source/ooo/module_lang_template.scp index 0455a4e75133..76003780f19a 100644 --- a/scp2/source/ooo/module_lang_template.scp +++ b/scp2/source/ooo/module_lang_template.scp @@ -63,6 +63,7 @@ Module gid_Module_Langpack_Basis_Template gid_File_Res_fps_Lang, gid_File_Res_frm_Lang, gid_File_Res_fwk_Lang, + gid_File_Res_oox_Lang, gid_File_Res_pcr_Lang, gid_File_Res_rpt_Lang, gid_File_Res_sb_Lang, ___ Libreoffice-commits mailing list libreoffice-comm...@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-commits
[Libreoffice-bugs] [Bug 129164] Missing Menu Format/Zone/Define
https://bugs.documentfoundation.org/show_bug.cgi?id=129164 --- Comment #6 from y.leme...@wanadoo.fr --- (In reply to Julien Nabet from comment #5) > Heiko/Xisco: I don't remember "print area" is present in Writer but am not > sure. > Any thoughts here? I think that you ask the right question : is Zone/Definir an actual option of writer ? If not (Zone/Definir is only available under calc), that bug is NOT a bug ; only a dream of my mind. Please will you forgive me and close the thread ? In fact, under writer, restriction of impress is possible page by page, NOT zone by zone Thank you for your help ! y.leme...@wanadoo.fr -- 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 129203] Split Cell Recommendations
https://bugs.documentfoundation.org/show_bug.cgi?id=129203 Heiko Tietze changed: What|Removed |Added CC|libreoffice-ux-advise@lists |heiko.tietze@documentfounda |.freedesktop.org|tion.org Keywords|needsUXEval | Ever confirmed|0 |1 Status|UNCONFIRMED |NEW --- Comment #1 from Heiko Tietze --- Sounds reasonable. We have to implement it with check boxes instead the radio buttons and spinners next to it. Or just the spinners as 1 could mean no change. -- 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 129203] Split Cell Recommendations
https://bugs.documentfoundation.org/show_bug.cgi?id=129203 Heiko Tietze changed: What|Removed |Added CC|libreoffice-ux-advise@lists |heiko.tietze@documentfounda |.freedesktop.org|tion.org Keywords|needsUXEval | Ever confirmed|0 |1 Status|UNCONFIRMED |NEW --- Comment #1 from Heiko Tietze --- Sounds reasonable. We have to implement it with check boxes instead the radio buttons and spinners next to it. Or just the spinners as 1 could mean no change. -- 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] online.git: test/httpwstest.cpp test/Makefile.am test/UnitCalc.cpp test/UnitLoad.cpp
test/Makefile.am|4
test/UnitCalc.cpp | 486
test/UnitLoad.cpp | 10 -
test/httpwstest.cpp | 398 --
4 files changed, 491 insertions(+), 407 deletions(-)
New commits:
commit b5f78fe73d9879751492bcfa50b151b95fd33e8c
Author: Miklos Vajna
AuthorDate: Fri Dec 6 08:51:51 2019 +0100
Commit: Miklos Vajna
CommitDate: Fri Dec 6 08:51:51 2019 +0100
Convert some Calc tests to a new-style one
So that they are in-process, which means it's easier to debug when they
fail.
Also, in UnitLoad, give up on trying to avoid the sleep after
disconnecting, it seems the old condition was not reliable.
Change-Id: I972a3319887a70eeea2585104ed1e762830ca505
diff --git a/test/Makefile.am b/test/Makefile.am
index 61fd8a142..532c28818 100644
--- a/test/Makefile.am
+++ b/test/Makefile.am
@@ -33,6 +33,7 @@ noinst_LTLIBRARIES = \
unit-uno-command.la \
unit-load.la \
unit-cursor.la \
+ unit-calc.la \
unit-wopi-loadencoded.la unit-wopi-temp.la
MAGIC_TO_FORCE_SHLIB_CREATION = -rpath /dummy
@@ -158,6 +159,8 @@ unit_load_la_SOURCES = UnitLoad.cpp
unit_load_la_LIBADD = $(CPPUNIT_LIBS)
unit_cursor_la_SOURCES = UnitCursor.cpp
unit_cursor_la_LIBADD = $(CPPUNIT_LIBS)
+unit_calc_la_SOURCES = UnitCalc.cpp
+unit_calc_la_LIBADD = $(CPPUNIT_LIBS)
if HAVE_LO_PATH
SYSTEM_STAMP = @SYSTEMPLATE_PATH@/system_stamp
@@ -189,6 +192,7 @@ TESTS = unit-copy-paste.la unit-typing.la unit-convert.la
unit-prefork.la unit-t
unit-uno-command.la \
unit-load.la \
unit-cursor.la \
+ unit-calc.la \
unit-wopi-loadencoded.la unit-wopi-temp.la
# TESTS = unit-client.la
# TESTS += unit-admin.la
diff --git a/test/UnitCalc.cpp b/test/UnitCalc.cpp
new file mode 100644
index 0..b874fa352
--- /dev/null
+++ b/test/UnitCalc.cpp
@@ -0,0 +1,486 @@
+/* -*- Mode: C++; tab-width: 4; indent-tabs-mode: nil; c-basic-offset: 4;
fill-column: 100 -*- */
+/*
+ * This file is part of the LibreOffice project.
+ *
+ * This Source Code Form is subject to the terms of the Mozilla Public
+ * License, v. 2.0. If a copy of the MPL was not distributed with this
+ * file, You can obtain one at http://mozilla.org/MPL/2.0/.
+ */
+
+#include
+#include
+#include
+#include
+
+#include
+#include
+#include
+#include
+
+#include
+#include
+#include
+
+class LOOLWebSocket;
+
+namespace
+{
+double getColRowSize(const std::string& property, const std::string& message,
int index)
+{
+Poco::JSON::Parser parser;
+const Poco::Dynamic::Var result = parser.parse(message);
+const auto& command = result.extract();
+std::string text = command->get("commandName").toString();
+
+CPPUNIT_ASSERT_EQUAL(std::string(".uno:ViewRowColumnHeaders"), text);
+CPPUNIT_ASSERT(command->isArray(property));
+
+Poco::JSON::Array::Ptr array = command->getArray(property);
+
+CPPUNIT_ASSERT(array->isObject(index));
+
+Poco::SharedPtr item = array->getObject(index);
+
+CPPUNIT_ASSERT(item->has("size"));
+
+return item->getValue("size");
+}
+
+double getColRowSize(const std::shared_ptr& socket, const
std::string& item,
+ int index, const std::string& testname)
+{
+std::vector response;
+response = helpers::getResponseMessage(socket, "commandvalues:", testname);
+CPPUNIT_ASSERT_MESSAGE("did not receive a commandvalues: message as
expected",
+ !response.empty());
+std::vector json(response.begin() +
std::string("commandvalues:").length(),
+ response.end());
+json.push_back(0);
+return getColRowSize(item, json.data(), index);
+}
+}
+
+/// Test suite for Calc.
+class UnitCalc : public UnitWSD
+{
+TestResult testCalcEditRendering();
+TestResult testCalcRenderAfterNewView51();
+TestResult testCalcRenderAfterNewView53();
+TestResult testColumnRowResize();
+TestResult testOptimalResize();
+
+public:
+void invokeTest() override;
+};
+
+UnitBase::TestResult UnitCalc::testCalcEditRendering()
+{
+const char* testname = "calcEditRendering ";
+Poco::URI uri(helpers::getTestServerURI());
+std::shared_ptr socket
+= helpers::loadDocAndGetSocket("calc_render.xls", uri, testname);
+
+helpers::sendTextFrame(socket, "mouse type=buttondown x=5000 y=5 count=1
buttons=1 modifier=0",
+ testname);
+helpers::sendTextFrame(socket, "key type=input char=97 key=0", testname);
+helpers::sendTextFrame(socket, "key type=input char=98 key=0", testname);
+helpers::sendTextFrame(socket, "key type=input char=99 key=0", testname);
+
+helpers::assertResponseString(socket, "cellformula: abc", testname);
+
+const char* req = "tilecombine nviewid=0 part=0 width=512 height=512
tileposx=3840 tileposy=0 "
+ "tilewidth=7680 tileheight=7680";
+
[Libreoffice-commits] core.git: solenv/bin xmloff/inc xmloff/source xmloff/util
solenv/bin/native-code.py |1 +
xmloff/inc/facreg.hxx |7 ---
xmloff/source/core/facreg.cxx |3 ---
xmloff/source/draw/sdxmlexp.cxx | 12 +++-
xmloff/util/xo.component|3 ++-
5 files changed, 14 insertions(+), 12 deletions(-)
New commits:
commit 6182f1053c1cf98fb3c7129e478e271ea1ee9977
Author: Miklos Vajna
AuthorDate: Thu Dec 5 21:13:12 2019 +0100
Commit: Miklos Vajna
CommitDate: Fri Dec 6 08:50:13 2019 +0100
xmloff: create XMLDrawExportOasis instances with an uno constructor
See tdf#74608 for motivation.
Change-Id: Id8cad1ed02b5fee93184e17ebf80435c01aa3618
Reviewed-on: https://gerrit.libreoffice.org/84583
Tested-by: Jenkins
Reviewed-by: Miklos Vajna
diff --git a/solenv/bin/native-code.py b/solenv/bin/native-code.py
index 533bcd0564c4..5b67a5300bf4 100755
--- a/solenv/bin/native-code.py
+++ b/solenv/bin/native-code.py
@@ -290,6 +290,7 @@ core_constructor_list = [
"com_sun_star_comp_Draw_XMLOasisMetaExporter_get_implementation",
"com_sun_star_comp_Draw_XMLOasisContentExporter_get_implementation",
"com_sun_star_comp_Draw_XMLOasisStylesExporter_get_implementation",
+"com_sun_star_comp_Draw_XMLOasisExporter_get_implementation",
"com_sun_star_comp_Draw_XMLOasisImporter_get_implementation",
"com_sun_star_comp_Draw_XMLOasisStylesImporter_get_implementation",
"com_sun_star_comp_Draw_XMLOasisContentImporter_get_implementation",
diff --git a/xmloff/inc/facreg.hxx b/xmloff/inc/facreg.hxx
index a4e8cb50d272..25b2334f0b1b 100644
--- a/xmloff/inc/facreg.hxx
+++ b/xmloff/inc/facreg.hxx
@@ -31,13 +31,6 @@ namespace com { namespace sun { namespace star {
namespace uno { class XInterface; }
} } }
-// draw oasis export
-OUString XMLDrawExportOasis_getImplementationName() throw();
-css::uno::Sequence XMLDrawExportOasis_getSupportedServiceNames()
throw();
-/// @throws css::uno::Exception
-css::uno::Reference XMLDrawExportOasis_createInstance(
-css::uno::Reference const & rSMgr);
-
// impress animation import
OUString AnimationsImport_getImplementationName() throw();
css::uno::Sequence AnimationsImport_getSupportedServiceNames()
throw();
diff --git a/xmloff/source/core/facreg.cxx b/xmloff/source/core/facreg.cxx
index 97b7a2b71918..a6018bf06ed6 100644
--- a/xmloff/source/core/facreg.cxx
+++ b/xmloff/source/core/facreg.cxx
@@ -56,9 +56,6 @@ XMLOFF_DLLPUBLIC void * xo_component_getFactory( const
sal_Char * pImplName, voi
SINGLEFACTORY( AnimationsImport )
-// draw oasis export
-else SINGLEFACTORY( XMLDrawExportOasis )
-
// drawing layer export
else SINGLEFACTORY( XMLDrawingLayerExport )
diff --git a/xmloff/source/draw/sdxmlexp.cxx b/xmloff/source/draw/sdxmlexp.cxx
index e54af095a2e7..68854c836b68 100644
--- a/xmloff/source/draw/sdxmlexp.cxx
+++ b/xmloff/source/draw/sdxmlexp.cxx
@@ -2772,7 +2772,17 @@
com_sun_star_comp_Draw_XMLOasisStylesExporter_get_implementation(
| SvXMLExportFlags::AUTOSTYLES | SvXMLExportFlags::FONTDECLS));
}
-SERVICE( XMLDrawExportOasis, "com.sun.star.comp.Draw.XMLOasisExporter",
"XMLDrawExportOasis", true,
SvXMLExportFlags::OASIS|SvXMLExportFlags::META|SvXMLExportFlags::STYLES|SvXMLExportFlags::MASTERSTYLES|SvXMLExportFlags::AUTOSTYLES|SvXMLExportFlags::CONTENT|SvXMLExportFlags::SCRIPTS|SvXMLExportFlags::SETTINGS|SvXMLExportFlags::FONTDECLS|SvXMLExportFlags::EMBEDDED
);
+extern "C" SAL_DLLPUBLIC_EXPORT uno::XInterface*
+com_sun_star_comp_Draw_XMLOasisExporter_get_implementation(uno::XComponentContext*
pCtx,
+
uno::Sequence const& /*rSeq*/)
+{
+return cppu::acquire(new SdXMLExport(
+pCtx, "XMLDrawExportOasis", true,
+SvXMLExportFlags::OASIS | SvXMLExportFlags::META |
SvXMLExportFlags::STYLES
+| SvXMLExportFlags::MASTERSTYLES | SvXMLExportFlags::AUTOSTYLES
+| SvXMLExportFlags::CONTENT | SvXMLExportFlags::SCRIPTS |
SvXMLExportFlags::SETTINGS
+| SvXMLExportFlags::FONTDECLS | SvXMLExportFlags::EMBEDDED));
+}
SERVICE( XMLDrawingLayerExport, "com.sun.star.comp.DrawingLayer.XMLExporter",
"XMLDrawingLayerExport", true,
SvXMLExportFlags::OASIS|SvXMLExportFlags::STYLES|SvXMLExportFlags::AUTOSTYLES|SvXMLExportFlags::CONTENT|SvXMLExportFlags::FONTDECLS|SvXMLExportFlags::EMBEDDED
);
SERVICE( XMLImpressClipboardExport,
"com.sun.star.comp.Impress.XMLClipboardExporter", "XMLImpressClipboardExport",
false,
SvXMLExportFlags::OASIS|SvXMLExportFlags::STYLES|SvXMLExportFlags::AUTOSTYLES|SvXMLExportFlags::CONTENT|SvXMLExportFlags::FONTDECLS|SvXMLExportFlags::EMBEDDED
);
diff --git a/xmloff/util/xo.component b/xmloff/util/xo.component
index 33db764c0e91..eb218ca12d21 100644
--- a/xmloff/util/xo.component
+++ b/xmloff/util/xo.component
@@ -64,7 +64,8 @@
constructor="com_sun_star_comp_Draw_XMLExporter_get_implementation">
-
+
[Libreoffice-ux-advise] [Bug 129058] [UX] Repeat shortcut (Ctrl+Shift+Y) is too far for short-finger users using en (qwerty) keyboard
https://bugs.documentfoundation.org/show_bug.cgi?id=129058 --- Comment #4 from Heiko Tietze --- From the design meeting: + I always use TWO hands for that keyboard shortcuts =) (Roman) + keyboard issue for English, see also bug 115052 for other than English + Excel (or all MSO) uses F4 (or ctrl+Y) for "repeat last action" (but the same key also for redo) + shift+ctrl+r? - cannot press it without hurting myself, ctrl+alt+r works + alt+ should be reserved for hotkeys + keep it - common, usable (maybe not for everyone), consistent (Heiko) + more opinions needed (Roman) => keep it boiling for a week -- 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-bugs] [Bug 129058] [UX] Repeat shortcut (Ctrl+Shift+Y) is too far for short-finger users using en (qwerty) keyboard
https://bugs.documentfoundation.org/show_bug.cgi?id=129058 --- Comment #4 from Heiko Tietze --- >From the design meeting: + I always use TWO hands for that keyboard shortcuts =) (Roman) + keyboard issue for English, see also bug 115052 for other than English + Excel (or all MSO) uses F4 (or ctrl+Y) for "repeat last action" (but the same key also for redo) + shift+ctrl+r? - cannot press it without hurting myself, ctrl+alt+r works + alt+ should be reserved for hotkeys + keep it - common, usable (maybe not for everyone), consistent (Heiko) + more opinions needed (Roman) => keep it boiling for a week -- 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 33173] Tabbed UI (Writer): Division/section-per-tab (similar to Lotus WordPro)
https://bugs.documentfoundation.org/show_bug.cgi?id=33173 --- Comment #43 from Heiko Tietze --- No question that we have to improve the Navigator, a proposal is here [1]. But despite all the shortcommings the basic way of dealing with content is working well. From the WYSIWYG point of view I doubt that putting content in tabbed sections is working well for the majority of users. And there are also many requests to have tabs for multiple documents in one app that would clash with your proposal. [1] https://design.blog.documentfoundation.org/2016/07/31/how-the-navigator-may-support-object-handling-in-libreoffice-draw/ -- 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 129221] Numbered bullets don't restart after header in importred .docx file
https://bugs.documentfoundation.org/show_bug.cgi?id=129221 Dieter Praas changed: What|Removed |Added Ever confirmed|0 |1 CC||dgp-m...@gmx.de Status|UNCONFIRMED |NEEDINFO --- Comment #1 from Dieter Praas --- Thank you for reporting the bug. Please attach a sample docx-file, as this makes it easier for us to verify the bug. I have set the bug's status to 'NEEDINFO'. Please change it back to 'UNCONFIRMED' once the requested document is provided. (Please note that the attachment will be public, remove any sensitive information before attaching it) -- 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 99477] EDITING: "View> Freeze Cells> Freeze First..." does not work if the sheet is already frozen
https://bugs.documentfoundation.org/show_bug.cgi?id=99477 Heiko Tietze changed: What|Removed |Added URL|https://www.hpsupportphonen | |umbers.com/how-to-fix-error | |-code-49-4c02/ | -- 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 128912] Document property "Keywords" are exported incorrectly to PDF property (extra quotes)
https://bugs.documentfoundation.org/show_bug.cgi?id=128912 Dieter Praas changed: What|Removed |Added Whiteboard| QA:needsComment| CC||dgp-m...@gmx.de Ever confirmed|0 |1 Status|UNCONFIRMED |NEW Component|Writer |Printing and PDF export --- Comment #1 from Dieter Praas --- I confirm the described behaviour with Version: 6.5.0.0.alpha0+ (x64) Build ID: 89f0af144c18efafe2573801641689a1432c0cae CPU threads: 4; OS: Windows 10.0 Build 18362; UI render: GL; VCL: win; Locale: de-DE (de_DE); UI-Language: en-GB 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 125257] [META] Tip of the day
https://bugs.documentfoundation.org/show_bug.cgi?id=125257 Bug 125257 depends on bug 128712, which changed state. Bug 128712 Summary: Is the explanation clear in tip nr. 14 about selection zooming? https://bugs.documentfoundation.org/show_bug.cgi?id=128712 What|Removed |Added Status|ASSIGNED|RESOLVED Resolution|--- |FIXED -- 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: cui/inc
cui/inc/tipoftheday.hrc |5 -
1 file changed, 4 insertions(+), 1 deletion(-)
New commits:
commit 6e70a98b15c97ad2a3714aae5a5bfa22d307f236
Author: Seth Chaiklin
AuthorDate: Sun Dec 1 18:25:00 2019 +0200
Commit: Heiko Tietze
CommitDate: Fri Dec 6 08:27:21 2019 +0100
tdf#128712 clarification and addition of Draw tips
Split one tip into two different tips.
Added two more Draw tips
Change-Id: Idbb9b5ba0c136a8cb110eb8b7ed8f8d2855c9221
Reviewed-on: https://gerrit.libreoffice.org/84161
Tested-by: Jenkins
Reviewed-by: Heiko Tietze
diff --git a/cui/inc/tipoftheday.hrc b/cui/inc/tipoftheday.hrc
index 602e1755ef01..ab279e6393ad 100644
--- a/cui/inc/tipoftheday.hrc
+++ b/cui/inc/tipoftheday.hrc
@@ -57,7 +57,7 @@ const std::tuple
TIPOFTHEDAY_STRINGARRAY[] =
{ NC_("RID_CUI_TIPOFTHEDAY", "You can display a number as a fraction
(0.125 = 1/8): Format > Cells, Number > Fraction."), "", "tipoftheday_c.png"},
{ NC_("RID_CUI_TIPOFTHEDAY", "To remove a hyperlink but keep its text,
right-click on the hyperlink, and use 'Remove Hyperlink'."), "",
"tipoftheday_w.png"},
{ NC_("RID_CUI_TIPOFTHEDAY", "To remove several hyperlinks at once,
select the text with the hyperlinks, then right-click and use ‘Remove
Hyperlink’."), "", "tipoftheday_w.png"},
- { NC_("RID_CUI_TIPOFTHEDAY", "To quickly zoom in the selection, press /
(divide key) on the number pad. Press * to restore entire page in screen."),
"", "tipoftheday_d.png"},
+ { NC_("RID_CUI_TIPOFTHEDAY", "To zoom a selection to fit the entire
window in Draw, use the / (divide key) on the number pad."), "",
"tipoftheday_d.png"},
{ NC_("RID_CUI_TIPOFTHEDAY", "Click a column field (row) PivotTable and
press F12 to group data. Choices adapt to content: Date (month, quarter, year),
number (classes)"), "", "tipoftheday_c.png"},
{ NC_("RID_CUI_TIPOFTHEDAY", "You can restarts the slide show after a
pause specified at Slide Show > Slide Show Settings > Loop and repeat."), "",
"tipoftheday_i.png"},
{ NC_("RID_CUI_TIPOFTHEDAY", "To distribute some text in multi-columns
select the text and apply Format > Columns."), "", "tipoftheday_w.png"},
@@ -65,6 +65,8 @@ const std::tuple
TIPOFTHEDAY_STRINGARRAY[] =
{ NC_("RID_CUI_TIPOFTHEDAY", "Create different master pages in a
presentation template: View > Master Slide and Slide > New Master (or per
toolbar or right click in slide pane)."), "", "tipoftheday_i.png"},
{ NC_("RID_CUI_TIPOFTHEDAY", "Want to sort a pivot table? Click on
drop-list's arrow in the row/col header and select sort method: ascending,
descending, or custom."), "", "tipoftheday_c.png"},
{ NC_("RID_CUI_TIPOFTHEDAY", "Use Page/Slide > Properties > 'Fit object
to paper format' in Draw/Impress to resize the objects so that they fit on your
chosen paper format."), "", "tipoftheday_d.png"},
+ { NC_("RID_CUI_TIPOFTHEDAY", "Fit the entire page in a Draw window, use *
on the number pad."), "", "tipoftheday_d.png"},
+ { NC_("RID_CUI_TIPOFTHEDAY", "In a Draw page, use '-' to zoom out; '+' to
zoom in."), "", "tipoftheday_d.png"},
{ NC_("RID_CUI_TIPOFTHEDAY", "To automatically number your table rows in
Writer, select the relevant column, then apply a numbering style from List
Styles."), "", "tipoftheday_w.png"},
{ NC_("RID_CUI_TIPOFTHEDAY", "%PRODUCTNAME allows you to use assistive
tools, such as external screen readers, Braille devices or speech recognition
input devices."), "https://www.libreoffice.org/get-help/accessibility/;, ""},
{ NC_("RID_CUI_TIPOFTHEDAY", "Want to sort a series in %PRODUCTNAME Calc
such as A1, A2, A3, A11, A15, not in alphabetical order but on the number?
Enable natural sort in the Options tab."),
"modules/scalc/ui/sortoptionspage/SortOptionsPage", "tipoftheday_c.png"},
//https://help.libreoffice.org/%PRODUCTVERSION/%LANGUAGENAME/text/scalc/01/12030200.html
@@ -88,6 +90,7 @@ const std::tuple
TIPOFTHEDAY_STRINGARRAY[] =
{ NC_("RID_CUI_TIPOFTHEDAY", "Want to count words for just one particular
paragraph style? Use Edit > Find & Replace > Paragraph Styles, select the style
> Find All and read the number from the status bar."), "", "tipoftheday_w.png"},
{ NC_("RID_CUI_TIPOFTHEDAY", "Generate fully customized PDF documents
with the exact format, image compression, comments, access rights, password,
etc., via File > Export as PDF."), "", ""},
{ NC_("RID_CUI_TIPOFTHEDAY", "Writer includes LibreLogo: simple Logo-like
programming environment with turtle vector graphics, DTP and graphic design."),
"https://help.libreoffice.org/%PRODUCTVERSION/%LANGUAGENAME/text/swriter/librelogo/LibreLogo.html;,
"tipoftheday_w.png"}, //local help missing
+ { NC_("RID_CUI_TIPOFTHEDAY", "Construct your own 2D shapes in Draw.
Select two or more objects, and explore possibilities with Shape > Combine,
Shape > Merge, Shape > Subtract, and Shape > Intersect."),
[Libreoffice-bugs] [Bug 126754] FONT FEATURES DIALOG: Wrong OpenType tag for fractions in "font features" dialog
https://bugs.documentfoundation.org/show_bug.cgi?id=126754 Dieter Praas changed: What|Removed |Added Ever confirmed|0 |1 Status|UNCONFIRMED |NEW --- Comment #4 from Dieter Praas --- (In reply to Tobias Hemm from comment #3) > What RGB stated is absolutely correct. => Status 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 129215] PDF Hyperlink in writer not resolving.
https://bugs.documentfoundation.org/show_bug.cgi?id=129215 Dieter Praas changed: What|Removed |Added CC||dgp-m...@gmx.de Status|UNCONFIRMED |NEEDINFO Ever confirmed|0 |1 --- Comment #1 from Dieter Praas --- Steve, thank you for reporting the bug. Could you please a) try to reproduce it with the latest version of LibreOffice from https://www.libreoffice.org/download/libreoffice-fresh/ ? and (if this doesn't solve your problem) b) provide a clearer set of step-by-step instructions on how to reproduce the problem or add a sample document. Please change it back to 'UNCONFIRMED' if the bug is still present in the latest version. Change to RESOLVED WORKSFORME, if the problem went away. -- 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 'libreoffice-6-4' - vcl/uiconfig
vcl/uiconfig/ui/printdialog.ui |6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) New commits: commit 30912c4953b18bd47ef870aa7edcd2847e702934 Author: Heiko Tietze AuthorDate: Thu Dec 5 16:17:02 2019 +0100 Commit: Heiko Tietze CommitDate: Fri Dec 6 08:22:44 2019 +0100 Resolves tdf#129140 - Wording in printer dialog Wording improved Change-Id: I67fcee9bdae869eb57882b1944e8975d4c564735 Reviewed-on: https://gerrit.libreoffice.org/84572 Tested-by: Jenkins Reviewed-by: Heiko Tietze (cherry picked from commit 291b1acd3b9664ed41954458648448d7799d4df9) Reviewed-on: https://gerrit.libreoffice.org/84590 diff --git a/vcl/uiconfig/ui/printdialog.ui b/vcl/uiconfig/ui/printdialog.ui index 1822f688a1c9..215e7d82f686 100644 --- a/vcl/uiconfig/ui/printdialog.ui +++ b/vcl/uiconfig/ui/printdialog.ui @@ -619,9 +619,9 @@ False True - Print only in one side - Print in both sides (long edge) - Print in both sides (short edge) + Print on one side (simplex) + Print on both sides (duplex long edge) + Print on both sides (duplex short edge) ___ Libreoffice-commits mailing list libreoffice-comm...@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-commits
[Libreoffice-bugs] [Bug 127472] Translation error: The German word "Datenbank" is not equivalent to "date base"
https://bugs.documentfoundation.org/show_bug.cgi?id=127472 --- Comment #3 from Dieter Praas --- (In reply to Julien Nabet from comment #2) > Dieter/Andreas/Sophia/Thomas: any thoughts about a correct translation here? I prefer "Basisdatum": It's close to the English word and it's meaning is clear within the specific context. -- 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 127305] Auto-fill QR Code dialog Box for selected text from the document
https://bugs.documentfoundation.org/show_bug.cgi?id=127305 Commit Notification changed: What|Removed |Added Whiteboard||target:6.5.0 -- 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 'libreoffice-6-4' - 2 commits - editeng/source include/editeng sc/source sd/source sw/source
editeng/source/misc/urlfieldhelper.cxx | 28 +---
include/editeng/urlfieldhelper.hxx |5 +++--
sc/source/ui/drawfunc/drtxtob.cxx |6 ++
sc/source/ui/view/editsh.cxx | 17 +
sd/source/ui/view/drviews2.cxx |3 +--
sd/source/ui/view/drviews7.cxx | 15 +++
sd/source/ui/view/drviewsf.cxx |2 +-
sw/source/uibase/shells/drwtxtex.cxx |7 ++-
8 files changed, 34 insertions(+), 49 deletions(-)
New commits:
commit f7d4d2a7a824801796c54debaf70c6e0efb76a89
Author: Samuel Mehrbrodt
AuthorDate: Thu Dec 5 09:58:10 2019 +0100
Commit: Samuel Mehrbrodt
CommitDate: Fri Dec 6 08:17:40 2019 +0100
Fix "Open Hyperlink" context menu in sc
Change-Id: I05fce087d20123447c1e5bd0f27db8d1c9ef3641
Reviewed-on: https://gerrit.libreoffice.org/84518
Tested-by: Jenkins
Reviewed-by: Samuel Mehrbrodt
(cherry picked from commit 069a45e661086d1014855ca4f7ad384ba5752bb6)
Reviewed-on: https://gerrit.libreoffice.org/84577
diff --git a/sc/source/ui/view/editsh.cxx b/sc/source/ui/view/editsh.cxx
index 80a7bf1cdea2..61888c663ef4 100644
--- a/sc/source/ui/view/editsh.cxx
+++ b/sc/source/ui/view/editsh.cxx
@@ -623,7 +623,7 @@ void ScEditShell::Execute( SfxRequest& rReq )
{
const SvxURLField* pURLField = GetURLField();
if ( pURLField )
-ScGlobal::OpenURL( pURLField->GetURL(),
pURLField->GetTargetFrame() );
+ScGlobal::OpenURL( pURLField->GetURL(),
pURLField->GetTargetFrame(), true );
return;
}
case SID_EDIT_HYPERLINK:
commit 64233bbaa0e91ddf14d59ae7547df6bbfa60adcc
Author: Samuel Mehrbrodt
AuthorDate: Wed Dec 4 15:19:00 2019 +0100
Commit: Samuel Mehrbrodt
CommitDate: Fri Dec 6 08:17:10 2019 +0100
tdf#128666 Only enable hyperlink actions when just the field is selected
Change-Id: I984df967877a47fb9f89c3626737348a87d3ffa5
Reviewed-on: https://gerrit.libreoffice.org/84418
Tested-by: Jenkins
Reviewed-by: Samuel Mehrbrodt
(cherry picked from commit f31c3ebb60e4678eb09e377b638b368531df47dc)
Reviewed-on: https://gerrit.libreoffice.org/84571
diff --git a/editeng/source/misc/urlfieldhelper.cxx
b/editeng/source/misc/urlfieldhelper.cxx
index 6df7171e14c0..564bc54e781e 100644
--- a/editeng/source/misc/urlfieldhelper.cxx
+++ b/editeng/source/misc/urlfieldhelper.cxx
@@ -11,27 +11,33 @@
#include
#include
+#include
-void URLFieldHelper::RemoveURLField(Outliner* pOutl, const OutlinerView* pOLV)
+void URLFieldHelper::RemoveURLField(EditView& pEditView)
{
-if (!pOutl || !pOLV)
-return;
-
-const SvxFieldData* pField = pOLV->GetFieldAtCursor();
+pEditView.SelectFieldAtCursor();
+const SvxFieldData* pField = pEditView.GetFieldAtCursor();
if (auto pUrlField = dynamic_cast(pField))
{
-ESelection aSel = pOLV->GetSelection();
-pOutl->QuickInsertText(pUrlField->GetRepresentation(), aSel);
-pOLV->GetEditView().Invalidate();
+ESelection aSel = pEditView.GetSelection();
+
pEditView.GetEditEngine()->QuickInsertText(pUrlField->GetRepresentation(),
aSel);
+pEditView.Invalidate();
}
}
-bool URLFieldHelper::IsCursorAtURLField(const OutlinerView* pOLV)
+bool URLFieldHelper::IsCursorAtURLField(const EditView& pEditView)
{
-if (!pOLV)
+// tdf#128666 Make sure only URL field (or nothing) is selected
+ESelection aSel = pEditView.GetSelection();
+auto nSelectedParas = aSel.nEndPara - aSel.nStartPara;
+auto nSelectedChars = aSel.nEndPos - aSel.nStartPos;
+bool bIsValidSelection
+= nSelectedParas == 0
+ && (nSelectedChars == 0 || nSelectedChars == 1 || nSelectedChars ==
-1);
+if (!bIsValidSelection)
return false;
-const SvxFieldData* pField = pOLV->GetFieldAtCursor();
+const SvxFieldData* pField = pEditView.GetFieldAtCursor();
if (dynamic_cast(pField))
return true;
diff --git a/include/editeng/urlfieldhelper.hxx
b/include/editeng/urlfieldhelper.hxx
index 547e2654ea9b..e6c7c92935a4 100644
--- a/include/editeng/urlfieldhelper.hxx
+++ b/include/editeng/urlfieldhelper.hxx
@@ -12,12 +12,13 @@
#include
#include
#include
+#include
class EDITENG_DLLPUBLIC URLFieldHelper
{
public:
-static void RemoveURLField(Outliner* pOutl, const OutlinerView* pOLV);
-static bool IsCursorAtURLField(const OutlinerView* pOLV);
+static void RemoveURLField(EditView& pEditView);
+static bool IsCursorAtURLField(const EditView& pEditView);
};
/* vim:set shiftwidth=4 softtabstop=4 expandtab cinoptions=b1,g0,N-s
cinkeys+=0=break: */
diff --git a/sc/source/ui/drawfunc/drtxtob.cxx
b/sc/source/ui/drawfunc/drtxtob.cxx
index daf58d072eea..6cc27d4368c3 100644
--- a/sc/source/ui/drawfunc/drtxtob.cxx
+++ b/sc/source/ui/drawfunc/drtxtob.cxx
@@ -326,8
[Libreoffice-bugs] [Bug 127305] Auto-fill QR Code dialog Box for selected text from the document
https://bugs.documentfoundation.org/show_bug.cgi?id=127305 --- Comment #2 from Commit Notification --- shubham goyal committed a patch related to this issue. It has been pushed to "master": https://git.libreoffice.org/core/commit/704a558b8689beb1a83a3e2d21481e0ea118e134 tdf#127305 display selected text in URL field QR Code Dialog It will be available in 6.5.0. The patch should be included in the daily builds available at https://dev-builds.libreoffice.org/daily/ in the next 24-48 hours. More information about daily builds can be found at: https://wiki.documentfoundation.org/Testing_Daily_Builds Affected users are encouraged to test the fix and report feedback. -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-commits] core.git: cui/source
cui/source/dialogs/QrCodeGenDialog.cxx |8
1 file changed, 8 insertions(+)
New commits:
commit 704a558b8689beb1a83a3e2d21481e0ea118e134
Author: shubham goyal <22shub...@gmail.com>
AuthorDate: Fri Sep 13 18:23:51 2019 +0200
Commit: Samuel Mehrbrodt
CommitDate: Fri Dec 6 08:16:40 2019 +0100
tdf#127305 display selected text in URL field QR Code Dialog
Change-Id: Ic0d36225cc2c509c706a4599d45b92c6b9fea40e
Reviewed-on: https://gerrit.libreoffice.org/78879
Tested-by: Jenkins
Reviewed-by: Samuel Mehrbrodt
diff --git a/cui/source/dialogs/QrCodeGenDialog.cxx
b/cui/source/dialogs/QrCodeGenDialog.cxx
index 7bd72ff0fc1c..d936219f7209 100644
--- a/cui/source/dialogs/QrCodeGenDialog.cxx
+++ b/cui/source/dialogs/QrCodeGenDialog.cxx
@@ -73,6 +73,14 @@ QrCodeGenDialog::QrCodeGenDialog(weld::Widget* pParent,
Reference xModel
{
if (!bEditExisting)
{
+// TODO: This only works in Writer doc. Should also work in shapes
+Reference xSelections(m_xModel->getCurrentSelection(),
UNO_QUERY);
+if (xSelections.is())
+{
+Reference xSelection(xSelections->getByIndex(0),
UNO_QUERY);
+if (xSelection.is())
+m_xEdittext->set_text(xSelection->getString());
+}
return;
}
___
Libreoffice-commits mailing list
libreoffice-comm...@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice-commits
[Libreoffice-commits] core.git: sax/source
sax/source/tools/fastserializer.cxx | 11 +++
1 file changed, 7 insertions(+), 4 deletions(-)
New commits:
commit 579db0d2d3d2ddf5a5f8feaa2e7cc4dde81d7701
Author: László Németh
AuthorDate: Thu Dec 5 11:42:59 2019 +0100
Commit: László Németh
CommitDate: Fri Dec 6 08:10:51 2019 +0100
cleanup "tdf#117274 XLSX export: fix VML comment shape type id"
Limit special MSO ID check for attribute values.
Follow-up of commit c5d37d324cd6d17114c209de1862344ad58a1d93.
Change-Id: I0f16b0df0c5575b799bb505a93c660c15b3273c5
Reviewed-on: https://gerrit.libreoffice.org/84549
Tested-by: Jenkins
Reviewed-by: László Németh
diff --git a/sax/source/tools/fastserializer.cxx
b/sax/source/tools/fastserializer.cxx
index cc7293a6a3f9..a362ff438383 100644
--- a/sax/source/tools/fastserializer.cxx
+++ b/sax/source/tools/fastserializer.cxx
@@ -130,9 +130,7 @@ namespace sax_fastparser {
if (nLen == -1)
nLen = pStr ? strlen(pStr) : 0;
-if ( !bEscape ||
-// tdf#127274 don't escape the special VML shape type id
"#_x_t202"
-(pStr && strcmp(pStr, "#_x_t202") == 0) )
+if (!bEscape)
{
writeBytes( pStr, nLen );
return;
@@ -465,7 +463,12 @@ namespace sax_fastparser {
writeBytes(sEqualSignAndQuote, N_CHARS(sEqualSignAndQuote));
-write(rAttrList.getFastAttributeValue(j),
rAttrList.AttributeValueLength(j), true);
+const char* pAttributeValue = rAttrList.getFastAttributeValue(j);
+
+// tdf#127274 don't escape the special VML shape type id
"#_x_t202"
+bool bEscape = !(pAttributeValue && strcmp(pAttributeValue,
"#_x_t202") == 0);
+
+write(pAttributeValue, rAttrList.AttributeValueLength(j), bEscape);
writeBytes(sQuote, N_CHARS(sQuote));
}
___
Libreoffice-commits mailing list
libreoffice-comm...@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice-commits
[Libreoffice-bugs] [Bug 127022] menu bar is broken in RTL interface on Windows
https://bugs.documentfoundation.org/show_bug.cgi?id=127022 Boaz Dodin changed: What|Removed |Added Keywords||regression -- 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: Changes to 'feature/accessibilitycheck'
New branch 'feature/accessibilitycheck' available with the following commits: commit d513b0acb2083160025dee85ce31c0fee15a251e Author: Tomaž Vajngerl Date: Thu Dec 5 22:24:49 2019 +0100 accessibility check dialog This adds the accessibility check dialog which is responsible to show all the accessibility check issues in the current document. Currently this just shows the text message in a list that comes from AccessibilityCheck. Change-Id: I8fd27038e3d85cd31fe172eee5e391fd4b7243ae commit 97df8a92b5955bd6f811e8b89f8e93d6b9c6b98b Author: Tomaž Vajngerl Date: Thu Dec 5 22:04:35 2019 +0100 accessibility check base functionality This adds AccessibilityCheck class to writer, which perfors the accessibility check of the current document to make the document conform to PDF/UA requirements. The first check this adds is check for the "alt" (sometimes also called "title") to be present for graphics, OLE objects (charts) and shapes. Change-Id: I98dcca787099bdb17cab9291546074cdde2ae5a8 commit b6f9f668790c63b52da03589573e35b9d9452f58 Author: Tomaž Vajngerl Date: Sun Dec 1 11:00:28 2019 +0100 Add accessibility check to the Writer menu Change-Id: I7e4c3267288b238583822489c8098e64319dda16 ___ Libreoffice-commits mailing list libreoffice-comm...@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-commits
[Libreoffice-bugs] [Bug 99477] EDITING: "View> Freeze Cells> Freeze First..." does not work if the sheet is already frozen
https://bugs.documentfoundation.org/show_bug.cgi?id=99477 Ronan Smith changed: What|Removed |Added URL||https://www.hpsupportphonen ||umbers.com/how-to-fix-error ||-code-49-4c02/ --- Comment #27 from Ronan Smith --- The post is informative and the topic is discussed is really good keep on sharing new things. If you facing any problem regarding of HP Error 49.4 c02 visite our website click here https://www.hpsupportphonenumbers.com/how-to-fix-error-code-49-4c02/ -- 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 128466] Not possible to paste a picture from the clipboard in a spreadsheet in calc on iOS
https://bugs.documentfoundation.org/show_bug.cgi?id=128466 --- Comment #5 from Commit Notification --- Tor Lillqvist committed a patch related to this issue. It has been pushed to "libreoffice-6-4": https://git.libreoffice.org/core/commit/c45acdcdd022a17559b9f7b85790c656a1599339 tdf#128466: Accept also JPEG It will be available in 6.4.0.1. The patch should be included in the daily builds available at https://dev-builds.libreoffice.org/daily/ in the next 24-48 hours. More information about daily builds can be found at: https://wiki.documentfoundation.org/Testing_Daily_Builds Affected users are encouraged to test the fix and report feedback. -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 128466] Not possible to paste a picture from the clipboard in a spreadsheet in calc on iOS
https://bugs.documentfoundation.org/show_bug.cgi?id=128466 Commit Notification changed: What|Removed |Added Whiteboard|target:6.5.0|target:6.5.0 target:6.4.0.1 -- 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 'libreoffice-6-4' - sc/source
sc/source/ui/view/viewfun5.cxx |2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
New commits:
commit c45acdcdd022a17559b9f7b85790c656a1599339
Author: Tor Lillqvist
AuthorDate: Wed Nov 13 13:30:43 2019 +0200
Commit: Tor Lillqvist
CommitDate: Fri Dec 6 07:18:55 2019 +0100
tdf#128466: Accept also JPEG
Change-Id: If8499cde875e03cb6c56259badd64ba6aee08a66
Reviewed-on: https://gerrit.libreoffice.org/82584
Reviewed-by: Tor Lillqvist
Tested-by: Tor Lillqvist
(cherry picked from commit 7dba640b5691c22d6529e53752255fddc2b461e6)
Reviewed-on: https://gerrit.libreoffice.org/82618
Tested-by: Jenkins
(cherry picked from commit 3adb591bc632854dc9f0af0c8498ae45171080a7)
Reviewed-on: https://gerrit.libreoffice.org/84524
diff --git a/sc/source/ui/view/viewfun5.cxx b/sc/source/ui/view/viewfun5.cxx
index cdac007fc8df..0e61a2a8a072 100644
--- a/sc/source/ui/view/viewfun5.cxx
+++ b/sc/source/ui/view/viewfun5.cxx
@@ -482,7 +482,7 @@ bool ScViewFunc::PasteDataFormat( SotClipboardFormatId
nFormatId,
}
}
}
-else if (nFormatId == SotClipboardFormatId::BITMAP || nFormatId ==
SotClipboardFormatId::PNG)
+else if (nFormatId == SotClipboardFormatId::BITMAP || nFormatId ==
SotClipboardFormatId::PNG || nFormatId == SotClipboardFormatId::JPEG)
{
BitmapEx aBmpEx;
if( aDataHelper.GetBitmapEx( SotClipboardFormatId::BITMAP, aBmpEx ) )
___
Libreoffice-commits mailing list
libreoffice-comm...@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice-commits
[Libreoffice-commits] core.git: vcl/uiconfig
vcl/uiconfig/ui/printdialog.ui |6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) New commits: commit 291b1acd3b9664ed41954458648448d7799d4df9 Author: Heiko Tietze AuthorDate: Thu Dec 5 16:17:02 2019 +0100 Commit: Heiko Tietze CommitDate: Fri Dec 6 07:16:36 2019 +0100 Resolves tdf#129140 - Wording in printer dialog Wording improved Change-Id: I67fcee9bdae869eb57882b1944e8975d4c564735 Reviewed-on: https://gerrit.libreoffice.org/84572 Tested-by: Jenkins Reviewed-by: Heiko Tietze diff --git a/vcl/uiconfig/ui/printdialog.ui b/vcl/uiconfig/ui/printdialog.ui index 1822f688a1c9..215e7d82f686 100644 --- a/vcl/uiconfig/ui/printdialog.ui +++ b/vcl/uiconfig/ui/printdialog.ui @@ -619,9 +619,9 @@ False True - Print only in one side - Print in both sides (long edge) - Print in both sides (short edge) + Print on one side (simplex) + Print on both sides (duplex long edge) + Print on both sides (duplex short edge) ___ Libreoffice-commits mailing list libreoffice-comm...@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-commits
[Libreoffice-bugs] [Bug 129222] New: + transfer data to new tab
https://bugs.documentfoundation.org/show_bug.cgi?id=129222 Bug ID: 129222 Summary: + transfer data to new tab Product: LibreOffice Version: 6.3.2.2 release Hardware: All OS: All Status: UNCONFIRMED Severity: normal Priority: medium Component: Calc Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: toddandma...@zoho.com Dear Libre Office, You do have a Windows version of Calc, so this might be a "Feature, not a "Bug". 1) open a fresh, blank spreadsheet 2) in 1:1 put "one" is a text. Do not click off the cell 3) go to the bottom left and click the "+" sign to get a new division tab. Your text will now be transferred to the new tab and removed from the first. If you click off the cell to save it before clicking the "+" sign, your text stays where it should. So the bug is that clicking the "+" sign should close whatever you have open before creating the new tab. -T -- 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 33173] Tabbed UI (Writer): Division/section-per-tab (similar to Lotus WordPro)
https://bugs.documentfoundation.org/show_bug.cgi?id=33173 --- Comment #42 from Todd --- (In reply to Heiko Tietze from comment #41) > I don't see the advantage over the Navigator [1] or master documents [2]. > Users who are familiar with one kind of interaction may prefer this but > there is no requirement missing, AFAICS. So the suggestion is to not change > what we have (and where other users are familiar with). > And while we have some interest in the topic, it's at the same time quite > old and of less importance for the whole product. So setting back to medium. Heiko, I am the original porter (OP) of this request. I do constantly used both. In my technical opinion, although your are absolutely correct, both do work, your method is a good 10 times more difficult to use and is not as intuitive to the user. Please do not look at this a "we already have a way, don't fix what is not broken", but as "how can we make this more user friendly". If you like doing thing the obscure, difficult way, leave the current method in place as an alternative. You already support tabs in Calc, so add the feature to Writer should be a piece of cake. It would be wonderful if you would institute this request and would EVER fix the envelope printing, then I and others could FINALLY get off the DEFUNCT Word Pro, which works better than Writer and has been dead and unsupported for about 20 years or so. This is what tabs looks like in Calc. Here are two tabs. One is "January" and its 1:1 text is "Month 1"; the second its "February" and its 1:1 text is "Month 02": Month 01 Month 02 You now have an army of folks also requesting this, so it is time it got implemented. Many thanks, -T -- 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 109425] Libreoffice Notebookbar is not exposing accessible events needed for screen reader users.
https://bugs.documentfoundation.org/show_bug.cgi?id=109425 --- Comment #39 from V Stuart Foote --- @Andreas, Jim, * So testing on Windows 10 Home 64-bit en-US with NVDA 2019.2 and todays TB77 Version: 6.5.0.0.alpha0+ (x64) Build ID: 790b5de8941d8f8d98c73ed1343289d7220211ad CPU threads: 4; OS: Windows 10.0 Build 18362; UI render: default; VCL: win; Locale: en-US (en_US); UI-Language: en-US Calc: threaded The additional GTK Focus events have restored reasonable keyboard navigation to the NB, had a few sequencing issues within groupings, but so much closer now. Thanks! But for some reason the focus A11Y 'accessible events' are not fired when advancing through the NB in its nested position in the app frame. But if you reduce the width of the frame, collapsing the NB, the popup bar exposed with the 'chevrons' exposes all of the accessible events. What is different between controls held on the NB, versus the same controls held in the overflow 'chevrons' popup that allows the UNO controls 'accessible event' to fire? And otherwise, continue to have issues with a non-functional F10 & F6 movements when the main menubar is not exposed. Seems too fragile, and prone to losing track of position in the UI. No recovery with keyboard, requiring a blind mouse click into the document canvas to recover focus. -- 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 129221] New: Numbered bullets don't restart after header in importred .docx file
https://bugs.documentfoundation.org/show_bug.cgi?id=129221 Bug ID: 129221 Summary: Numbered bullets don't restart after header in importred .docx file Product: LibreOffice Version: 6.2.7.1 release Hardware: x86-64 (AMD64) OS: Linux (All) Status: UNCONFIRMED Severity: normal Priority: medium Component: Writer Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: u...@flanagan-consulting.com Description: Original Word docx has numbered lists under subheads. Numbering restarts with "1" after each subhead. When opened by LO 6.2.7.1 (from openSuSe) the list numbering continues through the subheads and does not restart at "1" each time. Saving file as .odt preserves this error. Steps to Reproduce: 1. Open .docx file 2. Numbered lists continue through subheads 3. Actual Results: Numbered lists do not restart at "1" after subhead Expected Results: Numbered lists start with "1" after a header. Reproducible: Always User Profile Reset: Yes Additional Info: Have seen his file display by Word and numbering restarts after headers. Version: 6.2.7.1 Build ID: 20(Build:1) CPU threads: 12; OS: Linux 4.12; UI render: default; VCL: kde5; Locale: en-US (en_US.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 58941] Support enabling optional smart font features
https://bugs.documentfoundation.org/show_bug.cgi?id=58941 V Stuart Foote changed: What|Removed |Added See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=12 ||9219 -- 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 71732] [META] Bugs related to text rendering, typography and font features in LO
https://bugs.documentfoundation.org/show_bug.cgi?id=71732 V Stuart Foote changed: What|Removed |Added Depends on||129219 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=129219 [Bug 129219] Further refinement of OpenType/Graphite Font features in the “Character” dialogue -- 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 129219] Further refinement of OpenType/Graphite Font features in the “Character” dialogue
https://bugs.documentfoundation.org/show_bug.cgi?id=129219 V Stuart Foote changed: What|Removed |Added CC||dr.khaled.ho...@gmail.com, ||heiko.tietze@documentfounda ||tion.org, ||martin_hos...@sil.org, ||qui...@gmail.com, ||vstuart.fo...@utsa.edu Status|UNCONFIRMED |NEW See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=58 ||941 Summary|Different Implementation of |Further refinement of |OpenType Font Features in |OpenType/Graphite Font |the “Character” Dialogue|features in the “Character” ||dialogue Blocks||71732 Version|6.2.8.2 release |6.2.0.3 release Ever confirmed|0 |1 --- Comment #3 from V Stuart Foote --- The work referred to was done for bug 58941 Example panels from other applications for handling OpenType features, and some relevant discussion of technical limitations of current Graphite modeled solution implemented with HarfBuzz libs. But sure, probably room for additional refinement of the GUI. @Hieko, should this go through additional UX/Design work-up? Or, just leave it to our sage devs... Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=71732 [Bug 71732] [META] Bugs related to text rendering, typography and font features in LO -- 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 129212] Hints is not word wrapped into the hint window
https://bugs.documentfoundation.org/show_bug.cgi?id=129212 V Stuart Foote changed: What|Removed |Added Resolution|--- |DUPLICATE Status|UNCONFIRMED |RESOLVED CC||vstuart.fo...@utsa.edu --- Comment #1 from V Stuart Foote --- fixed for 6.3.4 release *** This bug has been marked as a duplicate of bug 128524 *** -- 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 113050] FILEOPEN: PDF freezes Draw, 46-pages, 1.2 MB, created by Distiller
https://bugs.documentfoundation.org/show_bug.cgi?id=113050 --- Comment #9 from QA Administrators --- Dear Mike, 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 101674] FILEOPEN PDF Massive low performance trying to make simple edits on a complex, one page PDF
https://bugs.documentfoundation.org/show_bug.cgi?id=101674 --- Comment #6 from QA Administrators --- Dear E.Mi, 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 119873] Useless padding in video object
https://bugs.documentfoundation.org/show_bug.cgi?id=119873 --- Comment #6 from QA Administrators --- Dear Ingo von Borstel, 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 121211] IMPORT: Calc range 'table definition only option selected' fails to create table
https://bugs.documentfoundation.org/show_bug.cgi?id=121211 --- Comment #8 from QA Administrators --- Dear Robert Großkopf, 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 121756] Empty area under embedded table after redo (disappearing after clicking into the embedded table)
https://bugs.documentfoundation.org/show_bug.cgi?id=121756 --- Comment #5 from QA Administrators --- Dear Telesto, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from 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 121210] IMPORT: No possibility to set Auto Value to a Integer Primary Key when importing Calc range
https://bugs.documentfoundation.org/show_bug.cgi?id=121210 --- Comment #14 from QA Administrators --- Dear Robert Großkopf, 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 89887] FileOpen: Drawing is not visible in DOCX file
https://bugs.documentfoundation.org/show_bug.cgi?id=89887 --- Comment #10 from QA Administrators --- Dear Sergey Kozyr, 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 128843] enhancement: if text is already in a section, ask for confirmation before linking a file in the section
https://bugs.documentfoundation.org/show_bug.cgi?id=128843 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 128942] Remove frame around rotation wheel within Position and Size / Ratation dialog
https://bugs.documentfoundation.org/show_bug.cgi?id=128942 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 121557] Printing document with frame and controls
https://bugs.documentfoundation.org/show_bug.cgi?id=121557 --- Comment #4 from QA Administrators --- Dear libreoffice, 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 61424] CONFIGURATION: Normal view not possible with custom short cut key
https://bugs.documentfoundation.org/show_bug.cgi?id=61424 --- Comment #24 from QA Administrators --- Dear bugquestcontri, 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 121209] TABLEWIZARD: Field type isn't correctly recognized for Integer and Boolean using automatic field type recognition
https://bugs.documentfoundation.org/show_bug.cgi?id=121209 --- Comment #6 from QA Administrators --- Dear Robert Großkopf, 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 121526] DOCX Import Textbox inserted in header created with Word moves down in Writer
https://bugs.documentfoundation.org/show_bug.cgi?id=121526 --- Comment #5 from QA Administrators --- Dear NISZ LibreOffice Team, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from 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 120978] dxf file missing text
https://bugs.documentfoundation.org/show_bug.cgi?id=120978 --- Comment #5 from QA Administrators --- Dear david chen, 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 121524] DOCX Import 5cm high Footer created with Word become disabled in Writer
https://bugs.documentfoundation.org/show_bug.cgi?id=121524 --- Comment #5 from QA Administrators --- Dear NISZ LibreOffice Team, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from 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 121834] FILEOPEN DOCX Word Header looks different in Writer
https://bugs.documentfoundation.org/show_bug.cgi?id=121834 --- Comment #5 from QA Administrators --- Dear Ettore Atalan, 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 119662] FILEOPEN PPTX embed EMF picture not displayed correctly
https://bugs.documentfoundation.org/show_bug.cgi?id=119662 --- Comment #7 from QA Administrators --- Dear zyl, 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 52234] EDITING: Mouse pointer does not change timely to "move view" when drag modus changes to "without shadow"
https://bugs.documentfoundation.org/show_bug.cgi?id=52234 --- Comment #22 from QA Administrators --- Dear sunmoon51, 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 120722] Handles are not scaled properly on higher resolutions
https://bugs.documentfoundation.org/show_bug.cgi?id=120722 --- Comment #32 from QA Administrators --- Dear 和尚蟹, 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 121548] 100% CPU usage after opening certain DOCX files
https://bugs.documentfoundation.org/show_bug.cgi?id=121548 --- Comment #7 from QA Administrators --- Dear vsza+tdf, 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 120634] Unexpected change of table content paragraph style when deleting a row
https://bugs.documentfoundation.org/show_bug.cgi?id=120634 --- Comment #7 from QA Administrators --- Dear Ulrich Gemkow, 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 120418] LibreOffice Base -> Set toolbar view, then switch between options -> Toolbar view returns to the original settings
https://bugs.documentfoundation.org/show_bug.cgi?id=120418 --- Comment #12 from QA Administrators --- Dear Vera Blagoveschenskaya, 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 96324] Subscript missing in exported SVG (see comment 10)
https://bugs.documentfoundation.org/show_bug.cgi?id=96324 --- Comment #19 from QA Administrators --- Dear u.fuchs, 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 129157] there is a defect in the login page
https://bugs.documentfoundation.org/show_bug.cgi?id=129157 --- Comment #2 from David Bowie --- Pretty great post. I just stumbled upon your blog and wanted to say that I’ve truly loved browsing your blog posts. http://thecomplaintpoint-au.com/lg-complaints-email-phone-number -- 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 87720] Default insert image anchor, wrapping, and spacing
https://bugs.documentfoundation.org/show_bug.cgi?id=87720 --- Comment #37 from Aron Budea --- (In reply to Aron Budea from comment #36) > Good catch, this has actually been set to "To Character" on master since, > because of the very annoying bug 87719. The commit should be backported to > 6.4, because it was introduced after branching 6.4. And now it is: https://cgit.freedesktop.org/libreoffice/core/commit/?h=libreoffice-6-4=d0aa2dbdf37aefe5b8d096fc5ea50cd13f87c5b0 -- 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-bugs] [Bug 87720] Default insert image anchor, wrapping, and spacing
https://bugs.documentfoundation.org/show_bug.cgi?id=87720 --- Comment #37 from Aron Budea --- (In reply to Aron Budea from comment #36) > Good catch, this has actually been set to "To Character" on master since, > because of the very annoying bug 87719. The commit should be backported to > 6.4, because it was introduced after branching 6.4. And now it is: https://cgit.freedesktop.org/libreoffice/core/commit/?h=libreoffice-6-4=d0aa2dbdf37aefe5b8d096fc5ea50cd13f87c5b0 -- 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 129190] PIVOT CHARTS do not survive round-trip with flat ODS
https://bugs.documentfoundation.org/show_bug.cgi?id=129190 m.a.riosv changed: What|Removed |Added OS|Linux (All) |All -- 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 123408] the sum of this selection is wrong, an offset of 1/100.
https://bugs.documentfoundation.org/show_bug.cgi?id=123408 m.a.riosv changed: What|Removed |Added CC||andrew...@biagionelli.com --- Comment #4 from m.a.riosv --- *** Bug 129220 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 129220] I'm getting a repeatable error with the SUM() function
https://bugs.documentfoundation.org/show_bug.cgi?id=129220 m.a.riosv changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED CC||miguelangelrv@libreoffice.o ||rg Resolution|--- |DUPLICATE --- Comment #2 from m.a.riosv --- *** This bug has been marked as a duplicate of bug 123408 *** -- 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 129127] Crash when sort by column of Excel 97-2003 file with specific data
https://bugs.documentfoundation.org/show_bug.cgi?id=129127 Terrence Enger changed: What|Removed |Added CC||lo_b...@iseries-guru.com --- Comment #9 from Terrence Enger --- Working on debian-buster with a local build of commit 9ab43aeb, 2019-12-04, I reproduce Julien's SIGSEGV. However in bibisect-linux-64-6.5 commit 4bea6716 s-h 304368c7, I merely get an incorrect sort: naming columns by the original positions: expected : B A C E D observed : A B C E D -- 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 100603] Spreadsheet not calculating properly, sum() not updated with auto-calculate or [f9]; hard-recalc needed
https://bugs.documentfoundation.org/show_bug.cgi?id=100603 m.a.riosv changed: What|Removed |Added Status|NEW |RESOLVED Resolution|--- |WORKSFORME --- Comment #5 from m.a.riosv --- Works for me. Version: 6.5.0.0.alpha0+ (x64) Build ID: 60e8941fd581bb06cbf6be62edb8c387e7c07812 CPU threads: 4; OS: Windows 10.0 Build 19035; UI render: default; VCL: win; Locale: es-ES (es_ES); UI-Language: en-US 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 129216] Converting from DOC to DOCX should strip macros.
https://bugs.documentfoundation.org/show_bug.cgi?id=129216 Aron Budea changed: What|Removed |Added Resolution|--- |DUPLICATE Status|UNCONFIRMED |RESOLVED --- Comment #1 from Aron Budea --- Bug 108269's fix enabled roundtripping macros. Bug 125338 has been opened about macros persisting when saved from DOCM to DOCX, I have added the DOC case there as well, let's close this as dupe. *** This bug has been marked as a duplicate of bug 125338 *** -- 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 125338] Saving DOC(M) as DOCX doesn't get rid of macro
https://bugs.documentfoundation.org/show_bug.cgi?id=125338 Aron Budea changed: What|Removed |Added CC||dcnel...@zixcorp.com --- Comment #6 from Aron Budea --- *** Bug 129216 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 97791] Calc:: Copying formulas DIVIDES prior combined Cells
https://bugs.documentfoundation.org/show_bug.cgi?id=97791 m.a.riosv changed: What|Removed |Added Resolution|--- |NOTABUG Status|NEW |RESOLVED --- Comment #4 from m.a.riosv --- I'm remain thinking not a bug, if we paste, we also past the cell format, so looks fine breaking the merged. Reinforcing this idea, using context menu to past the formula doesn't modify merged for destination cells. -- 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 108253] [META] Calc cell formula bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=108253 Bug 108253 depends on bug 97791, which changed state. Bug 97791 Summary: Calc:: Copying formulas DIVIDES prior combined Cells https://bugs.documentfoundation.org/show_bug.cgi?id=97791 What|Removed |Added Status|NEW |RESOLVED Resolution|--- |NOTABUG -- 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 108364] [META] Table/Row/Column/Cell management function bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=108364 Bug 108364 depends on bug 97791, which changed state. Bug 97791 Summary: Calc:: Copying formulas DIVIDES prior combined Cells https://bugs.documentfoundation.org/show_bug.cgi?id=97791 What|Removed |Added Status|NEW |RESOLVED Resolution|--- |NOTABUG -- 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 125338] Saving DOC(M) as DOCX doesn't get rid of macro
https://bugs.documentfoundation.org/show_bug.cgi?id=125338 Aron Budea changed: What|Removed |Added Summary|Saving DOCM as DOCX doesn't |Saving DOC(M) as DOCX |get rid of macro|doesn't get rid of macro -- 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 125338] Saving DOCM as DOCX doesn't get rid of macro
https://bugs.documentfoundation.org/show_bug.cgi?id=125338 --- Comment #5 from Aron Budea --- Created attachment 156343 --> https://bugs.documentfoundation.org/attachment.cgi?id=156343=edit Sample DOC w macro Same thing happens if the source is a DOC with macro. Attaching attachment 133753 converted to DOC in Word as a sample for that. When converted to DOCX in LO, the macro persists. -- 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 97552] unexpected changes in formula references
https://bugs.documentfoundation.org/show_bug.cgi?id=97552 m.a.riosv changed: What|Removed |Added Resolution|FIXED |WORKSFORME --- Comment #11 from m.a.riosv --- There is not patch to fix, so the proper it's resolved as 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 103381] [META] Pivot table (aka Data Pilot) bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=103381 Bug 103381 depends on bug 96977, which changed state. Bug 96977 Summary: PIVOTTABLE FORMATTING: pivot table uses the formatted column label which cause errors when calling GETPIVOTDATA https://bugs.documentfoundation.org/show_bug.cgi?id=96977 What|Removed |Added Status|NEW |RESOLVED Resolution|--- |WORKSFORME -- 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 96977] PIVOTTABLE FORMATTING: pivot table uses the formatted column label which cause errors when calling GETPIVOTDATA
https://bugs.documentfoundation.org/show_bug.cgi?id=96977 m.a.riosv changed: What|Removed |Added Resolution|--- |WORKSFORME Status|NEW |RESOLVED --- Comment #4 from m.a.riosv --- Works for me. Version: 6.5.0.0.alpha0+ (x64) Build ID: 60e8941fd581bb06cbf6be62edb8c387e7c07812 CPU threads: 4; OS: Windows 10.0 Build 19035; UI render: default; VCL: win; Locale: es-ES (es_ES); UI-Language: en-US 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 95308] Split indicator appears on top of comments
https://bugs.documentfoundation.org/show_bug.cgi?id=95308 m.a.riosv changed: What|Removed |Added Severity|normal |minor --- Comment #5 from m.a.riosv --- Still Version: 6.5.0.0.alpha0+ (x64) Build ID: 60e8941fd581bb06cbf6be62edb8c387e7c07812 CPU threads: 4; OS: Windows 10.0 Build 19035; UI render: default; VCL: win; Locale: es-ES (es_ES); UI-Language: en-US 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 95307] Comments shown in wrong position when hovering over comment indicators
https://bugs.documentfoundation.org/show_bug.cgi?id=95307 --- Comment #5 from m.a.riosv --- Still Version: 6.5.0.0.alpha0+ (x64) Build ID: 60e8941fd581bb06cbf6be62edb8c387e7c07812 CPU threads: 4; OS: Windows 10.0 Build 19035; UI render: default; VCL: win; Locale: es-ES (es_ES); UI-Language: en-US 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 93334] [FILEOPEN] Problem importing CSV
https://bugs.documentfoundation.org/show_bug.cgi?id=93334 --- Comment #10 from m.a.riosv --- Works in the same way. Version: 6.5.0.0.alpha0+ (x64) Build ID: 60e8941fd581bb06cbf6be62edb8c387e7c07812 CPU threads: 4; OS: Windows 10.0 Build 19035; UI render: default; VCL: win; Locale: es-ES (es_ES); UI-Language: en-US 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 91192] Writer not recognizing a URL's trailing carat, hash mark, question mark, or backslash
https://bugs.documentfoundation.org/show_bug.cgi?id=91192 m.a.riosv changed: What|Removed |Added Resolution|--- |WORKSFORME Status|NEW |RESOLVED --- Comment #9 from m.a.riosv --- Works for me. Version: 6.5.0.0.alpha0+ (x64) Build ID: 60e8941fd581bb06cbf6be62edb8c387e7c07812 CPU threads: 4; OS: Windows 10.0 Build 19035; UI render: default; VCL: win; Locale: es-ES (es_ES); UI-Language: en-US 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 90209] FORMATTING FILESAVE conditional formatting fails to be saved
https://bugs.documentfoundation.org/show_bug.cgi?id=90209 --- Comment #5 from m.a.riosv --- Now the conditional format is not copied from G26:H26 to G27. Version: 6.5.0.0.alpha0+ (x64) Build ID: 60e8941fd581bb06cbf6be62edb8c387e7c07812 CPU threads: 4; OS: Windows 10.0 Build 19035; UI render: default; VCL: win; Locale: es-ES (es_ES); UI-Language: en-US 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 84763] Poor performance entering data with conditional formatting
https://bugs.documentfoundation.org/show_bug.cgi?id=84763 --- Comment #10 from m.a.riosv --- Still Version: 6.5.0.0.alpha0+ (x64) Build ID: 60e8941fd581bb06cbf6be62edb8c387e7c07812 CPU threads: 4; OS: Windows 10.0 Build 19035; UI render: default; VCL: win; Locale: es-ES (es_ES); UI-Language: en-US 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 83116] Cannot convert dates with fractional seconds >= 0.9995
https://bugs.documentfoundation.org/show_bug.cgi?id=83116 m.a.riosv changed: What|Removed |Added Status|NEW |RESOLVED Resolution|--- |WORKSFORME --- Comment #13 from m.a.riosv --- Looks works fine now. Version: 6.5.0.0.alpha0+ (x64) Build ID: 60e8941fd581bb06cbf6be62edb8c387e7c07812 CPU threads: 4; OS: Windows 10.0 Build 19035; UI render: default; VCL: win; Locale: es-ES (es_ES); UI-Language: en-US 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 73120] Cannot Find & Replace for a range, this function works for the entire sheet
https://bugs.documentfoundation.org/show_bug.cgi?id=73120 --- Comment #8 from m.a.riosv --- Still Version: 6.5.0.0.alpha0+ (x64) Build ID: 60e8941fd581bb06cbf6be62edb8c387e7c07812 CPU threads: 4; OS: Windows 10.0 Build 19035; UI render: default; VCL: win; Locale: es-ES (es_ES); UI-Language: en-US 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 71147] FILEOPEN: lwp-files open not or without charts/tables
https://bugs.documentfoundation.org/show_bug.cgi?id=71147 --- Comment #15 from m.a.riosv --- General Error, general input/output error Version: 6.5.0.0.alpha0+ (x64) Build ID: 60e8941fd581bb06cbf6be62edb8c387e7c07812 CPU threads: 4; OS: Windows 10.0 Build 19035; UI render: default; VCL: win; Locale: es-ES (es_ES); UI-Language: en-US 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 68720] FORMATTING: The cells in a column from csv-import that contain the currency symbol is not properly formatted as currency
https://bugs.documentfoundation.org/show_bug.cgi?id=68720 --- Comment #9 from m.a.riosv --- Still Version: 6.5.0.0.alpha0+ (x64) Build ID: 60e8941fd581bb06cbf6be62edb8c387e7c07812 CPU threads: 4; OS: Windows 10.0 Build 19035; UI render: default; VCL: win; Locale: es-ES (es_ES); UI-Language: en-US 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 59391] Naming a cell causes certain references using labeled ranges to go undefined; recalculate/autocalculate
https://bugs.documentfoundation.org/show_bug.cgi?id=59391 --- Comment #7 from m.a.riosv --- Still Version: 6.3.3.2 (x64) Build ID: a64200df03143b798afd1ec74a12ab50359878ed CPU threads: 4; OS: Windows 10.0; UI render: default; VCL: win; Locale: es-ES (es_ES); UI-Language: en-US Calc: -- 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 104049] Renaming paragraph style in Writer destroys the document
https://bugs.documentfoundation.org/show_bug.cgi?id=104049 --- Comment #4 from m.a.riosv --- Still Version: 6.5.0.0.alpha0+ (x64) Build ID: 60e8941fd581bb06cbf6be62edb8c387e7c07812 CPU threads: 4; OS: Windows 10.0 Build 19035; UI render: default; VCL: win; Locale: es-ES (es_ES); UI-Language: en-US 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 129220] I'm getting a repeatable error with the SUM() function
https://bugs.documentfoundation.org/show_bug.cgi?id=129220 Andrew changed: What|Removed |Added CC||andrew...@biagionelli.com --- Comment #1 from Andrew --- Created attachment 156342 --> https://bugs.documentfoundation.org/attachment.cgi?id=156342=edit Test case demonstrating the bug. Faulty values are in cells A15 and A17. -- 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 129220] New: I'm getting a repeatable error with the SUM() function
https://bugs.documentfoundation.org/show_bug.cgi?id=129220 Bug ID: 129220 Summary: I'm getting a repeatable error with the SUM() function Product: LibreOffice Version: 6.2.8.2 release Hardware: Other OS: Windows (All) Status: UNCONFIRMED Severity: normal Priority: medium Component: Calc Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: andrew...@biagionelli.com Description: The sum of 12 numbers using the SUM() function should be exactly 0.11, but instead comes out to be: 0.1090 Doing an individual sum (A2+A3+...A13) gives the correct 0.11 Worse, the difference between these two gives: 0.00056899 instead of the expected 0.0010 Details of the actual numbers used is below, in "steps to reproduce". Detailed version & equipment info: - Calc reports: Version: 6.2.8.2 (x64) Build ID: f82ddfca21ebc1e222a662a32b25c0c9d20169ee CPU threads: 8; OS: Windows 10.0; UI render: default; VCL: win; Locale: en-US (en_US); UI-Language: en-US Calc: threaded - Windows reports: Processor: Intel Core i5-8265U @ 1.60GHz 1.80 GHz Steps to Reproduce: 1. In cells A2:A13 I have the following exact numbers (NOT formulas): -37.12 0 18.56 0 0 0 0 0 18.56 0.11 2. In cell A15 I have: =IF(A16="","",SUM(A2:A13)) 3. In cell A16 I have: =A2+A3+A4+A5+A6+A7+A8+A9+A10+A11+A12+A13 4. In cell A17 I have: =IF(A15=A16,"",A16-A15) 5. Now, cells A15-A17 show the following values: A15: 0.1090 A16: 0.1100 A17: 0.00056899 I tried this in a new spreadsheet (cell A1 is empty). Actual Results: A15: 0.1090 A16: 0.1100 A17: 0.00056899 Expected Results: A15: 0.1100 A16: 0.1100 A17: 0. Reproducible: Always User Profile Reset: Yes Additional Info: - LibreOffice Calc Help -> About reports: Version: 6.2.8.2 (x64) Build ID: f82ddfca21ebc1e222a662a32b25c0c9d20169ee CPU threads: 8; OS: Windows 10.0; UI render: default; VCL: win; Locale: en-US (en_US); UI-Language: en-US Calc: threaded - Windows 10 Settings -> About reports: Processor: Intel Core i5-8265U @ 1.60GHz 1.80 GHz Windows 10 Home Version 1903 OS Build 18362.476 -- 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 129219] Different Implementation of OpenType Font Features in the “Character” Dialogue
https://bugs.documentfoundation.org/show_bug.cgi?id=129219 --- Comment #2 from Tobias Hemm --- Created attachment 156341 --> https://bugs.documentfoundation.org/attachment.cgi?id=156341=edit Table with OpenType Features to be Implemented -- 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 129219] Different Implementation of OpenType Font Features in the “Character” Dialogue
https://bugs.documentfoundation.org/show_bug.cgi?id=129219 --- Comment #1 from Tobias Hemm --- Created attachment 156340 --> https://bugs.documentfoundation.org/attachment.cgi?id=156340=edit Demonstration of Possible Implementation in Character Dialogue -- 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 129219] New: Different Implementation of OpenType Font Features in the “Character” Dialogue
https://bugs.documentfoundation.org/show_bug.cgi?id=129219 Bug ID: 129219 Summary: Different Implementation of OpenType Font Features in the “Character” Dialogue Product: LibreOffice Version: 6.2.8.2 release Hardware: All OS: All Status: UNCONFIRMED Severity: enhancement Priority: medium Component: LibreOffice Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: tobiasenthe...@mailbox.org Description: I prepared to file an enhancement for LO Writer regarding a graphical implementation of OpenType features. When I was ready to file the enhancement, I found that, from Version 6.2, something like that is already available. So I updated from 6.1 to 6.2 in order to test it. And I think It’s not badly done. But in my opinion it could be improved a lot. My idea was to create a new tab called "OpenType" or "OpenType Features" in the character dialogue. I would make it the second tab. I think this would be better than "hiding" it below the font size column. These features become more an more important, which is why I think that they deserve a more prominent position in a separate tab and more space. Furthermore, my suggestion would have been to not only group the features in a sensible way in order to provide a clear and comprehensible overview, but also to always show all features and "grey out" the ones not-available in a font. The attached table shows a possible way of implementing and grouping the features. (If multiple active features are possible, you could use checkboxes (see attached image). If the features of one group are mutually exclusive and therefore only one choice is allowed, use a bullet. For long lists with one option, like with character variants, I would use a dropdown menu.) Please consider that I am not sure about which of these features are mutually exclusive and which are not, since I am not familiar with all of them from practice. I am also not sure about how to group and order them. There are many features. You can also give me a list with all features you implement, if you want me to do more grouping work. The list under the following link also provides orientation on grouping etc.: https://en.wikipedia.org/wiki/List_of_typographic_features A lot of information about OpenType features can be found under this link. I attached an image that shows how it could look like, and the above mentioned table shows the features that I would consider needed. For example, the features "Swash" and "Contextual Swash" are missing as graphical options, at the moment. The image is, however, just a demonstration; not all of the features are considered here. It would be great if you also implemented a description that appears on mouse hover, e.g. if you hover over “Small Caps”, there arises the text “Substitutes lower-case letters with small caps versions” and the abbreviation of the feature, here "smcp" (also see image). You find these descriptions on the Wikipedia page (see link above). By the way, the current German translation of the implemented features is pretty poor. Can you please tell me how I can contribute to improving it? You could also just pass on the attached table to your translation guys. It contains a column with German translations. If you need help or support for this implementation, you can ask me. I am not a programmer, but I can help you find out information about the OpenType features, and maybe I can test. Actual Results: no bug, therefore unnecessary Expected Results: no bug, therefore unnecessary Reproducible: Always User Profile Reset: No Additional Info: -- 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 129218] VIEWING: Some svg are incorrectly rendered (maybe due to css)
https://bugs.documentfoundation.org/show_bug.cgi?id=129218 Do changed: What|Removed |Added CC||domenico@gmail.com --- Comment #1 from Do --- Created attachment 156339 --> https://bugs.documentfoundation.org/attachment.cgi?id=156339=edit Mentioned SVG images Images -- 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 129218] New: VIEWING: Some svg are incorrectly rendered (maybe due to css)
https://bugs.documentfoundation.org/show_bug.cgi?id=129218 Bug ID: 129218 Summary: VIEWING: Some svg are incorrectly rendered (maybe due to css) Product: LibreOffice Version: 6.3.3.2 release Hardware: All OS: Linux (All) Status: UNCONFIRMED Severity: normal Priority: medium Component: Writer Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: domenico@gmail.com Description: I modify some svg using css in place xml attribute and I used nested translate. So, some element are not displyed. Just on Ubuntu version. Steps to Reproduce: 1. add GaussianDistribugion_old.svg 2. add GaussianDistribugion.svg 3. add Tao_symbol.svg 4. add Luscher.svg Actual Results: 1. good 2. miss the curve (path) 3. left line is not displyed 4. image is not centred and text is not displayed Expected Results: take a look in a browser or on windows Reproducible: Always User Profile Reset: No OpenGL enabled: Yes Additional Info: OpenGL vendor string: X.Org OpenGL renderer string: AMD RS780 (DRM 2.50.0 / 5.3.0-24-generic, LLVM 9.0.0) OpenGL core profile version string: 3.3 (Core Profile) Mesa 19.2.1 OpenGL core profile shading language version string: 3.30 OpenGL core profile context flags: (none) OpenGL core profile profile mask: core profile OpenGL core profile extensions: OpenGL version string: 3.0 Mesa 19.2.1 OpenGL shading language version string: 1.30 OpenGL context flags: (none) OpenGL extensions: OpenGL ES profile version string: OpenGL ES 3.0 Mesa 19.2.1 OpenGL ES profile shading language version string: OpenGL ES GLSL ES 3.00 OpenGL ES profile extensions: -- 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 34722] FILEOPEN: Text boxes are not shown in generated .doc documents
https://bugs.documentfoundation.org/show_bug.cgi?id=34722 --- Comment #25 from Regina Henschel --- (In reply to Julien Nabet from comment #24) > Regina: taking a look at this one, I noticed that the log > warn:legacy.osl:271686:271686:sw/source/filter/ww8/ww8graf.cxx:2596: Where > is the Shape ? > appeared first with mso_sptNotchedCircularArrow > ... > pRet is false because "GetCustomShapeContent( aObjData.eShapeType )" from > line 4433 > (see > https://opengrok.libreoffice.org/xref/core/filter/source/msfilter/msdffimp. > cxx?r=be3a8183#4433) returns nothing. > > Indeed this function doesn't deal with case "mso_sptNotchedCircularArrow" > (see > https://opengrok.libreoffice.org/xref/core/svx/source/customshapes/ > EnhancedCustomShapeGeometry.cxx?r=d2702aea#8346) > but when taking a look at how the other ones are implemented, it seems it's > quite complex. > I don't pretend I could succeed but are there some doc about how to > implement them? I don't know what you are looking for, and think, I cannot really help you. The specification of the binary format is in [MS-ODRAW]: Office Drawing Binary File Format https://docs.microsoft.com/en-us/openspecs/office_file_formats/ms-olp/6ae2fd93-51fc-4e75-a54a-1b175c627b51 The shapes in question are legacy "text box" shapes in MS, German "Textfeld". Those does not exists in modern docx. OOo2.4.3 opens the file without problems, OOo3.2 crashes. The texts are legacy rectangles there, not custom shapes and not frames. They are anchored "at character". I see only three custom shapes, one for the rounded rectangle at the top, one for the rectangle with text UNIT PLUS in the middle, and one for the last rectangle at the bottom. The other lines are single lines. -- 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: Planned Gerrit upgrade on Wed, Dec 25 from 00:00 to 04:00 UTC
Hi, Guilhem, I have done the necessary for gerrit and wiki. The account configuration page likst "Known services" including Bugzilla and AxkLibo. Must I or should I do something about my accounts with the latter two services? If so, how do I go about it? Thanks, Terry. ___ LibreOffice mailing list LibreOffice@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice
