[Libreoffice-bugs] [Bug 118137] RTL: wrong direction when type numbers with slash
https://bugs.documentfoundation.org/show_bug.cgi?id=118137 radwan hallak changed: What|Removed |Added CC||rdwan.h...@gmail.com --- Comment #1 from radwan hallak --- Created attachment 142694 --> https://bugs.documentfoundation.org/attachment.cgi?id=142694&action=edit screenshot for the correct and wrong direction -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 118137] New: RTL: wrong direction when type numbers with slash
https://bugs.documentfoundation.org/show_bug.cgi?id=118137 Bug ID: 118137 Summary: RTL: wrong direction when type numbers with slash Product: LibreOffice Version: 6.1.0.0.beta1+ Hardware: All OS: Windows (All) Status: UNCONFIRMED Severity: normal Priority: medium Component: LibreOffice Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: rdwan.h...@gmail.com Description: When I type numbers with slash / in Right To Left direction like date, The numbers appears from left to right. This behavior is wrong because we are read the date or any numbers with slash from right to left in Arabic this bug tested in: Version: 5.4.5.1 Build ID: 79c9829dd5d8054ec39a82dc51cd9eff340dbee8 CPU threads: 4; OS: Windows 6.1; UI render: default; Locale: en-US (en_US); Calc: group Version: 6.0.4.2 (x64) Build ID: 9b0d9b32d5dcda91d2f1a96dc04c645c450872bf CPU threads: 4; OS: Windows 6.1; UI render: default; Locale: ar-JO (en_US); Calc: group Version: 6.1.0.0.beta1 (x64) Build ID: 8c76dfe1284e211954c30f219b3a38dcdd82f8a0 CPU threads: 4; OS: Windows 6.1; UI render: default; Locale: ar-SY (en_US); Calc: group Steps to Reproduce: 1.tools - language settings - languages - set locale setting: Arabic ,then ok and restart office 2.press Ctrl+Shift+D OR Right-to-left icon to set RTL direction. 3.type 13/6/2018 or any numbers with slash Actual Results: the numbers appears from left to right Expected Results: numbers must appears from right to left Reproducible: Always User Profile Reset: Yes Additional Info: User-Agent: Mozilla/5.0 (Windows NT 6.1; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/66.0.3359.181 Safari/537.36 -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 117489] The existing formatting isn't replaced consistently when applying a table style
https://bugs.documentfoundation.org/show_bug.cgi?id=117489 --- Comment #6 from Jim Raykowski --- Would the expected result be the same as applying a table style and using Ctrl-M to clear direct formatting? -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 118123] Tango shouldnt be falling back on Colibre
https://bugs.documentfoundation.org/show_bug.cgi?id=118123 --- Comment #4 from andreas_k --- I am pro colibre as global fallback but tango doesnt work without galaxy. So l suggest to define as tango fallback galaxy and for global fallback colibre. Second option would be to merge tango with galaxy than the galaxy fallback is not needed cause galaxy is included in tango.but this will be done ordinary when you would offer tango as extension. As long as tango and galaxy are in core. -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 118136] New: Impress: "Rename slides" usability and better placeholder names
https://bugs.documentfoundation.org/show_bug.cgi?id=118136 Bug ID: 118136 Summary: Impress: "Rename slides" usability and better placeholder names Product: LibreOffice Version: 6.0.4.2 release Hardware: All OS: All Status: UNCONFIRMED Severity: enhancement Priority: medium Component: Impress Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: explore...@gmail.com Description: The "Rename slides" feature in Impress is not quite useful, at least for my own workflow in crafting a presentation. And the rename feature is not easily discovered (the slide names are only seen on hover tooltips of the slide thumbnails and on the "Navigator" side pane). For me I didn't even know they can be renamed until I modified a slide from a corporate template (in place, without duplicating). (And exported it to PDF and realized that the names are used in PDF bookmarks - see bug 118135.) I don't know of any use of such "slide names" other than PDF bookmarks (are they meant for machine-readable identifiers, or are they meant for remarks for humans?), but my impression is that slide title texts are already enough to identify slides without needing other explicit "names" (slide numbers are less useful as the slides my be reused in another presentation and users may print slides out of context). So I think there's a usability issue here. I hope this report can: 1. Tell me or other users about the usefulness for slide names. 2. If the slide name feature is to stay, then give us more intelligent placeholder slide names, other than "Slide 1", "Slide 2", etc. Steps to Reproduce: 1. In LibreOffice Impress, create a new, blank presentation. 2. Make four slides (Press Ctrl-M three times). 3. Edit the titles in the *contents* of four slides so they are "Foo", "Bar", "Baz" and "Baz" respectively. 4. Select the second slide, use "Slides" -> "Rename slides" to name it "Barred". 5. Open "View"->"Navigator" and see the slide names. 6. Go to "View"->"Slide Sorter" and move your mouse cursor over each of the slide thumbnails. Actual Results: The slide names shown in steps 5 and 6 are "Slide 1", "Barred", "Slide 3" and "Slide 4" respectively (name varied on your LibreOffice language). Expected Results: A more intelligent naming should be used on unnamed slides. For example slides with title text box, the title text should be used on the slide names. I.e. "[Foo]", "Barred", "[Baz]", "[Baz]" Or: "Foo", "Barred", "Baz", "Baz" Reproducible: Always User Profile Reset: No Additional Info: I have a rough algorithm in my mind for intelligently picking a (placeholder) slide name, if it can be implemented: 1. If the slide features a title text box, and it's content is not empty, then just use the title text as slide names. 2. Otherwise, if the slide contains a content text box, and if it contains non-empty text, then uses the _first line_ of the content text as slide name, followed by ellipsis if more content follows. 3. If the slide's content box contains only a chart, and is chart has a title, use the chart's title as the slide name. If it doesn't have a title, use "[Chart]" as slide name. 4. Similarly, if the slide's content box contains a table, image, audio or video, use "[Table]", "[Picture]", "[Audio]" or "[Video]" as the name. Do so only if the slide has no other text content boxes (floating text boxes are not considered). 5. If the slide can be determined to be blank, use "[Blank]". 6. If it's none of the above, use the generic "[Unnamed Slide]" as the slide name. And I welcome more suggestions on this. User-Agent: Mozilla/5.0 (Windows NT 6.1; Win64; x64; rv:60.0) Gecko/20100101 Firefox/60.0 -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 116537] Incorrect output of mail merge print with specified record ranges
https://bugs.documentfoundation.org/show_bug.cgi?id=116537 Mike Kaganski changed: What|Removed |Added See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=11 ||4663 -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 118135] New: Impress: Unnamed slides should give meaningful name for PDF Indexes/Bookmarks
https://bugs.documentfoundation.org/show_bug.cgi?id=118135 Bug ID: 118135 Summary: Impress: Unnamed slides should give meaningful name for PDF Indexes/Bookmarks Product: LibreOffice Version: 6.0.4.2 release Hardware: All OS: All Status: UNCONFIRMED Severity: enhancement Priority: medium Component: Impress Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: explore...@gmail.com Description: This is a feature request for usability. The "Slides" -> "Rename slides" feature is seldom used in my workflow in crafting a presentation. For now I don't know the practical uses of such slide names (are they identifiers for scripts/machine codes, or are they meant for remarks for humans?), but one thing does irritate me. When the slides are exported to PDF, these unnamed slides would be given placeholder names like "Slide 1", "Slide 2" etc. (locale-specific), and they would become names for "Indexes"/"Bookmarks" in PDF, despite the slides already having titles that can give a better index during export. An example use case is described in "Steps to Reproduce" below. Steps to Reproduce: 1. In LibreOffice Impress, create a new, blank presentation. 2. Make four slides (Press Ctrl-M three times). 3. Edit the titles in the *contents* of four slides so they are "Foo", "Bar", "Baz" and "Baz" respectively. 4. Select the second slide, use "Slides" -> "Rename slides" to name it "Barred" 5. Export this presentation to PDF 6. Open the PDF in Adobe Reader, Evince or whatever PDF viewer you have. Actual Results: If you show the "Bookmarks" in Adobe Reader, or "Index" in Evince's side pane, you see they are marked "Slide 1", "Barred", "Slide 3" and "Slide 4" respectively (name varied on your LibreOffice language). Expected Results: The "Bookmarks" or "Index" names would be "Foo", "Barred", "Baz", "Baz (2)" respectively (if the bookmark names don't allow collision). Reproducible: Always User Profile Reset: No Additional Info: User-Agent: Mozilla/5.0 (Windows NT 6.1; Win64; x64; rv:60.0) Gecko/20100101 Firefox/60.0 -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 109120] MAILMERGE: Merged documents saved as individual documents - filenames should start from 1 (one), not 0 (zero)
https://bugs.documentfoundation.org/show_bug.cgi?id=109120 Mike Kaganski changed: What|Removed |Added Keywords||easyHack, skillCpp --- Comment #6 from Mike Kaganski --- A code pointer: see construction of sOutPath in IMPL_LINK_NOARG(SwMMResultSaveDialog, SaveOutputHdl_Impl, weld::Button&, void) in sw/source/ui/dbui/mmresultdialogs.cxx. -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 91004] 'Tms Rmn' font should be substituted for Times New Roman or Liberation Serif
https://bugs.documentfoundation.org/show_bug.cgi?id=91004 --- Comment #14 from Felix Miata --- (In reply to Volga from comment #13) > Does macOS and Linux distributions having system-wide solutions to replace > 'Tms Rmn' to other font? I do not find the string 'Tms Rmn' anywhere in /etc/fonts/ in openSUSE 42.3. -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 91004] 'Tms Rmn' font should be substituted for Times New Roman or Liberation Serif
https://bugs.documentfoundation.org/show_bug.cgi?id=91004 --- Comment #13 from Volga --- Does macOS and Linux distributions having system-wide solutions to replace 'Tms Rmn' to other font? If so LibreOffice need to handle them. -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 79826] Impress can not properly open specific PPT (Powerpoint 2007 version?)
https://bugs.documentfoundation.org/show_bug.cgi?id=79826 --- Comment #14 from Volga --- This is succeed. https://view.officeapps.live.com/op/view.aspx?src=http%3A%2F%2Fbugs.documentfoundation.org%2Fattachment.cgi%3Fid%3D100711 -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 108487] FILESAVE ODT: Vertical text alignment changes after saving and reopening when a small change is made
https://bugs.documentfoundation.org/show_bug.cgi?id=108487 --- Comment #3 from QA Administrators --- ** Please read this message in its entirety before responding ** 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 http://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://kiwiirc.com/nextclient/irc.freenode.net/#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 mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 51727] EDITING: Tabstops for tablecontrols don't work
https://bugs.documentfoundation.org/show_bug.cgi?id=51727 --- Comment #15 from QA Administrators --- ** Please read this message in its entirety before responding ** 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 http://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://kiwiirc.com/nextclient/irc.freenode.net/#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 mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 45994] FILESAVE/FILEOPEN: ODF - Frame and image position properties not preserved on roundtrip
https://bugs.documentfoundation.org/show_bug.cgi?id=45994 --- Comment #14 from QA Administrators --- ** Please read this message in its entirety before responding ** 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 http://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://kiwiirc.com/nextclient/irc.freenode.net/#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 mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 55053] FORMATTING: Outline Formatting Spacing Issues
https://bugs.documentfoundation.org/show_bug.cgi?id=55053 --- Comment #16 from QA Administrators --- ** Please read this message in its entirety before responding ** 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 http://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://kiwiirc.com/nextclient/irc.freenode.net/#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 mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 82234] EDITING: Indent size shouldn't effect the tab stop position values
https://bugs.documentfoundation.org/show_bug.cgi?id=82234 --- Comment #10 from QA Administrators --- ** Please read this message in its entirety before responding ** 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 http://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://kiwiirc.com/nextclient/irc.freenode.net/#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 mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 76567] Compatibility problem with an Excel file with scrollbar
https://bugs.documentfoundation.org/show_bug.cgi?id=76567 --- Comment #9 from QA Administrators --- ** Please read this message in its entirety before responding ** 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 http://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://kiwiirc.com/nextclient/irc.freenode.net/#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 mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 47818] EDITING: extending selection after pasting selects from top left
https://bugs.documentfoundation.org/show_bug.cgi?id=47818 --- Comment #8 from QA Administrators --- ** Please read this message in its entirety before responding ** 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 http://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://kiwiirc.com/nextclient/irc.freenode.net/#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 mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 47341] Fade in and out animation of transparent object goes wrong, if hardware acceleration is disabled
https://bugs.documentfoundation.org/show_bug.cgi?id=47341 --- Comment #17 from QA Administrators --- ** Please read this message in its entirety before responding ** 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 http://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://kiwiirc.com/nextclient/irc.freenode.net/#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 mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 95610] Android: TIFF Image in file not visible
https://bugs.documentfoundation.org/show_bug.cgi?id=95610 --- Comment #5 from QA Administrators --- ** Please read this message in its entirety before responding ** 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 http://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://kiwiirc.com/nextclient/irc.freenode.net/#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 mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 76447] MULTIPLE.OPERATIONS() shows wrong results when some internal limit is reached
https://bugs.documentfoundation.org/show_bug.cgi?id=76447 --- Comment #11 from QA Administrators --- ** Please read this message in its entirety before responding ** 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 http://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://kiwiirc.com/nextclient/irc.freenode.net/#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 mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 88568] INSERTING FILE: random line breaks inserted when it is a UNIX file
https://bugs.documentfoundation.org/show_bug.cgi?id=88568 --- Comment #11 from QA Administrators --- ** Please read this message in its entirety before responding ** 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 http://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://kiwiirc.com/nextclient/irc.freenode.net/#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 mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 51613] FILESAVE: Saving Mean Value Lines in XLS/X format not possible
https://bugs.documentfoundation.org/show_bug.cgi?id=51613 --- Comment #12 from QA Administrators --- ** Please read this message in its entirety before responding ** 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 http://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://kiwiirc.com/nextclient/irc.freenode.net/#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 mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 107469] Export to MediaWiki struggles with "fancy" quotes and other characters
https://bugs.documentfoundation.org/show_bug.cgi?id=107469 --- Comment #5 from QA Administrators --- ** Please read this message in its entirety before responding ** 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 http://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://kiwiirc.com/nextclient/irc.freenode.net/#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 mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 43928] EDITING Forms - tabstops in tablecontrols could not be changed
https://bugs.documentfoundation.org/show_bug.cgi?id=43928 --- Comment #16 from QA Administrators --- ** Please read this message in its entirety before responding ** 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 http://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://kiwiirc.com/nextclient/irc.freenode.net/#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 mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 77484] Writer: Tabstopps applied wrong if page margins and frameborder are set.
https://bugs.documentfoundation.org/show_bug.cgi?id=77484 --- Comment #12 from QA Administrators --- ** Please read this message in its entirety before responding ** 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 http://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://kiwiirc.com/nextclient/irc.freenode.net/#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 mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 118070] LibreOffice 6.0.4.2 fails to build with GLM 0.9.9.0: GLM_GTX_bit is an experimental extension
https://bugs.documentfoundation.org/show_bug.cgi?id=118070 Adolfo Jayme changed: What|Removed |Added Whiteboard|target:6.2.0 target:6.1.0.1 |target:6.2.0 target:6.1.0.1 |target:6.0.6 target:6.0.5 |target:6.0.5 -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 118134] New: Impress Honeycomb and Vortex Transition Effect Does Not Work
https://bugs.documentfoundation.org/show_bug.cgi?id=118134 Bug ID: 118134 Summary: Impress Honeycomb and Vortex Transition Effect Does Not Work Product: LibreOffice Version: 6.0.4.2 release Hardware: All OS: Linux (All) Status: UNCONFIRMED Severity: normal Priority: medium Component: Impress Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: rickpr...@live.com Description: Hi I am using an Asus Intel Pentium N3540 2.16ghz quad core laptop running Ubuntu 18.04 LTS and using both the stable version of Libre Office 5.4 whatever the business deployment version is and the latest version is here in China. The computer is running Gnome 3.28.1 and a 64 bit OS. Libreoffice Impress transition effects work but two of the effects do not work properly unlike they do on Windows machines - These are Honeycomb and Vortex transition effects. All the other effects work these two do not. Honeycomb acts as a slide fade from left to right which is not right. Vortex does nothing. Any idea what is wrong and when these bugs will get fixed or what is wrong. Tried playing around with all the stuff in options under view for hardware acceleration / opengl all that stuff it does nothing to change anything. Best Regards, Rick Steps to Reproduce: 1. Open Impress 2. Make a presentation. 3. Try using the Honeycomb or Vortext transition effects they don't work. Actual Results: don't work Expected Results: should work Reproducible: Always User Profile Reset: Yes OpenGL enabled: Yes Additional Info: Version 5.4.7.2 CPU Threads - 4 Ox: Linux 4.15 Ui Render - GL; VCL: gtk2 User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:60.0) Gecko/20100101 Firefox/60.0 -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 99115] SVG Insert: Styles defined globally (with *) aren't handle correctly
https://bugs.documentfoundation.org/show_bug.cgi?id=99115 Xisco Faulí changed: What|Removed |Added CC||thorsten.wagne...@gmail.com --- Comment #11 from Xisco Faulí --- *** Bug 118132 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 118132] Bad rendering of SVG images
https://bugs.documentfoundation.org/show_bug.cgi?id=118132 Xisco Faulí changed: What|Removed |Added CC||xiscofa...@libreoffice.org Status|UNCONFIRMED |RESOLVED Resolution|--- |DUPLICATE --- Comment #6 from Xisco Faulí --- Thanks for reporting the issue. This is a dupe of bug 99115 *** This bug has been marked as a duplicate of bug 99115 *** -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 118133] FILESAVE: DOC: Image is missing if roundtrip is done in headless mode
https://bugs.documentfoundation.org/show_bug.cgi?id=118133 --- Comment #3 from Xisco Faulí --- Created attachment 142693 --> https://bugs.documentfoundation.org/attachment.cgi?id=142693&action=edit Sample 2 Another file affected by the same problem -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 118034] Import of xslx chart has wrong position and wrong precision of trendline equation
https://bugs.documentfoundation.org/show_bug.cgi?id=118034 --- Comment #6 from himajin100...@gmail.com --- I was writing about legend, but for equations, I think I needed to look at aDefaultPos https://opengrok.libreoffice.org/xref/core/chart2/source/view/charttypes/VSeriesPlotter.cxx?r=0c195667#1275 -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 118133] FILESAVE: DOC: Image is missing if roundtrip is done in headless mode
https://bugs.documentfoundation.org/show_bug.cgi?id=118133 Xisco Faulí changed: What|Removed |Added Status|UNCONFIRMED |NEW Ever confirmed|0 |1 Keywords||bibisected, bisected, ||regression CC||vmik...@collabora.co.uk --- Comment #2 from Xisco Faulí --- Regression introduced by: author Miklos Vajna 2018-04-20 16:32:00 +0200 committer Miklos Vajna 2018-04-20 21:04:35 +0200 commit edda1e5fc8113aa4744e32f97c96a3cc311485ca (patch) treeb6da5a4a637a9a3ae3ed9307fe59d6f1df80b197 parent e9c52f55f0cc7155d6883e4d2abf14f1638b03b3 (diff) DOCX import: lazy-read images without external headers So that similar to ODT, images are not loaded on file open, only when the user scrolls there. Bisected with: bibisect-linux64-6.2 Adding Cc: to Miklos Vajna -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 118133] FILESAVE: DOC: Image is missing if roundtrip is done in headless mode
https://bugs.documentfoundation.org/show_bug.cgi?id=118133 Xisco Faulí changed: What|Removed |Added CC||xiscofa...@libreoffice.org --- Comment #1 from Xisco Faulí --- Created attachment 142692 --> https://bugs.documentfoundation.org/attachment.cgi?id=142692&action=edit How the document looks after RT -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 118133] New: FILESAVE: DOC: Image is missing if roundtrip is done in headless mode
https://bugs.documentfoundation.org/show_bug.cgi?id=118133 Bug ID: 118133 Summary: FILESAVE: DOC: Image is missing if roundtrip is done in headless mode Product: LibreOffice Version: 6.2.0.0.alpha0+ Master Hardware: All OS: All Status: UNCONFIRMED Severity: normal Priority: medium Component: Writer Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: xiscofa...@libreoffice.org Created attachment 142691 --> https://bugs.documentfoundation.org/attachment.cgi?id=142691&action=edit sample file Steps to reproduce: 1. Open attached document 2. Save it as .DOC with -headless --convert-to doc 3. Open the output file Observed behaviour: the image 'Proof Points is missing. Reproduced in Version: 6.2.0.0.alpha0+ Build ID: 4c6e11886a9d396bf7be18e9e3209a73c6e303ad CPU threads: 4; OS: Linux 4.13; UI render: default; VCL: gtk3; Locale: ca-ES (ca_ES.UTF-8); Calc: group threaded [Bug found by office-interoperability-tools] -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 116898] Please provide Autofit option also for regular text boxes
https://bugs.documentfoundation.org/show_bug.cgi?id=116898 Regina Henschel changed: What|Removed |Added Ever confirmed|0 |1 Status|UNCONFIRMED |NEW --- Comment #11 from Regina Henschel --- There exists two boolean attributes in file format: 'draw:fit-to-size' and 'style:shrink-to-fit'. They are general graphic-properties and can be applied to any shape. The implementation has been corrected by Michael Stahl (bug 97630), but there exist no UI yet. Two boolean attributes results in four situations: (A)draw:fit-to-size="true" and style:shrink-to-fit="false" is currently called "Fit-to-Frame" in the UI and is available in the UI for legacy rectangles and polygons and curves. (B)draw:fit-to-size="false" and style:shrink-to-fit="true" has no UI and is the default setting for presentation outline shapes. That is what sergio calls "auto fit text". (C)draw:fit-to-size="false" and style:shrink-to-fit="false" is currently the default for shapes other than presentation outline shapes. (D)draw:fit-to-size="true" and style:shrink-to-fit="true" makes no sense. It is rendered same as (A). But the attribute style:shrink-to-fit="true" is kept, so when you disable draw:fit-to-size in the UI, you get situation (B). To bring a graphic text box into situation (B), insert the text box in Impress and apply the presentation style 'Outline1'. Then open then "Text..." dialog and uncheck the checkbox 'Fit to Frame' in case it is checked. You can copy the text box to Draw, it keeps the property. But there exists no way in the UI to reset the text box to the default. It is a valid request to get a UI to manually set the property "style:shrink-to-fit" on and off. -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 118084] "File does not exist" all due it exists, might be a problem with special characters.
https://bugs.documentfoundation.org/show_bug.cgi?id=118084 --- Comment #4 from snackbar...@keemail.me --- Update 3: Documents works in Windows 10 x64, so this problem is limited to Linux or my version, Kubuntu 17.10.1. -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 116898] Please provide Autofit option also for regular text boxes
https://bugs.documentfoundation.org/show_bug.cgi?id=116898 --- Comment #10 from sergio.calleg...@gmail.com --- No, there is no autofit for regular text boxes. Autofit is that feature by which you create a text box and while you write text into it, the font size of the text is progressively reduced, to keep the text fitting in the box. This is what may happen in the layout boxes (those controlled via the master page) and which is ON by default. When autofit is supported by a box where you can enter text, you see it as a tickbox in the context menu (right click) as "Autofit Text" right after the "Text" entry and before the "Fontwork" one. It is different from the Text options: "Fit width to text" (off by default). When ON, makes the text box width grow while you type text in the text box. "Fit height to text" (on by default). When ON, makes the text box height grow while you type text in the text box. The combination "Fit width to text OFF" and "Fit height to text ON" makes the text box work so that as you type the text you type fits the box width while the box grows in height (and is probably what you refer to). Autofit is also different from the Text option "Fit to frame" (off by default). When ON, makes the text always fit the box, by "linear scaling" it, so that the text may look distorted (different scaling on X and Y dimensions). Autofit never distorts the text, since it scales the font size and re-wraps. Autofit is also a strange beast in LibO, for the fact that you seem to have no control on which boxes may get it. For instance the "click to add text" "content" boxes in the "title, content" and "title, 2 content" layouts get the autofit, but the "click to add title" box does not get it. Furthermore, the "click to add text" box in the "title slide" layout does not get it either. -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 115464] UI of export to PNG and JPG misleading for resolution
https://bugs.documentfoundation.org/show_bug.cgi?id=115464 --- Comment #19 from Regina Henschel --- (In reply to Tomaz Vajngerl from comment #17) > I still don't understand why we need to "lock" something. All three > parameters are changeable, they just depend on each other. There exists three situations: Change widht/height length and change DPI => Pixels are calculated Change width/height in pixels and change DPI => width/height length is calculated Change width/height in pixels and change width/height length => DPI is calculated So if the user changes e.g. width/height length, you cannot change DPI or pixels automatically, because there are two situations in which a length change are possible. Locking one of them makes it possible to calculate the other. (In reply to Heiko Tietze from comment #16) > Different units are available right now via dropdown. You cannot offer pixel as length in this context. Because here 'pixel' do not mean a length unit, but reflects the number of color items. Only with the additional information of DPI you get a length from it. That is different from e.g. CSS. -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 118034] Import of xslx chart has wrong position and wrong precision of trendline equation
https://bugs.documentfoundation.org/show_bug.cgi?id=118034 --- Comment #5 from himajin100...@gmail.com --- typo: what I came out => what came out -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 118034] Import of xslx chart has wrong position and wrong precision of trendline equation
https://bugs.documentfoundation.org/show_bug.cgi?id=118034 --- Comment #4 from himajin100...@gmail.com --- Reproduced. Version: 6.2.0.0.alpha0+ (x64) Build ID: 951e7a43e62c22d4c7f7fb18de738d86ab3c2251 CPU threads: 4; OS: Windows 10.0; UI render: default; TinderBox: Win-x86_64@42, Branch:master, Time: 2018-06-04_04:31:29 Locale: ja-JP (ja_JP); Calc: CL https://opengrok.libreoffice.org/xref/core/chart2/source/view/charttypes/VSeriesPlotter.cxx?r=0c195667#1321 1. With which UI should I use to change this property like 2(= ZF_STANDARD + 2)? cf: https://opengrok.libreoffice.org/xref/core/svl/source/numbers/zforlist.cxx?r=8d77bc56#97 2. With which UI should I use to change these property? https://opengrok.libreoffice.org/xref/core/chart2/source/view/main/VLegend.cxx?r=bdf5a7b5#1026 https://opengrok.libreoffice.org/xref/core/chart2/source/view/main/VLegend.cxx?r=bdf5a7b5#1030 if these property are true , and LegendPosition_LINE_END, for example , rOutAvailableSpace will be passed to lcl_calculatePositionAndRemainingSpace as reference and will be changed inside the function. This rOutAvailableSpace will be used to decide where to place plot-area. honestly, this is what I came out of my brain when I was thinking about tdf#115630 3. For these properties, what xml elements or attributes should we use in ODF? -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 118123] Tango shouldnt be falling back on Colibre
https://bugs.documentfoundation.org/show_bug.cgi?id=118123 --- Comment #3 from V Stuart Foote --- Hmmm, not sure I follow your reasoning Andreas? In bug 116696 cmnt 10 you agree the replacement of Galaxy by Colibre offers complete coverage--so Galaxy should go. Admittedly the 3D Tango styling is rather off the design aesthetic of Colibre, but so? As long as there is full icon coverage--what difference does the fall back make? Here it just points out how incomplete Tango by itself is. -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 118123] Tango shouldnt be falling back on Colibre
https://bugs.documentfoundation.org/show_bug.cgi?id=118123 andreas_k changed: What|Removed |Added Status|RESOLVED|NEW Ever confirmed|0 |1 Resolution|DUPLICATE |--- CC||kain...@gmail.com --- Comment #2 from andreas_k --- This bug is definitely no duplicate of bug 11696. Tango MUST fallback to Galaxy otherwise you destroy Tango, cause around 60% of Tango icons come from Galaxy. Tango can't live without Galaxy and Colibre is definitely no usefull fallback for Tango. -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 106228] [META] Icon theme issues
https://bugs.documentfoundation.org/show_bug.cgi?id=106228 Bug 106228 depends on bug 118123, which changed state. Bug 118123 Summary: Tango shouldnt be falling back on Colibre https://bugs.documentfoundation.org/show_bug.cgi?id=118123 What|Removed |Added Status|RESOLVED|NEW Resolution|DUPLICATE |--- -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 115464] UI of export to PNG and JPG misleading for resolution
https://bugs.documentfoundation.org/show_bug.cgi?id=115464 --- Comment #18 from Tomaz Vajngerl --- (In reply to Heiko Tietze from comment #16) > Different units are available right now via dropdown. No... pixels have a different meaning than logical units. We can't mix them together, or at least we need to show the final pixel dimensions (width and height) in the dialog all the time and somewhere near the (for example like Gimp does it when you create a new image). -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 106228] [META] Icon theme issues
https://bugs.documentfoundation.org/show_bug.cgi?id=106228 Bug 106228 depends on bug 118123, which changed state. Bug 118123 Summary: Tango shouldnt be falling back on Colibre https://bugs.documentfoundation.org/show_bug.cgi?id=118123 What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |DUPLICATE -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 118123] Tango shouldnt be falling back on Colibre
https://bugs.documentfoundation.org/show_bug.cgi?id=118123 V Stuart Foote changed: What|Removed |Added Resolution|--- |DUPLICATE Status|UNCONFIRMED |RESOLVED CC||vstuart.fo...@utsa.edu --- Comment #1 from V Stuart Foote --- Sorry Jay, going to push this back over to the original bug 116696 issue where we dropped Galaxy for Colibre--for better or worse. *** This bug has been marked as a duplicate of bug 116696 *** -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 118132] Bad rendering of SVG images
https://bugs.documentfoundation.org/show_bug.cgi?id=118132 --- Comment #5 from Thorsten Wagner --- Created attachment 142690 --> https://bugs.documentfoundation.org/attachment.cgi?id=142690&action=edit Screenshot 4 (LO 6.1 and LO from master, image inserted into drawing) -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 118132] Bad rendering of SVG images
https://bugs.documentfoundation.org/show_bug.cgi?id=118132 --- Comment #4 from Thorsten Wagner --- Created attachment 142689 --> https://bugs.documentfoundation.org/attachment.cgi?id=142689&action=edit Screenshot 3 (LO 6.1 and LO from master, image opened as drawing) -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 118132] Bad rendering of SVG images
https://bugs.documentfoundation.org/show_bug.cgi?id=118132 --- Comment #3 from Thorsten Wagner --- Created attachment 142688 --> https://bugs.documentfoundation.org/attachment.cgi?id=142688&action=edit Screenshot 2 (LO 5.4, image inserted into drawing) -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 118132] Bad rendering of SVG images
https://bugs.documentfoundation.org/show_bug.cgi?id=118132 --- Comment #2 from Thorsten Wagner --- Created attachment 142687 --> https://bugs.documentfoundation.org/attachment.cgi?id=142687&action=edit Screenshot 1 (LO 5.4, image opened as drawing) -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 118132] Bad rendering of SVG images
https://bugs.documentfoundation.org/show_bug.cgi?id=118132 --- Comment #1 from Thorsten Wagner --- Created attachment 142686 --> https://bugs.documentfoundation.org/attachment.cgi?id=142686&action=edit SVG image sample -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 118132] New: Bad rendering of SVG images
https://bugs.documentfoundation.org/show_bug.cgi?id=118132 Bug ID: 118132 Summary: Bad rendering of SVG images Product: LibreOffice Version: 6.2.0.0.alpha0+ Master Hardware: All OS: All Status: UNCONFIRMED Severity: normal Priority: medium Component: Draw Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: thorsten.wagne...@gmail.com Description: Some SVG images are not rendered correctly. A sample created with MatPlotLib is attached to show the issue. Steps to Reproduce: 1. Open attached SVG image as drawing 2. Open new drawing and insert attached SVG image Actual Results: (1) Using LO 5.4 rendering is correct when opening SVG image as drawing. (2) Using LO 5.4 rendering is not corrent when insertig SVG image into an existing drawing. (3) Using LO 6.1 as well as LO from master rendering is neither correct when opening SVG image as drawing nor when inserting SVG image into an existing drawing. Issue exists with GL rendering and with native rendering. Expected Results: Rendering should be correct and the same when opening SVG image as drawing and when inserting SVG image into an existing drawing. Reproducible: Always User Profile Reset: Yes OpenGL enabled: Yes Additional Info: (1) LO 5.4: Version: 5.4.7.2.0+ Build ID: e52e5f310e8ce376f0462d6a6a5fbc1a61a148df CPU threads: 8; OS: Mac OS X 10.11.6; UI render: GL; Locale: de-DE (en.UTF-8); Calc: group (2) LO from master: Version: 6.2.0.0.alpha0+ Build ID: faba9fa5d30290df5f8dd2bc0e97a287f20ef563 CPU threads: 8; OS: Mac OS X 10.11.6; UI render: GL; Locale: de-DE (en.UTF-8); Calc: group threaded User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.11; rv:60.0) Gecko/20100101 Firefox/60.0 -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 115464] UI of export to PNG and JPG misleading for resolution
https://bugs.documentfoundation.org/show_bug.cgi?id=115464 --- Comment #17 from Tomaz Vajngerl --- (In reply to Regina Henschel from comment #13) > I disagree with Tomaz order. I want to export so, that the png has the same > width and height as the original vector graphic object and I want to set the > DPI according the purpose of the export. I do not care in how many pixels > this settings result. I can live with the different order. > Using a "lock"-icon is a good idea to make clear, what can be changed and > what not. That is better than the radio button in a previous mockup. I still don't understand why we need to "lock" something. All three parameters are changeable, they just depend on each other. Changing DPI that changes the logical width or height is essentially a no-op, which causes a lot of confusion now, so why allow it in the first place.. -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 34804] EDITING: Keyboard shortcut for Format-Highlighting does not work
https://bugs.documentfoundation.org/show_bug.cgi?id=34804 --- Comment #19 from John Anderson --- I must say Libre Office is really a good tool and is better as compared to same tools of other brands. Its providing good features and many shortcuts. For more reliable gadgets, tools, and support go to https://netgears.support/netgear-powerline/ -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 111003] Unexpected file reads while closing LibO (for example reading description.xml of all the dictionaries)
https://bugs.documentfoundation.org/show_bug.cgi?id=111003 Telesto changed: What|Removed |Added Ever confirmed|1 |0 Status|NEEDINFO|UNCONFIRMED --- Comment #3 from Telesto --- Happens 1 out of 3 instances Version: 6.2.0.0.alpha0+ Build ID: 51aa57cd8ed46d28262e0d315328231f0fa814f4 CPU threads: 4; OS: Windows 6.3; UI render: default; TinderBox: Win-x86@42, Branch:master, Time: 2018-06-12_05:54:56 Locale: nl-NL (nl_NL); Calc: CL -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 113645] Scrolling using the vertical scroll bar has become more choppy with OpenGL enabled
https://bugs.documentfoundation.org/show_bug.cgi?id=113645 --- Comment #3 from Telesto --- Repro with Version: 6.2.0.0.alpha0+ Build ID: 51aa57cd8ed46d28262e0d315328231f0fa814f4 CPU threads: 4; OS: Windows 6.3; UI render: GL; TinderBox: Win-x86@42, Branch:master, Time: 2018-06-12_05:54:56 Locale: nl-NL (nl_NL); Calc: CL -> Only when using the vertical scroll slider with left click; fine when using the scroll wheel -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 115811] pdfium based ipdf defaults to 96 dpi for image, need an option for higher resolution
https://bugs.documentfoundation.org/show_bug.cgi?id=115811 --- Comment #7 from Jan Holesovsky --- Yep, the dynamic approach would be great :-) - but later, needs some planning... -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 116011] Font badly rendered in presentation mode with OpenGL enabled
https://bugs.documentfoundation.org/show_bug.cgi?id=116011 --- Comment #4 from Telesto --- Created attachment 142685 --> https://bugs.documentfoundation.org/attachment.cgi?id=142685&action=edit Bibisect log Bisected to author Michael Stahl2017-04-24 18:21:50 +0200 committer Michael Stahl2017-04-24 18:38:05 +0200 commit 2eb91035c2f60e9dc476336474d51b23b666bb04 (patch) treebd52efadca5ac629dc0ae9c7526b8cec3beee7b3 parent 83e5014a9339d7d92323517f5615b1c18c860e22 (diff) tdf#107205 vcl: don't always use D2DWriteTextOutRenderer ... because it cannot rotate text. https://cgit.freedesktop.org/libreoffice/core/commit/?id=2eb91035c2f60e9dc476336474d51b23b666bb04 -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 116608] The bold part of Times of New Roman font bold & italic is disappearing at smaller zoom levels (depending on font size)
https://bugs.documentfoundation.org/show_bug.cgi?id=116608 Buovjaga changed: What|Removed |Added Ever confirmed|1 |0 Status|NEEDINFO|UNCONFIRMED -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 116011] Font badly rendered in presentation mode with OpenGL enabled
https://bugs.documentfoundation.org/show_bug.cgi?id=116011 --- Comment #3 from Telesto --- Repro with Version: 6.2.0.0.alpha0+ Build ID: 51aa57cd8ed46d28262e0d315328231f0fa814f4 CPU threads: 4; OS: Windows 6.3; UI render: GL; TinderBox: Win-x86@42, Branch:master, Time: 2018-06-12_05:54:56 Locale: nl-NL (nl_NL); Calc: CL Combined with bug 117966 -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 78091] Calc copy-paste of a cell information to commandline may result to lost of a character
https://bugs.documentfoundation.org/show_bug.cgi?id=78091 raal changed: What|Removed |Added Status|NEW |NEEDINFO CC||r...@post.cz --- Comment #6 from raal --- Version: 6.2.0.0.alpha0+ Build ID: c4c56de1b0e62ec866b519b2b24c5e805f0a86d3 CPU threads: 4; OS: Linux 4.4; UI render: default; VCL: gtk3; (In reply to sirollihamalainen from comment #0) > Created attachment 98188 [details] > Three stages of the bug: beginning, copy-paste and backspace > > If you try to merge two cells in to one, you may encounter little problem: > After pasting the one's data after another's to the command line, the > "cursor" jumps one step too far to the right (and leaves an "empty" space > after pasted data). confirm >However if you use backspace to erase this one, you'll > end up erasing the last character of actual data, even while it seems right > on the command line. not confirm Please retest with actual version. Thank you. -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 116608] The bold part of Times of New Roman font bold & italic is disappearing at smaller zoom levels (depending on font size)
https://bugs.documentfoundation.org/show_bug.cgi?id=116608 --- Comment #11 from Telesto --- (In reply to Xisco Faulí from comment #10) > Hi Telesto, > Could you please try to reproduce it with a master build from > http://dev-builds.libreoffice.org/daily/master/ ? > > I have set the bug's status to 'NEEDINFO'. Please change it back to > 'UNCONFIRMED' if the bug is still present in the master build I still repro this without OpenGL enabled Version: 6.2.0.0.alpha0+ Build ID: 51aa57cd8ed46d28262e0d315328231f0fa814f4 CPU threads: 4; OS: Windows 6.3; UI render: default; TinderBox: Win-x86@42, Branch:master, Time: 2018-06-12_05:54:56 Locale: nl-NL (nl_NL); Calc: CL -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 103007] Show sum of selected entries with AutoFilter
https://bugs.documentfoundation.org/show_bug.cgi?id=103007 raal changed: What|Removed |Added CC||r...@post.cz Status|NEW |RESOLVED Resolution|--- |DUPLICATE --- Comment #6 from raal --- *** This bug has been marked as a duplicate of bug 34873 *** -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 93791] FORMATTING of cells lost when editing content in general input field
https://bugs.documentfoundation.org/show_bug.cgi?id=93791 raal changed: What|Removed |Added Status|NEW |NEEDINFO --- Comment #5 from raal --- Cannot reproduce with Version: 6.2.0.0.alpha0+ Build ID: c4c56de1b0e62ec866b519b2b24c5e805f0a86d3 CPU threads: 4; OS: Linux 4.4; UI render: default; VCL: gtk3; please retest, thank you. -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 116898] Please provide Autofit option also for regular text boxes
https://bugs.documentfoundation.org/show_bug.cgi?id=116898 --- Comment #9 from Buovjaga --- (In reply to sergio.callegari from comment #8) > My issue or enhancement request is that I would like to have the option to > switch autofit also on "regular" (non-layout or master pages controlled) > text boxes. You say "autofit also on", but do you actually mean "autofit also off"? Because autofit is on by default for regular text boxes. -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 107946] Document Scales Up
https://bugs.documentfoundation.org/show_bug.cgi?id=107946 Justin L changed: What|Removed |Added CC||ry...@iname.com --- Comment #5 from Justin L --- *** Bug 117449 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 103494] [META] Textbox bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=103494 Bug 103494 depends on bug 117449, which changed state. Bug 117449 Summary: Text boxes positions and sizes are incorrect https://bugs.documentfoundation.org/show_bug.cgi?id=117449 What|Removed |Added Status|NEW |RESOLVED Resolution|--- |DUPLICATE -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 117449] Text boxes positions and sizes are incorrect
https://bugs.documentfoundation.org/show_bug.cgi?id=117449 Justin L changed: What|Removed |Added Status|NEW |RESOLVED Resolution|--- |DUPLICATE --- Comment #19 from Justin L --- *** This bug has been marked as a duplicate of bug 107946 *** -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 66890] EDITING: Double-clicking fill handle does not fill down the entire range
https://bugs.documentfoundation.org/show_bug.cgi?id=66890 raal changed: What|Removed |Added CC||r...@post.cz --- Comment #7 from raal --- still repro steps from comment 3 Version: 6.2.0.0.alpha0+ Build ID: c4c56de1b0e62ec866b519b2b24c5e805f0a86d3 CPU threads: 4; OS: Linux 4.4; UI render: default; VCL: gtk3; -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 38356] Saving formula in Excel XML format is invalid
https://bugs.documentfoundation.org/show_bug.cgi?id=38356 raal changed: What|Removed |Added CC||r...@post.cz Blocks||113869 --- Comment #8 from raal --- repro LO 6,win7 XML generated by excel: 3 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=113869 [Bug 113869] [META] MS Office XML formats (pre-OOXML) bugs and enhancements -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 113869] [META] MS Office XML formats (pre-OOXML) bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=113869 raal changed: What|Removed |Added Depends on||38356 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=38356 [Bug 38356] Saving formula in Excel XML format is invalid -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 117449] Text boxes positions and sizes are incorrect
https://bugs.documentfoundation.org/show_bug.cgi?id=117449 Justin L changed: What|Removed |Added See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=41 ||542 --- Comment #18 from Justin L --- (In reply to raal from comment #17) > there is a function for that: CalcLineSpace(xx, bEvenIfNoLine) That irrelevant commit is going to haunt me forever. The real story is in bug 41542. Unfortunately for Ryszard, the ODF specs say that LO was SUPPOSED to honour the spacing definition, even though the borders were disabled. (That is also true for .doc*.) Bug 41542 Comment 34 says "For a long time (at least since version 3.6) LibreOffice has reset the padding values to zero when borders were removed, but some older documents may still have padding values despite having no border - and thus may now render differently as the padding is activated." So, I'm afraid that this needs to be chalked up to old bugs in LO, and you will just need to manually fix the documents that need the adjustment to look right. Sorry for the bad news. -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 118020] long unresponsive time
https://bugs.documentfoundation.org/show_bug.cgi?id=118020 --- Comment #2 from mbagb...@gmail.com --- Can I revert back to a previous version? I'm unsure what sort of "improvement" was done with the last update but everything worked fine with the earlier version and I'd prefer to revert to an earlier version than risk losing the words added to the spellchecker to take advantage of the "improvement". Or would I be better off to go back to using Open Office? -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 45758] FORMATTING: Graphical objects change Z-order when closing then opening spreadsheet (possible FILEOPEN problem).
https://bugs.documentfoundation.org/show_bug.cgi?id=45758 raal changed: What|Removed |Added CC||r...@post.cz --- Comment #11 from raal --- Repro Version: 6.2.0.0.alpha0+ Build ID: c4c56de1b0e62ec866b519b2b24c5e805f0a86d3 CPU threads: 4; OS: Linux 4.4; UI render: default; VCL: gtk3; -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 46180] FILEOPEN - LO Base fails to connect to "*.DBF" files but connects OK to "*.dbf"
https://bugs.documentfoundation.org/show_bug.cgi?id=46180 Julien Nabet changed: What|Removed |Added CC||er...@redhat.com --- Comment #13 from Julien Nabet --- This bug concerns dbf but what about the other extensions? I mean how csv/CSV files are managed? Indeed I suppose we encounter the same issues: - open csv/CSV files in Calc or Base - csv/CSV files may be on Windows, Linux, network shares, etc. Eike: I noticed the function lcl_MayBeAscii in https://opengrok.libreoffice.org/xref/core/sc/source/ui/unoobj/scdetect.cxx#154 but it's disabled. Any thoughts or any idea who may help here? -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 72202] FILEOPEN: xlsx chart fails to be correctly imported with LO 4.1.3. Data is not shown.
https://bugs.documentfoundation.org/show_bug.cgi?id=72202 raal changed: What|Removed |Added Status|NEW |NEEDINFO -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 72202] FILEOPEN: xlsx chart fails to be correctly imported with LO 4.1.3. Data is not shown.
https://bugs.documentfoundation.org/show_bug.cgi?id=72202 raal changed: What|Removed |Added CC||r...@post.cz --- Comment #8 from raal --- Created attachment 142684 --> https://bugs.documentfoundation.org/attachment.cgi?id=142684&action=edit printscreen LO 6.2 No repro with Version: 6.2.0.0.alpha0+ Build ID: c4c56de1b0e62ec866b519b2b24c5e805f0a86d3 CPU threads: 4; OS: Linux 4.4; UI render: default; VCL: gtk3; Please retest. -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 118125] Impress reports wrong rotation angle in PPTX
https://bugs.documentfoundation.org/show_bug.cgi?id=118125 Paul Trojahn changed: What|Removed |Added Status|NEEDINFO|RESOLVED Resolution|--- |NOTABUG --- Comment #6 from Paul Trojahn --- That doesn't look like a bug to me. Unlike in PowerPoint, angles in Impress are counterclockwise. -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 117999] CROSS REFERENCE: References to a numbered list with brackets / parentheses shouldn't have brackets / parentheses
https://bugs.documentfoundation.org/show_bug.cgi?id=117999 --- Comment #8 from antoniak.pi...@gmail.com --- (In reply to Xisco Faulí from comment #7) > I guess we can handle this as an enhancement Can I ask what would it work? -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 60469] : Wrong "formulas formating" from excel 2010
https://bugs.documentfoundation.org/show_bug.cgi?id=60469 raal changed: What|Removed |Added CC||r...@post.cz --- Comment #10 from raal --- better, but still reproducible. LO 6.2 , Linux -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 67629] FILEOPEN Particular .xlsx hangs Spreadsheet & pegs a core
https://bugs.documentfoundation.org/show_bug.cgi?id=67629 raal changed: What|Removed |Added CC||r...@post.cz --- Comment #7 from raal --- LO 6.2 - load 100% of cpu, bug still present. -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 91257] Cells show wrong numbers
https://bugs.documentfoundation.org/show_bug.cgi?id=91257 raal changed: What|Removed |Added Status|NEW |NEEDINFO -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 91257] Cells show wrong numbers
https://bugs.documentfoundation.org/show_bug.cgi?id=91257 --- Comment #6 from raal --- Created attachment 142683 --> https://bugs.documentfoundation.org/attachment.cgi?id=142683&action=edit Cell format The cells are formated as strings, so no bug in LO when show the values. Maybe a bug when copy/paste the content. Unfortunately without clear steps to reproduce it, we cannot track down the origin of the problem. Please provide a clearer set of step-by-step instructions on how to reproduce the problem. -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 91298] Standard Filter: Value changes to serial number
https://bugs.documentfoundation.org/show_bug.cgi?id=91298 raal changed: What|Removed |Added CC||r...@post.cz --- Comment #3 from raal --- Reproducible with Version: 6.2.0.0.alpha0+ Build ID: c4c56de1b0e62ec866b519b2b24c5e805f0a86d3 CPU threads: 4; OS: Linux 4.4; UI render: default; VCL: gtk3; -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 86603] CONTEXT MENU: Width is too small
https://bugs.documentfoundation.org/show_bug.cgi?id=86603 V Stuart Foote changed: What|Removed |Added CC||vstuart.fo...@utsa.edu Status|NEW |RESOLVED Resolution|--- |WORKSFORME --- Comment #5 from V Stuart Foote --- Yup, looks fine in 6.2... -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 86349] [META] Context menu bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=86349 Bug 86349 depends on bug 86603, which changed state. Bug 86603 Summary: CONTEXT MENU: Width is too small https://bugs.documentfoundation.org/show_bug.cgi?id=86603 What|Removed |Added Status|NEW |RESOLVED Resolution|--- |WORKSFORME -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 86603] CONTEXT MENU: Width is too small
https://bugs.documentfoundation.org/show_bug.cgi?id=86603 raal changed: What|Removed |Added CC||r...@post.cz --- Comment #4 from raal --- Created attachment 142682 --> https://bugs.documentfoundation.org/attachment.cgi?id=142682&action=edit printscreen LO 6.2 Hi Jay, can we close this bug? -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 45904] move java based api tests to c++
https://bugs.documentfoundation.org/show_bug.cgi?id=45904 --- Comment #125 from Commit Notification --- Jens Carl committed a patch related to this issue. It has been pushed to "master": http://cgit.freedesktop.org/libreoffice/core/commit/?id=939fc7dc50a038edb252a8da941ef4e1c018f2b0 tdf#45904 Move _XCellRangeData Java test to C++ It will be available in 6.2.0. The patch should be included in the daily builds available at http://dev-builds.libreoffice.org/daily/ in the next 24-48 hours. More information about daily builds can be found at: http://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 mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 45904] move java based api tests to c++
https://bugs.documentfoundation.org/show_bug.cgi?id=45904 Commit Notification changed: What|Removed |Added Whiteboard|target:5.2.0 target:5.5.0 |target:5.2.0 target:5.5.0 |target:6.0.0 target:6.1.0 |target:6.0.0 target:6.1.0 ||target:6.2.0 -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 116642] [HELP] Incorrect description of the COUNTIFS function
https://bugs.documentfoundation.org/show_bug.cgi?id=116642 --- Comment #4 from Commit Notification --- Olivier Hallot committed a patch related to this issue. It has been pushed to "libreoffice-6-1": http://cgit.freedesktop.org/libreoffice/help/commit/?id=b574fd22322fd31db2da408729cdd1c402626524&h=libreoffice-6-1 tdf#116642 Fix COUNTIFS page + help makefiles -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 116642] [HELP] Incorrect description of the COUNTIFS function
https://bugs.documentfoundation.org/show_bug.cgi?id=116642 Commit Notification changed: What|Removed |Added Whiteboard|target:6.2.0|target:6.2.0 target:6.1.0.1 -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 117826] Pattern is off (dashes at instead of solid horizontal lines) in Presentation mode with OpenGL
https://bugs.documentfoundation.org/show_bug.cgi?id=117826 Xisco Faulí changed: What|Removed |Added CC||qui...@gmail.com, ||xiscofa...@libreoffice.org --- Comment #11 from Xisco Faulí --- Adding Cc: to Tomaž Vajngerl -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 34804] EDITING: Keyboard shortcut for Format-Highlighting does not work
https://bugs.documentfoundation.org/show_bug.cgi?id=34804 --- Comment #18 from kaueneg...@gmail.com --- Still happening on: Versão: 6.0.4.2 (x64) ID de compilação: 9b0d9b32d5dcda91d2f1a96dc04c645c450872bf Threads da CPU:4; SO:Windows 10.0; Realizador da interface: padrão; Local: pt-BR (pt_BR); Calc: CL -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 117884] Tables in 6.2 Rendered Incorrectly
https://bugs.documentfoundation.org/show_bug.cgi?id=117884 Commit Notification changed: What|Removed |Added Whiteboard|target:6.2.0|target:6.2.0 target:6.1.0.1 -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 117884] Tables in 6.2 Rendered Incorrectly
https://bugs.documentfoundation.org/show_bug.cgi?id=117884 --- Comment #7 from Commit Notification --- Mark Hung committed a patch related to this issue. It has been pushed to "libreoffice-6-1": http://cgit.freedesktop.org/libreoffice/core/commit/?id=5f42787232a5a2ece35d4c018df8a9b7c856919f&h=libreoffice-6-1 tdf#117884: intersect border with paint area of upper frame. It will be available in 6.1.0.1. The patch should be included in the daily builds available at http://dev-builds.libreoffice.org/daily/ in the next 24-48 hours. More information about daily builds can be found at: http://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 mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 114957] [META] Help not installed dialog box bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=114957 Bug 114957 depends on bug 114875, which changed state. Bug 114875 Summary: Don't show "No offline help installed" popup again https://bugs.documentfoundation.org/show_bug.cgi?id=114875 What|Removed |Added Status|ASSIGNED|RESOLVED Resolution|--- |FIXED -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 118128] FILESAVE : Save as CSV : Error ... invalid parameter
https://bugs.documentfoundation.org/show_bug.cgi?id=118128 --- Comment #4 from massimo.s...@ats-bg.it --- Created attachment 142681 --> https://bugs.documentfoundation.org/attachment.cgi?id=142681&action=edit Saveas options : edit settings -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 118128] FILESAVE : Save as CSV : Error ... invalid parameter
https://bugs.documentfoundation.org/show_bug.cgi?id=118128 massimo.s...@ats-bg.it changed: What|Removed |Added Status|NEEDINFO|REOPENED --- Comment #3 from massimo.s...@ats-bg.it --- Also with "edit settings" checked, same error as soon as I click on [Save]. I could have different settings for CSV export, it depends on the last file I converted to CSV. Calc must show the settings before any other operation / check, otherwise the user cannot change them and solve this error. -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 103512] [META] AutoFilter-related bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=103512 Bug 103512 depends on bug 117276, which changed state. Bug 117276 Summary: Autofilter settings being reset in some cases https://bugs.documentfoundation.org/show_bug.cgi?id=117276 What|Removed |Added Status|ASSIGNED|RESOLVED Resolution|--- |FIXED -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
