[Bug 161507] SCALC_BUG_IN_FORMATTING_FOOTER
https://bugs.documentfoundation.org/show_bug.cgi?id=161507 ady changed: What|Removed |Added Status|UNCONFIRMED |NEEDINFO Ever confirmed|0 |1 -- You are receiving this mail because: You are the assignee for the bug.
[Bug 161294] Slides: command line export-to of selected slides
https://bugs.documentfoundation.org/show_bug.cgi?id=161294 Stéphane Guillou (stragu) changed: What|Removed |Added Ever confirmed|0 |1 Status|UNCONFIRMED |NEEDINFO --- Comment #7 from Stéphane Guillou (stragu) --- (In reply to Timur from comment #6) > Export to PDF is fine and would fulfill the purpose of the request. This currently works for Impress documents: libreoffice24.2 --headless --convert-to 'pdf:impress_pdf_Export:{"PageRange":{"type":"string","value":"2-3"}}' sample.odp Does that cover it? -- You are receiving this mail because: You are the assignee for the bug.
[Bug 161512] button disabled
https://bugs.documentfoundation.org/show_bug.cgi?id=161512 ady changed: What|Removed |Added OS|macOS (All) |All Version|7.5.1.2 release |6.0.0.3 release -- You are receiving this mail because: You are the assignee for the bug.
[Bug 161512] button disabled
https://bugs.documentfoundation.org/show_bug.cgi?id=161512 ady changed: What|Removed |Added Status|NEEDINFO|NEW --- Comment #1 from ady --- This is strange, and not so easy to reproduce – it requires special attention to the details of the STR. I can reproduce on MS Windows, but (the order of) the steps seems key. Basically: [ENTER] != "accept" icon Always start the following steps with a new empty Calc spreadsheet. 1. Cell A5: =A1 (accept the formula by clicking on the "accept" icon that occupies the same location as the equal sign on the formula bar, not by pressing a key on the keyboard). 1.1. You should still have the focus on cell A5. This is key. 2. Add the icon with the "Formula to Value" command to the standard toolbar. > The button is shown as expected. But: 1. Cell A5: =A1 [ENTER] 1.1. You should have the focus on cell A6 (i.e. on a cell that has no formula). 2. Add the icon with the "Formula to Value" command to the standard toolbar. > The button is grayed out. Another method: 1. Add the icon with the "Formula to Value" command to the standard toolbar. 2. Cell A5: =A1 [ENTER] 2.1. You should have the focus on cell A6 (i.e. on a cell that has no formula). > The button in the toolbar is grayed out. 3. Focus on cell A5. 4. Menu Data > Calculate > Formula to Value. 5. Undo once ([CTRL]+[Z] on Windows). > The button in the toolbar is shown as expected. Reproduced with LO 6.0 and up to 24.8 alpha. I have not tested with older versions than LO 6.0. The problem is that the behavior is inconsistent, because it depends on the exact steps (instead of working for any cell with a formula), and whether the formula was introduced with the “accept” icon (so we end still on a cell with formula), or instead we end the formula with [ENTER] (so we end on a cell without formula). I can even have one spreadsheet with the button grayed out, while on another window with a second spreadsheet (with the same exact content and the focus is located on the equivalent cell, just introduced with different steps) the button will be shown correctly. In some versions, when performing menu Data > Calculate > Formula to Value the content of the cell is not updated immediately (i.e. still shows a formula, not the value only). Changing the focus to another cell and back to the original cell will refresh the view of the content of the cell, displaying the expected value (no longer the formula). Whether related to the problem on the button or not, this shows that there is some refresh problem with this feature. -- You are receiving this mail because: You are the assignee for the bug.
[Bug 161469] NOW() Function in Calc Macro Omits Sub-Seconds
https://bugs.documentfoundation.org/show_bug.cgi?id=161469 Andreas Heinisch changed: What|Removed |Added Ever confirmed|0 |1 Status|UNCONFIRMED |NEW --- Comment #5 from Andreas Heinisch --- Repro in: Version: 7.6.1.2 (X86_64) / LibreOffice Community Build ID: f5defcebd022c5bc36bbb79be232cb6926d8f674 CPU threads: 16; OS: Windows 10.0 Build 22631; UI render: Skia/Raster; VCL: win Locale: en-GB (de_DE); UI: en-GB Calc: CL threaded Code pointer: https://opengrok.libreoffice.org/xref/core/basic/source/runtime/methods.cxx#2117 -- You are receiving this mail because: You are the assignee for the bug.
[Bug 161315] 'Empty' can't be used as a default value for arguments (Option Compatible)
https://bugs.documentfoundation.org/show_bug.cgi?id=161315 Andreas Heinisch changed: What|Removed |Added Ever confirmed|0 |1 Status|UNCONFIRMED |NEW --- Comment #1 from Andreas Heinisch --- Repro in: Version: 7.6.1.2 (X86_64) / LibreOffice Community Build ID: f5defcebd022c5bc36bbb79be232cb6926d8f674 CPU threads: 16; OS: Windows 10.0 Build 22631; UI render: Skia/Raster; VCL: win Locale: en-GB (de_DE); UI: en-GB Calc: CL threaded -- You are receiving this mail because: You are the assignee for the bug.
[Bug 100290] Header/Footer with different First Page/Left & Right Content - Margins & Spacing can't be changed once set
https://bugs.documentfoundation.org/show_bug.cgi?id=100290 --- Comment #6 from Martin Sourada --- Still present in: Version: 24.2.4.2 (AARCH64) / LibreOffice Community Build ID: 51a6219feb6075d9a4c46691dcfe0cd9c4fff3c2 CPU threads: 8; OS: macOS 14.5; UI render: Skia/Raster; VCL: osx Locale: cs-CZ (cs_CZ.UTF-8); UI: cs-CZ Calc: threaded -- You are receiving this mail because: You are the assignee for the bug.
[Bug 140879] [META] Console noise
https://bugs.documentfoundation.org/show_bug.cgi?id=140879 Bug 140879 depends on bug 152050, which changed state. Bug 152050 Summary: "Childwindow slot missing" debug console noise when using Calc https://bugs.documentfoundation.org/show_bug.cgi?id=152050 What|Removed |Added Status|NEW |RESOLVED Resolution|--- |FIXED -- You are receiving this mail because: You are the assignee for the bug.
[Bug 152050] "Childwindow slot missing" debug console noise when using Calc
https://bugs.documentfoundation.org/show_bug.cgi?id=152050 Mike Kaganski changed: What|Removed |Added CC||noelgran...@gmail.com Status|NEW |RESOLVED Resolution|--- |FIXED --- Comment #4 from Mike Kaganski --- Fixed by commit d57861bc1526122024a8f8d9051582ca22e1d7be (SAL_WARN->SAL_INFO in SfxDispatcher, 2023-09-01). As told in the commit message, "nobody cares if child window slot is missing". -- You are receiving this mail because: You are the assignee for the bug.
[Bug 150884] [META] Sparklines bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=150884 Bug 150884 depends on bug 152050, which changed state. Bug 152050 Summary: "Childwindow slot missing" debug console noise when using Calc https://bugs.documentfoundation.org/show_bug.cgi?id=152050 What|Removed |Added Status|NEW |RESOLVED Resolution|--- |FIXED -- You are receiving this mail because: You are the assignee for the bug.
[Bug 161516] Label "Compare Document…" menu (and toolbars menu items) action more clearly, to indicate comparison direction
https://bugs.documentfoundation.org/show_bug.cgi?id=161516 Stéphane Guillou (stragu) changed: What|Removed |Added CC||libreoffice-ux-advise@lists ||.freedesktop.org, ||stephane.guillou@libreoffic ||e.org Ever confirmed|0 |1 Status|UNCONFIRMED |NEW Keywords||needsUXEval --- Comment #1 from Stéphane Guillou (stragu) --- I agree this is confusing and is an issue that needs resolving. (In reply to Jeff Fortin Tam from comment #0) > "Compare Document with a Previous Version…" > (if that's indeed what it does) I feel like using terms that relate to recency or relative age is not the right solution. A user might be comparing their version of a document with another person's version, with diverging histories but no clear "before" and "after". The help[1] does use "newer" vs "older": > You should always start with opening the newer document and compare it with > the > older document. Maybe using a term like "reference" or "base" would be better? But really, I feel like this feature should have an intermediate step that lets the user choose which document is the base and which one is compared to the base, because the current UX is very, very poor: 1. open base document 2. compare 3. see that direction is wrong 4. close document 5. open modified document 6. compare, now in the right direction UX/Design team, opinions? Band-aid relabel, or more involved (but possibly a interesting easyHack) intermediate step? [1]: https://help.libreoffice.org/latest/en-US/text/shared/guide/redlining_doccompare.html -- You are receiving this mail because: You are the assignee for the bug.
[Bug 161516] Label "Compare Document…" menu (and toolbars menu items) action more clearly, to indicate comparison direction
https://bugs.documentfoundation.org/show_bug.cgi?id=161516 Stéphane Guillou (stragu) changed: What|Removed |Added CC||libreoffice-ux-advise@lists ||.freedesktop.org, ||stephane.guillou@libreoffic ||e.org Ever confirmed|0 |1 Status|UNCONFIRMED |NEW Keywords||needsUXEval --- Comment #1 from Stéphane Guillou (stragu) --- I agree this is confusing and is an issue that needs resolving. (In reply to Jeff Fortin Tam from comment #0) > "Compare Document with a Previous Version…" > (if that's indeed what it does) I feel like using terms that relate to recency or relative age is not the right solution. A user might be comparing their version of a document with another person's version, with diverging histories but no clear "before" and "after". The help[1] does use "newer" vs "older": > You should always start with opening the newer document and compare it with > the > older document. Maybe using a term like "reference" or "base" would be better? But really, I feel like this feature should have an intermediate step that lets the user choose which document is the base and which one is compared to the base, because the current UX is very, very poor: 1. open base document 2. compare 3. see that direction is wrong 4. close document 5. open modified document 6. compare, now in the right direction UX/Design team, opinions? Band-aid relabel, or more involved (but possibly a interesting easyHack) intermediate step? [1]: https://help.libreoffice.org/latest/en-US/text/shared/guide/redlining_doccompare.html -- You are receiving this mail because: You are on the CC list for the bug.
[Bug 146932] CJK font-size in Writer default paragraph style is not the same as Western font
https://bugs.documentfoundation.org/show_bug.cgi?id=146932 Tom changed: What|Removed |Added Status|UNCONFIRMED |NEEDINFO Ever confirmed|0 |1 --- Comment #8 from Tom --- While waiting for this bug to be addressed, I came upon a workaround that could be useful. My action is as follows: How to Get Around It: To begin, launch Writer and go to "Tools > Options > Language Settings > Language" to enable CJK and Complex. "Styles > Manage Styles" (or hit F11) is the second step. Move the cursor to the Default Paragraph Style and then click the "Modify" button. Fourth, on the Font tab, manually adjust the Western and CJK font widths to 10.5pt or 12pt, whichever you want. Now that I've made these adjustments, the Western and CJK font sizes are identical and reflect the value I entered. For the time being, this workaround will keep the Western and CJK default font sizes aligned, but in an ideal world, they would automatically be the same. Even in the most recent master build, this problem has been there since version 6.1. Gnome is installed on Fedora 34. tested at https://atlasdoorrepair.com/ This problem has been around since at least version 6.1, and it continues to be a problem in the master build that is currently being used. Fedora 34 with Gnome is the operating system that I am running. -- You are receiving this mail because: You are the assignee for the bug.
[Bug 160781] [EDITING] Find and Replace with [x] Cell Styles mistakes Direction (Rows & Columns)
https://bugs.documentfoundation.org/show_bug.cgi?id=160781 BogdanB changed: What|Removed |Added Blocks||106876 CC||buzea.bog...@libreoffice.or ||g Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=106876 [Bug 106876] [META] Find & Replace with styles -- You are receiving this mail because: You are the assignee for the bug.
[Bug 106876] [META] Find & Replace with styles
https://bugs.documentfoundation.org/show_bug.cgi?id=106876 BogdanB changed: What|Removed |Added Depends on||160781 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=160781 [Bug 160781] [EDITING] Find and Replace with [x] Cell Styles mistakes Direction (Rows & Columns) -- You are receiving this mail because: You are the assignee for the bug.
[Bug 108014] [META] Writer character style bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=108014 BogdanB changed: What|Removed |Added Depends on||16 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=16 [Bug 16] Writer: Line numbering can't be hidden by applying character style hidden -- You are receiving this mail because: You are the assignee for the bug.
[Bug 113071] [META] Line numbering/numbers bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=113071 BogdanB changed: What|Removed |Added Depends on||16 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=16 [Bug 16] Writer: Line numbering can't be hidden by applying character style hidden -- You are receiving this mail because: You are the assignee for the bug.
[Bug 160000] Writer: Line numbering can't be hidden by applying character style hidden
https://bugs.documentfoundation.org/show_bug.cgi?id=16 BogdanB changed: What|Removed |Added Blocks||113071, 108014 CC||buzea.bog...@libreoffice.or ||g Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=108014 [Bug 108014] [META] Writer character style bugs and enhancements https://bugs.documentfoundation.org/show_bug.cgi?id=113071 [Bug 113071] [META] Line numbering/numbers bugs and enhancements -- You are receiving this mail because: You are the assignee for the bug.
[Bug 66701] PDF: Malfunctioning PDF's digital signature function.
https://bugs.documentfoundation.org/show_bug.cgi?id=66701 --- Comment #53 from Tom --- An additional test was performed on the problem using LibreOffice 4.2.5.2 in a 64-bit environment of Windows 7. The situation has become even more dire; whenever I make an effort to export a PDF that contains a digital signature, LibreOffice crashes. (It is working correctly to export PDFs without requiring a digital signature or authentication) tried at https://atlasdoorrepair.com/ -- 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||161451 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=161451 [Bug 161451] docx-import »squash« lines of text -- You are receiving this mail because: You are the assignee for the bug.
[Bug 161451] docx-import »squash« lines of text
https://bugs.documentfoundation.org/show_bug.cgi?id=161451 BogdanB changed: What|Removed |Added Blocks||71732 CC||buzea.bog...@libreoffice.or ||g Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=71732 [Bug 71732] [META] Bugs related to text rendering, typography and font features in LO -- You are receiving this mail because: You are the assignee for the bug.
[Bug 108844] [META] Cut/copy bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=108844 BogdanB changed: What|Removed |Added Depends on||131667 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=131667 [Bug 131667] Calc: UI: Edit Cut (or Ctrl+X) without effect - does not cut nor change the clipboard -- You are receiving this mail because: You are the assignee for the bug.
[Bug 131667] Calc: UI: Edit Cut (or Ctrl+X) without effect - does not cut nor change the clipboard
https://bugs.documentfoundation.org/show_bug.cgi?id=131667 BogdanB changed: What|Removed |Added Blocks||108844 CC||buzea.bog...@libreoffice.or ||g Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=108844 [Bug 108844] [META] Cut/copy bugs and enhancements -- You are receiving this mail because: You are the assignee for the bug.
[Bug 158618] Picture made with draw and pasted in Writer disappear when you modify or/and register Writer file
https://bugs.documentfoundation.org/show_bug.cgi?id=158618 BogdanB changed: What|Removed |Added Blocks||107943 CC||buzea.bog...@libreoffice.or ||g Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=107943 [Bug 107943] [META] Save bugs and enhancements -- You are receiving this mail because: You are the assignee for the bug.
[Bug 107943] [META] Save bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=107943 BogdanB changed: What|Removed |Added Depends on||158618 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=158618 [Bug 158618] Picture made with draw and pasted in Writer disappear when you modify or/and register Writer file -- You are receiving this mail because: You are the assignee for the bug.
[Bug 37754] In edit mode formula preview window is shifted in Draw
https://bugs.documentfoundation.org/show_bug.cgi?id=37754 Stéphane Guillou (stragu) changed: What|Removed |Added Version|3.3.3 release |3.3.0 release Keywords||preBibisect, regression Hardware|x86 (IA32) |All CC||stephane.guillou@libreoffic ||e.org OS|Windows (All) |All --- Comment #27 from Stéphane Guillou (stragu) --- (In reply to Regina Henschel from comment #12) > The bug is partly there in Version: 4.5.0.0.alpha0+ > Build ID: 5b829710d65310c6082c2c65ec1239515e319a8e > TinderBox: Win-x86@39, Branch:master, Time: 2014-12-02_06:39:26 > Locale: de_DE > The initial view is still wrong, when switching to edit mode. But when you > move the scrollbar of the document, the object jumps to the correct place. Same on Linux: Version: 24.8.0.0.alpha1+ (X86_64) / LibreOffice Community Build ID: 5a75414d1772d1fd998f405e3b9bd80b1f10c51f CPU threads: 8; OS: Linux 6.5; UI render: default; VCL: gtk3 Scroll or zoom refreshes the view. Not reproduced with OOo 3.3, but reproduced in LO 3.3.0. -- You are receiving this mail because: You are the assignee for the bug.
[Bug 106045] [META] Vertical and rotated text direction issues
https://bugs.documentfoundation.org/show_bug.cgi?id=106045 BogdanB changed: What|Removed |Added Depends on||161503 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=161503 [Bug 161503] Rotated text doesn't work in some situations -- You are receiving this mail because: You are the assignee for the bug.
[Bug 104449] [META] DOCX (OOXML) textbox-related issues
https://bugs.documentfoundation.org/show_bug.cgi?id=104449 BogdanB changed: What|Removed |Added Depends on||161503 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=161503 [Bug 161503] Rotated text doesn't work in some situations -- You are receiving this mail because: You are the assignee for the bug.
[Bug 161503] Rotated text doesn't work in some situations
https://bugs.documentfoundation.org/show_bug.cgi?id=161503 BogdanB changed: What|Removed |Added CC||buzea.bog...@libreoffice.or ||g Blocks||106045, 104449 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=104449 [Bug 104449] [META] DOCX (OOXML) textbox-related issues https://bugs.documentfoundation.org/show_bug.cgi?id=106045 [Bug 106045] [META] Vertical and rotated text direction issues -- You are receiving this mail because: You are the assignee for the bug.
[Bug 160635] open or insert a TIFF image over 33,554,432 pixels fails in various ways ("Image Filter not found" in sd, Section dialog in sw, Push button in sc)
https://bugs.documentfoundation.org/show_bug.cgi?id=160635 --- Comment #7 from Fred --- (In reply to Stéphane Guillou (stragu) from comment #5) ... > > Indeed, the patch defines: > > nMaxPixelsAllowed = (256 * 1024 * 1024) / 4 > > ... which is later divided by 2, so a max of 33,554,432 pixels, which > matches the 5793x5793 import failing. > > So that was by design, but I guess we could fail more gracefully. What do > you think, Caolán? This limit has been lessened from previous release... Version: 7.3.1.3 Build ID: 30(Build:3) CPU threads: 4; OS: Linux 5.17; UI render: default; VCL: gtk3 Locale: en-US (en_US.UTF-8); UI: en-US Calc: threaded Request that the previous upper limit be maintained so that existing previously valid .odp files remain valid. -- You are receiving this mail because: You are the assignee for the bug.
[Bug 161226] Incorrect formula entries cannot be undone using the undo icon
https://bugs.documentfoundation.org/show_bug.cgi?id=161226 Stéphane Guillou (stragu) changed: What|Removed |Added Ever confirmed|0 |1 Summary|Formeleditor|Incorrect formula entries ||cannot be undone using the ||undo icon Status|UNCONFIRMED |NEEDINFO CC||stephane.guillou@libreoffic ||e.org --- Comment #5 from Stéphane Guillou (stragu) --- (In reply to gopitzohl...@gmail.com from comment #3) > libreoffice-base-7.6.7.2: No progress bar is displayed when exporting > e-books. (Please keep reports about one single issue. This is bug 133767.) (In reply to gopitzohl...@gmail.com from comment #2) > Description: > Incorrect formula entries cannot be undone using the undo icon. > > Steps to reproduce: > 1. Wants to edit a formula > 2. The changes are saved. > 3. The changes cannot be undone. > > Actual results: > The new version of the formula is displayed. > > Expected results: > The new version of the formula is displayed You gave the same for "actual" and "expected". I tried undoing changes after saving a formula in: Version: 7.6.7.2 (X86_64) / LibreOffice Community Build ID: dd47e4b30cb7dab30588d6c79c651f218165e3c5 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 ... and it worked as expected for me. Note that you have to enter edit mode in the formula object to undo changes to it, as the change history of the OLE object is separate to the Writer document's. (See e.g. bug 62595, bug 82535, bug 95283) Is that the issue you experience? If the undo didn't work while editing the formula object, please test again with version 24.2 (as 7.6 should not get further bug fixes). If you can still reproduce the issue, please provide more precise steps, and the full version information from Help > About LibreOffice. Thank you. -- You are receiving this mail because: You are the assignee for the bug.
[Bug 141578] Libreoffice unusable with different scale factors used for different screens in multimonitor setup (on kf5/qt5/qt6 vcl + wayland)
https://bugs.documentfoundation.org/show_bug.cgi?id=141578 --- Comment #62 from Stéphane Guillou (stragu) --- *** Bug 161257 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are the assignee for the bug.
[Bug 161257] Impress shows only top left quarter of slides on presentation screen
https://bugs.documentfoundation.org/show_bug.cgi?id=161257 Stéphane Guillou (stragu) changed: What|Removed |Added Resolution|--- |DUPLICATE Whiteboard| QA:needsComment| CC||stephane.guillou@libreoffic ||e.org Status|UNCONFIRMED |RESOLVED --- Comment #2 from Stéphane Guillou (stragu) --- (In reply to Callegar from comment #1) > This is due to the fact that the QT and kf VCLs do not cope with display > scaling correctly. Indeed, we're tracking this multimonitor + scaling + KDE/Qt + Wayland issue in bug 141578. See a potential temporary workaround in bug 141578 comment 61. > Is there a way to list the supported VCLs? Please see https://wiki.documentfoundation.org/Development/Environment_variables#General *** This bug has been marked as a duplicate of bug 141578 *** -- You are receiving this mail because: You are the assignee for the bug.
[Bug 160635] open or insert a TIFF image over 33,554,432 pixels fails in various ways ("Image Filter not found" in sd, Section dialog in sw, Push button in sc)
https://bugs.documentfoundation.org/show_bug.cgi?id=160635 Stéphane Guillou (stragu) changed: What|Removed |Added CC||f...@damen.org --- Comment #6 from Stéphane Guillou (stragu) --- *** Bug 161299 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are the assignee for the bug.
[Bug 161299] Impress: nondisplayed image(s) in existing .odp or 'Image filter not found' on Insert/Image...
https://bugs.documentfoundation.org/show_bug.cgi?id=161299 Stéphane Guillou (stragu) changed: What|Removed |Added CC||stephane.guillou@libreoffic ||e.org Version|unspecified |24.2.3.2 release Resolution|--- |DUPLICATE Status|UNCONFIRMED |RESOLVED --- Comment #3 from Stéphane Guillou (stragu) --- Thanks for the report. (In reply to Fred from comment #2) > I just created a similar file using ImageJ with the following macro commands: > newImage("Untitled", "RGB blue", 8906, 4096, 1); > saveAs("Tiff", "/tmp/IMG3.tif"); > > and trying to Insert>Image... into a new .odp file results in the same > ‘Image filter not found’ popup message. I could reproduce that by running the macro on https://ij.imjoy.io/ and saving the 109.4 mb image, then inserting it in: Version: 24.2.3.2 (X86_64) / LibreOffice Community Build ID: 433d9c2ded56988e8a90e6b2e771ee4e6a5ab2ba 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 I looked further into it and reported in bug 160635 comment 5. Marking as duplicate. *** This bug has been marked as a duplicate of bug 160635 *** -- You are receiving this mail because: You are the assignee for the bug.
[Bug 126152] [META] TIFF image bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=126152 Stéphane Guillou (stragu) changed: What|Removed |Added Depends on||160635 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=160635 [Bug 160635] open or insert a TIFF image over 33,554,432 pixels fails in various ways ("Image Filter not found" in sd, Section dialog in sw, Push button in sc) -- You are receiving this mail because: You are the assignee for the bug.
[Bug 47148] [META] Image handling problems
https://bugs.documentfoundation.org/show_bug.cgi?id=47148 Stéphane Guillou (stragu) changed: What|Removed |Added Depends on||160635 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=160635 [Bug 160635] open or insert a TIFF image over 33,554,432 pixels fails in various ways ("Image Filter not found" in sd, Section dialog in sw, Push button in sc) -- You are receiving this mail because: You are the assignee for the bug.
[Bug 160635] open or insert a TIFF image over 33,554,432 pixels fails in various ways ("Image Filter not found" in sd, Section dialog in sw, Push button in sc)
https://bugs.documentfoundation.org/show_bug.cgi?id=160635 Stéphane Guillou (stragu) changed: What|Removed |Added Keywords||bibisected, bisected Status|NEEDINFO|NEW Version|24.2.2.2 release|7.5.3.2 release CC||caolan.mcnamara@collabora.c ||om Blocks||47148, 126152 Summary|"Image Filter not found"|open or insert a TIFF image |error when trying to open a |over 33,554,432 pixels |multipage TIFF image|fails in various ways ||("Image Filter not found" ||in sd, Section dialog in ||sw, Push button in sc) --- Comment #5 from Stéphane Guillou (stragu) --- Using ImageMagick, I can insert a 201.3 mb image created with: convert -size 5792x5793 xc:pink pink.tif But it fails with a 201.4 mb image created with: convert -size 5793x5793 xc:pink pink.tif So it looks like there's a number of pixels over which the filter fails. No issue if image is e.g. a PNG of the same size. Issue is not related to the size of the file, see bug 160635 in which it fails for a 109 mb picture. Funnily enough, if it fails to insert it into a Calc document, you end up with a Push Button Form Control labelled with the path to the image, and in Writer, with the section dialog. Reproduced in recent own build: Version: 25.2.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: 6f4adc1274cfac30b9097411bb193bd4386969f0 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 As well as LO 7.5.9, but not in 7.4.0.3. Bibisected with linux-64-7.5 to first bad build [1ae6bd31aa05c337c00ab8c83f7fdf35ed0c6fe4] which is a5d5c29769d3c744d8a89052842f73dabd71f445, a cherrypick of: commit b05fb34d48da717447b9b86db9546df72b25e988 author Caolán McNamara Sat Apr 01 22:04:32 2023 +0100 committer Caolán McNamara Sun Apr 02 17:44:42 2023 +0200 use the same max size that libtiff defaults to for its own utilities Reviewed-on: https://gerrit.libreoffice.org/c/core/+/149922 Indeed, the patch defines: nMaxPixelsAllowed = (256 * 1024 * 1024) / 4 ... which is later divided by 2, so a max of 33,554,432 pixels, which matches the 5793x5793 import failing. So that was by design, but I guess we could fail more gracefully. What do you think, Caolán? Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=47148 [Bug 47148] [META] Image handling problems https://bugs.documentfoundation.org/show_bug.cgi?id=126152 [Bug 126152] [META] TIFF image bugs and enhancements -- You are receiving this mail because: You are the assignee for the bug.
[Bug 161302] Add dark mode for VCL gen UI
https://bugs.documentfoundation.org/show_bug.cgi?id=161302 QA Administrators changed: What|Removed |Added Whiteboard|| QA:needsComment -- You are receiving this mail because: You are the assignee for the bug.
[Bug 140709] Undo of image position change doesn't restore original of an different image
https://bugs.documentfoundation.org/show_bug.cgi?id=140709 --- 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 158160] Libre Writer does not remember default language for documents
https://bugs.documentfoundation.org/show_bug.cgi?id=158160 QA Administrators changed: What|Removed |Added Status|NEEDINFO|RESOLVED Resolution|--- |INSUFFICIENTDATA -- You are receiving this mail because: You are the assignee for the bug.
[Bug 161307] Proposal to provide the Scibus Collect for Output function for storing copies of embedded images in a single location.
https://bugs.documentfoundation.org/show_bug.cgi?id=161307 QA Administrators changed: What|Removed |Added Whiteboard|| QA:needsComment -- You are receiving this mail because: You are the assignee for the bug.
[Bug 157834] Add simple arithmetic to pdf forms
https://bugs.documentfoundation.org/show_bug.cgi?id=157834 QA Administrators changed: What|Removed |Added Status|NEEDINFO|RESOLVED Resolution|--- |INSUFFICIENTDATA -- You are receiving this mail because: You are the assignee for the bug.
[Bug 140645] Undo breaks bookmark fields
https://bugs.documentfoundation.org/show_bug.cgi?id=140645 --- Comment #8 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 157834] Add simple arithmetic to pdf forms
https://bugs.documentfoundation.org/show_bug.cgi?id=157834 --- Comment #9 from QA Administrators --- Dear Mike Sapsard, 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 158160] Libre Writer does not remember default language for documents
https://bugs.documentfoundation.org/show_bug.cgi?id=158160 --- Comment #12 from QA Administrators --- Dear Andras Horvath, 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 100290] Header/Footer with different First Page/Left & Right Content - Margins & Spacing can't be changed once set
https://bugs.documentfoundation.org/show_bug.cgi?id=100290 --- Comment #5 from QA Administrators --- Dear Susobhan Ghosh, 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 161522] LibreOffice 7.6 displays and prints pdf in gibberish
https://bugs.documentfoundation.org/show_bug.cgi?id=161522 V Stuart Foote changed: What|Removed |Added Status|UNCONFIRMED |NEEDINFO CC||vsfo...@libreoffice.org Ever confirmed|0 |1 --- Comment #1 from V Stuart Foote --- How does it appear if you use the Insert -> Image and using the pdfium filter? PDF is not intended to be "editable" format, and TurboTax is one of those programs that masks content by rendering fonts with private use area Unicode encoding. The insert filter should bring it in with good fidelity, but the poppler to cairo rendering libs might not depending on how fonts are encoded. -- You are receiving this mail because: You are the assignee for the bug.
[Bug 161299] Impress: nondisplayed image(s) in existing .odp or 'Image filter not found' on Insert/Image...
https://bugs.documentfoundation.org/show_bug.cgi?id=161299 --- Comment #2 from Fred --- (In reply to Robert Großkopf from comment #1) > You are using a LO version of your Linux distribution. I have tested with > original packages of LO and LO 24.2.4.2 on OpenSUSE 15.6 64bit rpm Linux. > Could inset TIF-Image (35 MB) into Impress without any problem. > > Could you test it with original version of LO? > (See: https://wiki.documentfoundation.org/Installing_in_parallel for > installing LO parallel with normal user rights in your home folder) > > Could you create a smaller image, which couldn't be displayed in your > systems, and attach the image here? $ loaih build 24.2.4.2 $ ./LibreOffice-24.2.4.2.basic-x86_64.AppImage Same symptoms. The TIF file(s) are about 105M. I tried creating a cropped version of about 30M, but it loaded fine. There are other smaller png and tif images that show in the exiting .odp file and Insert>Image... fine in a new file. I just created a similar file using ImageJ with the following macro commands: newImage("Untitled", "RGB black", 8906, 4096, 1); saveAs("Tiff", "/tmp/IMG3.tif"); and trying to Insert>Image... into a new .odp file results in the same ‘Image filter not found’ popup message. -- You are receiving this mail because: You are the assignee for the bug.
[Bug 160542] Quickfind sidebar: Search term is not easy to spot
https://bugs.documentfoundation.org/show_bug.cgi?id=160542 --- Comment #5 from Jim Raykowski --- Created attachment 194672 --> https://bugs.documentfoundation.org/attachment.cgi?id=194672=edit find characters combined with unicode middle dot I've been poking around with unicode combining characters for fun. The attached screenshot shows the unicode middle dot combining character combined with the search term characters in the square brackets. -- You are receiving this mail because: You are the assignee for the bug.
[Bug 161258] Enable full RTL-CTL and CJK language support (as in Tools|Options|Languages & Locales|General by default
https://bugs.documentfoundation.org/show_bug.cgi?id=161258 Stéphane Guillou (stragu) changed: What|Removed |Added CC||stephane.guillou@libreoffic ||e.org --- Comment #3 from Stéphane Guillou (stragu) --- I don't think all language support settings should be turned on by default for all locales, and would prefer if efforts were directed towards improving the automatic use of relevant settings depending on locale (if they don't work as expected currently, as in e.g. bug 161255), and clarifying/improving language support options, as in e.g. bug 104318 and bug 39935. Of course, I understand the historical western-centric default is not ideal for many. But I don't think everything on by default in an already option-heavy application is the way to go. For example, it is not desirable to have something as prevalent as the Font tab of the Character dialog be split in two halves when that's not going to be useful to the user, ever. (Wondering in passing how feasible it would be to add a tick box to "turn off" Western/LTR support so it isn't the default anymore...) (My non-RTL/CTL user 2 cents) -- You are receiving this mail because: You are the assignee for the bug.
[Bug 161255] Expand heuristic for enabling RTL-CTL and/or CJK language support when installing/creating new profile
https://bugs.documentfoundation.org/show_bug.cgi?id=161255 Stéphane Guillou (stragu) changed: What|Removed |Added CC||stephane.guillou@libreoffic ||e.org Status|UNCONFIRMED |NEEDINFO Ever confirmed|0 |1 --- Comment #14 from Stéphane Guillou (stragu) --- (In reply to Mike Kaganski from comment #9) > [...] *if* it doesn't work for a *specific* OS, or a > specific locale, then that is a bug - and someone slightly familiar with the > bug tracker would indeed understand that the specific report is needed. like > "I use OS ABC; my locale settings in the OS are XYZ; I install LO using this > method; immediately after installation, I check the LibreOffice locale > setting, and it is ...; and when I look at the Asian / CTL checkboxes there > on the same options page, I see unexpected ... - my expectation is ..." Eyal, if the settings relevant to the system's locale are not turned by default, please provide precise information about your system and LO version so this bug can be actioned, as requested by Mike. So far, only Mike has provided some version info. I feel like a lot of this discussion should have happened on Ask.LO, so a clearer report could have been opened here later. -- You are receiving this mail because: You are the assignee for the bug.
[Bug 161522] New: LibreOffice 7.6 displays and prints pdf in gibberish
https://bugs.documentfoundation.org/show_bug.cgi?id=161522 Bug ID: 161522 Summary: LibreOffice 7.6 displays and prints pdf in gibberish Product: LibreOffice Version: 7.6.7.2 release Hardware: x86-64 (AMD64) OS: macOS (All) Status: UNCONFIRMED Severity: normal Priority: medium Component: LibreOffice Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: jmnew...@cruzio.com Description: When I open my TurboTax 2023 return (PDF) in LibreOffice, all text displays as gibberish. Default language is English, but the return displays and prints in elvish (or some such). Steps to Reproduce: 1.Open LibreOffice 2.Open Documents 3.Load tax return PDF Actual Results: File opens in unknown language Expected Results: File should display in English Reproducible: Always User Profile Reset: No Additional Info: None -- You are receiving this mail because: You are the assignee for the bug.
[Bug 161502] Calc: change Structure label of Function Wizard dialog
https://bugs.documentfoundation.org/show_bug.cgi?id=161502 --- Comment #5 from Commit Notification --- Bayram Çiçek committed a patch related to this issue. It has been pushed to "libreoffice-24-8": https://git.libreoffice.org/core/commit/1b88db8c1c0a92229a1998d4dcc4d5c488163f5a tdf#161502: change Structure label of Function Wizard dialog It will be available in 24.8.0.0.beta2. The patch should be included in the daily builds available at https://dev-builds.libreoffice.org/daily/ in the next 24-48 hours. More information about daily builds can be found at: https://wiki.documentfoundation.org/Testing_Daily_Builds Affected users are encouraged to test the fix and report feedback. -- You are receiving this mail because: You are the assignee for the bug.
[Bug 161502] Calc: change Structure label of Function Wizard dialog
https://bugs.documentfoundation.org/show_bug.cgi?id=161502 --- Comment #5 from Commit Notification --- Bayram Çiçek committed a patch related to this issue. It has been pushed to "libreoffice-24-8": https://git.libreoffice.org/core/commit/1b88db8c1c0a92229a1998d4dcc4d5c488163f5a tdf#161502: change Structure label of Function Wizard dialog It will be available in 24.8.0.0.beta2. The patch should be included in the daily builds available at https://dev-builds.libreoffice.org/daily/ in the next 24-48 hours. More information about daily builds can be found at: https://wiki.documentfoundation.org/Testing_Daily_Builds Affected users are encouraged to test the fix and report feedback. -- You are receiving this mail because: You are on the CC list for the bug.
[Bug 161502] Calc: change Structure label of Function Wizard dialog
https://bugs.documentfoundation.org/show_bug.cgi?id=161502 Commit Notification changed: What|Removed |Added Whiteboard|target:25.2.0 |target:25.2.0 ||target:24.8.0.0.beta2 -- You are receiving this mail because: You are on the CC list for the bug.
[Bug 161502] Calc: change Structure label of Function Wizard dialog
https://bugs.documentfoundation.org/show_bug.cgi?id=161502 Commit Notification changed: What|Removed |Added Whiteboard|target:25.2.0 |target:25.2.0 ||target:24.8.0.0.beta2 -- You are receiving this mail because: You are the assignee for the bug.
core.git: Branch 'libreoffice-24-8' - formula/uiconfig
formula/uiconfig/ui/structpage.ui |2 +- 1 file changed, 1 insertion(+), 1 deletion(-) New commits: commit 1b88db8c1c0a92229a1998d4dcc4d5c488163f5a Author: Bayram Çiçek AuthorDate: Tue May 28 18:35:57 2024 +0300 Commit: Adolfo Jayme Barrientos CommitDate: Wed Jun 12 01:10:49 2024 +0200 tdf#161502: change Structure label of Function Wizard dialog - label "Structure:" changed to "Content:" - this change also removes the duplicated "Structure" text from the dialog which makes the UX better Signed-off-by: Bayram Çiçek Change-Id: I6d70e019b80d4ef0d7207b62e1d0aa6d1f0a3b73 Reviewed-on: https://gerrit.libreoffice.org/c/core/+/168161 Tested-by: Pedro Silva Tested-by: Jenkins CollaboraOffice Reviewed-by: Pedro Silva (cherry picked from commit dc3e624b52e43bb197417b5d9339890afe7c5379) Reviewed-on: https://gerrit.libreoffice.org/c/core/+/168612 Reviewed-by: Adolfo Jayme Barrientos Tested-by: Jenkins (cherry picked from commit 9bbb02bcd7cf26b3e69e12481ffd041019d76082) Reviewed-on: https://gerrit.libreoffice.org/c/core/+/168626 diff --git a/formula/uiconfig/ui/structpage.ui b/formula/uiconfig/ui/structpage.ui index e4548ca33d4f..6faff9151657 100644 --- a/formula/uiconfig/ui/structpage.ui +++ b/formula/uiconfig/ui/structpage.ui @@ -25,7 +25,7 @@ True False start -_Structure: +Content: True struct
core.git: Branch 'libreoffice-24-8' - svx/source
svx/source/sdr/overlay/overlayselection.cxx | 33 +--- 1 file changed, 16 insertions(+), 17 deletions(-) New commits: commit 3c0db898092c2cf6148c01f6c561acc199d484f5 Author: Rafael Lima AuthorDate: Tue Jun 11 01:04:30 2024 +0200 Commit: Adolfo Jayme Barrientos CommitDate: Wed Jun 12 01:07:15 2024 +0200 tdf#161204 Fix selection outline with overlapping ranges The previous commit [1] caused a regression in the outline when two or more ranges overlapped in the selection. This patch fixes the issue. [1] dc243f0122ba656d2630e93bebfb84a2bfe4042a Change-Id: Ib5ec72504ba0efaae715c47628c3d5a47557f506 Reviewed-on: https://gerrit.libreoffice.org/c/core/+/168625 Tested-by: Jenkins Reviewed-by: Adolfo Jayme Barrientos diff --git a/svx/source/sdr/overlay/overlayselection.cxx b/svx/source/sdr/overlay/overlayselection.cxx index 232d6dcc487b..700aa1915c75 100644 --- a/svx/source/sdr/overlay/overlayselection.cxx +++ b/svx/source/sdr/overlay/overlayselection.cxx @@ -40,12 +40,19 @@ namespace sdr::overlay // combine ranges geometrically to a single, ORed polygon static basegfx::B2DPolyPolygon impCombineRangesToPolyPolygon(const std::vector< basegfx::B2DRange >& rRanges) { +// Determines the offset in twips +Size aSize(1, 1); +aSize = o3tl::convert(aSize, o3tl::Length::px, o3tl::Length::twip); +const sal_Int32 nOffset = aSize.getWidth(); + const sal_uInt32 nCount(rRanges.size()); basegfx::B2DPolyPolygon aRetval; for(sal_uInt32 a(0); a < nCount; a++) { -const basegfx::B2DPolygon aDiscretePolygon(basegfx::utils::createPolygonFromRect(rRanges[a])); +basegfx::B2DRange aRange(rRanges[a]); +aRange.grow(nOffset); +const basegfx::B2DPolygon aDiscretePolygon(basegfx::utils::createPolygonFromRect(aRange)); if(0 == a) { @@ -60,23 +67,15 @@ namespace sdr::overlay return aRetval; } -// Creates an ORed polygon with all the ranges shrinked by 1px -// This is used to draw the internal white line in the selection -static basegfx::B2DPolyPolygon impCombineRangesToInternalPolyPolygon(const std::vector< basegfx::B2DRange >& rRanges) +// tdf#161204 Creates a poly-polygon using white hairline to provide contrast +static basegfx::B2DPolyPolygon impCombineRangesToContrastPolyPolygon(const std::vector< basegfx::B2DRange >& rRanges) { -// Determines the offset in twips -Size aSize(1, 1); -aSize = o3tl::convert(aSize, o3tl::Length::px, o3tl::Length::twip); -const sal_Int32 nShrink = aSize.getWidth(); - const sal_uInt32 nCount(rRanges.size()); basegfx::B2DPolyPolygon aRetval; for(sal_uInt32 a(0); a < nCount; a++) { -basegfx::B2DRange aRange(rRanges[a]); -aRange.grow(-nShrink); -const basegfx::B2DPolygon aDiscretePolygon(basegfx::utils::createPolygonFromRect(aRange)); +const basegfx::B2DPolygon aDiscretePolygon(basegfx::utils::createPolygonFromRect(rRanges[a])); if(0 == a) { @@ -175,16 +174,16 @@ namespace sdr::overlay std::move(aPolyPolygon), aRGBColor)); -// Internal outline with white color to provide contrast -basegfx::B2DPolyPolygon aInternalPolyPolygon(impCombineRangesToInternalPolyPolygon(getRanges())); -const drawinglayer::primitive2d::Primitive2DReference aInternalSelectionOutline( +// tdf#161204 Outline with white color to provide contrast +basegfx::B2DPolyPolygon aContrastPolyPolygon(impCombineRangesToContrastPolyPolygon(getRanges())); +const drawinglayer::primitive2d::Primitive2DReference aContrastSelectionOutline( new drawinglayer::primitive2d::PolyPolygonHairlinePrimitive2D( -std::move(aInternalPolyPolygon), +std::move(aContrastPolyPolygon), basegfx::BColor(1.0, 1.0, 1.0))); // add both to result aRetval = drawinglayer::primitive2d::Primitive2DContainer { aUnifiedTransparence, aSelectionOutline }; - aRetval.append(drawinglayer::primitive2d::Primitive2DContainer{aUnifiedTransparence, aInternalSelectionOutline}); + aRetval.append(drawinglayer::primitive2d::Primitive2DContainer{aUnifiedTransparence, aContrastSelectionOutline}); } else {
[Bug 161521] FILEOPEN DOCX/RTF Wrong inner margin in mirrored page, starting on Even side
https://bugs.documentfoundation.org/show_bug.cgi?id=161521 --- Comment #3 from Gabor Kelemen (allotropia) --- Created attachment 194671 --> https://bugs.documentfoundation.org/attachment.cgi?id=194671=edit The example file saved as doc by Word 2016 -- You are receiving this mail because: You are the assignee for the bug.
[Bug 161521] FILEOPEN DOCX/RTF Wrong inner margin in mirrored page, starting on Even side
https://bugs.documentfoundation.org/show_bug.cgi?id=161521 --- Comment #2 from Gabor Kelemen (allotropia) --- Created attachment 194670 --> https://bugs.documentfoundation.org/attachment.cgi?id=194670=edit The example file saved as docx by Word 2016 -- You are receiving this mail because: You are the assignee for the bug.
[Bug 161521] FILEOPEN DOCX/RTF Wrong inner margin in mirrored page, starting on Even side
https://bugs.documentfoundation.org/show_bug.cgi?id=161521 --- Comment #1 from Gabor Kelemen (allotropia) --- Created attachment 194669 --> https://bugs.documentfoundation.org/attachment.cgi?id=194669=edit The example file in Word 2016 and in Writer master Sorry, it should be 4.27 cm, not 4.7 -- You are receiving this mail because: You are the assignee for the bug.
[Bug 81234] [META] RTF filter issues
https://bugs.documentfoundation.org/show_bug.cgi?id=81234 Gabor Kelemen (allotropia) changed: What|Removed |Added Depends on||161521 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=161521 [Bug 161521] FILEOPEN DOCX/RTF Wrong inner margin in mirrored page, starting on Even side -- You are receiving this mail because: You are the assignee for the bug.
[Bug 161521] New: FILEOPEN DOCX/RTF Wrong inner margin in mirrored page, starting on Even side
https://bugs.documentfoundation.org/show_bug.cgi?id=161521 Bug ID: 161521 Summary: FILEOPEN DOCX/RTF Wrong inner margin in mirrored page, starting on Even side Product: LibreOffice Version: 3.6.0.4 release Hardware: All OS: All Status: UNCONFIRMED Severity: normal Priority: medium Component: Writer Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: kelem...@ubuntu.com Blocks: 81234 Created attachment 194668 --> https://bugs.documentfoundation.org/attachment.cgi?id=194668=edit Manually made example file Attached minimal RTF represents a special case of page margin settings: it is mirrored, with the outside margin being 4.7 cm, and starting on an even page. This is imported incorrectly in Writer: while in Word the 4.7 cm margin is on the left side of the first page, in Writer is on the right side, changing page layout. 1. Open attached document -> "Hello" and "Footer" text is at the very left edge of the page, instead of being 4.7 cm from it. In Print view there is an automatically inserted blank page in front of the page. Version: 24.8.0.0.alpha1+ (X86_64) / LibreOffice Community Build ID: 5a75414d1772d1fd998f405e3b9bd80b1f10c51f CPU threads: 14; OS: Windows 10 X86_64 (10.0 build 19045); UI render: Skia/Raster; VCL: win Locale: hu-HU (hu_HU); UI: en-US Calc: default In RTF this started in 3.6, but not yet in 3.5. In DOCX or DOC formats it was like this already in 3.3, and still is in master. Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=81234 [Bug 81234] [META] RTF filter issues -- You are receiving this mail because: You are the assignee for the bug.
[Bug 161090] Allow specifying how many / which values are grouped in remainder of Pie-of-Pie or Bar-of-Pie chart
https://bugs.documentfoundation.org/show_bug.cgi?id=161090 --- Comment #2 from kurt.nordb...@protonmail.com --- FWIW, it appears to me that the default MSO behaviour (split type "auto") puts the last ceil(n/3.0) entries in the right subchart. -- You are receiving this mail because: You are on the CC list for the bug.
[Bug 161482] Pasting Text into a text box, the characters with Ruby are gone
https://bugs.documentfoundation.org/show_bug.cgi?id=161482 --- Comment #1 from nobu --- Created attachment 194667 --> https://bugs.documentfoundation.org/attachment.cgi?id=194667=edit sample file -- You are receiving this mail because: You are the assignee for the bug.
[Bug 92944] FILESAVE Export to tif should allow choosing of resolution and other properties
https://bugs.documentfoundation.org/show_bug.cgi?id=92944 --- Comment #9 from Andrea Giudiceandrea --- Dear QA Team, the issue still occurs using LibreOffice Draw 24.2.4.2 on Windows 10 64-bit. -- You are receiving this mail because: You are the assignee for the bug.
[Bug 140883] textcvt.cxx is "Missing rtl_TextToUnicodeConverter" on startup
https://bugs.documentfoundation.org/show_bug.cgi?id=140883 --- Comment #9 from Eyal Rozenberg --- Can't reproduce at the moment. Resolve as FIXED? As WFM? -- You are receiving this mail because: You are the assignee for the bug.
[Bug 161517] Bad rendering of Calc tables imported into Writer
https://bugs.documentfoundation.org/show_bug.cgi?id=161517 Rafael Lima changed: What|Removed |Added CC||rafael.palma.l...@gmail.com Resolution|--- |DUPLICATE Status|UNCONFIRMED |RESOLVED --- Comment #3 from Rafael Lima --- Yeah... this is an old issue. It's related to how Calc tables are pasted as OLE objects. This happens regardless of the target application. Writer, Impress, Draw all suffer from this. *** This bug has been marked as a duplicate of bug 135891 *** -- You are receiving this mail because: You are the assignee for the bug.
[Bug 135891] Background of Calc tables pasted as OLE objects in Impress not rendering fill colors as expected
https://bugs.documentfoundation.org/show_bug.cgi?id=135891 Rafael Lima changed: What|Removed |Added CC||pakipa...@hotmail.com --- Comment #9 from Rafael Lima --- *** Bug 161517 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are the assignee for the bug.
[Bug 108373] Conditional formatting changes format of dates and numbers
https://bugs.documentfoundation.org/show_bug.cgi?id=108373 m_a_riosv changed: What|Removed |Added CC||davidkno...@icloud.com --- Comment #13 from m_a_riosv --- *** Bug 161510 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are the assignee for the bug.
[Bug 161510] FORMATTING
https://bugs.documentfoundation.org/show_bug.cgi?id=161510 m_a_riosv changed: What|Removed |Added Resolution|--- |DUPLICATE CC||miguelangelrv@libreoffice.o ||rg Status|UNCONFIRMED |RESOLVED --- Comment #3 from m_a_riosv --- *** This bug has been marked as a duplicate of bug 108373 *** -- You are receiving this mail because: You are the assignee for the bug.
[Bug 161520] Rename "not divides" to "does not divide"
https://bugs.documentfoundation.org/show_bug.cgi?id=161520 --- Comment #1 from Rafael Lima --- This string is here: https://opengrok.libreoffice.org/xref/core/extras/source/autocorr/emoji/emoji.ulf#531 -- You are receiving this mail because: You are the assignee for the bug.
[Bug 161507] SCALC_BUG_IN_FORMATTING_FOOTER
https://bugs.documentfoundation.org/show_bug.cgi?id=161507 m_a_riosv changed: What|Removed |Added CC||miguelangelrv@libreoffice.o ||rg --- Comment #1 from m_a_riosv --- 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. -- You are receiving this mail because: You are the assignee for the bug.
[Bug 104742] [META] Network-involved bugs
https://bugs.documentfoundation.org/show_bug.cgi?id=104742 Bug 104742 depends on bug 161262, which changed state. Bug 161262 Summary: No UI for accepting/rejecting SSL certificates for ucb curl backend https://bugs.documentfoundation.org/show_bug.cgi?id=161262 What|Removed |Added Status|NEW |RESOLVED Resolution|--- |WONTFIX -- You are receiving this mail because: You are the assignee for the bug.
[Bug 161262] No UI for accepting/rejecting SSL certificates for ucb curl backend
https://bugs.documentfoundation.org/show_bug.cgi?id=161262 Andras Timar changed: What|Removed |Added Status|NEW |RESOLVED Resolution|--- |WONTFIX --- Comment #4 from Andras Timar --- OK, I accept the explanation, thanks. As a follow-up task, the UI could be removed from the code (sslwarndialog.ui and the code that uses it). -- You are receiving this mail because: You are the assignee for the bug.
[Bug 34694] [META] Improve usability of error messages
https://bugs.documentfoundation.org/show_bug.cgi?id=34694 Bug 34694 depends on bug 161262, which changed state. Bug 161262 Summary: No UI for accepting/rejecting SSL certificates for ucb curl backend https://bugs.documentfoundation.org/show_bug.cgi?id=161262 What|Removed |Added Status|NEW |RESOLVED Resolution|--- |WONTFIX -- You are receiving this mail because: You are the assignee for the bug.
[Bug 161512] button disabled
https://bugs.documentfoundation.org/show_bug.cgi?id=161512 Werner Tietz changed: What|Removed |Added Ever confirmed|0 |1 Status|UNCONFIRMED |NEEDINFO -- You are receiving this mail because: You are the assignee for the bug.
[Bug 133092] [META] Crash bugs
https://bugs.documentfoundation.org/show_bug.cgi?id=133092 Bug 133092 depends on bug 160801, which changed state. Bug 160801 Summary: Writer crash when use clear formatting after insert page break (macOS only) https://bugs.documentfoundation.org/show_bug.cgi?id=160801 What|Removed |Added Status|ASSIGNED|RESOLVED Resolution|--- |FIXED -- You are receiving this mail because: You are the assignee for the bug.
core.git: Branch 'distro/collabora/co-24.04.3' - sw/source
sw/source/core/text/guess.cxx | 34 +++--- sw/source/core/text/guess.hxx |4 +++- 2 files changed, 18 insertions(+), 20 deletions(-) New commits: commit f55d30a8baae5413769674ca86f9c91bc592ee5a Author: Caolán McNamara AuthorDate: Tue Jun 11 11:29:44 2024 +0100 Commit: Andras Timar CommitDate: Tue Jun 11 23:23:28 2024 +0200 more stale hyphenation data after skipping blanks m_xHyphWord is stale if m_nBreakStart changes turn maybeAdjustPositionsForBlockAdjust into a member to make it easier to discard m_xHyphWord on change to m_nBreakStart Change-Id: I6ca37371bf6b8362ebd16a08594afcff3222fa12 Reviewed-on: https://gerrit.libreoffice.org/c/core/+/168666 Reviewed-by: Mike Kaganski Tested-by: Jenkins CollaboraOffice diff --git a/sw/source/core/text/guess.cxx b/sw/source/core/text/guess.cxx index c199bbfcfa97..c4f74de7cef7 100644 --- a/sw/source/core/text/guess.cxx +++ b/sw/source/core/text/guess.cxx @@ -71,15 +71,14 @@ bool hasBlanksInLine(const SwTextFormatInfo& rInf, TextFrameIndex end) return false; } +} + // Called for the last text run in a line; if it is block-adjusted, or center / right-adjusted // with Word compatibility option set, and it has trailing spaces, then the function sets the // values, and returns 'false' value that SwTextGuess::Guess should return, to create a // trailing SwHolePortion. -bool maybeAdjustPositionsForBlockAdjust(TextFrameIndex& rCutPos, TextFrameIndex& rBreakPos, -TextFrameIndex& rBreakStart, sal_uInt16& rBreakWidth, -sal_uInt16& rExtraBlankWidth, sal_uInt16& rMaxSizeDiff, -const SwTextFormatInfo& rInf, const SwScriptInfo& rSI, -sal_uInt16 maxComp) +bool SwTextGuess::maybeAdjustPositionsForBlockAdjust(sal_uInt16& rMaxSizeDiff, const SwTextFormatInfo& rInf, + const SwScriptInfo& rSI, sal_uInt16 maxComp) { const auto& adjObj = rInf.GetTextFrame()->GetTextNodeForParaProps()->GetSwAttrSet().GetAdjust(); const SvxAdjust& adjust = adjObj.GetAdjust(); @@ -98,7 +97,7 @@ bool maybeAdjustPositionsForBlockAdjust(TextFrameIndex& rCutPos, TextFrameIndex& if (rInf.GetTextFrame()->IsRightToLeft()) return true; } -if (auto ch = rInf.GetChar(rCutPos); !ch) // end of paragraph - last line +if (auto ch = rInf.GetChar(m_nCutPos); !ch) // end of paragraph - last line { if (adjust == SvxAdjust::Block) { @@ -123,7 +122,7 @@ bool maybeAdjustPositionsForBlockAdjust(TextFrameIndex& rCutPos, TextFrameIndex& // tdf#57187: block-adjusted line shorter than full width, terminated by manual // line break, must not use trailing spaces for adjustment TextFrameIndex breakPos; -TextFrameIndex newCutPos = AdjustCutPos(rCutPos, breakPos, rInf); +TextFrameIndex newCutPos = AdjustCutPos(m_nCutPos, breakPos, rInf); if (auto ch = rInf.GetChar(newCutPos); ch && ch != CH_BREAK) return true; // next is neither line break nor paragraph end @@ -135,19 +134,19 @@ bool maybeAdjustPositionsForBlockAdjust(TextFrameIndex& rCutPos, TextFrameIndex& // Some trailing spaces actually found, and in case of block adjustment, the text portion // itself has spaces to be able to block-adjust, or single word is allowed to adjust -rBreakStart = rCutPos = newCutPos; -rBreakPos = breakPos; +m_nBreakStart = m_nCutPos = newCutPos; +m_nBreakPos = breakPos; +// throw away old m_xHyphWord because the current break pos is now between words +m_xHyphWord = nullptr; -rInf.GetTextSize(, rInf.GetIdx(), breakPos - rInf.GetIdx(), maxComp, rBreakWidth, +rInf.GetTextSize(, rInf.GetIdx(), breakPos - rInf.GetIdx(), maxComp, m_nBreakWidth, rMaxSizeDiff, rInf.GetCachedVclData().get()); -rInf.GetTextSize(, breakPos, rBreakStart - breakPos, maxComp, rExtraBlankWidth, +rInf.GetTextSize(, breakPos, m_nBreakStart - breakPos, maxComp, m_nExtraBlankWidth, rMaxSizeDiff, rInf.GetCachedVclData().get()); return false; // require SwHolePortion creation } -} - // provides information for line break calculation // returns true if no line break has to be performed // otherwise possible break or hyphenation position is determined @@ -254,9 +253,7 @@ bool SwTextGuess::Guess( const SwTextPortion& rPor, SwTextFormatInfo , // portion fits to line m_nCutPos = rInf.GetIdx() + nMaxLen; bool bRet = rPor.InFieldGrp() -|| maybeAdjustPositionsForBlockAdjust(m_nCutPos, m_nBreakPos, m_nBreakStart, - m_nBreakWidth, m_nExtraBlankWidth, - nMaxSizeDiff,
core.git: sw/source
sw/source/uibase/shells/textsh1.cxx |7 ++- 1 file changed, 6 insertions(+), 1 deletion(-) New commits: commit 6f4adc1274cfac30b9097411bb193bd4386969f0 Author: Patrick Luby AuthorDate: Fri May 31 16:23:59 2024 -0400 Commit: Patrick Luby CommitDate: Tue Jun 11 23:18:56 2024 +0200 tdf#160801 fix crash by delaying resetting of attributes Calling SwWrtShell::ResetAttr() will sometimes delete the current SwTextShell instance so call it after clearing the direct formatting flag. Change-Id: I43a66527cee30271447dff30f166086c6759e162 Reviewed-on: https://gerrit.libreoffice.org/c/core/+/168304 Tested-by: Jenkins Reviewed-by: Patrick Luby diff --git a/sw/source/uibase/shells/textsh1.cxx b/sw/source/uibase/shells/textsh1.cxx index a51c7f6432be..0144b01dbfaf 100644 --- a/sw/source/uibase/shells/textsh1.cxx +++ b/sw/source/uibase/shells/textsh1.cxx @@ -1049,12 +1049,17 @@ void SwTextShell::Execute(SfxRequest ) for (sal_uInt16 i = nBegin; i <= nEnd; ++i) aAttribs.insert( i ); } -rWrtSh.ResetAttr( aAttribs ); // also clear the direct formatting flag inside SwTableBox(es) if (SwFEShell* pFEShell = GetView().GetDocShell()->GetFEShell()) pFEShell->UpdateTableStyleFormatting(nullptr, true); +// tdf#160801 fix crash by delaying resetting of attributes +// Calling SwWrtShell::ResetAttr() will sometimes delete the +// current SwTextShell instance so call it after clearing the +// direct formatting flag. +rWrtSh.ResetAttr( aAttribs ); + rReq.Done(); break; }
core.git: framework/source
framework/source/services/autorecovery.cxx |2 +- 1 file changed, 1 insertion(+), 1 deletion(-) New commits: commit 8fadd44f5947e1022d3431e3ac781b0924c7652e Author: Andrea Gelmini AuthorDate: Tue Jun 11 15:27:45 2024 +0200 Commit: Julien Nabet CommitDate: Tue Jun 11 23:04:53 2024 +0200 Fix typo Change-Id: I8dee411e1f3b4f182791e45b286f24d20f4c98da Reviewed-on: https://gerrit.libreoffice.org/c/core/+/168680 Reviewed-by: Julien Nabet Tested-by: Jenkins diff --git a/framework/source/services/autorecovery.cxx b/framework/source/services/autorecovery.cxx index 14e09e7085de..c4fb2fcf3ed1 100644 --- a/framework/source/services/autorecovery.cxx +++ b/framework/source/services/autorecovery.cxx @@ -2452,7 +2452,7 @@ void AutoRecovery::implts_registerDocument(const css::uno::Reference< css::frame if (pIt != m_lDocCache.end()) { // Normally nothing must be done for this "late" notification. -// But may be the modified state was changed inbetween. +// But may be the modified state was changed in between. // Check it... implts_updateModifiedState(xDocument); return;
core.git: framework/source
framework/source/services/autorecovery.cxx |2 +- 1 file changed, 1 insertion(+), 1 deletion(-) New commits: commit 02b858e78667de122331a056af29d362d1cef56e Author: Andrea Gelmini AuthorDate: Tue Jun 11 15:27:29 2024 +0200 Commit: Julien Nabet CommitDate: Tue Jun 11 23:03:06 2024 +0200 Fix typo Change-Id: Ib50cf36b56ff0a77870948e7ce73eb5da84a6f55 Reviewed-on: https://gerrit.libreoffice.org/c/core/+/168679 Tested-by: Jenkins Reviewed-by: Julien Nabet diff --git a/framework/source/services/autorecovery.cxx b/framework/source/services/autorecovery.cxx index 3e3d92ba6a63..14e09e7085de 100644 --- a/framework/source/services/autorecovery.cxx +++ b/framework/source/services/autorecovery.cxx @@ -2553,7 +2553,7 @@ void AutoRecovery::implts_registerDocument(const css::uno::Reference< css::frame } /* SAFE */ -// Don't register new documents here. (They are registered elsewhere when saved or modifed...) +// Don't register new documents here. (They are registered elsewhere when saved or modified...) implts_flushConfigItem(aInfo, /*bRemoveIt=*/false, /*bAllowAdd=*/!aNew.OrgURL.isEmpty()); implts_startModifyListeningOnDoc(aInfo);
[Bug 161520] New: Rename "not divides" to "does not divide"
https://bugs.documentfoundation.org/show_bug.cgi?id=161520 Bug ID: 161520 Summary: Rename "not divides" to "does not divide" Product: LibreOffice Version: unspecified Hardware: All OS: All Status: UNCONFIRMED Severity: minor Priority: medium Component: UI Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: tuomas.hiet...@iki.fi Description: The symbol ∤ (U+02224) is called "not divides" in a LO UI string. However, the correct English name is "does not divide". https://decodeunicode.org/en/u+02224 Steps to Reproduce: 1. See https://translations.documentfoundation.org/translate/libo_ui-master/extrassourceautocorremoji/en/?checksum=6a333a83ddf14967 Actual Results: The string reads "not divides". Expected Results: The string reads "does not divide". Reproducible: Always User Profile Reset: No Additional Info: n/a -- You are receiving this mail because: You are the assignee for the bug.
[Bug 160401] FILEOPEN PPTX: wrong word order and font size when cap="small" on right-to-left text (Regression)
https://bugs.documentfoundation.org/show_bug.cgi?id=160401 --- Comment #4 from Caolán McNamara --- The preview is correct, but the final rendering not, so presumably goes wrong on generating the final portions -- You are receiving this mail because: You are the assignee for the bug.
[Bug 161411] UI Better wording for ASCII-only characters
https://bugs.documentfoundation.org/show_bug.cgi?id=161411 --- Comment #7 from Tuomas Hietala --- (In reply to Heiko Tietze from comment #5) > If we end up in a verbose label, I suggest to keep a short label and have > the explanatory text in a tooltip. > > ("aka" might become a migraine for l10n) Not sure about the migraine, but of course if we put it in a tooltip, we could as well write "also known as" as we wouldn't be running out of space anyway. So perhaps something like this: "Only Unicode 'Basic Latin' characters can be entered" And the tooltip/explanation: "Characters in the Unicode 'Basic Latin' block (also known as ASCII) include the letters A-Z, a-z, numbers 0-9 and the most common punctuation marks." -- You are receiving this mail because: You are the assignee for the bug.
[Bug 161411] UI Better wording for ASCII-only characters
https://bugs.documentfoundation.org/show_bug.cgi?id=161411 --- Comment #7 from Tuomas Hietala --- (In reply to Heiko Tietze from comment #5) > If we end up in a verbose label, I suggest to keep a short label and have > the explanatory text in a tooltip. > > ("aka" might become a migraine for l10n) Not sure about the migraine, but of course if we put it in a tooltip, we could as well write "also known as" as we wouldn't be running out of space anyway. So perhaps something like this: "Only Unicode 'Basic Latin' characters can be entered" And the tooltip/explanation: "Characters in the Unicode 'Basic Latin' block (also known as ASCII) include the letters A-Z, a-z, numbers 0-9 and the most common punctuation marks." -- You are receiving this mail because: You are on the CC list for the bug.
[Bug 120580] [META] Concordance file bugs and enhancements of alphabetical indexes
https://bugs.documentfoundation.org/show_bug.cgi?id=120580 Bug 120580 depends on bug 148241, which changed state. Bug 148241 Summary: LO Writer has issues editing index entries in tables https://bugs.documentfoundation.org/show_bug.cgi?id=148241 What|Removed |Added Status|NEW |RESOLVED Resolution|--- |FIXED -- You are receiving this mail because: You are the assignee for the bug.
[Bug 148241] LO Writer has issues editing index entries in tables
https://bugs.documentfoundation.org/show_bug.cgi?id=148241 Caolán McNamara changed: What|Removed |Added Status|NEW |RESOLVED Resolution|--- |FIXED --- Comment #6 from Caolán McNamara --- whatever the exact reason for it, after https://cgit.freedesktop.org/libreoffice/core/commit/?id=a48ee46a085abfa04779ece38c08dddb5bf017ea commit d22a86089edfcadbef5231525a2947b954f4784e Author: Armin Le Grand (allotropia) Date: Fri Jan 12 11:22:04 2024 +0100 tdf#158783 Correct compares of SwTOXMark Items That item was never 'pooled', so operator== was not really ever used. It just compared the 'type', so pretty many instances were assumed to be equal, what is wrong. this seems to work again reliably -- You are receiving this mail because: You are the assignee for the bug.
[Bug 161493] Creating a simple pivot table with 2x2 data fails
https://bugs.documentfoundation.org/show_bug.cgi?id=161493 --- Comment #8 from m_a_riosv --- No issue with Version: 24.2.4.2 (X86_64) / LibreOffice Community Build ID: 51a6219feb6075d9a4c46691dcfe0cd9c4fff3c2 CPU threads: 16; OS: Windows 10.0 Build 22631; UI render: Skia/Raster; VCL: win Locale: es-ES (es_ES); UI: en-US Calc: CL threaded Or Version: 24.8.0.0.alpha1+ (X86_64) / LibreOffice Community Build ID: a2b6ce5d21b7f5c84ced8485f5af279f1bf8135f CPU threads: 16; OS: Windows 11 X86_64 (10.0 build 22631); UI render: Skia/Raster; VCL: win Locale: es-ES (es_ES); UI: en-US Calc: CL threaded -- You are receiving this mail because: You are the assignee for the bug.
[Bug 161411] UI Better wording for ASCII-only characters
https://bugs.documentfoundation.org/show_bug.cgi?id=161411 --- Comment #6 from Tuomas Hietala --- (In reply to V Stuart Foote from comment #4) > Unlike the Unicode 'Basic Latin' block, referring to ASCII is a problem as > non-standard Extended-ASCII and localized 8-bit character mappings remain > prevalent. > > And also utf-8 is broken for password entry as noted in bug 50400--that our > SfxPasswordDialog::AllowAsciiOnly() used in pw dialogs exclusively validates > the 7-bit 128 character ASCII code set. > > That is what needs to be conveyed. > > (In reply to Tuomas Hietala from comment #3) > >... > > * ""Only Basic Latin (a.k.a. ASCII) characters (A-Z, a-z, 0-9 and the most > > common punctuation marks) can be entered" > > Something for everyone? > > Make that "Only Unicode 'Basic Latin' (a.k.a ASCII) characters (A-Z, a-z, > 0-9 and the most common punctuation marks) can be entered" Yes, that would be even more complete. -- You are receiving this mail because: You are the assignee for the bug.
[Bug 161411] UI Better wording for ASCII-only characters
https://bugs.documentfoundation.org/show_bug.cgi?id=161411 --- Comment #6 from Tuomas Hietala --- (In reply to V Stuart Foote from comment #4) > Unlike the Unicode 'Basic Latin' block, referring to ASCII is a problem as > non-standard Extended-ASCII and localized 8-bit character mappings remain > prevalent. > > And also utf-8 is broken for password entry as noted in bug 50400--that our > SfxPasswordDialog::AllowAsciiOnly() used in pw dialogs exclusively validates > the 7-bit 128 character ASCII code set. > > That is what needs to be conveyed. > > (In reply to Tuomas Hietala from comment #3) > >... > > * ""Only Basic Latin (a.k.a. ASCII) characters (A-Z, a-z, 0-9 and the most > > common punctuation marks) can be entered" > > Something for everyone? > > Make that "Only Unicode 'Basic Latin' (a.k.a ASCII) characters (A-Z, a-z, > 0-9 and the most common punctuation marks) can be entered" Yes, that would be even more complete. -- You are receiving this mail because: You are on the CC list for the bug.
[Bug 161519] New: i18n: convert the strings "The first" and "rows" to use a variable
https://bugs.documentfoundation.org/show_bug.cgi?id=161519 Bug ID: 161519 Summary: i18n: convert the strings "The first" and "rows" to use a variable Product: LibreOffice Version: unspecified Hardware: All OS: All Status: UNCONFIRMED Severity: normal Priority: medium Component: UI Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: tuomas.hiet...@iki.fi Description: Using two or more mini-strings with unknown content between is bad i18n practice. KDE calls them "word puzzles": https://techbase.kde.org/Development/Tutorials/Localization/i18n_Mistakes#Pitfall_#2:_Word_Puzzles Better practice, which allows more flexible translation, would be to use a single string which includes a variable. Steps to Reproduce: 1. See https://translations.documentfoundation.org/translate/libo_ui-master/swmessages/en/?checksum=b4518772080f7067 and https://translations.documentfoundation.org/translate/libo_ui-master/swmessages/en/?checksum=e8bbd55e1ad068b0 Actual Results: Word puzzle -style strings are used. Expected Results: A single string with a variable is used. Reproducible: Always User Profile Reset: No Additional Info: n/a -- You are receiving this mail because: You are the assignee for the bug.
[Bug 161518] New: "Send to back" is not honored if the objects are on different layers
https://bugs.documentfoundation.org/show_bug.cgi?id=161518 Bug ID: 161518 Summary: "Send to back" is not honored if the objects are on different layers Product: LibreOffice Version: 24.2.1.2 release Hardware: All OS: All Status: UNCONFIRMED Severity: normal Priority: medium Component: Draw Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: rgb.m...@gmail.com Created attachment 194666 --> https://bugs.documentfoundation.org/attachment.cgi?id=194666=edit Screencast illustrating the problem Steps to reproduce the problem (follow the attached screencapture): 1- Insert an object on layer Layout 2- Move to layer Controls and insert, on top of the first object, a second one 3- Right click on the second object → Arrange → Send to Back Result: 1- Second object still displayed on top 2- Click on the overlapping area and the first object will be selected, as if it were on top, even if it's displayed bellow. Screencast created with Version: 24.8.0.0.alpha1+ (X86_64) / LibreOffice Community Build ID: 567dbcf68711402736f65f4a0a47ef57549fe50f CPU threads: 8; OS: Linux 5.14; UI render: default; VCL: kf5 (cairo+xcb) Locale: es-ES (es_ES.UTF-8); UI: en-US Calc: threaded but problem also present on Version: 24.2.1.2 (X86_64) / LibreOffice Community Build ID: 420(Build:2) CPU threads: 8; OS: Linux 5.14; UI render: default; VCL: kf5 (cairo+xcb) Locale: es-ES (es_ES.UTF-8); UI: es-ES Calc: threaded I can't test older versions ATM, but I don't remember seeing this problem before. -- You are receiving this mail because: You are the assignee for the bug.
core.git: dbaccess/CppunitTest_dbaccess_macros_test.mk dbaccess/Module_dbaccess.mk dbaccess/qa
dbaccess/CppunitTest_dbaccess_macros_test.mk | 102 --- dbaccess/Module_dbaccess.mk |1 dbaccess/qa/extras/macros-test.cxx | 42 --- dev/null |binary 4 files changed, 145 deletions(-) New commits: commit ed54d14d5c9bf46b48741e37a12664921aed1c2a Author: Xisco Fauli AuthorDate: Tue Jun 11 16:16:13 2024 +0200 Commit: Xisco Fauli CommitDate: Tue Jun 11 21:32:53 2024 +0200 CppunitTest_dbaccess_macros_test: remove redundant test This was added in 0f4451c0b3bda3d14c7672ca670b4de959495365 "first part of a c++ based test for base" as an example on how to test base documents. At this point we already have other base tests doing more interesting stuff so I believe this test is not needed anymore Change-Id: Ice747800f3ab6d887d63595fe9dbdd531acf9014 Reviewed-on: https://gerrit.libreoffice.org/c/core/+/168684 Tested-by: Jenkins Reviewed-by: Xisco Fauli diff --git a/dbaccess/CppunitTest_dbaccess_macros_test.mk b/dbaccess/CppunitTest_dbaccess_macros_test.mk deleted file mode 100644 index 248a5520c66c.. --- a/dbaccess/CppunitTest_dbaccess_macros_test.mk +++ /dev/null @@ -1,102 +0,0 @@ -# -*- Mode: makefile-gmake; tab-width: 4; indent-tabs-mode: t -*- -# -# 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/. -# - -$(eval $(call gb_CppunitTest_CppunitTest,dbaccess_macros_test)) - -$(eval $(call gb_CppunitTest_add_exception_objects,dbaccess_macros_test, \ -dbaccess/qa/extras/macros-test \ -)) - -$(eval $(call gb_CppunitTest_use_externals,dbaccess_macros_test,\ -boost_headers \ -)) - -$(eval $(call gb_CppunitTest_use_libraries,dbaccess_macros_test, \ -basegfx \ -comphelper \ -cppu \ -cppuhelper \ -dba \ -dbu \ -sdbt \ -drawinglayer \ -editeng \ -for \ -forui \ -i18nlangtag \ -msfilter \ -oox \ -sal \ -salhelper \ -sax \ -sb \ -sfx \ -sot \ -svl \ -svt \ -svx \ -svxcore \ -test \ -subsequenttest \ -tl \ -tk \ -ucbhelper \ - unotest \ -utl \ -$(call gb_Helper_optional,SCRIPTING, \ -vbahelper) \ -vcl \ -xo \ -)) - -$(eval $(call gb_CppunitTest_use_api,dbaccess_macros_test,\ -offapi \ -oovbaapi \ -udkapi \ -)) - -$(eval $(call gb_CppunitTest_use_ure,dbaccess_macros_test)) -$(eval $(call gb_CppunitTest_use_vcl,dbaccess_macros_test)) - -$(eval $(call gb_CppunitTest_use_components,dbaccess_macros_test,\ -basic/util/sb \ -comphelper/util/comphelp \ -configmgr/source/configmgr \ -dbaccess/util/dba \ -dbaccess/util/dbu \ -dbaccess/util/sdbt \ -dbaccess/source/filter/xml/dbaxml \ -filter/source/config/cache/filterconfig1 \ -forms/util/frm \ -framework/util/fwk \ -i18npool/util/i18npool \ -oox/util/oox \ -package/source/xstor/xstor \ -package/util/package2 \ -sax/source/expatwrap/expwrap \ -scripting/source/basprov/basprov \ -scripting/util/scriptframe \ -sfx2/util/sfx \ -sot/util/sot \ -svl/source/fsstor/fsstorage \ -svl/util/svl \ -toolkit/util/tk \ -ucb/source/core/ucb1 \ -ucb/source/ucp/file/ucpfile1 \ -ucb/source/ucp/tdoc/ucptdoc1 \ -unotools/util/utl \ -unoxml/source/rdf/unordf \ -unoxml/source/service/unoxml \ -uui/util/uui \ -xmloff/util/xo \ -)) - -$(eval $(call gb_CppunitTest_use_configuration,dbaccess_macros_test)) - -# vim: set noet sw=4 ts=4: diff --git a/dbaccess/Module_dbaccess.mk b/dbaccess/Module_dbaccess.mk index c51b66c3522d..e3df5dc33dc2 100644 --- a/dbaccess/Module_dbaccess.mk +++ b/dbaccess/Module_dbaccess.mk @@ -52,7 +52,6 @@ $(eval $(call gb_Module_add_check_targets,dbaccess,\ CppunitTest_dbaccess_dialog_save \ CppunitTest_dbaccess_empty_stdlib_save \ CppunitTest_dbaccess_nolib_save \ - CppunitTest_dbaccess_macros_test \ CppunitTest_dbaccess_hsqlschema_import \ )) endif diff --git a/dbaccess/qa/extras/macros-test.cxx b/dbaccess/qa/extras/macros-test.cxx deleted file mode 100644 index 9b11863ef3da.. --- a/dbaccess/qa/extras/macros-test.cxx +++ /dev/null @@ -1,42 +0,0 @@ -/* -*- Mode: C++; tab-width: 4; indent-tabs-mode: nil; c-basic-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/. - */ - -#include -#include - -using namespace ::com::sun::star; - -#if !defined(MACOSX) && !defined(_WIN32) - -class DBAccessTest : public UnoApiTest -{ -public: -DBAccessTest(); - -void
[Bug 161441] UI: Hard to tell which side of a shape being used for as reference for rotation
https://bugs.documentfoundation.org/show_bug.cgi?id=161441 --- Comment #15 from Telesto --- (In reply to Eyal Rozenberg from comment #14) > (In reply to Telesto from comment #0) > > UI: Hard to tell which side of a shape being used for as reference for > > rotation > > Are you sure that is exactly the problem? See below You're right, this isn't the core problem. FWIW: when reporting an it's always flipping between reporting a 'solution' with a description of the problem. Or more a description of experience without clear cut answer to the solution (and sometimes even real clue why the experience being off) > > > This rather common experience, IMHO. Lets assume some - like me - re-using a > > shape (by copy paste) initially drawn say vertically but used horizontally. > > The horizontal shape will have 90 degree angle. Really counter intuitive > In itself, this is not counter-intuitive to me, nor does it matter. At the same time: Yes, you right and No, it does matter. Yes, you are right: It doesn't matter as long I can archive my goal. It would have gone unnoticed if I used the WYSWING rotation mode .uno:ClickChangeRotation. However I struggled to realize it exists (Draw/Impress have it; Writer does not) and properly accessing it (see bug 161500). So I did look at sidebar -> rotation. With the experience that a visually similar oriented shape (rectangle) can have a 0 degree rotation or 90 degree (compare green rectangle and red rectangle in attachment 194623). Also if you rotate the green rectangle 90 degree (right). Having 2 shapes with same rotation degree set delivering a different result > problem, I would say, is with the ffect you mentioned earlier: > > > the negative or positive rotation doesn't matter, until you you add > > text to a shape > > So, I would say that the meaningful issue you're pointing out is that, on > one hand, the shapes looks the same, but on the other hand, they have > significantly different behaviors. Yes > What other behavior distinguishes the shapes other than the text block? The rotation seen in the sidebar/dialogs. > Because, for the text block, one could argue that once you "enter" the > block, you see a rectangular frame for the text block itself, that lets you > know what you can expect when typing. Please explain why that is not good > enough. > > Opposite happens to: copy/paste of horizontal shape rotation to vertical. > > So horizontal shape getting angle of 90, which feels natural (to me) > > I didn't understand this sentence. Nor your definition of a "horizontal > shape". Do you mean a 2D shape for which the page-horizontal extent is > larger than the page-vertical extent? > > > A) Use one angle as basepoint (say horizontal). So vertically drawn object > > is has automatically a 90 degree angle. No clue if this being workable > > Don't quite get this either. You seem to have defined a "vertical shape" and > a "horizontal shape", but what does it mean to be "vertically drawn"? I sometimes have hard time expressing myself; sorry. I hope the illustration given based on attachment 194623 helps > > > B) Some visual indicator on the shape itself marking where the top side of > > the shape is; improving the UI feedback > > How would this be useful other than for knowing how the text area behaves? Well it's suboptimal solution, IMHO. The core issue: the experience that a visually similar oriented shape (rectangle) can have a 0 degree angle or 90 degree angle. And follow-up on that the adjusting the angle becomes math. Rotate the green shape (with text) (attachment 194623) 45 degree. Now rotate the red shape (with text), to match the green shape. I have to really think/or use the try and error mode to conclude:315 / 135 degree. Normally I mindlessly adjust to the same value (45 degree). Also notice that the label text is hard to read. So you want to adjust that (already an additional step I didn't intend to do). To conclude: there is no way to adjust the label orientation (as far I can tell). So no need to redo you work by re-draw the rectangle, I suppose. A (simple) rotating action which I normally perceive as something done mindlessly becomes mind numbing, time consuming frustrating activity. The application working against me (in my perception). And no it's hard to draw a rectangle with a 90 degree rotation -- You are receiving this mail because: You are the assignee for the bug.
[Bug 161441] UI: Hard to tell which side of a shape being used for as reference for rotation
https://bugs.documentfoundation.org/show_bug.cgi?id=161441 --- Comment #15 from Telesto --- (In reply to Eyal Rozenberg from comment #14) > (In reply to Telesto from comment #0) > > UI: Hard to tell which side of a shape being used for as reference for > > rotation > > Are you sure that is exactly the problem? See below You're right, this isn't the core problem. FWIW: when reporting an it's always flipping between reporting a 'solution' with a description of the problem. Or more a description of experience without clear cut answer to the solution (and sometimes even real clue why the experience being off) > > > This rather common experience, IMHO. Lets assume some - like me - re-using a > > shape (by copy paste) initially drawn say vertically but used horizontally. > > The horizontal shape will have 90 degree angle. Really counter intuitive > In itself, this is not counter-intuitive to me, nor does it matter. At the same time: Yes, you right and No, it does matter. Yes, you are right: It doesn't matter as long I can archive my goal. It would have gone unnoticed if I used the WYSWING rotation mode .uno:ClickChangeRotation. However I struggled to realize it exists (Draw/Impress have it; Writer does not) and properly accessing it (see bug 161500). So I did look at sidebar -> rotation. With the experience that a visually similar oriented shape (rectangle) can have a 0 degree rotation or 90 degree (compare green rectangle and red rectangle in attachment 194623). Also if you rotate the green rectangle 90 degree (right). Having 2 shapes with same rotation degree set delivering a different result > problem, I would say, is with the ffect you mentioned earlier: > > > the negative or positive rotation doesn't matter, until you you add > > text to a shape > > So, I would say that the meaningful issue you're pointing out is that, on > one hand, the shapes looks the same, but on the other hand, they have > significantly different behaviors. Yes > What other behavior distinguishes the shapes other than the text block? The rotation seen in the sidebar/dialogs. > Because, for the text block, one could argue that once you "enter" the > block, you see a rectangular frame for the text block itself, that lets you > know what you can expect when typing. Please explain why that is not good > enough. > > Opposite happens to: copy/paste of horizontal shape rotation to vertical. > > So horizontal shape getting angle of 90, which feels natural (to me) > > I didn't understand this sentence. Nor your definition of a "horizontal > shape". Do you mean a 2D shape for which the page-horizontal extent is > larger than the page-vertical extent? > > > A) Use one angle as basepoint (say horizontal). So vertically drawn object > > is has automatically a 90 degree angle. No clue if this being workable > > Don't quite get this either. You seem to have defined a "vertical shape" and > a "horizontal shape", but what does it mean to be "vertically drawn"? I sometimes have hard time expressing myself; sorry. I hope the illustration given based on attachment 194623 helps > > > B) Some visual indicator on the shape itself marking where the top side of > > the shape is; improving the UI feedback > > How would this be useful other than for knowing how the text area behaves? Well it's suboptimal solution, IMHO. The core issue: the experience that a visually similar oriented shape (rectangle) can have a 0 degree angle or 90 degree angle. And follow-up on that the adjusting the angle becomes math. Rotate the green shape (with text) (attachment 194623) 45 degree. Now rotate the red shape (with text), to match the green shape. I have to really think/or use the try and error mode to conclude:315 / 135 degree. Normally I mindlessly adjust to the same value (45 degree). Also notice that the label text is hard to read. So you want to adjust that (already an additional step I didn't intend to do). To conclude: there is no way to adjust the label orientation (as far I can tell). So no need to redo you work by re-draw the rectangle, I suppose. A (simple) rotating action which I normally perceive as something done mindlessly becomes mind numbing, time consuming frustrating activity. The application working against me (in my perception). And no it's hard to draw a rectangle with a 90 degree rotation -- You are receiving this mail because: You are on the CC list for the bug.
[Bug 138705] AccessibleControlShape::disposing: this should never happen! (debug build)
https://bugs.documentfoundation.org/show_bug.cgi?id=138705 --- Comment #5 from BogdanB --- Retested. warn:vcl:101483:101483:vcl/source/window/dndeventdispatcher.cxx:137: rejecting drag enter due to missing listeners. warn:vcl:101483:101483:vcl/source/window/dndeventdispatcher.cxx:185: rejecting drag over due to missing listeners. warn:vcl:101483:101483:vcl/source/window/dndeventdispatcher.cxx:185: rejecting drag over due to missing listeners. warn:vcl:101483:101483:vcl/source/window/dndeventdispatcher.cxx:185: rejecting drag over due to missing listeners. warn:xmloff:101483:101483:xmloff/source/draw/ximpshap.cxx:1711: draw:control without a form:id attribute! warn:xmloff:101483:101483:xmloff/source/draw/ximpshap.cxx:1711: draw:control without a form:id attribute! warn:xmloff:101483:101483:xmloff/source/draw/ximpshap.cxx:1711: draw:control without a form:id attribute! --- warn:svx:101483:101483:svx/source/sdr/contact/viewobjectcontactofunocontrol.cxx:1297: DBG_UNHANDLED_EXCEPTION in isPrintableControl exception: com.sun.star.uno.RuntimeException message: "unsatisfied query for interface of type com.sun.star.beans.XPropertySet! at /home/tdf/lode/jenkins/workspace/lo_gerrit/tb/src_master/include/com/sun/star/uno/Reference.hxx:85" warn:svx:101483:101483:svx/source/sdr/contact/viewobjectcontactofunocontrol.cxx:1297: DBG_UNHANDLED_EXCEPTION in isPrintableControl exception: com.sun.star.uno.RuntimeException message: "unsatisfied query for interface of type com.sun.star.beans.XPropertySet! at /home/tdf/lode/jenkins/workspace/lo_gerrit/tb/src_master/include/com/sun/star/uno/Reference.hxx:85" warn:legacy.osl:101483:101483:forms/source/helper/windowstateguard.cxx:184: WindowStateGuard_Impl::disposing: where does this come from? warn:legacy.osl:101483:101483:forms/source/helper/windowstateguard.cxx:184: WindowStateGuard_Impl::disposing: where does this come from? --- warn:legacy.tools:101483:101483:svx/source/sdr/contact/viewobjectcontactofunocontrol.cxx:1085: ViewObjectContactOfUnoControl_Impl::createControlForDevice: no control model at the SdrUnoObject!? warn:legacy.osl:101483:101483:svx/source/sdr/contact/viewobjectcontactofunocontrol.cxx:927: ViewObjectContactOfUnoControl_Impl::positionAndZoomControl: no output device or no control! Version: 24.8.0.0.alpha1+ (X86_64) / LibreOffice Community Build ID: 6d39b1a6068bbbd5ca4947f668f989dbfb73342d CPU threads: 16; OS: Linux 6.5; UI render: default; VCL: gtk3 Locale: ro-RO (ro_RO.UTF-8); UI: en-US Calc: threaded -- You are receiving this mail because: You are the assignee for the bug.
[Bug 140883] textcvt.cxx is "Missing rtl_TextToUnicodeConverter" on startup
https://bugs.documentfoundation.org/show_bug.cgi?id=140883 BogdanB changed: What|Removed |Added CC||buzea.bog...@libreoffice.or ||g --- Comment #8 from BogdanB --- Please, retest, seems to be solved meanwhile. Version: 24.8.0.0.alpha1+ (X86_64) / LibreOffice Community Build ID: 6d39b1a6068bbbd5ca4947f668f989dbfb73342d CPU threads: 16; OS: Linux 6.5; UI render: default; VCL: gtk3 Locale: ro-RO (ro_RO.UTF-8); UI: en-US Calc: threaded -- You are receiving this mail because: You are the assignee for the bug.
[Bug 142244] warn:legacy.osl:20384:20384:vcl/source/outdev/bitmap.cxx:463: CopyBits with zero or negative width or height
https://bugs.documentfoundation.org/show_bug.cgi?id=142244 --- Comment #2 from BogdanB --- Fewer warnings in 24.8. warn:vcl:88607:88607:vcl/source/window/dndeventdispatcher.cxx:137: rejecting drag enter due to missing listeners. warn:vcl:88607:88607:vcl/source/window/dndeventdispatcher.cxx:185: rejecting drag over due to missing listeners. warn:vcl:88607:88607:vcl/source/window/dndeventdispatcher.cxx:185: rejecting drag over due to missing listeners. warn:vcl:88607:88607:vcl/source/window/dndeventdispatcher.cxx:185: rejecting drag over due to missing listeners. Version: 24.8.0.0.alpha1+ (X86_64) / LibreOffice Community Build ID: 6d39b1a6068bbbd5ca4947f668f989dbfb73342d CPU threads: 16; OS: Linux 6.5; UI render: default; VCL: gtk3 Locale: ro-RO (ro_RO.UTF-8); UI: en-US Calc: threaded -- You are receiving this mail because: You are the assignee for the bug.