[Libreoffice-bugs] [Bug 105948] [META] Undo/Redo bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=105948 Aron Budea changed: What|Removed |Added Depends on||149173 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=149173 [Bug 149173] Crash BigPtrEntry::GetArray(this=0x61726940) const at bparr.hxx:106:23 (STR: comment 3) -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 149173] Crash BigPtrEntry::GetArray(this=0x0000600001726940) const at bparr.hxx:106:23 (STR: comment 3)
https://bugs.documentfoundation.org/show_bug.cgi?id=149173 Aron Budea changed: What|Removed |Added Keywords|bibisectRequest |bibisected, bisected CC||aron.bu...@gmail.com, ||bakos.attilakar...@nisz.hu Regression By||Attila Bakos (NISZ) Blocks||105948 See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=14 ||3574 --- Comment #9 from Aron Budea --- Bibsected using steps from comment 3 to the following commit using repo bibisect-linux-64-7.4. Adding CC: to Attila Bakos (NISZ). https://cgit.freedesktop.org/libreoffice/core/commit/?id=2951cbdf3a6e2b62461665546b47e1d253fcb834 author Attila Bakos (NISZ) 2021-11-10 14:10:11 +0100 committer László Németh2022-01-03 14:28:15 +0100 tdf#143574 OOXML export/import of textboxes in group shapes Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=105948 [Bug 105948] [META] Undo/Redo bugs and enhancements -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 149591] WORD COMPLETION: Make it visible, if there is more than one option for word completion
https://bugs.documentfoundation.org/show_bug.cgi?id=149591 --- Comment #3 from Heiko Tietze --- (In reply to Dieter from comment #2) > This would replace Ctrl+tab, correct? (Shift+) Ctrl+Tab is the default to jump from one tab to another in a tabview. Not so good decision to use it for invisible text alternatives. So yes. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 149459] [FORMATTING] Tab key do not select shapes by turn if they are copy-pasted and moved by arrow key
https://bugs.documentfoundation.org/show_bug.cgi?id=149459 Dieter changed: What|Removed |Added Status|UNCONFIRMED |NEW CC||dgp-m...@gmx.de Summary|[FORMATTING] Tab key do not |[FORMATTING] Tab key do not |select shapes by turn if|select shapes by turn if |they are copy-pasted|they are copy-pasted and ||moved by arrow key Blocks||108741 Severity|normal |minor Ever confirmed|0 |1 --- Comment #2 from Dieter --- I confirm it with Version: 7.3.4.2 (x64) / LibreOffice Community Build ID: 728fec16bd5f605073805c3c9e7c4212a0120dc5 CPU threads: 4; OS: Windows 10.0 Build 19044; UI render: default; VCL: win Locale: de-DE (de_DE); UI: de-DE Calc: threaded Additional information It works as expected if you move lines with touchpad and not with arrow key Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=108741 [Bug 108741] [META] Shapes bugs and enhancements -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 108741] [META] Shapes bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=108741 Dieter changed: What|Removed |Added Depends on||149459 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=149459 [Bug 149459] [FORMATTING] Tab key do not select shapes by turn if they are copy-pasted and moved by arrow key -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 81639] FORMATTING: Frame style position is not assignable to paragraph area
https://bugs.documentfoundation.org/show_bug.cgi?id=81639 Dieter changed: What|Removed |Added See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=14 ||9452 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 149452] "Update selected style" doesn't set frame style's anchor type to match selected object
https://bugs.documentfoundation.org/show_bug.cgi?id=149452 Dieter changed: What|Removed |Added Status|UNCONFIRMED |NEW CC||dgp-m...@gmx.de Blocks||108357 Ever confirmed|0 |1 Whiteboard| QA:needsComment| See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=81 ||639 --- Comment #1 from Dieter --- I confirm it with Version: 7.3.4.2 (x64) / LibreOffice Community Build ID: 728fec16bd5f605073805c3c9e7c4212a0120dc5 CPU threads: 4; OS: Windows 10.0 Build 19044; UI render: Skia/Raster; VCL: win Locale: de-DE (de_DE); UI: en-GB Calc: CL At least related to bug 81639 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=108357 [Bug 108357] [META] Writer frame/image/OLE style bugs and enhancements -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 108357] [META] Writer frame/image/OLE style bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=108357 Dieter changed: What|Removed |Added Depends on||149452 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=149452 [Bug 149452] "Update selected style" doesn't set frame style's anchor type to match selected object -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 134759] Tracking changes items appear while not being shown at all
https://bugs.documentfoundation.org/show_bug.cgi?id=134759 Aron Budea changed: What|Removed |Added CC||aron.bu...@gmail.com Keywords|bibisectRequest |bibisectNotNeeded -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 149319] In Draw and Writer, F1 (Help) on "Optimize" in Table bar does not have a linked help page
https://bugs.documentfoundation.org/show_bug.cgi?id=149319 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 149452] "Update selected style" doesn't set frame style's anchor type to match selected object
https://bugs.documentfoundation.org/show_bug.cgi?id=149452 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 149449] CSS class redefinition gets ignored inside SVGs
https://bugs.documentfoundation.org/show_bug.cgi?id=149449 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 149448] Line spacing
https://bugs.documentfoundation.org/show_bug.cgi?id=149448 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 142662] Crash in: mergedlo.dll
https://bugs.documentfoundation.org/show_bug.cgi?id=142662 --- Comment #6 from QA Administrators --- Dear reelix, 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 142575] Libreoffice impress right-ckeck menu disappears
https://bugs.documentfoundation.org/show_bug.cgi?id=142575 --- Comment #3 from QA Administrators --- Dear skane, 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 70624] index order depend on the screen zoom and on chapter position
https://bugs.documentfoundation.org/show_bug.cgi?id=70624 --- Comment #17 from QA Administrators --- Dear gioni, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 48645] FORMATTING: alignr, alignl operators distort fraction representation
https://bugs.documentfoundation.org/show_bug.cgi?id=48645 --- Comment #13 from QA Administrators --- Dear Yakov, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 48892] EDITING: AutoCorrect treatment of closing quote in proximity to en dash / em dash
https://bugs.documentfoundation.org/show_bug.cgi?id=48892 --- Comment #17 from QA Administrators --- Dear Patrick Gillespie, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 127009] "Selection" property is empty when selecting a slide in Slides pane using PyUNO
https://bugs.documentfoundation.org/show_bug.cgi?id=127009 --- Comment #8 from QA Administrators --- Dear Konstantin Kharlamov, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 105948] [META] Undo/Redo bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=105948 Aron Budea changed: What|Removed |Added Depends on||148522 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=148522 [Bug 148522] Undo line color changes aligns text centered (and doesn't undo the line color) -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 148522] Undo line color changes aligns text centered (and doesn't undo the line color)
https://bugs.documentfoundation.org/show_bug.cgi?id=148522 Aron Budea changed: What|Removed |Added See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=12 ||9961 Whiteboard| QA:needsComment| Blocks||105948, 100366 Ever confirmed|0 |1 Keywords|bibisectRequest |bibisected, bisected Version|7.4.0.0 alpha0+ |7.2.0.4 release Status|UNCONFIRMED |NEW Regression By||Miklos Vajna CC||aron.bu...@gmail.com, ||vmik...@collabora.com --- Comment #2 from Aron Budea --- Reproducted using LO 7.4.0.0.beta1+ (cdf48e57da6b8a6a5eb4131340fa2c14be135714) / Ubuntu. It's also a regression, and started going bad with the following commit, bibisected using repo bibisect-linux-64-7.2. Adding CC: to Miklos Vajna. https://cgit.freedesktop.org/libreoffice/core/commit/?id=fdeb04f7c59cf8032fe17072ed779e70505cc6ab author Miklos Vajna 2020-12-15 17:17:56 +0100 committer Miklos Vajna 2020-12-15 22:41:14 +0100 tdf#129961 svx: finish UI for table shadow as direct format Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=100366 [Bug 100366] [META] Impress/Draw table bugs and enhancements https://bugs.documentfoundation.org/show_bug.cgi?id=105948 [Bug 105948] [META] Undo/Redo bugs and enhancements -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 100366] [META] Impress/Draw table bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=100366 Aron Budea changed: What|Removed |Added Depends on||148522 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=148522 [Bug 148522] Undo line color changes aligns text centered (and doesn't undo the line color) -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 149613] New: Selecting the Japanese currency [JPY ￥ Japanese] from the drop-down of the currency icon, it will be Jordan's currency.
https://bugs.documentfoundation.org/show_bug.cgi?id=149613 Bug ID: 149613 Summary: Selecting the Japanese currency [JPY ￥ Japanese] from the drop-down of the currency icon, it will be Jordan's currency. Product: LibreOffice Version: 7.3.0.3 release Hardware: All OS: All Status: UNCONFIRMED Severity: normal Priority: medium Component: Calc Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: tac...@hotmail.co.jp Description: Selecting the Japanese currency [JPY ￥ Japanese] from the drop-down of the currency icon, it will be Jordan's currency. Steps to Reproduce: 1. Enter the number 1234 in Cell [A1] 2. Select Cell [A1] 3. Select [JPY ￥ 日本語] from the dropdown of the currency icon. or Select [JPY ￥ Japanese] (I don't know how it is written in each country.) Actual Results: Cell [A1] : د.أ. 1,234.-- It is Jordan's currency. Expected Results: Cell [A1] : ￥ 1,234 Reproducible: Always User Profile Reset: No Additional Info: Selecting The standard format in each country at the top row is correctly [¥ 1,234]. Selecting [JPY] located at the bottom will be [1,234 JPY] correctly. Selecting [JPY ￥ Japanese] from the cell format setting, it will be [￥ 1,234] correctly. The problem is only [JPY ￥ Japanese] in the middle of the currency icon drop-down. There is no problem with Ver 7.2.1.2 There seems to be a problem after Ver7.3 Reproduce with Ver 7.3.0.3 Reproduce with Latest Ver 7.4.0.0.beta1 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 149612] New: LibreOffice Writer stops working after 15-120 minutes
https://bugs.documentfoundation.org/show_bug.cgi?id=149612 Bug ID: 149612 Summary: LibreOffice Writer stops working after 15-120 minutes Product: LibreOffice Version: 7.3.3.2 release Hardware: All OS: macOS (All) Status: UNCONFIRMED Severity: normal Priority: medium Component: Writer Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: lane...@gmail.com Description: When working in Writer it stops working completely after anywhere from 15 minutes to 2 hours of work. I typically work from 4 Writer files simultaneously, which I fear might contribute to the problem. Steps to Reproduce: 1.Pull up 4 LibreOffice Writer files in separate windows and work in all of them 2.Wait for Writer to stop working 3. Actual Results: After an average of about 45 minutes of working in Writer, it gives up and refuses to work any more. (I've seen it quit in as little as 5 minutes and as much as 2 hours.) I have to quit and bring it back up again, whereupon I get a pop-up that list the files that need to be recovered. I click the "Start" (i.e., recover) button, and after recovering all listed files (which takes about 5 seconds) it's replaced a "Finish" button. After clicking "Finish," the files all show up one behind the other (not tiled), all the exact same size regardless of the size they were when Writer stopped. Expected Results: Writer should not have stopped at all. Reproducible: Always User Profile Reset: Yes Additional Info: [Information automatically included from LibreOffice] Locale: en-US Module: TextDocument [Information guessed from browser] OS: Mac OS X (All) OS is 64bit: no -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 148687] Crash swlo!SwAnchoredObject::GetObjRectWithSpaces+0x98:
https://bugs.documentfoundation.org/show_bug.cgi?id=148687 Aron Budea changed: What|Removed |Added CC||bakos.attilakar...@nisz.hu Regression By||Attila Bakos (NISZ) -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 103494] [META] Textbox bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=103494 Aron Budea changed: What|Removed |Added Depends on||148687 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=148687 [Bug 148687] Crash swlo!SwAnchoredObject::GetObjRectWithSpaces+0x98: -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 87740] [META] Anchor and text wrapping bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=87740 Aron Budea changed: What|Removed |Added Depends on||148687 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=148687 [Bug 148687] Crash swlo!SwAnchoredObject::GetObjRectWithSpaces+0x98: -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 105948] [META] Undo/Redo bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=105948 Aron Budea changed: What|Removed |Added Depends on||148687 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=148687 [Bug 148687] Crash swlo!SwAnchoredObject::GetObjRectWithSpaces+0x98: -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 148687] Crash swlo!SwAnchoredObject::GetObjRectWithSpaces+0x98:
https://bugs.documentfoundation.org/show_bug.cgi?id=148687 Aron Budea changed: What|Removed |Added Status|UNCONFIRMED |NEW Keywords|bibisectRequest,|bibisected, bisected, |wantBacktrace |haveBacktrace Ever confirmed|0 |1 CC||aron.bu...@gmail.com Blocks||105948, 87740, 103494 See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=14 ||7126 --- Comment #5 from Aron Budea --- Reproducted using LO 7.4.0.0.beta1+ (cdf48e57da6b8a6a5eb4131340fa2c14be135714) / Ubuntu. It's a regression from the following commit, bibisected using repo bibisect-linux-64-7.4. Adding CC: to Attila Bakos (NISZ). https://cgit.freedesktop.org/libreoffice/core/commit/?id=0d29394598db2e336a9982cbb7041ea407b2bf6d author Attila Bakos (NISZ) 2022-02-07 17:09:42 +0100 committer László Németh2022-03-01 17:53:01 +0100 tdf#147126 sw: fix missing as_char anchoring of group textboxes Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=87740 [Bug 87740] [META] Anchor and text wrapping bugs and enhancements https://bugs.documentfoundation.org/show_bug.cgi?id=103494 [Bug 103494] [META] Textbox bugs and enhancements https://bugs.documentfoundation.org/show_bug.cgi?id=105948 [Bug 105948] [META] Undo/Redo bugs and enhancements -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 149596] UI Groupedbar is missing
https://bugs.documentfoundation.org/show_bug.cgi?id=149596 V Stuart Foote changed: What|Removed |Added CC||vstuart.fo...@utsa.edu Resolution|--- |NOTABUG Status|NEEDINFO|RESOLVED --- Comment #3 from V Stuart Foote --- The MUFFIN Notebook Bar UI "Grouped Bar" remains as a Experimental mode. To activate, enable Experimental mode features from Tools -> Options -> Advanced 'Enable experimental features (may be unstable)' checkbox. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 149611] New: Allow the page to adhere to the theme of the system.
https://bugs.documentfoundation.org/show_bug.cgi?id=149611 Bug ID: 149611 Summary: Allow the page to adhere to the theme of the system. Product: LibreOffice Version: 7.3.4.2 release Hardware: All OS: All Status: UNCONFIRMED Severity: enhancement Priority: medium Component: UI Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: beedellrokejulianlockh...@gmail.com Description: As "http://i.redd.it/ecdrtquwed691.png; depicts, the page does not adhere to the theme of the system automatically. This is present within Web View too, which easily demonstrates why this feature is necessary and obviously should already be present. Steps to Reproduce: Apply any theme to your device and observe how LibreOffice's page does not adhere to my colourative customization, but rather to custom colouration. Actual Results: LibreOffice's page does not adhere to my colourative customization, but rather to its custom colourative preference. Expected Results: LibreOffice's page should adhere to my colourative customization, but rather to its custom colourative preference. Reproducible: Always User Profile Reset: No OpenGL enabled: Yes Additional Info: The provided "LibreOffice Dark Theme" is inadequate even as a manual method of remediation of this problem, because it is infeasible to maintain by those that frequently replace the theme of their system, and is able to be unpleasant if, during daytime, the light version was utilized, and has not been switched to the dark theme before LibreOffice is invoked during darkness. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 149610] New: Whether and how to present iconography should adhere to what the host-OS or desktop-environment mandate.
https://bugs.documentfoundation.org/show_bug.cgi?id=149610 Bug ID: 149610 Summary: Whether and how to present iconography should adhere to what the host-OS or desktop-environment mandate. Product: LibreOffice Version: 7.3.4.2 release Hardware: All OS: All Status: UNCONFIRMED Severity: enhancement Priority: medium Component: UI Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: beedellrokejulianlockh...@gmail.com Description: Whether and how to present iconography should adhere to what the host-OS or desktop environment (especially the stylistic KConfig Module of KDE Plasma and/or GNOME's relevant keys, which "https://askubuntu.com/a/67260/1002900; mentions) mandate. Steps to Reproduce: 1. Invoke “kcmshell5 kcm_style”. 2. Customize how and/or whether iconography text is presented atop buttons and entries within contextual menus, as "http://i.imgur.com/lpMkSSA.png; depicts. Actual Results: LibreOffice does not adhere to this preference. Expected Results: LibreOffice should adhere to this preference. Reproducible: Always User Profile Reset: No OpenGL enabled: Yes Additional Info: Qt software presents text and/or iconography how I have configured it to be. This is useful for accessibility, especially screen-readers, because provision of text allows those buttons to be easily read. Additionally, provision of iconography and/or text is able to increase or decrease cognitive load: for me, replacement of all iconography with text allows me to operate digital interfaces significantly more quickly than I am able to if they are represented iconographically. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 149609] New: LibreOffice 7.3.3.2 Calc Button
https://bugs.documentfoundation.org/show_bug.cgi?id=149609 Bug ID: 149609 Summary: LibreOffice 7.3.3.2 Calc Button Product: LibreOffice Version: 7.3.3.2 release Hardware: x86-64 (AMD64) OS: All Status: UNCONFIRMED Severity: minor Priority: medium Component: Calc Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: crl...@gmail.com Description: In version LibreOffice (Calc) 7.1.7.2 the activation of the button to activate a macro works well, in version 7.3.3.2 it doesn't work the same way, I have to leave the cell where I enter the information so that I can only activate the button of the function, it is not a big problem, but could improve. Actual Results: Entering data into a cell, it should create a .jpg file so far so good, at the moment I need to activate a button to execute a macro (call a created image) it does not activate, I need to press the button twice or I have to exit of that cell and the button that calls the macro is just activated, this does not happen in previous versions, problem in Windows and Linux and the same thing happens. Expected Results: It works, but it's a little inconvenience, especially if you're used to it working right the first time and not needing two steps for the macro call to just work Reproducible: Always User Profile Reset: No Additional Info: I have carried out the tests on several machines and with Linux and Windows and it is the same problem. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 149608] New: Allow documents to adhere to the font of the host operating-system.
https://bugs.documentfoundation.org/show_bug.cgi?id=149608 Bug ID: 149608 Summary: Allow documents to adhere to the font of the host operating-system. Product: LibreOffice Version: 7.3.4.2 release Hardware: All OS: All Status: UNCONFIRMED Severity: enhancement Priority: medium Component: UI Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: beedellrokejulianlockh...@gmail.com Description: One of the problems that prevents migration of my .txt-files to the more versatile formats that LibreOffice supports is that they are unable to adhere to the typography that the host operating-systems has chosen. This is important because not solely is it obvious regression of functionality, it provides consistency to the user, which is important if they are dyslexic or unable to easily see, because it necessitates unnecessary additional configuration, especially if they frequently replace their font(s). Steps to Reproduce: 1. Invoke “kcmshell5 kcm_fonts”. 2. Configure the fonts to not be Liberation Serif, as "http://i.imgur.com/XcEQ1IC.png; depicts. 3. Unnecessarily, but to demonstrate well what I have stated, remove the entries from what "http://i.imgur.com/6TJ3l4p.png; depicts when the styles of the document are empty too (which they are by default, and which "http://i.imgur.com/nNswItI.png; depicts). Actual Results: LibreOffice merely defaults to Liberation (Serif?), which appears to be its default. Expected Results: LibreOffice should utilize the default theme that the user has configured for their operating-system. Reproducible: Always User Profile Reset: No OpenGL enabled: Yes Additional Info: During implementation of this, know that Windows's font is not actually hard-coded, and that no software expects that. It is provided by registry-keys. Windows' typographical customisability and aliasage is actually approximately as advanced as most derivatives of UNIX's. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 144994] libreoffice crashes with kf5-wayland when LanguageTool extension is in use
https://bugs.documentfoundation.org/show_bug.cgi?id=144994 Michael Weghorn changed: What|Removed |Added Status|NEEDINFO|NEW --- Comment #26 from Michael Weghorn --- (In reply to giors_00 from comment #25) > Bug seems to be back. > > (...) > > I've tried in Gnome (Wayland), Plasma X11 and Plasma Wayland (5.25) on arch > linux. It seems to be working fine except in Plasma Wayland: Writer crashes > immediately no matter if you're facing a new empty document or a large one). Thanks for testing. Unless it worked for you with a version in between, the issue was probably never solved in the first place. As mentioned in comment 20, the issue that I could reproduce and fix on Debian testing might be different from the root cause of the problem you're running into. Setting back to NEW, since I was able to reproduce (hopefully the same problem) in an arch VM earlier (but Writer still starts just fine for me on Debian testing in a Plasma Wayland session with the Languagetool extension installed, so *might* be somewhat related to a difference between Arch and Debian). -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 149602] Merging a paragraph with another paragraph by pressing backspace, moves the image to unexpected spot
https://bugs.documentfoundation.org/show_bug.cgi?id=149602 --- Comment #5 from Mike Kaganski --- (In reply to Telesto from comment #4) Just no. For other effects, there are other positioning modes. And "there is an wiki next to help" because I decided to create a FAQ when there was no information at all. Do you want to tell me I shouldn't? Or maybe instead of discouraging me from contributing the way I feel the easiest for the initial text, until it gets into help, you yourself contribute by creating respective help topic - the text is already there? -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 149607] New: Help link for Year (Two Digits) interpretation wrong
https://bugs.documentfoundation.org/show_bug.cgi?id=149607 Bug ID: 149607 Summary: Help link for Year (Two Digits) interpretation wrong Product: LibreOffice Version: 7.3.2.2 release Hardware: x86-64 (AMD64) OS: Windows (All) Status: UNCONFIRMED Severity: trivial Priority: medium Component: Documentation Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: jeremygharri...@yahoo.co.uk CC: olivier.hal...@libreoffice.org Looking for Help on Date Acceptance patterns, I found that ok, under Global - Languages, on file:///C:/Program%20Files/LibreOffice/help/en-GB/text/shared/optionen/0114.html?DbPAR=SHARED#bm_id3154751 . On attempting to follow the link in "For all patterns, two-digit year input is interpreted according to the setting in Tools - Options - General - Year (Two Digits)" (last paragraph), which leads to file:///C:/Program%20Files/LibreOffice/help/en-GB/html?=SHARED=WIN#jahreszahlen , I get a 'Problem Loading Page' error, with: File not found Firefox can’t find the file at /C:/Program Files/LibreOffice/help/en-GB/html?=SHARED=WIN#jahreszahlen. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 139057] Image anchored-to-character at edge of a paragraph isn't included in selection of paragraph
https://bugs.documentfoundation.org/show_bug.cgi?id=139057 --- Comment #19 from Telesto --- (In reply to sdc.blanco from comment #18) Ah, very helpful -- Still kind of interested what the (personal) preference/opinion/idea/ gut feeling is on this: Selecting a single paragraph (single line or multiple lines of text) and using drag and drop (or cut and paste) with images anchored to character with the anchor located at the very start or very end of this paragraph, will be outside the selection: thus not included in the cut or drag action and thus remain at the old position when moving the paragraph. Those anchors will be included if you select multiple (2 or more) paragraphs Should the images/shapes being concluded if a single paragraph is selected (in theory), to be included in the move (drag drop) or cut paste by default. Or is the current behaviour the more sensible one I find the current behaviour unintuitive. But that's only an opinion of a single user.. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 149602] Merging a paragraph with another paragraph by pressing backspace, moves the image to unexpected spot
https://bugs.documentfoundation.org/show_bug.cgi?id=149602 Telesto changed: What|Removed |Added CC||sdc.bla...@youmail.dk --- Comment #4 from Telesto --- (In reply to Mike Kaganski from comment #3) > (In reply to Telesto from comment #0) > > Expected Results: > > Moving relative to anchoring position > > Absolutely wrong. Expected result is that it must be positioned according to > the *positioning* defined for the object, where anchoring *may* play *some* > role. See FAQ [1] (that you had been pointed to several times already, so it > is very confusing why this misunderstanding issue arises again and again - > can you point what should be improved in the explanation?). The wiki might have been pointed out to me, but I don't recall. Why is there an wiki next to help? And well the wiki topic very broad, about all types of anchoring. > Specifically here: the vertical *positioning* of the objects is N cm *from > top* to "Margin", which means "to entire paragraph area" (this is handled in > tdf#149252). So your blue rectangle object must be put 1.11 cm under the top > edge of the *current* paragraph (e.g., *inside* which the anchor is > located). So anchor has *some* effect here - it specifies which paragraph > will be taken into account - but otherwise, the positioning rule does not > care where exactly in the paragraph the anchor is (but for other positioning > rules, like "Center" to "Character", it would matter). > > The separation between anchoring and positioning allows for great > flexibility. This is not a bug. If I had positioned those shapes by using of the position and size dialog it might occurred to me Yes, and should have looked at the position and size dialog after the surprising effect) So bottom line: image position is based on the entire paragraph (default setting), regardless of the position of the 'to character' anchor. I kind of guessed it would relative to the position of the anchor (but that's totally wrong, my mistake) Still: In the case here a merge (fusion) of paragraphs occurred. The reference location changes. Applying Paragraph Position used at paragraph 2, one to one, on paragraph 1.. sounds bit silly. It's technically expected, from user perspective pretty unexpected, IMHO) I kind of expected that on merge of the paragraphs, the position would be corrected. So the current position of the shape in reference to paragraph 1 would be measured. The values from left/ from top being adapted (to reflect the change situation on screen). Preventing shapes flying around to a "random" place (from user perspective) -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 127071] FILEOPEN DOCX: Image moves as Below Line is read as From bottom to Line of text (comment 7)
https://bugs.documentfoundation.org/show_bug.cgi?id=127071
Regina Henschel changed:
What|Removed |Added
CC||michael.st...@allotropia.de
--- Comment #12 from Regina Henschel ---
The binary import in
https://opengrok.libreoffice.org/xref/core/sw/source/filter/ww8/ww8graf.cxx?r=e6de84d4#2432
has these lines:
2432 // Below line in word is a positive value, while in writer its
2433 // negative
2434 tools::Long nYPos = rFSPA.nYaTop;
2435 // #i22673#
2436 if ((eVertRel == text::RelOrientation::TEXT_LINE) && (eVertOri ==
text::VertOrientation::NONE))
2437 nYPos = -nYPos;
Similar exist for export.
That has been introduced with the patches from
https://bz.apache.org/ooo/show_bug.cgi?id=22673
So one way could be to introduces similar toggle of the sign for import/export
from docx. But it has to consider image rotation in addition. The import from
doc has a bug for rotated images that it imports the image unrotated but scaled
into the bounding box of the rotated images.
Only toggling the sign like
if (m_pImpl->nVertRelation == 9 && m_pImpl->nVertOrient
== 0)
{
m_pImpl->nTopPosition = -m_pImpl->nTopPosition;
}
in
https://opengrok.libreoffice.org/xref/core/writerfilter/source/dmapper/GraphicImport.cxx?r=8b4b852a#805
does not work. The image moves in correct direction, but has a wrong position.
I have tried it.
But an addition problem is, that such toggled sign is written to ODF too. That
results in the fact, that an image with "from top by 1cm" in file markup moves
upwards in LO rendering, in contrast to a shape, which move correctly down with
the same file markup.
So my suggestion is, to not fix this by introducing some position manipulating
in OOXML import/export. Instead the wrong handling of the vertical position of
images in Writer should be fixed.
But I have no idea, where this happens. Any code pointer?
--
You are receiving this mail because:
You are the assignee for the bug.
[Libreoffice-bugs] [Bug 141495] CONFIGURATION = EOMONTH function corruption
https://bugs.documentfoundation.org/show_bug.cgi?id=141495 --- Comment #23 from Commit Notification --- Eike Rathke committed a patch related to this issue. It has been pushed to "libreoffice-7-4": https://git.libreoffice.org/core/commit/e54ec5412d9196fb37979db2865b0305bc3d4ad1 Related: tdf#142293 tdf#141495 Allow additional symbols in externals map It will be available in 7.4.0.0.beta2. 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 141495] CONFIGURATION = EOMONTH function corruption
https://bugs.documentfoundation.org/show_bug.cgi?id=141495 Commit Notification changed: What|Removed |Added Whiteboard|target:7.5.0|target:7.5.0 ||target:7.4.0.0.beta2 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 149606] New: "Set Paragraph Style" Options are Unreadable in Dark Mode
https://bugs.documentfoundation.org/show_bug.cgi?id=149606
Bug ID: 149606
Summary: "Set Paragraph Style" Options are Unreadable in Dark
Mode
Product: LibreOffice
Version: 7.3.3.2 release
Hardware: x86-64 (AMD64)
OS: Linux (All)
Status: UNCONFIRMED
Severity: normal
Priority: medium
Component: UI
Assignee: libreoffice-bugs@lists.freedesktop.org
Reporter: christian.hollinger2...@gmail.com
Description:
I am using the openSUSE Dark system theme, Breeze (dark) Icon style,
LibreOffice Dark color scheme, and default ("do not use Themes") LibreOffice
theme. I have changed no other values.
The options in the "Set Paragraph Style" selector (both the combo box at the
top-left and the "Styles" tool in the right sidebar) have black text and cannot
be seen against the dark background. For the combo box in the top-left, the
only way to see the options is to hover the mouse over them, which turns the
background white. For the "Styles" tool in the sidebar, I have to click on a
Style to lighten the background in order to actually read the foreground text
(style title). I tried messing around with various settings but nothing seems
to be working.
This only seems to affect Write.
Steps to Reproduce:
1. Set visual options as described in the first paragraph of this bug's
Description.
2. Either click on the "Set Paragraph Style" selector at the top left to open
the options, or open the "Styles" tool in the sidebar.
Actual Results:
Options are unreadable.
Expected Results:
Used light colors for the foreground text, or a lightly colored background.
Reproducible: Always
User Profile Reset: Yes
OpenGL enabled: Yes
Additional Info:
Version: 7.3.3.2 / LibreOffice Community
Build ID: 30(Build:2)
CPU threads: 6; OS: Linux 5.18; UI render: default; VCL: kf5 (cairo+xcb)
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 91688] VIEWING: Print Preview does not display comments
https://bugs.documentfoundation.org/show_bug.cgi?id=91688 pamela nelson changed: What|Removed |Added URL||https://www.kortingsok.nl --- Comment #29 from pamela nelson --- instead of resolving the issue just bumping it wow wonderful https://www.kortingsok.nl -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 149605] New: Conflict with VoiceOver/NVDA
https://bugs.documentfoundation.org/show_bug.cgi?id=149605 Bug ID: 149605 Summary: Conflict with VoiceOver/NVDA Product: LibreOffice Version: unspecified Hardware: All OS: All Status: UNCONFIRMED Severity: normal Priority: medium Component: LibreOffice Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: nickkir...@hotmail.com I encounter a problem when saving documents in MS Office format while using Libreoffice with accessibility functions such as VoiceOver or NVDA running. Libreoffice goes into not responding mode and can be a nightmare to reopen. The problems occur in both Windows 10 and iMac OS. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 149596] UI Groupedbar is missing
https://bugs.documentfoundation.org/show_bug.cgi?id=149596 --- Comment #2 from ThP --- Only *UI Groupedbar compact* available, *UI Groupedbar* removed. Two different styles. *UI Groupedbar compact* has two rows, *UI Groupedbar* three. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 149319] In Draw and Writer, F1 (Help) on "Optimize" in Table bar does not have a linked help page
https://bugs.documentfoundation.org/show_bug.cgi?id=149319 Olivier Hallot changed: What|Removed |Added Status|UNCONFIRMED |NEW Ever confirmed|0 |1 --- Comment #2 from Olivier Hallot --- In both cases, F1 is sending a bad HID and the Help shows the right page for the bad HID. Draw : SD_HID_SDGRAPHICVIEWSHELL Writer : SW_HID_EDIT_WIN In both case it should be "hid/.uno:OptimizeTable" -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 149598] "Format cells" dialog does not remember size
https://bugs.documentfoundation.org/show_bug.cgi?id=149598 m.a.riosv changed: What|Removed |Added Severity|normal |enhancement -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 149321] F1 (Help) Table > Size does not link to relevant page
https://bugs.documentfoundation.org/show_bug.cgi?id=149321 Olivier Hallot changed: What|Removed |Added Ever confirmed|0 |1 Status|UNCONFIRMED |NEW --- Comment #3 from Olivier Hallot --- The uno command is .uno:TableAutoFitMenu as found in line 629 of sw/uiconfig/swriter/menubar/menubar.xml . 1) There is no Help page to receive this command. 2) furthermore, for some reason, the command is not sent to the Help, "slot0" is sent instead -> check the .uno:TableAutoFitMenu code. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 149525] Add sparklines extended tips
https://bugs.documentfoundation.org/show_bug.cgi?id=149525 Hossein changed: What|Removed |Added Whiteboard|reviewed:2022 target:7.5.0 |reviewed:2022 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 80430] [META] Documentation gap for new features
https://bugs.documentfoundation.org/show_bug.cgi?id=80430 Olivier Hallot changed: What|Removed |Added Depends on||149352 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=149352 [Bug 149352] F1 (Help) Edit > Selection Mode > Standard in Writer gives 404 error -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 149352] F1 (Help) Edit > Selection Mode > Standard in Writer gives 404 error
https://bugs.documentfoundation.org/show_bug.cgi?id=149352 Olivier Hallot changed: What|Removed |Added Assignee|libreoffice-b...@lists.free |olivier.hallot@libreoffice. |desktop.org |org Ever confirmed|0 |1 Blocks||80430 Status|UNCONFIRMED |NEW Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=80430 [Bug 80430] [META] Documentation gap for new features -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 43459] Opening document fails when on samba mount with mixed OS windows/linux
https://bugs.documentfoundation.org/show_bug.cgi?id=43459 Julien Nabet changed: What|Removed |Added Status|NEW |NEEDINFO CC||serval2...@yahoo.fr --- Comment #8 from Julien Nabet --- On pc Debian x86-64 with LO Debian package 7.3.4.1, I don't reproduce this. Here's what I did: - created a Samba share on Linux machine - created and saved an ods file with LO from Windows machine on the Samba share and let it opened - opened the file from Linux machine I tried with copy the file and read-only, both worked. Could someone else give it a try? I may have missed something? -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 80430] [META] Documentation gap for new features
https://bugs.documentfoundation.org/show_bug.cgi?id=80430 Olivier Hallot changed: What|Removed |Added Depends on||149393 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=149393 [Bug 149393] BASE and DECIMAL spreadsheet functions need cross-references -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 149393] BASE and DECIMAL spreadsheet functions need cross-references
https://bugs.documentfoundation.org/show_bug.cgi?id=149393 Olivier Hallot changed: What|Removed |Added Assignee|libreoffice-b...@lists.free |olivier.hallot@libreoffice. |desktop.org |org Status|UNCONFIRMED |NEW Blocks||80430 Ever confirmed|0 |1 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=80430 [Bug 80430] [META] Documentation gap for new features -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 55004] backup copy fails when using share / samba
https://bugs.documentfoundation.org/show_bug.cgi?id=55004 Julien Nabet changed: What|Removed |Added CC||serval2...@yahoo.fr Status|NEW |NEEDINFO --- Comment #41 from Julien Nabet --- On pc Debian testing x86-64 with LO Debian package 7.3.4.2, I don't reproduce this. Here what I did: - created a local samba share - launched Writer and create a brand new file - saved it with name "test1.odt" on the local samba share - enabled option "Always create backup copy" - relaunched LO Writer - opened test1.odt - added some text - saved it again => I got a non null file ~/.config/libreoffice/4/user/backup/test1.bak (8,7K). Did I miss something or could someone may give a new try with LO 7.3.4? -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 149089] FILEOPEN: docx: get extra mini space between Chinese character when open docx file
https://bugs.documentfoundation.org/show_bug.cgi?id=149089 --- Comment #18 from Zhang Qide --- Created attachment 180823 --> https://bugs.documentfoundation.org/attachment.cgi?id=180823=edit before bug 148940 the kerning between Chinese character is more acceptable before fix bug 148940 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 118320] Add support for Windows 10/11 dark mode
https://bugs.documentfoundation.org/show_bug.cgi?id=118320 Rafael Lima changed: What|Removed |Added See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=14 ||8675 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 148675] Table grid lines are black on black in Dark mode
https://bugs.documentfoundation.org/show_bug.cgi?id=148675 Rafael Lima changed: What|Removed |Added See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=11 ||8320 OS|Windows (All) |All --- Comment #3 from Rafael Lima --- (In reply to Timur from comment #1) > Please see if related to > https://bugs.documentfoundation.org/show_bug.cgi?id=118320#c91 This bug is not Windows-only. It happens on Linux as well. I could not find a Windows Dark-Mode meta bug, so I'm adding the one you mentioned as a "See Also" bug. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 143148] Use pragma once instead of include guards (Episode 2: Endgame)
https://bugs.documentfoundation.org/show_bug.cgi?id=143148 --- Comment #35 from Commit Notification --- Diane Leigh committed a patch related to this issue. It has been pushed to "master": https://git.libreoffice.org/core/commit/243ffb1604e784a5dbc455a32681af32dd0126af tdf#143148 Use pragma once in embedserv and helpcompiler It will be available in 7.5.0. The patch should be included in the daily builds available at https://dev-builds.libreoffice.org/daily/ in the next 24-48 hours. More information about daily builds can be found at: https://wiki.documentfoundation.org/Testing_Daily_Builds Affected users are encouraged to test the fix and report feedback. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 143148] Use pragma once instead of include guards (Episode 2: Endgame)
https://bugs.documentfoundation.org/show_bug.cgi?id=143148 Commit Notification changed: What|Removed |Added Whiteboard|target:7.3.0 target:7.4.0 |target:7.3.0 target:7.4.0 |reviewed:2022 |reviewed:2022 target:7.5.0 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 143344] [META] Linux Dark Mode bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=143344 Rafael Lima changed: What|Removed |Added Depends on||148675 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=148675 [Bug 148675] Table grid lines are black on black in Dark mode -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 148675] Table grid lines are black on black in Dark mode
https://bugs.documentfoundation.org/show_bug.cgi?id=148675 Rafael Lima changed: What|Removed |Added Status|UNCONFIRMED |NEW Ever confirmed|0 |1 CC||rafael.palma.l...@gmail.com Blocks||143344 --- Comment #2 from Rafael Lima --- Confirmed with Version: 7.5.0.0.alpha0+ / LibreOffice Community Build ID: ca47989ad60b1414f92be22a1fbf4c1d1a92dd97 CPU threads: 12; OS: Linux 5.13; UI render: default; VCL: kf5 (cairo+xcb) Locale: pt-BR (pt_BR.UTF-8); UI: en-US Calc: CL Border colors do not have an "Automatic" color option, so I'm not sure how we will be able to handle dark borders in Dark mode. Text in tables are shown in white when using dark mode, so we should have the same behavior for table borders. Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=143344 [Bug 143344] [META] Linux Dark Mode bugs and enhancements -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 149089] FILEOPEN: docx: get extra mini space between Chinese character when open docx file
https://bugs.documentfoundation.org/show_bug.cgi?id=149089 --- Comment #17 from Zhang Qide --- Created attachment 180822 --> https://bugs.documentfoundation.org/attachment.cgi?id=180822=edit another doc compare side by side -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 149580] Text boundaries stop applying when saving as DOCX and opening both files
https://bugs.documentfoundation.org/show_bug.cgi?id=149580 Rafael Lima changed: What|Removed |Added Ever confirmed|0 |1 Status|UNCONFIRMED |NEW --- Comment #3 from Rafael Lima --- Repro with Version: 7.5.0.0.alpha0+ / LibreOffice Community Build ID: ca47989ad60b1414f92be22a1fbf4c1d1a92dd97 CPU threads: 12; OS: Linux 5.13; UI render: default; VCL: kf5 (cairo+xcb) Locale: pt-BR (pt_BR.UTF-8); UI: en-US Calc: CL The ODT file should not be showing the table boundaries since View - Table Boundaries option is unchecked. Setting this to NEW. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 149600] Hue band in color picker dialog doesn't react to clicks before picking a color
https://bugs.documentfoundation.org/show_bug.cgi?id=149600 Caolán McNamara changed: What|Removed |Added Status|NEW |ASSIGNED Assignee|libreoffice-b...@lists.free |caol...@redhat.com |desktop.org | --- Comment #1 from Caolán McNamara --- I imagine the problem is that the initial color is "Automatic" -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 149596] UI Groupedbar is missing
https://bugs.documentfoundation.org/show_bug.cgi?id=149596 Rafael Lima changed: What|Removed |Added Status|UNCONFIRMED |NEEDINFO Ever confirmed|0 |1 CC||rafael.palma.l...@gmail.com --- Comment #1 from Rafael Lima --- We have the Groupedbar Compact option under View - User Interface. Isn't this the option you're looking for? Tested with Version: 7.5.0.0.alpha0+ / LibreOffice Community Build ID: ca47989ad60b1414f92be22a1fbf4c1d1a92dd97 CPU threads: 12; OS: Linux 5.13; UI render: default; VCL: kf5 (cairo+xcb) Locale: pt-BR (pt_BR.UTF-8); UI: en-US Calc: CL -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 149089] FILEOPEN: docx: get extra mini space between Chinese character when open docx file
https://bugs.documentfoundation.org/show_bug.cgi?id=149089 --- Comment #16 from Zhang Qide --- The date align in the first page is correct after the commit. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 149525] Add sparklines extended tips
https://bugs.documentfoundation.org/show_bug.cgi?id=149525 --- Comment #4 from Olivier Hallot --- (In reply to Commit Notification from comment #3) > Olivier Hallot committed a patch related to this issue. > It has been pushed to "master": > > https://git.libreoffice.org/help/commit/ > 8fee25674c3bdb0cf3cee4a7dfcc2a814431549b > > tdf#149525 Update Writer-View-Toolbars PLease forget this patch wrong bug number. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 149089] FILEOPEN: docx: get extra mini space between Chinese character when open docx file
https://bugs.documentfoundation.org/show_bug.cgi?id=149089 --- Comment #15 from Zhang Qide --- Maybe the terminology should called "kerning", or "字符间距" or "间隙" in Chinese -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 112485] [META] Line shape and line-level bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=112485 Rafael Lima changed: What|Removed |Added Depends on||149597 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=149597 [Bug 149597] ENHANCEMENT: Multi-color line attribute (dashed lines with alternate background color -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 149597] ENHANCEMENT: Multi-color line attribute (dashed lines with alternate background color
https://bugs.documentfoundation.org/show_bug.cgi?id=149597 Rafael Lima changed: What|Removed |Added Blocks||112485 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=112485 [Bug 112485] [META] Line shape and line-level bugs and enhancements -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 149597] ENHANCEMENT: Multi-color line attribute (dashed lines with alternate background color
https://bugs.documentfoundation.org/show_bug.cgi?id=149597 Rafael Lima changed: What|Removed |Added Severity|normal |enhancement CC||rafael.palma.l...@gmail.com Keywords||needsUXEval --- Comment #1 from Rafael Lima --- When I have to do this, I simply create a copy of the dashed line, change its style to solid and change the color. Then I align them to be perfectly on top of each other. This is a bit cumbersome, I know. To implement what you're proposing we would have to: 1) Add an option for background line color (which does not exist ATM) 2) Change the dashed line drawing method I could not find an equivalent feature in other office suites. Let's hear from the UX team about this idea. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 128196] filenames containing '#' get truncated when saving to GVFS smb:// paths (Samba share), effectively causing silent data loss
https://bugs.documentfoundation.org/show_bug.cgi?id=128196 Julien Nabet changed: What|Removed |Added Status|NEW |ASSIGNED Assignee|libreoffice-b...@lists.free |serval2...@yahoo.fr |desktop.org | --- Comment #9 from Julien Nabet --- I gave a try with https://gerrit.libreoffice.org/c/core/+/136084 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 149089] FILEOPEN: docx: get extra mini space between Chinese character when open docx file
https://bugs.documentfoundation.org/show_bug.cgi?id=149089 --- Comment #14 from Zhang Qide --- Created attachment 180821 --> https://bugs.documentfoundation.org/attachment.cgi?id=180821=edit long doc To make things worse， Libreoffice open a docx file Contains 51 pages long get 4 pages more than ms office because of the extra mini space. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 149089] FILEOPEN: docx: get extra mini space between Chinese character when open docx file
https://bugs.documentfoundation.org/show_bug.cgi?id=149089 --- Comment #13 from Zhang Qide --- Created attachment 180820 --> https://bugs.documentfoundation.org/attachment.cgi?id=180820=edit compare same doc with ms office 2013 side by side see the attachment -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 149525] Add sparklines extended tips
https://bugs.documentfoundation.org/show_bug.cgi?id=149525 --- Comment #3 from Commit Notification --- Olivier Hallot committed a patch related to this issue. It has been pushed to "master": https://git.libreoffice.org/help/commit/8fee25674c3bdb0cf3cee4a7dfcc2a814431549b tdf#149525 Update Writer-View-Toolbars -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 149525] Add sparklines extended tips
https://bugs.documentfoundation.org/show_bug.cgi?id=149525 Commit Notification changed: What|Removed |Added Whiteboard|reviewed:2022 |reviewed:2022 target:7.5.0 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 141495] CONFIGURATION = EOMONTH function corruption
https://bugs.documentfoundation.org/show_bug.cgi?id=141495 --- Comment #22 from Eike Rathke --- The last commit 9aab475e221e1abee2108b21545f2bdaa48552e6 allows reading and repairing such broken documents, but the cause why those programmatic names were written is unidentified. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 141495] CONFIGURATION = EOMONTH function corruption
https://bugs.documentfoundation.org/show_bug.cgi?id=141495 --- Comment #21 from Commit Notification --- Eike Rathke committed a patch related to this issue. It has been pushed to "master": https://git.libreoffice.org/core/commit/9aab475e221e1abee2108b21545f2bdaa48552e6 Related: tdf#142293 tdf#141495 Allow additional symbols in externals map It will be available in 7.5.0. The patch should be included in the daily builds available at https://dev-builds.libreoffice.org/daily/ in the next 24-48 hours. More information about daily builds can be found at: https://wiki.documentfoundation.org/Testing_Daily_Builds Affected users are encouraged to test the fix and report feedback. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 141495] CONFIGURATION = EOMONTH function corruption
https://bugs.documentfoundation.org/show_bug.cgi?id=141495 Commit Notification changed: What|Removed |Added Whiteboard||target:7.5.0 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 139057] Image anchored-to-character at edge of a paragraph isn't included in selection of paragraph
https://bugs.documentfoundation.org/show_bug.cgi?id=139057 --- Comment #18 from sdc.bla...@youmail.dk --- (In reply to Telesto from comment #16) > How snap to character in paragraph exactly works is still black box to me. There is no "snap to character" in the sense of an automatic positioning/tracking in relation to the location of "to character" anchor, unless you select (in Position and Size Horizontal "to" "Character"). Positioning always depends on the positioning controls selected in the Position and Size dialog (where most of the controls are to define positions in relation to the page or the paragraph where the anchor is located, also when "to character" anchor is used). If you know where you want the image/shape positioned in relation to the anchor, then set the position with the controls and drag the anchor. The shape will "follow" and "keep" its position (as defined in the controls). > I have tendency to say, if an image is > moved by drag and drop to different paragraph, mimic the behaviour of to > paragraph, and simply but at the start of the paragraph. So skipping the - > to me arbitrary - picking of some character. In terms of positioning, "to character" and "to paragraph" anchors are almost identical, except that "to character" also offers positioning options that depend on the character (e.g., font size, padding) or line of text where the "to character" anchor is positioned. If you are not going to use those character-specific options (and do not want to move individual words with "attached" objects, as in your word "blue" with blue shape), then "to paragraph" anchor is sufficient. In general, if you approach positioning solely in terms of "drag and drop" (and never use the positioning options) (and do not have a need to link objects to individual words) then there is no reason to use "to character" anchoring. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 97341] Width for document comments cannot be changed manually
https://bugs.documentfoundation.org/show_bug.cgi?id=97341 himajin100...@gmail.com changed: What|Removed |Added CC||himajin100...@gmail.com Whiteboard|happy fathers day whatsapp | |status video download | Keywords|topicWeb| URL|https://mestatusvideo.com/h | |appy-fathers-day-whatsapp-s | |tatus-video-download/ | -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 144994] libreoffice crashes with kf5-wayland when LanguageTool extension is in use
https://bugs.documentfoundation.org/show_bug.cgi?id=144994 --- Comment #25 from giors...@yahoo.it --- Bug seems to be back. Version: 7.3.4.2 / LibreOffice Community Build ID: 30(Build:2) CPU threads: 4; OS: Linux 5.18; UI render: default; VCL: kf5 (cairo+wayland) Locale: es-ES (es_ES.UTF-8); UI: es-ES 7.3.4-2 Calc: threaded I've tried in Gnome (Wayland), Plasma X11 and Plasma Wayland (5.25) on arch linux. It seems to be working fine except in Plasma Wayland: Writer crashes immediately no matter if you're facing a new empty document or a large one). -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 149219] File → New → Labels: Wrong German translation of appearing dialog, differs to LO-help
https://bugs.documentfoundation.org/show_bug.cgi?id=149219 Robert Großkopf changed: What|Removed |Added Resolution|--- |WORKSFORME Status|UNCONFIRMED |RESOLVED --- Comment #2 from Robert Großkopf --- Tested with LO 7.3.4.2 - seems it has been solved. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 149604] New: Dialog Labels → Format: "V-Pitch" in overview shows wrong positioned heads of arrows
https://bugs.documentfoundation.org/show_bug.cgi?id=149604 Bug ID: 149604 Summary: Dialog Labels → Format: "V-Pitch" in overview shows wrong positioned heads of arrows Product: LibreOffice Version: 7.3.4.2 release Hardware: x86-64 (AMD64) OS: Linux (All) Status: UNCONFIRMED Severity: normal Priority: medium Component: UI Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: rob...@familiegrosskopf.de Created attachment 180819 --> https://bugs.documentfoundation.org/attachment.cgi?id=180819=edit Open the screenshot and have a look to the red marked "heads of arrows" Open the attached screenshot. There are heads of arrows, which should be positioned near "Top Margin" and "V. Pitch" (in German "Rand oben" and "V. Abstand"). This arrows appear depending on the zoom factor of the windows-system near/behind V. Pitch. Irritates only a little bit… Detected with LO 7.3.4.2 under OpenSUSE 15.3 64bit rpm Linux. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 149603] New: MacOS Safari (Monterey) does not display LibreOffice HELP
https://bugs.documentfoundation.org/show_bug.cgi?id=149603 Bug ID: 149603 Summary: MacOS Safari (Monterey) does not display LibreOffice HELP Product: LibreOffice Version: 7.2.7.2 release Hardware: ARM OS: macOS (All) Status: UNCONFIRMED Severity: normal Priority: medium Component: LibreOffice Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: alanandpe...@outlook.com Description: LibreOffice Help not shown with Safari set as the default browser in MacOS Monterey on M1 chip. The file: ///Users/username/Library/Application%20Support/LibreOffice/4/user/temp/lu18205pva.tmp/NewHelp0.html can be opened with Chrome or Firefox, for example, but (even when manually opened)the result is just a blank window in Safari. Steps to Reproduce: 1. Safari set as default browser 2. Click on Menu-Bar Help or any Help button (e.g. in the CALC Function Wizard) Actual Results: Safari displays a blank window Expected Results: LibreOffice Help page displayed Reproducible: Always User Profile Reset: Yes Additional Info: [Information automatically included from LibreOffice] Locale: en-US Module: SpreadsheetDocument [Information guessed from browser] OS: Mac OS X (12.4) OS is 64bit: no (YES ACTUALLY!) >From LibreOffice - About LibreOffice (NOT Help - About LibreOffice): Version: 7.3.4.2 Build: 728fec16bd5f605073805c3c9e7c4212a0120dc5 Environment: CPU threads: 8; OS: Mac OS X 12.4 User Interface: UI render: default; VCL: osx Locale: en-GB (en_GB.UTF-8); UI: en-US Misc: Calc: threaded (ON M1 CHIP) -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 128196] filenames containing '#' get truncated when saving to GVFS smb:// paths (Samba share), effectively causing silent data loss
https://bugs.documentfoundation.org/show_bug.cgi?id=128196 Julien Nabet changed: What|Removed |Added Status|UNCONFIRMED |NEW Ever confirmed|0 |1 CC||serval2...@yahoo.fr --- Comment #8 from Julien Nabet --- On pc Debian x86-64 with master sources updated today, I could reproduce this. I installed Samba (for the first time, I thought it would have been more complicated) following https://ubuntu.com/tutorials/install-and-configure-samba#1-overview. Then: - "File/Save Remote..." - Manage service, Windows share and configured it - saved a brand new file named test#1.odt => it saved a file just named "test" -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 112876] Make use of scroll lock for navigation configurable (it conflicts with system use as keyboard layout indicator)
https://bugs.documentfoundation.org/show_bug.cgi?id=112876 Buovjaga changed: What|Removed |Added Keywords||difficultyMedium -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 149089] FILEOPEN: docx: get extra mini space between Chinese character when open docx file
https://bugs.documentfoundation.org/show_bug.cgi?id=149089 --- Comment #12 from Mark Hung --- @Zhang Qide: would you please take another screenshot ( with display grid on ) and highlight where it is still problematic? -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 149593] UI same hotkeys for two items "Formulaire" and "Protéger la feuille"
https://bugs.documentfoundation.org/show_bug.cgi?id=149593 Julien Nabet changed: What|Removed |Added CC||serval2...@yahoo.fr --- Comment #2 from Julien Nabet --- For "Formulaires": https://translations.documentfoundation.org/translate/libo_ui-master/officecfgregistrydataorgopenofficeofficeui/fr/?checksum=45eaf5fda4532744=note%3AVfg7K_by=-priority%2Cposition For "Protéger la feuille": https://translations.documentfoundation.org/translate/libo_ui-master/officecfgregistrydataorgopenofficeofficeui/fr/?checksum=2194fdca0596edd3=note%3AhfP6T_by=-priority%2Cposition BTW, in this same menu, there are also: "Personnaliser" and "Partager le classeur..." which both use "p" as shortcut. "Options d'Autocorrection" and "Autosaisie" which both use "a". "Recherche de valeur cible..." and "Gestionnaire des extensions" which both use "e". "Orthographe" and "Options..." : "o" ... It seems definition of shortcuts is a never ending story and it's not only in French UI :-(. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 126109] EDITING/UI: Slow when replacing string to number
https://bugs.documentfoundation.org/show_bug.cgi?id=126109 --- Comment #19 from Commit Notification --- Noel Grandin committed a patch related to this issue. It has been pushed to "master": https://git.libreoffice.org/core/commit/1a7913c1b57b333223b30194c67c4d8d11e583d2 tdf#126109 calc slow when replacing string to number It will be available in 7.5.0. The patch should be included in the daily builds available at https://dev-builds.libreoffice.org/daily/ in the next 24-48 hours. More information about daily builds can be found at: https://wiki.documentfoundation.org/Testing_Daily_Builds Affected users are encouraged to test the fix and report feedback. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 149601] Multiple grammar check passes needed for "Quotation marks" grammar checker
https://bugs.documentfoundation.org/show_bug.cgi?id=149601 Mike Kaganski changed: What|Removed |Added Attachment #180817|A. en-US text with problems |An en-US text with problems description|for "Quotation marks" |for "Quotation marks" |grammar checker |grammar checker -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 149089] FILEOPEN: docx: get extra mini space between Chinese character when open docx file
https://bugs.documentfoundation.org/show_bug.cgi?id=149089 --- Comment #11 from Zhang Qide --- the bug almost same as before Version: 7.5.0.0.alpha0+ (x64) / LibreOffice Community Build ID: f804b8d0b1fc0c215c8883c76344b2d256d5c003 CPU threads: 4; OS: Windows 6.1 Service Pack 1 Build 7601; UI render: Skia/Raster; VCL: win Locale: zh-CN (zh_CN); UI: zh-CN Calc: CL -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 139057] Image anchored-to-character at edge of a paragraph isn't included in selection of paragraph
https://bugs.documentfoundation.org/show_bug.cgi?id=139057 Eyal Rozenberg changed: What|Removed |Added Summary|Image to character with the |Image anchored-to-character |anchor positioned at the|at edge of a paragraph |end or beginning of a |isn't included in selection |paragraph isn't included in |of paragraph |the selection (except if| |multiple paragraph's being | |selected) | --- Comment #17 from Eyal Rozenberg --- Tried to shorten the title while preserving the meaning, but with less detail. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 139057] Image to character with the anchor positioned at the end or beginning of a paragraph isn't included in the selection (except if multiple paragraph's being selected)
https://bugs.documentfoundation.org/show_bug.cgi?id=139057 Telesto changed: What|Removed |Added Blocks|112182 | --- Comment #16 from Telesto --- (In reply to sdc.blanco from comment #14) > (In reply to Telesto from comment #11) > > In short and in general: Problems in comment 11 seem to stem from > difficulties in knowing how to select an anchor (see bug 146445 for relevant > explanations), Three parts * It's partly about visibility. It nice to now if a selection does include an anchor (and which images shapes/and such entails; images get highlighted; shapes not * If a text selection automatically include the anchor (to character) directly to the left and/or right of the selection. * The intuitivity/ predictability of the behaviour. Select a single text paragraph does *not* include images anchored at the start/end of the paragraph, but multiple paragraphs does. If the paragraph being a bulleted list it does include images too. I still don't grasp the reasoning why a single paragraph should behave differently. >which is related to/interacts with difficulty in knowing how > to interpret the current anchor icon properly to determine the anchor > location. Yes >Bug 138351 discusses the issue of improving the display of anchor > location -- but even if that is improved, it is necessary to know how to > insure that the anchor is included in the selection. Yes > > Possible "responses": > - make it easier for a user to know when an anchor is included in a text > selection (but no proposals offered for design changes.) Yes. One would be making anchor visible as formatting mark regardless of the selection (so being aware of the anchor being present) However this still partial fix. There can be overlapping anchors (multiple at the same spot. And you still don't know which anchor belongs to which shape/image. And you might want distinction between the anchor icon for 'to paragraph' and 'to character' anchors. > - give better documentation about how to insure selection of an anchor (but > less effective for those users who expect the interface to be "intuitive", > and therefore will not read documentation). Yes > > About selecting the anchor: > > Here are three examples that will illustrate how to "succeed" in places > where you have "failed". Perhaps these positive examples (along with the > explanations in bug 146445) will help you to form an understanding of what > is needed to insure that an anchor is selected. > > > 3. Move the text up. Yellow and orange shape not moving > Do NOT repro with cursor placed in paragraph and Ctrl+Alt+Up arrow. All > shapes move. > Do repro with Ctrl+X on selection and Ctrl+V. > > > 8. Double click 'Blue' > > 9. Drag & drop below heading 1.. image not following > > 11. Place cursor after 'yellow' and select blue with the space before > > 12. Drag up below heading 1. -> Only "blue' text moves image stays > 8 and 11 show examples where you have failed to select the anchor. > > Additional tests to show how to drag blue shape up, by including the anchor > in the selection. > > 13. Open attachment 180813 [details], place cursor before "b" in blue, then > select two characters to left (i.e., space and "w" at end of yellow). Drag > selection to Heading 1, see "blue" shape follow. Noticed that, but well obviously a strange selection.. but well > > 14. Open attachment 180813 [details], select blue shape, move anchor to > middle of word "blue". Double-click "blue", drag to Heading 1, see "blue" > shape follow. Yes, true. If you move an image/shape to different paragraph (drag and drop) the anchor will by design move the next paragraph & snap behind (so anchor at the right) of a word (if it's a non-empty paragraph). How snap to character in paragraph exactly works is still black box to me. It does pick some character in the paragraph. I have tendency to say, if an image is moved by drag and drop to different paragraph, mimic the behaviour of to paragraph, and simply but at the start of the paragraph. So skipping the - to me arbitrary - picking of some character.. [but well I'm adding lots of different topics in a single bug report] I'm currently using this bug as a 'discussion topic'. To figure out if there is a bug (or bugs) and which part being documentation or UI feedback issues. Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=112182 [Bug 112182] [META] Text and object selection issues -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 112182] [META] Text and object selection issues
https://bugs.documentfoundation.org/show_bug.cgi?id=112182 Telesto changed: What|Removed |Added Depends on|139057 | Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=139057 [Bug 139057] Image to character with the anchor positioned at the end or beginning of a paragraph isn't included in the selection (except if multiple paragraph's being selected) -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 149602] Merging a paragraph with another paragraph by pressing backspace, moves the image to unexpected spot
https://bugs.documentfoundation.org/show_bug.cgi?id=149602 Mike Kaganski changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |NOTABUG --- Comment #3 from Mike Kaganski --- (In reply to Telesto from comment #0) > Expected Results: > Moving relative to anchoring position Absolutely wrong. Expected result is that it must be positioned according to the *positioning* defined for the object, where anchoring *may* play *some* role. See FAQ [1] (that you had been pointed to several times already, so it is very confusing why this misunderstanding issue arises again and again - can you point what should be improved in the explanation?). Specifically here: the vertical *positioning* of the objects is N cm *from top* to "Margin", which means "to entire paragraph area" (this is handled in tdf#149252). So your blue rectangle object must be put 1.11 cm under the top edge of the *current* paragraph (e.g., *inside* which the anchor is located). So anchor has *some* effect here - it specifies which paragraph will be taken into account - but otherwise, the positioning rule does not care where exactly in the paragraph the anchor is (but for other positioning rules, like "Center" to "Character", it would matter). The separation between anchoring and positioning allows for great flexibility. This is not a bug. [1] https://wiki.documentfoundation.org/Faq/Writer/AnchoringAndPositioning -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 112182] [META] Text and object selection issues
https://bugs.documentfoundation.org/show_bug.cgi?id=112182 Dieter changed: What|Removed |Added Depends on||139057 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=139057 [Bug 139057] Image to character with the anchor positioned at the end or beginning of a paragraph isn't included in the selection (except if multiple paragraph's being selected) -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 139057] Image to character with the anchor positioned at the end or beginning of a paragraph isn't included in the selection (except if multiple paragraph's being selected)
https://bugs.documentfoundation.org/show_bug.cgi?id=139057 Dieter changed: What|Removed |Added Blocks||112182 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=112182 [Bug 112182] [META] Text and object selection issues -- You are receiving this mail because: You are the assignee for the bug.
