[Libreoffice-bugs] [Bug 152141] Category's Labels don't work
https://bugs.documentfoundation.org/show_bug.cgi?id=152141 --- Comment #3 from Fabio --- Created attachment 183688 --> https://bugs.documentfoundation.org/attachment.cgi?id=183688=edit I show the problem -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 152092] Libreoffice impress freezes when I try to move slides and I'm forced to quit. 'EDITING'
https://bugs.documentfoundation.org/show_bug.cgi?id=152092 Stéphane Guillou (stragu) changed: What|Removed |Added CC||stephane.guillou@libreoffic ||e.org Ever confirmed|0 |1 Status|UNCONFIRMED |NEEDINFO --- Comment #4 from Stéphane Guillou (stragu) --- I haven't been able to reproduce with: Version: 7.3.6.2 / LibreOffice Community Build ID: c28ca90fd6e1a19e189fc16c05f8f8924961e12e CPU threads: 8; OS: Linux 5.15; UI render: default; VCL: gtk3 Locale: de-DE (en_AU.UTF-8); UI: en-US Calc: threaded Or: Version: 7.5.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: deb7bc82de19ea8e20c767fdf21f9ba4feb5e9f0 CPU threads: 8; OS: Linux 5.15; UI render: default; VCL: gtk3 Locale: en-AU (en_AU.UTF-8); UI: en-US Calc: threaded Could you please try: - Updating to 7.3.7: https://www.libreoffice.org/download/download-libreoffice/ - If that doesn't help, you can try a more recent version, like 7.4 (version 7.3 shoudn't see any more releases) Does this happen with any document in particular? In that case, it would be helpful to share a file as an attachment, to help us test. Thank you! -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 152150] gtk3: Non-modal dialog on top of modal dialog unusable
https://bugs.documentfoundation.org/show_bug.cgi?id=152150 Samuel Mehrbrodt (allotropia) changed: What|Removed |Added See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=14 ||8971 CC||caol...@redhat.com, ||samuel.mehrbrodt@allotropia ||.de -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 152150] New: gtk3: Non-modal dialog on top of modal dialog unusable
https://bugs.documentfoundation.org/show_bug.cgi?id=152150 Bug ID: 152150 Summary: gtk3: Non-modal dialog on top of modal dialog unusable Product: LibreOffice Version: 7.5.0.0 alpha0+ Master Hardware: All OS: All Status: UNCONFIRMED Severity: normal Priority: medium Component: UI Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: samuel.mehrbr...@allotropia.de 1. Open Writer 2. File->Export As->Export as PDF 3. Enable "Universal Accessibility (PDF/UA) 4. Export -> Accessibility Check dialog appears Expected: Any of the buttons in the dialog can be clicked Actual: Buttons not clickable Works with gen, doesn't work with gtk3. Problem since 1409159d6117d49e61fe5369f858239ff259fc1e -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 38933] python add-in cannot return array in calc in-cell function
https://bugs.documentfoundation.org/show_bug.cgi?id=38933 nobu changed: What|Removed |Added Resolution|--- |FIXED Status|NEW |RESOLVED --- Comment #12 from nobu --- Version 7.1.2 or later It has been confirmed that if you write a code that returns the array, you will return the array as expected. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 127593] [META] Python Macro bugs
https://bugs.documentfoundation.org/show_bug.cgi?id=127593 Bug 127593 depends on bug 38933, which changed state. Bug 38933 Summary: python add-in cannot return array in calc in-cell function https://bugs.documentfoundation.org/show_bug.cgi?id=38933 What|Removed |Added Status|NEW |RESOLVED Resolution|--- |FIXED -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 104113] [META] Extension manager dialog bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=104113 Bug 104113 depends on bug 38933, which changed state. Bug 38933 Summary: python add-in cannot return array in calc in-cell function https://bugs.documentfoundation.org/show_bug.cgi?id=38933 What|Removed |Added Status|NEW |RESOLVED Resolution|--- |FIXED -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 152146] HYPERTEXT() does not work with click or doubleclick.
https://bugs.documentfoundation.org/show_bug.cgi?id=152146 Julien Nabet changed: What|Removed |Added Summary|HYPERTEXT() does not work |HYPERTEXT() does not work |with click ot doubleclick. |with click or doubleclick. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 104980] Notebookbar contextual groups: no indication if document modified/to be saved
https://bugs.documentfoundation.org/show_bug.cgi?id=104980 --- Comment #9 from Helmut Leininger --- Still present in LO 7.4.3.2 in other bar configurations, a dot is shown on the diskette icon when the document is modified. This is not the case with notebook bar in Register or Grouped mode -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 149800] Unwanted white border in exported SVG
https://bugs.documentfoundation.org/show_bug.cgi?id=149800 László Németh changed: What|Removed |Added Status|ASSIGNED|RESOLVED Resolution|--- |FIXED Assignee|nem...@numbertext.org |libreoffice-b...@lists.free ||desktop.org --- Comment #4 from László Németh --- @Dolon: many thanks for the detailed bug report! @Buovjaga, Rainer Bielefeld: many thanks for the QA! Commit description: tdf#149800 SVG export: remove extra white line of semi-transparent shape A shape is exported using two svg:paths, first one is for the fill, and the second one is for the line. Semi-transparency of shapes enabled the disabled stroke of the first path, resulting an ~1 pt width extra white line behind the normal line of the shape. It was visible only, if the normal shape line was thinner than 1 pt, or if the normal line was semi-transparent or disabled. The extra line got the same transparency value, as the fill, so its visibility depended on that, too. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 111450] [META] SVG fileSave filter (Draw/Impress)
https://bugs.documentfoundation.org/show_bug.cgi?id=111450 Bug 111450 depends on bug 149800, which changed state. Bug 149800 Summary: Unwanted white border in exported SVG https://bugs.documentfoundation.org/show_bug.cgi?id=149800 What|Removed |Added Status|ASSIGNED|RESOLVED Resolution|--- |FIXED -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 113592] LibreLogo: add fallback localization to fix platform issues
https://bugs.documentfoundation.org/show_bug.cgi?id=113592 --- Comment #6 from Commit Notification --- László Németh committed a patch related to this issue. It has been pushed to "master": https://git.libreoffice.org/core/commit/d687d74a4e3ba70a4e21fcd7db532c3cffc7d4d2 tdf#113592 LibreLogo: update fallback localization It will be available in 7.5.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 113592] LibreLogo: add fallback localization to fix platform issues
https://bugs.documentfoundation.org/show_bug.cgi?id=113592 Commit Notification changed: What|Removed |Added Whiteboard|target:6.0.0 target:5.4.4 |target:6.0.0 target:5.4.4 ||target:7.5.0 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 152138] Internet Options->Email help page is empty on macOS
https://bugs.documentfoundation.org/show_bug.cgi?id=152138 Buovjaga changed: What|Removed |Added Status|UNCONFIRMED |NEW CC||ilmari.lauhakangas@libreoff ||ice.org Ever confirmed|0 |1 --- Comment #3 from Buovjaga --- Set to NEW. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 152108] spell-checking of mixed-language phrases
https://bugs.documentfoundation.org/show_bug.cgi?id=152108 Ulrich Windl changed: What|Removed |Added CC||ulrich.wi...@rz.uni-regensb ||urg.de --- Comment #3 from Ulrich Windl --- (In reply to Stéphane Guillou (stragu) from comment #1) > A similar report is Bug 131487. Indeed; to me it seems that any marking for specific language should override the built-in word-boundaries. So for the example (using pseudo-language)"Firewall-Regeln" there should be two components: "Firewall" Using english language rules) and "-Regeln" (using default (German) language rules); maybe the leading minus in "-Regeln" actually causes the problem. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 152079] Increase coordinate precision and make it uniform
https://bugs.documentfoundation.org/show_bug.cgi?id=152079 --- Comment #4 from Mike Kaganski --- (In reply to Mike Kaganski from comment #1) > the API, which needs incompatible changes. I see how I used bad / incorrect wording. Sorry. It's not "incompatible". It's just a large set of new interfaces/methods, and also large changes (e.g., in filters code) to use those. But that's all doable, and the scale is expected, given the task. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 152131] Dragging document from window header bar to another location copies wrong document version
https://bugs.documentfoundation.org/show_bug.cgi?id=152131 --- Comment #1 from Mike Little --- This test was performed on: Version: 7.4.2.3 / LibreOffice Community Build ID: 382eef1f22670f7f4118c8c2dd222ec7ad009daf CPU threads: 4; OS: Mac OS X 13.0; UI render: default; VCL: osx Locale: en-AU (en_AU.UTF-8); UI: en-US Calc: threaded To reproduce this bug: 1. Create a new text document in LibreOffice Writer. Type "this is the original document" into the document. >>MJL: Done. 2. Save it under the name "Test.odt". >>MJL: Done. 3. Type "And this is an amendment" into the document. >>MJL: Done. 4. Save it under the name "Test001.odt". >>MJL: Done, document saved as Test001.odt as the same path as "Test.odt". 5. Drag the document icon from the title bar of the window to another location (such as the desktop). You will find that the dragged document is "Test.odt" and not "Test001.odt". If you open the dragged file, you will see that it does not contain the words "And this is an amendment". >>MJL: Need to explain “Drag the document icon from the title bar of the >>window” … can you provide screen shot? Which window? The LibreOffice “Start >>centre”, or a MacOS Finder window? I am assuming and testing for a MacOS >>“Finder” window, and dragging the Test001.odt to the desktop… Sorry, I opened the dragged file, and it contained the words “And this is an amendment” >> Conclusion: I was not able to confirm the behaviour. Can you provide screen >> shots of the action: “Drag the document icon from the title bar of the >> window to another location (such as the desktop)”? -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 152079] Increase coordinate precision and make it uniform
https://bugs.documentfoundation.org/show_bug.cgi?id=152079 --- Comment #3 from Mike Kaganski --- (In reply to Eyal Rozenberg from comment #2) > Have developers, or the ESC, considered the possibility of maintaining the > old API via some sort of adaptation layer, allowing for more permissiveness > in the codebase itself? With the adaptation layer always implemented in > terms of the more fluid API? And so that you get the old/stable API by > default, but you can opt-in to the more current one with some preprocessor > define or extra headers? Unless that is unavoidable, I don't think it's reasonable; and we don't see a blocker here yet: it's always easy to introduce a XInterfaceFoo2 over the former XInterfaceFoo, and provide the new methods/properties there, alongside with the old methods. This is how we always solve these problems, and this covers your idea generally. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 152134] assign user macro to Tools menu fails on V7.4.2.3.x64 (Windows11) works on Windows8.1 V4..(same sheet)
https://bugs.documentfoundation.org/show_bug.cgi?id=152134 --- Comment #2 from wzpd...@gmail.com --- Correction, function working on Windows8.1 LO version 6.1.0.3 x64 and not v 4.0. Bug on LO v7.4.2.3 x64 remains. Have since removed LO 7.4 from Windows11 and installed v 6.1.0.3 x64 in its place and the function works normally as it did on Windows8.1 so bug is in LO between these two versions..would like to upgrade to most current version of LO that does not have this bug.. advise? -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 109087] [META] Calc sheet header and footer bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=109087 Bug 109087 depends on bug 145356, which changed state. Bug 145356 Summary: EDITING: Calc doesn't use custom header font settings https://bugs.documentfoundation.org/show_bug.cgi?id=145356 What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |WORKSFORME -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 103182] [META] GTK3-specific bugs
https://bugs.documentfoundation.org/show_bug.cgi?id=103182 Bug 103182 depends on bug 145356, which changed state. Bug 145356 Summary: EDITING: Calc doesn't use custom header font settings https://bugs.documentfoundation.org/show_bug.cgi?id=145356 What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |WORKSFORME -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 145356] EDITING: Calc doesn't use custom header font settings
https://bugs.documentfoundation.org/show_bug.cgi?id=145356 Roman Kuznetsov <79045_79...@mail.ru> changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |WORKSFORME --- Comment #4 from Roman Kuznetsov <79045_79...@mail.ru> --- (In reply to Tom Williams from comment #3) > This is working for me in Calc 7.3.7 on Ubuntu Linux. So, this bug report > can be closed. Thanks. Closed as WFM -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 152138] Internet Options->Email help page is empty on macOS
https://bugs.documentfoundation.org/show_bug.cgi?id=152138 --- Comment #2 from Mike Kaganski --- Thanks for testing! Just one step was missing: 0. Read and comprehend this report. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 151936] Changing text color of form inputfield doesn't work
https://bugs.documentfoundation.org/show_bug.cgi?id=151936 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 151932] GalleryItem ( XGalleryItem ) wipes some of its properties as soon as it is returned from a function.
https://bugs.documentfoundation.org/show_bug.cgi?id=151932 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 151928] Installation Wizard is not maximizable and requires UX improvement
https://bugs.documentfoundation.org/show_bug.cgi?id=151928 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 148454] Crash when I change font size in KDE Plasma 5.22.5
https://bugs.documentfoundation.org/show_bug.cgi?id=148454 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 148454] Crash when I change font size in KDE Plasma 5.22.5
https://bugs.documentfoundation.org/show_bug.cgi?id=148454 --- Comment #3 from QA Administrators --- Dear Samantha, 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 148420] imported scans went white after calling export to pdf
https://bugs.documentfoundation.org/show_bug.cgi?id=148420 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 140533] wrong printout for barcode font i2of5txt
https://bugs.documentfoundation.org/show_bug.cgi?id=140533 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 148420] imported scans went white after calling export to pdf
https://bugs.documentfoundation.org/show_bug.cgi?id=148420 --- Comment #3 from QA Administrators --- Dear Rikkit, 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 140533] wrong printout for barcode font i2of5txt
https://bugs.documentfoundation.org/show_bug.cgi?id=140533 --- Comment #4 from QA Administrators --- Dear Tomasz, 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 137999] Changing motion path's proportion doesn't change file's "modified" status
https://bugs.documentfoundation.org/show_bug.cgi?id=137999 --- Comment #2 from QA Administrators --- Dear Ming Hua, 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 137981] Image inside frame still present after cutting frame (but invisible)
https://bugs.documentfoundation.org/show_bug.cgi?id=137981 --- Comment #6 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 104980] Notebookbar contextual groups: no indication if document modified/to be saved
https://bugs.documentfoundation.org/show_bug.cgi?id=104980 --- Comment #8 from QA Administrators --- Dear Helmut Leininger, 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 145356] EDITING: Calc doesn't use custom header font settings
https://bugs.documentfoundation.org/show_bug.cgi?id=145356 --- Comment #3 from Tom Williams --- This is working for me in Calc 7.3.7 on Ubuntu Linux. So, this bug report can be closed. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 151152] Autofilter checkbox status is wrong when I deselect one item, click OK, then click on the dropdown again (2nd case)
https://bugs.documentfoundation.org/show_bug.cgi?id=151152 Aron Budea changed: What|Removed |Added OS|Linux (All) |All -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 152148] The Polish version: MAKS.K(dane; rząd_K) ≡ LARGE(…; …) and MIN.K()
https://bugs.documentfoundation.org/show_bug.cgi?id=152148 Eike Rathke changed: What|Removed |Added Component|Calc|Localization -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 151152] Autofilter checkbox status is wrong when I deselect one item, click OK, then click on the dropdown again (2nd case)
https://bugs.documentfoundation.org/show_bug.cgi?id=151152 Aron Budea changed: What|Removed |Added See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=15 ||2082 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 152082] Converting .xlsx to .ods does not correctly convert chosen filtering options
https://bugs.documentfoundation.org/show_bug.cgi?id=152082 Aron Budea changed: What|Removed |Added CC||aron.bu...@gmail.com See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=15 ||1152 --- Comment #4 from Aron Budea --- (In reply to Roman Kuznetsov from comment #3) > I bisected this one in win64-7.2 bisect repo and got > > https://git.libreoffice.org/core/commit/ > 3069df790cca2917e5aedd87bac1af65f9605d51 That's a backport from 7.3, let's add the original as well. Also, same commit as identified in bug 151152. https://cgit.freedesktop.org/libreoffice/core/commit/?id=f6b143a57d9bd8f5d7b29febcb4e01ee1eb2ff1d author Balazs Varga 2021-07-02 09:40:32 +0200 committer László Németh2021-07-07 17:44:46 +0200 tdf#142910 sc filter: fix "greater than" or "smaller than" etc -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 151152] Autofilter checkbox status is wrong when I deselect one item, click OK, then click on the dropdown again (2nd case)
https://bugs.documentfoundation.org/show_bug.cgi?id=151152 Aron Budea changed: What|Removed |Added Keywords||bisected CC||aron.bu...@gmail.com --- Comment #3 from Aron Budea --- (In reply to Kevin Suo from comment #1) > The following commit seems related: > > commit f6b143a57d9bd8f5d7b29febcb4e01ee1eb2ff1d Confirmed by checking this and the predecessor commit in the linux-64-7.3 bibisect repo. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 152149] Can't Open "What's New" video to FULLSCREEN
https://bugs.documentfoundation.org/show_bug.cgi?id=152149 rwillem...@gmail.com changed: What|Removed |Added URL||https://www.libreoffice.org ||/discover/new-features/ -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 152149] New: Can't Open "What's New" video to FULLSCREEN
https://bugs.documentfoundation.org/show_bug.cgi?id=152149 Bug ID: 152149 Summary: Can't Open "What's New" video to FULLSCREEN Product: LibreOffice Version: 7.4.2.3 release Hardware: x86-64 (AMD64) OS: Windows (All) Status: UNCONFIRMED Severity: minor Priority: medium Component: LibreOffice Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: rwillem...@gmail.com Description: On Main Page (www.libreoffice.org) --> Discover ---> New Features. On opening the video, the FULLSCREEN button does not work, i.e. clicking the button does not open the video to full screen. Video plays fine but users will not be able to read what the video is saying due to the small size of the video window. Copying the URL for the video and then playing it allows the user to go to full screen. Steps to Reproduce: 1.Open the above listed web page 2. Start running the video 3. click on the Full Screen button Actual Results: Nothing happens Expected Results: Video should go to full screen Reproducible: Always User Profile Reset: No Additional Info: Nothing in help file -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 152144] Font color recent list lost after using background fill
https://bugs.documentfoundation.org/show_bug.cgi?id=152144 --- Comment #3 from m.a.riosv --- I can not get recent list cleared. For both, when used 'Automatic' or 'Not fill', the default value became the last on the recent list. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 152141] Category's Labels don't work
https://bugs.documentfoundation.org/show_bug.cgi?id=152141 --- Comment #2 from m.a.riosv --- Attach it here please, not sending a private email. Make it as simple as you can. Also to mention, a video, it's not of too much help. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 152107] Clicking on a cell shows garbage as the formula
https://bugs.documentfoundation.org/show_bug.cgi?id=152107 --- Comment #5 from LeroyG --- Related question in the ask site: https://ask.libreoffice.org/t/disable-calc-automatically-selecting-a-cell-when-clicking-out-of-another-cell/83939 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 152148] New: The Polish version: MAKS.K(dane; rząd_K) ≡ LARGE(…; …) and MIN.K()
https://bugs.documentfoundation.org/show_bug.cgi?id=152148 Bug ID: 152148 Summary: The Polish version: MAKS.K(dane; rząd_K) ≡ LARGE(…; …) and MIN.K() Product: LibreOffice Version: 3.3.0 release Hardware: All OS: All Status: UNCONFIRMED Severity: normal Priority: medium Component: Calc Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: mand...@o2.pl Description: My review concerns the Polish version: MAKS.K(dane; rząd_K) ≡ LARGE(…; …) and MIN.K() 1. Syntax error – „K” with „rząd_K” ≠ „K” with „MAKS.K”. „K” with „MAKS.K” = K „K” with „rząd_K” = 1, 2, 3... My proposition - rename the function to: MAKS.W() from MAKSymalna Wartość MIN.W() from MINimalna Wartość 2. 2 bugs in feature description MAKS.K() „Zwraca K-tą największą wartość zbioru danych.” 1 – the greatest value is only for K=1, 2 – the dataset has no value. My proposition: „Zwraca wartości ze zbioru danych - od największej (w kolejności określonej przez K).” 3. 2 bugs in feature description MIN.K() My proposition: „Zwraca wartości ze zbioru danych - od najmnieszej (w kolejności określonej przez K).” 4. Unnecessary synonym in the definition „Dane oznaczają zakres komórek zawierających dane.” My proposition: „dane oznaczają zakres komórek zbioru danych.” Steps to Reproduce: 1.It's just an opinion. 2.It's just an opinion. 3.It's just an opinion. Actual Results: It's just an opinion. Expected Results: It's just an opinion. Reproducible: Always User Profile Reset: No Additional Info: It's just an opinion. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 149758] void SwAutoFormat::DelEmptyLine(bool): Assertion `!m_aDelPam.HasMark()' failed.
https://bugs.documentfoundation.org/show_bug.cgi?id=149758 Hossein changed: What|Removed |Added CC||hoss...@libreoffice.org Status|NEW |ASSIGNED Assignee|libreoffice-b...@lists.free |hoss...@libreoffice.org |desktop.org | --- Comment #2 from Hossein --- Reproduced with the latest LO 7.5 dev master: Version: 7.5.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: 1f9b2a7057a519e0ea750875ac439129f1d3df87 CPU threads: 8; OS: Linux 5.15; UI render: default; VCL: x11 Locale: en-US (en_US.UTF-8); UI: en-US Calc: threaded -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 152138] Internet Options->Email help page is empty on macOS
https://bugs.documentfoundation.org/show_bug.cgi?id=152138 --- Comment #1 from Mike Little --- 1. Running MacOS… Version: 7.4.2.3 / LibreOffice Community Build ID: 382eef1f22670f7f4118c8c2dd222ec7ad009daf CPU threads: 4; OS: Mac OS X 13.0; UI render: default; VCL: osx Locale: en-AU (en_AU.UTF-8); UI: en-US Calc: threaded 2. Opened 7.4.2.3-rel, and a Writer application. 3. Created a test Writer document. 4. Choose File>Send>Email document 5. Apple Mail appears, with the test Writer document embedded in the email body. I have not previously choose the email program from the LibreOffice Preferences, LibreOffice>Internet> Mail; this was configured by default. Result: No problems with MacOS. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 152147] Default keyboard shortcut for non-breaking hyphen does not work
https://bugs.documentfoundation.org/show_bug.cgi?id=152147 --- Comment #1 from LeroyG --- For me works well, although Ctrl+Shift+- "is not listed as an option" (in the Shortcut Keys list), so I think that it is not configurable. - What shortcut do you see in menu Insert - Formatting Mark - Insert non-breaking hyphen? The same appear in the "Tooltip" when hovering the mouse pointer over the "Insert non-breaking hyphen" function (menu Tool - Customize - Keyboard tab)? - Do you remember the previous version number in which it worked for you? - What is the "7.4.2-2" within your LibreOffice version information? With me: Version: 7.3.6.2 / LibreOffice Community Build ID: 30(Build:2) CPU threads: 1; OS: Linux 5.14; UI render: default; VCL: gtk3 Locale: es-MX (en_US.UTF-8); UI: en-US Calc: threaded -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 152147] New: Default keyboard shortcut for non-breaking hyphen does not work
https://bugs.documentfoundation.org/show_bug.cgi?id=152147 Bug ID: 152147 Summary: Default keyboard shortcut for non-breaking hyphen does not work Product: LibreOffice Version: 7.4.2.3 release Hardware: All OS: Linux (All) Status: UNCONFIRMED Severity: normal Priority: medium Component: Writer Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: de...@screee.ee Description: As stated by the title, the established keyboard shortcut to insert a non-breaking-hyphen (Ctrl+Shift+Minus) does nothing. This shortcut is mentioned by the 'Home' extended menu in the 'Tabbed' UI, as well as official documentation at https://help.libreoffice.org/latest/en-US/text/shared/guide/space_hyphen.html It cannot be manually assigned either, because it is currently impossible to create keyboard shortcuts using the Minus/Plus keys with most modifier combinations, including Ctrl+Shift. (This probably warrants its own bug report?) If this is intended behavior, then at the very least, all mentions of the shortcut should be removed from the UI and official documentation. Although reinstating the shortcut would be the better option, if at all possible. I do not have the time to install and try to reproduce this in earlier versions of LibreOffice right now, so the version specified is simply the one I currently have installed. Resetting LibreOffice by removing $HOME/.config/libreoffice did not resolve the issue. Steps to Reproduce: a) Press Ctrl+Shift+Minus inside a document b) Open the keyboard shortcuts assignment window Actual Results: a) Nothing happens b) Ctrl+Shift+Minus is not listed as an option Expected Results: a) A non-breaking hyphen is inserted into the document b) Ctrl+Shift+Minus is listed as an option, assigned to non-breaking hyphen by default Reproducible: Always User Profile Reset: Yes Additional Info: Arch Linux, installed via package: extra/libreoffice-fresh Version: 7.4.2.3 / LibreOffice Community Build ID: 40(Build:3) CPU threads: 8; OS: Linux 6.0; UI render: default; VCL: kf5 (cairo+xcb) Locale: en-GB (en_GB.UTF-8); UI: en-US 7.4.2-2 Calc: threaded -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 152146] HYPERTEXT() does not work with click ot doubleclick.
https://bugs.documentfoundation.org/show_bug.cgi?id=152146 --- Comment #1 from MARINA-SODA --- If you use Ctrl+ to open a hyperlink, this problem also occurs when you try to open a link while the next cell is selected, for example. Therefore, I set the link opening method to single click, but even autofill does not work. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 152146] New: HYPERTEXT() does not work with click ot doubleclick.
https://bugs.documentfoundation.org/show_bug.cgi?id=152146 Bug ID: 152146 Summary: HYPERTEXT() does not work with click ot doubleclick. Product: LibreOffice Version: 7.2.3.2 release Hardware: x86-64 (AMD64) OS: Windows (All) Status: UNCONFIRMED Severity: normal Priority: medium Component: Calc Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: m5382607...@gomen-da.com Description: The formula "hypertext()" have many issue. 1.The first time if you wrote the formula is success. 2.The after of over the second time, your hyperlink will not work. If you click or double click, you can't open the link and if you touch these cells, you can't see popup message. ---> Click to open hyperlink "c://.". Steps to Reproduce: 1.There is a list on another sheet. Write a function that creates a link from the contents of that list to a local folder. 2.For example, if you write in A2 of Sheet2, "Autofill" downwards. 3.Click or double click the A cells. Actual Results: You cant open after A2. Expected Results: You can open after A2 too. Reproducible: Always User Profile Reset: Yes Additional Info: Once it happens, the cell will not allow you to open hyperlinks. Similar to this but different. It has nothing to do with cell properties. Occurs in autofill even if it's not wrapped. https://bugs.documentfoundation.org/show_bug.cgi?id=33951 I checked. Version: 7.5.0.0.alpha0+ (x64) / LibreOffice Community Build ID: 5a1f41a0d3aab15c113651f2edc9d4137ae99063 CPU threads: 8; OS: Windows 10.0 Build 19043; UI render: Skia/Raster; VCL: win Locale: ja-JP (ja_JP); UI: ja-JP Calc: CL threaded Version: 7.2.3.2 (x64) / LibreOffice Community Build ID: d166454616c1632304285822f9c83ce2e660fd92 CPU threads: 8; OS: Windows 10.0 Build 19045; UI render: Skia/Raster; VCL: win Locale: ja-JP (ja_JP); UI: ja-JP Calc: threaded -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 92122] UI: Floating panels cannot be docked, if "Show window contents while dragging" is disabled in Windows visual effects
https://bugs.documentfoundation.org/show_bug.cgi?id=92122 Regina Henschel changed: What|Removed |Added CC||rb.hensc...@t-online.de --- Comment #24 from Regina Henschel --- >From the help: "Docking toolbars and windows by drag-and-drop depends on your system's window manager settings. You must enable your system to show the full window contents when you move a window, instead of showing just the outer frame." It would be an enhancement to enable LibreOffice to drag-and-drop windows if the system is set to show only the outer frame. The problem is, that windows are really system windows, not something which LibreOffice has made itself. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 139772] FILEOPEN PDF: Importing results in poor import quality on some pdf files (testfile included)
https://bugs.documentfoundation.org/show_bug.cgi?id=139772 V Stuart Foote changed: What|Removed |Added CC||ashodnakash...@yahoo.com, ||qui...@gmail.com, ||vsfo...@libreoffice.org --- Comment #6 from V Stuart Foote --- Hmm, I set the new project provided os/DE environment variable PDFIMPORT_RESOLUTION_DPI = 300 (or higher) But seems like the pdfimport filter still uses the default 96dpi for PDFs like this composed of raster image pages, and the pixilation noted occurs. But if I "insert as image" with the pdfium filter, the first page of the PDF gets rendered to canvas with good quality at the page scale. @Tomaž, @Ashod shouldn't the environment variable also be affecting the pdfimport filters? Or am I missing something... =-ref-= https://gerrit.libreoffice.org/c/core/+/113223 https://gerrit.libreoffice.org/c/core/+/121087 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 92122] UI: Floating panels cannot be docked, if "Show window contents while dragging" is disabled in Windows visual effects
https://bugs.documentfoundation.org/show_bug.cgi?id=92122 --- Comment #23 from V Stuart Foote --- Yes this remains an issue on Windows builds. And seemingly other os/DE On Windows 10, as admin from CLI the "SystemPropertiesPerformance.exe" 'Performance Options' dialog, unchecking the Visual Effects tab 'Show window contents while dragging' checkbox will no longer expose the docking target rectangle as the mouse cursor passes over the target. Checking it enabled restores the drag target. Version: 7.4.2.3 (x64) / LibreOffice Community Build ID: 382eef1f22670f7f4118c8c2dd222ec7ad009daf CPU threads: 8; OS: Windows 10.0 Build 19044; UI render: Skia/Raster; VCL: win Locale: en-US (en_US); UI: en-US Calc: threaded or a current master against 7.5.0 Version: 7.5.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: bcf09f9a9bde21aac1302cbead2b23822458 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 152144] Font color recent list lost after using background fill
https://bugs.documentfoundation.org/show_bug.cgi?id=152144 --- Comment #2 from Jonny Grant --- Hi miguel, Interestingly the "Recent" list seems to get cleared when changing a cell to "no fill" unfortunatly too. -- 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 Hossein changed: What|Removed |Added Depends on||152145 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=152145 [Bug 152145] Placeholder text for the content control fields should be exported to the output -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 152145] Placeholder text for the content control fields should be exported to the output
https://bugs.documentfoundation.org/show_bug.cgi?id=152145 Hossein changed: What|Removed |Added CC||vmik...@collabora.com Blocks||107742 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=107742 [Bug 107742] [META] Form control bugs and enhancements -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 152145] New: Placeholder text for the content control fields should be exported to the output
https://bugs.documentfoundation.org/show_bug.cgi?id=152145 Bug ID: 152145 Summary: Placeholder text for the content control fields should be exported to the output Product: LibreOffice Version: 7.5.0.0 alpha0+ Master Hardware: All OS: All Status: UNCONFIRMED Severity: normal Priority: medium Component: Writer Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: hoss...@libreoffice.org Description: When exporting/printing a file containing content control fields, the placeholder text for the fields (those without any selection/editing) should be exported to the output. Steps to Reproduce: 1. Open attachment 182846 2. Export the document to PDF Actual Results: The placeholder text on page 1 and elsewhere is not exported to PDF. Expected Results: The placeholder text should be exported to PDF. Compare page 1 from PDF output from MS Word (attachment 183511) with the PDF output from LibreOffice 7.5 dev master (attachment 183512). Reproducible: Always User Profile Reset: No Additional Info: Version: 7.5.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: 1f9b2a7057a519e0ea750875ac439129f1d3df87 CPU threads: 8; OS: Linux 5.15; UI render: default; VCL: x11 Locale: en-US (en_US.UTF-8); UI: en-US Calc: threaded -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 102914] Synthetic italic in fonts with partial coverage exported as regular in PDF
https://bugs.documentfoundation.org/show_bug.cgi?id=102914 خالد حسني changed: What|Removed |Added OS|Linux (All) |All -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 86211] PDF Import: clipping is not implemented
https://bugs.documentfoundation.org/show_bug.cgi?id=86211 V Stuart Foote changed: What|Removed |Added See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=14 ||8526 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 99746] [META] PDF import filter in Draw
https://bugs.documentfoundation.org/show_bug.cgi?id=99746 V Stuart Foote changed: What|Removed |Added Depends on||148526 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=148526 [Bug 148526] LibreOffice Draw PDF file displayed incorrectly, visual elements blocked by unmasked radial gradient -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 82262] Incorrect PDF import into Draw showing layers that should be masked
https://bugs.documentfoundation.org/show_bug.cgi?id=82262 V Stuart Foote changed: What|Removed |Added See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=14 ||8526 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 148526] LibreOffice Draw PDF file displayed incorrectly, visual elements blocked by unmasked radial gradient
https://bugs.documentfoundation.org/show_bug.cgi?id=148526 V Stuart Foote changed: What|Removed |Added Summary|LibreOffice Draw | PDF file |LibreOffice Draw PDF file |displayed incorrectly | |displayed incorrectly, |Visual elements missing |visual elements blocked by ||unmasked radial gradient See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=82 ||262, ||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=86 ||211 Blocks||99746 CC||vsfo...@libreoffice.org --- Comment #5 from V Stuart Foote --- Remains valid, but this is a masking and clipping issue. The superfluous radial gradients are fully hidden when using the Insert as image pdfium import filter. And, they can be selected and removed from the Draw canvas otherwise. Version: 7.4.2.3 (x64) / LibreOffice Community Build ID: 382eef1f22670f7f4118c8c2dd222ec7ad009daf CPU threads: 8; OS: Windows 10.0 Build 19044; UI render: Skia/Raster; VCL: win Locale: en-US (en_US); UI: en-US Calc: threaded Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=99746 [Bug 99746] [META] PDF import filter in Draw -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 152079] Increase coordinate precision and make it uniform
https://bugs.documentfoundation.org/show_bug.cgi?id=152079 --- Comment #2 from Eyal Rozenberg --- (In reply to Mike Kaganski from comment #1) > There is an option of adopting EMUs (1/36000 mm), which allows for perfect > integral representation of both tiny fractions of millimeters and inches. > Using integers as much as possible avoids rounding errors. Sounds reasonable to me, I didn't mean to suggest an exclusive list of options. > The problem is not only the file format, but also the API, which needs > incompatible changes. Ah. I remember facing very staunch pushback about the "existing API" in the face of potential changes (bug 150537). That is a separate and more fundamental discussion than coordinate precision... but I'll just ask: Have developers, or the ESC, considered the possibility of maintaining the old API via some sort of adaptation layer, allowing for more permissiveness in the codebase itself? With the adaptation layer always implemented in terms of the more fluid API? And so that you get the old/stable API by default, but you can opt-in to the more current one with some preprocessor define or extra headers? -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 152143] Provide a mechanism to export PDF to text
https://bugs.documentfoundation.org/show_bug.cgi?id=152143 --- Comment #3 from V Stuart Foote --- Nope. That in effect is asking for LibreOffice to become a utility for parsing content of PDF. We are not a PDF editor, nor do we provide utilities to manipulate PDF. We deal in ODF and in external formats via appropriate filters--import and export. There is no ODF or project requirement to convert PDF to external text formats. There is a requirement as for bug 32249 to fully filter parse PDF structure into useable text runs/sentences/paragraphs. If you have a requirement--construct it within that context and it would be valid. Anything else is OUT OF SCOPE. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 112703] [META] ODF (XML) bug tracker
https://bugs.documentfoundation.org/show_bug.cgi?id=112703 Eyal Rozenberg changed: What|Removed |Added Depends on||152079 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=152079 [Bug 152079] Increase coordinate precision and make it uniform -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 152079] Increase coordinate precision and make it uniform
https://bugs.documentfoundation.org/show_bug.cgi?id=152079 Eyal Rozenberg changed: What|Removed |Added Blocks||112703 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=112703 [Bug 112703] [META] ODF (XML) bug tracker -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 152143] Provide a mechanism to export PDF to text
https://bugs.documentfoundation.org/show_bug.cgi?id=152143 Hossein changed: What|Removed |Added Component|Writer |Draw --- Comment #2 from Hossein --- I don't think this is a duplicate of tdf#32249. The title of that one is: Bug 32249 "When importing PDF with text in it , it will be better to have a easy and fluent option to edit the imported Text". So, the above issue is basically talking about being able to edit the text. I am here talking about being able to export the PDF as a text file. These are obviously different, even if you discuss about the commonalities in the implementation. > So you can already select and consolidate entire pages of imported draw shape > textboxes (by glyph index lookup in a ToUinicode CMAP) into a single draw > shape textbox--a sentence or paragraph of text. And then select that text, > copy it and paste it as needed. Then correct as lexically necessary. I disagree. This is not what was intended in this feature request. I have specifically requested means of exporting the whole PDF document as a text file, both via UI and command line. The above consolidation feature might help internally when you want to implement such a feature, but that is not what I have asked for. > Also, because PDF provides no lexical sense to the runs in a document (it is > a > published presentation format)--the discrete imported draw shape text boxes > *must be selected in sequence* for a manual merge. That would remain the case > working with draw shape textboxes on the Writer canvas and is a limitation of > the published rendering encoded into PDF. I disagree again. We have text boxes in LibreOffice, MS Office and elsewhere, but we can export the contents to text files. I haven't requested for a smart software that can understand the meaning of the document. The goal is to export the contents to a text file. > Doing more efficient and high fidelity text extraction from PDF into ODF > paragraphs is the end goal of bug 32249. > > Export of lexically correct word, sentence or paragraph to other document > formats then becomes routine export filtering that is already present. Even by accepting this implementation path, it can be said that this feature request is depending on tdf#32249, not a duplicate of it. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 149104] Fails to paste images into Writer
https://bugs.documentfoundation.org/show_bug.cgi?id=149104 Dieter changed: What|Removed |Added Status|NEEDINFO|RESOLVED Resolution|--- |WORKSFORME --- Comment #6 from Dieter --- So let's close as RESOLVED WORKSFORME. Feel free to change it back to UNCONFIRMED, if it happens again. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 113122] [META] PDF bugs and enhancement
https://bugs.documentfoundation.org/show_bug.cgi?id=113122 Bug 113122 depends on bug 144104, which changed state. Bug 144104 Summary: pdf import into draw and export causes formatting issues https://bugs.documentfoundation.org/show_bug.cgi?id=144104 What|Removed |Added Status|NEW |RESOLVED Resolution|--- |INVALID -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 113122] [META] PDF bugs and enhancement
https://bugs.documentfoundation.org/show_bug.cgi?id=113122 V Stuart Foote changed: What|Removed |Added Depends on||144104 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=144104 [Bug 144104] pdf import into draw and export causes formatting issues -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 144104] pdf import into draw and export causes formatting issues
https://bugs.documentfoundation.org/show_bug.cgi?id=144104 V Stuart Foote changed: What|Removed |Added Resolution|--- |INVALID Blocks||113122 Status|NEW |RESOLVED CC||vsfo...@libreoffice.org --- Comment #6 from V Stuart Foote --- Confirmed LibreOffice makes no claim that Round trip-- PDF import filter, PDF export filter --will produce even remotely similar documents. LibreOffice is not a PDF editor (open the PDF and write changes directly into it). Rather, we read in a PDF stream, we write out a PDF stream within limitations of the filters and document formats available. There are specific issues with the filters, and those should be addressed with specific BZ issues for each (both the import filter, and the export). *This* issue is not-actionable. IMHO => INVALID Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=113122 [Bug 113122] [META] PDF bugs and enhancement -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 113123] [META] PDF import filter in Writer
https://bugs.documentfoundation.org/show_bug.cgi?id=113123 V Stuart Foote changed: What|Removed |Added Depends on||151598 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=151598 [Bug 151598] Implement "Consolidate Text" functionality for text boxes in Writer -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 151598] Implement "Consolidate Text" functionality for text boxes in Writer
https://bugs.documentfoundation.org/show_bug.cgi?id=151598 V Stuart Foote changed: What|Removed |Added Blocks||113123 --- Comment #6 from V Stuart Foote --- IMHO this would be a useful tool for folks with workflows directly filter importing PDF to Write document canvas. Ability to consolidate the draw shape textboxes there is a valid requirement, facilitating eventual implementation of bug 32249 At present, workflows to consolidate text extracted from PDF require taking the PDF through import to Draw canvas. Merge it there, and then copy the result for paste to Writer document. If the draw shape textbox objects can be manipulated in the Writer context then providing the feature there is reasonable. Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=113123 [Bug 113123] [META] PDF import filter in Writer -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 99746] [META] PDF import filter in Draw
https://bugs.documentfoundation.org/show_bug.cgi?id=99746 V Stuart Foote changed: What|Removed |Added Depends on||148826 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=148826 [Bug 148826] Automatic Character color for textboxes of imported PDF are not responding to fixed document canvas color set by LibreOffice Dark color theme -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 148826] Automatic Character color for textboxes of imported PDF are not responding to fixed document canvas color set by LibreOffice Dark color theme
https://bugs.documentfoundation.org/show_bug.cgi?id=148826 V Stuart Foote changed: What|Removed |Added Summary|Dark mode makes reading PDF |Automatic Character color |text impossible |for textboxes of imported ||PDF are not responding to ||fixed document canvas color ||set by LibreOffice Dark ||color theme Status|UNCONFIRMED |NEW Blocks||99746, 113123 CC||vsfo...@libreoffice.org Ever confirmed|0 |1 --- Comment #4 from V Stuart Foote --- On initial import (creation of the textboxes) for imported PDF text runs, the 'Automatic' color of characters in the textboxes does not adjust to the fixed color set for document background in Application Colors 'LibreOffice Dark' color theme. As noted, resolves by selecting the textboxes and reapplying the automatic theme, i.e. select, apply a color from picker, reselect Automatic. Windows in DE 'Dark' color theme, with LO Application Colors 'LibreOffice Dark' color theme selected Version: 7.5.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: bcf09f9a9bde21aac1302cbead2b23822458 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 As expected, likewise affects PDF filter import to Writer canvas as well Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=99746 [Bug 99746] [META] PDF import filter in Draw https://bugs.documentfoundation.org/show_bug.cgi?id=113123 [Bug 113123] [META] PDF import filter in Writer -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 113123] [META] PDF import filter in Writer
https://bugs.documentfoundation.org/show_bug.cgi?id=113123 V Stuart Foote changed: What|Removed |Added Depends on||148826 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=148826 [Bug 148826] Automatic Character color for textboxes of imported PDF are not responding to fixed document canvas color set by LibreOffice Dark color theme -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 152142] RTL Text sometimes falls out of the text box
https://bugs.documentfoundation.org/show_bug.cgi?id=152142 Regina Henschel changed: What|Removed |Added Ever confirmed|0 |1 Status|UNCONFIRMED |NEW CC||rb.hensc...@t-online.de --- Comment #2 from Regina Henschel --- I can confirm that the text box inside the custom shape ha wrong position I see that the docx-file has left-to-right text directions in Word. But I see these problems: The odt-file should have set text direction to "right-to-left" in page style, but has not. Several default objects have as writing mode "Page", which means they use the writing mode from the closest object in which they are contained and which itself has not writing mode "Page". If the page has writing mode not explicitly set, then (I guess) it takes the writing mode from application environment. For me that is German with "left-to-right". Has the page style for You a text direction "right-to-left"? The result for me is, that the shape has WritingMode=0" and TextWritingMode="LR_TB" and the paragraph style Frame Content too. When they do not have the correct text direction, you cannot expect, that the export to docx, produces correct text directions in Word. Of cause that does not mean that the export will produce a usable document if they are correct. So please try the complete process generating the documents with explicitly setting text directions, so that it is possible to sort out those problems, which come in because of wrong defaults in text directions. In regard to the position problem, when I change the anchor of the shape from "as character" to "to character", the frame jumps to the correct position. I set it to "New", because there is surely something wrong. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 152144] Font color recent list lost after using background fill
https://bugs.documentfoundation.org/show_bug.cgi?id=152144 m.a.riosv changed: What|Removed |Added CC||miguelangelrv@libreoffice.o ||rg --- Comment #1 from m.a.riosv --- Seems the 'Recent' it's the same for both. Version: 7.4.3.1 (x64) / LibreOffice Community Build ID: 3793858a34d8fef5b92f8fee233f97766f05e281 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 But I don't know if it was designed to be so, or can be a bug. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 151677] tip on "formula bar" for "formula making" is displaying over the formula itself.
https://bugs.documentfoundation.org/show_bug.cgi?id=151677 Rafael Lima changed: What|Removed |Added CC||paj...@gmail.com --- Comment #4 from Rafael Lima --- *** Bug 151995 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 151995] Formula helper overlaps actual formula when top bars are removed
https://bugs.documentfoundation.org/show_bug.cgi?id=151995 Rafael Lima changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |DUPLICATE --- Comment #1 from Rafael Lima --- This is a duplicate of bug 151677. *** This bug has been marked as a duplicate of bug 151677 *** -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 112810] [META] Arabic & Farsi language-specific RTL issues
https://bugs.documentfoundation.org/show_bug.cgi?id=112810 Bug 112810 depends on bug 149457, which changed state. Bug 149457 Summary: Arabic Text Scrambled and Unreadable in PDF Files Opened by LibreOffice Draw https://bugs.documentfoundation.org/show_bug.cgi?id=149457 What|Removed |Added Status|NEW |RESOLVED Resolution|--- |DUPLICATE -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 104597] RTL script text runs are reversed on PDF import, PDFIProcessor::mirrorString misbehaving
https://bugs.documentfoundation.org/show_bug.cgi?id=104597 --- Comment #98 from V Stuart Foote --- *** Bug 149457 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 149457] Arabic Text Scrambled and Unreadable in PDF Files Opened by LibreOffice Draw
https://bugs.documentfoundation.org/show_bug.cgi?id=149457 V Stuart Foote changed: What|Removed |Added Status|NEW |RESOLVED Resolution|--- |DUPLICATE --- Comment #12 from V Stuart Foote --- The primary issue of the reversed text runs is corrected for the 7.4.3 release, with additional work in master against a 7.5 release. Any residual formatting or conversion of extracted RTL text runs should be opened as new issues against 7.4.3 *** This bug has been marked as a duplicate of bug 104597 *** -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 152141] Category's Labels don't work
https://bugs.documentfoundation.org/show_bug.cgi?id=152141 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 --- Could you attach a sample file? -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 104597] RTL script text runs are reversed on PDF import, PDFIProcessor::mirrorString misbehaving
https://bugs.documentfoundation.org/show_bug.cgi?id=104597 V Stuart Foote changed: What|Removed |Added CC||h...@013.net --- Comment #97 from V Stuart Foote --- *** Bug 151950 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 151950] Draw is messing up Hebrew while reading PDF documents
https://bugs.documentfoundation.org/show_bug.cgi?id=151950 V Stuart Foote changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |DUPLICATE CC||vsfo...@libreoffice.org --- Comment #4 from V Stuart Foote --- Rendering reversed text runs on opening of attachment 183473 confirmed corrected in Nightly against 7.4.3 where this is fixed. Version: 7.4.4.0.0+ (x64) / LibreOffice Community Build ID: f7f4b00185318c1f2949ca42316e1a92c57da23b 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 *** This bug has been marked as a duplicate of bug 104597 *** -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 152079] Increase coordinate precision and make it uniform
https://bugs.documentfoundation.org/show_bug.cgi?id=152079 --- Comment #1 from Mike Kaganski --- There is an option of adopting EMUs (1/36000 mm), which allows for perfect integral representation of both tiny fractions of millimeters and inches. Using integers as much as possible avoids rounding errors. The problem is not only the file format, but also the API, which needs incompatible changes. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 47351] Improper kerning of subscripts for italic characters
https://bugs.documentfoundation.org/show_bug.cgi?id=47351 --- Comment #11 from خالد حسني --- Do we have any example of other (office) software that handles this differently? It is not an issue of kerning, rather italic glyphs because of their slant will have more white space at the bottom than at the top. LibreOffice is positioning the scripts using the glyph advance width, which does not compensate for the slant. One way to fix this is to use the glyph bounding rectangle, but this can be very tricky and slow. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 117428] add an option to PDF export dialog to do ActualText per word
https://bugs.documentfoundation.org/show_bug.cgi?id=117428 V Stuart Foote changed: What|Removed |Added See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=15 ||2143 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 151598] Implement "Consolidate Text" functionality for text boxes in Writer
https://bugs.documentfoundation.org/show_bug.cgi?id=151598 V Stuart Foote changed: What|Removed |Added See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=15 ||2143 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 113122] [META] PDF bugs and enhancement
https://bugs.documentfoundation.org/show_bug.cgi?id=113122 Bug 113122 depends on bug 152143, which changed state. Bug 152143 Summary: Provide a mechanism to export PDF to text https://bugs.documentfoundation.org/show_bug.cgi?id=152143 What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |DUPLICATE -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 32249] When importing PDF with text in it , it will be better to have a easy and fluent option to edit the imported Text
https://bugs.documentfoundation.org/show_bug.cgi?id=32249 V Stuart Foote changed: What|Removed |Added CC||hoss...@libreoffice.org --- Comment #32 from V Stuart Foote --- *** Bug 152143 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 152143] Provide a mechanism to export PDF to text
https://bugs.documentfoundation.org/show_bug.cgi?id=152143 V Stuart Foote changed: What|Removed |Added CC||libreoffice-ux-advise@lists ||.freedesktop.org, ||vsfo...@libreoffice.org Status|UNCONFIRMED |RESOLVED See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=15 ||1598, ||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=11 ||7428 Keywords||needsUXEval Resolution|--- |DUPLICATE --- Comment #1 from V Stuart Foote --- (In reply to Hossein from comment #0) > Description: > Currently it is not possible to export PDF files loaded in LibreOffice > (Draw) to text. Not true. Currently LO has the 'Consolidate text' feature see work done for bug 118370 [1]. Which is functional just inconvenient to move PDF imported text to the Writer canvas for filter export. And this is a dupe of bug 32249, or at most of bug 151598 to implement 'Consolidate text' on the Writer canvas. In reasonable workflow, we now take an imported PDF (opened via Draw) to draw vcl canvas. The textboxes representing the text streams read out from PDF structures are discretely placed onto vcl canvas. So you can already select and consolidate entire pages of imported draw shape textboxes (by glyph index lookup in a ToUinicode CMAP) into a single draw shape textbox--a sentence or paragraph of text. And then select that text, copy it and paste it as needed. Then correct as lexically necessary. Also, because PDF provides no lexical sense to the runs in a document (it is a published presentation format)--the discrete imported draw shape text boxes *must be selected in sequence* for a manual merge. That would remain the case working with draw shape textboxes on the Writer canvas and is a limitation of the published rendering encoded into PDF. PDF provides an /ActualText construct that could be used more effectively than index lookup on a Unicode CMAP. For bug 66597 LibreOffice export filter for PDF /ActualText construct already is in place [2] for PDF creation but only to the grapheme cluster run. Bug 117428 is open to refactor PDF export to provide /ActualText at the word bound. What is unclear is how our poppler PDF import filter(s) would need to be refactored to use the lexical details to load draw shape textboxes with /ActualText--for roundtrip, or import of other sourced PDF. Doing more efficient and high fidelity text extraction from PDF into ODF paragraphs is the end goal of bug 32249. Export of lexically correct word, sentence or paragraph to other document formats then becomes routine export filtering that is already present. =-ref-= [1] https://gerrit.libreoffice.org/c/core/+/75043/ [2] https://gerrit.libreoffice.org/c/core/+/53315/ *** This bug has been marked as a duplicate of bug 32249 *** -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 103322] Use floating point for glyph positioning in VCL
https://bugs.documentfoundation.org/show_bug.cgi?id=103322 Luke changed: What|Removed |Added See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=15 ||2079 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 152079] Increase coordinate precision and make it uniform
https://bugs.documentfoundation.org/show_bug.cgi?id=152079 Luke changed: What|Removed |Added See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=10 ||3322 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 94773] FILEOPEN: OOXML - Object fill patterns incorrectly imported as hatching
https://bugs.documentfoundation.org/show_bug.cgi?id=94773 --- Comment #8 from Luke --- Still reproducible in Version: 7.5.0.0.alpha0+ (x86) / LibreOffice Community Build ID: 16a7e944ab1b318fafb7dd48d48379168403d2e8 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 92122] UI: Floating panels cannot be docked, if "Show window contents while dragging" is disabled in Windows visual effects
https://bugs.documentfoundation.org/show_bug.cgi?id=92122 --- Comment #22 from Jérôme --- Always occurs with LibreOffice 7.0 and Windows 10. -- You are receiving this mail because: You are the assignee for the bug.
