[Libreoffice-bugs] [Bug 158219] Calc should default to using another representation over FP64 (double precision floating-point)
https://bugs.documentfoundation.org/show_bug.cgi?id=158219 --- Comment #2 from Stéphane Guillou (stragu) --- See also recent bug 155795. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 158215] Calc Function DAYS doesnt return the number of Days as **integer**
https://bugs.documentfoundation.org/show_bug.cgi?id=158215 --- Comment #5 from Mike Kaganski --- (In reply to Mike Kaganski from comment #4) > "Calculates the difference between two date values *(including fraction of a > day when arguments include time parts)*", or the like. Or better, explicitly express the difference between numeric arguments (that are used unchanged, and provide fractional result), and textual arguments (that are handled using DATEVALUE, and this truncate). Werner Tietz: please consider a new report regarding introduction of a *new* function, say, DAYS.EXCEL - which would be compatible with what Excel does; usable in import/export (thus improving interoperability); and provide a more useful and consistent behavior. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 158094] Can't remove trusted certificate in Macro Security
https://bugs.documentfoundation.org/show_bug.cgi?id=158094 --- Comment #4 from Noel Grandin --- Aha, so I can reproduce this on Windows. On windows the xmlsecurity stuff seems to be happy with the certificate. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 158215] Calc Function DAYS doesnt return the number of Days as **integer**
https://bugs.documentfoundation.org/show_bug.cgi?id=158215 Mike Kaganski changed: What|Removed |Added Resolution|NOTABUG |--- Component|Calc|Documentation CC||olivier.hallot@libreoffice. ||org Status|RESOLVED|NEW Ever confirmed|0 |1 --- Comment #4 from Mike Kaganski --- It is indeed a problem of documentation. Setting the component accordingly. The help needs to mention something like "Calculates the difference between two date values *(including fraction of a day when arguments include time parts)*", or the like. Indeed, the standard is already explicit and exactly clear - it tells "If StartDate and EndDate are Numbers, this is EndDate – StartDate", which provides the exact answer how the result is obtained (no truncation / rounding of arguments and/or result involved). -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 158189] Hidden page break with multiple columns and table at the page beginning
https://bugs.documentfoundation.org/show_bug.cgi?id=158189 --- Comment #5 from Adam664 --- (In reply to demo4 from comment #2) > Yes, if you press Return in the very first table cell, the table moves down > one row and the dashed line is visible again. > > There seems to be other strange behavior (broken redo log) with tables and > page columns: > > On an empty document: > > 1. Apply "Columns: 2" to the "Default Page Style" > 2. insert table (Ctrl+F12 and Return) > 3. insert col break (Ctrl+Shift+Return) (seemingly nothing happens) > 4. insert new paragraph (Return) > 5. insert col break (Ctrl+Shift+Return) > 6. remove first line (Del Key) > > > The dashed line (which indicates a column break) is also hidden here. But > now the redo log seems to be broken. The following actions are displayed > when you move the mouse pointer over the undo button after performing each > of the above actions. > > 1. Undo: Change style: Default Page Style > 2. Undo: Insert table: "Table1" > 3. Undo: Change style: Table1 > This logged action seems wrong to me. > 4. Undo: New Paragraph > 5. Undo: Insert column break > 6. Undo: Delete Paragraphs > > > Pressing the undo button from the toolbar (or Ctrl+Z, similar), the > following things happen: > > 1. Undo: Delete Paragraphs > The Table disappears, the man. col break appears, the removed pilcrow > appears (Formatting Marks shown). > 2. Undo: Insert column break > The Table appears, the man. col break disappears, the pilcrow disappears. > Table remains in second col. > 3. Undo: New Paragraph > The table moves to the first page. > 4. Undo: Change style: Table1 > seemingly nothing happens > 5. Undo: Insert table: "Table1" > The table disappears > 6. Undo: Change style: Default Page Style > The Document changes to one column. > > > Redo the undone things results in another result than before: > 6. Redo: Change style: Default Page Style > The Document changes to two columns. > 5. Redo: Insert table: "Table1" > The table appears > 4. Redo: Change style: Table1 > seemingly nothing happens > 3. Redo: New Paragraph > The table remains on the first page and moves one line down > 2. Redo: Insert column break > The Table moves to the second col, second line, and the col break dashed > line is shown > 1. Redo: Delete Paragraphs > The Table moves back to the first col, the dashed line goes away > > > Maybe, this should be placed in a new issue? Yes, file this as another issue as its not directly related to the current issue. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 158189] Hidden page break with multiple columns and table at the page beginning
https://bugs.documentfoundation.org/show_bug.cgi?id=158189 Adam664 changed: What|Removed |Added Status|UNCONFIRMED |NEW OS|Windows (All) |All Version|7.6.1.2 release |7.5.3.2 release Ever confirmed|0 |1 --- Comment #4 from Adam664 --- Setting to NEW with the caveat that there is an easy work around, while the cursor is in the first row and column of the table, press enter to move the table down one line and the page break re-appears. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 158215] Calc Function DAYS doesnt return the number of Days as **integer**
https://bugs.documentfoundation.org/show_bug.cgi?id=158215 --- Comment #3 from Werner Tietz --- It may be explained in the wiki, but NOT in the Help about DAYS! -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 158219] Calc should default to using another representation over FP64 (double precision floating-point)
https://bugs.documentfoundation.org/show_bug.cgi?id=158219 --- Comment #1 from Mike Kaganski --- (In reply to Eyal Rozenberg from comment #0) > ... now, I know what you're going to say: It's a huge change, it's really > fundamental, it goes against half of everything we've written for 35 years, > nobody will ever have the time to spare to seriously work on this - maybe. > > ... > > See also bug 128312. Huh? You yourself provided a link to the bug report, where this was answered. And even putting aside the fact that your suggestions do not change things - there will still be only a limited accuracy - the only thing discussed there was not "it's huge work", but - only performance. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 158220] Calc 7.6.0.3 not setting cell format properly
https://bugs.documentfoundation.org/show_bug.cgi?id=158220 Saburo changed: What|Removed |Added Version|7.6.0.3 release |7.5.0.3 release Status|UNCONFIRMED |NEW Ever confirmed|0 |1 --- Comment #1 from Saburo --- Reproduced Version: 7.5.8.2 (X86_64) / LibreOffice Community Build ID: f718d63693263970429a68f568db6046aaa9df01 CPU threads: 4; OS: Windows 10.0 Build 19045; UI render: Skia/Raster; VCL: win Locale: ja-JP (ja_JP); UI: ja-JP Calc: CL Reproduce 7.5.0.3 Don't reproduce 7.4.7.2 Step 1.Select entire sheet, set font size to 16 2.type something in cell A1 3.type something in cell B2 4.Select entire sheet, set font size to 20 (A1:B2 font size 20,but C1 font size 16) This seems to only apply to the range of cells that are used -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 157410] Use SVG instead of bitmap when possible for HTML filters
https://bugs.documentfoundation.org/show_bug.cgi?id=157410 QA Administrators changed: What|Removed |Added Whiteboard| QA:needsComment| -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 157803] Prevent extending decimal extension for calculations with floating point arithmetic accuracy issues (IEEE 754) in 'General' number format type
https://bugs.documentfoundation.org/show_bug.cgi?id=157803 QA Administrators changed: What|Removed |Added Whiteboard| QA:needsComment| -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 158189] Hidden page break with multiple columns and table at the page beginning
https://bugs.documentfoundation.org/show_bug.cgi?id=158189 QA Administrators changed: What|Removed |Added Status|NEEDINFO|UNCONFIRMED Ever confirmed|1 |0 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 158013] lo reseting fonts resets fonts in document
https://bugs.documentfoundation.org/show_bug.cgi?id=158013 QA Administrators changed: What|Removed |Added Whiteboard|| QA:needsComment -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 155841] No hyphenation patterns available for Hebrew
https://bugs.documentfoundation.org/show_bug.cgi?id=155841 QA Administrators changed: What|Removed |Added Whiteboard| QA:needsComment| -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 154848] Using bigger images on slides may lead to a crash of Impress during presenting
https://bugs.documentfoundation.org/show_bug.cgi?id=154848 --- Comment #3 from QA Administrators --- Dear Joysn71, Please read this message in its entirety before proceeding. Your bug report is being closed as INSUFFICIENTDATA due to inactivity and a lack of information which is needed in order to accurately reproduce and confirm the problem. We encourage you to retest your bug against the latest release. If the issue is still present in the latest stable release, we need the following information (please ignore any that you've already provided): a) Provide details of your system including your operating system and the latest version of LibreOffice that you have confirmed the bug to be present b) Provide easy to reproduce steps – the simpler the better c) Provide any test case(s) which will help us confirm the problem d) Provide screenshots of the problem if you think it might help e) Read all comments and provide any requested information Once all of this is done, please set the bug back to UNCONFIRMED and we will attempt to reproduce the issue. Please do not: a) respond via email b) update the version field in the bug or any of the other details on the top section of our bug tracker Warm Regards, QA Team MassPing-NeedInfo-FollowUp -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 154847] When cloning slide with animation and removing objects on cloned slide, navigation backwards breaks
https://bugs.documentfoundation.org/show_bug.cgi?id=154847 QA Administrators changed: What|Removed |Added Status|NEEDINFO|RESOLVED Resolution|--- |INSUFFICIENTDATA -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 158189] Hidden page break with multiple columns and table at the page beginning
https://bugs.documentfoundation.org/show_bug.cgi?id=158189 --- Comment #3 from QA Administrators --- [Automated Action] NeedInfo-To-Unconfirmed -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 154848] Using bigger images on slides may lead to a crash of Impress during presenting
https://bugs.documentfoundation.org/show_bug.cgi?id=154848 QA Administrators changed: What|Removed |Added Status|NEEDINFO|RESOLVED Resolution|--- |INSUFFICIENTDATA -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 154847] When cloning slide with animation and removing objects on cloned slide, navigation backwards breaks
https://bugs.documentfoundation.org/show_bug.cgi?id=154847 --- Comment #3 from QA Administrators --- Dear Joysn71, Please read this message in its entirety before proceeding. Your bug report is being closed as INSUFFICIENTDATA due to inactivity and a lack of information which is needed in order to accurately reproduce and confirm the problem. We encourage you to retest your bug against the latest release. If the issue is still present in the latest stable release, we need the following information (please ignore any that you've already provided): a) Provide details of your system including your operating system and the latest version of LibreOffice that you have confirmed the bug to be present b) Provide easy to reproduce steps – the simpler the better c) Provide any test case(s) which will help us confirm the problem d) Provide screenshots of the problem if you think it might help e) Read all comments and provide any requested information Once all of this is done, please set the bug back to UNCONFIRMED and we will attempt to reproduce the issue. Please do not: a) respond via email b) update the version field in the bug or any of the other details on the top section of our bug tracker Warm Regards, QA Team MassPing-NeedInfo-FollowUp -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 154840] 7.5 not connecting to printer
https://bugs.documentfoundation.org/show_bug.cgi?id=154840 QA Administrators changed: What|Removed |Added Resolution|--- |INSUFFICIENTDATA Status|NEEDINFO|RESOLVED -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 154840] 7.5 not connecting to printer
https://bugs.documentfoundation.org/show_bug.cgi?id=154840 --- Comment #3 from QA Administrators --- Dear Nigel Wakefield, Please read this message in its entirety before proceeding. Your bug report is being closed as INSUFFICIENTDATA due to inactivity and a lack of information which is needed in order to accurately reproduce and confirm the problem. We encourage you to retest your bug against the latest release. If the issue is still present in the latest stable release, we need the following information (please ignore any that you've already provided): a) Provide details of your system including your operating system and the latest version of LibreOffice that you have confirmed the bug to be present b) Provide easy to reproduce steps – the simpler the better c) Provide any test case(s) which will help us confirm the problem d) Provide screenshots of the problem if you think it might help e) Read all comments and provide any requested information Once all of this is done, please set the bug back to UNCONFIRMED and we will attempt to reproduce the issue. Please do not: a) respond via email b) update the version field in the bug or any of the other details on the top section of our bug tracker Warm Regards, QA Team MassPing-NeedInfo-FollowUp -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 155158] Cursor dissapears when switching from chinese layout (windows 10)
https://bugs.documentfoundation.org/show_bug.cgi?id=155158 --- Comment #2 from QA Administrators --- Dear nikolasopi, This bug has been in NEEDINFO status with no change for at least 6 months. Please provide the requested information as soon as possible and mark the bug as UNCONFIRMED. Due to regular bug tracker maintenance, if the bug is still in NEEDINFO status with no change in 30 days the QA team will close the bug as INSUFFICIENTDATA due to lack of needed information. For more information about our NEEDINFO policy please read the wiki located here: https://wiki.documentfoundation.org/QA/Bugzilla/Fields/Status/NEEDINFO If you have already provided the requested information, please mark the bug as UNCONFIRMED so that the QA team knows that the bug is ready to be confirmed. Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-NeedInfo-Ping -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 92144] Calc styles cannot have percentage sizes for fonts
https://bugs.documentfoundation.org/show_bug.cgi?id=92144 --- Comment #13 from QA Administrators --- Dear mahfiaz, 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.
[Libreoffice-bugs] [Bug 48712] Initial Print Preview shows more than content area importing Excel .xls with row 3 merged
https://bugs.documentfoundation.org/show_bug.cgi?id=48712 --- Comment #6 from QA Administrators --- Dear Christopher M. Penalver, 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.
[Libreoffice-bugs] [Bug 43445] BUGZILLAASSISTANT BSA: Drop-down lists disappear when you are moving your mouse to them
https://bugs.documentfoundation.org/show_bug.cgi?id=43445 --- Comment #6 from QA Administrators --- Dear Ed, 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.
[Libreoffice-bugs] [Bug 118467] Libreoffice Modifies pagesize (A4->A4.Duplex) when printing with hpcups driver
https://bugs.documentfoundation.org/show_bug.cgi?id=118467 --- Comment #6 from QA Administrators --- Dear rkeller, 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.
[Libreoffice-bugs] [Bug 157978] Libre spreadsheets don't pop up surface pro onscreen keyboard
https://bugs.documentfoundation.org/show_bug.cgi?id=157978 --- Comment #5 from Richard --- "when I click in libreoffice writer" i meant to say -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 157978] Libre spreadsheets don't pop up surface pro onscreen keyboard
https://bugs.documentfoundation.org/show_bug.cgi?id=157978 --- Comment #4 from Richard --- hi, OP here. Yes what I've noticed is a) when I click in a word doc, the surface pro on-screen keyboard pops up automatically and allows me to type, as expected b) when I click on a cell in calc, and then click in the edit field up the top, the onscreen keyboard doesnt appear, and I have to go and launch the onscreen keyboard from the task bar to allow me to edit the cell. Hope that clarifies! Cheers Richard -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 157978] Libre spreadsheets don't pop up surface pro onscreen keyboard
https://bugs.documentfoundation.org/show_bug.cgi?id=157978 ady changed: What|Removed |Added CC||m.wegh...@posteo.de Resolution|INVALID |--- Status|RESOLVED|NEW --- Comment #3 from ady --- (In reply to Eyal Rozenberg from comment #2) > LibreOffice itself, AFAICT, does not offer an integrated on-screen/virtual > keyboard. I believe that the reporter is saying that using a "surface pro on-screen keyboard" in Writer works as expected, but not in Calc (at least partially?) IIUC, this is not about some virtual keyboard feature integrated in LO (which indeed is not included). To be clear, I don't have access to relevant hardware in order for me to test. I am resetting this report from INVALID to NEW, as it was before. I am wondering whether this should be set to NEEDINFO, so as to request more clear wording or steps in order for others to reproduce the problem. While this is not a typical accessibility issue, maybe one of the recent changes to accessibility support features introduced some kind of conflict with virtual keyboards? -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 158220] New: Calc 7.6.0.3 not setting cell format properly
https://bugs.documentfoundation.org/show_bug.cgi?id=158220 Bug ID: 158220 Summary: Calc 7.6.0.3 not setting cell format properly Product: LibreOffice Version: 7.6.0.3 release Hardware: All OS: Linux (All) Status: UNCONFIRMED Severity: normal Priority: medium Component: Calc Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: lp.allar...@gmail.com Description: The program is not using previously set cell format if I enter contents in an empty cell that has been previously formatted while selecting the entire sheet. Version: 7.6.0.3 (X86_64) / LibreOffice Community Build ID: 69edd8b8ebc41d00b4de3915dc82f8f0fc3b6265 CPU threads: 4; OS: Linux 5.4; UI render: default; VCL: gtk3 Locale: en-CA (en_CA.UTF-8); UI: en-US Calc: CL threaded Steps to Reproduce: Step-by-step example: -Select entire sheet, set font size to 16 (all other settings remain as-is) -I type something in cell A1, contents is set to size 16 as intended. -I type something in cell A2, contents is also set to size 16 -I select the entire sheet -I set the font to size 20 -I enter something in cell A3, contents is set to size 16 Actual Results: cell format is ignored Expected Results: Cell format should be considered Reproducible: Always User Profile Reset: Yes Additional Info: [Information automatically included from LibreOffice] Locale: en-US Module: SpreadsheetDocument [Information guessed from browser] OS: Linux (All) OS is 64bit: yes -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 98259] [META] Keyboard shortcuts and accelerators bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=98259 Gabor Kelemen (allotropia) changed: What|Removed |Added Depends on||148986 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=148986 [Bug 148986] Support the "XF86Forward" and "XF86Back" presenter mouse / remote clicker shortcuts to move between slides in presentation mode -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 148986] Support the "XF86Forward" and "XF86Back" presenter mouse / remote clicker shortcuts to move between slides in presentation mode
https://bugs.documentfoundation.org/show_bug.cgi?id=148986 Gabor Kelemen (allotropia) changed: What|Removed |Added Whiteboard| QA:needsComment| Status|UNCONFIRMED |NEW Blocks||98259 CC||kelem...@ubuntu.com Ever confirmed|0 |1 --- Comment #1 from Gabor Kelemen (allotropia) --- Confirming. I have a clicker device (ISY IP1000) that creates the same keycodes. Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=98259 [Bug 98259] [META] Keyboard shortcuts and accelerators bugs and enhancements -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 158179] Layer tab popup menu in Draw shows layer visibility setting of previous selected tab
https://bugs.documentfoundation.org/show_bug.cgi?id=158179 --- Comment #2 from Jim Raykowski --- (In reply to Heiko Tietze from comment #1) > Wouldn't it be easy to just rename the command to "Hide Layer"? Usually > labels should be phrased positively but in this case it is about explicitly > hiding. Nothing to say against change the internal logic, although it > involves more effort. In this case it seems to me better to use "Hide Layer". The effort to rename and change the internal logic isn't so much. Here's a link to a patch that renames/reworks the menu item and fixes the reported bug: https://gerrit.libreoffice.org/c/core/+/159427 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 158218] Document is not saved if solely text is pasted since last save
https://bugs.documentfoundation.org/show_bug.cgi?id=158218 m.a.riosv changed: What|Removed |Added Status|UNCONFIRMED |NEEDINFO Ever confirmed|0 |1 CC||miguelangelrv@libreoffice.o ||rg --- Comment #1 from m.a.riosv --- I can not reproduce Version: 24.2.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: c60a9db1f2a8e2a088c6b89bcdff4901b28f2864 CPU threads: 16; OS: Windows 10.0 Build 22631; UI render: default; VCL: win Locale: es-ES (es_ES); UI: en-US Calc: CL threaded Please test in safe mode, Menu/Help/Restart in Safe Mode Please can you paste the information in Menu/Help/About LibreOffice, there is an icon to copy. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 139532] [META] DOCX Floating table related issues
https://bugs.documentfoundation.org/show_bug.cgi?id=139532 Gabor Kelemen (allotropia) changed: What|Removed |Added Depends on||158213 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=158213 [Bug 158213] LibreOffice Writer incorrectly displays a .docx document with a table -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 139532] [META] DOCX Floating table related issues
https://bugs.documentfoundation.org/show_bug.cgi?id=139532 Bug 139532 depends on bug 158213, which changed state. Bug 158213 Summary: LibreOffice Writer incorrectly displays a .docx document with a table https://bugs.documentfoundation.org/show_bug.cgi?id=158213 What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |DUPLICATE -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 158213] LibreOffice Writer incorrectly displays a .docx document with a table
https://bugs.documentfoundation.org/show_bug.cgi?id=158213 Gabor Kelemen (allotropia) changed: What|Removed |Added Blocks||139532 Status|UNCONFIRMED |RESOLVED CC||kelem...@ubuntu.com Resolution|--- |DUPLICATE --- Comment #4 from Gabor Kelemen (allotropia) --- Floating tables... Seems to be fixed (3 pages, no endless loop... which were problematic in some bibisect versions) since: https://git.libreoffice.org/core/+/435f1aadf7dd8087a8997924bedfccff0f496ba2 author Miklos Vajna Fri Oct 27 08:11:05 2023 +0200 committer Miklos Vajna Fri Oct 27 09:47:42 2023 +0200 tree57d89342d7f20bb446ddef76e35947fd47e9dd32 parent 5946ffe7139189eff2c1e90ddb3edb146eb60e17 [diff] tdf#99822 sw floattable: allow nomimal overlap of objects from different cells *** This bug has been marked as a duplicate of bug 99822 *** Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=139532 [Bug 139532] [META] DOCX Floating table related issues -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 155841] No hyphenation patterns available for Hebrew
https://bugs.documentfoundation.org/show_bug.cgi?id=155841 --- Comment #3 from Eyal Rozenberg --- (In reply to Caolán McNamara from comment #2) > If there are hyphens used in, e.g. newspapers. is there any known style > guide for hyphenation they are following? I plan on trying to get in touch with some newspapers to see if I can figure this one out. But I do need to clarify that other than in media that is tall and narrow-column, hyphenation is possible but uncommon. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 158215] Calc Function DAYS doesnt return the number of Days as **integer**
https://bugs.documentfoundation.org/show_bug.cgi?id=158215 m.a.riosv changed: What|Removed |Added CC||miguelangelrv@libreoffice.o ||rg Resolution|--- |NOTABUG Status|UNCONFIRMED |RESOLVED --- Comment #2 from m.a.riosv --- It is explained in the wiki https://wiki.documentfoundation.org/Documentation/Calc_Functions/DAYS " Details specific to DAYS function The formula for this function is DAYS = Date2 – Date1, subtracting the two date-time serial numbers. This function is not identical to Microsoft Excel’s DAYS function, which does not take account of any time components of the dates. " -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 128312] Calculation involing some decimals return incorrect floats with 12 d.p.
https://bugs.documentfoundation.org/show_bug.cgi?id=128312 Eyal Rozenberg changed: What|Removed |Added See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=15 ||8219 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 158219] Calc should default to using another representation over FP64 (double precision floating-point)
https://bugs.documentfoundation.org/show_bug.cgi?id=158219 Eyal Rozenberg changed: What|Removed |Added See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=12 ||8312 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 158219] New: Calc should default to using another representation over FP64 (double precision floating-point)
https://bugs.documentfoundation.org/show_bug.cgi?id=158219 Bug ID: 158219 Summary: Calc should default to using another representation over FP64 (double precision floating-point) Product: LibreOffice Version: Inherited From OOo Hardware: All OS: All Status: UNCONFIRMED Severity: normal Priority: medium Component: Calc Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: eyalr...@gmx.com When a user enter fractional values in a spreadsheet, they expect the representation of that value to be exact, not an approximation by a base-2 representation like FP32 (IEEE 754 single-precision) FP64 (double-precision) etc. They meant the exact value they entered. Similarly, when a user sets a cell to the result of an additive formula involving decimal values (immediate or via cell reference), they expect the result to be exact, not approximate. For example, users expects the formula =(3100099 - 3200012)*0.01 to yield 99913 , which it does. But users also expect =3100099*0.01 - 3200012*0.01 to yield the same value... which it does not. This second formula yields -999.1297 instead of -999.13 Now, it is true that if a user is somewhat knowledgeable in matters of representation, they would understand why this happens. But most users are not; and moreover - this is not the user's _intent_. Now, obviously, a binary computer cannot perform infinite-accuracy computations, so there must be limits to our "indulgence". However - we are far from where this limit should be. A user is likely to accept that when they use trigonometric, exponential, logarithmic and other such functions - accuracy will be imperfect (and, in fact, most users don't try any of that stuff intentionally). At the very least, I argue that computations all of whose steps maintain representability in decimal form should be performed with perfect accuracy. This would require two "bigint"s for (signed) mantissa and base-10 exponent. Other possibilities could be: * Divisor and dividend * mantissa, exponent and basis (so, three "bigint"s) ... now, I know what you're going to say: It's a huge change, it's really fundamental, it goes against half of everything we've written for 35 years, nobody will ever have the time to spare to seriously work on this - maybe. But it's the right thing to do in principle. And as for mitigating the pain: * The default could change with a new ODF version, so that old documents maintain existing behavior. * There would be a choice of underlying representation model, e.g. for compatibility and for lovers of binary. * It could start as an opt-in before it becomes the default. See also bug 128312. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 158033] PDF: Writer Docx to PDF export fails to render asian fonts in V7
https://bugs.documentfoundation.org/show_bug.cgi?id=158033 --- Comment #11 from Prashanna --- Ah, thanks for the suggestion. I'll try give that a go the next chance I get. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 157803] Prevent extending decimal extension for calculations with floating point arithmetic accuracy issues (IEEE 754) in 'General' number format type
https://bugs.documentfoundation.org/show_bug.cgi?id=157803 --- Comment #1 from Eyal Rozenberg --- Please... 1. Attach an ODS file with the example in the screenshot. 2. Be more specific: Characterize how precision increases today, and what precision increase logic you're proposing. 3. Explain the relation to the other bugs you linked to. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 158218] New: Document is not saved if solely text is pasted since last save
https://bugs.documentfoundation.org/show_bug.cgi?id=158218 Bug ID: 158218 Summary: Document is not saved if solely text is pasted since last save Product: LibreOffice Version: 7.5.8.2 release Hardware: All OS: All Status: UNCONFIRMED Severity: normal Priority: medium Component: Calc Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: firebea...@gmail.com Description: When solely text is pasted into LibreOffice Calc since the last save, not all of the changes are saved to the file Steps to Reproduce: 1. Create an empty document document 2. Save the document 3. Copy some text 4. Paste text to LibreOffice Calc (Notice that the 'document has been modified' is active in the bottom bar) (copy it to every cell apart from A1) 5. Save the document (CTRL + S or Save via the menu) (Notice that the 'document has been modified' is inactive in the bottom bar) 6. Reopen the document (with LibreOffice Calc or a text editor) Actual Results: The recent changes are not saved Expected Results: The opened document should match the saved the document, and include the pasted text Reproducible: Always User Profile Reset: No Additional Info: A few observations: - Only when the changes since the last save solely consist of pasted text, the changes are not saved. Once it contains a mix of pasted text and changed fields, the changes save fine - Sometimes the file is correctly saved, this seems to be related if the pasted cell is within the range of the previously saved document For example. The csv already contains a value in cell A5. When a value is copied to both A4(within the range) and A6 (outside of the range). On save only A4 is written to the file, the value of A6 is ignored -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 155841] No hyphenation patterns available for Hebrew
https://bugs.documentfoundation.org/show_bug.cgi?id=155841 --- Comment #2 from Caolán McNamara --- For what it is worth, the libhyphen format is somewhat described at https://github.com/hunspell/hyphen/blob/master/README.hyphen (and the other READMEs beside it for more complicated things). Patterns to match text against, with odd numbers as potential hyphenation points and even numbers as not-to-hyphen points IIRC. If there are hyphens used in, e.g. newspapers. is there any known style guide for hyphenation they are following? -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 157410] Use SVG instead of bitmap when possible for HTML filters
https://bugs.documentfoundation.org/show_bug.cgi?id=157410 Eyal Rozenberg changed: What|Removed |Added Severity|enhancement |normal Status|UNCONFIRMED |NEW Ever confirmed|0 |1 --- Comment #3 from Eyal Rozenberg --- I would call gratuitous rasterization a bug. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 157410] Use SVG instead of bitmap when possible for HTML filters
https://bugs.documentfoundation.org/show_bug.cgi?id=157410 --- Comment #2 from Eyal Rozenberg --- Created attachment 190831 --> https://bugs.documentfoundation.org/attachment.cgi?id=190831=edit ODT with four vector-ish objects Document with the four types of objects suggested in the reproduction instructions. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 108741] [META] Shapes bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=108741 Eyal Rozenberg changed: What|Removed |Added Depends on||158217 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=158217 [Bug 158217] Default wrapping for shapes should be the same as for images, QRs etc. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 158217] Default wrapping for shapes should be the same as for images, QRs etc.
https://bugs.documentfoundation.org/show_bug.cgi?id=158217 Eyal Rozenberg changed: What|Removed |Added Blocks||108741 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=108741 [Bug 108741] [META] Shapes bugs and enhancements -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 158217] New: Default wrapping for shapes should be the same as for images, QRs etc.
https://bugs.documentfoundation.org/show_bug.cgi?id=158217 Bug ID: 158217 Summary: Default wrapping for shapes should be the same as for images, QRs etc. Product: LibreOffice Version: 24.2.0.0 alpha0+ Master Hardware: All OS: All Status: UNCONFIRMED Severity: minor Priority: medium Component: Writer Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: eyalr...@gmx.com If I insert a new shape in Writer, e.g. choosing Diamond in basic shapes and drawing a diamond - the created shape has a wrapping setting of "Through". If, however, I insert an image from a file, it has a wrapping setting of "Parallel". I believe shapes should default to "Parallel" wrapping as well. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 158215] Calc Function DAYS doesnt return the number of Days as **integer**
https://bugs.documentfoundation.org/show_bug.cgi?id=158215 --- Comment #1 from Werner Tietz --- additional: the odf-standard is not exactly clear about whole number or Fraction: http://docs.oasis-open.org/office/v1.2/os/OpenDocument-v1.2-os-part2.html#DAYS Can somebody prove the behaviour in Excel? -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 157978] Libre spreadsheets don't pop up surface pro onscreen keyboard
https://bugs.documentfoundation.org/show_bug.cgi?id=157978 Eyal Rozenberg changed: What|Removed |Added Resolution|--- |INVALID Whiteboard| QA:needsComment| Status|NEW |RESOLVED --- Comment #2 from Eyal Rozenberg --- LibreOffice itself, AFAICT, does not offer an integrated on-screen/virtual keyboard. I just tried using the Windows 10 integrated On-Screen Keyboard application with LO Calc 7.6.2.1, and that worked fine. Closing as INVALID. If I have misunderstood - please clearly state the expected behavior, and give exact reproduction instructions (other than starting Calc and typing text). -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 158216] New: donut chart : space parameter between nested donuts
https://bugs.documentfoundation.org/show_bug.cgi?id=158216 Bug ID: 158216 Summary: donut chart : space parameter between nested donuts Product: LibreOffice Version: 7.3.7.2 release Hardware: All OS: All Status: UNCONFIRMED Severity: enhancement Priority: medium Component: Chart Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: jerome.bo...@laposte.net Created attachment 190830 --> https://bugs.documentfoundation.org/attachment.cgi?id=190830=edit On the left the nested donuts as they exist. On the right the nested donuts with a space. I would like to specify a space parameter between the nested donuts. This make easier the labels layout (possibly by hand). -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 158167] Calc: cannot move selected row (recent 24.2)
https://bugs.documentfoundation.org/show_bug.cgi?id=158167 --- Comment #6 from BogdanB --- (In reply to Timur from comment #5) > Created attachment 190825 [details] > Video > > This should be obvious, if reproducible. Exactly, but I don't reproduce with Version: 24.2.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: d646341e5ddc625d9cf69777b4be174aebb43700 CPU threads: 16; OS: Linux 6.2; UI render: default; VCL: x11 Locale: ro-RO (ro_RO.UTF-8); UI: en-US Calc: threaded nor with Version: 24.2.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: d646341e5ddc625d9cf69777b4be174aebb43700 CPU threads: 16; OS: Linux 6.2; 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.
[Libreoffice-bugs] [Bug 158215] New: Calc Function DAYS doesnt return the number of Days as **integer**
https://bugs.documentfoundation.org/show_bug.cgi?id=158215 Bug ID: 158215 Summary: Calc Function DAYS doesnt return the number of Days as **integer** Product: LibreOffice Version: Inherited From OOo Hardware: All OS: All Status: UNCONFIRMED Severity: normal Priority: medium Component: Calc Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: werner-ti...@arcor.de Description: The Help about DAYS states: it returns the whole Days without Decimal-fraction. See also: https://forum.openoffice.org/en/forum/viewtopic.php?p=542967#p542967 Steps to Reproduce: 1. Insert Function =DAYS(NOW();DATE(2023;11;1)) Actual Results: It returns 13.8744083253332 Expected Results: 2. It should return 13 Reproducible: Always User Profile Reset: No Additional Info: Version: 7.6.2.1 (AARCH64) / LibreOffice Community Build ID: 56f7684011345957bbf33a7ee678afaf4d2ba333 CPU threads: 4; OS: Linux 6.1; UI render: default; VCL: gtk3 Locale: de-DE (de_DE.UTF-8); UI: en-US Flatpak Calc: threaded -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 123648] [META] Custom shapes
https://bugs.documentfoundation.org/show_bug.cgi?id=123648 Bug 123648 depends on bug 157956, which changed state. Bug 157956 Summary: Modernize the "Flowchart Alternate Process" shape to use circular corner rounding in all sizes https://bugs.documentfoundation.org/show_bug.cgi?id=157956 What|Removed |Added Status|ASSIGNED|RESOLVED Resolution|--- |FIXED -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 158214] picture resizing problem in LibreOffice write mode
https://bugs.documentfoundation.org/show_bug.cgi?id=158214 m.a.riosv changed: What|Removed |Added Status|UNCONFIRMED |NEEDINFO Ever confirmed|0 |1 CC||miguelangelrv@libreoffice.o ||rg --- Comment #1 from m.a.riosv --- Please attach a sample file, and paste the information in Menu/Help/About LibreOffice, there is an icon to copy. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 158213] LibreOffice Writer incorrectly displays a .docx document with a table
https://bugs.documentfoundation.org/show_bug.cgi?id=158213 --- Comment #3 from Vitaliy D --- Thank you, I confirm that LibreOffice 24.2.0.0.alpha0+ opens and edits this document correctly. Next question: will these changes from the 24.2.0.0.alpha0+ be merged into a stable version of 7.6.x ? Or will they "live" only within 24.2.0.0.alpha until it becomes at least "beta" ? -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 158188] Trying to sign a PDF destroys the file
https://bugs.documentfoundation.org/show_bug.cgi?id=158188 --- Comment #5 from Julien Nabet --- (In reply to Wolf-Dieter Groll from comment #2) > I Am using Debian 12.2 and the LibreOffice version from its repository. > No, I have not yet tried another version of LibreOffice. After stressful > experiences with mixed versions in the package management, I avoid such > experiments whenever possible. > > So I would have to take the time to install another version in parallel > without jeopardizing the normal package management, but I first have to find > out how to do this without risk. I use Debian testing, LO version is 7.5.8.2 with Debian updated today. I didn't mean having 2 versions in the same time. You can stick to stable and retrieve LO from testing repo but I suppose it would also require to update some libs (gtk or kde for example). IMHO, Debian stable are more for servers than end user machines so it uses old versions with security fixes. SID are for "power users", those who are ready to test bleeding edge versions but know/are not afraid how to deal with potential critical bugs. Testing is a good compromise. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 157698] [META] Unify lockdown UX in the Options dialog
https://bugs.documentfoundation.org/show_bug.cgi?id=157698 Bug 157698 depends on bug 158134, which changed state. Bug 158134 Summary: Unify lockdown behavior of Options dialog page Writer - Comparison https://bugs.documentfoundation.org/show_bug.cgi?id=158134 What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |FIXED -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 158134] Unify lockdown behavior of Options dialog page Writer - Comparison
https://bugs.documentfoundation.org/show_bug.cgi?id=158134 Balázs Varga (allotropia) changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |FIXED -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 157698] [META] Unify lockdown UX in the Options dialog
https://bugs.documentfoundation.org/show_bug.cgi?id=157698 Bug 157698 depends on bug 158133, which changed state. Bug 158133 Summary: Unify lockdown behavior of Options dialog page Writer - Changes https://bugs.documentfoundation.org/show_bug.cgi?id=158133 What|Removed |Added Status|ASSIGNED|RESOLVED Resolution|--- |FIXED -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 158134] Unify lockdown behavior of Options dialog page Writer - Comparison
https://bugs.documentfoundation.org/show_bug.cgi?id=158134 Commit Notification changed: What|Removed |Added Whiteboard||target:24.2.0 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 158134] Unify lockdown behavior of Options dialog page Writer - Comparison
https://bugs.documentfoundation.org/show_bug.cgi?id=158134 --- Comment #2 from Commit Notification --- Balazs Varga committed a patch related to this issue. It has been pushed to "master": https://git.libreoffice.org/core/commit/bfee998e71e2b7e8bcf4a366a00219a9b0f59035 tdf#158134 - UI: Part 29 - Unify lockdown behavior of Options dialog It will be available in 24.2.0. The patch should be included in the daily builds available at https://dev-builds.libreoffice.org/daily/ in the next 24-48 hours. More information about daily builds can be found at: https://wiki.documentfoundation.org/Testing_Daily_Builds Affected users are encouraged to test the fix and report feedback. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 157698] [META] Unify lockdown UX in the Options dialog
https://bugs.documentfoundation.org/show_bug.cgi?id=157698 Bug 157698 depends on bug 158131, which changed state. Bug 158131 Summary: Unify lockdown behavior of Options dialog page Writer - Table https://bugs.documentfoundation.org/show_bug.cgi?id=158131 What|Removed |Added Status|ASSIGNED|RESOLVED Resolution|--- |FIXED -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 158188] Trying to sign a PDF destroys the file
https://bugs.documentfoundation.org/show_bug.cgi?id=158188 raal changed: What|Removed |Added CC||r...@post.cz --- Comment #4 from raal --- (In reply to Wolf-Dieter Groll from comment #2) > > So I would have to take the time to install another version in parallel > without jeopardizing the normal package management, but I first have to find > out how to do this without risk. Hello, you can use AppImage https://www.libreoffice.org/download/appimage/ -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 158213] LibreOffice Writer incorrectly displays a .docx document with a table
https://bugs.documentfoundation.org/show_bug.cgi?id=158213 raal changed: What|Removed |Added CC||r...@post.cz --- Comment #2 from raal --- Created attachment 190829 --> https://bugs.documentfoundation.org/attachment.cgi?id=190829=edit prinstcreen No repro with Version: 24.2.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: 41d9584179ef7b4e18eda47c2c0a955df8c087a5 CPU threads: 4; OS: Linux 6.2; UI render: default; VCL: gtk3 Locale: cs-CZ (cs_CZ.UTF-8); UI: en-US Calc: threaded Seems to be fixed with dev version. Please could you test it with dev version? You can download it here: http://dev-builds.libreoffice.org/daily/master/ Thank you -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 158214] New: picture resizing problem in LibreOffice write mode
https://bugs.documentfoundation.org/show_bug.cgi?id=158214 Bug ID: 158214 Summary: picture resizing problem in LibreOffice write mode Product: LibreOffice Version: 7.6.2.1 release Hardware: x86-64 (AMD64) OS: Windows (All) Status: UNCONFIRMED Severity: normal Priority: medium Component: LibreOffice Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: pkwiere...@gmail.com Description: If a picture imported in write is rotated (90 degr right), enlarging to almost full pagesize is not possible. Enlarging height reduces width. Steps to Reproduce: 1.import a picture in write (A4 page size) 2.rotate it 90 degrees right (right button popup > turn or mirror > 90 degr richt 3.try to enlarge it to page size Actual Results: In stead of enlarging the height of the picture its width is reduced. Expected Results: the picture is page filling Reproducible: Always User Profile Reset: Yes Additional Info: I'm using the Dutch language version -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 158196] Add 'shuffle' or 'random' option to 'Sort' dialog
https://bugs.documentfoundation.org/show_bug.cgi?id=158196 --- Comment #13 from j22...@gmail.com --- (In reply to Tomaz Vajngerl from comment #10) > (In reply to Werner Tietz from comment #9) > > I don't agree with that, »shuffle« is the complete opposite of »sorting«. > > It's an almost identical action - shuffle is sort with an random order > instead of derived from the content. > > > If it is, then it should be another Option under →→Sheet→→Fill Cells→→Fill > > Random Numbers > > This has nothing to do with filling cells - it's shuffling existing cells, > so why it should be added there. The only thing in common with the random > number generator is that the actions do something randomly. Agree. 'Sort' in this context is an umbrella term for 're-arrange the elements'. The re-arrangement could be either in a given order (ascending, descending) or in a purposedly 'unordered' fashion (i.e. random). -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 158196] Add 'shuffle' or 'random' option to 'Sort' dialog
https://bugs.documentfoundation.org/show_bug.cgi?id=158196 --- Comment #12 from j22...@gmail.com --- (In reply to J22Gim from comment #11) > (In reply to Heiko Tietze from comment #5) > > (In reply to J22Gim from comment #0) > > > I propose to add a 'Shuffle' option available in the 'Sort' menu. > > Drawback is that the option bloats the UI. And it's rather unexpected to > > sort up/down and random. But the extra UNO command, as suggested by Rafael, > > to shuffle data sounds straightforward to me, at least for row/column. Don't > > get the "values in range". > > Nice! Agree. 'Sort' in this context is an umbrella term for 're-arrange the elements'. The re-arrangement could be either in a given order (ascending, descending) or in a purposedly 'unordered' fashion (i.e. random). -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 158196] Add 'shuffle' or 'random' option to 'Sort' dialog
https://bugs.documentfoundation.org/show_bug.cgi?id=158196 --- Comment #11 from j22...@gmail.com --- (In reply to Heiko Tietze from comment #5) > (In reply to J22Gim from comment #0) > > I propose to add a 'Shuffle' option available in the 'Sort' menu. > Drawback is that the option bloats the UI. And it's rather unexpected to > sort up/down and random. But the extra UNO command, as suggested by Rafael, > to shuffle data sounds straightforward to me, at least for row/column. Don't > get the "values in range". Nice! -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 158211] Form input writes over protected cells
https://bugs.documentfoundation.org/show_bug.cgi?id=158211 --- Comment #4 from m.a.riosv --- Please attach a sample file. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 158213] LibreOffice Writer incorrectly displays a .docx document with a table
https://bugs.documentfoundation.org/show_bug.cgi?id=158213 --- Comment #1 from Vitaliy D --- Created attachment 190828 --> https://bugs.documentfoundation.org/attachment.cgi?id=190828=edit The file that demonstrates the problem -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 158213] New: LibreOffice Writer incorrectly displays a .docx document with a table
https://bugs.documentfoundation.org/show_bug.cgi?id=158213 Bug ID: 158213 Summary: LibreOffice Writer incorrectly displays a .docx document with a table Product: LibreOffice Version: 7.5.8.2 release Hardware: x86-64 (AMD64) OS: Windows (All) Status: UNCONFIRMED Severity: normal Priority: medium Component: Writer Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: dv...@ukr.net Description: When a .docx document that contains a big table is opened in LibreOffice Writer, the table and the text in it are shown somewhat "condensed" where the text from the next cells intersects with the text from the previous cells, making it impossible to read and work with the document. Steps to Reproduce: 1. Open the attached file "example.docx" 2. Observe the results 3. Actual Results: It's not possible to read and work with the content of the document. Expected Results: The text in the table should be completely visible. Reproducible: Always User Profile Reset: Yes Additional Info: Version: 7.5.8.2 (X86_64) / LibreOffice Community Build ID: f718d63693263970429a68f568db6046aaa9df01 CPU threads: 4; OS: Windows 10.0 Build 19045; UI render: Skia/Raster; VCL: win Locale: ru-RU (ru_RU); UI: ru-RU Calc: threaded -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 158212] Crash on M1 Silicon Mac when using Zoom Accessibility on Mac
https://bugs.documentfoundation.org/show_bug.cgi?id=158212 Christian Lohmaier changed: What|Removed |Added CC||cl...@documentfoundation.or ||g --- Comment #2 from Christian Lohmaier --- cannot reproduce on a M1 macbook air and 7.5.8 (aarch64) on Ventura (13.6.1) I use ctrl+two-finger-on-touchpad to zoom in/out, but I don't think that matters... bug#132999 likely is duplicate/related, but I cannot even provoke any problem trying to repeatedly opening/closing the about dialog like I could back then so couple questions: * Are you using the intel build via Rosetta or are you using native aarch64 build? (about dialog should tell) * What version of macOS? * any other accessibility features enabled? * can you still reproduce when you update to 7.5.8 or 7.6.2? -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 158211] Form input writes over protected cells
https://bugs.documentfoundation.org/show_bug.cgi?id=158211 --- Comment #3 from Daan --- Hi, "form" is a way of entering data in cells. You can find it under Data - Form. I've noticed I worked on an old version indeed, so I installed both Flatpack and Appimage versions and tried again. But another worse bug appears now. If I select protected cells by ctrl-a in a protected sheet and use the "form" function the whole program freezes. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 158211] Form input writes over protected cells
https://bugs.documentfoundation.org/show_bug.cgi?id=158211 --- Comment #2 from Daan --- Hi, "form" is a way of entering data in cells. You can find it under Data - Form. I've noticed I worked on an old version indeed, so I installed both Flatpack and Appimage versions and tried again. But another worse bug appears now. If I select protected cells (in a protected sheet) and use the "form" function the whole program freezes. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 158210] Slide background transparency lost
https://bugs.documentfoundation.org/show_bug.cgi?id=158210 V Stuart Foote changed: What|Removed |Added CC||vsfo...@libreoffice.org --- Comment #2 from V Stuart Foote --- Can not confirm. Are you saving from Impress to ODP .odp, or to MS Office Open XML .pptx? For me, slide background JPEG set transparent kept that transparency for both file formats on reopen. Please attach your test presentation. =-testing-= Version: 24.2.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: 50add2043752c7b07beccef9a509bea6c09619f8 CPU threads: 8; OS: Windows 10.0 Build 19045; UI render: Skia/Vulkan; VCL: win Locale: en-US (en_US); UI: en-US Calc: threaded -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 158210] Slide background transparency lost
https://bugs.documentfoundation.org/show_bug.cgi?id=158210 Stéphane Guillou (stragu) changed: What|Removed |Added Ever confirmed|0 |1 CC||stephane.guillou@libreoffic ||e.org Status|UNCONFIRMED |NEEDINFO Summary|LIBRE OFFICE IMPRESS, |Slide background |VERSION 7.6.2.1 |transparency lost --- Comment #1 from Stéphane Guillou (stragu) --- Not reproduced in: Version: 7.6.3.1 (X86_64) / LibreOffice Community Build ID: c4af5b1259bceea6e979e6fe2435dbee7a5a87c2 CPU threads: 8; OS: Linux 5.15; UI render: default; VCL: gtk3 Locale: en-AU (en_AU.UTF-8); UI: en-US Calc: threaded My steps: 1. New Impress doc 2. change slide background to solid color, and to 50% transparency (from Slide properties dialog) 3. Save and reload Can you maybe attach an example document in which you reproduce the issue? -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 158189] Hidden page break with multiple columns and table at the page beginning
https://bugs.documentfoundation.org/show_bug.cgi?id=158189 --- Comment #2 from de...@web.de --- Yes, if you press Return in the very first table cell, the table moves down one row and the dashed line is visible again. There seems to be other strange behavior (broken redo log) with tables and page columns: On an empty document: 1. Apply "Columns: 2" to the "Default Page Style" 2. insert table (Ctrl+F12 and Return) 3. insert col break (Ctrl+Shift+Return) (seemingly nothing happens) 4. insert new paragraph (Return) 5. insert col break (Ctrl+Shift+Return) 6. remove first line (Del Key) The dashed line (which indicates a column break) is also hidden here. But now the redo log seems to be broken. The following actions are displayed when you move the mouse pointer over the undo button after performing each of the above actions. 1. Undo: Change style: Default Page Style 2. Undo: Insert table: "Table1" 3. Undo: Change style: Table1 This logged action seems wrong to me. 4. Undo: New Paragraph 5. Undo: Insert column break 6. Undo: Delete Paragraphs Pressing the undo button from the toolbar (or Ctrl+Z, similar), the following things happen: 1. Undo: Delete Paragraphs The Table disappears, the man. col break appears, the removed pilcrow appears (Formatting Marks shown). 2. Undo: Insert column break The Table appears, the man. col break disappears, the pilcrow disappears. Table remains in second col. 3. Undo: New Paragraph The table moves to the first page. 4. Undo: Change style: Table1 seemingly nothing happens 5. Undo: Insert table: "Table1" The table disappears 6. Undo: Change style: Default Page Style The Document changes to one column. Redo the undone things results in another result than before: 6. Redo: Change style: Default Page Style The Document changes to two columns. 5. Redo: Insert table: "Table1" The table appears 4. Redo: Change style: Table1 seemingly nothing happens 3. Redo: New Paragraph The table remains on the first page and moves one line down 2. Redo: Insert column break The Table moves to the second col, second line, and the col break dashed line is shown 1. Redo: Delete Paragraphs The Table moves back to the first col, the dashed line goes away Maybe, this should be placed in a new issue? -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 158212] Crash on M1 Silicon Mac when using Zoom Accessibility on Mac
https://bugs.documentfoundation.org/show_bug.cgi?id=158212 --- Comment #1 from Oliver King-Smith --- Created attachment 190827 --> https://bugs.documentfoundation.org/attachment.cgi?id=190827=edit Crash logs -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 158212] New: Crash on M1 Silicon Mac when using Zoom Accessibility on Mac
https://bugs.documentfoundation.org/show_bug.cgi?id=158212 Bug ID: 158212 Summary: Crash on M1 Silicon Mac when using Zoom Accessibility on Mac Product: LibreOffice Version: 7.5.2.2 release Hardware: ARM OS: macOS (All) Status: UNCONFIRMED Severity: normal Priority: medium Component: Base Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: oliver...@yahoo.com Description: Boot up LibreOffice. Switch to another program. Change the zoom level for the screen. Switch back to LibreOffice. More often than not you will get a crash. I have attached the crash log. Note this has been a problem on all versions of LibreOffice since I switched to M1 silicon. I don't recall ever having a problem on my x86 Macs. Steps to Reproduce: 1.Open LibreOffice 2.Start using a Text Document 3.Switch to another application 4.Change zoom level (I use the keyboard commands to change zoom level) 5.Switch back to LibreOffice Actual Results: Hard crash Expected Results: No crash It took longer to crash in safe mode, but it still crashed and gave the attached log Reproducible: Sometimes User Profile Reset: Yes Additional Info: Note this seems to be an M1 Mac Problem, but I haven't seen it on other programsso I think it might be a LibreOffice bug. It doesn't seem to happen on my x86 mac (or if it does it is a lot rarer). -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 158211] Form input writes over protected cells
https://bugs.documentfoundation.org/show_bug.cgi?id=158211 m.a.riosv changed: What|Removed |Added Ever confirmed|0 |1 Status|UNCONFIRMED |NEEDINFO -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 158211] Form input writes over protected cells
https://bugs.documentfoundation.org/show_bug.cgi?id=158211 m.a.riosv changed: What|Removed |Added CC||miguelangelrv@libreoffice.o ||rg --- Comment #1 from m.a.riosv --- First, your version it's a bit old. Have you protected the sheet: Menu/Tools/Protect sheet. https://help.libreoffice.org/latest/en-US/text/scalc/01/06060100.html?DbPAR=CALC#bm_id141619439455954 No clear for me your steps, what is the meaning the use a form to input after select all. And what form do you use? -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 147365] Don't Print but export to PDF - Picture settings should allow to set not to print but show in PDF
https://bugs.documentfoundation.org/show_bug.cgi?id=147365 --- Comment #11 from V Stuart Foote --- What about print to PDF using gs/ps based libs? Why any different? So NO, lets not attempt distinction in handling raster images (i.e. pictures) between printing filters and export filters to PDF/EPUB beyond what is already necessary for handling the raster image object frames. Not worth and dev or OASIS ODF extension effort, IMHO => WF -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 147365] Don't Print but export to PDF - Picture settings should allow to set not to print but show in PDF
https://bugs.documentfoundation.org/show_bug.cgi?id=147365 --- Comment #10 from Mannshoch --- Ah sorry, it seems I did not understand. I also not know what WF means. Sorry. I hope that someone others could help here in this case. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 108075] [META] Scrolling and Page up/down issues
https://bugs.documentfoundation.org/show_bug.cgi?id=108075 Bug 108075 depends on bug 58510, which changed state. Bug 58510 Summary: UI: distorted screen during scrolling. https://bugs.documentfoundation.org/show_bug.cgi?id=58510 What|Removed |Added Status|RESOLVED|NEW Resolution|WORKSFORME |--- -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 58510] UI: distorted screen during scrolling.
https://bugs.documentfoundation.org/show_bug.cgi?id=58510 ady changed: What|Removed |Added Status|RESOLVED|NEW Resolution|WORKSFORME |--- --- Comment #15 from ady --- (In reply to Steven Casey from comment #14) > I have not personally checked older versions. OK, so let's reset the report to NEW as it was before, until the problem can be reproduced in an older version but not on a new/current version of LO on the same system. IOW, both tests are needed in order to set the report as WFM. Perhaps at least one of the earlier reporters that reproduced the problem can confirm whether the problem is solved with a current version of LO. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 140411] Calc constantly re-calculating (bug in the sheet?)
https://bugs.documentfoundation.org/show_bug.cgi?id=140411 Stéphane Guillou (stragu) changed: What|Removed |Added Ever confirmed|0 |1 CC||stephane.guillou@libreoffic ||e.org Whiteboard| QA:needsComment| Status|UNCONFIRMED |NEEDINFO --- Comment #4 from Stéphane Guillou (stragu) --- Thanks for the report. Have you mentioned the issue on the project's GitHub? Does it still happen with the latest version of the extension, from July 2023 (at the time of writing) and the latest version of LibreOffice? -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 157978] Libre spreadsheets don't pop up surface pro onscreen keyboard
https://bugs.documentfoundation.org/show_bug.cgi?id=157978 Sophie Sipasseuth changed: What|Removed |Added Ever confirmed|0 |1 Status|UNCONFIRMED |NEW -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 157978] Libre spreadsheets don't pop up surface pro onscreen keyboard
https://bugs.documentfoundation.org/show_bug.cgi?id=157978 --- Comment #1 from Sophie Sipasseuth --- I also didn't find how to display a virtual keyboard in calc. But it seems it is possible to install one like Onboard. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 150614] crash when editing a HTML document and multiple documents open in Writer
https://bugs.documentfoundation.org/show_bug.cgi?id=150614 Stéphane Guillou (stragu) changed: What|Removed |Added Depends on|158005 | Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=158005 [Bug 158005] Character formatting border should be drawn around both Kanji and hiragana characters in Japanese text with furigana notation -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 50607] [META] Asian Phonetic Guide ( Ruby ) issues
https://bugs.documentfoundation.org/show_bug.cgi?id=50607 Stéphane Guillou (stragu) changed: What|Removed |Added Depends on||158005 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=158005 [Bug 158005] Character formatting border should be drawn around both Kanji and hiragana characters in Japanese text with furigana notation -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 158005] Character formatting border should be drawn around both Kanji and hiragana characters in Japanese text with furigana notation
https://bugs.documentfoundation.org/show_bug.cgi?id=158005 Stéphane Guillou (stragu) changed: What|Removed |Added Blocks|150614 |50607 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=50607 [Bug 50607] [META] Asian Phonetic Guide ( Ruby ) issues https://bugs.documentfoundation.org/show_bug.cgi?id=150614 [Bug 150614] crash when editing a HTML document and multiple documents open in Writer -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 150614] crash when editing a HTML document and multiple documents open in Writer
https://bugs.documentfoundation.org/show_bug.cgi?id=150614 Stéphane Guillou (stragu) changed: What|Removed |Added Depends on||158005 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=158005 [Bug 158005] Character formatting border should be drawn around both Kanji and hiragana characters in Japanese text with furigana notation -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 158005] Character formatting border should be drawn around both Kanji and hiragana characters in Japanese text with furigana notation
https://bugs.documentfoundation.org/show_bug.cgi?id=158005 Stéphane Guillou (stragu) changed: What|Removed |Added Severity|minor |enhancement Blocks||150614 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=150614 [Bug 150614] crash when editing a HTML document and multiple documents open in Writer -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 158005] Character formatting border should be drawn around both Kanji and hiragana characters in Japanese text with furigana notation
https://bugs.documentfoundation.org/show_bug.cgi?id=158005 Stéphane Guillou (stragu) changed: What|Removed |Added CC||stephane.guillou@libreoffic ||e.org --- Comment #6 from Stéphane Guillou (stragu) --- Created attachment 190826 --> https://bugs.documentfoundation.org/attachment.cgi?id=190826=edit screenshot of difference between with and without rubies (LO 24.2alpha0+) At least, reproducing the bug that character borders look very broken when applied on text with ruby characters. See attached screenshot showing character vs paragraph borders on text with vs without ruby characters. So, as I see it, two separate things here: (1) clearly broken extension of borders over the whitespace. This should at least behave the same as in text without ruby characters: one single box that includes the whitespace. We can track this in a separate report. (2) the focus of this report: an enhancement request to include the ruby characters inside the kanji's character border, possibly using a non-rectangular frame. Not sure this is possible without a fundamental change, as ruby characters have their own, separate character style. With the current way it is implemented, it's either kanji and harigana in two separate boxes (by editing the character style/formatting), or the whole paragraph in a single box (changing the paragraph style/formatting). Version: 24.2.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: 79f92d09ec52f0777fc03ff1d057a11b45e73f6d CPU threads: 8; OS: Linux 5.15; UI render: default; VCL: gtk3 Locale: en-AU (en_AU.UTF-8); UI: en-US Calc: threaded -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 158196] Add 'shuffle' or 'random' option to 'Sort' dialog
https://bugs.documentfoundation.org/show_bug.cgi?id=158196 --- Comment #10 from Tomaz Vajngerl --- (In reply to Werner Tietz from comment #9) > I don't agree with that, »shuffle« is the complete opposite of »sorting«. It's an almost identical action - shuffle is sort with an random order instead of derived from the content. > If it is, then it should be another Option under →→Sheet→→Fill Cells→→Fill > Random Numbers This has nothing to do with filling cells - it's shuffling existing cells, so why it should be added there. The only thing in common with the random number generator is that the actions do something randomly. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 148878] If a CSV file doesn't keep delimiter
https://bugs.documentfoundation.org/show_bug.cgi?id=148878 Timur changed: What|Removed |Added Status|UNCONFIRMED |NEEDINFO Ever confirmed|0 |1 --- Comment #7 from Timur --- Needinfo once more for the last comment, or NotABug. -- You are receiving this mail because: You are the assignee for the bug.
