[Libreoffice-bugs] [Bug 45949] SPELL check does not work for words with hyperlink
https://bugs.documentfoundation.org/show_bug.cgi?id=45949 --- Comment #20 from Mike Kaganski --- (In reply to László Németh from comment #15) > http://specs.openoffice.org/appwide/linguistic/Spellcheckdialog.sxw, > see also https://bz.apache.org/ooo/show_bug.cgi?id=40133. ... and these two also talk about general implementations, applicable to all components. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153317] New: MySQL/MariaDB direct connection: Content of field type 'Bit' isn't shown in Tools → SQL
https://bugs.documentfoundation.org/show_bug.cgi?id=153317 Bug ID: 153317 Summary: MySQL/MariaDB direct connection: Content of field type 'Bit' isn't shown in Tools → SQL Product: LibreOffice Version: 7.4.5.1 release Hardware: x86-64 (AMD64) OS: Linux (All) Status: UNCONFIRMED Severity: normal Priority: medium Component: Base Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: rob...@familiegrosskopf.de You will need a direct connection to MariaDB (or MySQL) for testing this bug. Create a field in a table as field type bit(1). Something like CREATE TABLE `test`.`tbl_Test` ( `ID` int(10) NOT NULL PRIMARY KEY, `Text` varchar(100) DEFAULT NULL, `Confirm` bit(1) DEFAULT NULL ); Add some content and click on "Confirm" for some rows. Execute this query in SQL-Mode: SELECT * FROM `test`.`tbl_Test` Will show the content of `Confirm` without problems. Now go to Tools → SQL. Set "Show output …". Execute the same query. No content appears for column `Confirm`. Same behavior will appear if you start the query by macro. No value could be found. Change the query: SELECT `ID`, `Text`, CASE WHEN `Confirm` THEN 1 ELSE 0 END FROM `test`.`tbl_Test` This query will give the correct 'values' for `Confirm`. Field type bit(1) couldn't be read directly through Tools → SQL or by macro with direct connection to MariaDB. This bug won't appear with JDBC connection to the same database. Tested with LO 7.4.5.1 on OpenSUSE 15.3 64bit rpm Linux. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 45949] SPELL check does not work for words with hyperlink
https://bugs.documentfoundation.org/show_bug.cgi?id=45949 --- Comment #19 from Mike Kaganski --- Is there a tracker for other components (Calc, Impress) - since this is fixed for Writer, but its component is Linguistic? -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 152724] FILESAVE FORMATTING Cell custom Format Code with _- (UI visible space width) is not saved correctly
https://bugs.documentfoundation.org/show_bug.cgi?id=152724 --- Comment #13 from ady --- (In reply to Laurent Balland from comment #12) > ? is now fixed in master (see bug 118324) TY. > 0 was already treated I'd like to emphasize that combining "?0" was not working in 7.4.4.2 for ods. I understand that you worked on the "?" part for 7.6; my point is that saying "0 was already treated" might be confusing to users, since the combination of "0" with some of the other codes was not working. > 0 was already treated, and any "reasonable" format combining #, ? and 0 > should be preserved in ODF in integer and decimal part. Would you please be so kind and mention here some example of "unreasonable" combination of "#, ? and 0"? Not only it would help for testing (now and in future versions), but especially to be aware and to be able to provide such information to other users. > _x still needs an ODF extension. I accordingly modified the summary. Would this RFE be assigned to someone for that? I compared the following 2 versions with an .ods file: Version: 7.6.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: d8e6b488ceaff7c88856ebcfcfec14d2d8cd7652 CPU threads: 4; OS: Windows 10.0 Build 19044; UI render: Skia/Raster; VCL: win Locale: en-US (es_AR); UI: en-US Calc: CL threaded Version: 7.4.4.2 (x64) / LibreOffice Community Build ID: 85569322deea74ec9134968a29af2df5663baa21 CPU threads: 4; OS: Windows 10.0 Build 19044; UI render: default; VCL: win Locale: en-US (es_AR); UI: en-US Calc: CL Steps and Results (in the same order as described here): With 7.4.4.2: Saved as: _-?0;-?0;_-?0;@ Opened as: [>0]" "#;[<0]-#;" "#;@ Then with 7.6.0.0.alpha0+... Saved as: _-?0;-?0;_-?0;@ Opened as: [>0]" "?0;[<0]-?0;" "?0;@ Then closed without saving, and opened it in 7.4.4.2: [>0]" "00;[<0]-00;" "00;@ Please note the double zeros in the last one. Whether this could generate problems with users sharing files between different versions of LO, IDK. Whether this can be avoided, IDK either. (On a side note, the ods file seemed to be opened slightly slower in the aforementioned 7.6.0.0.alpha0+ than in 7.4.4.2.) -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153298] A complex formula does not work in Calc 7.4.x
https://bugs.documentfoundation.org/show_bug.cgi?id=153298 --- Comment #2 from Yurij --- Created attachment 185057 --> https://bugs.documentfoundation.org/attachment.cgi?id=185057=edit The table of monthly results of the work of employees with the forms of output of annual reports. Any change in the parameter of any sheet from "LIST" to "Ser" in the "DOWN" sheet will delete all data. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 94074] If you select an image direct after caption was selected, imagerelated entries in contextmenu are missing
https://bugs.documentfoundation.org/show_bug.cgi?id=94074 --- Comment #11 from Dieter --- Still present in Version: 7.5.0.2 (X86_64) / LibreOffice Community Build ID: c0dd1bc3f1a385d110b88e26ece634da94921f58 CPU threads: 4; OS: Windows 10.0 Build 19044; UI render: default; VCL: win Locale: de-DE (de_DE); UI: de-DE Calc: threaded Steps to Reproduce: 1. Open attachment 184581 2. Select the frame. 3. Select the image. 4. Right click on the image. 5. The frame context menu will be displayed. (see properties entry in context menu) -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 86349] [META] Context menu bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=86349 Dieter changed: What|Removed |Added Depends on||94074 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=94074 [Bug 94074] If you select an image direct after caption was selected, imagerelated entries in contextmenu are missing -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 80649] Frame context menu appears on picture when anchored as character, when context menu is started immediately after another picture was selected
https://bugs.documentfoundation.org/show_bug.cgi?id=80649 Dieter changed: What|Removed |Added See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=94 ||074 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 94074] If you select an image direct after caption was selected, imagerelated entries in contextmenu are missing
https://bugs.documentfoundation.org/show_bug.cgi?id=94074 Dieter changed: What|Removed |Added Blocks||86349 CC||dgp-m...@gmx.de Keywords|needsDevEval| See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=80 ||649 --- Comment #10 from Dieter --- At least related to bug 80649 (not a duplicate, bug is also present with an image anchored to character) Problem is, that context image context menu doesn't miss some entries. but it is the frame context menu. You can easily see, that it is frame context menu, if you select properties. Don't know, if we still need DevEval here, because it doesn't happen anything since 2015!!!. I remove it. Buovyaga, feel free to add it again, if you think it is necessary. Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=86349 [Bug 86349] [META] Context menu bugs and enhancements -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 103152] [META] Writer image bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=103152 Bug 103152 depends on bug 152975, which changed state. Bug 152975 Summary: [UI/UX bug] Right-clicking on a selected image shows the frame's context menu when the frame was previously selected https://bugs.documentfoundation.org/show_bug.cgi?id=152975 What|Removed |Added Status|NEW |RESOLVED Resolution|--- |DUPLICATE -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 86349] [META] Context menu bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=86349 Bug 86349 depends on bug 152975, which changed state. Bug 152975 Summary: [UI/UX bug] Right-clicking on a selected image shows the frame's context menu when the frame was previously selected https://bugs.documentfoundation.org/show_bug.cgi?id=152975 What|Removed |Added Status|NEW |RESOLVED Resolution|--- |DUPLICATE -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 94074] If you select an image direct after caption was selected, imagerelated entries in contextmenu are missing
https://bugs.documentfoundation.org/show_bug.cgi?id=94074 Dieter changed: What|Removed |Added CC||piotr.os...@gmail.com --- Comment #9 from Dieter --- *** Bug 152975 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 152975] [UI/UX bug] Right-clicking on a selected image shows the frame's context menu when the frame was previously selected
https://bugs.documentfoundation.org/show_bug.cgi?id=152975 Dieter changed: What|Removed |Added Status|NEW |RESOLVED Resolution|--- |DUPLICATE --- Comment #7 from Dieter --- Looks like a duplicate of bug 94074 and at least related to bug 80649 (not a duplicate, bug is also present with an image anchored to character) *** This bug has been marked as a duplicate of bug 94074 *** -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 152975] [UI/UX bug] Right-clicking on a selected image shows the frame's context menu when the frame was previously selected
https://bugs.documentfoundation.org/show_bug.cgi?id=152975 Dieter changed: What|Removed |Added Ever confirmed|0 |1 Status|UNCONFIRMED |NEW CC||dgp-m...@gmx.de Whiteboard| QA:needsComment| Blocks||103152 --- Comment #6 from Dieter --- I confirm it with Version: 7.5.0.2 (X86_64) / LibreOffice Community Build ID: c0dd1bc3f1a385d110b88e26ece634da94921f58 CPU threads: 4; OS: Windows 10.0 Build 19044; UI render: default; VCL: win Locale: de-DE (de_DE); UI: de-DE Calc: threaded You can easily see, that it is frame context menu, if you select properties => frame dialog opens Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=103152 [Bug 103152] [META] Writer image bugs and enhancements -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 103152] [META] Writer image bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=103152 Dieter changed: What|Removed |Added Depends on||152975 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=152975 [Bug 152975] [UI/UX bug] Right-clicking on a selected image shows the frame's context menu when the frame was previously selected -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 35092] Inking functionality: Ink drawings / annotations with Stylus, Pen or Finger on Touchscreen or Tablet
https://bugs.documentfoundation.org/show_bug.cgi?id=35092 --- Comment #176 from jamesstone7575 --- https://www.newassignmenthelp.co.uk/resume-writing-services/;>Resume Writing Services from expert writers. Our team is extremely knowledgeable and skilled, and we can provide you authentic assignment writing services on schedule. Get writing help for all subjects that is quick, original, and flawless with a 100% guarantee. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 38844] Reduce XOR rendering (search RasterOp::Xor)
https://bugs.documentfoundation.org/show_bug.cgi?id=38844 dipamt1...@gmail.com changed: What|Removed |Added Status|NEW |ASSIGNED Assignee|libreoffice-b...@lists.free |dipamt1...@gmail.com |desktop.org | --- Comment #35 from dipamt1...@gmail.com --- I would like to work on this issue. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153316] New: Libre calc auto add/convert tab space to SOH
https://bugs.documentfoundation.org/show_bug.cgi?id=153316 Bug ID: 153316 Summary: Libre calc auto add/convert tab space to SOH Product: LibreOffice Version: 7.4.5.1 release Hardware: All OS: Windows (All) Status: UNCONFIRMED Severity: normal Priority: medium Component: Calc Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: a19...@gmail.com Created attachment 185056 --> https://bugs.documentfoundation.org/attachment.cgi?id=185056=edit Libre calc auto add/convert tab space to SOH I copy (ctrl + c) some VB code (with tab space in some line) EX: if isnull(ld_menu) or ld_menu = 0 then else select menu_name,menu_ename into :ls_menu_name,:ls_menu_en from sy_menus where menu_id = :ld_menu; if ls_menu_en <> '' then dw_100.object.st_100.text = ls_menu_name dw_100.object.st_101.text = ls_menu_en end if end if then open Libre cacl, dupble click a cell -> paste (ctrl +v). I copy that cell, paste to VB script editor, and the scipt cannot run. For check, i paste to Notepad++, and found some special charater (SOH) cause the problem. Please refer the picture. Please help me to check this. Thanks and best regards. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 152801] Input text for a formatted text box shows up as light gray instead of black.
https://bugs.documentfoundation.org/show_bug.cgi?id=152801 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 148178] SVG Export from macro in old version of SVG
https://bugs.documentfoundation.org/show_bug.cgi?id=148178 --- Comment #4 from QA Administrators --- [Automated Action] NeedInfo-To-Unconfirmed -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 99559] If table has bad header (made in MS Word) LO Writer doesn't show the first row of data.
https://bugs.documentfoundation.org/show_bug.cgi?id=99559 --- Comment #13 from QA Administrators --- Dear inforbano, 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 152975] [UI/UX bug] Right-clicking on a selected image shows the frame's context menu when the frame was previously selected
https://bugs.documentfoundation.org/show_bug.cgi?id=152975 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 90026] OLE Object Toolbar
https://bugs.documentfoundation.org/show_bug.cgi?id=90026 --- Comment #7 from QA Administrators --- Dear Xavier Verne, 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 45721] Removing horizontal rule inserted by AutoCorrect (paragraph border) is unintuitive
https://bugs.documentfoundation.org/show_bug.cgi?id=45721 --- Comment #20 from QA Administrators --- Dear Dotan Cohen, 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 140069] View -> User Interface, not available in Master Document (Writer)
https://bugs.documentfoundation.org/show_bug.cgi?id=140069 --- Comment #2 from QA Administrators --- Dear drei, 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 134201] Crash after pasting several times, then undoing those, then redoing
https://bugs.documentfoundation.org/show_bug.cgi?id=134201 --- Comment #13 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.
[Libreoffice-bugs] [Bug 108777] Undo doesnt work after setting 'Resize shape to fit text'
https://bugs.documentfoundation.org/show_bug.cgi?id=108777 --- Comment #10 from QA Administrators --- Dear Yousuf Philips (jay) (retired), 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 103593] can not drag table border to resize table in writer text table
https://bugs.documentfoundation.org/show_bug.cgi?id=103593 --- Comment #9 from QA Administrators --- Dear baigali, 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 103581] RTL tables inside RTL two-column sections partly disappear and run over the section
https://bugs.documentfoundation.org/show_bug.cgi?id=103581 --- Comment #9 from QA Administrators --- Dear antanins, 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 101019] Table - changing column width in a table with merged cells is effective only in one row
https://bugs.documentfoundation.org/show_bug.cgi?id=101019 --- Comment #12 from QA Administrators --- Dear Heinrich Hartl, 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 153315] EDITING - Crash after changing font size in style causing reformatting the document
https://bugs.documentfoundation.org/show_bug.cgi?id=153315 Yves Poissant changed: What|Removed |Added Crash report or||d8608389-1417-4856-87e0-a5d crash signature||3cb87ba39 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 142209] FILE SAVE:CALC: EXCEL compatibility issue for xlsx files containing checkboxes
https://bugs.documentfoundation.org/show_bug.cgi?id=142209 Aron Budea changed: What|Removed |Added Whiteboard||target:7.3.0 CC||aron.bu...@gmail.com -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 108256] EDITING: find/replace regular expressions: \n has 2 meanings, it shouldn't
https://bugs.documentfoundation.org/show_bug.cgi?id=108256 V Stuart Foote changed: What|Removed |Added CC||villapal...@yahoo.it --- Comment #14 from V Stuart Foote --- *** Bug 153311 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153311] ¶ copy-past/search LibreOffice
https://bugs.documentfoundation.org/show_bug.cgi?id=153311 V Stuart Foote changed: What|Removed |Added Resolution|--- |DUPLICATE CC||vsfo...@libreoffice.org Status|UNCONFIRMED |RESOLVED --- Comment #3 from V Stuart Foote --- *** This bug has been marked as a duplicate of bug 108256 *** -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153315] EDITING - Crash after changing font size in style causing reformatting the document
https://bugs.documentfoundation.org/show_bug.cgi?id=153315 --- Comment #2 from Yves Poissant --- Oups! I see that I interverted "Actual Result" with "Expected result". Sorry -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153315] EDITING - Crash after changing font size in style causing reformatting the document
https://bugs.documentfoundation.org/show_bug.cgi?id=153315 Yves Poissant changed: What|Removed |Added CC||ypoissa...@videotron.ca --- Comment #1 from Yves Poissant --- Created attachment 185055 --> https://bugs.documentfoundation.org/attachment.cgi?id=185055=edit The Writer document that crashes This is a reproduction of a book of 1200 pages approx. The document is not completed due to the crashing bug. In addition to the crash, there are several issues with formatting the text where there are footnotes. I shall report those issues once the crash is fixed. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153314] 'Sentence case' issue in Writer
https://bugs.documentfoundation.org/show_bug.cgi?id=153314 V Stuart Foote changed: What|Removed |Added CC||vsfo...@libreoffice.org --- Comment #1 from V Stuart Foote --- I can not explain why, but the pasted text: sentence case. tHis IS thE FIRst sENTenCE. thIs iS ThE sEConD seNTEncE. Is not handled as a Paragraph. And the sentences--selectable with a "triple mouse click" extends to the entire Paragraph (as opposed to the "4 mouse click" paragraph selection). But if I type the same sentences, they are correctly selected: word, sentence, paragraph. Likewise applying Sentence case from Format -> Text -> Sentence works. As does the "Cycle case". Version: 7.6.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: d8e6b488ceaff7c88856ebcfcfec14d2d8cd7652 CPU threads: 8; OS: Windows 10.0 Build 19044; 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 153315] New: EDITING - Crash after changing font size in style causing reformatting the document
https://bugs.documentfoundation.org/show_bug.cgi?id=153315 Bug ID: 153315 Summary: EDITING - Crash after changing font size in style causing reformatting the document Product: LibreOffice Version: 7.4.5.1 release Hardware: x86-64 (AMD64) OS: Windows (All) Status: UNCONFIRMED Severity: normal Priority: medium Component: Writer Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: ypoissa...@videotron.ca Description: After I change the "Default Paragraph Style" Font size from 9.5pt to 9.8pt Writer crashes. Steps to Reproduce: 1. Make sure the "Linux LIbertine G" font is installed. 2. Open the attached "JAS - HEA - Linux Libertine.odt" document. 3. In the Paragraph Style explorer, right click "Default Paragraph Style" -> "Modify" -> Font" -> Change "Size" from 9.5 to 9.8, select "OK. After the text is being reformatted for a while, Writer crashes. Actual Results: Expected the whole text being cleanly reformatted. Expected Results: Writer doesn't complete the reformating process and crashes instead. Reproducible: Always User Profile Reset: Yes Additional Info: Version: 7.4.5.1 (x64) / LibreOffice Community Build ID: 9c0871452b3918c1019dde9bfac75448afc4b57f CPU threads: 12; OS: Windows 10.0 Build 22621; UI render: Skia/Raster; VCL: win Locale: fr-CA (en_US); UI: en-US Calc: CL I've been having these crash issues for a while. I just found the easy reproduction steps described above. From my observations, I expect the crash is related to reformatting the footnotes. The crash also happen after resetting the user profile and while running in safe mode. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153272] Writer Macro Find with certain Search Attributes performs Replacement.
https://bugs.documentfoundation.org/show_bug.cgi?id=153272 --- Comment #4 from Don --- (In reply to Commit Notification from comment #3) > Julien Nabet committed a patch related to this issue. > It has been pushed to "master": > > https://git.libreoffice.org/core/commit/ > 2d9570523b16dd157384040642e3c2e0ed05 > > tdf#153272: add some missing properties in SwSearchProperties > > It will be available in 7.6.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. Pardon me if this is not how I should report feedback, but in looking at the committed patch I do not see mention of the hyphenation and orphan/Widow settings listed, is this a separate issue? Or was my comment #2 not submitted in time? Thank you, Don -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 148178] SVG Export from macro in old version of SVG
https://bugs.documentfoundation.org/show_bug.cgi?id=148178 --- Comment #3 from AndyG --- I'm using LibreOffice 7.4.4.2 (x64) on Windows 11 (and sometimes on OpenSUSE Leap 15.4). It is indeed the old version (1.1 instead of 1.2) of SVG when exported from a macro: http://www.w3.org/Graphics/SVG/1.1/DTD/svg11.dtd;> http://www.w3.org/2000/svg; xmlns:xlink="http://www.w3.org/1999/xlink; stroke-width="28.222" stroke-linejoin="round" xml:space="preserve"> The rest of the file is also quite different than when exported manually. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153314] New: 'Sentence case' issue in Writer
https://bugs.documentfoundation.org/show_bug.cgi?id=153314 Bug ID: 153314 Summary: 'Sentence case' issue in Writer Product: LibreOffice Version: 7.3.7.2 release Hardware: All OS: Windows (All) Status: UNCONFIRMED Severity: normal Priority: medium Component: Writer Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: andrew...@hotmail.com Description: 'Sentence case' feature doesn't capitalise after a full stop. It works after a ! or ? Steps to Reproduce: Steps 1. Type "sentence case. tHis IS thE FIRst sENTenCE. thIs iS ThE sEConD seNTEncE." 2. Apply Format/Text/Sentence case from the menu Actual Results: Actual result: "Sentence case. this is the first sentence. this is the second sentence." Expected Results: Expected result: "Sentence case. This is the first sentence. This is the second sentence." Reproducible: Always User Profile Reset: No Additional Info: It works after a ! or ? Type: "sentence case! tHis IS thE FIRst sENTenCE? thIs iS ThE sEConD seNTEncE?" Result: "Sentence case! This is the first sentence? This is the second sentence?" -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 133999] [META] XLSX (OOXML) Form Controls related issues
https://bugs.documentfoundation.org/show_bug.cgi?id=133999 --- Comment #1 from Gabor Kelemen (allotropia) --- Some good example documents for future bug hunting are: attachment 127852 from bug 103048 attachment 127728 from bug 100374 attachment 156990 from bug 129861 attachment 165013 from bug 136397 attachment 173557 from bug 143328 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 104309] Scrollbar or Spin Button form element is lost entirely when saving as xlsx
https://bugs.documentfoundation.org/show_bug.cgi?id=104309 Gabor Kelemen (allotropia) changed: What|Removed |Added See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=14 ||3328 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 143328] FILESAVE: All 3 form controls disappear on reopen in LO, incorrect in MSO
https://bugs.documentfoundation.org/show_bug.cgi?id=143328 Gabor Kelemen (allotropia) changed: What|Removed |Added See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=10 ||4309 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 133999] [META] XLSX (OOXML) Form Controls related issues
https://bugs.documentfoundation.org/show_bug.cgi?id=133999 Bug 133999 depends on bug 103048, which changed state. Bug 103048 Summary: FILEOPEN: XLSX with Form controls doesn't work in LO https://bugs.documentfoundation.org/show_bug.cgi?id=103048 What|Removed |Added Status|NEW |RESOLVED Resolution|--- |DUPLICATE -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 107742] [META] Form control bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=107742 Bug 107742 depends on bug 103048, which changed state. Bug 103048 Summary: FILEOPEN: XLSX with Form controls doesn't work in LO https://bugs.documentfoundation.org/show_bug.cgi?id=103048 What|Removed |Added Status|NEW |RESOLVED Resolution|--- |DUPLICATE -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 103048] FILEOPEN: XLSX with Form controls doesn't work in LO
https://bugs.documentfoundation.org/show_bug.cgi?id=103048 Gabor Kelemen (allotropia) changed: What|Removed |Added Resolution|--- |DUPLICATE Status|NEW |RESOLVED --- Comment #14 from Gabor Kelemen (allotropia) --- Sooo... after some time, a bit of review of issues reported: "No value appears in C14." -> this is the same issue as bug 100374 "In the hidden C10 cell a value should appear, in Excel this is an integer number, in Calc a date." -> also the same as bug 100374 Button texts no longer lose accented characters (comment #5) -> WFM, probably = bug 60673 Linked cell info disappears from the option button (comment #6) -> WFM The $ marks disappeared from linked cell info of the List Box (comment #7) -> yes, but this does not seem to be important. All in all, I don't think there is much point to keep this open in the current form. I can split out individual bugs for still remaining independent issues (which are definitely there, save as xlsx still wrecks this document :) ). *** This bug has been marked as a duplicate of bug 100374 *** -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 100374] FILEOPEN: XLSX - Form imported with wrong setting for a list box
https://bugs.documentfoundation.org/show_bug.cgi?id=100374 Gabor Kelemen (allotropia) changed: What|Removed |Added CC||kelem...@ubuntu.com --- Comment #6 from Gabor Kelemen (allotropia) --- *** Bug 103048 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 133999] [META] XLSX (OOXML) Form Controls related issues
https://bugs.documentfoundation.org/show_bug.cgi?id=133999 Bug 133999 depends on bug 129861, which changed state. Bug 129861 Summary: Drop down menu not working correctly in LibreOffice. https://bugs.documentfoundation.org/show_bug.cgi?id=129861 What|Removed |Added Status|NEW |RESOLVED Resolution|--- |DUPLICATE -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 100374] FILEOPEN: XLSX - Form imported with wrong setting for a list box
https://bugs.documentfoundation.org/show_bug.cgi?id=100374 Gabor Kelemen (allotropia) changed: What|Removed |Added CC||dgbat...@gmail.com --- Comment #5 from Gabor Kelemen (allotropia) --- *** Bug 129861 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 129861] Drop down menu not working correctly in LibreOffice.
https://bugs.documentfoundation.org/show_bug.cgi?id=129861 Gabor Kelemen (allotropia) changed: What|Removed |Added Resolution|--- |DUPLICATE Status|NEW |RESOLVED --- Comment #4 from Gabor Kelemen (allotropia) --- This is the same import problem as bug 100374: the List boxes Properties -> Data -> Contents of the linked cell setting is "The selected entry" but it should be "Position of the selected entry". Manually changing this setting fixes the problem. *** This bug has been marked as a duplicate of bug 100374 *** -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 102495] [META] KDE VCL backend bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=102495 Bug 102495 depends on bug 127215, which changed state. Bug 127215 Summary: If saving a file.with.dots, ".odt" is not appended, so Export to PDF results in file.with.PDF instead of file.with.dots.PDF (KDE or OpenSuse?) https://bugs.documentfoundation.org/show_bug.cgi?id=127215 What|Removed |Added Status|NEEDINFO|RESOLVED Resolution|--- |FIXED -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 127215] If saving a file.with.dots, ".odt" is not appended, so Export to PDF results in file.with.PDF instead of file.with.dots.PDF (KDE or OpenSuse?)
https://bugs.documentfoundation.org/show_bug.cgi?id=127215 gorgonz changed: What|Removed |Added Resolution|--- |FIXED Status|NEEDINFO|RESOLVED --- Comment #15 from gorgonz --- No, is not an issue anymore. Tested with Version: 7.3.6.2 / LibreOffice Community Build ID: 30(Build:2) CPU threads: 12; OS: Linux 5.14; UI render: default; VCL: kf5 (cairo+xcb) Locale: de-DE (de_DE.UTF-8); UI: de-DE Calc: threaded and works as expected. Nice job, well done :-) -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 133999] [META] XLSX (OOXML) Form Controls related issues
https://bugs.documentfoundation.org/show_bug.cgi?id=133999 Bug 133999 depends on bug 142209, which changed state. Bug 142209 Summary: FILE SAVE:CALC: EXCEL compatibility issue for xlsx files containing checkboxes https://bugs.documentfoundation.org/show_bug.cgi?id=142209 What|Removed |Added Status|NEW |RESOLVED Resolution|--- |FIXED -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 142209] FILE SAVE:CALC: EXCEL compatibility issue for xlsx files containing checkboxes
https://bugs.documentfoundation.org/show_bug.cgi?id=142209 Gabor Kelemen (allotropia) changed: What|Removed |Added CC||kelem...@ubuntu.com, ||vmik...@collabora.com Status|NEW |RESOLVED Resolution|--- |FIXED --- Comment #9 from Gabor Kelemen (allotropia) --- Thanks Miklos for fixing this! (Don't worry about the highlighted Cell link on the image, that was lost in 7.3 but got fixed in master) -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 142209] FILE SAVE:CALC: EXCEL compatibility issue for xlsx files containing checkboxes
https://bugs.documentfoundation.org/show_bug.cgi?id=142209 --- Comment #8 from Gabor Kelemen (allotropia) --- Created attachment 185054 --> https://bugs.documentfoundation.org/attachment.cgi?id=185054=edit The example file exported with 7.3 in Excel 2016 This got better in 7.3 with: https://git.libreoffice.org/core/+/94678a7b9c6b7e577c15adacc885e03551bcf17b author Miklos Vajna Wed Jun 30 16:22:42 2021 +0200 committer Miklos Vajna Wed Jun 30 20:33:39 2021 +0200 XLSX export: improve handling of checkbox (form controls) Now the second checkbox is also exported and visible in Excel 2010/13/16. (and became visible in Calc as well recently, see: https://bugs.documentfoundation.org/show_bug.cgi?id=143328#c9) -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 142432] [DOCX] Arc is rendered as Pie, rotation is incorrect
https://bugs.documentfoundation.org/show_bug.cgi?id=142432 --- Comment #11 from Alvaro Segura --- Created attachment 185053 --> https://bugs.documentfoundation.org/attachment.cgi?id=185053=edit Arcs with arrows LO 7.4.5 vs Word The bug is still in LO 7.4.5. This attachment shows arcs with modified start and end angles (I use that often to represent angles, as in the picture) and with an arrow end. Notice the "pie" lines that go to the arc center have an arrow in one of the segments. The "camera" object also appears rotated 90 deg extra in LO, but that is a different issue. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 109527] [META] Spell check dialog bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=109527 Bug 109527 depends on bug 152738, which changed state. Bug 152738 Summary: LO75RC1: Automatic spell-check not underlining misspelled words; dialog doesn't use paragraph's language https://bugs.documentfoundation.org/show_bug.cgi?id=152738 What|Removed |Added Status|ASSIGNED|RESOLVED Resolution|--- |FIXED -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 152738] LO75RC1: Automatic spell-check not underlining misspelled words; dialog doesn't use paragraph's language
https://bugs.documentfoundation.org/show_bug.cgi?id=152738 László Németh changed: What|Removed |Added Status|ASSIGNED|RESOLVED Assignee|nem...@numbertext.org |libreoffice-b...@lists.free ||desktop.org Resolution|--- |FIXED --- Comment #13 from László Németh --- @Martin: many thanks for the bug report! (Unfortunatelly, I wasn't able to reproduce it last year likely because of my old build.) @Stéphane: many thanks for the test document and bibisecting! @Noel: many thanks for the review! @Telesto: many thanks for handling the issue! -- 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 Stéphane Guillou (stragu) changed: What|Removed |Added Depends on||135613 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=135613 [Bug 135613] Shapes can't be moved using arrow keys when they are in a table -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 103100] [META] Writer table bugs
https://bugs.documentfoundation.org/show_bug.cgi?id=103100 Stéphane Guillou (stragu) changed: What|Removed |Added Depends on||135613 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=135613 [Bug 135613] Shapes can't be moved using arrow keys when they are in a table -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 99671] [META] Gallery bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=99671 Stéphane Guillou (stragu) changed: What|Removed |Added Depends on|135613 | Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=135613 [Bug 135613] Shapes can't be moved using arrow keys when they are in a table -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 135613] Shapes can't be moved using arrow keys when they are in a table
https://bugs.documentfoundation.org/show_bug.cgi?id=135613 Stéphane Guillou (stragu) changed: What|Removed |Added Blocks|99671 |108741, 103100 CC||stephane.guillou@libreoffic ||e.org Regression By||Heiko Tietze Summary|Gallery shapes can't be |Shapes can't be moved using |moved using arrow keys when |arrow keys when they are in |they are in a table (since |a table |6.3)| --- Comment #8 from Stéphane Guillou (stragu) --- DM described in Bug 129467 Description an interesting way to restore the functionality: > If you click the shape and hit the left/right > arrow keys does not 'nudge' it. > If you then click in the cell to the right and click back on the shape you > still can't nudge it. > If you now drag the shape below outside the table and drag back to where it > was you still can't nudge it. > But drag it below outside the table and as an extra click in the > aforementioned cell (to the right) and drag it back to where it was and > suddenly it is nudgeable! > Click to the right cell again and back again and it becomes unnudgeable once > more. Regina did some extra testing in Bug 129467 Comment 2. Still reproducible in a recent master build: Version: 7.6.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: 9740331d8bc56a9b6fbe3e4c1b26fb97f6639cc6 CPU threads: 8; OS: Linux 5.15; UI render: default; VCL: gtk3 Locale: en-AU (en_AU.UTF-8); UI: en-US Calc: threaded Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=99671 [Bug 99671] [META] Gallery bugs and enhancements https://bugs.documentfoundation.org/show_bug.cgi?id=103100 [Bug 103100] [META] Writer table 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 135613] Gallery shapes can't be moved using arrow keys when they are in a table (since 6.3)
https://bugs.documentfoundation.org/show_bug.cgi?id=135613 Stéphane Guillou (stragu) changed: What|Removed |Added CC||miscellaneous@paintdrawer.c ||o.uk --- Comment #7 from Stéphane Guillou (stragu) --- *** Bug 129467 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 129467] Shape Nudge (with Arrow Key) Fails
https://bugs.documentfoundation.org/show_bug.cgi?id=129467 Stéphane Guillou (stragu) changed: What|Removed |Added CC||stephane.guillou@libreoffic ||e.org Status|NEW |RESOLVED Resolution|--- |DUPLICATE --- Comment #4 from Stéphane Guillou (stragu) --- Thanks, DM and Regina. I am marking as a duplicate of more recent bug 135613 because this regression was bibisected there already. But I will mention your two comments there. *** This bug has been marked as a duplicate of bug 135613 *** -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 152724] FILESAVE FORMATTING Cell custom Format Code with _- (UI visible space width) is not saved correctly
https://bugs.documentfoundation.org/show_bug.cgi?id=152724 Laurent Balland changed: What|Removed |Added Summary|FILESAVE FORMATTING Cell|FILESAVE FORMATTING Cell |custom Format Code with _- |custom Format Code with _- |(UI visible space width)|(UI visible space width) is |and ? (optional digit space |not saved correctly |placeholder) is not saved | |correctly | --- Comment #12 from Laurent Balland --- (In reply to ady from comment #11) > There are at least 3 codes (and their combinations) that are not saved > correctly in ods. Currently, the custom Format Codes are being saved as > follows: > > ? -> # > 0 -> # > _- -> " " > > > See comment #8 for sum-up. ? is now fixed in master (see bug 118324) 0 was already treated, and any "reasonable" format combining #, ? and 0 should be preserved in ODF in integer and decimal part. _x still needs an ODF extension. I accordingly modified the summary. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153313] find and replace not working for "(" or ")"
https://bugs.documentfoundation.org/show_bug.cgi?id=153313 Buovjaga changed: What|Removed |Added CC||ilmari.lauhakangas@libreoff ||ice.org Status|UNCONFIRMED |NEEDINFO Ever confirmed|0 |1 --- Comment #1 from Buovjaga --- Works for me. Are you sure you don't have "Regular expressions" active? Arch Linux 64-bit, X11 Version: 7.4.5.1 / LibreOffice Community Build ID: 40(Build:1) CPU threads: 8; OS: Linux 6.1; UI render: default; VCL: kf5 (cairo+xcb) Locale: fi-FI (fi_FI.UTF-8); UI: en-US 7.4.5-1 Calc: threaded -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 103537] [META] High contrast mode bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=103537 Bug 103537 depends on bug 152845, which changed state. Bug 152845 Summary: no visible AutoText preview in high contrast mode (Windows) https://bugs.documentfoundation.org/show_bug.cgi?id=152845 What|Removed |Added Status|ASSIGNED|RESOLVED Resolution|--- |FIXED -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 108663] [META] AutoText bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=108663 Bug 108663 depends on bug 152845, which changed state. Bug 152845 Summary: no visible AutoText preview in high contrast mode (Windows) https://bugs.documentfoundation.org/show_bug.cgi?id=152845 What|Removed |Added Status|ASSIGNED|RESOLVED Resolution|--- |FIXED -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 118320] Add support for Windows 10/11 dark mode
https://bugs.documentfoundation.org/show_bug.cgi?id=118320 Bug 118320 depends on bug 148085, which changed state. Bug 148085 Summary: About dialog hyperlinks look bad (invisible / have no contrast) in dark mode on Windows https://bugs.documentfoundation.org/show_bug.cgi?id=148085 What|Removed |Added Status|ASSIGNED|RESOLVED Resolution|--- |FIXED -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 150915] [META] Windows Dark Mode bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=150915 Bug 150915 depends on bug 148085, which changed state. Bug 148085 Summary: About dialog hyperlinks look bad (invisible / have no contrast) in dark mode on Windows https://bugs.documentfoundation.org/show_bug.cgi?id=148085 What|Removed |Added Status|ASSIGNED|RESOLVED Resolution|--- |FIXED -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 103202] [META] About dialog bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=103202 Bug 103202 depends on bug 148085, which changed state. Bug 148085 Summary: About dialog hyperlinks look bad (invisible / have no contrast) in dark mode on Windows https://bugs.documentfoundation.org/show_bug.cgi?id=148085 What|Removed |Added Status|ASSIGNED|RESOLVED Resolution|--- |FIXED -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 103184] [META] UI theming bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=103184 Bug 103184 depends on bug 148085, which changed state. Bug 148085 Summary: About dialog hyperlinks look bad (invisible / have no contrast) in dark mode on Windows https://bugs.documentfoundation.org/show_bug.cgi?id=148085 What|Removed |Added Status|ASSIGNED|RESOLVED Resolution|--- |FIXED -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 137972] Correcting with spell checker context menu places cursor at the left (previously right)
https://bugs.documentfoundation.org/show_bug.cgi?id=137972 --- Comment #13 from Heiko Tietze --- *** Bug 149854 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 149854] Track Changes: replace of the first letter of a word is not consistent; new character at the left or right of deleted one depending on how (STR comment 8)
https://bugs.documentfoundation.org/show_bug.cgi?id=149854 --- Comment #15 from Heiko Tietze --- Better have it together with the still open bug 137972. *** This bug has been marked as a duplicate of bug 137972 *** -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 152997] SVG: circle based upon combination of solid lines + dashes, only renders as solid line
https://bugs.documentfoundation.org/show_bug.cgi?id=152997 raal changed: What|Removed |Added OS|All |Windows (All) Keywords|bibisectRequest |bibisected, bisected CC||armin.le.gr...@me.com Regression By||Armin Le Grand --- Comment #6 from raal --- This seems to have begun at the below commit. Adding Cc: to Armin Le Grand ; Could you possibly take a look at this one? Thanks 7cb578a0cfaf873a5b417879b9bb82cc59ec91ea is the first bad commit commit 7cb578a0cfaf873a5b417879b9bb82cc59ec91ea Author: Norbert Thiebaud Date: Tue Feb 11 12:31:14 2020 -0800 source sha:c3e098483f4db12e9502c6cbc056e3d7498b7b6c https://git.libreoffice.org/core/+/c3e098483f4db12e9502c6cbc056e3d7498b7b6c -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153259] Enhancement Request: Exclude some pages from field "Page Count"
https://bugs.documentfoundation.org/show_bug.cgi?id=153259 Heiko Tietze changed: What|Removed |Added CC|heiko.tietze@documentfounda |libreoffice-ux-advise@lists |tion.org|.freedesktop.org Keywords||needsUXEval --- Comment #6 from Heiko Tietze --- (In reply to ajlittoz from comment #5) > Consequently we could have a new setting in the > manual page break dialog to restart page count. My approach was to exclude page styles from the total count (and ditch the request in bug 71583). Restarting the count makes it somewhat inconsistent and error-prone thinking of moving a page around. But nevertheless worth to discuss, back to UX. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153312] EDITING Data Validation/Vlookup pulldown list won't work unless items alphabetical
https://bugs.documentfoundation.org/show_bug.cgi?id=153312 --- Comment #4 from Paul Kinzelman --- Sorry, thanks for the clear explanation -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153312] EDITING Data Validation/Vlookup pulldown list won't work unless items alphabetical
https://bugs.documentfoundation.org/show_bug.cgi?id=153312 Eike Rathke changed: What|Removed |Added Status|RESOLVED|CLOSED -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153312] EDITING Data Validation/Vlookup pulldown list won't work unless items alphabetical
https://bugs.documentfoundation.org/show_bug.cgi?id=153312 Eike Rathke changed: What|Removed |Added Resolution|--- |NOTABUG Status|UNCONFIRMED |RESOLVED --- Comment #3 from Eike Rathke --- VLOOKUP() without 4th parameter or 4th parameter's argument being not 0 does a range lookup for which the lookup range MUST be sorted ascending. If you want an exact match instead specify 0 as 4th argument, like =IFERROR(VLOOKUP(D4;A5:B8;2;0);" ") See online help https://help.libreoffice.org/7.5/en-GB/text/scalc/01/04060109.html?DbPAR=CALC#bm_id3153152 Btw, I'd not use IFERROR() but IFNA() instead to not suppress other than #N/A errors. Not a bug. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153313] New: find and replace not working for "(" or ")"
https://bugs.documentfoundation.org/show_bug.cgi?id=153313
Bug ID: 153313
Summary: find and replace not working for "(" or ")"
Product: LibreOffice
Version: 7.4.5.1 release
Hardware: x86-64 (AMD64)
OS: Windows (All)
Status: UNCONFIRMED
Severity: normal
Priority: medium
Component: Calc
Assignee: libreoffice-bugs@lists.freedesktop.org
Reporter: pdsbpa...@gmail.com
Description:
"find and replace" in Calc works badly with brackets
Actual Results:
very easy
=if(ab2must be changed in if(cd2...
replace (a produce directly an error in the"search"
replace a > ok
) > error
($ > error
Expected Results:
=if(cd2
Reproducible: Always
User Profile Reset: No
Additional Info:
that perfectly works with 7.3 and older versions, of course.
With the new sheets with 16K columns, impossible to turn back in 7.3 !
--
You are receiving this mail because:
You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153259] Enhancement Request: Exclude some pages from field "Page Count"
https://bugs.documentfoundation.org/show_bug.cgi?id=153259 --- Comment #5 from ajlittoz --- (In reply to Heiko Tietze from comment #3) > Besides introducing a standard approach to not count pages with a certain > style, I wonder if we should also consider bug 71583 "There is no page count > field for different page styles or sections", which requests "page 1 of 10" > for one part of the document and another "page 1 of 10" for a different part. I read the request in bug 71583 but the suggestion of creating a field page-count-for-style does not solve the question for counting pages in chapters or parts, at least for me. My chapters are all laid out with the same page style with "dynamic" header and footer, thanks to fields. A style-page-count field would give me the total number of pages consumed by all chapters. In addition what constitutes a "part" has as many definitions as there are users. The only common criterion is: a part starts with a page break and ends with a page break. Consequently we could have a new setting in the manual page break dialog to restart page count. Related to this, a new field needs to be defined to return the value of the current part page count. We have then three fields: -1- the present Page Count field returning the effective total number of pages (related to document statistics, according to ODF) -2- a field omitting the pages excluding from the count -3- a field for the current "part" defined by the aforementioned setting in the page break dialog -2- covers the request for "This books contains x pages", not counting covers et al. -3- covers the request for chapters However, it is not possible to have "My document is 132 pages long including 14 appendix pages." because there is presently no way to capture a field value into a variable. This could be another enhancement request. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153310] FILEOPEN PPTX: Tabulations are not respected
https://bugs.documentfoundation.org/show_bug.cgi?id=153310 m.a.riosv changed: What|Removed |Added CC||miguelangelrv@libreoffice.o ||rg Ever confirmed|0 |1 Status|UNCONFIRMED |NEW --- Comment #2 from m.a.riosv --- Seems the tab stop in not imported fine. Menu/Tools/Options/LibreOffice Impress - Tab stops. Version: 7.6.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: d8e6b488ceaff7c88856ebcfcfec14d2d8cd7652 CPU threads: 4; OS: Windows 10.0 Build 19045; UI render: Skia/Raster; VCL: win Locale: es-ES (es_ES); UI: en-US Calc: CL threaded Jumbo -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153312] EDITING Data Validation/Vlookup pulldown list won't work unless items alphabetical
https://bugs.documentfoundation.org/show_bug.cgi?id=153312 --- Comment #2 from Paul Kinzelman --- I forgot to mention, when I set up the Data | Validity box, I selected: "Cell range", then Allow empty cells (I did some testing with these as well) Show selection list And I had OFF this one: Sort entries ascending -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153312] EDITING Data Validation/Vlookup pulldown list won't work unless items alphabetical
https://bugs.documentfoundation.org/show_bug.cgi?id=153312 Paul Kinzelman changed: What|Removed |Added CC||p...@kinzelman.com --- Comment #1 from Paul Kinzelman --- Created attachment 185052 --> https://bugs.documentfoundation.org/attachment.cgi?id=185052=edit Simple example file that illustrates the bug -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 143148] Use pragma once instead of include guards (Episode 2: Endgame)
https://bugs.documentfoundation.org/show_bug.cgi?id=143148 --- Comment #76 from Commit Notification --- anfanite396 committed a patch related to this issue. It has been pushed to "master": https://git.libreoffice.org/core/commit/31605a4f46cbe5a231122da9bfb07c859522ec3d tdf#143148 Use pragma once instead of include guards It will be available in 7.6.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 153312] New: EDITING Data Validation/Vlookup pulldown list won't work unless items alphabetical
https://bugs.documentfoundation.org/show_bug.cgi?id=153312 Bug ID: 153312 Summary: EDITING Data Validation/Vlookup pulldown list won't work unless items alphabetical Product: LibreOffice Version: 7.4.4.2 release Hardware: All OS: Windows (All) Status: UNCONFIRMED Severity: normal Priority: medium Component: Calc Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: p...@kinzelman.com Description: I created a simple example of a pulldown list consisting of a vertical list of items. If the items are not in alphabetical order, the pulldown does not work. The pulldown can select an item that's not alphabetical, but the adjacent VLOOKUP function to have that selection put a value in another cell doesn't work. I've attached a simple example to illustrate. A5:A8 - list of pulldown items B5:B8 - list of data I want when I select the corresponding A item D4 is the pulldown to select E4 contains the result of the pulldown data from column B. If you pulldown and select FFF you get Ftoo. If you pulldown and select DDD you get Dtoo. If you pulldown and select BBB you get a blank (probably error) If you pulldown and select AAA you get a blank If I reorder the data in A5:B8 alphabetically, it works, I get the -too data in E4 as expected. Steps to Reproduce: 1.See description 2. 3. Actual Results: See description Expected Results: See description Reproducible: Always User Profile Reset: No Additional Info: Version: 7.4.4.2 (x64) / LibreOffice Community Build ID: 85569322deea74ec9134968a29af2df5663baa21 CPU threads: 12; OS: Windows 10.0 Build 22621; 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 153296] FILESAVE DOCX VML shapetype is not detected as preset shape by Word
https://bugs.documentfoundation.org/show_bug.cgi?id=153296 Regina Henschel changed: What|Removed |Added Assignee|rb.hensc...@t-online.de |libreoffice-b...@lists.free ||desktop.org Status|ASSIGNED|NEW --- Comment #5 from Regina Henschel --- The problem noticed with Fontwork shapes exists the same way for other types of custom shapes too. Only that for other shape types the VML Fallback is usually not used. The patch adds a map with the correct markup for Fontwork shapes. That is not a complete fix. For other types of custom shapes still a not suitable markup is used. I think the basic idea for the "vml-shape-types" file is wrong. It generates the markup from the definitions of preset shapes in OOXML. Instead the markup should be used, that Word generates, when it saves a doc or rtf file to docx in compatibility mode. Minus the 48 types now handled, there are still 154 types that would have to be fixed. Since the VML fallback is not used for other than Fontwork shapes, I think it is not worth the effort. Therefore, I do not set the bug to 'Fixed', but will not work on it any further. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 152997] SVG: circle based upon combination of solid lines + dashes, only renders as solid line
https://bugs.documentfoundation.org/show_bug.cgi?id=152997 raal changed: What|Removed |Added CC||r...@post.cz --- Comment #5 from raal --- It works in Linux, but I see chinese characters in the picture, It's different bug. I can reproduce in windows. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 92056] underline dropdown
https://bugs.documentfoundation.org/show_bug.cgi?id=92056 V Stuart Foote changed: What|Removed |Added Resolution|WORKSFORME |FIXED CC||vsfo...@libreoffice.org --- Comment #17 from V Stuart Foote --- Actually think we can call this FIXED https://gerrit.libreoffice.org/c/core/+/24491/ by Szymon Kłos Additional work for bug 153299 would provide Strikethrough. With some UX decision for doing similar for Overline, or not. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 80271] FILESAVE: Shape not getting preserved in RT file
https://bugs.documentfoundation.org/show_bug.cgi?id=80271 Regina Henschel changed: What|Removed |Added CC||rb.hensc...@t-online.de --- Comment #7 from Regina Henschel --- Still no ellipse in Version: 7.6.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: f1830bff71847a9c17715cff52383956719847fe CPU threads: 8; OS: Windows 10.0 Build 19045; UI render: Skia/Raster; VCL: win Locale: de-DE (en_US); UI: en-US Calc: CL threaded -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153299] Add drop-down menu to "Strikethrough" options
https://bugs.documentfoundation.org/show_bug.cgi?id=153299 --- Comment #5 from V Stuart Foote --- (In reply to Heiko Tietze from comment #3) > I think it's not a big deal to enhance the simple strikethrough to allow > other line styles than single lines. Could be an interesting easy hack. > Hossein, what do you think? See https://gerrit.libreoffice.org/c/core/+/24491/ for the work done to add the droplist (TB, NB, SB) for Underline control, believe similar would be needed for doing a similar Strikethrough control. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 152738] LO75RC1: Automatic spell-check not underlining misspelled words; dialog doesn't use paragraph's language
https://bugs.documentfoundation.org/show_bug.cgi?id=152738 László Németh changed: What|Removed |Added Assignee|libreoffice-b...@lists.free |nem...@numbertext.org |desktop.org | Status|NEW |ASSIGNED -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 152346] 7.5 alpha Windows 32-bit crashes on startup
https://bugs.documentfoundation.org/show_bug.cgi?id=152346 --- Comment #10 from David --- It does get as far as creating a new profile directory. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 152346] 7.5 alpha Windows 32-bit crashes on startup
https://bugs.documentfoundation.org/show_bug.cgi?id=152346 --- Comment #9 from David --- The install works properly. It is when trying to open an application after the install that LibreOffice fails on initialization. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 152346] 7.5 alpha Windows 32-bit crashes on startup
https://bugs.documentfoundation.org/show_bug.cgi?id=152346 --- Comment #8 from David --- I'm using the normal GUI install with default settings. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 146601] Libre Calc does not display cell entries as they are typed
https://bugs.documentfoundation.org/show_bug.cgi?id=146601 Stéphane Guillou (stragu) changed: What|Removed |Added CC||stephane.guillou@libreoffic ||e.org Ever confirmed|0 |1 Status|UNCONFIRMED |NEEDINFO --- Comment #11 from Stéphane Guillou (stragu) --- Michael, can you still see the issue in a more recent version, like 7.4.5? -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 152346] 7.5 alpha Windows 32-bit crashes on startup
https://bugs.documentfoundation.org/show_bug.cgi?id=152346 David changed: What|Removed |Added Status|NEEDINFO|UNCONFIRMED Ever confirmed|1 |0 --- Comment #7 from David --- (In reply to Stéphane Guillou (stragu) from comment #6) > (In reply to David from comment #5) > > I just tried the latest 7.5.0.3_x86 installer on both Windows 7 32 and > > 64-bit machines with any previous profile directory removed and the computer > > rebooted. > > Are you using SI-GUI, or downloading from our pre-releases server > https://dev-builds.libreoffice.org/daily/master/Win-x86@39/, or from the > main website > https://www.libreoffice.org/download/download-libreoffice/?type=win- > x86=7.5.0 ? I originally got the downloads from the daily masters, but the last one I got from https://www.libreoffice.org/donate/dl/win-x86/7.5.0/en-US/LibreOffice_7.5.0.3_Win_x86.msi All previous installs and the profile directories, including development builds, were removed and the computer rebooted before doing the latest install. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153311] ¶ copy-past/search LibreOffice
https://bugs.documentfoundation.org/show_bug.cgi?id=153311 --- Comment #1 from Neolinux --- ¶ copy-past/search LibreOffice I'd like with one text selection, include end text ¶ (is not character). So I could search for example two ¶ ¶ ¶ and than replace with one ¶ ¶ With office (microsoft) is easy, I could copy ¶ with other characters, and than past into the search text. ThankYou for the attention. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153311] New: ¶ copy-past/search LibreOffice
https://bugs.documentfoundation.org/show_bug.cgi?id=153311 Bug ID: 153311 Summary: ¶ copy-past/search LibreOffice Product: LibreOffice Version: 6.4.7.2 release Hardware: Other OS: Linux (All) Status: UNCONFIRMED Severity: enhancement Priority: medium Component: LibreOffice Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: villapal...@yahoo.it Description: ¶ copy-past/search LibreOffice I'd like with one text selection, include end text ¶ (is not character). So I could search for example two ¶ ¶ ¶ and than replace with one ¶ ¶ With office (microsoft) is easy, I could copy ¶ with other characters, and than past into the search text. ThankYou for the attention. Steps to Reproduce: 1.copy ¶ (end text) with normal characters 2.past ¶ with normal characters for search-substitution text Actual Results: 3.now is not possible, it could be a nice improve Expected Results: 2.past ¶ with normal characters for search-substitution text Reproducible: Always User Profile Reset: No Additional Info: is that all with Ubuntu -- You are receiving this mail because: You are the assignee for the bug.
