[Libreoffice-bugs] [Bug 139886] CALC: "Replace All" in "Current selection only" changes selection in the table
https://bugs.documentfoundation.org/show_bug.cgi?id=139886 Ian S. changed: What|Removed |Added CC||bugrepor...@public-files.de --- Comment #2 from Ian S. --- OK, that's a point, indeed. At least there should be an explicitly information about the change of selection in the "Search Results" dialog: Imagine a huge selection larger than the screen, a "Find & Replace" which hits most of the selected cells so that the "Search Results" dialog's list of cells hit is elusive and the newly unselected cells are out of screen bounds... IMHO there should not be another checkbox option in the "Find & Replace" dialog. Instead I would prefer an option to proceed with the new or the original selection in the "Search Results" dialog if selection has changed. Best regards Ian -- 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 108519] [META] Page break bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=108519 NISZ LibreOffice Team changed: What|Removed |Added Depends on||138139 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=138139 [Bug 138139] FILEOPEN DOCX Empty paragraph with only page break has its border from style drawn -- 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 138139] FILEOPEN DOCX Empty paragraph with only page break has its border from style drawn
https://bugs.documentfoundation.org/show_bug.cgi?id=138139 NISZ LibreOffice Team changed: What|Removed |Added Blocks||108519 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=108519 [Bug 108519] [META] Page break bugs and enhancements -- 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 108519] [META] Page break bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=108519 NISZ LibreOffice Team changed: What|Removed |Added Depends on||139407 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=139407 [Bug 139407] FILEOPEN DOCX: Empty numbering list displays the 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-bugs] [Bug 138139] FILEOPEN DOCX Empty paragraph with only page break has its border from style drawn
https://bugs.documentfoundation.org/show_bug.cgi?id=138139 NISZ LibreOffice Team changed: What|Removed |Added See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=13 ||9407 -- 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 139407] FILEOPEN DOCX: Empty numbering list displays the number
https://bugs.documentfoundation.org/show_bug.cgi?id=139407 NISZ LibreOffice Team changed: What|Removed |Added CC||libreoff...@nisz.hu See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=13 ||8139 Blocks||108519 --- Comment #5 from NISZ LibreOffice Team --- This is similar to bug #138139 In this case the last paragraph of the documents second page contains only a page break. But also there is numbering set on the paragraph. Word does not display that numbering until there is no other content in that paragraph than the page break, putting a letter there shows the numbering in Word too. Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=108519 [Bug 108519] [META] Page break bugs and enhancements -- 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 135384] Writer hangs on inserting ToC if "Enable cursor" is unchecked
https://bugs.documentfoundation.org/show_bug.cgi?id=135384 --- Comment #8 from Justin L --- SwViewOption::IsIgnoreProtectedArea() means Enable Cursor is checked on. The TOX is protected because "Protected against manual changes". It probably is done via a GetProtect() property. But I will do no more here because only a Michael-Stahl-comparable person should touch something like this. -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 139910] Calc when save-ing document as .xlsx messes up formula, if save-ing as .xls works fine.
https://bugs.documentfoundation.org/show_bug.cgi?id=139910 Ming Hua changed: What|Removed |Added CC||ming.v@qq.com --- Comment #1 from Ming Hua --- I haven't tested your steps yet, but I'd like to point out that LibreOffice Calc and Microsoft Excel use different notations for sheets and cells in formula, and it's well documented in LO Help: https://help.libreoffice.org/7.0/en-US/text/shared/optionen/01060900.html In short, Calc uses "$Sheet1.A1" by default ($ for sheet name, . between sheet name and cell name), while Excel uses "Sheet1!A1" by default (no symbol for sheet name, ! between sheet name and cell name). So if you file is in Excel's XLSX or XLS format, and interoperability between Calc and Excel is important, you should consider using Excel's notations everywhere. In Calc this is configured in Tools > Options > LibreOffice Calc > Formula. -- 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 139474] Style inspector not showing Direct Formatting in Comment box
https://bugs.documentfoundation.org/show_bug.cgi?id=139474 Dieter changed: What|Removed |Added Whiteboard| QA:needsComment| CC||dgp-m...@gmx.de, ||libreoffice-ux-advise@lists ||.freedesktop.org Keywords||needsUXEval --- Comment #2 from Dieter --- ... and ask Design-Team cc: Design-Team -- 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 139474] Style inspector not showing Direct Formatting in Comment box
https://bugs.documentfoundation.org/show_bug.cgi?id=139474 Dieter changed: What|Removed |Added Whiteboard| QA:needsComment| CC||dgp-m...@gmx.de, ||libreoffice-ux-advise@lists ||.freedesktop.org Keywords||needsUXEval --- Comment #2 from Dieter --- ... and ask Design-Team cc: Design-Team -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 106179] [META] Writer comment bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=106179 Dieter changed: What|Removed |Added Depends on||139474 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=139474 [Bug 139474] Style inspector not showing Direct Formatting in Comment box -- 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 139474] Style inspector not showing Direct Formatting in Comment box
https://bugs.documentfoundation.org/show_bug.cgi?id=139474 Dieter changed: What|Removed |Added Blocks||106179 Severity|normal |enhancement --- Comment #1 from Dieter --- I confirm the expected behaviour, but I won't expect informations about comments Style inspector shows Para Styles Para DF Char Styles Char DF For me it is obvious, that this doesn't refer to comments. So let's treat it as enhancement request and ask Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=106179 [Bug 106179] [META] Writer comment bugs and enhancements -- 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: compilerplugins/clang
compilerplugins/clang/stringconstant.cxx |9 +
compilerplugins/clang/test/stringconstant.cxx |2 ++
2 files changed, 11 insertions(+)
New commits:
commit 2682feb036fdf566028a9cab83ba8369484e459b
Author: Stephan Bergmann
AuthorDate: Mon Jan 25 20:30:14 2021 +0100
Commit: Stephan Bergmann
CommitDate: Tue Jan 26 08:42:09 2021 +0100
Adapt loplugin:stringconstant to many functions taking string_view args now
So look through (implicit) O[U]String to string_view conversions for those
arguments.
Change-Id: I1101d3f681d227ad0a76a4477bf52a1a3898cfdc
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/109926
Tested-by: Jenkins
Reviewed-by: Stephan Bergmann
diff --git a/compilerplugins/clang/stringconstant.cxx
b/compilerplugins/clang/stringconstant.cxx
index 372dbceb92ba..0447ba96ad1c 100644
--- a/compilerplugins/clang/stringconstant.cxx
+++ b/compilerplugins/clang/stringconstant.cxx
@@ -1954,6 +1954,15 @@ void StringConstant::handleStringCtor(
bool explicitFunctionalCastNotation, StringKind stringKind)
{
auto e0 = argExpr->IgnoreParenImpCasts();
+if (auto const e1 = dyn_cast(e0)) {
+if (auto const e2 = dyn_cast(e1->getMethodDecl())) {
+if
(loplugin::TypeCheck(e2->getConversionType()).ClassOrStruct("basic_string_view")
+.StdNamespace())
+{
+e0 = e1->getImplicitObjectArgument()->IgnoreParenImpCasts();
+}
+}
+}
auto e1 = dyn_cast(e0);
if (e1 == nullptr) {
if (explicitFunctionalCastNotation) {
diff --git a/compilerplugins/clang/test/stringconstant.cxx
b/compilerplugins/clang/test/stringconstant.cxx
index 1e325633d856..02f83b531068 100644
--- a/compilerplugins/clang/test/stringconstant.cxx
+++ b/compilerplugins/clang/test/stringconstant.cxx
@@ -110,6 +110,8 @@ int main() {
(void) OUString("\xC2\x80", 2, RTL_TEXTENCODING_UTF8); // expected-error
{{simplify construction of 'OUString' with UTF-8 content as OUString(u"\u0080")
[loplugin:stringconstant]}}
+OUString().reverseCompareTo(OUString()); // expected-error {{in call of
'rtl::OUString::reverseCompareTo', replace default-constructed 'OUString' with
an empty string literal [loplugin:stringconstant]}}
+
OUStringBuffer ub;
ub.append(""); // expected-error {{call of 'rtl::OUStringBuffer::append'
with suspicious empty string constant argument [loplugin:stringconstant]}}
ub.append("foo\0bar"); // expected-error {{call of
'rtl::OUStringBuffer::append' with string constant argument containing embedded
NULLs [loplugin:stringconstant]}}
___
Libreoffice-commits mailing list
libreoffice-comm...@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice-commits
[Libreoffice-bugs] [Bug 139547] Writer removes images from document during (auto)save operation
https://bugs.documentfoundation.org/show_bug.cgi?id=139547 Dieter changed: What|Removed |Added Ever confirmed|0 |1 Whiteboard| QA:needsComment| CC||dgp-m...@gmx.de Status|UNCONFIRMED |NEEDINFO --- Comment #1 from Dieter --- Tommy, thank you for reporting the bug. To be certain the reported issue is not related to corruption in the user profile, could you please reset your Libreoffice profile (https://wiki.documentfoundation.org/UserProfile) and re-test? I have set the bug's status to 'NEEDINFO'. Please change it back to 'UNCONFIRMED' if the issue is still present. Please also paste informations from Help => About LibreOffice -- 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: avmedia/source basic/source chart2/source connectivity/source cui/source dbaccess/source editeng/source framework/source i18nlangtag/source i18npool/inc i18npool/source
avmedia/source/framework/mediaitem.cxx|2 +- basic/source/inc/buffer.hxx |4 ++-- chart2/source/controller/inc/CommandDispatchContainer.hxx |2 +- chart2/source/view/axes/Tickmarks.cxx |2 +- chart2/source/view/axes/Tickmarks.hxx |2 +- connectivity/source/drivers/firebird/DatabaseMetaData.cxx |2 +- connectivity/source/drivers/firebird/DatabaseMetaData.hxx |2 +- cui/source/dialogs/AdditionsDialog.cxx|2 +- cui/source/inc/AdditionsDialog.hxx|2 +- cui/source/inc/cuihyperdlg.hxx|2 +- dbaccess/source/ui/control/opendoccontrols.cxx|2 +- dbaccess/source/ui/inc/opendoccontrols.hxx|2 +- editeng/source/editeng/editview.cxx |2 +- editeng/source/editeng/impedit.cxx|2 +- editeng/source/editeng/impedit.hxx|2 +- framework/source/services/desktop.cxx |2 +- framework/source/uiconfiguration/ImageList.cxx|2 +- framework/source/uiconfiguration/ImageList.hxx|2 +- i18nlangtag/source/languagetag/languagetag.cxx|4 ++-- i18npool/inc/breakiteratorImpl.hxx|2 +- i18npool/source/breakiterator/breakiteratorImpl.cxx |2 +- include/avmedia/mediaitem.hxx |2 +- include/editeng/editview.hxx |2 +- include/framework/desktop.hxx |2 +- include/oox/dump/dumperbase.hxx |2 +- include/sfx2/docfile.hxx |2 +- include/sfx2/lokhelper.hxx|2 +- include/svx/svdobj.hxx|2 +- include/vcl/SwapFile.hxx |2 +- include/vcl/event.hxx |2 +- include/vcl/filter/PDFiumLibrary.hxx |2 +- include/vcl/graph.hxx |2 +- include/vcl/notebookbar/notebookbar.hxx |2 +- include/vcl/uitest/logger.hxx |2 +- linguistic/source/hyphdsp.hxx |8 linguistic/source/spelldsp.hxx|8 linguistic/source/thesdsp.hxx |4 ++-- oox/source/drawingml/diagram/diagram.hxx |2 +- oox/source/dump/dumperbase.cxx|2 +- sdext/source/presenter/PresenterToolBar.cxx |2 +- sfx2/source/doc/docfile.cxx |2 +- sfx2/source/view/lokhelper.cxx|2 +- starmath/inc/ElementsDockingWindow.hxx|2 +- svx/source/svdraw/presetooxhandleadjustmentrelations.cxx |2 +- svx/source/svdraw/svdobj.cxx |2 +- sw/inc/fldbas.hxx |2 +- sw/source/core/fields/fldbas.cxx |2 +- sw/source/uibase/fldui/fldmgr.cxx |2 +- sw/source/uibase/inc/fldmgr.hxx |2 +- sw/source/uibase/sidebar/WriterInspectorTextPanel.cxx |4 ++-- uui/source/iahndl.hxx |2 +- vcl/inc/image.h |2 +- vcl/inc/impgraph.hxx |2 +- vcl/inc/sft.hxx |2 +- vcl/inc/unx/freetype_glyphcache.hxx |2 +- vcl/inc/unx/glyphcache.hxx|2 +- vcl/inc/verticaltabctrl.hxx |4 ++-- vcl/source/control/ivctrl.cxx |2 +- vcl/source/gdi/graph.cxx |2 +- vcl/source/gdi/impgraph.cxx |2 +- vcl/source/gdi/pdfbuildin_fonts.cxx |2 +- vcl/source/gdi/pdfbuildin_fonts.hxx |2 +- vcl/source/uitest/logger.cxx |6 -- vcl/source/window/NotebookBarAddonsMerger.cxx |2 +- vcl/unx/generic/glyphs/freetype_glyphcache.cxx|4 ++-- writerfilter/source/dmapper/DomainMapperTableManager.cxx |2 +- writerfilter/source/dmapper/DomainMapperTableManager.hxx |2 +- writerfilter/source/dmapper/NumberingManager.cxx |2 +- writerfilter/source/dmapper/NumberingManager.hxx |4 ++-- writerfilter/source/dmapper/SettingsTable.cxx |4 ++-- writerfilter/source/dmapper/SettingsTable.hxx |4 ++-- xmlsecurity/source/xmlsec/nss/nssinitializer.cxx |2
[Libreoffice-bugs] [Bug 139530] FORMCONTROLS Text Box Vertical Alignment option ignored during PDF export
https://bugs.documentfoundation.org/show_bug.cgi?id=139530 Dieter changed: What|Removed |Added CC||dgp-m...@gmx.de Component|Writer |Printing and PDF export -- 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 103458] When tracking changes, backspacing over a deleted word should skip over it instead of moving inside it
https://bugs.documentfoundation.org/show_bug.cgi?id=103458 Ulrich Windl changed: What|Removed |Added CC||ulrich.wi...@rz.uni-regensb ||urg.de --- Comment #6 from Ulrich Windl --- In 6.4.7.2 backspacing over a deleted word just does nothing, i.e.: the cursor does not move at 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-commits] core.git: icon-themes/elementary icon-themes/elementary_svg
icon-themes/elementary/cmd/32/currencyfield.png |binary icon-themes/elementary/cmd/32/menubar.png|binary icon-themes/elementary/cmd/32/tablemodefix.png |binary icon-themes/elementary/cmd/32/tablemodefixprop.png |binary icon-themes/elementary/cmd/32/tablemodevariable.png |binary icon-themes/elementary/cmd/32/zoom.png |binary icon-themes/elementary/cmd/lc_currencyfield.png |binary icon-themes/elementary/cmd/lc_menubar.png|binary icon-themes/elementary/cmd/lc_tablemodefix.png |binary icon-themes/elementary/cmd/lc_tablemodefixprop.png |binary icon-themes/elementary/cmd/lc_tablemodevariable.png |binary icon-themes/elementary/cmd/sc_currencyfield.png |binary icon-themes/elementary/cmd/sc_menubar.png|binary icon-themes/elementary/cmd/sc_position.png |binary icon-themes/elementary/cmd/sc_tablemodefix.png |binary icon-themes/elementary/cmd/sc_tablemodefixprop.png |binary icon-themes/elementary/cmd/sc_tablemodevariable.png |binary icon-themes/elementary/sc/res/sidebar/CellBorder.png |binary icon-themes/elementary_svg/cmd/32/currencyfield.svg |2 +- icon-themes/elementary_svg/cmd/32/menubar.svg|2 +- icon-themes/elementary_svg/cmd/32/tablemodefix.svg |2 +- icon-themes/elementary_svg/cmd/32/tablemodefixprop.svg |2 +- icon-themes/elementary_svg/cmd/32/tablemodevariable.svg |2 +- icon-themes/elementary_svg/cmd/32/zoom.svg |2 +- icon-themes/elementary_svg/cmd/lc_currencyfield.svg |2 +- icon-themes/elementary_svg/cmd/lc_menubar.svg|2 +- icon-themes/elementary_svg/cmd/lc_tablemodefix.svg |2 +- icon-themes/elementary_svg/cmd/lc_tablemodefixprop.svg |2 +- icon-themes/elementary_svg/cmd/lc_tablemodevariable.svg |2 +- icon-themes/elementary_svg/cmd/sc_currencyfield.svg |2 +- icon-themes/elementary_svg/cmd/sc_menubar.svg|7 +-- icon-themes/elementary_svg/cmd/sc_position.svg |2 +- icon-themes/elementary_svg/cmd/sc_tablemodefix.svg |2 +- icon-themes/elementary_svg/cmd/sc_tablemodefixprop.svg |2 +- icon-themes/elementary_svg/cmd/sc_tablemodevariable.svg |2 +- icon-themes/elementary_svg/sc/res/sidebar/CellBorder.svg |2 +- 36 files changed, 22 insertions(+), 19 deletions(-) New commits: commit a553c85cbd80a045b2e4742eefaa7fcc3953cb08 Author: Rizal Muttaqin AuthorDate: Mon Jan 25 21:22:16 2021 +0700 Commit: Rizal Muttaqin CommitDate: Tue Jan 26 08:28:32 2021 +0100 elementary: tdf#139056 update color to follow upstream brand - Update Currency related icons - Update Cell Border of Calc's sidebar - Update Table Mode icons - Update Menubar icons Change-Id: I3b75b1e3c4792f35548bd4f6042fd08ed81a Change-Id: If3ac469a472e660f6fe25221c9ce1053ac170369 Reviewed-on: https://gerrit.libreoffice.org/c/core/+/109911 Tested-by: Jenkins Reviewed-by: Rizal Muttaqin diff --git a/icon-themes/elementary/cmd/32/currencyfield.png b/icon-themes/elementary/cmd/32/currencyfield.png index 659093b1bdbe..237243c18c7d 100644 Binary files a/icon-themes/elementary/cmd/32/currencyfield.png and b/icon-themes/elementary/cmd/32/currencyfield.png differ diff --git a/icon-themes/elementary/cmd/32/menubar.png b/icon-themes/elementary/cmd/32/menubar.png index 4e45b333c25f..4f910f1cc7d1 100644 Binary files a/icon-themes/elementary/cmd/32/menubar.png and b/icon-themes/elementary/cmd/32/menubar.png differ diff --git a/icon-themes/elementary/cmd/32/tablemodefix.png b/icon-themes/elementary/cmd/32/tablemodefix.png index 325f26655bc6..49f879670ad1 100644 Binary files a/icon-themes/elementary/cmd/32/tablemodefix.png and b/icon-themes/elementary/cmd/32/tablemodefix.png differ diff --git a/icon-themes/elementary/cmd/32/tablemodefixprop.png b/icon-themes/elementary/cmd/32/tablemodefixprop.png index 6fa40fde1fbb..14e6d0fe7d20 100644 Binary files a/icon-themes/elementary/cmd/32/tablemodefixprop.png and b/icon-themes/elementary/cmd/32/tablemodefixprop.png differ diff --git a/icon-themes/elementary/cmd/32/tablemodevariable.png b/icon-themes/elementary/cmd/32/tablemodevariable.png index a3c35fd1125c..20a17d7819b0 100644 Binary files a/icon-themes/elementary/cmd/32/tablemodevariable.png and b/icon-themes/elementary/cmd/32/tablemodevariable.png differ diff --git a/icon-themes/elementary/cmd/32/zoom.png b/icon-themes/elementary/cmd/32/zoom.png index da35c733a840..59fd3a38d97b 100644 Binary files a/icon-themes/elementary/cmd/32/zoom.png and b/icon-themes/elementary/cmd/32/zoom.png differ diff --git a/icon-themes/elementary/cmd/lc_currencyfield.png b/icon-themes/elementary/cmd/lc_currencyfield.png index 88362cc0c63a..5cb1e5c3f053 100644 Binary files a/icon-themes/elementary/cmd/lc_currencyfield.png and
Re: unknown element urn:oasis:names:tc:opendocument:xmlns:text:1.0 text:soft-page-break
that SAL_WARN should probably just be changed into SAL_INFO, the way the code works, if that function doesn't decode the element, some other function will probably do so. ___ LibreOffice mailing list LibreOffice@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice
[Libreoffice-bugs] [Bug 104371] Window size is minuscule when unmaximizing after a LibreOffice app was started maximized
https://bugs.documentfoundation.org/show_bug.cgi?id=104371 --- Comment #6 from Koen Roggemans --- I think this bug describes the behaviour on https://askubuntu.com/questions/1274365/windows-of-an-application-have-minimum-size-and-i-cant-find-the-window-anymore We have noticed that with several of our students on Ubuntu 20.04 with LO 7.0.4.2 -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 139899] [META] PPTX Table issues
https://bugs.documentfoundation.org/show_bug.cgi?id=139899 Aron Budea changed: What|Removed |Added Depends on||137949 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=137949 [Bug 137949] IMPORT OOXML: Table row height is wrong. -- 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 42673] With disconnected network printers, Calc hangs opening some files waiting on the Windows print spooler
https://bugs.documentfoundation.org/show_bug.cgi?id=42673 --- Comment #29 from Mike Kaganski --- (In reply to Tim van der Meij from comment #26) > I found that it started occurring when I installed the printer > (Epson XP 630) through Windows and the printer was offline, and found this > bug. This promised to be helpful to reproduce the problem. However, I still was unable to repro. What I did: 1. I went to Epson web site [1], chose "Windows 10 (64-bit)" to download "Drivers and Utilities Combo Package Installer" (XP630_Lite_NA.exe from 2019-05-20, 11.9 MB) 2. I started the installer, and allowed it to install "drivers and utilities" only (and allowed Windows Firewall) 3. I didn't configure printer there in the installer (I don't have one) 4. I opened Windows 10 Start Manu->Settings->Devices->Printers and Scanners 5. [+] Add a printer or scanner -> The printer that I want isn't listed 6. Add a printer using a TCP/IP address or hostname 7. Device type: TCP/IP Device; Hostname or IP address: e.g. 192.168.1.100 (a random unused IP in my subnet); "[ ] Query the printer ..." unchecked 8. Device Type: Standard -> EPSON Network Printer 9. I chose Epson XP 630 model in the list 10. Clicked Next and checked "[x] Set as the default printer", and finished Starting Calc (either from the start center, or using dedicated Start Menu shortcut (soffice --calc)) still does not give a timeout problem here. If someone could provide detailed steps to follow to have the problem appear, please provide them very verbosely, so that one could be sure one uses the known problematic configuration. There are many variables on each step, as I shown above. Which driver for which model, architecture and which version to use? How to install? which networking settings to configure? ... Knowing these could allow a developer to see and fix this. Thanks! [1] https://epson.com/Support/Printers/All-In-Ones/XP-Series/Epson-XP-630/s/SPT_C11CE79201 -- 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 139853] libreoffice Calc Vlookup Error
https://bugs.documentfoundation.org/show_bug.cgi?id=139853 --- Comment #3 from peter --- Dear ： can you follow my action: 1. create 2 files for excel : A.xls; B.xls; 2. opten the files 3. use need use the menu insert ->function vlookup from A.xls to B.xls; you will found the Error, TKS! -- 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 139547] Writer removes images from document during (auto)save operation
https://bugs.documentfoundation.org/show_bug.cgi?id=139547 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 139544] Calc Sort Dialogue Options: After change the direction the options "... boundary column(s) ..." must be called "... boundary row(s) ..."
https://bugs.documentfoundation.org/show_bug.cgi?id=139544 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 139540] Function HYPERLINK used in formula creates hyperlink independent from conditional evaluation
https://bugs.documentfoundation.org/show_bug.cgi?id=139540 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 139883] Calc refuses to edit an unprotected cell in a protected worksheet when the selected range includes protected cells
https://bugs.documentfoundation.org/show_bug.cgi?id=139883 QA Administrators changed: What|Removed |Added Keywords||bibisectRequest -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 139546] Calc Sort Dialogue Options: Language Sort Options are not visible when you use your default language
https://bugs.documentfoundation.org/show_bug.cgi?id=139546 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 139519] Image vanishes from canvas (empty square or transparent square) after pasting an image to certain position
https://bugs.documentfoundation.org/show_bug.cgi?id=139519 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 139530] FORMCONTROLS Text Box Vertical Alignment option ignored during PDF export
https://bugs.documentfoundation.org/show_bug.cgi?id=139530 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 139539] Makro Basic - CALC - loadComponentFromURL - mode "hidden" unfixes fixed rows, mode "not hidden" doesn't
https://bugs.documentfoundation.org/show_bug.cgi?id=139539 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 134347] Total word count error
https://bugs.documentfoundation.org/show_bug.cgi?id=134347 QA Administrators changed: What|Removed |Added Status|NEEDINFO|RESOLVED Resolution|--- |INSUFFICIENTDATA -- 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 135269] crashed while deleting from section from copy-and-paste
https://bugs.documentfoundation.org/show_bug.cgi?id=135269 --- Comment #2 from QA Administrators --- Dear fmr, 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 134347] Total word count error
https://bugs.documentfoundation.org/show_bug.cgi?id=134347 --- Comment #5 from QA Administrators --- Dear Gordon, Please read this message in its entirety before proceeding. Your bug report is being closed as INSUFFICIENTDATA due to inactivity and a lack of information which is needed in order to accurately reproduce and confirm the problem. We encourage you to retest your bug against the latest release. If the issue is still present in the latest stable release, we need the following information (please ignore any that you've already provided): a) Provide details of your system including your operating system and the latest version of LibreOffice that you have confirmed the bug to be present b) Provide easy to reproduce steps – the simpler the better c) Provide any test case(s) which will help us confirm the problem d) Provide screenshots of the problem if you think it might help e) Read all comments and provide any requested information Once all of this is done, please set the bug back to UNCONFIRMED and we will attempt to reproduce the issue. Please do not: a) respond via email b) update the version field in the bug or any of the other details on the top section of our bug tracker Warm Regards, QA Team MassPing-NeedInfo-FollowUp -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 135004] Can't open or create documents
https://bugs.documentfoundation.org/show_bug.cgi?id=135004 --- Comment #4 from QA Administrators --- Dear luaned, 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 96702] Index is with Link text (underline)
https://bugs.documentfoundation.org/show_bug.cgi?id=96702 --- Comment #4 from QA Administrators --- Dear Matteo, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://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 94437] Editing: entries from a deleted alphabetic index reappear when a new index is inserted
https://bugs.documentfoundation.org/show_bug.cgi?id=94437 --- Comment #19 from QA Administrators --- Dear Bernard Moreton, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://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 74056] EDITING: Index Quirks
https://bugs.documentfoundation.org/show_bug.cgi?id=74056 --- Comment #7 from QA Administrators --- Dear Frank, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://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 122987] Cell movement by ALT + drag on multiple selected sheets.
https://bugs.documentfoundation.org/show_bug.cgi?id=122987 --- Comment #4 from QA Administrators --- Dear jun meguro, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://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 122485] UI: the black border of the selected cell visible through the comment box
https://bugs.documentfoundation.org/show_bug.cgi?id=122485 --- Comment #5 from QA Administrators --- Dear Telesto, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://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 122980] Macro does not execute as recorded
https://bugs.documentfoundation.org/show_bug.cgi?id=122980 --- Comment #2 from QA Administrators --- Dear roger.millichamp, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://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 122476] FILEOPEN XLSX, Pivot table with extendable line gets distorted and its pivot diagram messed up
https://bugs.documentfoundation.org/show_bug.cgi?id=122476 --- Comment #6 from QA Administrators --- Dear NISZ LibreOffice Team, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://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 122474] FILEOPEN XLSX, Pivot table gets refreshed automatically when opened in LO
https://bugs.documentfoundation.org/show_bug.cgi?id=122474 --- Comment #6 from QA Administrators --- Dear NISZ LibreOffice Team, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://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 122469] FILESAVE XLSX, A total result line appears in pivot table after saving
https://bugs.documentfoundation.org/show_bug.cgi?id=122469 --- Comment #7 from QA Administrators --- Dear NISZ LibreOffice Team, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://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 122465] FILEOPEN XLSX, Extra Data line and button appears in pivot table in Calc.
https://bugs.documentfoundation.org/show_bug.cgi?id=122465 --- Comment #6 from QA Administrators --- Dear NISZ LibreOffice Team, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://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 119408] Fails to start Draw, Impress due to new Avahi dependency
https://bugs.documentfoundation.org/show_bug.cgi?id=119408 --- Comment #6 from QA Administrators --- Dear lj308, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://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 122462] FILEOPEN XLSX, Xlsx cells have border in LO while they do not in MSO.
https://bugs.documentfoundation.org/show_bug.cgi?id=122462 --- Comment #7 from QA Administrators --- Dear NISZ LibreOffice Team, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://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 118350] Writer can't handle RTL direction from MS office odt file.
https://bugs.documentfoundation.org/show_bug.cgi?id=118350 --- Comment #13 from QA Administrators --- Dear Fahad Al-Saidi, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://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 103751] RTL outline numbering not working as expected...
https://bugs.documentfoundation.org/show_bug.cgi?id=103751 --- Comment #17 from QA Administrators --- Dear Nima Az, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://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 103627] Writer ignores +
https://bugs.documentfoundation.org/show_bug.cgi?id=103627 --- Comment #12 from QA Administrators --- Dear Terrence Enger, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://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 101188] Exclude header from alphabetical index
https://bugs.documentfoundation.org/show_bug.cgi?id=101188 --- Comment #4 from QA Administrators --- Dear carlos.camara, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://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 103458] When tracking changes, backspacing over a deleted word should skip over it instead of moving inside it
https://bugs.documentfoundation.org/show_bug.cgi?id=103458 --- Comment #5 from QA Administrators --- Dear Ulrich Windl, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://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 138934] Hyperlink: Headings in "Target in document" window show numbered sublevels, regardless of settings in "Chapter Numbering"
https://bugs.documentfoundation.org/show_bug.cgi?id=138934 --- Comment #6 from Jim Raykowski --- Hello All, Here is a link to a patch that does the expand/collapse part of this request: https://gerrit.libreoffice.org/c/core/+/109930 A demo video is available at bug 114567 -- 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 114567] HYPERLINK DIALOG: "Target in document" dialog should display the level of headings
https://bugs.documentfoundation.org/show_bug.cgi?id=114567 --- Comment #3 from Jim Raykowski --- Created attachment 169146 --> https://bugs.documentfoundation.org/attachment.cgi?id=169146=edit Hyperlink Target in Document Headings expand collapse Here is a link to a patch that does this: https://gerrit.libreoffice.org/c/core/+/109930 Continued effort is needed to preserve the tree state when the tree is refreshed. -- 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
unknown element urn:oasis:names:tc:opendocument:xmlns:text:1.0 text:soft-page-break
Hi A QA question. The debugger of TB77 builds nowdays includes some of the logging information (when a debugger being attached). Obviously helpful for some background on the crash However not able to asses the importance. Somewhere between SAL INFO and assert I guess. This got my attention more specifically warn:xmloff:5296:5108:xmloff/source/draw/shapeimport.cxx:356: unknown element urn:oasis:names:tc:opendocument:xmlns:text:1.0 text:soft-page-break Reported it as bug 139867, but that wasn't seen as the proper place. So not gonna fix this.. merely informing and ideally some advice what to do with 'sal_warn'. As similar warning can be seen in jenskins on a regular basis. Regards, Telesto ___ LibreOffice mailing list LibreOffice@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice
[Libreoffice-bugs] [Bug 139365] Table>insert Rows should move the cursor to the new row.
https://bugs.documentfoundation.org/show_bug.cgi?id=139365 --- Comment #8 from tor...@yahoo.com --- (In reply to Roman Kuznetsov from comment #7) > (In reply to TorrAB from comment #5) > > (In reply to Roman Kuznetsov from comment #4) > > > I want to insert a new row in my table but I don't want that it moves the > > > text cursor to the new row at once > > > > > > -1 from me > > > > **Why? What is on your mind when you insert a new row? > > I am not arguing, just asking. > > I just insert some rows below if I know that I need it in future, but I > don't want text cursor will move to another place from its current position! Strange. You want to insert some rows just-in-case you will need them in the future, as if it were a complex and time-consuming operation? -- 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 139572] status bar disappears
https://bugs.documentfoundation.org/show_bug.cgi?id=139572 --- Comment #4 from Nick Levinson --- Created attachment 169145 --> https://bugs.documentfoundation.org/attachment.cgi?id=169145=edit screenshots of problem and kludge -- 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 139918] New: Page Format Size set to A4 instead of Letter for US users
https://bugs.documentfoundation.org/show_bug.cgi?id=139918 Bug ID: 139918 Summary: Page Format Size set to A4 instead of Letter for US users Product: LibreOffice Version: 7.0.4.2 release Hardware: All OS: Windows (All) Status: UNCONFIRMED Severity: normal Priority: medium Component: Writer Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: spokanemagn...@gmail.com Description: The Page Format Size is set to A4 by default for US users. That is NOT the only issue with the Page Format settings, as the Margins: Normal(0.75") actually formats with the right page margin set at 0.79" for some reason (perhaps related to the wrong paper size for the US as indicated above; however, after changing that to Letter, the Normal(0.75") issue persists (although all the other margin default settings are correct)). Steps to Reproduce: 1. Go to Page Format Size. The US setting is mistakenly set for A4. 2. Select Margins: Normal(0.75") 3. Open a new blank document Actual Results: Note the incorrect margins of 0.79". Expected Results: Margins set to 0.75". Reproducible: Always User Profile Reset: No Additional Info: The only solution is to create your own default templates and/or never use the Normal(0.75") setting and opt for the Normal(1"), or some other, setting instead. OpenGL is not being used. -- 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 139917] New: Smooth scroll works opposite of that indicated by checkbox
https://bugs.documentfoundation.org/show_bug.cgi?id=139917 Bug ID: 139917 Summary: Smooth scroll works opposite of that indicated by checkbox Product: LibreOffice Version: 7.0.4.2 release Hardware: All OS: Windows (All) Status: UNCONFIRMED Severity: minor Priority: medium Component: Writer Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: spokanemagn...@gmail.com Description: When you put the cursor at the bottom (or top) of the vertical scroll bar in a long document and L-click to rapidly scroll down (or up) to quickly get roughly where you want to in the document, the result is a very slow, herky-jerky motion and is definitely NOT smooth. Ironically, the way to smooth the scrolling is to deselect the smooth scroll function in: Tools>Options>LO Writer>View. So, with Smooth scroll deselected, the scrolling in the manner described becomes nice and smooth. Is there a reason anyone would want anything but smooth scrolling? Steps to Reproduce: 1. Choose long document 2. L-click at the bottom of the vertical scroll bar Actual Results: Does not immediately start to scroll. Then jerks to a new location before stalling for an eternity before taking about big step down the scroll bar. Expected Results: Smooth scrolling all the way down to the bottom of the document. Reproducible: Always User Profile Reset: No Additional Info: Need to ironically deselect the Smooth scroll function to get Writer to scroll smoothly through the document. As far as OpenGL is concerned, if I select that checkbox, it does not stay checked and indicates that it is not used? Apparently, one has to download it separately, but there are no instructions that I could find on how to do so (what folder to put it in, what to name it, etc. for it to work with 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 139878] multiple selection range in Manage Conditional Formatting is not possible with shrink
https://bugs.documentfoundation.org/show_bug.cgi?id=139878 m.a.riosv changed: What|Removed |Added Status|UNCONFIRMED |NEW Ever confirmed|0 |1 CC||miguelangelrv@libreoffice.o ||rg --- Comment #1 from m.a.riosv --- Reproducible also with Version: 7.2.0.0.alpha0+ (x64) / LibreOffice Community Build ID: 86c8c775bbefe333d684e12c99855a3c1de68051 CPU threads: 4; OS: Windows 10.0 Build 21292; UI render: default; VCL: win Locale: es-ES (es_ES); UI: en-US Calc: CL Not a regression because it never worked. -- 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 139883] Calc refuses to edit an unprotected cell in a protected worksheet when the selected range includes protected cells
https://bugs.documentfoundation.org/show_bug.cgi?id=139883 m.a.riosv changed: What|Removed |Added Status|UNCONFIRMED |NEW CC||miguelangelrv@libreoffice.o ||rg Keywords||regression Ever confirmed|0 |1 --- Comment #1 from m.a.riosv --- Reproduced also with Version: 7.2.0.0.alpha0+ (x64) / LibreOffice Community Build ID: 86c8c775bbefe333d684e12c99855a3c1de68051 CPU threads: 4; OS: Windows 10.0 Build 21292; UI render: default; VCL: win Locale: es-ES (es_ES); UI: en-US Calc: CL Regression from 6.4. -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 139886] CALC: "Replace All" in "Current selection only" changes selection in the table
https://bugs.documentfoundation.org/show_bug.cgi?id=139886 m.a.riosv changed: What|Removed |Added CC||miguelangelrv@libreoffice.o ||rg --- Comment #1 from m.a.riosv --- I think it is the intended behavior. This way the finding or replacing cells can be use as selected for new actions, like e.g. give them a new format or do a new replacement only on those, what should be near to impossible without this behavior. As much could be a request for enhancement, with a new option to retain the selection. -- 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 67194] EDITING Make it possible to include Localized Options (Autocorrect) in using Format > AutoCorrect > Apply
https://bugs.documentfoundation.org/show_bug.cgi?id=67194 sdc.bla...@youmail.dk changed: What|Removed |Added See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=12 ||8192 --- Comment #4 from sdc.bla...@youmail.dk --- It is hard to tell whether this bug is a duplicate of bug 128192. If the OP had a document with paragraphs that were not in Default Paragraph Style, then this might be reason why Tools > AutoCorrect > Apply did not apply -- in which case it is probably a duplicate. Meanwhile, comment 3 here has framed this bug as an issue about using Localized Options with Tools > AutoCorrect > Apply. From that point of view, bug 128192 shows at least WFM in relation to this bug 67194, because Localized Options (for replace quotes) are applied (to Default Paragraph Style). -- 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 128192] Tools > Autocorrect > Apply only applies the Localized Options for single and double quote replacement on "Default paragraph style" - but should apply for all paragraph
https://bugs.documentfoundation.org/show_bug.cgi?id=128192 sdc.bla...@youmail.dk changed: What|Removed |Added See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=67 ||194 -- 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 139893] Calc export to CSV doesn't escape commas
https://bugs.documentfoundation.org/show_bug.cgi?id=139893 m.a.riosv changed: What|Removed |Added CC||miguelangelrv@libreoffice.o ||rg --- Comment #2 from m.a.riosv --- Agree with @Uwe_Auer comment. -- 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 139914] Permission to open /opt directory to add extensions denied
https://bugs.documentfoundation.org/show_bug.cgi?id=139914 --- Comment #2 from Gilbert Dion --- For at least the last 15 years, Antidote (from Druide.com) spell checker extension could be installed from the /opt directory where it is put by the Antidote installer itself. Now, with the latest version of LO, it is no longer possible. There is no need to write into this directory, just to "read" the extension located there. Since any user can read into /opt/Druide/Connectix10/Connect/LibreOffice from Nautilus or from a terminal, I don't see why suddenly this is no longer possible with 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 128192] Tools > Autocorrect > Apply only applies the Localized Options for single and double quote replacement on "Default paragraph style" - but should apply for all paragraph
https://bugs.documentfoundation.org/show_bug.cgi?id=128192 sdc.bla...@youmail.dk changed: What|Removed |Added Summary|Autocorrect doesn't behave |Tools > Autocorrect > Apply |consistently while typing |only applies the Localized |and while applying in |Options for single and |retrospeck, in text with|double quote replacement on |not Default paragraph style |"Default paragraph style" - ||but should apply for all ||paragraph styles CC||sdc.bla...@youmail.dk --- Comment #4 from sdc.bla...@youmail.dk --- Confirmed with 7.2.0.0.alpha0+ Tools > AutoCorrect > Apply will apply quotes in Localized Options in a paragraph with "Default Paragraph Style", but will not convert quotes in a paragraph with "Text Body" paragraph style. -- 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 139916] Calc In New Window rows do NOT fit side by side as in OpenOffice
https://bugs.documentfoundation.org/show_bug.cgi?id=139916 --- Comment #1 from Steve Dulaney --- Created attachment 169144 --> https://bugs.documentfoundation.org/attachment.cgi?id=169144=edit In calc New window The rows do not match up Sorry about the msgboxes in the file . Just keep clicking OK. I forgot to delete msgboxes. -- 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 139916] New: Calc In New Window rows do NOT fit side by side as in OpenOffice
https://bugs.documentfoundation.org/show_bug.cgi?id=139916 Bug ID: 139916 Summary: Calc In New Window rows do NOT fit side by side as in OpenOffice Product: LibreOffice Version: 3.3.0 release Hardware: x86-64 (AMD64) OS: Windows (All) Status: UNCONFIRMED Severity: normal Priority: medium Component: Calc Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: stdula...@netscape.net Description: In New Window when I click on one of the two windows the window moves down a little so the any 2 rows between 2 windows are Never even. In OpenOffice the rows are even between the 2 windows.Problem in LibreOffice new window Notice that the rows in OpenOffice line up in window1 and win:2 In LibreOffice they do Not line up When you click on one window the whole window moves down so the rows never line up It is better if the rows in Window and Window:2 line up as in OpenOffice it provides a lot more business applications Must be a bugg? Excel is so bad I have to simulate split windows that scrolls SEPERATELY. with new window. In my Cash Register program after 25 purchases the cash register scrolls off the screen. If I use freeze Pane I can only show 5 purchases at one time. Steps to Reproduce: 1.In Calc do New window 2.Resize each window on oposite sides of screen 3.Click on the first window then the second window :2 Better yet Try file below Actual Results: When you click on the other window that window moves down so the rows Never even up as in OpenOffice Expected Results: The rows in each window should be directly across from rows in the other window. They do not even up. Reproducible: Always User Profile Reset: No Additional Info: Rows in both windows should be directly across from (even) each other. Not slightly lower. I know I am picky (actually Excel is terrible anyway) You All do a super excellent job. Thanks Steve Dulaney -- 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 90507] Tools - AutoCorrect - Apply converts non-empty "Default Paragraph Style" paragraphs to "Text Body" PS --even when no [M] options are selected
https://bugs.documentfoundation.org/show_bug.cgi?id=90507 --- Comment #11 from V Stuart Foote --- (In reply to sdc.blanco from comment #10) > ... > But this potentially helpful behavior "collides" with the issue in bug > 59034, namely that (many) [M] options only work with Default PS. > ... Yes I would agree, and would also note the 'Replace Custom Styles' has some interesting behavior as well. Not clear if those are relative to the Standard Template, or to the Template used to create the document--but its action when applied is to remove other PS and revert to something present in the template. So, makes me wonder exactly what is considered a "custom" style as related to the AutoFormat in (editeng/acorrcfg.hxx & acorrcfg.cxx)? I've gotten lost several times now trying to trace it out in Opengrok. -- 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 90507] Tools - AutoCorrect - Apply converts non-empty "Default Paragraph Style" paragraphs to "Text Body" PS --even when no [M] options are selected
https://bugs.documentfoundation.org/show_bug.cgi?id=90507 --- Comment #11 from V Stuart Foote --- (In reply to sdc.blanco from comment #10) > ... > But this potentially helpful behavior "collides" with the issue in bug > 59034, namely that (many) [M] options only work with Default PS. > ... Yes I would agree, and would also note the 'Replace Custom Styles' has some interesting behavior as well. Not clear if those are relative to the Standard Template, or to the Template used to create the document--but its action when applied is to remove other PS and revert to something present in the template. So, makes me wonder exactly what is considered a "custom" style as related to the AutoFormat in (editeng/acorrcfg.hxx & acorrcfg.cxx)? I've gotten lost several times now trying to trace it out in Opengrok. -- 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 139915] FILEOPEN DOCX Two text boxes on two pages open on a single page
https://bugs.documentfoundation.org/show_bug.cgi?id=139915 Aron Budea changed: What|Removed |Added Status|UNCONFIRMED |NEW Ever confirmed|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-bugs] [Bug 139915] FILEOPEN DOCX Two text boxes on two pages open on a single page
https://bugs.documentfoundation.org/show_bug.cgi?id=139915 --- Comment #1 from Aron Budea --- Created attachment 169143 --> https://bugs.documentfoundation.org/attachment.cgi?id=169143=edit PDF exported in Word -- 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 120804] [META] Bugs introduced by initial DrawingML shape import in DOCX
https://bugs.documentfoundation.org/show_bug.cgi?id=120804 Aron Budea changed: What|Removed |Added Depends on||139915 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=139915 [Bug 139915] FILEOPEN DOCX Two text boxes on two pages open on a single page -- 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 139915] New: FILEOPEN DOCX Two text boxes on two pages open on a single page
https://bugs.documentfoundation.org/show_bug.cgi?id=139915 Bug ID: 139915 Summary: FILEOPEN DOCX Two text boxes on two pages open on a single page Product: LibreOffice Version: 4.3.0.4 release Hardware: All OS: All Status: UNCONFIRMED Keywords: bibisected, bisected, implementationError Severity: normal Priority: medium Component: filters and storage Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: ba...@caesar.elte.hu CC: muhammet.k...@collabora.com Blocks: 120804 Created attachment 169142 --> https://bugs.documentfoundation.org/attachment.cgi?id=169142=edit Sample DOCX The attached DOCX document contains two text boxes, on two separate pages. In Writer, they open on a single page, overlapping, and mispositioned. Observed using LO 7.2.0.0.alpha0+ (4e1294b7d6f8de981147f15d4ca1b4e4853249eb) / Ubuntu. Before the following commit in 7.1, bibisected using repo bibisect-linux-64-7.1, the text boxes were within the page area, so the placement was slightly better, but still on a single page. https://cgit.freedesktop.org/libreoffice/core/commit/?id=b6850bbe95418ecfde404be1696548f18d200c9b author Attila Bakos2020-08-06 13:49:43 +0200 committer László Németh2020-08-21 23:48:33 +0200 "tdf#106153 sw compatibility: fix textboxes exceeding the page" Before the following change in 4.3 that enabled WPS support (bibisected using repo bibisect-43max), the text box placement was fine, on two pages. Thus we can conclude this is an implementation error concerning that feature. https://cgit.freedesktop.org/libreoffice/core/commit/?id=57450afb768c085df0ba2344aa94b5f843060178 author Miklos Vajna 2013-12-03 11:59:42 +0100 committer Miklos Vajna 2013-12-03 15:39:04 +0100 "DOCX import: declare wps as a supported feature" The following might be an interesting bit, as it corrected prior layout issues, where the document looked similar to the pre-7.1 layout, except the text boxes started in the margin, not at the start of page. Bibisected using repo bibisect-41max, builds in the range crash on start, but there is a likely candidate in the range. https://cgit.freedesktop.org/libreoffice/core/log/?qt=range=6b18d7d28efb0285f01e36f5b0cb2cddb1c68488..9cc1e7b165abe3f19c2919f8d9cf8efc3e8cf315 Likely commit: https://cgit.freedesktop.org/libreoffice/core/commit/?id=b399c1a38cf7217bf530af3a78e8472d97890ac8 author Cédric Bosdonnat 2013-04-29 15:41:37 +0200 committer Cédric Bosdonnat 2013-04-30 09:34:28 +0200 "n#592908: docx import, fixed handling of w10:wrap" Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=120804 [Bug 120804] [META] Bugs introduced by initial DrawingML shape import in DOCX -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 139522] Don't retain image position when cut/pasting exclusively the image
https://bugs.documentfoundation.org/show_bug.cgi?id=139522 --- Comment #4 from S.Zosgornik --- Paste an image without its formatting attributes can already be archived by either Edit->Cut\Copy->Edit->Paste Special->Paste Special... or Right Click->Cut\Copy->Right Click->Paste Special->More Options Unfortunately, there isn't any option to keep the file type yet. -- 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 139522] Don't retain image position when cut/pasting exclusively the image
https://bugs.documentfoundation.org/show_bug.cgi?id=139522 --- Comment #4 from S.Zosgornik --- Paste an image without its formatting attributes can already be archived by either Edit->Cut\Copy->Edit->Paste Special->Paste Special... or Right Click->Cut\Copy->Right Click->Paste Special->More Options Unfortunately, there isn't any option to keep the file type yet. -- 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 59036] EDITING AutoCorrect: "Remove blank paragraphs" will work for all styles, other "[M]" options only for Default
https://bugs.documentfoundation.org/show_bug.cgi?id=59036 sdc.bla...@youmail.dk changed: What|Removed |Added See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=13 ||6824 -- 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 136824] AutoCorrect > Apply does not work in bulleted or numbered lists.
https://bugs.documentfoundation.org/show_bug.cgi?id=136824 sdc.bla...@youmail.dk changed: What|Removed |Added See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=59 ||036 CC||sdc.bla...@youmail.dk --- Comment #2 from sdc.bla...@youmail.dk --- Repro with 7.2.0.0.alpha0+ 0. Activate "URL Recognition" in both [M] and [T] in AutoCorrect Options 1. Turn off AutoCorrect while Typing 2. Start a numbered list ( Format > Lists > Numbered List ) 3. Add entries to List, make sure they are "Default Paragraph Style" 4. Add a URL to one of the list items 5. Tools > AutoCorrect > Apply Actual Result: No change to URL Expected Result: URL configured as Hyperlink Just to be sure: turn on AutoCorrect while Typing. Add URL to list entry. Recognized as URL as expected. -- 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 139914] Permission to open /opt directory to add extensions denied
https://bugs.documentfoundation.org/show_bug.cgi?id=139914
--- Comment #1 from Uwe Auer ---
/opt filesystem on Linux generally is owned by root.root (by default) and no
user without permission ("sudo" or login to root using "su -") can install into
/opt/libreofficex.y. Either
1) Extension is "Installed for all users" by root
2) Extension is "Installed for current user" into user profile
3) Permissions and/or ownership for /opt/ibreofficex.y and sub-directories are
manually changed by the system administrator to accomplish a user installation
into /opt (absolutely not recommended way to go)
>From my perspective not a LibreOffice 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 90507] Tools - AutoCorrect - Apply converts non-empty "Default Paragraph Style" paragraphs to "Text Body" PS --even when no [M] options are selected
https://bugs.documentfoundation.org/show_bug.cgi?id=90507 --- Comment #10 from sdc.bla...@youmail.dk --- (In reply to V Stuart Foote from comment #9) > It is actually pretty handy "feature", but it needs documentation of its > current state Thanks for interesting archeology. Have been trying to improve the documentation, but will appreciate any help I can get. >From one PoV, whether intended or not, it could look like AutoCorrect was designed to make it easier (or to encourage) shifting over to Styles-based document production. This bug 90507 notes that Tools - AutoCorrect - Apply automatically changes all Default PS to Text Body (requested or not). [This has been documented since at least 2015, but now I have tried to clarify the "note" about this]. (Bug or not, this current behavior is consistent with promoting a styles-based approach, and makes it "easy" to get rid of unstyled (default) paragraphs from a document.) Bug 95433 notes (and objects to) that using choosing "Apply Styles" in [T] also changes Default PS to Text Body after Enter is used. (but is that a bug?, especially when user has chosen "Apply Styles"?) In both cases, these "bugs" could be seen as features to help insure the avoidance of unstyled paragraphs appearing in a document. But this potentially helpful behavior "collides" with the issue in bug 59034, namely that (many) [M] options only work with Default PS. In short, at present, this (speculative) "helpful" behavior described in bug 90507 and bug 95433 undercuts the possibility to make post-facto auto-correcting clean-up in a document (unless one is willing to remove all non-default PS). -- 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 90507] Tools - AutoCorrect - Apply converts non-empty "Default Paragraph Style" paragraphs to "Text Body" PS --even when no [M] options are selected
https://bugs.documentfoundation.org/show_bug.cgi?id=90507 --- Comment #10 from sdc.bla...@youmail.dk --- (In reply to V Stuart Foote from comment #9) > It is actually pretty handy "feature", but it needs documentation of its > current state Thanks for interesting archeology. Have been trying to improve the documentation, but will appreciate any help I can get. >From one PoV, whether intended or not, it could look like AutoCorrect was designed to make it easier (or to encourage) shifting over to Styles-based document production. This bug 90507 notes that Tools - AutoCorrect - Apply automatically changes all Default PS to Text Body (requested or not). [This has been documented since at least 2015, but now I have tried to clarify the "note" about this]. (Bug or not, this current behavior is consistent with promoting a styles-based approach, and makes it "easy" to get rid of unstyled (default) paragraphs from a document.) Bug 95433 notes (and objects to) that using choosing "Apply Styles" in [T] also changes Default PS to Text Body after Enter is used. (but is that a bug?, especially when user has chosen "Apply Styles"?) In both cases, these "bugs" could be seen as features to help insure the avoidance of unstyled paragraphs appearing in a document. But this potentially helpful behavior "collides" with the issue in bug 59034, namely that (many) [M] options only work with Default PS. In short, at present, this (speculative) "helpful" behavior described in bug 90507 and bug 95433 undercuts the possibility to make post-facto auto-correcting clean-up in a document (unless one is willing to remove all non-default PS). -- 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 139701] UI: Underline split button in regular toolbar
https://bugs.documentfoundation.org/show_bug.cgi?id=139701 --- Comment #4 from S.Zosgornik --- +1 the drop down arrow also helps to distinguish to the next right set of tools -- 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 139701] UI: Underline split button in regular toolbar
https://bugs.documentfoundation.org/show_bug.cgi?id=139701 --- Comment #4 from S.Zosgornik --- +1 the drop down arrow also helps to distinguish to the next right set of tools -- 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 59034] EDITING AutoCorrect's "Replace while modifying existing text" works only for Default style
https://bugs.documentfoundation.org/show_bug.cgi?id=59034 --- Comment #4 from sdc.bla...@youmail.dk --- (In reply to Commit Notification from comment #3) > Seth Chaiklin committed a patch related to this issue. > Relevant to: tdf#59034 mention that [M] only applies to Default The changes will appear in: https://help.libreoffice.org/7.2/en-US/text/shared/01/06040100.html but I already think that it is wrong --- While it seems that most [M] options only work with "default" PS, there are some exceptions (possibly post 2013) Tested with 7.2.0.0.alpha0+ *Only works with Default Paragraph Style* - Use replacement table - Correct TWo INitial CApitals - Delete spaces and tabs at beginning and end of paragraph - Combine single line paragraphs if length greater than.. *Works on many different Paragraph Styles.* Replace blank paragraphs Replace Custom Styles Will have to test further and adjust the documentation accordingly. (or hope that someone with greater insight into the matter will speak up.) (meanwhile, the OP is repro'ed with 7.2.0.0.alpha0+) -- 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 139914] New: Permission to open /opt directory to add extensions denied
https://bugs.documentfoundation.org/show_bug.cgi?id=139914 Bug ID: 139914 Summary: Permission to open /opt directory to add extensions denied Product: LibreOffice Version: 7.0.4.2 release Hardware: x86-64 (AMD64) OS: Linux (All) Status: UNCONFIRMED Severity: normal Priority: medium Component: Writer Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: gilbertd...@gmail.com Description: I have a spell checker extension (Antidote) which is stored in the /opt directory. Since version 7.0.4.2, this extension disappeared from Writer. I no longer have access to the /opt directory to add this extension. Steps to Reproduce: 1. Open LibreOffice 2. Hit Ctrl-Alt-E 3. Navigate to the system /opt directory 4. Click on it. Actual Results: Error message: Error opening directory '/opt': Permission denied Expected Results: Navigate to the extension subdirectory and add it to the program. Reproducible: Always User Profile Reset: Yes OpenGL enabled: Yes Additional Info: Version: 7.0.4.2 Compilation: 573028415b474775687f7355a6d413c41d013a01 Environment: Threads CPU: 2; OS: Linux 5.8 Interface utilisateur: UI Render: par défaut; VCL: gtk3 Locale: fr-CA (fr_CA.UTF-8); Langue IHM: fr-FR Divers: 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 139296] scrolling document canvas down & up can cause a line of text to "tear" with loss of registration, it clears when the line moves out of view far enough or view passes to
https://bugs.documentfoundation.org/show_bug.cgi?id=139296 --- Comment #32 from spokanemagn...@gmail.com --- Very good observation. This could be why I originally thought documents that were originally formatted in Word and later reformatted to Writer were immune to the text tearing problem…because I was NOT editing them. Later, when I edited my resume, which was originally written in Word, it started exhibiting the symptoms virtually every time I scrolled even just a few lines (i.e., extremely repeatable). This also might be a clue, as my resume has a lot of formatting (headers, footers, indents, tabs, and tables). Earlier, I noticed the problem when working with files using my technical notes template, which also has a lot of formatting (two different type fonts, three different font colors, two different background fill colors, bullet and number lists, numerous tables, and a header), but I have yet to notice it when working in my default letter template (which has virtually no formatting except page margins, type font and size). I also verified that if you have a line of text that is tearing and you highlight that line, the problem self-corrects on that line…but transfers the problem to the next line. So, you either have to scroll up or down until the bad line is off screen, reload the page, click the toggle automatic spell checking or toggle formatting marks buttons in the standard menu, or click to display the sidebar. To sum up what has been discovered to this point: • it seems to happen less frequently if Skia rendering is turned off and hardware acceleration switched on • it has nothing to do with the chosen font • it seems to be less severe if the font size is ≥12 points • it seems to happen less often if the line spacing is set to fixed and is ≥2 points greater than the font size • it seems to happen less often with the zoom level ≤100% • it seems to only happen with documents at least two or three pages in length • it seems to happen less often if all font sizes, line spacing, margins, headers/footers measurements, tabs, page width and length, etc. are all evenly divisible (or leave a one- or two-digit terminating decimal number (to avoid rounding errors???)) • it has nothing to do with animated text, direct cursor, math baseline alignment, displaying hidden text or paragraphs, sidebar open (or not), synchronized axis in grid resolution, etc. • it seems to happen less often if the units of measure are NOT in inches • it seems to happen less often if you avoid using the Normal (0.75ʺ) format page margin setting because the margins are messed up (left margin actually at 0.79ʺ) • it seems to happen less often if you change the page format size to letter, as it should NOT be set to A4 for US (probably connected to the point mentioned directly above as the paper size width for A4 is not 8.5ʺ, but is 8.27ʺ One thing I have not had time to investigate is ODF File Format 1.3 Extended versus using an earlier version. -- 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 59034] EDITING AutoCorrect's "Replace while modifying existing text" works only for Default style
https://bugs.documentfoundation.org/show_bug.cgi?id=59034 --- Comment #3 from Commit Notification --- Seth Chaiklin committed a patch related to this issue. It has been pushed to "master": https://git.libreoffice.org/help/commit/67826012b8b84e43e92bb7e8111981e3c51fee13 Relevant to: tdf#59034 mention that [M] only applies to Default -- 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 59034] EDITING AutoCorrect's "Replace while modifying existing text" works only for Default style
https://bugs.documentfoundation.org/show_bug.cgi?id=59034 Commit Notification changed: What|Removed |Added Whiteboard||target:7.2.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: helpcontent2
helpcontent2 |2 +- 1 file changed, 1 insertion(+), 1 deletion(-) New commits: commit 01ac21d99fb9945f9d3ab2fe3ed04e3c86fa5583 Author: Seth Chaiklin AuthorDate: Mon Jan 25 23:06:05 2021 +0100 Commit: Gerrit Code Review CommitDate: Mon Jan 25 23:06:05 2021 +0100 Update git submodules * Update helpcontent2 from branch 'master' to 67826012b8b84e43e92bb7e8111981e3c51fee13 - Relevant to: tdf#59034 mention that [M] only applies to Default tdf#59034 makes sensible request to document that [M] only applies to "Default Paragraph Style". (Made a few tests with 7.2.0.0.alpha0+ -- and this seems to still be true) Modified explanation of [M] to address this point. tdf#90507 notes that Tools - AutoCorrect - Apply will convert Default PS into "Text Body" PS. There is already a "note" that warns about this -- but it is not easy to understand, because it mentions "deselecting". (Was it added in 2015 in: https://help.libreoffice.org/4.3/Common/Options_3 by WikiSysop)? Testing shows that it is true, that if no M fields are selected, all Default PS are still converted to Text Body (as long as paragraph is non-empty -- in my tests). Have simplified and added point about being non-empty. tdf#95433 shows some confusion about when a Heading is created automatically, plus "help" is missing a critical feature (need for an uppercase letter). Also, explanation about higher heading levels is not clear. Have modified the description for "Apply Styles". + add a for Writer, with link to AutoCorrect commands * updated to , and Change-Id: Ib17c12a13a0aff58ebbbfd145cad7809b99cdb05 Reviewed-on: https://gerrit.libreoffice.org/c/help/+/109878 Tested-by: Jenkins Reviewed-by: Seth Chaiklin diff --git a/helpcontent2 b/helpcontent2 index a8f26cd4da64..67826012b8b8 16 --- a/helpcontent2 +++ b/helpcontent2 @@ -1 +1 @@ -Subproject commit a8f26cd4da648ffd80ed7292a5c9a2363ca4f153 +Subproject commit 67826012b8b84e43e92bb7e8111981e3c51fee13 ___ Libreoffice-commits mailing list libreoffice-comm...@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-commits
[Libreoffice-commits] help.git: source/text
source/text/shared/01/06040100.xhp | 83 - 1 file changed, 47 insertions(+), 36 deletions(-) New commits: commit 67826012b8b84e43e92bb7e8111981e3c51fee13 Author: Seth Chaiklin AuthorDate: Mon Jan 25 13:12:04 2021 +0100 Commit: Seth Chaiklin CommitDate: Mon Jan 25 23:06:05 2021 +0100 Relevant to: tdf#59034 mention that [M] only applies to Default tdf#59034 makes sensible request to document that [M] only applies to "Default Paragraph Style". (Made a few tests with 7.2.0.0.alpha0+ -- and this seems to still be true) Modified explanation of [M] to address this point. tdf#90507 notes that Tools - AutoCorrect - Apply will convert Default PS into "Text Body" PS. There is already a "note" that warns about this -- but it is not easy to understand, because it mentions "deselecting". (Was it added in 2015 in: https://help.libreoffice.org/4.3/Common/Options_3 by WikiSysop)? Testing shows that it is true, that if no M fields are selected, all Default PS are still converted to Text Body (as long as paragraph is non-empty -- in my tests). Have simplified and added point about being non-empty. tdf#95433 shows some confusion about when a Heading is created automatically, plus "help" is missing a critical feature (need for an uppercase letter). Also, explanation about higher heading levels is not clear. Have modified the description for "Apply Styles". + add a for Writer, with link to AutoCorrect commands * updated to , and Change-Id: Ib17c12a13a0aff58ebbbfd145cad7809b99cdb05 Reviewed-on: https://gerrit.libreoffice.org/c/help/+/109878 Tested-by: Jenkins Reviewed-by: Seth Chaiklin diff --git a/source/text/shared/01/06040100.xhp b/source/text/shared/01/06040100.xhp index 0b28bbcc3..0f948b6bd 100644 --- a/source/text/shared/01/06040100.xhp +++ b/source/text/shared/01/06040100.xhp @@ -20,7 +20,7 @@ - Options + Options (AutoCorrect) /text/shared/01/06040100.xhp @@ -58,28 +58,28 @@ -In text documents, you can choose to apply the AutoCorrect corrections while you type [T], or only when you modify existing text [M] with Tools - AutoCorrect - Apply. - When you choose to modify existing text with all options deselected, still all "Default" paragraph styles will be converted to "Text body" styles. see i72339Don't use inline switches for notes, tips and warnings. The icon will still show up. +In text documents, you can choose to apply the AutoCorrect corrections while you type [T], or by choosing Tools - AutoCorrect - Apply to modify existing text [M]. The [M] options are applied only to paragraphs with Default Paragraph Style. + All non-empty paragraphs with "Default Paragraph Style" are converted to "Text Body" paragraph style when Tools - AutoCorrect - Apply is used. see i72339Don't use inline switches for notes, tips and warnings. The icon will still show up. -Use replacement table +Use replacement table If you type a letter combination that matches a shortcut in the replacement table, the letter combination is replaced with the replacement text. - Correct TWo INitial CApitals + Correct TWo INitial CApitals If you type two uppercase letters at the beginning of a "WOrd", the second uppercase letter is automatically replaced with a lowercase letter. - Capitalize first letter of every sentence. + Capitalize first letter of every sentence. Capitalizes the first letter of every sentence. The first letter in a Calc cell will never be capitalized automatically.see i78661 -Automatic *bold*, /italic/, -strikeout- and _underline_ +Automatic *bold*, /italic/, -strikeout- and _underline_ Automatically applies bold, italic, strikethrough or underline formatting to text enclosed by asterisks (*), slashes (/), hyphens (-), and underscores (_), respectively. These characters disappear after the formatting is applied. This feature does not work if the formatting characters * / - _ are entered with an Input Method Editor. - URL Recognition + URL Recognition Automatically creates a hyperlink when you type a URL. UFI: moved "replace 1st" to Localized Options tab page, cws cbosdo01 - Replace DashesUFI: changed switches, added table, #61325#UFI: see i73558 for name: not the dashes are replaced but the hyphens (or even better the minus signs) + Replace DashesUFI: changed switches, added table, #61325#UFI: see i73558 for name: not the dashes are replaced but the hyphens (or even better the minus signs) Replaces one or two hyphens with a long dash (see the following table). Text will be replaced after you type a trailing white space (space, tab, or return). In the following table, the A and B represent text consisting of
[Libreoffice-bugs] [Bug 135895] Improve documentation about numbered lists without a list style (see comment 15)
https://bugs.documentfoundation.org/show_bug.cgi?id=135895 --- Comment #29 from sdc.bla...@youmail.dk --- (In reply to kitchm from comment #27) > While there are times when a person may do it as you described, many people > do not. Precisely. That is why I have asked how you have done it, so that I do not have to keep guessing. There multiple ways to use LO. The documentation seeks only to document those ways, not to push users into a particular workflow. The procedures I described in comment 26 were meant to reveal something about the behavior of LO (and then to ask the design team for feedback about whether it was intended). So let's look at your intended workflow > Where I want an outline or list, I start with > selecting the outline or list first, and only then do I add text. For example, would this correspond to what you do? A. Select Numbering First, Then add Entries 1. On Formatting bar, use dropdown menu in "Toggle Numbered List" icon to select 1),2),3) numbering scheme. Actual and expected result: 1) appears in document 2. Make an entry, then press Enter 3. Repeat for second line 4. Repeat for third line, but press Enter twice after third line. Result: There is a 4) after the first Enter, and then an empty paragraph after the second Enter. 5. On Formatting bar, use dropdown menu in Toggle Numbered List to select another numbering scheme (e.g., 1.2.3.) Result: The empty paragraph changes to 1. 6. Make three entries, without pressing return after the third. 7. On Formatting bar (or Bullets and Numbering bar), use dropdown menu to change numbering scheme to Roman numerals. Actual and expected result: Numbering scheme on second list changes, but the first list does not change. In other words, I have tried to follow your way of doing things (or at least I have guessed as closely as your description permits), but have not encountered the initial problem that you described. Now here is another way that (sort of) follows your (general procedure) but does produce the problem you have indicated. B. Select Numbering First, Then add Entries 1. Format > Lists > Numbered List 2. Make three entries. 3. Then add a few blank lines after the Numbered List. 4. Format > Lists > Numbered List Actual result: 4. appears in document (with a few blank lines above it, and the initial list with three entries, 1. 2. 3.). 5. Continuing from the 4., make some more entries in this "second" list. 6. (then I followed steps 4 to 6 in comment 0, namely, select the "list" below the blank lines, used dropdown box in the Bullets and Formatting toolbar to select a different outline type, and now both lists use the same numbering scheme, which is the problem that you reported. (You did not mention "Restart numbering" in your initial report, but, I suspect it is involved in someway in your workflow, which is creating the problem that you report. For example, in version B, if we apply "Restart Numbering" after step 4 and before starting step 5, then it looks like the "second list" is separate from the first, but when you change the numbering scheme for the "second list", then "first" list also changes. Is that what you did? If you have used yet another procedure to produce the problem that you reported, then please describe it. Thanks. -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-ux-advise] [Bug 135895] Improve documentation about numbered lists without a list style (see comment 15)
https://bugs.documentfoundation.org/show_bug.cgi?id=135895 --- Comment #29 from sdc.bla...@youmail.dk --- (In reply to kitchm from comment #27) > While there are times when a person may do it as you described, many people > do not. Precisely. That is why I have asked how you have done it, so that I do not have to keep guessing. There multiple ways to use LO. The documentation seeks only to document those ways, not to push users into a particular workflow. The procedures I described in comment 26 were meant to reveal something about the behavior of LO (and then to ask the design team for feedback about whether it was intended). So let's look at your intended workflow > Where I want an outline or list, I start with > selecting the outline or list first, and only then do I add text. For example, would this correspond to what you do? A. Select Numbering First, Then add Entries 1. On Formatting bar, use dropdown menu in "Toggle Numbered List" icon to select 1),2),3) numbering scheme. Actual and expected result: 1) appears in document 2. Make an entry, then press Enter 3. Repeat for second line 4. Repeat for third line, but press Enter twice after third line. Result: There is a 4) after the first Enter, and then an empty paragraph after the second Enter. 5. On Formatting bar, use dropdown menu in Toggle Numbered List to select another numbering scheme (e.g., 1.2.3.) Result: The empty paragraph changes to 1. 6. Make three entries, without pressing return after the third. 7. On Formatting bar (or Bullets and Numbering bar), use dropdown menu to change numbering scheme to Roman numerals. Actual and expected result: Numbering scheme on second list changes, but the first list does not change. In other words, I have tried to follow your way of doing things (or at least I have guessed as closely as your description permits), but have not encountered the initial problem that you described. Now here is another way that (sort of) follows your (general procedure) but does produce the problem you have indicated. B. Select Numbering First, Then add Entries 1. Format > Lists > Numbered List 2. Make three entries. 3. Then add a few blank lines after the Numbered List. 4. Format > Lists > Numbered List Actual result: 4. appears in document (with a few blank lines above it, and the initial list with three entries, 1. 2. 3.). 5. Continuing from the 4., make some more entries in this "second" list. 6. (then I followed steps 4 to 6 in comment 0, namely, select the "list" below the blank lines, used dropdown box in the Bullets and Formatting toolbar to select a different outline type, and now both lists use the same numbering scheme, which is the problem that you reported. (You did not mention "Restart numbering" in your initial report, but, I suspect it is involved in someway in your workflow, which is creating the problem that you report. For example, in version B, if we apply "Restart Numbering" after step 4 and before starting step 5, then it looks like the "second list" is separate from the first, but when you change the numbering scheme for the "second list", then "first" list also changes. Is that what you did? If you have used yet another procedure to produce the problem that you reported, then please describe it. Thanks. -- 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 95433] EDITING autocorrect option "Apply styles" causes Default Style paragraphs to change to "Text Body" paragraph style while typing
https://bugs.documentfoundation.org/show_bug.cgi?id=95433 V Stuart Foote changed: What|Removed |Added Version|3.5.0 release |Inherited From OOo -- 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 59034] EDITING AutoCorrect's "Replace while modifying existing text" works only for Default style
https://bugs.documentfoundation.org/show_bug.cgi?id=59034 V Stuart Foote changed: What|Removed |Added CC||vstuart.fo...@utsa.edu Version|3.6.4.3 release |Inherited From OOo -- 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 59036] EDITING AutoCorrect: "Remove blank paragraphs" will work for all styles, other "[M]" options only for Default
https://bugs.documentfoundation.org/show_bug.cgi?id=59036 V Stuart Foote changed: What|Removed |Added Version|3.6.4.3 release |Inherited From OOo -- 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 90507] Tools - AutoCorrect - Apply converts non-empty "Default Paragraph Style" paragraphs to "Text Body" PS --even when no [M] options are selected
https://bugs.documentfoundation.org/show_bug.cgi?id=90507 V Stuart Foote changed: What|Removed |Added Version|unspecified |Inherited From OOo -- 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 90507] Tools - AutoCorrect - Apply converts non-empty "Default Paragraph Style" paragraphs to "Text Body" PS --even when no [M] options are selected
https://bugs.documentfoundation.org/show_bug.cgi?id=90507 V Stuart Foote changed: What|Removed |Added Version|unspecified |Inherited From OOo -- 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: helpcontent2
helpcontent2 |2 +- 1 file changed, 1 insertion(+), 1 deletion(-) New commits: commit 5658d6a4961f321613e25828597bbadfcebee021 Author: Olivier Hallot AuthorDate: Mon Jan 25 18:26:44 2021 -0300 Commit: Gerrit Code Review CommitDate: Mon Jan 25 22:26:44 2021 +0100 Update git submodules * Update helpcontent2 from branch 'master' to a8f26cd4da648ffd80ed7292a5c9a2363ca4f153 - Use Imperative mode Change-Id: If1d4393608b22a4ae1fdc698ccea84feb911358c Reviewed-on: https://gerrit.libreoffice.org/c/help/+/109918 Tested-by: Jenkins Reviewed-by: Adolfo Jayme Barrientos diff --git a/helpcontent2 b/helpcontent2 index c637d9f61e63..a8f26cd4da64 16 --- a/helpcontent2 +++ b/helpcontent2 @@ -1 +1 @@ -Subproject commit c637d9f61e639170bcdb9e23d3cb08d2fc36d692 +Subproject commit a8f26cd4da648ffd80ed7292a5c9a2363ca4f153 ___ Libreoffice-commits mailing list libreoffice-comm...@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-commits
[Libreoffice-commits] help.git: source/text
source/text/shared/01/01100200.xhp |2 +- 1 file changed, 1 insertion(+), 1 deletion(-) New commits: commit a8f26cd4da648ffd80ed7292a5c9a2363ca4f153 Author: Olivier Hallot AuthorDate: Mon Jan 25 13:09:33 2021 -0300 Commit: Adolfo Jayme Barrientos CommitDate: Mon Jan 25 22:26:44 2021 +0100 Use Imperative mode Change-Id: If1d4393608b22a4ae1fdc698ccea84feb911358c Reviewed-on: https://gerrit.libreoffice.org/c/help/+/109918 Tested-by: Jenkins Reviewed-by: Adolfo Jayme Barrientos diff --git a/source/text/shared/01/01100200.xhp b/source/text/shared/01/01100200.xhp index 30c56e907..4216668af 100644 --- a/source/text/shared/01/01100200.xhp +++ b/source/text/shared/01/01100200.xhp @@ -77,6 +77,6 @@ Resets the editing time to zero, the creation date to the current date and time, and the version number to 1. The modification and printing dates are also deleted. Save preview image with this document Saves a thumbnail preview .png inside the document. This image may be used by a file manager under certain conditions. - If you want to disable generating thumbnails in general, then choose Tools - Options - LibreOffice - Advanced. Click the Open Expert Configuration button, and search for GenerateThumbnail. If this property has the value true, then double-click on it to set its value to false. + To disable generating thumbnails in general, choose Tools - Options - LibreOffice - Advanced. Click the Open Expert Configuration button, and search for GenerateThumbnail. If this property has the value true, then double-click on it to set its value to false. ___ Libreoffice-commits mailing list libreoffice-comm...@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-commits
