[Bug 161207] spam - GBOSLOT
https://bugs.documentfoundation.org/show_bug.cgi?id=161207 Stéphane Guillou (stragu) changed: What|Removed |Added URL|https://www.gboslot.com/| -- You are receiving this mail because: You are the assignee for the bug.
[Bug 161207] spam - GBOSLOT
https://bugs.documentfoundation.org/show_bug.cgi?id=161207 Stéphane Guillou (stragu) changed: What|Removed |Added Resolution|--- |INVALID Component|libabw |deletionRequest Summary|GBOSLOT |spam - GBOSLOT Status|UNCONFIRMED |RESOLVED Product|Document Liberation Project |LibreOffice -- You are receiving this mail because: You are the assignee for the bug.
[Bug 161207] GBOSLOT
https://bugs.documentfoundation.org/show_bug.cgi?id=161207 --- Comment #1 from Stéphane Guillou (stragu) --- The content of attachment 194256 has been deleted for the following reason: spam -- You are receiving this mail because: You are the assignee for the bug.
[Bug 156364] Fonts are displayed slightly different on Linux, which causes the characters to overlap
https://bugs.documentfoundation.org/show_bug.cgi?id=156364 Stéphane Guillou (stragu) changed: What|Removed |Added CC||stephane.guillou@libreoffic ||e.org --- Comment #6 from Stéphane Guillou (stragu) --- Can't see an overlap either on Ubuntu 22.04 + GNOME 42.9, 1× scaling, DPI 96×96, display 1600×900, with: Version: 24.8.0.0.alpha1+ (X86_64) / LibreOffice Community Build ID: ae798781ef4df7a1fdef13af0bc459bf4f6e7b4c CPU threads: 8; OS: Linux 6.5; UI render: default; VCL: gtk3 Locale: en-AU (en_AU.UTF-8); UI: en-US Calc: CL threaded -- You are receiving this mail because: You are the assignee for the bug.
[Bug 160919] UI: Release notes button is black on dark blue background if macOS's "increase contrast" setting is on
https://bugs.documentfoundation.org/show_bug.cgi?id=160919 Chas Belov changed: What|Removed |Added Ever confirmed|1 |0 Status|NEEDINFO|UNCONFIRMED --- Comment #2 from Chas Belov --- Current version info: Version: 24.2.3.2 (X86_64) / LibreOffice Community Build ID: 433d9c2ded56988e8a90e6b2e771ee4e6a5ab2ba CPU threads: 6; OS: macOS 14.5; UI render: Skia/Metal; VCL: osx Locale: en-US (en_US.UTF-8); UI: en-US Calc: threaded I don't know how to tell for sure what version I previously had. It's not in my downloads, and a search on current and past install.log files only turns up Adobe Acrobat on a search for the string "Libre". However, I believe it would have been one of the 23's and not 24.0 or 24.1. -- You are receiving this mail because: You are the assignee for the bug.
[Bug 160801] Writer crash when use clear formatting after insert page break (macOS only)
https://bugs.documentfoundation.org/show_bug.cgi?id=160801 --- Comment #6 from vika --- Clear formatting is proceeded from the Formatting toolbar. Insert page is proceeded from menu Insert | Page break. Writer crashes only on Mac when "Numeric with sublevels" is used for Heading numbering. I've recorded a short video: https://filesender.arnes.si/?s=download=d79d52b1-aa93-4672-a102-a51a37e55bae -- You are receiving this mail because: You are the assignee for the bug.
[Bug 160045] Writer Header cleared when pasting RTF
https://bugs.documentfoundation.org/show_bug.cgi?id=160045 --- Comment #4 from dave whitman --- Just updated to: Version: 24.2.3.2 (X86_64) / LibreOffice Community Build ID: 433d9c2ded56988e8a90e6b2e771ee4e6a5ab2ba CPU threads: 12; OS: Windows 10.0 Build 22631; UI render: Skia/Raster; VCL: win Locale: en-GB (en_GB); UI: en-US Calc: threaded When RTF text is pasted the text disappears from the header although now the header remains as well as the dividing line from the text! -- You are receiving this mail because: You are the assignee for the bug.
[Bug 101216] [META] Calc comment bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=101216 Bug 101216 depends on bug 158110, which changed state. Bug 158110 Summary: Copy/paste of Calc comments fails when more than one cell is copied https://bugs.documentfoundation.org/show_bug.cgi?id=158110 What|Removed |Added Status|ASSIGNED|RESOLVED Resolution|--- |FIXED -- You are receiving this mail because: You are the assignee for the bug.
[Bug 108479] [META] Paste special bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=108479 Bug 108479 depends on bug 158110, which changed state. Bug 158110 Summary: Copy/paste of Calc comments fails when more than one cell is copied https://bugs.documentfoundation.org/show_bug.cgi?id=158110 What|Removed |Added Status|ASSIGNED|RESOLVED Resolution|--- |FIXED -- You are receiving this mail because: You are the assignee for the bug.
core.git: sc/qa sc/source
sc/qa/uitest/pasteSpecial/tdf139858.py |7
sc/qa/uitest/pasteSpecial/tdf158110.py | 48 +
sc/qa/uitest/pasteSpecial/tdf160765.py |9 +-
sc/source/ui/miscdlgs/inscodlg.cxx |7 ++--
sc/source/ui/view/viewfun3.cxx | 21 --
5 files changed, 78 insertions(+), 14 deletions(-)
New commits:
commit 76941af9837406b1526b2f2d13c89df7a2023072
Author: Andreas Heinisch
AuthorDate: Mon May 6 14:53:19 2024 +0200
Commit: Andreas Heinisch
CommitDate: Wed May 22 07:27:32 2024 +0200
tdf#158110 - Paste special: Remove special ADDNOTES flag handling
Remove special ADDNOTES flag handling and just add it to existing NOTE flag
to ensure no content will be deleted. However, the check for empty cells needs
to be improved.
Change-Id: I44ae75aa3997a0b1041447106bc3c07146043351
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/167202
Reviewed-by: Andreas Heinisch
Tested-by: Jenkins
diff --git a/sc/qa/uitest/pasteSpecial/tdf139858.py
b/sc/qa/uitest/pasteSpecial/tdf139858.py
old mode 100755
new mode 100644
index ca81c7715cb6..b5689ec3fdca
--- a/sc/qa/uitest/pasteSpecial/tdf139858.py
+++ b/sc/qa/uitest/pasteSpecial/tdf139858.py
@@ -12,6 +12,7 @@ from uitest.framework import UITestCase
from libreoffice.calc.document import get_cell_by_position
from libreoffice.uno.propertyvalue import mkPropertyValues
from uitest.uihelper.calc import enter_text_to_cell
+from uitest.uihelper.common import get_state_as_dict
from libreoffice.calc.paste_special import reset_default_values
class tdf139858(UITestCase):
@@ -51,6 +52,12 @@ class tdf139858(UITestCase):
xCommentsChkBox = xPasteSpecialDlg.getChild("comments")
xCommentsChkBox.executeAction("CLICK", tuple())
+# After tdf#158110 when an existing comment is overwritten, a
confirmation dialog is shown
+xCheckWarningDlg = self.xUITest.getTopFocusWindow()
+if get_state_as_dict(xCheckWarningDlg)["ID"] ==
"CheckWarningDialog":
+xYesBtn = xCheckWarningDlg.getChild("yes")
+xYesBtn.executeAction("CLICK", tuple())
+
# Without the fix in place, this test would have failed with
# AssertionError: 'A1 sample text' != ''
# i.e., the cell content was overwritten
diff --git a/sc/qa/uitest/pasteSpecial/tdf158110.py
b/sc/qa/uitest/pasteSpecial/tdf158110.py
new file mode 100644
index ..9b0dba6ed8cd
--- /dev/null
+++ b/sc/qa/uitest/pasteSpecial/tdf158110.py
@@ -0,0 +1,48 @@
+# -*- tab-width: 4; indent-tabs-mode: nil; py-indent-offset: 4 -*-
+#
+# This file is part of the LibreOffice project.
+#
+# This Source Code Form is subject to the terms of the Mozilla Public
+# License, v. 2.0. If a copy of the MPL was not distributed with this
+# file, You can obtain one at http://mozilla.org/MPL/2.0/.
+#
+
+from uitest.framework import UITestCase
+
+from libreoffice.calc.document import get_cell_by_position
+from libreoffice.uno.propertyvalue import mkPropertyValues
+from libreoffice.calc.paste_special import reset_default_values
+
+class tdf158110(UITestCase):
+def test_tdf158110_paste_special_multiple_cells(self):
+with self.ui_test.create_doc_in_start_center("calc") as document:
+xGridWin = self.xUITest.getTopFocusWindow().getChild("grid_window")
+
+# Insert a comment in cell A1
+xGridWin.executeAction("SELECT", mkPropertyValues({"CELL":"A1"}))
+xArgs = mkPropertyValues({"Text": "Comment 1"})
+self.xUITest.executeCommandWithParameters(".uno:InsertAnnotation",
xArgs)
+
+# Copy cell range A1:A2 to clipboard
+xGridWin.executeAction("SELECT", mkPropertyValues({"RANGE":
"A1:A2"}))
+self.xUITest.executeCommand(".uno:Copy")
+
+# Paste data using special options (check only comments)
+xGridWin.executeAction("SELECT", mkPropertyValues({"CELL": "B1"}))
+with
self.ui_test.execute_dialog_through_command(".uno:PasteSpecial") as
xPasteSpecialDlg:
+reset_default_values(self, xPasteSpecialDlg)
+xDateTimeChkBox = xPasteSpecialDlg.getChild("datetime")
+xDateTimeChkBox.executeAction("CLICK", tuple())
+xTextChkBox = xPasteSpecialDlg.getChild("text")
+xTextChkBox.executeAction("CLICK", tuple())
+xNumbersChkBox = xPasteSpecialDlg.getChild("numbers")
+xNumbersChkBox.executeAction("CLICK", tuple())
+xCommentsChkBox = xPasteSpecialDlg.getChild("comments")
+xCommentsChkBox.executeAction("CLICK", tuple())
+
+# Without the fix in place, this test would have failed with
+# AssertionError: 'Comment 1' != ''
+# i.e., the comment was not copied
+self.assertEqual("Comment 1",
[Bug 157390] Converting PowerPoint PPTX to PDF causes overlap in artistic text characters
https://bugs.documentfoundation.org/show_bug.cgi?id=157390 Stéphane Guillou (stragu) changed: What|Removed |Added See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=16 ||0872 -- You are receiving this mail because: You are the assignee for the bug.
[Bug 103100] [META] Writer table bugs
https://bugs.documentfoundation.org/show_bug.cgi?id=103100 Stéphane Guillou (stragu) changed: What|Removed |Added Depends on||160872 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=160872 [Bug 160872] Overlapped character in Print / PDF when there is a vertical string of Kanji characters in a table -- You are receiving this mail because: You are the assignee for the bug.
[Bug 43808] [META] Right-To-Left and Complex Text Layout language issues (RTL/CTL)
https://bugs.documentfoundation.org/show_bug.cgi?id=43808 Stéphane Guillou (stragu) changed: What|Removed |Added Depends on||160872 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=160872 [Bug 160872] Overlapped character in Print / PDF when there is a vertical string of Kanji characters in a table -- You are receiving this mail because: You are the assignee for the bug.
[Bug 160872] Overlapped character in Print / PDF when there is a vertical string of Kanji characters in a table
https://bugs.documentfoundation.org/show_bug.cgi?id=160872 Stéphane Guillou (stragu) changed: What|Removed |Added Status|UNCONFIRMED |NEW CC||kha...@libreoffice.org, ||stephane.guillou@libreoffic ||e.org See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=15 ||7390 Summary|Printed results are |Overlapped character in |incorrect when there is a |Print / PDF when there is a |vertical string of Kanji|vertical string of Kanji |characters in a table. |characters in a table Ever confirmed|0 |1 Regression By||Khaled Hosny Blocks||43808, 103100 Component|Writer |Printing and PDF export --- Comment #5 from Stéphane Guillou (stragu) --- Reproduced in PDF export as well. Indeed, if the left cell's orientation is changed from Vertical to Horizontal, the issue is not reproduced. I bibisected with linux-64-7.5 repo to two commits, very similarly to bug 157390. (I am ignoring the table cells rendered off into the left margin, issue that is now resolved.) At build commit [caee3eee4bab84fb7e7f438ea1ff43496414f096], first row is missing its last few characters. This is: commit 60fd694ac362e9314f54fa992e31e8baa5bdf80f author Khaled HosnyTue Sep 06 00:56:37 2022 +0200 committer خالد حسني Tue Sep 06 15:05:39 2022 +0200 vcl: Add LogicalFontInstance::GetGlyphWidth() Reviewed-on: https://gerrit.libreoffice.org/c/core/+/139462 Later on, at build commit [e02e4eac04b0750cdd4e82ee0d7962033ca96786], the missing characters in row 1 are back but overlap previous characters - same as in a recent daily build. commit e5a797a9beb03b9d9759a94b98107f509a0d5488 author Khaled HosnySun Sep 18 13:04:05 2022 +0200 committer خالد حسني Mon Sep 19 13:38:52 2022 +0200 vcl: Fix Type 3 glyph widths Reviewed-on: https://gerrit.libreoffice.org/c/core/+/140126 Version: 24.8.0.0.alpha1+ (X86_64) / LibreOffice Community Build ID: ae798781ef4df7a1fdef13af0bc459bf4f6e7b4c CPU threads: 8; OS: Linux 6.5; UI render: default; VCL: gtk3 Locale: en-AU (en_AU.UTF-8); UI: en-US Calc: CL threaded Khaled, any chance you could have a look at this one and bug 157390, or should I ping John? Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=43808 [Bug 43808] [META] Right-To-Left and Complex Text Layout language issues (RTL/CTL) https://bugs.documentfoundation.org/show_bug.cgi?id=103100 [Bug 103100] [META] Writer table bugs -- You are receiving this mail because: You are the assignee for the bug.
[Bug 158288] When you select part of a column with merged cells, all columns that are part of the merged cell are selected
https://bugs.documentfoundation.org/show_bug.cgi?id=158288 --- Comment #9 from ady --- (In reply to Bigor from comment #0) > Expected Results: > selected a2:a5 Just click on any cell (so there is no "selected range"), then click on the upper-left "Name Box" and type-in "a2:a5" (without quotation marks). I am not sure about the consequences of applying any action to that selected a2:a5 range, considering that cell a4 is no longer just a4 alone. Now, while the selection itself is possible as I just mentioned, I agree with Aron in comment 5. I am not sure this should be considered a bug. FWIW, Calc already has some possibilities (on the individual cells that conform the merged area, a4:c4 in the example) that are not available in Excel (IIRC, but I cannot check it myself ATM). If you still need to perform actions on individual cells, them maybe they should not be really merged at all and the user should consider some alternative layout. Moreover, there are situations in which the current behavior is desired. Having said that, maybe the OP could provide some practical use-case where the request is more meaningful. -- You are receiving this mail because: You are the assignee for the bug.
[Bug 158288] When you select part of a column with merged cells, all columns that are part of the merged cell are selected
https://bugs.documentfoundation.org/show_bug.cgi?id=158288 --- Comment #9 from ady --- (In reply to Bigor from comment #0) > Expected Results: > selected a2:a5 Just click on any cell (so there is no "selected range"), then click on the upper-left "Name Box" and type-in "a2:a5" (without quotation marks). I am not sure about the consequences of applying any action to that selected a2:a5 range, considering that cell a4 is no longer just a4 alone. Now, while the selection itself is possible as I just mentioned, I agree with Aron in comment 5. I am not sure this should be considered a bug. FWIW, Calc already has some possibilities (on the individual cells that conform the merged area, a4:c4 in the example) that are not available in Excel (IIRC, but I cannot check it myself ATM). If you still need to perform actions on individual cells, them maybe they should not be really merged at all and the user should consider some alternative layout. Moreover, there are situations in which the current behavior is desired. Having said that, maybe the OP could provide some practical use-case where the request is more meaningful. -- You are receiving this mail because: You are on the CC list for the bug.
[Bug 161204] UI - dashed outline for active cell border
https://bugs.documentfoundation.org/show_bug.cgi?id=161204 --- Comment #3 from ady --- (In reply to Robert Lacroix from comment #0) > Fix this problem once-and-for-all by changing cell border for active and > selected cells to a dashed line using the normal colour for dashes and the > complementary colour between the dashes. There are some merits to the proposal, but also some potential conflicts. The solid "focus" (or active) line might conflict with some borders and other lines used in Calc, but dashed lines are also in use under other conditions. In LO 24.2, there have been some changes that affect how the active cell is shown/marked. For instance, there is a new optional Column/Row Highlighting setting. Further changes in up-coming versions will also have an impact on this matter. For example, the active cell/range indicator (the same we are discussing in this enhancement request) is shown slightly outside the cell, instead of overlapping with the cell's limits / grid / border. So maybe this enhancement request includes an interesting suggestion, but perhaps the aforementioned changes reduce the need for it. Using a 2-colors "dashed" surrounding line to mark the active cell/range might be worth consideration anyway. -- You are receiving this mail because: You are on the CC list for the bug.
[Bug 161204] UI - dashed outline for active cell border
https://bugs.documentfoundation.org/show_bug.cgi?id=161204 --- Comment #3 from ady --- (In reply to Robert Lacroix from comment #0) > Fix this problem once-and-for-all by changing cell border for active and > selected cells to a dashed line using the normal colour for dashes and the > complementary colour between the dashes. There are some merits to the proposal, but also some potential conflicts. The solid "focus" (or active) line might conflict with some borders and other lines used in Calc, but dashed lines are also in use under other conditions. In LO 24.2, there have been some changes that affect how the active cell is shown/marked. For instance, there is a new optional Column/Row Highlighting setting. Further changes in up-coming versions will also have an impact on this matter. For example, the active cell/range indicator (the same we are discussing in this enhancement request) is shown slightly outside the cell, instead of overlapping with the cell's limits / grid / border. So maybe this enhancement request includes an interesting suggestion, but perhaps the aforementioned changes reduce the need for it. Using a 2-colors "dashed" surrounding line to mark the active cell/range might be worth consideration anyway. -- You are receiving this mail because: You are the assignee for the bug.
[Bug 160801] Writer crash when use clear formatting after insert page break (macOS only)
https://bugs.documentfoundation.org/show_bug.cgi?id=160801 Stéphane Guillou (stragu) changed: What|Removed |Added CC||stephane.guillou@libreoffic ||e.org Status|UNCONFIRMED |NEEDINFO Ever confirmed|0 |1 --- Comment #5 from Stéphane Guillou (stragu) --- (In reply to vika from comment #3) > Steps: > 1. Insert page break before Heading 1 > 2. Clear formatting on the new page. > On Mac crash, on WIN does not. Can you please clarify the steps? What exactly do you use for "clear formatting"? Is it Format > Clear Direct Formatting? And what do you mean by "new page"? The blank page before Heading 1? -- You are receiving this mail because: You are the assignee for the bug.
[Bug 161207] GBOSLOT
https://bugs.documentfoundation.org/show_bug.cgi?id=161207 casinogboslot changed: What|Removed |Added URL||https://www.gboslot.com/ -- You are receiving this mail because: You are the assignee for the bug.
[Bug 161207] New: GBOSLOT
https://bugs.documentfoundation.org/show_bug.cgi?id=161207 Bug ID: 161207 Summary: GBOSLOT Product: Document Liberation Project Version: unspecified Hardware: All OS: All Status: UNCONFIRMED Severity: normal Priority: medium Component: libabw Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: bulanjelita...@gmail.com Created attachment 194256 --> https://bugs.documentfoundation.org/attachment.cgi?id=194256=edit GBOSLOT daftar gboslot disini bisa langsung wd besar dengan bermain slot rekomendasi yang ada. -- You are receiving this mail because: You are the assignee for the bug.
[Bug 108815] [META] Print range/area bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=108815 BogdanB changed: What|Removed |Added Depends on||155768 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=155768 [Bug 155768] PRINTING: If "Default" cell style has border, black lines bleed over the printing range IF page border is also applied in default page style -- You are receiving this mail because: You are the assignee for the bug.
[Bug 155768] PRINTING: If "Default" cell style has border, black lines bleed over the printing range IF page border is also applied in default page style
https://bugs.documentfoundation.org/show_bug.cgi?id=155768 BogdanB changed: What|Removed |Added Summary|PRINTING: If "Default" cell |PRINTING: If "Default" cell |style has border, black |style has border, black |lines bleed over the|lines bleed over the |printing range IF page |printing range IF page |border is also applied in |border is also applied in |default page style. |default page style CC||buzea.bog...@libreoffice.or ||g Blocks||108815 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=108815 [Bug 108815] [META] Print range/area bugs and enhancements -- You are receiving this mail because: You are the assignee for the bug.
[Bug 136524] [META] Performance/hang/lag/high CPU issues
https://bugs.documentfoundation.org/show_bug.cgi?id=136524 BogdanB changed: What|Removed |Added Depends on||158543 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=158543 [Bug 158543] Lots of CPU time used when moving a table left/right or up/down with arrow keys (or when dragging) but no lag -- You are receiving this mail because: You are the assignee for the bug.
[Bug 108364] [META] Table/Row/Column/Cell management function bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=108364 BogdanB changed: What|Removed |Added Depends on||158543 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=158543 [Bug 158543] Lots of CPU time used when moving a table left/right or up/down with arrow keys (or when dragging) but no lag -- You are receiving this mail because: You are the assignee for the bug.
[Bug 158543] Lots of CPU time used when moving a table left/right or up/down with arrow keys (or when dragging) but no lag
https://bugs.documentfoundation.org/show_bug.cgi?id=158543 BogdanB changed: What|Removed |Added CC||buzea.bog...@libreoffice.or ||g Blocks||108364, 136524 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=108364 [Bug 108364] [META] Table/Row/Column/Cell management function bugs and enhancements https://bugs.documentfoundation.org/show_bug.cgi?id=136524 [Bug 136524] [META] Performance/hang/lag/high CPU issues -- You are receiving this mail because: You are the assignee for the bug.
[Bug 115930] [META] Adding and deleting cells / rows / columns
https://bugs.documentfoundation.org/show_bug.cgi?id=115930 BogdanB changed: What|Removed |Added Depends on||160851 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=160851 [Bug 160851] Hiding rows or columns in Calc causes severe lag -- You are receiving this mail because: You are the assignee for the bug.
[Bug 160851] Hiding rows or columns in Calc causes severe lag
https://bugs.documentfoundation.org/show_bug.cgi?id=160851 BogdanB changed: What|Removed |Added Blocks||115930 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=115930 [Bug 115930] [META] Adding and deleting cells / rows / columns -- You are receiving this mail because: You are the assignee for the bug.
[Bug 160851] Hiding rows or columns in Calc causes severe lag
https://bugs.documentfoundation.org/show_bug.cgi?id=160851 BogdanB changed: What|Removed |Added Blocks||136524 CC||buzea.bog...@libreoffice.or ||g Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=136524 [Bug 136524] [META] Performance/hang/lag/high CPU issues -- You are receiving this mail because: You are the assignee for the bug.
[Bug 136524] [META] Performance/hang/lag/high CPU issues
https://bugs.documentfoundation.org/show_bug.cgi?id=136524 BogdanB changed: What|Removed |Added Depends on||160851 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=160851 [Bug 160851] Hiding rows or columns in Calc causes severe lag -- You are receiving this mail because: You are the assignee for the bug.
[Bug 108519] [META] Page break bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=108519 BogdanB changed: What|Removed |Added Depends on||158938 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=158938 [Bug 158938] Writer loses page break character (0x0C) when utf-8 file is saved -- You are receiving this mail because: You are the assignee for the bug.
[Bug 158938] Writer loses page break character (0x0C) when utf-8 file is saved
https://bugs.documentfoundation.org/show_bug.cgi?id=158938 BogdanB changed: What|Removed |Added CC||buzea.bog...@libreoffice.or ||g Summary|Writer loses page break |Writer loses page break |character (0x0C) when utf-8 |character (0x0C) when utf-8 |file is saved. |file is saved 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.
[Bug 161022] [META] Word-breaking / line-breaking issues
https://bugs.documentfoundation.org/show_bug.cgi?id=161022 BogdanB changed: What|Removed |Added Depends on||151162 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=151162 [Bug 151162] Inserting a Word Joiner Unicode character doesn't always prevent a line break from occurring -- You are receiving this mail because: You are the assignee for the bug.
[Bug 151162] Inserting a Word Joiner Unicode character doesn't always prevent a line break from occurring
https://bugs.documentfoundation.org/show_bug.cgi?id=151162 BogdanB changed: What|Removed |Added Blocks||102345, 161022 CC||buzea.bog...@libreoffice.or ||g Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=102345 [Bug 102345] [META] Formatting marks (aka Non-printing characters) bugs and enhancements https://bugs.documentfoundation.org/show_bug.cgi?id=161022 [Bug 161022] [META] Word-breaking / line-breaking issues -- You are receiving this mail because: You are the assignee for the bug.
[Bug 102345] [META] Formatting marks (aka Non-printing characters) bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=102345 BogdanB changed: What|Removed |Added Depends on||151162 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=151162 [Bug 151162] Inserting a Word Joiner Unicode character doesn't always prevent a line break from occurring -- You are receiving this mail because: You are the assignee for the bug.
[Bug 159052] Line break '\n' is changed to '\r\n' when copy text from shape
https://bugs.documentfoundation.org/show_bug.cgi?id=159052 BogdanB changed: What|Removed |Added CC||buzea.bog...@libreoffice.or ||g Blocks||161022 Summary|line break '\n' is changed |Line break '\n' is changed |to '\r\n' when copy text|to '\r\n' when copy text |from shape |from shape Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=161022 [Bug 161022] [META] Word-breaking / line-breaking issues -- You are receiving this mail because: You are the assignee for the bug.
[Bug 161022] [META] Word-breaking / line-breaking issues
https://bugs.documentfoundation.org/show_bug.cgi?id=161022 BogdanB changed: What|Removed |Added Depends on||159052 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=159052 [Bug 159052] Line break '\n' is changed to '\r\n' when copy text from shape -- You are receiving this mail because: You are the assignee for the bug.
[Bug 150285] [META] Problems with Kashida, Justified Arabic/Persian text
https://bugs.documentfoundation.org/show_bug.cgi?id=150285 BogdanB changed: What|Removed |Added Depends on||161153 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=161153 [Bug 161153] Inserting tashdid (a.k.a. shaddah) character (Unicode 0651) breaks or distorts Persian text -- You are receiving this mail because: You are the assignee for the bug.
[Bug 161153] Inserting tashdid (a.k.a. shaddah) character (Unicode 0651) breaks or distorts Persian text
https://bugs.documentfoundation.org/show_bug.cgi?id=161153 BogdanB changed: What|Removed |Added CC||buzea.bog...@libreoffice.or ||g Blocks||71732, 150285 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=71732 [Bug 71732] [META] Bugs related to text rendering, typography and font features in LO https://bugs.documentfoundation.org/show_bug.cgi?id=150285 [Bug 150285] [META] Problems with Kashida, Justified Arabic/Persian text -- You are receiving this mail because: You are the assignee for the bug.
[Bug 71732] [META] Bugs related to text rendering, typography and font features in LO
https://bugs.documentfoundation.org/show_bug.cgi?id=71732 BogdanB changed: What|Removed |Added Depends on||161153 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=161153 [Bug 161153] Inserting tashdid (a.k.a. shaddah) character (Unicode 0651) breaks or distorts Persian text -- You are receiving this mail because: You are the assignee for the bug.
[Bug 161202] Hiding a section containing a table leads to unintended page breaks
https://bugs.documentfoundation.org/show_bug.cgi?id=161202 BogdanB changed: What|Removed |Added Summary|hiding a section containing |Hiding a section containing |a table leads to unintended |a table leads to unintended |page breaks |page breaks -- You are receiving this mail because: You are the assignee for the bug.
[Bug 161202] hiding a section containing a table leads to unintended page breaks
https://bugs.documentfoundation.org/show_bug.cgi?id=161202 BogdanB changed: What|Removed |Added Blocks||107738, 108519 CC||buzea.bog...@libreoffice.or ||g Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=107738 [Bug 107738] [META] Section bugs and enhancements 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.
[Bug 108519] [META] Page break bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=108519 BogdanB changed: What|Removed |Added Depends on||161202 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=161202 [Bug 161202] hiding a section containing a table leads to unintended page breaks -- You are receiving this mail because: You are the assignee for the bug.
[Bug 107738] [META] Section bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=107738 BogdanB changed: What|Removed |Added Depends on||161202 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=161202 [Bug 161202] hiding a section containing a table leads to unintended page breaks -- You are receiving this mail because: You are the assignee for the bug.
[Bug 160918] FORMCONTROLS: Add ability to sort tab order by alphanumeric based on form control name
https://bugs.documentfoundation.org/show_bug.cgi?id=160918 --- Comment #6 from Steve --- I have attached 2 ODTs and their exported PDFs. The field names are already assigned alpha field names according to the tab order I desire. 1.1.01, 1.1.02 etc. Try tabbing through the 'Automatic Sort' PDF - it shows the limitations of 'Automatic Sort'. Now try tabbing through the 'Alpha Sort' PDF - hopefully you will agree it has much better usability. This is a short form and took me 5 minutes to manually fix the sort order. If I had an Alpha Sort feature it would be done in an instant, and with less chance of error. Longer forms take ... much longer. I hope this helps explain the request. This is an efficiency issue with pretty much every PDF form I create with Writer. -- You are receiving this mail because: You are the assignee for the bug.
[Bug 160918] FORMCONTROLS: Add ability to sort tab order by alphanumeric based on form control name
https://bugs.documentfoundation.org/show_bug.cgi?id=160918 --- Comment #5 from Steve --- Created attachment 194255 --> https://bugs.documentfoundation.org/attachment.cgi?id=194255=edit Complex tab sort order example - sorted manually by alpha PDF -- You are receiving this mail because: You are the assignee for the bug.
[Bug 160918] FORMCONTROLS: Add ability to sort tab order by alphanumeric based on form control name
https://bugs.documentfoundation.org/show_bug.cgi?id=160918 --- Comment #4 from Steve --- Created attachment 194254 --> https://bugs.documentfoundation.org/attachment.cgi?id=194254=edit Complex tab sort order example - sorted manually by alpha ODT -- You are receiving this mail because: You are the assignee for the bug.
[Bug 160918] FORMCONTROLS: Add ability to sort tab order by alphanumeric based on form control name
https://bugs.documentfoundation.org/show_bug.cgi?id=160918 --- Comment #3 from Steve --- Created attachment 194253 --> https://bugs.documentfoundation.org/attachment.cgi?id=194253=edit Complex tab sort order example - sorted by Automatic Sort PDF -- You are receiving this mail because: You are the assignee for the bug.
[Bug 160918] FORMCONTROLS: Add ability to sort tab order by alphanumeric based on form control name
https://bugs.documentfoundation.org/show_bug.cgi?id=160918 --- Comment #2 from Steve --- Created attachment 194252 --> https://bugs.documentfoundation.org/attachment.cgi?id=194252=edit Complex tab sort order example - sorted by Automatic Sort ODT -- You are receiving this mail because: You are the assignee for the bug.
core.git: Branch 'libreoffice-24-2' - android/source
android/source/res/values-ca/strings.xml |2 +- android/source/res/values-eo/strings.xml |2 ++ android/source/res/values-iw/strings.xml |2 ++ android/source/res/values-ja/strings.xml | 29 + android/source/res/values-uk/strings.xml | 14 ++ 5 files changed, 48 insertions(+), 1 deletion(-) New commits: commit 6abd859a8265838e2ac01221aedfbaf54a725e65 Author: Weblate AuthorDate: Mon May 20 12:36:51 2024 +0200 Commit: Michael Weghorn CommitDate: Wed May 22 05:55:34 2024 +0200 android-viewer translated using Weblate Ukrainian currently translated at 100.0% (132 of 132 strings) Change-Id: I4ee59322448e4cf264ecb809ae4ff3fd50544d8c Added translation for android-viewer using Weblate (Hebrew) Change-Id: I210051045b09b343d678be0e20cb983146f1ef88 android-viewer translated using Weblate Japanese currently translated at 56.8% (75 of 132 strings) Change-Id: Ia98cc4b886712602cd409724b5ffd2e716b89e18 android-viewer translated using Weblate Japanese currently translated at 55.3% (73 of 132 strings) Change-Id: I5409b94082b4712ae961df0409970e058d45d57d Added translation for android-viewer using Weblate (Esperanto) Change-Id: Iaeb01145eb5f33066c3f4bbf21db2017e606da69 android-viewer translated using Weblate Japanese currently translated at 53.7% (71 of 132 strings) Change-Id: I20e43eb7376e160771152e55b6325f2dc59bf70a android-viewer translated using Weblate Catalan currently translated at 100.0% (132 of 132 strings) Change-Id: I2661d61745e4664a228f1c1d9d1f9eb1fd83a109 android-viewer translated using Weblate Japanese currently translated at 34.8% (46 of 132 strings) Change-Id: Ie6b66ae3c2c878463f7c413fd77397e698bc Co-authored-by: Adolfo Jayme Barrientos Co-authored-by: Taichi Haradaguchi <20001...@ymail.ne.jp> Co-authored-by: Weblate Co-authored-by: Weblate Co-authored-by: Євген Кондратюк Translate-URL: https://translations.documentfoundation.org/projects/android-viewer/android-strings-24-2/ca/ Translate-URL: https://translations.documentfoundation.org/projects/android-viewer/android-strings-24-2/ja/ Translate-URL: https://translations.documentfoundation.org/projects/android-viewer/android-strings-24-2/uk/ Translation: android-viewer/android-strings-24-2 Reviewed-on: https://gerrit.libreoffice.org/c/core/+/167771 Tested-by: Jenkins Reviewed-by: Michael Weghorn diff --git a/android/source/res/values-ca/strings.xml b/android/source/res/values-ca/strings.xml index 40cd9511c45c..a37184e13cdf 100644 --- a/android/source/res/values-ca/strings.xml +++ b/android/source/res/values-ca/strings.xml @@ -92,7 +92,7 @@ Amplada òptima D\'acord D\'acord -Introduïu la longitud addicional en centèsimes de mil·límetre. +Introduïu la longitud addicional en centèsimes de mil·límetre Afegeix un full de càlcul No s\'ha trobat cap càmera Mida mitjana diff --git a/android/source/res/values-eo/strings.xml b/android/source/res/values-eo/strings.xml new file mode 100644 index ..a6b3daec9354 --- /dev/null +++ b/android/source/res/values-eo/strings.xml @@ -0,0 +1,2 @@ + + \ No newline at end of file diff --git a/android/source/res/values-iw/strings.xml b/android/source/res/values-iw/strings.xml new file mode 100644 index ..a6b3daec9354 --- /dev/null +++ b/android/source/res/values-iw/strings.xml @@ -0,0 +1,2 @@ + + \ No newline at end of file diff --git a/android/source/res/values-ja/strings.xml b/android/source/res/values-ja/strings.xml index 4996be06def2..09b86e3ffaca 100644 --- a/android/source/res/values-ja/strings.xml +++ b/android/source/res/values-ja/strings.xml @@ -46,4 +46,33 @@ 前を検索 このファイルは読み取り専用です。 キャンセル +最高品質 +挿入オプションを選択: +戻る +新規表計算ドキュメント +ワークシート名を変更 +ドキュメントの保存に失敗しました。 +新規図形描画 +スライドを削除 +やり直す +最近開いたファイル +ドキュメントを保存しています… +ワークシートを削除 +いいえ +新規文書ドキュメント +ワークシートの追加 +新規プレゼンテーション +戻る +パスワードを入力してください +削除オプションを選択: +キーボードを表示 +写真を選択 +カメラが見つかりません +表の挿入 +スライドを追加 +文字 +スタイル +値 +PDFにエクスポートできません +ファイルを保存できません \ No newline at end of file diff --git a/android/source/res/values-uk/strings.xml b/android/source/res/values-uk/strings.xml index e6048cc3dff0..837ec6d50656 100644 --- a/android/source/res/values-uk/strings.xml +++ b/android/source/res/values-uk/strings.xml @@ -118,4 +118,18 @@ Символ Встановити типову мову Bmp має нульове значення! +ОК +Збереження не завершено. Були якісь зміни? +Підкреслений +Неможливо продовжити. +Жирний +LibreOffice Browser +Пошук +Оглядач LibreOffice \'Beta\' +Викреслити +Ключове слово не знайдено +Налаштування +Каталог не збережено. +Нахилений +Ваш
[Bug 103302] [META] Writer's web layout/view bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=103302 Stéphane Guillou (stragu) changed: What|Removed |Added Depends on||160890 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=160890 [Bug 160890] Pagination appears suddenly in web view in Writer when text gets very long -- You are receiving this mail because: You are the assignee for the bug.
[Bug 160890] Pagination appears suddenly in web view in Writer when text gets very long
https://bugs.documentfoundation.org/show_bug.cgi?id=160890 Stéphane Guillou (stragu) changed: What|Removed |Added Blocks||103302 Component|Writer |Writer Web Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=103302 [Bug 103302] [META] Writer's web layout/view bugs and enhancements -- You are receiving this mail because: You are the assignee for the bug.
[Bug 160890] Pagination appears suddenly in web view in Writer when text gets very long
https://bugs.documentfoundation.org/show_bug.cgi?id=160890 Stéphane Guillou (stragu) changed: What|Removed |Added CC||stephane.guillou@libreoffic ||e.org Version|24.2.2.2 release|Inherited From OOo Status|UNCONFIRMED |RESOLVED Resolution|--- |NOTABUG --- Comment #3 from Stéphane Guillou (stragu) --- (In reply to Mike Kaganski from comment #1) > No, it was always this way. The "web view" is implemented using 10 meter > long pages. Let's close as "not a bug" then. -- You are receiving this mail because: You are the assignee for the bug.
[Bug 106179] [META] Writer comment bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=106179 james heal changed: What|Removed |Added URL||https://www.toobit.com/en-U ||S/price/TRB --- Comment #84 from james heal --- Discover the latest TRB crypto price data on Toobit, including real-time market updates and comprehensive news coverage to keep you informed about the TRB market cap and trends. https://www.toobit.com/en-US/price/TRB -- You are receiving this mail because: You are the assignee for the bug.
[Bug 160895] LibreOffice freezes on document open
https://bugs.documentfoundation.org/show_bug.cgi?id=160895 skybirds...@gmail.com changed: What|Removed |Added Status|NEEDINFO|UNCONFIRMED Ever confirmed|1 |0 --- Comment #3 from skybirds...@gmail.com --- Tested the new version, still reproducible. It does happen with all components except the database. I tried safe mode and removing my user profile, but the same issue persisted. -- You are receiving this mail because: You are the assignee for the bug.
[Bug 73292] FILESAVE: saving as .uot makes page size microscopic (only when Inches used)
https://bugs.documentfoundation.org/show_bug.cgi?id=73292 Jim Avera changed: What|Removed |Added Summary|FILESAVE: saving as .uot|FILESAVE: saving as .uot |make page size microscopic |makes page size microscopic |(only when Inches used) |(only when Inches used) -- You are receiving this mail because: You are the assignee for the bug.
[Bug 122652] [META] Memory problems in LibreOffice
https://bugs.documentfoundation.org/show_bug.cgi?id=122652 Stéphane Guillou (stragu) changed: What|Removed |Added Depends on||157994 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=157994 [Bug 157994] "Error in writing sub-document content.xml", with large files -- You are receiving this mail because: You are the assignee for the bug.
[Bug 157994] "Error in writing sub-document content.xml", with large files
https://bugs.documentfoundation.org/show_bug.cgi?id=157994 Stéphane Guillou (stragu) changed: What|Removed |Added Blocks||122652 Status|UNCONFIRMED |NEW CC||stephane.guillou@libreoffic ||e.org Ever confirmed|0 |1 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=122652 [Bug 122652] [META] Memory problems in LibreOffice -- You are receiving this mail because: You are the assignee for the bug.
[Bug 160892] "Write Error. Error in writing sub-document SfxBaseModel::storeSelf: 0x70c23..."
https://bugs.documentfoundation.org/show_bug.cgi?id=160892 Stéphane Guillou (stragu) changed: What|Removed |Added Resolution|--- |DUPLICATE Status|UNCONFIRMED |RESOLVED CC||stephane.guillou@libreoffic ||e.org --- Comment #9 from Stéphane Guillou (stragu) --- (In reply to rgz92 from comment #8) > However as > mentioned, the issue is not present with the same file on another PC with > inferior specs, so it may still be a corrupt file issue, just not a file in > the user folder. What should I check? Maybe keep an eye on memory use while editing the file? Some related reports, showing the issue has been popping up on and off over the years: - bug 60769 - bug 109049 - bug 112235 - bug 157994 seems to point to a RAM issue In any case, pCoud link does not work anymore, and pastebin link neither. I think we should consolidate into bug 157994. *** This bug has been marked as a duplicate of bug 157994 *** -- You are receiving this mail because: You are the assignee for the bug.
[Bug 157994] "Error in writing sub-document content.xml", with large files
https://bugs.documentfoundation.org/show_bug.cgi?id=157994 Stéphane Guillou (stragu) changed: What|Removed |Added CC||razmikghazaryan@protonmail. ||com --- Comment #15 from Stéphane Guillou (stragu) --- *** Bug 160892 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are the assignee for the bug.
[Bug 73292] FILESAVE: saving as .uot make page size microscopic (only when Inches used)
https://bugs.documentfoundation.org/show_bug.cgi?id=73292 --- Comment #24 from Jim Avera --- Still present in master (May 20, 2024) Version: 24.8.0.0.alpha1+ (X86_64) / LibreOffice Community Build ID: 101b08fe1ec77ffe8c1a9b2b8f9f20884269a1ed CPU threads: 12; OS: Linux 6.5; UI render: default; VCL: gtk3 Locale: en-US (en_US.UTF-8); UI: en-US Calc: threaded SIMPLIFIED REPRO INSTRUCTIONS: 1. Verify (or set) Tools->Options->LibreOfficeDev Writer->General->Measurement unit to "Inch" 2. Load any writer document which uses US Letter size (8.5" x 11" Portrait) (such as sample attached to this bug) 3. File->SaveAs and select Unified Office Format (.uot) as the file type; Save 4. File->Reload RESULTS: The content vanishes Format->Page Style->Page shows Format: User Width: 0.04" hEIGHT: 0.04" -- You are receiving this mail because: You are the assignee for the bug.
[Bug 73292] FILESAVE: saving as .uot make page size microscopic (only when Inches used)
https://bugs.documentfoundation.org/show_bug.cgi?id=73292 Jim Avera changed: What|Removed |Added Summary|FILESAVE: saving as .uot|FILESAVE: saving as .uot |results in microscopic page |make page size microscopic |size when re-opened (only |(only when Inches used) |when Inches used) | -- You are receiving this mail because: You are the assignee for the bug.
[Bug 112235] FILESAVE Unable to save with lost linked image: Error in writing sub-document content.xml
https://bugs.documentfoundation.org/show_bug.cgi?id=112235 Stéphane Guillou (stragu) changed: What|Removed |Added URL||https://ask.libreoffice.org ||/en/question/90164/cannot-s ||ave-file-error-in-writing-s ||ub-document-contentxml/ -- You are receiving this mail because: You are the assignee for the bug.
[Bug 160980] Jenkins TB78 WiX builds of msi package are not signed
https://bugs.documentfoundation.org/show_bug.cgi?id=160980 QA Administrators changed: What|Removed |Added Whiteboard|| QA:needsComment -- You are receiving this mail because: You are the assignee for the bug.
[Bug 157614] Contextual menus span over 2 screens making them difficult to read
https://bugs.documentfoundation.org/show_bug.cgi?id=157614 --- Comment #3 from QA Administrators --- Dear spacetrash, 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.
[Bug 160974] Hide Open Remote commands from popup menus
https://bugs.documentfoundation.org/show_bug.cgi?id=160974 QA Administrators changed: What|Removed |Added Whiteboard|| QA:needsComment -- You are receiving this mail because: You are the assignee for the bug.
[Bug 160973] Hide Open Remote commands from Tabbed UI
https://bugs.documentfoundation.org/show_bug.cgi?id=160973 QA Administrators changed: What|Removed |Added Whiteboard|| QA:needsComment -- You are receiving this mail because: You are the assignee for the bug.
[Bug 89389] form control shapes loose link with their control when grouped
https://bugs.documentfoundation.org/show_bug.cgi?id=89389 --- Comment #8 from QA Administrators --- Dear Lionel Elie Mamane, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.
[Bug 156466] FILESAVE DOC: Saved file made Word hang
https://bugs.documentfoundation.org/show_bug.cgi?id=156466 --- Comment #3 from QA Administrators --- Dear Regina Henschel, 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.
[Bug 87825] Incorrect filename in title bar (CMIS)
https://bugs.documentfoundation.org/show_bug.cgi?id=87825 --- Comment #13 from QA Administrators --- Dear beimaginativeegroup, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.
[Bug 49195] References in doc-files are not displayed
https://bugs.documentfoundation.org/show_bug.cgi?id=49195 --- Comment #13 from QA Administrators --- Dear Aleksey, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.
[Bug 148772] Text in Word 2007 DOCX table shown with a vertical layout instead of an horizontal layout (OK if resaved in MSO)
https://bugs.documentfoundation.org/show_bug.cgi?id=148772 --- Comment #15 from QA Administrators --- Dear Rom M., To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.
[Bug 148741] FILEOPEN DOCX: Image on different page compared to ODT (and older LibreOffice versions)
https://bugs.documentfoundation.org/show_bug.cgi?id=148741 --- Comment #5 from QA Administrators --- Dear Telesto, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.
[Bug 147113] grid not aligning with row and column headers after upgrade.
https://bugs.documentfoundation.org/show_bug.cgi?id=147113 --- Comment #4 from QA Administrators --- Dear Archie, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.
[Bug 160891] Feature request: better pageless mode
https://bugs.documentfoundation.org/show_bug.cgi?id=160891 Stéphane Guillou (stragu) changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED CC||stephane.guillou@libreoffic ||e.org Resolution|--- |DUPLICATE Whiteboard| QA:needsComment| --- Comment #1 from Stéphane Guillou (stragu) --- (In reply to espinosa_cz from comment #0) > This is a new feature request. Sorry if this is not the right place to do so. Thanks for the suggestion! This is the right place to file those :) This was already requested in bug 160111, which lead to opening bug 160185, which was closed as duplicate of bug 37817. Let's close as duplicate of bug 37817, as I also think it covers what you are after. Let us know if you disagree, or feel free to comment on bug 37817 if you think the discussion is missing something (for example, it doesn' yet mention "Google Docs' Pageless mode"). *** This bug has been marked as a duplicate of bug 37817 *** -- You are receiving this mail because: You are the assignee for the bug.
[Bug 37817] Add a view mode without page margins, header/footer and rulers (comment 13)
https://bugs.documentfoundation.org/show_bug.cgi?id=37817 Stéphane Guillou (stragu) changed: What|Removed |Added CC||espinosa...@centrum.cz --- Comment #28 from Stéphane Guillou (stragu) --- *** Bug 160891 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are the assignee for the bug.
[Bug 160769] LibreOffice 24.2 Document recovery (from timed autoSave) doesn't restore all open files after crash
https://bugs.documentfoundation.org/show_bug.cgi?id=160769 --- Comment #11 from bikehel...@gmail.com --- (In reply to Stéphane Guillou (stragu) from comment #10) > I think solutions like bug 146769 and bug 117237 should be prioritised, > instead of some users relying on killing the process to restore all > documents. > > But considering some users are surprised by the new behaviour, I'm wondering > if the dialog could somehow show all files, but differentiate between > modified and unmodified ones, like two sections with "Needs recovering" and > "Changes already saved" headers, still giving the options to restore > unmodified. That would make it clear what might have missing data, and what > definitely wouldn't. > Just a thought. There's no need to reinvent the wheel here. Standard behaviour in Windows is to stick a * in front of the filename if it needs saving. Although not universal, I have seen that in Linux Distros and MacOS as well. You can use the same dialog window, with all files present, and just stick a * on the ones with unsaved changes. If the list is sorted alphabetically, that should also put them straight at the top. Then put two buttons below: [Recover All Documents] [Recover Only Unsaved Documents] to determine the recovery behaviour that the user gets. And then put in a new confirmation when exiting LibreOffice from the File menu specifically (not the X in the top right), similar to the Opera Web Browser. "Reopen all documents at next start?" [Yes] [No] [Cancel] (Not the wording of Opera's, but you get the idea once you've tried it once or twice.) And then as a final quality of life update (This would require larger code changes), have it backup the open documents (on exiting) to the working drive so that even if the originals disappear, it can fully recover everything at the next start - both modified and unmodified - if desired. This should be toggleable in the Settings in the Load/Save area. Likely beside the "Always create a backup copy" option, which saves backups onto the working drive when saving. I would split that to two options if implemented, "Always create a backup copy when saving", and "Always create a backup when exiting LibreOffice" If this is implemented, it should alert you if the original for reopened documents is no longer present. The type of person using this feature regularly would want to know if suddenly their original has been renamed/deleted/etc from outside of the program. So this adds a lot of polish on top, for that type of user, in that you are treating their precious documents as extra important. By slightly modifying the recovery feature you effectively add a full secondary backup layer to LibreOffice - unless they shut it off. At least a few people would heap praise on the programmers if implemented right. The wording that I would use (on a bright banner bar at the top of the open document) would be: "This document was not found at the previous filename and location. Please re-save this or reopen the original if necessary." That alerts the user to go re-open it if it changed from (for example) "2024-03 Quarterly Inventory.ods" to "2024 Q1 Quarterly Inventory.ods", etc.; they either go open the proper one and save to it, or re-save the open one and continue on from there. It avoids them accidentally splitting their document into two chains when they (or someone else) were doing folder/filename cleanup. That's about all the gotchas that I can think of. With that implemented, it becomes an incredibly handy feature for one type of user. Even with only a limited / first part implementation, it's much more useful than what we have now. I hope that helps a programmer that doesn't need this at all, to understand a feature implementation that would be very useful to some other types of users. -- You are receiving this mail because: You are the assignee for the bug.
[Bug 160894] When I utilize the "optimal height" feature to adjust row heights in CALC the screen goes crazy
https://bugs.documentfoundation.org/show_bug.cgi?id=160894 --- Comment #5 from Stéphane Guillou (stragu) --- (oh, and I tested with the sheet "Overlaod Relays Thermal Unit Selector_2", which is the one focused on fileopen. Is that the one you mean?) -- You are receiving this mail because: You are the assignee for the bug.
[Bug 160894] When I utilize the "optimal height" feature to adjust row heights in CALC the screen goes crazy
https://bugs.documentfoundation.org/show_bug.cgi?id=160894 Stéphane Guillou (stragu) changed: What|Removed |Added Ever confirmed|0 |1 Status|UNCONFIRMED |NEEDINFO CC||stephane.guillou@libreoffic ||e.org --- Comment #4 from Stéphane Guillou (stragu) --- Can you share a video or at least a screenshot of the visual issues? Have you tried turning off "Use hardware acceleration" in Tools > Options > LibreOffice > View? I can't reproduce on Ubuntu 22.04 + GNOME 42.9 with 7.6.7.2, 24.2.3.2, nor a recent daily build: Version: 24.8.0.0.alpha1+ (X86_64) / LibreOffice Community Build ID: ae798781ef4df7a1fdef13af0bc459bf4f6e7b4c CPU threads: 8; OS: Linux 6.5; UI render: default; VCL: gtk3 Locale: en-AU (en_AU.UTF-8); UI: en-US Calc: CL threaded -- You are receiving this mail because: You are the assignee for the bug.
[Bug 105948] [META] Undo/Redo bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=105948 Aron Budea changed: What|Removed |Added Depends on||161172 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=161172 [Bug 161172] UNDO incomplete: list level is not restored in a specific document -- You are receiving this mail because: You are the assignee for the bug.
[Bug 160895] LibreOffice freezes on document open
https://bugs.documentfoundation.org/show_bug.cgi?id=160895 --- Comment #2 from Stéphane Guillou (stragu) --- Also: does it happen with all components? Writer, Calc, Draw, Impress...? -- You are receiving this mail because: You are the assignee for the bug.
[Bug 158288] When you select part of a column with merged cells, all columns that are part of the merged cell are selected
https://bugs.documentfoundation.org/show_bug.cgi?id=158288 --- Comment #8 from Aron Budea --- Let's see if my understanding if correct: - When you merge A4 to C4, there's no A4 cell anymore, only A4:C4 range, - A range is a rectangular area of cells, - When you select cells using Shift, or hold the left mouse button and drag, you select a range. This implies once the cells are merged in the example, there is no A2:A5 range anymore, and the smallest range including A2:A5 (and consequently A4:C4) is A2:C5. I'm not arguing there shouldn't be a way to select the least amount of cells+ranges that come with selection of cells, it just won't be a range anymore, and it should be a separate way apart from range selection. (In reply to Eyal Rozenberg from comment #7) > This seems like a bug to me, because it denies us the expressive potential > of the selection. We can choose to select a 3x5 region covering the merged > cell; and we can (try to) select 1x5 region, in one of 3 ways (left, middle, > right). Why should all four user behaviors result in the same thing, while > almost no mouse-down selection behavior can produce a selection of > a1,a2,a3,merged-a4-through-c4,a5 ? I see no argument in this comment why the selection you're looking for shouldn't be done in a different way, perhaps would be good to think about that first, instead of fragmenting the behavior by adding a compatibility flag. -- You are receiving this mail because: You are the assignee for the bug.
[Bug 158288] When you select part of a column with merged cells, all columns that are part of the merged cell are selected
https://bugs.documentfoundation.org/show_bug.cgi?id=158288 --- Comment #8 from Aron Budea --- Let's see if my understanding if correct: - When you merge A4 to C4, there's no A4 cell anymore, only A4:C4 range, - A range is a rectangular area of cells, - When you select cells using Shift, or hold the left mouse button and drag, you select a range. This implies once the cells are merged in the example, there is no A2:A5 range anymore, and the smallest range including A2:A5 (and consequently A4:C4) is A2:C5. I'm not arguing there shouldn't be a way to select the least amount of cells+ranges that come with selection of cells, it just won't be a range anymore, and it should be a separate way apart from range selection. (In reply to Eyal Rozenberg from comment #7) > This seems like a bug to me, because it denies us the expressive potential > of the selection. We can choose to select a 3x5 region covering the merged > cell; and we can (try to) select 1x5 region, in one of 3 ways (left, middle, > right). Why should all four user behaviors result in the same thing, while > almost no mouse-down selection behavior can produce a selection of > a1,a2,a3,merged-a4-through-c4,a5 ? I see no argument in this comment why the selection you're looking for shouldn't be done in a different way, perhaps would be good to think about that first, instead of fragmenting the behavior by adding a compatibility flag. -- You are receiving this mail because: You are on the CC list for the bug.
[Bug 160895] LibreOffice freezes on document open
https://bugs.documentfoundation.org/show_bug.cgi?id=160895 Stéphane Guillou (stragu) changed: What|Removed |Added Whiteboard| QA:needsComment| Status|UNCONFIRMED |NEEDINFO Ever confirmed|0 |1 CC||stephane.guillou@libreoffic ||e.org --- Comment #1 from Stéphane Guillou (stragu) --- Thank you for the report. Can you please: - test version 24.2.3 to see if it is still reproducible - if the issue persists, backup and remove your user profile: https://wiki.documentfoundation.org/UserProfile#Manual_procedure_(all_versions) -- You are receiving this mail because: You are the assignee for the bug.
[Bug 160904] Remove "= and <>" from "Search criteria = and <> must apply to whole cells"
https://bugs.documentfoundation.org/show_bug.cgi?id=160904 Stéphane Guillou (stragu) changed: What|Removed |Added Status|UNCONFIRMED |NEW Ever confirmed|0 |1 CC||heiko.tietze@documentfounda ||tion.org, ||stephane.guillou@libreoffic ||e.org --- Comment #5 from Stéphane Guillou (stragu) --- Setting to "new" as something needs to be done. Heiko, opinion on the wording? -- You are receiving this mail because: You are the assignee for the bug.
[Bug 161204] UI - dashed outline for active cell border
https://bugs.documentfoundation.org/show_bug.cgi?id=161204 --- Comment #2 from Robert Lacroix --- (In reply to m_a_riosv from comment #1) > Please attach a sample file, reduce the size as much as possible without > private information, and paste the information in Menu/Help/About > LibreOffice, there is a copy icon. Won't the colour of the border of the active cell depend on the user's platform, and not necessarily on the contents of a workbook? It's blue for me, the same colour as the row and column indicators. Version: 7.4.7.2 / LibreOffice Community Build ID: 40(Build:2) CPU threads: 12; OS: Linux 6.6; UI render: default; VCL: gtk3 Locale: en-CA (en_CA.UTF-8); UI: en-US Debian package version: 4:7.4.7-1+deb12u1 Calc: threaded -- You are receiving this mail because: You are the assignee for the bug.
[Bug 161204] UI - dashed outline for active cell border
https://bugs.documentfoundation.org/show_bug.cgi?id=161204 --- Comment #2 from Robert Lacroix --- (In reply to m_a_riosv from comment #1) > Please attach a sample file, reduce the size as much as possible without > private information, and paste the information in Menu/Help/About > LibreOffice, there is a copy icon. Won't the colour of the border of the active cell depend on the user's platform, and not necessarily on the contents of a workbook? It's blue for me, the same colour as the row and column indicators. Version: 7.4.7.2 / LibreOffice Community Build ID: 40(Build:2) CPU threads: 12; OS: Linux 6.6; UI render: default; VCL: gtk3 Locale: en-CA (en_CA.UTF-8); UI: en-US Debian package version: 4:7.4.7-1+deb12u1 Calc: threaded -- You are receiving this mail because: You are on the CC list for the bug.
[Bug 160905] Vertical and horizontal page shift when viewing the document in separate windows -- Make this position independent of ZOOM_FACTORS, VIEVING_MODES and WINDOWS_SIZES
https://bugs.documentfoundation.org/show_bug.cgi?id=160905 --- Comment #3 from Stéphane Guillou (stragu) --- (In reply to Stéphane Guillou (stragu) from comment #2) > Thank you for the report and the nice video demo. > This is essentially already tracked in bug 43253 and bug 116372 ...and bug 129827. -- You are receiving this mail because: You are the assignee for the bug.
[Bug 113396] [META] Single, book and multi-page view bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=113396 Stéphane Guillou (stragu) changed: What|Removed |Added Depends on||129827 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=129827 [Bug 129827] "New Window" split windows, changing page view affects all open windows -- You are receiving this mail because: You are the assignee for the bug.
[Bug 129827] "New Window" split windows, changing page view affects all open windows
https://bugs.documentfoundation.org/show_bug.cgi?id=129827 Stéphane Guillou (stragu) changed: What|Removed |Added Blocks||113396 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=113396 [Bug 113396] [META] Single, book and multi-page view bugs and enhancements -- You are receiving this mail because: You are the assignee for the bug.
[Bug 116372] VIEWING: Page jumps relative to ruler when switching to another window of the same document
https://bugs.documentfoundation.org/show_bug.cgi?id=116372 Stéphane Guillou (stragu) changed: What|Removed |Added See Also|https://bugs.documentfounda | |tion.org/show_bug.cgi?id=16 | |0905| -- You are receiving this mail because: You are the assignee for the bug.
[Bug 141843] [META] Bugs when file opened in multiple windows
https://bugs.documentfoundation.org/show_bug.cgi?id=141843 Stéphane Guillou (stragu) changed: What|Removed |Added Depends on|160905 | Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=160905 [Bug 160905] Vertical and horizontal page shift when viewing the document in separate windows -- Make this position independent of ZOOM_FACTORS, VIEVING_MODES and WINDOWS_SIZES -- You are receiving this mail because: You are the assignee for the bug.
[Bug 106773] [META] Writer document canvas view / viewport jump issues
https://bugs.documentfoundation.org/show_bug.cgi?id=106773 Stéphane Guillou (stragu) changed: What|Removed |Added Depends on|160905 | Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=160905 [Bug 160905] Vertical and horizontal page shift when viewing the document in separate windows -- Make this position independent of ZOOM_FACTORS, VIEVING_MODES and WINDOWS_SIZES -- You are receiving this mail because: You are the assignee for the bug.
[Bug 160905] Vertical and horizontal page shift when viewing the document in separate windows -- Make this position independent of ZOOM_FACTORS, VIEVING_MODES and WINDOWS_SIZES
https://bugs.documentfoundation.org/show_bug.cgi?id=160905 Stéphane Guillou (stragu) changed: What|Removed |Added Whiteboard| QA:needsComment| Blocks|106773, 141843 | CC||stephane.guillou@libreoffic ||e.org See Also|https://bugs.documentfounda | |tion.org/show_bug.cgi?id=11 | |6372| Status|UNCONFIRMED |RESOLVED Resolution|--- |DUPLICATE --- Comment #2 from Stéphane Guillou (stragu) --- Thank you for the report and the nice video demo. This is essentially already tracked in bug 43253 and bug 116372 (see their numerous duplicates), so marking this one as a duplicate too. Please feel free to comment there if you think some details are missing. *** This bug has been marked as a duplicate of bug 43253 *** Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=106773 [Bug 106773] [META] Writer document canvas view / viewport jump issues https://bugs.documentfoundation.org/show_bug.cgi?id=141843 [Bug 141843] [META] Bugs when file opened in multiple windows -- You are receiving this mail because: You are the assignee for the bug.
[Bug 43253] Zooming in "New Window" split view
https://bugs.documentfoundation.org/show_bug.cgi?id=43253 Stéphane Guillou (stragu) changed: What|Removed |Added CC||piotr.os...@gmail.com --- Comment #25 from Stéphane Guillou (stragu) --- *** Bug 160905 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are the assignee for the bug.
[Bug 160910] Clicking at the end of a line sends at the start of the next one, when there's a line break.
https://bugs.documentfoundation.org/show_bug.cgi?id=160910 Stéphane Guillou (stragu) changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED CC||stephane.guillou@libreoffic ||e.org Resolution|--- |WORKSFORME --- Comment #4 from Stéphane Guillou (stragu) --- (In reply to Kalytis from comment #3) > Can't reproduce anymore on 24.2.3.2. OK, let's close as "works for me" then. If it pops up again, feel free to set back to "unconfirmed". -- You are receiving this mail because: You are the assignee for the bug.
[Bug 160769] LibreOffice 24.2 Document recovery (from timed autoSave) doesn't restore all open files after crash
https://bugs.documentfoundation.org/show_bug.cgi?id=160769 --- Comment #10 from Stéphane Guillou (stragu) --- I think solutions like bug 146769 and bug 117237 should be prioritised, instead of some users relying on killing the process to restore all documents. But considering some users are surprised by the new behaviour, I'm wondering if the dialog could somehow show all files, but differentiate between modified and unmodified ones, like two sections with "Needs recovering" and "Changes already saved" headers, still giving the options to restore unmodified. That would make it clear what might have missing data, and what definitely wouldn't. Just a thought. -- You are receiving this mail because: You are the assignee for the bug.
[Bug 100155] [META] Improve object selection and alignment
https://bugs.documentfoundation.org/show_bug.cgi?id=100155 Stéphane Guillou (stragu) changed: What|Removed |Added Depends on||128394 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=128394 [Bug 128394] Writer: Make multiple frames selectable -- You are receiving this mail because: You are the assignee for the bug.
[Bug 128394] Writer: Make multiple frames selectable
https://bugs.documentfoundation.org/show_bug.cgi?id=128394 Stéphane Guillou (stragu) changed: What|Removed |Added Blocks||100155 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=100155 [Bug 100155] [META] Improve object selection and alignment -- You are receiving this mail because: You are the assignee for the bug.
[Bug 128394] Writer: Make multiple frames selectable
https://bugs.documentfoundation.org/show_bug.cgi?id=128394 Stéphane Guillou (stragu) changed: What|Removed |Added Version|unspecified |Inherited From OOo CC||stephane.guillou@libreoffic ||e.org --- Comment #2 from Stéphane Guillou (stragu) --- Same in OOo 3.3. -- You are receiving this mail because: You are the assignee for the bug.
