[Libreoffice-bugs] [Bug 95372] OOXML sectPr: image is on the wrong side of the section break
https://bugs.documentfoundation.org/show_bug.cgi?id=95372 Aron Budea changed: What|Removed |Added CC||ba...@caesar.elte.hu Hardware|Other |All Keywords||filter:docx Blocks||130447 Version|5.0.3.1 rc |Inherited From OOo --- Comment #10 from Aron Budea --- Still in LO Version: 7.3.0.0.alpha0+ (c97bdca2d7abf30a99c45192b8f49c5bf76ca035) / Ubuntu. It wasn't fine in older versions, either. Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=130447 [Bug 130447] [META] DOCX (OOXML) section-related issues -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 130447] [META] DOCX (OOXML) section-related issues
https://bugs.documentfoundation.org/show_bug.cgi?id=130447 Aron Budea changed: What|Removed |Added Depends on||95372 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=95372 [Bug 95372] OOXML sectPr: image is on the wrong side of the section break -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 95430] Embedded VISIO object is zoomed and can't be zoomed out
https://bugs.documentfoundation.org/show_bug.cgi?id=95430 Aron Budea changed: What|Removed |Added CC||ba...@caesar.elte.hu Hardware|Other |All -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 143986] In slideshow mode, when we go to the next slide, horizontal bands flicker across the screen
https://bugs.documentfoundation.org/show_bug.cgi?id=143986 --- Comment #3 from NarayanAras --- Created attachment 174456 --> https://bugs.documentfoundation.org/attachment.cgi?id=174456=edit Shows the band that flickers across the screen -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 141731] Missing tool tip for recent files on welcome screen
https://bugs.documentfoundation.org/show_bug.cgi?id=141731 --- Comment #6 from Vasily Melenchuk (CIB) --- Everything is fine for me locally with recent master with mentioned my fix (https://git.libreoffice.org/core/commit/8fdbb8aed1b48734a717d5f98ada566de7204605) and without it. Or bug behavior is quite unstable? So cannot reproduce. And I'm somewhat sceptic about role of my changes: they are done in unrelated area. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 143986] In slideshow mode, when we go to the next slide, horizontal bands flicker across the screen
https://bugs.documentfoundation.org/show_bug.cgi?id=143986 --- Comment #2 from NarayanAras --- BTW I am using an Acer Aspire A315-53 laptop, with 12 GB RAM Processor: i3-8130U CPU @ 2.20GHz, 2208 Mhz Installed Physical Memory (RAM) 12.0 GB Available Physical Memory 6.18 GB Total Virtual Memory13.7 GB Available Virtual Memory6.75 GB So I guess this problem is not due to a shortage of system resources. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 143986] In slideshow mode, when we go to the next slide, horizontal bands flicker across the screen
https://bugs.documentfoundation.org/show_bug.cgi?id=143986 --- Comment #1 from NarayanAras --- BTW I am using an Acer Aspire A315-53 laptop, with 12 GB RAM Processor: i3-8130U CPU @ 2.20GHz, 2208 Mhz Installed Physical Memory (RAM) 12.0 GB Available Physical Memory 6.18 GB Total Virtual Memory13.7 GB Available Virtual Memory6.75 GB So I guess this problem is not due to a shortage of system resources. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 143986] New: In slideshow mode, when we go to the next slide, horizontal bands flicker across the screen
https://bugs.documentfoundation.org/show_bug.cgi?id=143986 Bug ID: 143986 Summary: In slideshow mode, when we go to the next slide, horizontal bands flicker across the screen Product: LibreOffice Version: 3.3.0 release Hardware: All OS: Windows (All) Status: UNCONFIRMED Severity: normal Priority: medium Component: Impress Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: raindrops.from...@gmail.com Description: In slideshow mode, when we go to the next slide, horizontal bands flicker across the screen. Mostly only one band appears, near the top of the screen. The band disappears in a fraction of a second. The band only appears when the slide transition is happening. Such bands do NOT appear when I press the DownArrow key to animate the slide (e.g. when a numbered list is animated by 1st level paragraph). These bands have approximately 1" height, and they span the full width of the screen. They are always filled with a fixed black-and-white geometric pattern that looks like a QR bar code pattern. This problem occurs in both the latest stable version of LibreOffice (7.2.0.4) and the latest Alpha nightly (7.3.0.0). This is a highly annoying problem: It creates a horrible impression of the presenter! Steps to Reproduce: 1.Make any presentation in slide show mode. 2.Press downArrow to progress through the presentation. 3. Actual Results: A band flickers during slide transition moment, and disappears in a fraction of a second. Expected Results: The band must not appear. Reproducible: Always User Profile Reset: No Additional Info: [Information automatically included from LibreOffice] Locale: en-US Module: PresentationDocument OS: Windows 10 Home (64 bit) -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 90931] 'Apply Style' drop down doesnt show accurate style previews
https://bugs.documentfoundation.org/show_bug.cgi?id=90931 --- Comment #10 from Colin --- (In reply to Colin from comment #8) > > I can confirm it's still not performing according to expectations. > I am also minded to note that the multibox at the foot of the page refused > to display anything but "default" for [Applied Styles]. I subsequently > installed the extension "Styles Reporter" which upon activation, also > appeared to remediate the missing "applied styles". > Sorry, I omitted the most pertinent piece of information - the missing applied styles were in relation to styles that were only applied within conditional formatting elements -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 90931] 'Apply Style' drop down doesnt show accurate style previews
https://bugs.documentfoundation.org/show_bug.cgi?id=90931 --- Comment #9 from Colin --- (In reply to Colin from comment #8) > > My post in AskLib contains confirmation from another user that the error was > apparent for him also. Please advise if you would like me to remove the > extension and re-test prior to filing a further report - which should > probably still define the anomaly but offer a workaround Sorry, forgot to add the link https://ask.libreoffice.org/t/identifying-utilised-and-redundant-user-styles-in-calc-conditional-formatting/67157 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 90931] 'Apply Style' drop down doesnt show accurate style previews
https://bugs.documentfoundation.org/show_bug.cgi?id=90931 --- Comment #8 from Colin --- Version: 7.0.6.2 (x64) Build ID: 144abb84a525d8e30c9dbbefa69cbbf2d8d4ae3b CPU threads: 4; OS: Windows 10.0 Build 19042; UI render: Skia/Raster; VCL: win Locale: sv-SE (en_GB); UI: en-GB Calc: threaded I can confirm it's still not performing according to expectations. I am also minded to note that the multibox at the foot of the page refused to display anything but "default" for [Applied Styles]. I subsequently installed the extension "Styles Reporter" which upon activation, also appeared to remediate the missing "applied styles". My post in AskLib contains confirmation from another user that the error was apparent for him also. Please advise if you would like me to remove the extension and re-test prior to filing a further report - which should probably still define the anomaly but offer a workaround -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 116727] EDITING: Undo while Clone Formatting leads to text having double font size (see comment 4)
https://bugs.documentfoundation.org/show_bug.cgi?id=116727 Gerald Pfeifer changed: What|Removed |Added Summary|EDITING: Undo after Clone |EDITING: Undo while Clone |Formatting leads to text|Formatting leads to text |having double font size |having double font size |(see comment 4) |(see comment 4) --- Comment #9 from Gerald Pfeifer --- Still reproducible with Version: 7.3.0.0.alpha0+ / LibreOffice Community Build ID: da006fbe2d4c5891933390d72f6e6026b28d39fc CPU threads: 8; OS: Linux 5.13; UI render: default; VCL: gtk3 Locale: en-US (en_US.UTF-8); UI: en-US TinderBox: Linux-rpm_deb-x86_64@86-TDF, Branch:master, Time: 2021-08-19_11:31:56 Note this only appears reproducible when clone mode is still active. If I hit after cloning, things appear fine. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 143613] Many UI containers seem to use a hard coded black background with the black text of the light colored theme in XFCE.
https://bugs.documentfoundation.org/show_bug.cgi?id=143613 QA Administrators changed: What|Removed |Added Whiteboard| QA:needsComment| -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 143750] Missing or extra parentheses and/or quotation marks function no longer works in version 7.2.0.2.
https://bugs.documentfoundation.org/show_bug.cgi?id=143750 QA Administrators changed: What|Removed |Added Whiteboard| QA:needsComment| -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 140638] Cannot use LibreOffice 7.1.0 via OLE on Windows Server 2016
https://bugs.documentfoundation.org/show_bug.cgi?id=140638 QA Administrators changed: What|Removed |Added Whiteboard| QA:needsComment| -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 143955] Copy does not work in LibreOffice Writer 7.2.0.
https://bugs.documentfoundation.org/show_bug.cgi?id=143955 QA Administrators changed: What|Removed |Added Status|NEEDINFO|UNCONFIRMED Ever confirmed|1 |0 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 143761] Enhancement: PLEASE revert location of RGB controls in Draw
https://bugs.documentfoundation.org/show_bug.cgi?id=143761 QA Administrators changed: What|Removed |Added Whiteboard|| QA:needsComment -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 143764] bump scroll too fast
https://bugs.documentfoundation.org/show_bug.cgi?id=143764 QA Administrators changed: What|Removed |Added Whiteboard|| QA:needsComment -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 143758] Content of listbox in table control will disappear when listbox is refreshed by macro.
https://bugs.documentfoundation.org/show_bug.cgi?id=143758 QA Administrators changed: What|Removed |Added Whiteboard|| QA:needsComment -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 143955] Copy does not work in LibreOffice Writer 7.2.0.
https://bugs.documentfoundation.org/show_bug.cgi?id=143955 --- Comment #7 from QA Administrators --- [Automated Action] NeedInfo-To-Unconfirmed -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 140535] equation sign '=' is not printed
https://bugs.documentfoundation.org/show_bug.cgi?id=140535 --- Comment #5 from QA Administrators --- Dear Bruno Schäfer, This bug has been in NEEDINFO status with no change for at least 6 months. Please provide the requested information as soon as possible and mark the bug as UNCONFIRMED. Due to regular bug tracker maintenance, if the bug is still in NEEDINFO status with no change in 30 days the QA team will close the bug as INSUFFICIENTDATA due to lack of needed information. For more information about our NEEDINFO policy please read the wiki located here: https://wiki.documentfoundation.org/QA/Bugzilla/Fields/Status/NEEDINFO If you have already provided the requested information, please mark the bug as UNCONFIRMED so that the QA team knows that the bug is ready to be confirmed. Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-NeedInfo-Ping -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 77437] Macros: VBA loop While ActiveCell <> "" don't work on Libreoffice
https://bugs.documentfoundation.org/show_bug.cgi?id=77437 --- Comment #13 from QA Administrators --- Dear Alejandro Moreno, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://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] [Bug 76134] FORMATTING: Column widths are not interpreted properly from Microsoft Word 2003 XML format
https://bugs.documentfoundation.org/show_bug.cgi?id=76134 --- Comment #12 from QA Administrators --- Dear Gergely Rácz, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://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] [Bug 70337] uninserted spurious object appearing in document
https://bugs.documentfoundation.org/show_bug.cgi?id=70337 --- Comment #10 from QA Administrators --- Dear Paolo Benvenuto, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://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] [Bug 125419] Dialog theming/UX - "Highlight color" is hard to use with finger
https://bugs.documentfoundation.org/show_bug.cgi?id=125419 --- Comment #3 from QA Administrators --- Dear Nicolas Christener, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://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] [Bug 116727] EDITING: Undo after Clone Formatting leads to text having double font size (see comment 4)
https://bugs.documentfoundation.org/show_bug.cgi?id=116727 --- Comment #8 from QA Administrators --- Dear Gerald Pfeifer, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://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] [Bug 112819] FORMATTING: Weird presentation of indented paragraphs (e.g. list items) in comments
https://bugs.documentfoundation.org/show_bug.cgi?id=112819 --- Comment #4 from QA Administrators --- Dear Thomas Lendo, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://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] [Bug 143889] f4 crashes LODev
https://bugs.documentfoundation.org/show_bug.cgi?id=143889 Dmitrii A changed: What|Removed |Added CC||anisimov...@gmail.com --- Comment #2 from Dmitrii A --- no repro in Version: 7.3.0.0.alpha0+ (x64) / LibreOffice Community Build ID: ac80ec817eb07c77a51bc0729985a473c734182e CPU threads: 16; OS: Windows 10.0 Build 19042; UI render: Skia/Raster; VCL: win Locale: ru-RU (ru_RU); UI: en-US Calc: CL -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 143964] insert/overwrite cursor shape lags in formula editing
https://bugs.documentfoundation.org/show_bug.cgi?id=143964 Dmitrii A changed: What|Removed |Added CC||anisimov...@gmail.com --- Comment #1 from Dmitrii A --- no repro in Version: 7.3.0.0.alpha0+ (x64) / LibreOffice Community Build ID: ac80ec817eb07c77a51bc0729985a473c734182e CPU threads: 16; OS: Windows 10.0 Build 19042; UI render: Skia/Raster; VCL: win Locale: ru-RU (ru_RU); UI: en-US Calc: CL I think it works how it should, when cursor is in front the simbols it instantly changes. When there are no symbols to replace for example in the end of string it doesn't. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 143978] Calc: shrink to fit
https://bugs.documentfoundation.org/show_bug.cgi?id=143978 Dmitrii A changed: What|Removed |Added CC||anisimov...@gmail.com --- Comment #1 from Dmitrii A --- no repro in Version: 7.3.0.0.alpha0+ (x64) / LibreOffice Community Build ID: ac80ec817eb07c77a51bc0729985a473c734182e CPU threads: 16; OS: Windows 10.0 Build 19042; UI render: Skia/Raster; VCL: win Locale: ru-RU (ru_RU); UI: en-US Calc: CL Content shrinks gradualy due to the number of simbols. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 143984] Relative table size lost on RTF export
https://bugs.documentfoundation.org/show_bug.cgi?id=143984 Dmitrii A changed: What|Removed |Added Status|UNCONFIRMED |NEW Ever confirmed|0 |1 --- Comment #2 from Dmitrii A --- confirm in Version: 7.3.0.0.alpha0+ (x64) / LibreOffice Community Build ID: ac80ec817eb07c77a51bc0729985a473c734182e CPU threads: 16; OS: Windows 10.0 Build 19042; UI render: Skia/Raster; VCL: win Locale: ru-RU (ru_RU); UI: en-US Calc: CL -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 143970] Regression in Calc, LibreOffice 7.2.0.4 Final. "Will Not auto-fill if the cell above or down is Blank" OR "Will auto fill 1 up or 1 down cell only, if there is no Empty
https://bugs.documentfoundation.org/show_bug.cgi?id=143970 Getafix changed: What|Removed |Added Summary|Will auto fill 1 up or 1|Regression in Calc, |down cell only, Regression |LibreOffice 7.2.0.4 Final. |in Calc, LibreOffice|"Will Not auto-fill if the |7.2.0.4 Final |cell above or down is ||Blank" OR "Will auto fill 1 ||up or 1 down cell only, if ||there is no Empty cell" --- Comment #2 from Getafix --- Regression in Calc, LibreOffice 7.2.0.4 Final. "Will Not auto-fill if the cell above or down is Blank" OR "Will auto fill 1 up or 1 down cell only, if there is no Empty cell" -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 143970] Will auto fill 1 up or 1 down cell only, Regression in Calc, LibreOffice 7.2.0.4 Final
https://bugs.documentfoundation.org/show_bug.cgi?id=143970 --- Comment #1 from Getafix --- same happens when we press "alt" + "down arrow", list/dropdown wont appear if there is a empty cell above -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 143881] FORMULA: abs{x}^2 is formatted with unexpected operator precedence
https://bugs.documentfoundation.org/show_bug.cgi?id=143881
--- Comment #4 from dante19031...@gmail.com ---
(In reply to Roman Kuznetsov from comment #3)
> (In reply to hardy from comment #2)
> > I can accept that you do not want to change the syntax of the formula
> > editor. I was fully aware of this workaround, and just wanted to help
> > improving LibreOffice.
>
>
> So, possibly we can change this one to an enhancement.
>
> Dante, what do you think about hardy's ideas?
Problems:
Changing the behavior would break old documents.
Changing the UI would break the visual editor because those brackets keep the
sentence together. The abs priority is the same as multiplication, so sums
inside of it would exit the abs the moment you type them.
The most I can do is change the code inserted via the UI to { abs { } }.
I leave that decision up to you. The UI change is one line patch.
I also find that feature a bit troubling, however blackguards compatibility is
problematic.
And also, log(x)^2 is equivalent to { { log } { { ( x ) } ^ 2 } } for the
parser, but the problem is invisible. Math isn't right from mathematics POV, it
just looks like it.
--
You are receiving this mail because:
You are the assignee for the bug.
[Libreoffice-bugs] [Bug 143959] PDF import do not take embedded fonts
https://bugs.documentfoundation.org/show_bug.cgi?id=143959 Kevin Suo changed: What|Removed |Added Assignee|libreoffice-b...@lists.free |suokunl...@126.com |desktop.org | -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 143959] PDF import do not take embedded fonts
https://bugs.documentfoundation.org/show_bug.cgi?id=143959 --- Comment #8 from Kevin Suo --- (In reply to Timur from comment #7) Timur and Gabriel Dorante, if I am understanding correct, this now works correct on master builds (i.e., fonts are shown as "TimesNewRoman" and thus is correctly applied as Times New Roman font by the system), but is broken in 7.2 build (i.e., fonts are shown as "AA+TimesNewRoman")? -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 141731] Missing tool tip for recent files on welcome screen
https://bugs.documentfoundation.org/show_bug.cgi?id=141731 Eleonora Govallo changed: What|Removed |Added Keywords|bibisectRequest |bibisected, bisected CC||vasily.melenc...@cib.de --- Comment #5 from Eleonora Govallo --- Hello! I bisected this bug: all bisected 7.3 versions have this bug, all bisected 7.1 versions haven't this bug. In version 7.2 source sha:8fdbb8aed1b48734a717d5f98ada566de7204605 https://gerrit.libreoffice.org/c/core/+/119990 https://git.libreoffice.org/core/commit/8fdbb8aed1b48734a717d5f98ada566de7204605 Added to CC Vasily Melenchuk -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-commits] core.git: svtools/source
svtools/source/misc/langtab.cxx | 38 +-
1 file changed, 25 insertions(+), 13 deletions(-)
New commits:
commit 05924f9b2e651f545d8ceea883d9b1729257349d
Author: Eike Rathke
AuthorDate: Fri Aug 20 23:17:27 2021 +0200
Commit: Eike Rathke
CommitDate: Sat Aug 21 01:58:59 2021 +0200
Use LanguageTagIcu::getDisplayName() for on-the-fly language list entries
So the for {tag} entries "too geeky" argument of spell-checker
dictionary developers and language enthusiasts will be moot in
future and we can stop adding 100 more tags if it's not for locale
data.
Change-Id: Ic44fe5b2f794ddb258e56ec073f310ccaf6e470d
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/120799
Tested-by: Jenkins
Reviewed-by: Eike Rathke
diff --git a/svtools/source/misc/langtab.cxx b/svtools/source/misc/langtab.cxx
index 7bd30f365158..9981cf6862b3 100644
--- a/svtools/source/misc/langtab.cxx
+++ b/svtools/source/misc/langtab.cxx
@@ -29,8 +29,11 @@
#include
#include
#include
+#include
#include
+#include
+#include
#include
#include
#include
@@ -156,16 +159,25 @@ OUString ApplyLreOrRleEmbedding( const OUString )
return aRes;
}
-static OUString lcl_getDescription( std::u16string_view rBcp47 )
+static OUString lcl_getDescription( const LanguageTag& rTag )
{
-// Place in curly brackets, so all on-the-fly tags are grouped together at
-// the top of a listbox (but behind the "[None]" entry), and not sprinkled
-// all over, which alphabetically might make sense in an English UI only
-// anyway. Also a visual indicator that it is a programmatical name, IMHO.
-/* TODO: pulling descriptive names (language, script, country, subtags)
- * from liblangtag or ISO databases might be nice, but those are English
- * only. Maybe ICU, that has translations for language and country. */
-return OUString::Concat("{") + rBcp47 + "}";
+OUString aStr( LanguageTagIcu::getDisplayName( rTag,
Application::GetSettings().GetUILanguageTag()));
+if (aStr.isEmpty() || aStr == rTag.getBcp47())
+{
+// Place in curly brackets, so all on-the-fly tags without display name
+// are grouped together at the top of a listbox (but behind the
+// "[None]" entry), and not sprinkled all over, which alphabetically
+// might make sense in an English UI only anyway. Also a visual
+// indicator that it is a programmatical name, IMHO.
+return OUString::Concat("{") + aStr + "}";
+}
+else
+{
+// The ICU display name might be identical to a predefined name or even
+// to another tag's ICU name; clarify that this is a generated name and
+// append the language tag in curly brackets to distinguish.
+return aStr + " {" + rTag.getBcp47() + "}";
+}
}
SvtLanguageTableImpl::SvtLanguageTableImpl()
@@ -193,7 +205,7 @@ SvtLanguageTableImpl::SvtLanguageTableImpl()
aLang.setScriptType(LanguageTag::ScriptType(nType));
sal_uInt32 nPos = FindIndex(nLangType);
if (nPos == RESARRAY_INDEX_NOTFOUND)
-AddItem((aName.isEmpty() ? lcl_getDescription(rBcp47) :
aName), nLangType);
+AddItem((aName.isEmpty() ? lcl_getDescription(aLang) : aName),
nLangType);
}
}
}
@@ -219,8 +231,8 @@ OUString SvtLanguageTableImpl::GetString( const
LanguageType eType ) const
if ( RESARRAY_INDEX_NOTFOUND != nPos && nPos < GetEntryCount() )
return m_aStrings[nPos].first;
-//Rather than return a fairly useless "Unknown" name, return a geeky but
usable-in-a-pinch lang-tag
-OUString sLangTag( lcl_getDescription(
LanguageTag::convertToBcp47(eType)));
+// Obtain from ICU, or a geeky but usable-in-a-pinch lang-tag.
+OUString sLangTag( lcl_getDescription( LanguageTag(eType)));
SAL_WARN("svtools.misc", "Language: 0x"
<< std::hex << eType
<< " with unknown name, so returning lang-tag of: "
@@ -287,7 +299,7 @@ LanguageType SvtLanguageTable::GetLanguageTypeAtIndex(
sal_uInt32 nIndex )
sal_uInt32 SvtLanguageTable::AddLanguageTag( const LanguageTag& rLanguageTag )
{
-return theLanguageTable::get().AddItem(
lcl_getDescription(rLanguageTag.getBcp47()),
+return theLanguageTable::get().AddItem( lcl_getDescription(rLanguageTag),
rLanguageTag.getLanguageType());
}
[Libreoffice-commits] core.git: i18nlangtag/CppunitTest_i18nlangtag_test_languagetag.mk i18nlangtag/qa
i18nlangtag/CppunitTest_i18nlangtag_test_languagetag.mk |2
i18nlangtag/qa/cppunit/test_languagetag.cxx | 75
2 files changed, 77 insertions(+)
New commits:
commit 6d6119bc4e4a783c76b3ae35626d6fea0de0abac
Author: Eike Rathke
AuthorDate: Fri Aug 20 22:49:40 2021 +0200
Commit: Eike Rathke
CommitDate: Sat Aug 21 01:58:16 2021 +0200
Unit test for LanguageTagIcu::getDisplayName()
Change-Id: Ibe95fba21ed94be7fb4848f19161d492bc403e4d
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/120798
Tested-by: Jenkins
Reviewed-by: Eike Rathke
diff --git a/i18nlangtag/CppunitTest_i18nlangtag_test_languagetag.mk
b/i18nlangtag/CppunitTest_i18nlangtag_test_languagetag.mk
index 72402632d341..801bfe7b99ff 100644
--- a/i18nlangtag/CppunitTest_i18nlangtag_test_languagetag.mk
+++ b/i18nlangtag/CppunitTest_i18nlangtag_test_languagetag.mk
@@ -21,6 +21,8 @@ $(eval $(call
gb_CppunitTest_use_libraries,i18nlangtag_test_languagetag,\
))
$(eval $(call gb_CppunitTest_use_externals,i18nlangtag_test_languagetag,\
+ icu_headers \
+ icuuc \
liblangtag \
libxml2 \
))
diff --git a/i18nlangtag/qa/cppunit/test_languagetag.cxx
b/i18nlangtag/qa/cppunit/test_languagetag.cxx
index c3dfb151e14e..8f76fb58d6f1 100644
--- a/i18nlangtag/qa/cppunit/test_languagetag.cxx
+++ b/i18nlangtag/qa/cppunit/test_languagetag.cxx
@@ -16,6 +16,7 @@
#include
#include
+#include
#include
@@ -33,10 +34,12 @@ public:
void testAllTags();
void testAllIsoLangEntries();
+void testDisplayNames();
CPPUNIT_TEST_SUITE(TestLanguageTag);
CPPUNIT_TEST(testAllTags);
CPPUNIT_TEST(testAllIsoLangEntries);
+CPPUNIT_TEST(testDisplayNames);
CPPUNIT_TEST_SUITE_END();
};
@@ -803,6 +806,78 @@ void TestLanguageTag::testAllIsoLangEntries()
//CPPUNIT_ASSERT( true == false );
}
+void TestLanguageTag::testDisplayNames()
+{
+OUString aStr;
+aStr = LanguageTagIcu::getDisplayName( LanguageTag("en-US"),
LanguageTag("en-US"));
+CPPUNIT_ASSERT_EQUAL( OUString("English (United States)"), aStr);
+aStr = LanguageTagIcu::getDisplayName( LanguageTag("en-US"),
LanguageTag("en"));
+CPPUNIT_ASSERT_EQUAL( OUString("English (United States)"), aStr);
+aStr = LanguageTagIcu::getDisplayName( LanguageTag("en"),
LanguageTag("en"));
+CPPUNIT_ASSERT_EQUAL( OUString("English"), aStr);
+
+aStr = LanguageTagIcu::getDisplayName( LanguageTag("en-US"),
LanguageTag("de-DE"));
+CPPUNIT_ASSERT_EQUAL( OUString("Englisch (Vereinigte Staaten)"), aStr);
+aStr = LanguageTagIcu::getDisplayName( LanguageTag("en-US"),
LanguageTag("de"));
+CPPUNIT_ASSERT_EQUAL( OUString("Englisch (Vereinigte Staaten)"), aStr);
+aStr = LanguageTagIcu::getDisplayName( LanguageTag("en"),
LanguageTag("de"));
+CPPUNIT_ASSERT_EQUAL( OUString("Englisch"), aStr);
+
+aStr = LanguageTagIcu::getDisplayName( LanguageTag("de-DE"),
LanguageTag("en"));
+CPPUNIT_ASSERT_EQUAL( OUString("German (Germany)"), aStr);
+aStr = LanguageTagIcu::getDisplayName( LanguageTag("de"),
LanguageTag("en"));
+CPPUNIT_ASSERT_EQUAL( OUString("German"), aStr);
+aStr = LanguageTagIcu::getDisplayName( LanguageTag("de-DE-1901"),
LanguageTag("en"));
+CPPUNIT_ASSERT_EQUAL( OUString("German (Germany, Traditional German
orthography)"), aStr);
+aStr = LanguageTagIcu::getDisplayName( LanguageTag("de-DE-1901"),
LanguageTag("de-DE"));
+CPPUNIT_ASSERT_EQUAL( OUString("Deutsch (Deutschland, Alte deutsche
Rechtschreibung)"), aStr);
+
+aStr = LanguageTagIcu::getDisplayName( LanguageTag("en-GB"),
LanguageTag("en"));
+CPPUNIT_ASSERT_EQUAL( OUString("English (United Kingdom)"), aStr);
+aStr = LanguageTagIcu::getDisplayName( LanguageTag("en-GB-oxendict"),
LanguageTag("en"));
+CPPUNIT_ASSERT_EQUAL( OUString("English (United Kingdom, Oxford English
Dictionary spelling)"), aStr);
+
+aStr = LanguageTagIcu::getDisplayName( LanguageTag("ca-ES-valencia"),
LanguageTag("en"));
+CPPUNIT_ASSERT_EQUAL( OUString("Catalan (Spain, Valencian)"), aStr);
+
+aStr = LanguageTagIcu::getDisplayName( LanguageTag("sr-Cyrl-RS"),
LanguageTag("en"));
+CPPUNIT_ASSERT_EQUAL( OUString("Serbian (Serbia)"), aStr);
+aStr = LanguageTagIcu::getDisplayName( LanguageTag("sr-Latn-RS"),
LanguageTag("en"));
+CPPUNIT_ASSERT_EQUAL( OUString("Serbian (Latin, Serbia)"), aStr);
+
+aStr = LanguageTagIcu::getDisplayName( LanguageTag("tlh"),
LanguageTag("en"));
+CPPUNIT_ASSERT_EQUAL( OUString("Klingon"), aStr);
+
+aStr = LanguageTagIcu::getDisplayName( LanguageTag("und"),
LanguageTag("en"));
+CPPUNIT_ASSERT_EQUAL( OUString("Unknown language"), aStr);
+
+aStr = LanguageTagIcu::getDisplayName( LanguageTag("zxx"),
LanguageTag("en"));
+CPPUNIT_ASSERT_EQUAL( OUString("No linguistic content"), aStr);
+
+aStr = LanguageTagIcu::getDisplayName( LanguageTag("x-lala"),
LanguageTag("en"));
+CPPUNIT_ASSERT_EQUAL(
[Libreoffice-bugs] [Bug 143750] Missing or extra parentheses and/or quotation marks function no longer works in version 7.2.0.2.
https://bugs.documentfoundation.org/show_bug.cgi?id=143750 --- Comment #2 from Eek! A Bug. Kill it! --- I did some more experimenting after reading your comments and discovered something very interesting, if not downright odd. I now realize that this issue is, at least in part, due to my unchecking the “Check spelling as you type” option in: Tools > Options… > Language Settings > Writing Aids > Options. NOTE: The same thing can be accomplished by simply turning off the “Toggle Automatic Spell Checking (Shift+F7)” feature in the Standard Menu Bar. (So, why have a duplicate feature with a different, albeit similar, name?) I did this because of the nagging issue LO Writer has of auto-correcting text that is in fact correct as typed; for example, computer code that is not capitalized. Now, one would NOT think that this setting, the “Check spelling as you type” setting, would have anything to do with the issue this bug report was referring to, which is the “Check grammar as you type” setting, but I have just tried numerous times and the grammar (e.g., incorrect capitalization, missing/unpaired quotation marks, and the missing/unpaired parentheses) functions do NOT work unless you also have the “Check spelling as you type” setting checked. That is counterintuitive behavior because spelling and grammar are two completely different subjects, which is why they presumably have two separate check-boxes. Additionally, it makes little sense because there is only a red squiggly underline associated with the “Toggle Automatic Spell Checking” icon in the Standard Menu Bar—not a blue squiggly underline paired with it. Example: I wrote the two sentences below with an extra, or missing, punctuation mark. Note: I had both “Toggle Automatic Spell Checking” and “Check spelling as you type” turned off and the “Check grammar as you type” turned on. LO Writer did NOT detect either grammatical error – not what one would expect after turning the grammar checker on. “Now is the time for all “good men and women” to come to the aid of their country. “Now is the time for all good men (and women)) to come to the aid of their country.” I then clicked the “Toggle Automatic Spell Checking” on the Standard Menu Bar to turn it on and it then instantly detected the missing quotation mark in the first sentence but failed to detect the extra, or unpaired, closing parentheses in the second sentence. That is bizarre because both grammar checking functions use the same checkbox (Parentheses) to invoke both functions (parentheses and quotation marks). On the other hand, if you then turn “Check grammar as you type” off, it does not detect either punctuation error – as expected. The following is a related side note. If you try to check the checkbox for “Check spelling as you type” when the “Toggle Automatic Spell Checking” is NOT selected in the Standard Tool Bar, then when you press “Apply”, the Standard Tool Bar will automatically switch to being selected – but the checkbox for “Check spelling as you type” you just checked will flip back to being unchecked. If you then either close the window, click the “Apply” button a second time, or press “OK”, the two settings will sync back up together. This rather odd behavior is counter-intuitive and unexpected. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-commits] core.git: i18nlangtag/source include/i18nlangtag
i18nlangtag/source/languagetag/languagetagicu.cxx | 22 ++
include/i18nlangtag/languagetagicu.hxx| 17 +
2 files changed, 39 insertions(+)
New commits:
commit c482aefe08e4486aa35ba87edea1a341c97b8610
Author: Eike Rathke
AuthorDate: Fri Aug 20 22:47:08 2021 +0200
Commit: Eike Rathke
CommitDate: Sat Aug 21 00:11:47 2021 +0200
Introduce LanguageTagIcu::getDisplayName()
To be used in generating display names for on-the-fly language
tags in the language listbox.
Change-Id: Ibb36fe312e550f77f1e2d3acc2dbff9e83c15f7b
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/120797
Reviewed-by: Eike Rathke
Tested-by: Jenkins
diff --git a/i18nlangtag/source/languagetag/languagetagicu.cxx
b/i18nlangtag/source/languagetag/languagetagicu.cxx
index c35e7a85ef8b..fd1c9bc75670 100644
--- a/i18nlangtag/source/languagetag/languagetagicu.cxx
+++ b/i18nlangtag/source/languagetag/languagetagicu.cxx
@@ -46,4 +46,26 @@ icu::Locale LanguageTagIcu::getIcuLocale( const LanguageTag
& rLanguageTag, std:
);
}
+// static
+OUString LanguageTagIcu::getDisplayName( const LanguageTag & rLanguageTag,
const LanguageTag & rDisplayLanguage )
+{
+// This will be initialized by the first call; as the UI language doesn't
+// change the tag mostly stays the same, unless someone overrides it for a
+// call here, and thus obtaining the UI icu::Locale has to be done only
+// once.
+static thread_local LanguageTag aUITag( LANGUAGE_SYSTEM);
+static thread_local icu::Locale aUILocale;
+
+if (aUITag != rDisplayLanguage)
+{
+aUITag = rDisplayLanguage;
+aUILocale = getIcuLocale( rDisplayLanguage);
+}
+
+icu::Locale aLocale( getIcuLocale( rLanguageTag));
+icu::UnicodeString aResult;
+aLocale.getDisplayName( aUILocale, aResult);
+return OUString( reinterpret_cast(aResult.getBuffer()), aResult.length());
+}
+
/* vim:set shiftwidth=4 softtabstop=4 expandtab: */
diff --git a/include/i18nlangtag/languagetagicu.hxx
b/include/i18nlangtag/languagetagicu.hxx
index 755d8eb12c76..430c483f344d 100644
--- a/include/i18nlangtag/languagetagicu.hxx
+++ b/include/i18nlangtag/languagetagicu.hxx
@@ -15,6 +15,7 @@
#include
#include
+#include
#include
class LanguageTag;
@@ -49,6 +50,22 @@ public:
Always resolves an empty tag to the system locale.
*/
static icu::Locale getIcuLocale( const LanguageTag & rLanguageTag,
std::u16string_view rVariant, std::u16string_view rKeywords);
+
+/** Obtain the display name for a language tag.
+
+Gets a localized name from icu::Locale::getDisplayName(). Meant to be
+used only with language tags that do not have a language list entry in
+svtools/inc/langtab.hrc STR_ARR_SVT_LANGUAGE_TABLE, thus used by
+SvtLanguageTable::GetLanguageString()
+
+@param rLanguageTag
+The language tag for which the name is to be displayed.
+
+@param rDisplayLanguage
+The language in which the name is to be displayed.
+Usually Application::GetSettings().GetUILanguageTag().
+ */
+static OUStringgetDisplayName( const LanguageTag & rLanguageTag,
const LanguageTag & rDisplayLanguage );
};
#endif // INCLUDED_I18NLANGTAG_LANGUAGETAGICU_HXX
[Libreoffice-bugs] [Bug 143985] Deleted Program
https://bugs.documentfoundation.org/show_bug.cgi?id=143985 Eike Rathke changed: What|Removed |Added Status|RESOLVED|CLOSED -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 143985] Deleted Program
https://bugs.documentfoundation.org/show_bug.cgi?id=143985 Eike Rathke changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |NOTOURBUG --- Comment #1 from Eike Rathke --- And why would it be a bug of LibreOffice if your Windows update deleted it? NotOurBug. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 143979] FORMATTING: Date format is mangled when file is closed and reopened
https://bugs.documentfoundation.org/show_bug.cgi?id=143979 Eike Rathke changed: What|Removed |Added OS|Mac OS X (All) |All Ever confirmed|0 |1 Status|UNCONFIRMED |NEW Hardware|x86-64 (AMD64) |All Version|7.1.4.2 release |Inherited From OOo --- Comment #1 from Eike Rathke --- Seems the empty string is eliminated while saving the format description and that ends up as i.e. two consecutive month elements for MM and MMM which when read in correctly form M. Workaround: use U+200B ZERO WIDTH SPACE, ZWSP in your quotes. This looks the same -MM""MMM-DDNN but if you copy-paste it and travel through with the cursor you'll notice one extra character where the cursor does not move. that is saved and preserved when loaded: <200b> -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 143946] Add klingon as a supported language
https://bugs.documentfoundation.org/show_bug.cgi?id=143946 Eike Rathke changed: What|Removed |Added Status|UNCONFIRMED |ASSIGNED Ever confirmed|0 |1 Version|7.1.3.2 release |unspecified Assignee|libreoffice-b...@lists.free |er...@redhat.com |desktop.org | --- Comment #3 from Eike Rathke --- I will add it just because it's Klingon.. Anyhow, the difference with Esperanto and Lojban is that they have locale data, for which the language list entries are needed anyway. Do you plan to contribute locale data as well? Otherwise the language will be selectable for character/paragraph/font attribution and spell-check, but not as default language for all documents or for number formatting. See https://wiki.documentfoundation.org/LibreOffice_Localization_Guide/How_To_Submit_New_Locale_Data -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 141611] Lock icon does not appear on newly protected sheets in a new window
https://bugs.documentfoundation.org/show_bug.cgi?id=141611 George changed: What|Removed |Added Resolution|--- |FIXED Status|UNCONFIRMED |RESOLVED --- Comment #3 from George --- Fixed now for me. Version: 7.2.0.4 / LibreOffice Community Build ID: 9a9c6381e3f7a62afc1329bd359cc48accb6435b CPU threads: 4; OS: Linux 5.4; UI render: default; VCL: gtk3 Locale: en-CA (en_CA.UTF-8); UI: en-US Calc: threaded -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 143985] New: Deleted Program
https://bugs.documentfoundation.org/show_bug.cgi?id=143985 Bug ID: 143985 Summary: Deleted Program Product: LibreOffice Version: unspecified Hardware: x86 (IA32) OS: Windows (All) Status: UNCONFIRMED Severity: normal Priority: medium Component: LibreOffice Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: aar...@gmail.com Description: Strange. I updated my Windows 10 and for some reason my entire LibreOffice program was deleted except for the help file. My .odt extensions were set to MS Word. So I am reinstalling the latest release and remapping my documents to default open with Libre but gosh... Actual Results: I should be able to fix it Expected Results: I should be able to fix it Reproducible: Always User Profile Reset: No Additional Info: I should be able to fix it -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 143581] Feature request - Insertion of super and subscript in chart and axis titles
https://bugs.documentfoundation.org/show_bug.cgi?id=143581 diva...@gmail.com changed: What|Removed |Added Assignee|libreoffice-b...@lists.free |diva...@gmail.com |desktop.org | Ever confirmed|0 |1 Status|UNCONFIRMED |NEW --- Comment #1 from diva...@gmail.com --- Created attachment 174455 --> https://bugs.documentfoundation.org/attachment.cgi?id=174455=edit Illustration of menus pesented to explain the bugs -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 143975] Confirming command popup HUD (#91874) deletes selected text in Writer
https://bugs.documentfoundation.org/show_bug.cgi?id=143975 BogdanB changed: What|Removed |Added CC||buzea.bog...@libreoffice.or ||g Resolution|--- |DUPLICATE Status|UNCONFIRMED |RESOLVED --- Comment #2 from BogdanB --- *** This bug has been marked as a duplicate of bug 143817 *** -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 143817] Search Commands deleting contents in Writer when command applied to selected text
https://bugs.documentfoundation.org/show_bug.cgi?id=143817 BogdanB changed: What|Removed |Added CC||zimtigerc...@outlook.com --- Comment #6 from BogdanB --- *** Bug 143975 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 83536] Exports fixed with tables to HTML even when size is relative.
https://bugs.documentfoundation.org/show_bug.cgi?id=83536 Telesto changed: What|Removed |Added See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=14 ||3982 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 143982] Automatic table alignment which behaves as relative converted to absolute size on DOC/DOCX/RTF export
https://bugs.documentfoundation.org/show_bug.cgi?id=143982 Telesto changed: What|Removed |Added See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=83 ||536 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 143984] Relative table size lost on RTF export
https://bugs.documentfoundation.org/show_bug.cgi?id=143984 Telesto changed: What|Removed |Added Version|7.3.0.0 alpha0+ Master |Inherited From OOo --- Comment #1 from Telesto --- Also in 4.4.7.2 and in LibreOffice 3.3.0 OOO330m19 (Build:6) tag libreoffice-3.3.0.4 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 143984] New: Relative table size lost on RTF export
https://bugs.documentfoundation.org/show_bug.cgi?id=143984 Bug ID: 143984 Summary: Relative table size lost on RTF export Product: LibreOffice Version: 7.3.0.0 alpha0+ Master Hardware: All OS: All Status: UNCONFIRMED Severity: normal Priority: medium Component: Writer Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: tele...@surfxs.nl Description: Relative table size lost on RTF export Steps to Reproduce: 1. Open attachment 174454 2. Table -> Properties -> Table tab -> Notice relative being checked 3. Save as RTF 4. File reload 5. Table -> Properties -> Table tab -> Notice relative being unchecked Actual Results: Unchecked relative checkbox Expected Results: Checked Reproducible: Always User Profile Reset: No Additional Info: Version: 7.3.0.0.alpha0+ (x64) / LibreOffice Community Build ID: f58f35b2c8ca1efbacec642a8f3de5b0c499bc6b CPU threads: 4; OS: Windows 6.3 Build 9600; UI render: Skia/Raster; VCL: win Locale: nl-NL (nl_NL); UI: en-US Calc: CL -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 143983] Table alignment 'Left' becomes 'From left' on DOCX/RTF export (not with DOC)
https://bugs.documentfoundation.org/show_bug.cgi?id=143983 --- Comment #1 from Telesto --- Created attachment 174454 --> https://bugs.documentfoundation.org/attachment.cgi?id=174454=edit Example file -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 143983] New: Table alignment 'Left' becomes 'From left' on DOCX/RTF export (not with DOC)
https://bugs.documentfoundation.org/show_bug.cgi?id=143983 Bug ID: 143983 Summary: Table alignment 'Left' becomes 'From left' on DOCX/RTF export (not with DOC) Product: LibreOffice Version: 7.3.0.0 alpha0+ Master Hardware: All OS: All Status: UNCONFIRMED Severity: normal Priority: medium Component: Writer Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: tele...@surfxs.nl Description: Table alignment 'Left' becomes 'From left' on DOCX/RTF export (not with DOC) Steps to Reproduce: 1. Open the attached file 2. Table -> Properties -> Table tab -> Notice setting 'Relative + Left" 3. File Save as -> DOCX 4. File reload 5. Table -> Properties -> Table tab -> Notice setting From Left Actual Results: >From left Expected Results: Left I assume? Reproducible: Always User Profile Reset: No Additional Info: Version: 7.3.0.0.alpha0+ (x64) / LibreOffice Community Build ID: f58f35b2c8ca1efbacec642a8f3de5b0c499bc6b CPU threads: 4; OS: Windows 6.3 Build 9600; UI render: Skia/Raster; VCL: win Locale: nl-NL (nl_NL); UI: en-US Calc: CL -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 143982] Automatic table alignment which behaves as relative converted to absolute size on DOC/DOCX/RTF export
https://bugs.documentfoundation.org/show_bug.cgi?id=143982 Telesto changed: What|Removed |Added Summary|Automatic table alignment |Automatic table alignment |which behaves as relative |which behaves as relative |converted to absolute size |converted to absolute size |on DOC/DOCX/RTF |on DOC/DOCX/RTF export Version|7.3.0.0 alpha0+ Master |Inherited From OOo --- Comment #2 from Telesto --- Also in Versie 4.0.0.3 (Bouw-id: 7545bee9c2a0782548772a21bc84a9dcc583b89) and in LibreOffice 3.3.0 OOO330m19 (Build:6) tag libreoffice-3.3.0.4 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 143982] Automatic table alignment which behaves as relative converted to absolute size on DOC/DOCX/RTF
https://bugs.documentfoundation.org/show_bug.cgi?id=143982 --- Comment #1 from Telesto --- Created attachment 174453 --> https://bugs.documentfoundation.org/attachment.cgi?id=174453=edit Example file -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 143982] New: Automatic table alignment which behaves as relative converted to absolute size on DOC/DOCX/RTF
https://bugs.documentfoundation.org/show_bug.cgi?id=143982 Bug ID: 143982 Summary: Automatic table alignment which behaves as relative converted to absolute size on DOC/DOCX/RTF Product: LibreOffice Version: 7.3.0.0 alpha0+ Master Hardware: All OS: All Status: UNCONFIRMED Severity: normal Priority: medium Component: Writer Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: tele...@surfxs.nl Description: Automatic table alignment which behaves as relative converted to absolute size on DOCX Steps to Reproduce: 1. Open the attached file 2. Table -> Properties -> Table tab -> Notice automatic turned on 3. Drag the inner border red border to left or right (notice the embedded table adapting 4. File reload without save (there is bug which unchecks 'automatic when dragging inner border) 5. Save as DOCX 6. File reload 7. Drag the inner border to left (notice the embedded table not adapting) Actual Results: Relative behaviour lost on DOC/DOCX/ RTF export Expected Results: Should be still present Reproducible: Always User Profile Reset: No Additional Info: Version: 7.3.0.0.alpha0+ (x64) / LibreOffice Community Build ID: f58f35b2c8ca1efbacec642a8f3de5b0c499bc6b CPU threads: 4; OS: Windows 6.3 Build 9600; UI render: Skia/Raster; VCL: win Locale: nl-NL (nl_NL); UI: en-US Calc: CL -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 143981] New: Incorrect display of dark theme in LibreOffice
https://bugs.documentfoundation.org/show_bug.cgi?id=143981 Bug ID: 143981 Summary: Incorrect display of dark theme in LibreOffice Product: LibreOffice Version: 7.3.0.0 alpha0+ Master Hardware: x86-64 (AMD64) OS: Windows (All) Status: UNCONFIRMED Severity: normal Priority: medium Component: LibreOffice Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: katyalukkar...@gmail.com Description: When you select a dark theme in LibreOffice, the color changes only in the work area, with the exception of the scroll bar and ruler. The main menu, sidebar, toolbars, scrollbars, rulers, and status bar are all displayed in a light theme. Steps to Reproduce: 1.Click "Tools" in LibreOffice 2.Then click "Options" 3.And then "Application Colors" 4.choose in Color Scheme LibreOfficedev Dark Actual Results: the color changes only in the work area, with the exception of the scroll bar and ruler. The main menu, sidebar, toolbars, scrollbars, rulers, and status bar are all displayed in a light theme. Expected Results: color change takes place entirely in the application, including all elements: main menu, sidebar, scrollbar, status bar and work surface Reproducible: Always User Profile Reset: Yes Additional Info: Version: 7.3.0.0.alpha0+ (x64) / LibreOffice Community Build ID: cb2827f5f65324f309fa0e3c30d0b19ad237410e CPU threads: 8; OS: Windows 10.0 Build 19042; UI render: Skia/Raster; VCL: win Locale: ru-RU (ru_RU); UI: en-US Calc: CL -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 143613] Many UI containers seem to use a hard coded black background with the black text of the light colored theme in XFCE.
https://bugs.documentfoundation.org/show_bug.cgi?id=143613 --- Comment #3 from vbh...@vbhunt.net --- (In reply to Екатерина from comment #2) > no repro in Version: 7.3.0.0.alpha0+ (x64) / LibreOffice Community > Build ID: cb2827f5f65324f309fa0e3c30d0b19ad237410e > CPU threads: 8; OS: Windows 10.0 Build 19042; UI render: Skia/Raster; VCL: > win > Locale: ru-RU (ru_RU); UI: en-US > Calc: CL I couldn't reproduce the problem on any Windows version. From my original report: "This seems to only affect the Linux version." Thus, if you're trying to debug this problem in Windows, you will fail miserably as it doesn't happen in Windows. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 65353] FILESAVE: LibreOffice embeds fonts defined in styles (e.g. CJK and CTL fonts) but arent used in the document
https://bugs.documentfoundation.org/show_bug.cgi?id=65353 --- Comment #47 from Brenton Chapin --- The font embedding is all over the place. I've been using "embed fonts...", "only embed fonts that are used...", and leaving all the font scripts options unchecked, and it's a bit random what fonts are embedded. Extra fonts are embedded, and some fonts actually used are sometimes omitted. I upgraded from 7.1.1.2 to 7.2.0.4, and that helped, but it's still wonky. I am on Ubuntu 18.04. I have a document that uses Arimo and Allegreya Sans (from fonts.google.com). The default font is Liberation Sans, however the document doesn't use that font anywhere. I added some text using yet another font, Ubuntu, then changed it to Allegreya Sans. There is nothing in Ubuntu font left in the document, anywhere, as far as I can tell, but ever since I used it, Ubuntu is added to the save file. Liberation Sans may also end up in the save file. Without fonts, the file is 30k. With embedded fonts, I have seen sizes of 800k, 1.7M, 2M, 2.1M, and 3M. When Liberation Sans gets added back into the fonts LibreOffice decides to embed, I can get rid of that one by saving the file without embedded fonts, quitting LibreOffice, starting LibreOffice, loading the file without the embedded fonts, turning on the embed fonts option, and saving. That gets rid of Liberation Sans, but Ubuntu is still in there. If I make any edit at all, then save again, Liberation Sans will be shoved in again. I tried a direct approach of simply using an archiver (7-zip) to remove the Ubuntu fonts from the odt file, but that corrupted it. I also fiddled with the Paragraph Style: Default Paragraph Style, changing the default font from Liberation Sans to Arimo. That made it worse-- Arimo was left out, and Liberation Sans put in. One final note about embedding fonts: it doesn't work for the text entry fields of PDF forms either. If you add a Text Box, set the font to something custom, and export to PDF, the text entry field in the PDF form will not use the font you chose, it will use the default font of Helvetica. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 76115] FILEOPEN: Calc can't read generated XLSX without docProps folder - opens if extracted and rezipped
https://bugs.documentfoundation.org/show_bug.cgi?id=76115 --- Comment #16 from Volga --- (In reply to Caolán McNamara from comment #9) > The problem is that the zip has "\" instead of "/" as the separators. This could be fixed via integrating even more powerful library to parse the zip format. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 143613] Many UI containers seem to use a hard coded black background with the black text of the light colored theme in XFCE.
https://bugs.documentfoundation.org/show_bug.cgi?id=143613 --- Comment #2 from Екатерина --- no repro in Version: 7.3.0.0.alpha0+ (x64) / LibreOffice Community Build ID: cb2827f5f65324f309fa0e3c30d0b19ad237410e CPU threads: 8; OS: Windows 10.0 Build 19042; UI render: Skia/Raster; VCL: win Locale: ru-RU (ru_RU); UI: en-US Calc: CL -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 143980] New: Add numpy to LibreOffice\program\python
https://bugs.documentfoundation.org/show_bug.cgi?id=143980 Bug ID: 143980 Summary: Add numpy to LibreOffice\program\python Product: LibreOffice Version: 7.2.0.4 release Hardware: All OS: All Status: UNCONFIRMED Severity: enhancement Priority: medium Component: Calc Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: e...@helpidea.net Description: Calc is a container of Tables, and from DataArray, is a container of Arrays. I noticed that numpy is a very powerful and great manager of Arrays, and useful for many math activites. Why don't add numpy python library to LibreOffice? Actual Results: Now the numpy python library is missing Expected Results: Add the numpy python library to LibreOffice Reproducible: Always User Profile Reset: No Additional Info: Add the numpy python library to LibreOffice -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 143979] New: FORMATTING: Date format is mangled when file is closed and reopened
https://bugs.documentfoundation.org/show_bug.cgi?id=143979 Bug ID: 143979 Summary: FORMATTING: Date format is mangled when file is closed and reopened Product: LibreOffice Version: 7.1.4.2 release Hardware: x86-64 (AMD64) OS: Mac OS X (All) Status: UNCONFIRMED Severity: normal Priority: medium Component: Calc Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: m...@shadsterling.com Description: I habitually format date cells as `-MM""MMM-DDNN` (where the `""` acts as a separator between `MM` and `MMM`), so today appears as `2021-08Aug-20Fri` In some files, every time I close and reopen the file the date cell formats have reverted to `-M-DDNN` (where `M` is expanded to the first letter of `MMM`), so today appears as `2021-A-20Fri` The format it saved with also does not appear in the list of formats in the Format Cells dialog Steps to Reproduce: 1. Format some dates with `-MM""MMM-DDNN` 2. Save and close 3. Reopen For some files it does it every time, for other files it never does it, I have no idea what the difference is Actual Results: All my dates got reformatted Expected Results: All my formats should be preserved Reproducible: Always User Profile Reset: No Additional Info: Version: 7.1.4.2 / LibreOffice Community Build ID: a529a4fab45b75fefc5b6226684193eb000654f6 CPU threads: 16; OS: Mac OS X 10.16; UI render: default; VCL: osx Locale: en-US (en_US.UTF-8); UI: en-US Calc: threaded -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 143976] Can't enter in Calc numbers consisting of more than 16 digits
https://bugs.documentfoundation.org/show_bug.cgi?id=143976 Eike Rathke changed: What|Removed |Added Status|RESOLVED|CLOSED -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 143976] Can't enter in Calc numbers consisting of more than 16 digits
https://bugs.documentfoundation.org/show_bug.cgi?id=143976 Eike Rathke changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |NOTABUG --- Comment #3 from Eike Rathke --- Numeric input is converted to IEEE 754 double binary floating point numbers. They can not hold more than 14-16 decimal digits. For numeric identifiers use text input instead, either by assigning the Text number format to the cell prior to input, or by preceding the input with an ' apostrophe single quote, like '11 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 143978] New: Calc: shrink to fit
https://bugs.documentfoundation.org/show_bug.cgi?id=143978 Bug ID: 143978 Summary: Calc: shrink to fit Product: LibreOffice Version: 7.2.0.4 release Hardware: x86-64 (AMD64) OS: Windows (All) Status: UNCONFIRMED Severity: normal Priority: medium Component: Calc Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: brijesh.da...@gmail.com Description: LibreOffice 7.2 Calc: a cell with shrink to fit - too much shrink the content if it is not fit. Steps to Reproduce: 1.right click on a cell or select a cell and go to format>Cells.. 2.select alignment tab 3.check "shrink to fit" 4.enter content that can not fit in the cell Actual Results: when we enter content that can not fit in the cell it should shrink gradually but it shrink too much. Expected Results: when we enter content that can not fit in the cell it should shrink gradually but it shrink too much. Reproducible: Always User Profile Reset: No Additional Info: when we enter content that can not fit in the cell it should shrink gradually but it shrink too much. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 143977] New: In “View” menus and "Tabbed" toolbars, be consistent about “hide / show”
https://bugs.documentfoundation.org/show_bug.cgi?id=143977 Bug ID: 143977 Summary: In “View” menus and "Tabbed" toolbars, be consistent about “hide / show” Product: LibreOffice Version: unspecified Hardware: All OS: Linux (All) Status: UNCONFIRMED Severity: enhancement Priority: medium Component: Writer Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: j.a.sw...@gmail.com Description: In the “View” menus, we have various items to be viewed or not: • Status bar • Formatting marks • Text boundaries And so on. Tick the box, and the canvas will show the item. Untick it and the canvas hides it. But at least two items depart from this convention. We have: • Show Whitespace • Show Tracked Changes To be consistent, these items should simply be: • Whitespace • Tracked Changes And to keep the present defaults, “Whitespace” should be ticked by default, “Tracked changes” unticked. This change will make the menus more consistent—and easier for the eye to scan. The same applies to toolbars. In the “Tabbed” and “Tabbed Compact” user interfaces, “Show Whitespace” should just be “Whitespace.” Steps to Reproduce: 1. Where available, click the "View" dropdown menu or 1. Switch to "Tabbed" or "Tabbed Compact" interface. 2. Click view. 3. See the toolbar. Actual Results: Displays: "Show Whitespace" and "Show Tracked Changes" Expected Results: Display: "Whitespace" and "Tracked Changes" Reproducible: Always User Profile Reset: Yes Additional Info: Version: 7.1.5.2 / LibreOffice Community Build ID: 85f04e9f809797b8199d13c421bd8a2b025d52b5 CPU threads: 4; OS: Linux 5.4; UI render: default; VCL: gtk3 Locale: en-US (en_US.UTF-8); UI: en-US Flatpak Calc: threaded -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-commits] core.git: Branch 'feature/cib_contract891c' - vcl/source
vcl/source/gdi/pdfwriter_impl.cxx | 11 +++
1 file changed, 11 insertions(+)
New commits:
commit 2f4ed9f048b904f1228c58a20d4f4bcfb87294fd
Author: Armin Le Grand (Allotropia)
AuthorDate: Fri Aug 20 17:51:14 2021 +0200
Commit: Armin Le Grand (Allotropia)
CommitDate: Fri Aug 20 17:51:14 2021 +0200
AKDB-465: Correct usage of aCodeUnitsPerGlyph
aCodeUnitsPerGlyph needs to be reset together with
aCodeUnits, else if e.g. two code units for an already
created glyph exists at the beginning that will by
error be reused throughout the conversion of the
given rText. Exactly that creates the described
error. In the PDF, the /ToUnicode entry was created
wrong due to this error. With this fix the same
/ToUnicode list as in master gets created.
Change-Id: I2feb8b1cb7d3bbaf3372ed369ab3b4b470071d4e
diff --git a/vcl/source/gdi/pdfwriter_impl.cxx
b/vcl/source/gdi/pdfwriter_impl.cxx
index 62f75b8a82ae..19ba5b76c3a3 100644
--- a/vcl/source/gdi/pdfwriter_impl.cxx
+++ b/vcl/source/gdi/pdfwriter_impl.cxx
@@ -8662,6 +8662,17 @@ void PDFWriterImpl::drawLayout( SalLayout& rLayout,
const OUString& rText, bool
while ((nGlyphs = rLayout.GetNextGlyphs(nTmpMaxGlyphs, pGlyphs,
aGNGlyphPos, nIndex, pFallbackFonts)) != 0)
{
aCodeUnits.clear();
+
+// AKDB-465 aCodeUnitsPerGlyph needs to be reset here, too, else the
+// units per glyph from former texts *will* wrongly be reused.
+// Experimented by not using aCodeUnits.data() &
aCodeUnitsPerGlyph.data()
+// for the call to registerGlyphs below directly, but adding a
live-offset
+// to these. That again would make it necessary to also grow aCodeUnits
+// all the time and the offsets would be not the same for both.
+// Went out to be too complicated. AFAIU the simple solution below does
+// not loose needed infos, so go with it. ProoveOfConcept: it works.
+aCodeUnitsPerGlyph.clear();
+
for( int i = 0; i < nGlyphs; i++ )
{
// default case: 1 glyph is one unicode
[Libreoffice-bugs] [Bug 119075] Slow switching sheets back and forth after saving a document with many comments
https://bugs.documentfoundation.org/show_bug.cgi?id=119075 Buovjaga changed: What|Removed |Added Keywords|wantBacktrace |haveBacktrace -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 119075] Slow switching sheets back and forth after saving a document with many comments
https://bugs.documentfoundation.org/show_bug.cgi?id=119075 --- Comment #23 from Buovjaga --- Created attachment 174452 --> https://bugs.documentfoundation.org/attachment.cgi?id=174452=edit Perf flamegraph Took a perf trace of switching a sheet after saving and generated flamegraph. Version: 7.3.0.0.alpha0+ / LibreOffice Community Build ID: 58a5bd793a2ed57077fc598281cc74e16373b877 CPU threads: 8; OS: Linux 5.13; UI render: default; VCL: kf5 (cairo+xcb) Locale: fi-FI (fi_FI.UTF-8); UI: en-US Calc: threaded -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 143961] Impress crashes when inserting a videofile
https://bugs.documentfoundation.org/show_bug.cgi?id=143961 Julien Nabet changed: What|Removed |Added CC|serval2...@yahoo.fr | --- Comment #4 from Julien Nabet --- Thank you for your feedback. On pc Debian x86-64 with master sources updated today, I can't reproduce this. So I can't help here=>uncc myself. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 143974] Basic function CStr is failing to properly convert integers after 41 steps in a for loop
https://bugs.documentfoundation.org/show_bug.cgi?id=143974 --- Comment #2 from Uwe Auer --- Repro in Version: 7.3.0.0.alpha0+ (x64) / LibreOffice Community Build ID: d001836139b28d367cc70b64a13519d173066df1 CPU threads: 1; OS: Windows 10.0 Build 19043; UI render: Skia/Raster; VCL: win Locale: en-US (en_DE); UI: de-DE Calc: threaded -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 143974] Basic function CStr is failing to properly convert integers after 41 steps in a for loop
https://bugs.documentfoundation.org/show_bug.cgi?id=143974 --- Comment #1 from Uwe Auer --- The title of this report mentions "...convert integers..." but obviously variable "i" is not an integer, but a floating point value. Explicitly using "Dim i As Long" prevents the observed behavior to occur, i.e. use modified macro: Sub Main Dim Txt As String Dim i As Long For i = 1 To 50 Txt = Txt + CStr(i) If (i mod 10 = 0) Then Txt = Txt + CHR(10) Else Txt = Txt + ", " End If Next i MsgBox Txt End Sub Not sure, whether variables having no explicit type declaration are correctly assumed to have a floating point type. Hence this is not a statement "bug or not a bug". -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 131130] SLIDESHOW: Images OCCASIONALLY cropped or missing during slideshow presentation
https://bugs.documentfoundation.org/show_bug.cgi?id=131130 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] [Bug 143962] EDITING Address error when move (drag and drop) a range
https://bugs.documentfoundation.org/show_bug.cgi?id=143962 m.a.riosv changed: What|Removed |Added CC||miguelangelrv@libreoffice.o ||rg Status|UNCONFIRMED |NEW Ever confirmed|0 |1 --- Comment #4 from m.a.riosv --- For me a bug, dragging an edge of a range of a formula, must adapt the range to the new position, like it does with an only one cell reference. The bug it's also with cut & paste. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 143976] Can't enter in Calc numbers consisting of more than 16 digits
https://bugs.documentfoundation.org/show_bug.cgi?id=143976 --- Comment #2 from andis.lazd...@gmail.com --- Created attachment 174451 --> https://bugs.documentfoundation.org/attachment.cgi?id=174451=edit Scctreenshot of what I see in attached sample file -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 143976] Can't enter in Calc numbers consisting of more than 16 digits
https://bugs.documentfoundation.org/show_bug.cgi?id=143976 andis.lazd...@gmail.com changed: What|Removed |Added CC||andis.lazd...@gmail.com --- Comment #1 from andis.lazd...@gmail.com --- Created attachment 174450 --> https://bugs.documentfoundation.org/attachment.cgi?id=174450=edit Example demonstrating wrong behaviour of long numbers -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 143976] New: Can't enter in Calc numbers consisting of more than 16 digits
https://bugs.documentfoundation.org/show_bug.cgi?id=143976 Bug ID: 143976 Summary: Can't enter in Calc numbers consisting of more than 16 digits Product: LibreOffice Version: 7.2.0.4 release Hardware: All OS: All Status: UNCONFIRMED Severity: normal Priority: medium Component: Calc Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: andis.lazd...@gmail.com Description: I'm made list of fuel cards and realized that I can't enter any number longer than 16 digits. Fuel card number contains 18 digits. All numbers consisting from more than 16 digits are recognized as scientific decimal number. This behavior is appears in Libreoffice 7.1 and 7.2. Steps to Reproduce: 1.Open empty sheet in calc (example is attached). 2.In any cell, e.g. A1 enter 11 (at least 17 digits) 3.Press Enter and, if necessary, change number format to Number > '-1235' Actual Results: 111000 appears instead of 11 and the number is recognized as large scientific decimal number. Expected Results: 11 appears on a screen and is recognized as number Reproducible: Always User Profile Reset: Yes OpenGL enabled: Yes Additional Info: I tried to change language settings to EN, but it didn't changed the behavior. Version: 7.2.0.4 / LibreOffice Community Build ID: 9a9c6381e3f7a62afc1329bd359cc48accb6435b CPU threads: 8; OS: Linux 5.4; UI render: default; VCL: gtk3 Locale: lv-LV (en_US.UTF-8); UI: en-US Calc: CL -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 140638] Cannot use LibreOffice 7.1.0 via OLE on Windows Server 2016
https://bugs.documentfoundation.org/show_bug.cgi?id=140638 --- Comment #2 from cpohle --- Maybe this is related: We're running an application that calls LO Writer via OLE like this (code from Sybase PowerBuilder): OleControl loc_Object ... loc_Object.ObjectData = loc_Object.InsertClass( "LibreOffice.WriterDocument.1" ).ObjectData loc_Object.Activate( OffSite! ) Up to LO 7.0.6, this works seamlessly. However, since 7.1.x, the application throws a Windows error: Error no. 298, Too many posts were made to a semaphore. Any idea what has changed from 7.0.x to 7.1.x that might cause this error? -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 143955] Copy does not work in LibreOffice Writer 7.2.0.
https://bugs.documentfoundation.org/show_bug.cgi?id=143955 --- Comment #6 from Joël Bissonnette --- I deactivated Experimental Features and now copy works. So I assume something was buggy wth Experimental Features and the new version 7.2.0? -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 107830] [META] DOCX (OOXML) paragraph-related issues
https://bugs.documentfoundation.org/show_bug.cgi?id=107830 Bug 107830 depends on bug 142542, which changed state. Bug 142542 Summary: FILEOPEN DOCX Extra paragraph spacing in direct formatted text (comment #5) https://bugs.documentfoundation.org/show_bug.cgi?id=142542 What|Removed |Added Status|ASSIGNED|RESOLVED Resolution|--- |FIXED -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-commits] core.git: sw/qa writerfilter/source
sw/qa/extras/ooxmlexport/data/tdf142542_cancelledAutospacing.docx |binary
sw/qa/extras/ooxmlexport/ooxmlexport11.cxx| 10 ++
writerfilter/source/dmapper/DomainMapper_Impl.cxx | 36
++
3 files changed, 32 insertions(+), 14 deletions(-)
New commits:
commit f4b80f4e060a68aa35a7ec678d18af989e82f055
Author: Justin Luth
AuthorDate: Wed Aug 4 15:49:07 2021 +0200
Commit: Justin Luth
CommitDate: Fri Aug 20 17:11:39 2021 +0200
tdf#142542 writerfilter: allow para to cancel style autoSpacing
Change-Id: I7535e7574c3ec9a108a810ba3209074d01aa96f3
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/120275
Tested-by: Jenkins
Reviewed-by: Justin Luth
diff --git a/sw/qa/extras/ooxmlexport/data/tdf142542_cancelledAutospacing.docx
b/sw/qa/extras/ooxmlexport/data/tdf142542_cancelledAutospacing.docx
new file mode 100644
index ..615799fd7565
Binary files /dev/null and
b/sw/qa/extras/ooxmlexport/data/tdf142542_cancelledAutospacing.docx differ
diff --git a/sw/qa/extras/ooxmlexport/ooxmlexport11.cxx
b/sw/qa/extras/ooxmlexport/ooxmlexport11.cxx
index 92a841b826f8..de3eea4c0659 100644
--- a/sw/qa/extras/ooxmlexport/ooxmlexport11.cxx
+++ b/sw/qa/extras/ooxmlexport/ooxmlexport11.cxx
@@ -546,12 +546,22 @@
DECLARE_OOXMLEXPORT_TEST(testTdf113258_noBeforeAutospacing, "tdf113258_noBeforeA
getProperty(xShape->getStart(),
"ParaTopMargin"));
}
+DECLARE_OOXMLEXPORT_TEST(testTdf142542_cancelledAutospacing,
"tdf142542_cancelledAutospacing.docx")
+{
+//Direct formatting disabling autoSpacing must override paragraph-style's
autoSpacing.
+CPPUNIT_ASSERT_EQUAL(static_cast(0),
getProperty(getParagraph(1), "ParaTopMargin"));
+CPPUNIT_ASSERT_EQUAL(static_cast(0),
getProperty(getParagraph(1), "ParaBottomMargin"));
+}
+
DECLARE_OOXMLEXPORT_EXPORTONLY_TEST(testTdf137655, "tdf137655.docx")
{
xmlDocUniquePtr pXmlDoc = parseExport("word/document.xml");
// These were 280.
assertXPath(pXmlDoc,
"/w:document/w:body/w:tbl/w:tr[2]/w:tc[1]/w:p[1]/w:pPr/w:spacing", "before",
"0");
assertXPath(pXmlDoc,
"/w:document/w:body/w:tbl/w:tr[2]/w:tc[2]/w:p[1]/w:pPr/w:spacing", "before",
"0");
+
+//tdf#142542: ensure that the original beforeAutospacing = 0 is not
changed.
+assertXPath(pXmlDoc,
"/w:document/w:body/w:tbl/w:tr[2]/w:tc[1]/w:p[1]/w:pPr/w:spacing",
"beforeAutospacing", "0");
}
DECLARE_OOXMLEXPORT_TEST(testTdf120511_eatenSection,
"tdf120511_eatenSection.docx")
diff --git a/writerfilter/source/dmapper/DomainMapper_Impl.cxx
b/writerfilter/source/dmapper/DomainMapper_Impl.cxx
index 9dedab0ba7da..8fffee9d32e4 100644
--- a/writerfilter/source/dmapper/DomainMapper_Impl.cxx
+++ b/writerfilter/source/dmapper/DomainMapper_Impl.cxx
@@ -1685,7 +1685,6 @@ void DomainMapper_Impl::finishParagraph( const
PropertyMapPtr& pPropertyMap, con
const bool bAllowAdjustments =
!GetSettingsTable()->GetDoNotUseHTMLParagraphAutoSpacing();
sal_Int32 nBeforeAutospacing = -1;
bool bIsAutoSet = pParaContext &&
pParaContext->isSet(PROP_PARA_TOP_MARGIN_BEFORE_AUTO_SPACING);
-bool bIsZeroAutospacingWithoutTopmargin = false;
const bool bNoTopmargin = pParaContext &&
!pParaContext->isSet(PROP_PARA_TOP_MARGIN);
// apply INHERITED autospacing only if top margin is not set
if ( bIsAutoSet || bNoTopmargin )
@@ -1695,44 +1694,53 @@ void DomainMapper_Impl::finishParagraph( const
PropertyMapPtr& pPropertyMap, con
// (see default_spacing = -1 in processing of
LN_CT_Spacing_beforeAutospacing)
if ( bNoTopmargin && nBeforeAutospacing ==
ConversionHelper::convertTwipToMM100(-1) )
{
-nBeforeAutospacing = 0;
-bIsZeroAutospacingWithoutTopmargin = true;
+sal_Int32 nStyleAuto = -1;
+
GetPropertyFromParaStyleSheet(PROP_PARA_TOP_MARGIN_BEFORE_AUTO_SPACING) >>=
nStyleAuto;
+if (nStyleAuto > 0)
+nBeforeAutospacing = 0;
}
}
if ( nBeforeAutospacing > -1 && pParaContext )
{
-if ( bAllowAdjustments && !bIsZeroAutospacingWithoutTopmargin )
+if (bAllowAdjustments)
{
if ( GetIsFirstParagraphInShape() ||
(GetIsFirstParagraphInSection() && GetSectionContext() &&
GetSectionContext()->IsFirstSection()) ||
(m_bFirstParagraphInCell && m_nTableDepth > 0 &&
m_nTableDepth == m_nTableCellDepth) )
{
-nBeforeAutospacing = 0;
// export requires grabbag to match top_margin, so keep them
in sync
-if ( bIsAutoSet )
+if (nBeforeAutospacing && bIsAutoSet)
pParaContext->Insert(
PROP_PARA_TOP_MARGIN_BEFORE_AUTO_SPACING, uno::makeAny( sal_Int32(0) ),true,
PARA_GRAB_BAG );
+nBeforeAutospacing = 0;
}
}
-if ( !bIsZeroAutospacingWithoutTopmargin || (m_nTableDepth > 0 &&
[Libreoffice-commits] core.git: helpcontent2
helpcontent2 |2 +- 1 file changed, 1 insertion(+), 1 deletion(-) New commits: commit d7cb5461bf71a267a754f5c7dcb0d4bfc70ee844 Author: Alain Romedenne AuthorDate: Fri Aug 20 16:54:55 2021 +0200 Commit: Gerrit Code Review CommitDate: Fri Aug 20 16:54:55 2021 +0200 Update git submodules * Update helpcontent2 from branch 'master' to 374e66c1c0353e0042a70ae67d663ccb084fb39a - ScriptForge - (SF_UI) CreateBaseDocument() new CalcFileName argument Change-Id: I1f7005c6eb51ee9323dd2ad960c50031dfb62cf0 Reviewed-on: https://gerrit.libreoffice.org/c/help/+/120642 Tested-by: Jenkins Reviewed-by: Jean-Pierre Ledure diff --git a/helpcontent2 b/helpcontent2 index dd88f0407623..374e66c1c035 16 --- a/helpcontent2 +++ b/helpcontent2 @@ -1 +1 @@ -Subproject commit dd88f0407623a3c075727254abe5c93a88a5dedb +Subproject commit 374e66c1c0353e0042a70ae67d663ccb084fb39a
[Libreoffice-commits] help.git: source/text
source/text/sbasic/shared/03/sf_ui.xhp | 11 ---
1 file changed, 8 insertions(+), 3 deletions(-)
New commits:
commit 374e66c1c0353e0042a70ae67d663ccb084fb39a
Author: Alain Romedenne
AuthorDate: Thu Aug 19 09:42:36 2021 +0200
Commit: Jean-Pierre Ledure
CommitDate: Fri Aug 20 16:54:55 2021 +0200
ScriptForge - (SF_UI) CreateBaseDocument() new CalcFileName argument
Change-Id: I1f7005c6eb51ee9323dd2ad960c50031dfb62cf0
Reviewed-on: https://gerrit.libreoffice.org/c/help/+/120642
Tested-by: Jenkins
Reviewed-by: Jean-Pierre Ledure
diff --git a/source/text/sbasic/shared/03/sf_ui.xhp
b/source/text/sbasic/shared/03/sf_ui.xhp
index c56a754bf..b3c1443f8 100644
--- a/source/text/sbasic/shared/03/sf_ui.xhp
+++ b/source/text/sbasic/shared/03/sf_ui.xhp
@@ -267,21 +267,26 @@
Creates and stores a
new %PRODUCTNAME Base document embedding an empty database of the given type.
The method returns a Document service instance.
- svc.CreateBaseDocument(filename: str, embeddeddatabase: str =
'HSQLDB', registrationname: str = ''): svc
+ svc.CreateBaseDocument(filename: str, embeddeddatabase: str =
'HSQLDB', registrationname: str = '', opt calcfilename: str): svc
filename : Identifies the file to
create. It must follow the SF_FileSystem.FileNaming
notation. If the file already exists, it is overwritten without
warning
- embeddeddatabase : Either "HSQLDB" (default) or
"FIREBIRD".
+ embeddeddatabase : Either "HSQLDB" (default),
"FIREBIRD" or "CALC".
registrationname : The name used to store the new
database in the databases register. When = "" (default), no registration takes
place. If the name already exists it is overwritten without warning.
+ calcfilename : Only when
embeddeddatabase = "CALC", calcfilename
represents the file containing the tables as Calc sheets. The file must exist
or an error is raised.
- Dim myBase As Object
+ Dim myBase As Object, myCalcBase As
Object
Set myBase =
ui.CreateBaseDocument("C:\Databases\MyBaseFile.odb", "FIREBIRD")
+ Set
myCalcBase = ui.CreateBaseDocument("C:\Databases\MyCalcBaseFile.odb",
_
+
"CALC", , "C:\Databases\MyCalcFile.ods")
myBase =
svcUI.CreateBaseDocument(r"C:\Databases\MyBaseFile.odb", "FIREBIRD")
+ myCalcBase =
svcUI.CreateBaseDocument(r"C:\Databases\MyCalcBaseFile.odb", \
+
"CALC", calcfilename = r"C:\Databases\MyCalcFile.ods")
[Libreoffice-bugs] [Bug 143961] Impress crashes when inserting a videofile
https://bugs.documentfoundation.org/show_bug.cgi?id=143961 --- Comment #3 from 7a4131b4-fa6b-4bb2-835b-b150b7e2e...@123test.anonaddy.com --- Impress is crashing no matter which video file or format (tested with mp4 und mpg) is used. In addition all LibreOffice applications are crashing when inserting a video. I am using the .deb Version of LibreOffice -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 143961] Impress crashes when inserting a videofile
https://bugs.documentfoundation.org/show_bug.cgi?id=143961 --- Comment #2 from 7a4131b4-fa6b-4bb2-835b-b150b7e2e...@123test.anonaddy.com --- Created attachment 174449 --> https://bugs.documentfoundation.org/attachment.cgi?id=174449=edit terminal output of Impress crashing This is the terminal output when launching impress via the command line and then inserting a video file. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 129672] Export pdf: Error message in Adobe Reader "Cannot extract the embedded font 'BAAAAA+ LiberationSerif'" for unicode characters
https://bugs.documentfoundation.org/show_bug.cgi?id=129672 --- Comment #10 from Timur --- I cannot reproduce anymore with old LO, so no point in testing new LO. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 82984] FILEOPEN: Error opening XLSX file in zip64 format
https://bugs.documentfoundation.org/show_bug.cgi?id=82984 --- Comment #14 from dongshili --- When will this BUG be solved? -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 127031] Base report builder time formatting issue
https://bugs.documentfoundation.org/show_bug.cgi?id=127031 --- Comment #4 from Robert Großkopf --- Bug still the same in LO 7.2.0.3 on OpenSUSE 15.2 64bit rpm Linux. Filed, which is formatted as [HH]:MM:SS is shown as "#FMT". Accumulated time won't be shown right. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 129672] Export pdf: Error message in Adobe Reader "Cannot extract the embedded font 'BAAAAA+ LiberationSerif'" for unicode characters
https://bugs.documentfoundation.org/show_bug.cgi?id=129672 Timur changed: What|Removed |Added See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=14 ||3959 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 143959] PDF import do not take embedded fonts
https://bugs.documentfoundation.org/show_bug.cgi?id=143959 Timur changed: What|Removed |Added Priority|medium |low Severity|normal |minor Resolution|DUPLICATE |--- CC||suokunl...@126.com Keywords||bibisected, bisected See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=12 ||9672 Status|RESOLVED|UNCONFIRMED --- Comment #7 from Timur --- "TimesNewRoman" italic is also not a good font. But let's go for a change in 7.2: commit 78d231e25e0984a98622cfc5da7ec26677cd75c2 Date: Fri Jul 23 15:34:36 2021 +0200 source sha:0ebe806d011b7084b49dd038f3521a03bc935f8c pre sha:4b5dd477bbe1647c6c60374da2e4cabcf5b6b58b commit 0ebe806d011b7084b49dd038f3521a03bc935f8c[log] author Kevin Suo Sat Jul 17 14:25:45 2021 +0800 committer Adolfo Jayme Barrientos Fri Jul 23 14:53:03 2021 +0200 treee6c0e7aaf2507607709759464b3f991b6679b6c0 parent 4b5dd477bbe1647c6c60374da2e4cabcf5b6b58b [diff] sdext.pdfimport: Restore to read font file for the determination... of font attributes, as suggested by Mike Kaganski in https://gerrit.libreoffice.org/c/core/+/118977 This partially reverts da59686672fd2bc98f8cb28d5f04dc978b50ac13 but did some modification of the previous code with some explanationary comments. HI Kevin, please see this. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 131130] SLIDESHOW: Images OCCASIONALLY cropped or missing during slideshow presentation
https://bugs.documentfoundation.org/show_bug.cgi?id=131130 --- Comment #12 from Gerson --- I've downloaded and tested Michele's presentation and it worked fine, no glitches. But that's the point. The bug is intermittent. It happens pretty much in all my Impress files, but not always. Sometimes I use an Impress file to give a talk or class it all goes well. Then some time later I use the same file again and there's glitches. When this happens, I close LibreOffice, open it again, and the presentation runs smoothly with no glitches. Currently I'm recording my classes, but I've been using PDFs to avoid these glitches. But I'll start using Impress now to see if we get "lucky" and a glitch may happen during a recorded class. PS: could it be that it only happens with physicists working on graphene? ;-) -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 103182] [META] GTK3-specific bugs
https://bugs.documentfoundation.org/show_bug.cgi?id=103182 Bug 103182 depends on bug 142394, which changed state. Bug 142394 Summary: Slow drawing of semi-transparent large color object https://bugs.documentfoundation.org/show_bug.cgi?id=142394 What|Removed |Added Status|NEW |RESOLVED Resolution|--- |FIXED -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 142394] Slow drawing of semi-transparent large color object
https://bugs.documentfoundation.org/show_bug.cgi?id=142394 Caolán McNamara changed: What|Removed |Added Assignee|libreoffice-b...@lists.free |caol...@redhat.com |desktop.org | Status|NEW |RESOLVED Resolution|--- |FIXED --- Comment #4 from Caolán McNamara --- dunno if performance can ever be said to be fixed but that presumably resolves the regression find, backport to 7-2 in gerrit -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 142394] Slow drawing of semi-transparent large color object
https://bugs.documentfoundation.org/show_bug.cgi?id=142394 --- Comment #3 from Commit Notification --- Caolán McNamara committed a patch related to this issue. It has been pushed to "master": https://git.libreoffice.org/core/commit/1727fe82330dcf67eeece4eacfd4907f85714b0f tdf#142394 return to using CAIRO_OPERATOR_SOURCE in drawBitmap It will be available in 7.3.0. The patch should be included in the daily builds available at https://dev-builds.libreoffice.org/daily/ in the next 24-48 hours. More information about daily builds can be found at: https://wiki.documentfoundation.org/Testing_Daily_Builds Affected users are encouraged to test the fix and report feedback. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 142394] Slow drawing of semi-transparent large color object
https://bugs.documentfoundation.org/show_bug.cgi?id=142394 Commit Notification changed: What|Removed |Added Whiteboard||target:7.3.0 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-commits] core.git: vcl/headless
vcl/headless/svpgdi.cxx |5 + 1 file changed, 5 insertions(+) New commits: commit 1727fe82330dcf67eeece4eacfd4907f85714b0f Author: Caolán McNamara AuthorDate: Thu Aug 19 13:01:33 2021 +0100 Commit: Caolán McNamara CommitDate: Fri Aug 20 16:32:40 2021 +0200 tdf#142394 return to using CAIRO_OPERATOR_SOURCE in drawBitmap since commit cd09fc9451897e6efedbf9f5e1d5b9bd96e65cb5 Date: Mon Mar 22 19:06:15 2021 +0100 do not enable mbSupportsBitmap32 for headless (tdf#141171) turned back off the mbSupportsBitmap32 support experiemented with in commit 86ea64f216819696cd86d1926aff0a138ace2baf Date: Fri Feb 15 13:14:32 2019 +0100 Support for native 32bit Bitmap in VCL and SVP (cairo) backend Change-Id: I818c3f11d0334278a65a0e45b61141327669121d Reviewed-on: https://gerrit.libreoffice.org/c/core/+/120709 Reviewed-by: Caolán McNamara Tested-by: Jenkins diff --git a/vcl/headless/svpgdi.cxx b/vcl/headless/svpgdi.cxx index 926ef9fe1f6d..2a5d1ba350ad 100644 --- a/vcl/headless/svpgdi.cxx +++ b/vcl/headless/svpgdi.cxx @@ -2168,7 +2168,12 @@ void SvpSalGraphics::drawBitmap(const SalTwoRect& rTR, const SalBitmap& rSourceB return; } +#if 0 // LO code is not yet bitmap32-ready. + // if m_bSupportsBitmap32 becomes trye for Svp revisit this copyWithOperator(rTR, source, CAIRO_OPERATOR_OVER); +#else +copyWithOperator(rTR, source, CAIRO_OPERATOR_SOURCE); +#endif } void SvpSalGraphics::drawBitmap(const SalTwoRect& rTR, const BitmapBuffer* pBuffer, cairo_operator_t eOp)
