[Libreoffice-bugs] [Bug 139057] Image to character/paragraph at the end or beginning of a paragraph isn't included in a single line section
https://bugs.documentfoundation.org/show_bug.cgi?id=139057 --- Comment #9 from Telesto --- Created attachment 180761 --> https://bugs.documentfoundation.org/attachment.cgi?id=180761=edit Example file Second attempt (In reply to Michael Stahl (allotropia) from comment #8) > i don't think there's an easy tweak to this that preserves the API > compatibility that comment#4 is about, and it's a rather minor problem, you > can always click on the image to delete it that way. A small retry probably better describing the 'issue'. Primary question: What's the value of anchoring an image to an character if the anchor is broken with ease. The anchor suggests a connection between 'the character' and the image . The image is positioned relative to the anchor point, so if the characters move (drag/drop or copy/paste) the image should be following. 1. Open the attached file 2. Double click Lorem Ipsum 3. Drag the text to the top of the page (say it's a list without bullets) 4. Notice the image moving (why: image is anchored to character, and the anchor is manually attached to 'm' of ipsum 5. CTRL+Z 6. Change the anchor of the image to 'to paragraph' 7. Change the anchor back to 'to character' (anchor will but after ipsum). Now drag the text up again.. Image stay's behind (expected to move along with the text) as in 4 8. Undo the dragging up (but anchor still behind 'ipsum') 9. Press CTRL+A and enable bulleted list 10. Move Ipsum Lorum up (with arrows). Notice the anchor moving along. I guess there being an explanation for each and every case in technical sense. But from end-user perspective this kind of arbitrary. And well 'to character' has to states. (A). Truly positioned to a character. (B) put after a characters (most common, I guess). Which is not truly a to character anchor, IMHO In case of 'to paragraph' we end up' what 'anchor to paragraph' means. Is the image bound to the paragraph (the characters) or bound to paragraph location. Currently it's mixture of both (case dependent) A fix would be to actually anchoring the anchor to a character and not the 'invisible' behind or in case of to paragraph 'prior' the visible character. [sorry, for the bad terminology]. But I'm not overseeing the consequences.. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 108539] [META] Chart data table bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=108539 Bug 108539 depends on bug 149536, which changed state. Bug 149536 Summary: [UI] The Data Table dialog enables the button Move Row Up and disables the button Move Row Down when the opposite is needed (and vice versa). https://bugs.documentfoundation.org/show_bug.cgi?id=149536 What|Removed |Added Status|ASSIGNED|RESOLVED Resolution|--- |FIXED -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 149535] Add highlighting (background color) to options for marking misspelled words in the spelling checker
https://bugs.documentfoundation.org/show_bug.cgi?id=149535 Rafael Lima changed: What|Removed |Added Keywords||accessibility, needsUXEval CC||rafael.palma.l...@gmail.com Blocks||96000 --- Comment #1 from Rafael Lima --- Sounds a good idea to me. Let's hear from the UX team. Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=96000 [Bug 96000] [META] Spelling and grammar checking bugs and enhancements -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 96000] [META] Spelling and grammar checking bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=96000 Rafael Lima changed: What|Removed |Added Depends on||149535 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=149535 [Bug 149535] Add highlighting (background color) to options for marking misspelled words in the spelling checker -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 103381] [META] Pivot table (aka Data Pilot) bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=103381 Rafael Lima changed: What|Removed |Added Depends on||149526 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=149526 [Bug 149526] Calc Pivot Table where the range includes many empty rows takes 30 minutes and 9GB of Ram before crashing -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 149526] Calc Pivot Table where the range includes many empty rows takes 30 minutes and 9GB of Ram before crashing
https://bugs.documentfoundation.org/show_bug.cgi?id=149526 Rafael Lima changed: What|Removed |Added Status|UNCONFIRMED |NEEDINFO Ever confirmed|0 |1 CC||rafael.palma.l...@gmail.com Blocks||103381 --- Comment #1 from Rafael Lima --- Hi Colin, can you try with a more recent version of LO? The current fresh branch is in 7.3.4. You can also try 7.4 beta / 7.5 alpha. Let us know if the problem persists. Also, if you can provide a sample file, we can test if this is indeed a bug. Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=103381 [Bug 103381] [META] Pivot table (aka Data Pilot) bugs and enhancements -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 149481] Calc 7.3.x crashed when pasting from tsv, but only if I deleted the existing contents
https://bugs.documentfoundation.org/show_bug.cgi?id=149481 Rafael Lima changed: What|Removed |Added Ever confirmed|0 |1 Status|UNCONFIRMED |NEEDINFO --- Comment #4 from Rafael Lima --- (In reply to omui+libreoffice from comment #3) > I'll spin up a ubuntu and fedora vm to test and report back. Nice idea. Let us know of the results of your testing with Ubuntu/Fedora. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 137833] Image appears rotated when loaded in latest LO
https://bugs.documentfoundation.org/show_bug.cgi?id=137833 Timur changed: What|Removed |Added See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=14 ||6019 --- Comment #9 from Timur --- Insert is OK but Open in LO/Draw is not. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 149513] LibreOffice Draw 7.3 Navigator Drag broken + Crashes - Windows 10
https://bugs.documentfoundation.org/show_bug.cgi?id=149513 --- Comment #4 from Nico --- Haven't yet had the time to continue working on the file as some things came up urgently. Will try to get a "bugged" file for you as soon as I can. I did a quick run but when I tried to prepare the file by removing everything important like exact layouts or specific shapes and pictures and tried to regroup and safe, everything was fine after saving and closing. :/ It seems a bit impossible to always pinpoint it down to one thing. It's pretty annoying for me and I imagine for you guys too since it's hard to reproduce. I would love to send you guys the whole files but I cannot legally do so for GDPR reasons and company security. :C Also here is another Crash Report: https://crashreport.libreoffice.org/stats/crash_details/7dbe43dd-27ce-470c-8124-1eb6aaa7afc0 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 149563] FILEOPEN DOCX Table with negative indent appears incorrectly in section with negative top margin
https://bugs.documentfoundation.org/show_bug.cgi?id=149563 Rafael Lima changed: What|Removed |Added Ever confirmed|0 |1 Status|UNCONFIRMED |NEW --- Comment #2 from Rafael Lima --- Repro with Version: 7.5.0.0.alpha0+ / LibreOffice Community Build ID: 66b849eab05bb6b696cced84ca90c17ca1bc31dd CPU threads: 16; OS: Linux 5.13; UI render: default; VCL: kf5 (cairo+xcb) Locale: pt-BR (pt_BR.UTF-8); UI: en-US Calc: CL The first column is indeed too narrow and it's not possible to see the entire text in the column. Some of it is hidden to the left. Changing the frame position as described fixes the issue in this case, however it moves the entire table to the left. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 135890] Chart Properties Sidebar broken when chart is double-clicked before opening the sidebar
https://bugs.documentfoundation.org/show_bug.cgi?id=135890 Rafael Lima changed: What|Removed |Added See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=11 ||6838 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 116838] EDITING Not possible to edit chart from sidebar (steps on comment 4)
https://bugs.documentfoundation.org/show_bug.cgi?id=116838 Rafael Lima changed: What|Removed |Added See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=13 ||5890 CC||rafael.palma.l...@gmail.com --- Comment #10 from Rafael Lima --- Still repro with Version: 7.5.0.0.alpha0+ / LibreOffice Community Build ID: 66b849eab05bb6b696cced84ca90c17ca1bc31dd CPU threads: 16; OS: Linux 5.13; UI render: default; VCL: kf5 (cairo+xcb) Locale: pt-BR (pt_BR.UTF-8); UI: en-US Calc: CL This bug is also present from within Calc. See Bug 135890 which has a bisected report about this issue. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 149563] FILEOPEN DOCX Table with negative indent appears incorrectly in section with negative top margin
https://bugs.documentfoundation.org/show_bug.cgi?id=149563 --- Comment #1 from Gabor Kelemen (allotropia) --- Created attachment 180760 --> https://bugs.documentfoundation.org/attachment.cgi?id=180760=edit The example file in Word 2016 and Writer master -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 107334] [META] Chart wizard dialog issues
https://bugs.documentfoundation.org/show_bug.cgi?id=107334 Rafael Lima changed: What|Removed |Added Depends on||149561 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=149561 [Bug 149561] Chart type is not saved when an empty XY Scatter chart is created -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 149561] Chart type is not saved when an empty XY Scatter chart is created
https://bugs.documentfoundation.org/show_bug.cgi?id=149561 Rafael Lima changed: What|Removed |Added Summary|Calc change chart type if |Chart type is not saved |you create empty chart |when an empty XY Scatter ||chart is created Blocks||107334 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=107334 [Bug 107334] [META] Chart wizard dialog issues -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 149561] Calc change chart type if you create empty chart
https://bugs.documentfoundation.org/show_bug.cgi?id=149561 Rafael Lima changed: What|Removed |Added Ever confirmed|0 |1 CC||rafael.palma.l...@gmail.com Status|UNCONFIRMED |NEW --- Comment #1 from Rafael Lima --- Repro with Version: 7.5.0.0.alpha0+ / LibreOffice Community Build ID: 66b849eab05bb6b696cced84ca90c17ca1bc31dd CPU threads: 16; OS: Linux 5.13; UI render: default; VCL: kf5 (cairo+xcb) Locale: pt-BR (pt_BR.UTF-8); UI: en-US Calc: CL To reproduce: 1) Insert an empty chart by simply going to Insert - Chart and then XY (Scatter) and choose the "Lines Only" type. 2) Click Finish and deselect the chart 3) Double-click the newly inserted chart 4) Right-click and choose Chart Type 5) Notice that the option "Points and Lines" is selected instead of "Lines Only" Changing the chart type to "Points only" or "Lines only" using this dialog has no effect. Changing it to "3D Lines" will effectively change the chart type. But if you double-click it and then go to Chart Type, then the dialog will show no chart type selected, which is also a bug. Setting this to NEW. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 90534] FILEOPEN: The top/bottom margins and footer text in Pleading document do not match MS-Office layout
https://bugs.documentfoundation.org/show_bug.cgi?id=90534 Gabor Kelemen (allotropia) changed: What|Removed |Added See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=14 ||9563 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 104522] [META] DOCX (OOXML) header & footer-related issues
https://bugs.documentfoundation.org/show_bug.cgi?id=104522 Gabor Kelemen (allotropia) changed: What|Removed |Added Depends on||149563 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=149563 [Bug 149563] FILEOPEN DOCX Table with negative indent appears incorrectly in section with negative top margin -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 149563] New: FILEOPEN DOCX Table with negative indent appears incorrectly in section with negative top margin
https://bugs.documentfoundation.org/show_bug.cgi?id=149563 Bug ID: 149563 Summary: FILEOPEN DOCX Table with negative indent appears incorrectly in section with negative top margin Product: LibreOffice Version: 7.4.0.0 alpha0+ Master Hardware: All OS: All Status: UNCONFIRMED Severity: normal Priority: medium Component: Writer Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: kelem...@ubuntu.com Blocks: 104522 Created attachment 180759 --> https://bugs.documentfoundation.org/attachment.cgi?id=180759=edit Example file from Word 2016 Attached Word-made document has a table in the first page header, which is also set to have negative top page margin. The table has a negative 1 cm indent. Since the table is in a negative top page margin section, it is placed inside a text frame, since bug 119952 was fixed. However, the text frame does not take into account the tables negative indent, but the table inside does. This makes the left column of the table hidden under the left edge of the frame. 1, Open attached document 2, Notice the first three row of the table text show 1, 2, 3 instead of 11, 22, 33 Version: 7.5.0.0.alpha0+ (x64) / LibreOffice Community Build ID: c0e66cfab12d6c78d68af09498533362724dbd05 CPU threads: 14; OS: Windows 10.0 Build 19044; UI render: default; VCL: win Locale: en-US (hu_HU); UI: en-US Calc: threaded To make this match the layout better, the horizontal position of the frame should be "From Left" instead of "Left" and the "by" value should be the tables left indent, while the tables left indent should be 0. In Word, the negative indent of the table moves the table towards the left of the page, into the left margin. Of course this would be only a workaround, until the negative page margin feature is properly implemented - see https://bugs.documentfoundation.org/show_bug.cgi?id=119952#c2 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=104522 [Bug 104522] [META] DOCX (OOXML) header & footer-related issues -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 149554] CRASH: using empty transpose
https://bugs.documentfoundation.org/show_bug.cgi?id=149554 --- Comment #3 from Rafael Lima --- I have just tested using a build that comes after the patch and the problem is still there, but a bit differently: Steps to reproduce: 1) Select cells A1:C3 2) Ctrl + C 3) Ctrl + Shift + V (Paste special dialog opens) 4) Transpose All (runs ok the first time) 5) Press Ctrl + Shif + V again 5) Transpose All 6) Crash Version: 7.5.0.0.alpha0+ / LibreOffice Community Build ID: 66b849eab05bb6b696cced84ca90c17ca1bc31dd CPU threads: 16; 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 149544] Changing the anchor from 'to character' to 'to paragraph' of an shape doesn't update anchoring position (needs deselect and reselect of the shape)
https://bugs.documentfoundation.org/show_bug.cgi?id=149544 --- Comment #2 from Telesto --- Created attachment 180758 --> https://bugs.documentfoundation.org/attachment.cgi?id=180758=edit Example file -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 149562] Macros created in LO 7.3 Writer will crash LO 7.4 if the *.odt file was saved with password protection
https://bugs.documentfoundation.org/show_bug.cgi?id=149562 Xisco Faulí changed: What|Removed |Added Ever confirmed|0 |1 Status|UNCONFIRMED |NEEDINFO CC||xiscofa...@libreoffice.org --- Comment #4 from Xisco Faulí --- Thank you for reporting the bug. Please attach a sample document, as this makes it easier for us to verify the bug. I have set the bug's status to 'NEEDINFO'. Please change it back to 'UNCONFIRMED' once the requested document is provided. (Please note that the attachment will be public, remove any sensitive information before attaching it. See https://wiki.documentfoundation.org/QA/FAQ#How_can_I_eliminate_confidential_data_from_a_sample_document.3F for help on how to do so.) -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 149562] Macros created in LO 7.3 Writer will crash LO 7.4 if the *.odt file was saved with password protection
https://bugs.documentfoundation.org/show_bug.cgi?id=149562 --- Comment #3 from HTK300 --- Created attachment 180757 --> https://bugs.documentfoundation.org/attachment.cgi?id=180757=edit example of letter wizard dialog for letter wizard -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 149562] Macros created in LO 7.3 Writer will crash LO 7.4 if the *.odt file was saved with password protection
https://bugs.documentfoundation.org/show_bug.cgi?id=149562 --- Comment #2 from HTK300 --- Created attachment 180756 --> https://bugs.documentfoundation.org/attachment.cgi?id=180756=edit screenshot upon crash at file opening screenshot upon crash at file opening -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 149562] Macros created in LO 7.3 Writer will crash LO 7.4 if the *.odt file was saved with password protection
https://bugs.documentfoundation.org/show_bug.cgi?id=149562 --- Comment #1 from HTK300 --- Created attachment 180755 --> https://bugs.documentfoundation.org/attachment.cgi?id=180755=edit screenshot Macro message notification about macro being present in the file being opened -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 149562] New: Macros created in LO 7.3 Writer will crash LO 7.4 if the *.odt file was saved with password protection
https://bugs.documentfoundation.org/show_bug.cgi?id=149562 Bug ID: 149562 Summary: Macros created in LO 7.3 Writer will crash LO 7.4 if the *.odt file was saved with password protection Product: LibreOffice Version: 7.4.0.0 alpha0+ Master Hardware: x86-64 (AMD64) OS: Windows (All) Status: UNCONFIRMED Severity: normal Priority: medium Component: Writer Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: harry_the_kor...@web.de Description: a password protected WRITER file, that was created in LO 7.3xx using the Letter Wizard (personal, which creates MACROS within) will crash in Writer LO 7.4 reproducibly Steps to Reproduce: 1. Open LO7.3 and create a writer document using the Letter wizard 2. save the file with password protection 3. Open the password protected file (with macros disabled) in LO 7.4 4. Writer will ask for the password protection to be entered 5. a splash screen will pop up about the macros... 6. LO 7.4 will crash ! Actual Results: LO 7.4 will crash ! Expected Results: normally opening the previously password protected writer (including Macros, but disabled) file should be able to be editable. Reproducible: Always User Profile Reset: No Additional Info: see expected results.. -- 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 Hossein changed: What|Removed |Added Whiteboard|target:7.3.0 target:7.4.0 |target:7.3.0 target:7.4.0 ||reviewed:2022 --- Comment #34 from Hossein --- Re-evaluating the EasyHack in 2022 This task is still relevant, at it is can be a starting point for the newbies who want to start working with the code and submitting patches. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 137833] Image appears rotated when loaded in latest LO
https://bugs.documentfoundation.org/show_bug.cgi?id=137833 --- Comment #8 from Simo He --- This might be resolved since bug 146019 is solved -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 149453] Copy-paste with changes showing deletions
https://bugs.documentfoundation.org/show_bug.cgi?id=149453 Timur changed: What|Removed |Added Resolution|--- |DUPLICATE Status|UNCONFIRMED |RESOLVED --- Comment #10 from Timur --- This report is a duplicate. *** This bug has been marked as a duplicate of bug 134304 *** -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 134304] Copy and paste of tracking changes in writer should be implemented if both Track off
https://bugs.documentfoundation.org/show_bug.cgi?id=134304 Timur changed: What|Removed |Added CC||tnet...@gmail.com --- Comment #3 from Timur --- *** Bug 149453 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 134704] KDE5 - unable to dock sidebar by dragging frame
https://bugs.documentfoundation.org/show_bug.cgi?id=134704 Heiko Tietze changed: What|Removed |Added CC|libreoffice-ux-advise@lists |heiko.tietze@documentfounda |.freedesktop.org|tion.org Keywords|needsUXEval | --- Comment #11 from Heiko Tietze --- (In reply to Jan-Marek Glogowski from comment #10) > Docking is a property of the Window type Feel free to resolve WF. User expectation and UX statement is clear: redocking is expected. And I suggest to realize it per pull down menu as done for the sidebar. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 72994] Make the same logic for Goal Seek and Solver tools from end-user perspective
https://bugs.documentfoundation.org/show_bug.cgi?id=72994 --- Comment #16 from Mary Lane --- The code starts by finding the current position of the user's eyes, then uses this information to calculate which direction they are looking in. To get more assistance, go to: https://www.onlineessayshelp.co.uk/essay-writing-service/ -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 134704] KDE5 - unable to dock sidebar by dragging frame
https://bugs.documentfoundation.org/show_bug.cgi?id=134704 --- Comment #10 from Jan-Marek Glogowski --- (In reply to Heiko Tietze from comment #9) > (In reply to Jan-Marek Glogowski from comment #8) > > Quoting from the commit message: > > > > (134704) not fixed, because the sidebar window is now a dialog, which is > > not dockable. FWIW the same has happened to the Navigator (F5), which > > also renders it non-dockable. No idea, if this is an intentional change. > > > > It's, easy to see the difference for toolbars... > > > > - Maybe this is intentional and can now be closed as WONTFIX? > > - Maybe UX has some additional general input? > > The sidebar is typically docked and thus users expect redocking. Works via > the context menu but the Navigator does not have it. Ideally we add a button > to the dialog interactions. Btw. maximizing the (undocked) sidebar is > pointless. Yup, I'm aware. But previously you could dock the Navigator with the mouse, just like toolbars. This is not possible anymore. You can not dock the Navigator and just re-dock the sidebar via the menu command. I don't know if it was possible to dock the sidebar on the left side, for example. Docking is a property of the Window type, and with both being dialogs, that is not possible anymore by moving them into docking areas with the mouse (where you see the rectangles showing up in the main window). -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 147436] Certain changes remain in track & changes record even after undo of every change
https://bugs.documentfoundation.org/show_bug.cgi?id=147436 Amalia Constantin changed: What|Removed |Added Attachment #180754|Track changes video |Track changes issue description|| -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 139668] Anchor to paragraph not included in selection when selecting a full paragraph
https://bugs.documentfoundation.org/show_bug.cgi?id=139668 Michael Stahl (allotropia) changed: What|Removed |Added See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=13 ||9057 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 139057] Image to character/paragraph at the end or beginning of a paragraph isn't included in a single line section
https://bugs.documentfoundation.org/show_bug.cgi?id=139057 Michael Stahl (allotropia) changed: What|Removed |Added Resolution|--- |WONTFIX See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=13 ||9668 Status|NEW |RESOLVED --- Comment #8 from Michael Stahl (allotropia) --- yep, the image anchored at the edge of a section will be selected only if the selection spans multiple paragraphs. but this is already the case if it's anchored at the end of any paragraph, the difference is just that in this case you can't extend the selection in the direction where the image is anchored, because there's nowhere to go, you have to extend it in the *other* direction. i don't think there's an easy tweak to this that preserves the API compatibility that comment#4 is about, and it's a rather minor problem, you can always click on the image to delete it that way. so i guess it could be NOTABUG or WONTFIX... -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 147436] Certain changes remain in track & changes record even after undo of every change
https://bugs.documentfoundation.org/show_bug.cgi?id=147436 Amalia Constantin changed: What|Removed |Added Attachment #180754|Track changes video.wmv |Track changes issue.wmv filename|| -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 147436] Certain changes remain in track & changes record even after undo of every change
https://bugs.documentfoundation.org/show_bug.cgi?id=147436 Amalia Constantin changed: What|Removed |Added Attachment #180753|0 |1 is obsolete|| --- Comment #7 from Amalia Constantin --- Created attachment 180754 --> https://bugs.documentfoundation.org/attachment.cgi?id=180754=edit Track changes video -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 148868] Quirk when changing the first character after a picture in a table
https://bugs.documentfoundation.org/show_bug.cgi?id=148868 Michael Stahl (allotropia) changed: What|Removed |Added See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=13 ||3957 Assignee|libreoffice-b...@lists.free |michael.st...@allotropia.de |desktop.org | Resolution|--- |FIXED Status|NEW |RESOLVED --- Comment #6 from Michael Stahl (allotropia) --- i'm not sure if this is a bug or not, but with the fix done for bug 133957 it's now relatively easy to special-case this. on the one hand i find it a little inconsistent when a deletion doesn't delete everything that's selected. on the other hand, there are convenient shortcuts to select short pieces of text such as by double clicking on a word, in order to replace the text by typing, and in that case it's inconvenient to delete the image. so let's try this out, interpret selection from the UI within one paragraph then typing similar to "Replace"; if selection spans multiple paragraph nothing changes. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 147436] Certain changes remain in track & changes record even after undo of every change
https://bugs.documentfoundation.org/show_bug.cgi?id=147436 --- Comment #6 from Amalia Constantin --- I was able to reproduce the issue, by following the steps in the screencast video: undo action is not able to clear the text formatting introduced by the tracked changes. Additionally I would make the following notes: - The issue is easily reproduced starting also with a new text document as seen in the attached video Track changes issue.mp4. - Having bold as default setting for tracking changes to attributes can be misleading when the user does make other text format changes (italic or underline) and does not expect the text to be bolded - also the ribbon does not reflect the bold attribute, while the text is displayed as bolded. I would recommend reassessing this option or its implementation having Microsoft Word as reference. - Additionally if clone formatting is used between text with the same format attributes, LibreOffice signals the formatted text as changed, even if no change has been applied due to the clone formatting. I would reference Microsoft Word for this use case, where the software is capable of recognizing whether a text attribute has been in fact changed or not as a consequence of user actions. Please see the attached video for reference. Reproduced on the configuration below: Version: 7.3.4.2 (x64) / LibreOffice Community Build ID: 728fec16bd5f605073805c3c9e7c4212a0120dc5 CPU threads: 16; OS: Windows 10.0 Build 19044; UI render: Skia/Vulkan; VCL: win Locale: en-US (en_US); UI: en-US Calc: CL -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 147436] Certain changes remain in track & changes record even after undo of every change
https://bugs.documentfoundation.org/show_bug.cgi?id=147436 --- Comment #5 from Amalia Constantin --- Created attachment 180753 --> https://bugs.documentfoundation.org/attachment.cgi?id=180753=edit Video with reproducing steps for track changes issue -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 149332] Writer choose the wrong language for text I type
https://bugs.documentfoundation.org/show_bug.cgi?id=149332 --- Comment #9 from Mike Kaganski --- Created attachment 180752 --> https://bugs.documentfoundation.org/attachment.cgi?id=180752=edit Adding a Spanish layout for Windows language on Windows 10 (In reply to Francesco from comment #8) > You continue to close this; I don't agree but i don't want to do ping pong. Thanks for that. > >you can use *any* keyboard layout with any input language > How? How many people know/can do that? It is an operating system feature. And the operating system documentation is not something to be discussed in LibreOffice bug report. However, *if needed*, we can indeed create some wiki; if you feel it would be good, you are welcome to create such a wiki page. For instance, on Windows 10, you can add languages in Language Preferences system applet, and there, you "add a keyboard", where you choose the layout you need. See the attachment. > I have a multilingual keyboard but > Writer recognize it as "Polish" and underlines in red any word wrote in a > different language different than polish. Because according to Writer > anything I write using that input keyboard MUST be polish or underlined. No, according to Writer, the *keyboard* is irrelevant, but the *input language* matters. > And what about the languages without a keyboard layout? the problem is still > present (local languages, or others as Esperanto) How? The user would want to have *some* existing keyboard layout. Assigning the *wanted* keyboard layout for the language could be possible. And even in case when there is no *input language* like that (note that Esperanto is indeed among the languages list e.g. on Windows), there is the mentioned *setting* to not use the system input language in LibreOffice. The configuration is there in place; the real proportion of users with "local languages" not covered by the existing OS options is definitely less than number of those who are covered, so the default setting as it is now makes perfect sense. > And what about bilingual documents? I get crazy with them. The feature is *exactly* for bi- (tri-, ...) lingual document. You set up as many input languages in your system as you want; and then you use the OS key combination to switch the input language (from Spanish to English when you start writing in English; then from English to Spanish, when you switch back) - and Writer does everything to mark the text with the proper language. It only needs the proper input language setup; and note that everyone in the world /except/ for some Roman-language users who use several Roman languages that happen to have a keyboard layout that fits them all may feel it unusual; every Cyrillic, or Asian, or Arabic speaking user would already have the layouts together with input languages set up in the system. For Roman language speakers, the only difference would be that their input languages would share the same layout. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 149453] Copy-paste with changes showing deletions
https://bugs.documentfoundation.org/show_bug.cgi?id=149453 --- Comment #9 from ThomasU --- Thanks. After struggling a while I found out that the SW_DEBUG=1 "environment variable" should not be defined in the bash environment of the terminal I use to launch LibreOffice but rather in the soffice command line. I needed more precise instructions. I'm not in the same world as yours! What's needed on the command line is: /opt/libreofficedev7.3/program/swriter -env:SW_DEBUG=1 Your F12 is based on what is described on line 25 of: https://cgit.freedesktop.org/libreoffice/core/tree/sw/qa/extras/README Then I type " " Enter tracking mode Delete which becomes striked out Then type F12 Then files nodes.xml and layout.xml get dumped in the folder where I started swriter. Then on line 270 of nodes.xml I see: I've attached layout.xml -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 149453] Copy-paste with changes showing deletions
https://bugs.documentfoundation.org/show_bug.cgi?id=149453 --- Comment #8 from ThomasU --- Created attachment 180751 --> https://bugs.documentfoundation.org/attachment.cgi?id=180751=edit layout.xml -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 45763] 237 pages complex .doc file hang when trying to open
https://bugs.documentfoundation.org/show_bug.cgi?id=45763 Timur changed: What|Removed |Added CC||l.lu...@collabora.com --- Comment #32 from Timur --- Some improvement in 7.4 repo: from 760,33s user 1,48s system 99% cpu 12:44,19 total to411,96s user 1,27s system 99% cpu 6:55,83 total commit 86039563de87149a01ffb980b5ec99074b98fd5e author Luboš Luňák May 14 2022 std::stable_sort() where libc++ debug mode breaks a unittest Adding Luboš here to see this unexpected? improvement for opening DOC. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 149332] Writer choose the wrong language for text I type
https://bugs.documentfoundation.org/show_bug.cgi?id=149332 --- Comment #8 from Francesco --- You continue to close this; I don't agree but i don't want to do ping pong. >you can use *any* keyboard layout with any input language How? How many people know/can do that? I have a multilingual keyboard but Writer recognize it as "Polish" and underlines in red any word wrote in a different language different than polish. Because according to Writer anything I write using that input keyboard MUST be polish or underlined. And what about the languages without a keyboard layout? the problem is still present (local languages, or others as Esperanto) And what about bilingual documents? I get crazy with them. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 133092] [META] Crash bugs
https://bugs.documentfoundation.org/show_bug.cgi?id=133092 Bug 133092 depends on bug 149507, which changed state. Bug 149507 Summary: CRASH: pasting and undoing https://bugs.documentfoundation.org/show_bug.cgi?id=149507 What|Removed |Added Status|NEW |RESOLVED Resolution|--- |FIXED -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 149507] CRASH: pasting and undoing
https://bugs.documentfoundation.org/show_bug.cgi?id=149507 Michael Stahl (allotropia) changed: What|Removed |Added Status|NEW |RESOLVED Assignee|libreoffice-b...@lists.free |michael.st...@allotropia.de |desktop.org | Resolution|--- |FIXED --- Comment #4 from Michael Stahl (allotropia) --- fixed on master -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 98743] TIFF EXPORT saves weird image: in different x-y resolution and dimensions
https://bugs.documentfoundation.org/show_bug.cgi?id=98743 --- Comment #24 from xordevore...@gmail.com --- Created attachment 180750 --> https://bugs.documentfoundation.org/attachment.cgi?id=180750=edit original bug report's file, exported as a tif from paint.net Paint.net uses three parameters with TIF exports: a dithering level (1 to 8) bit depth (1, 4, 8, 24, 32) and a quantization algorithm dependent on selected bit depth (Median Cut, Octree) With me using paint.net's auto-detect setting, paint.net selected Octree for the algorithm and a dithering level of 7 when re-saving the original bug reporter's attachment as a TIF file. Paint.net forces use of the octree quantization algorithm for bit depths 24 and 32, and the user is given the choice between octree and median cut for depths 1, 4, and 8, but does not report on the UI what the actual bit depth was if set to auto-detect (but because Octree was defaulted, the auto-detected bit depth had to be either 24 or 32). Wild guess here, perhaps the engine you're using for the TIF export is not reporting everything it's implementing during the export process and is locked to a particular export format, or is using an optimization algorithm other than the one paint.net is using (which wouldn't of itself be a bug, just a different approaching to performing the export). I did not see any visual difference between the original and paint.net's export, so I'm not sure what information got lost between the original's 417K and paint.net's 277K export. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 108908] [META] Visual Basic for Applications (VBA) macro issues
https://bugs.documentfoundation.org/show_bug.cgi?id=108908 Bug 108908 depends on bug 149531, which changed state. Bug 149531 Summary: Excel Visual Basic compatibility issue in LibreOffice Calc: .Delete https://bugs.documentfoundation.org/show_bug.cgi?id=149531 What|Removed |Added Status|ASSIGNED|RESOLVED Resolution|--- |FIXED -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 149507] CRASH: pasting and undoing
https://bugs.documentfoundation.org/show_bug.cgi?id=149507 --- Comment #3 from Commit Notification --- Michael Stahl committed a patch related to this issue. It has been pushed to "master": https://git.libreoffice.org/core/commit/6de844c5da695bf4605bef5510d33e74a7ff04ee tdf#149507 sw: don't delete bookmarks in SwUndoInsLayFormat::UndoImpl() 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 149507] CRASH: pasting and undoing
https://bugs.documentfoundation.org/show_bug.cgi?id=149507 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 53027] EDITING: dBase-Import-Wizard fails when trying to append DECIMAL(NUMERIC) and BOOLEAN data types
https://bugs.documentfoundation.org/show_bug.cgi?id=53027 --- Comment #59 from themagus1...@gmail.com --- https://www.techsmoothy.com/polygon-price-prediction-2025/ -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 147791] Add UNO command to "Print Current Page Directly"
https://bugs.documentfoundation.org/show_bug.cgi?id=147791 --- Comment #9 from mkass...@internode.net --- I am unable to do this myself, and am hoping that someone else can do this task. A previous poster said it was an 'easy hack' to do. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 147791] Add UNO command to "Print Current Page Directly"
https://bugs.documentfoundation.org/show_bug.cgi?id=147791 --- Comment #8 from mkass...@internode.net --- I am unable to do this myself, and am hoping that someone else can do this task. A previous poster said it was an 'easy hack' to do. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 149554] CRASH: using empty transpose
https://bugs.documentfoundation.org/show_bug.cgi?id=149554 --- Comment #2 from Commit Notification --- Luboš Luňák committed a patch related to this issue. It has been pushed to "master": https://git.libreoffice.org/core/commit/ef1be22efb3e1625da1683ea98392cc41657b1cd allocate columns in ScTable::TransposeClip() (tdf#149554) 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 149554] CRASH: using empty transpose
https://bugs.documentfoundation.org/show_bug.cgi?id=149554 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 149561] New: Calc change chart type if you create empty chart
https://bugs.documentfoundation.org/show_bug.cgi?id=149561 Bug ID: 149561 Summary: Calc change chart type if you create empty chart Product: LibreOffice Version: 7.3.4.2 release Hardware: All OS: All Status: UNCONFIRMED Severity: normal Priority: medium Component: Calc Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: triongh...@gmail.com I'm trying to add empty chart: Insert -> Chart -> XY (scatter) -> Lines Only -> Finish Result: calc create chart with type "Points and Lines". Same for any type of charts (calc cteates empty chart with wrong type). This bug persists for a long time. It can be minor unnoying bug but sometimes if you build chart with many rows and with different positions of names and data in sheets, it randomly broke the wholl chart if you trying to change it's type afterwards. P.S. And creating chart through Chart Wizard never work for me, because my sheets always have splited X's and Y's so I always create empty charts and than add data raws/columns manually. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 143249] UI: Improve handling of configuring table borders in table properties dialog (to make it work for multiple workflows)
https://bugs.documentfoundation.org/show_bug.cgi?id=143249 --- Comment #35 from Heiko Tietze --- Created attachment 180749 --> https://bugs.documentfoundation.org/attachment.cgi?id=180749=edit Mockup #2 Coming back to this topic. I think we agree on the general layout. Regina mentioned that we have 12 border lines in total (depending on single/multi selection) and Telesto is unhappy with the workflow. In fact there are two scenarios: a) (most common) apply the same attributes for some borders such as the surrounding edges, and b) set individual attributes (for example red on top, blue on bottom). This second mockup shows two alternatives. First we could present toggle buttons for all 12 options plus some combined defaults. This makes the UI quite busy. So I wonder if we allow to set attributes for a few common combinations (similar to what we have today as Presets) and have all individual settings accessible per dropdown. To deal with the potentially large dialog I suggest to place Padding and Shadow (forgot to change the label Width to Distance) into expanders and use a scrollbox for the attributes. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 149556] OOXML Better support of element in Writer table
https://bugs.documentfoundation.org/show_bug.cgi?id=149556 --- Comment #5 from Regina Henschel --- No, I do not plan to work on it, because I will stay in areas with shapes, where I more familiar with. It should be possible to map the short form of the attribute values to the long form on import. That is likely an easyHack. Writing out the short form on export is currently not good. That should only be done, when reading is implemented in all active versions and in the last "end of life" version. Because LO does not write strict OOXML, where it would be necessary, a change in the export filter is not urgent. I consider fixing the errors in the long form of the attribute values not an easyHack. It does not only need changes in the import and export filters but likely in the rendering engine too. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 149560] Excel Visual Basic compatibility issue in LibreOffice Calc: Round trip produces a corrupt xls file
https://bugs.documentfoundation.org/show_bug.cgi?id=149560 Óvári changed: What|Removed |Added See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=14 ||9325 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 149560] Excel Visual Basic compatibility issue in LibreOffice Calc: Round trip produces a corrupt xls file
https://bugs.documentfoundation.org/show_bug.cgi?id=149560 --- Comment #3 from Óvári --- Created attachment 180748 --> https://bugs.documentfoundation.org/attachment.cgi?id=180748=edit button2macroback.xls -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 149560] Excel Visual Basic compatibility issue in LibreOffice Calc: Round trip produces a corrupt xls file
https://bugs.documentfoundation.org/show_bug.cgi?id=149560 --- Comment #2 from Óvári --- Created attachment 180747 --> https://bugs.documentfoundation.org/attachment.cgi?id=180747=edit button2macro.ods -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 149560] Excel Visual Basic compatibility issue in LibreOffice Calc: Round trip produces a corrupt xls file
https://bugs.documentfoundation.org/show_bug.cgi?id=149560 --- Comment #1 from Óvári --- Created attachment 180746 --> https://bugs.documentfoundation.org/attachment.cgi?id=180746=edit button2macro.xls -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 108908] [META] Visual Basic for Applications (VBA) macro issues
https://bugs.documentfoundation.org/show_bug.cgi?id=108908 Óvári changed: What|Removed |Added Depends on||149560 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=149560 [Bug 149560] Excel Visual Basic compatibility issue in LibreOffice Calc: Round trip produces a corrupt xls file -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 149560] Excel Visual Basic compatibility issue in LibreOffice Calc: Round trip produces a corrupt xls file
https://bugs.documentfoundation.org/show_bug.cgi?id=149560 Óvári changed: What|Removed |Added Blocks||108908 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=108908 [Bug 108908] [META] Visual Basic for Applications (VBA) macro issues -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 149560] New: Excel Visual Basic compatibility issue in LibreOffice Calc: Round trip produces a corrupt xls file
https://bugs.documentfoundation.org/show_bug.cgi?id=149560 Bug ID: 149560 Summary: Excel Visual Basic compatibility issue in LibreOffice Calc: Round trip produces a corrupt xls file Product: LibreOffice Version: 7.3.4.2 release Hardware: All OS: All Status: UNCONFIRMED Severity: normal Priority: medium Component: Calc Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: ovari...@zoho.com Description: Using LibreOffice Calc, a round trip from .xls to .ods to .xls doesn't work for a Excel spreadsheet with a simple button which runs a subroutine that shows a message box. Steps to Reproduce: An Excel button2macro.xls spreadsheet file with a button that runs macro MsgBox "Hello World!" With LibreOffice Calc, save the button2macro.xls file as button2macro.ods. Clicking the "Button 1" shows the "Hello World!" dialog box. Close LibreOffice. With LibreOffice Calc, save the button2macro.ods file as button2macroback.xls. Open the button2macroback.xls with Microsoft Excel 2010 and a dialog shows with a message: ``` Office has detected a problem with this file. To help protect your computer this file cannot be opened. ``` LibreOffice Calc 7.3.4.2 opens the button2macroback.xls file and it works most of the time; however, there was a time when the file opened and the button was clicked and it didn't work with the message: ``` A Scripting Framework error occurred while running the UNKNOWN script UNKNOWN. Message: Incorrecct format for Script URI: /run/build/libreoffice/scripting/source/provider/MasterScriptProvider.css:238 ``` Perhaps the MasterScriptProvider.css:238 can help with finding a solution so a round trip of a VBA file is achievable. Actual Results: Open the button2macroback.xls with Microsoft Excel 2010 and a dialog shows with a message: ``` Office has detected a problem with this file. To help protect your computer this file cannot be opened. ``` Expected Results: The button2macroback.xls spreadsheet file should be able to be opened with Microsoft Excel 2010. Reproducible: Always User Profile Reset: No Additional Info: The Excel button2macro.xls spreadsheet file will be attached as later as unsure how to attach it now. Will help with bug 149325. Thank you -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 149332] Writer choose the wrong language for text I type
https://bugs.documentfoundation.org/show_bug.cgi?id=149332 Mike Kaganski changed: What|Removed |Added Resolution|--- |NOTABUG Status|REOPENED|RESOLVED --- Comment #7 from Mike Kaganski --- (In reply to Francesco from comment #5) Sorry, obviously missed this. Replying now. > A general case of mine is *very common*, because often with a keyboard you > can write more than one language. > Let's take English as example: if anybody should write a document in English > and has Spanish (French, Finnish, Polish, Ungarian ...) keyboard. > In any program (with exception of Writer) (s)he could just start typing, > because the *Spanish keyboard includes all English letters* by default. > But not in Writer, because even if the text is in correct english and the > document is in English, the text will be underlined. > > So you want to force spanish-speaker people to install two layouts if they > dont' want that correct text is underlined? No. You likely missed that you can use *any* keyboard layout with any input language; so if you are OK with Spanish keyboard, just add a new input language (English), *with the same Spanish keyboard layout*, and only change the input language. > But the user *decided* that the document is in a given language, and set it > to *that* language. The feature is exactly to make this "set it to that language" unneeded, because that setting would happen upon input language change automatically. But if the user insists that they prefer to use manual setting, they are free to disable application of system input language. No, this should not be removed; and there is the configuration for this. This is not a bug. This is closed as such. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 108908] [META] Visual Basic for Applications (VBA) macro issues
https://bugs.documentfoundation.org/show_bug.cgi?id=108908 Óvári changed: What|Removed |Added Depends on||149559 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=149559 [Bug 149559] Excel Visual Basic compatibility issue in LibreOffice Calc: Application.ScreenUpdating = False does not always work -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 149559] Excel Visual Basic compatibility issue in LibreOffice Calc: Application.ScreenUpdating = False does not always work
https://bugs.documentfoundation.org/show_bug.cgi?id=149559 Óvári changed: What|Removed |Added Blocks||108908 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=108908 [Bug 108908] [META] Visual Basic for Applications (VBA) macro issues -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 149556] OOXML Better support of element in Writer table
https://bugs.documentfoundation.org/show_bug.cgi?id=149556 Xisco Faulí changed: What|Removed |Added Status|UNCONFIRMED |NEW Ever confirmed|0 |1 --- Comment #4 from Xisco Faulí --- Moving to NEW. @Regina, do you plan to work on it ? Otherwise, do you think this could be turned into an easyhack ? -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 149556] OOXML Better support of element in Writer table
https://bugs.documentfoundation.org/show_bug.cgi?id=149556 Xisco Faulí changed: What|Removed |Added Hardware|x86-64 (AMD64) |All CC||xiscofa...@libreoffice.org OS|BSD (Others)|All -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 43100] EDITING: It is better for spaces at the end of line to cause a new line
https://bugs.documentfoundation.org/show_bug.cgi?id=43100 Attila Szűcs changed: What|Removed |Added Status|NEW |ASSIGNED Assignee|libreoffice-b...@lists.free |szucs.atti...@nisz.hu |desktop.org | -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 120715] Cursor doesn't move forward on typing space at the end of .docx file when text is centered
https://bugs.documentfoundation.org/show_bug.cgi?id=120715 Attila Szűcs changed: What|Removed |Added Assignee|libreoffice-b...@lists.free |szucs.atti...@nisz.hu |desktop.org | Status|NEW |ASSIGNED -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 104683] Show nonprinting characters: show spaces at the end of the line before break line for justified
https://bugs.documentfoundation.org/show_bug.cgi?id=104683 Attila Szűcs changed: What|Removed |Added Assignee|libreoffice-b...@lists.free |szucs.atti...@nisz.hu |desktop.org | Status|NEW |ASSIGNED -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 149555] Section header ignored (multiple headers + table of contents)
https://bugs.documentfoundation.org/show_bug.cgi?id=149555 Timur changed: What|Removed |Added Regression By||Michael Stahl CC||michael.st...@allotropia.de Keywords||bibisected, bisected, ||filter:docx, regression --- Comment #1 from Timur --- DOCX is MSO created. Regression in 7.2. 4 pages and correct header went to 5 pages and wrong header. sha:7ab349296dac79dad3fec09f60348efcbb9ea17e author Michael Stahl Fri Nov 20 2020 sw: fix copying and deleting of section content via API Michael, please see. Commit is not in other reports. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 149555] Section header ignored (multiple headers + table of contents)
https://bugs.documentfoundation.org/show_bug.cgi?id=149555 Timur changed: What|Removed |Added Ever confirmed|0 |1 Status|UNCONFIRMED |NEW -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 147130] CRASH - Collabora Office SIGABRT - seemingly random crashes on startup
https://bugs.documentfoundation.org/show_bug.cgi?id=147130 --- Comment #3 from Alex Thurgood --- Although I'm not surprised by the "purge" currently being carried out given the tensions between some members of the Board, once can't really tell people to report bugs about Collabora Productivity for several years to the LibreOffice BZ instance, and then simply cancel the reports as NOTOURBUG, absent some policy decision taken by the Board/ESC to no longer accept them. Additionally, there is currently no mechanism for reporting bugs about Collabora Productivity to Collabora - the github issues page is for CollaboraOnline, and the LibreOffice for Android still points to LO BZ for report bugs. A consistent approach is required. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 149547] Writer creates a new character style named "__XXX___invalid" on its own
https://bugs.documentfoundation.org/show_bug.cgi?id=149547 Timur changed: What|Removed |Added Severity|normal |minor -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 149547] Writer creates a new character style named "__XXX___invalid" on its own
https://bugs.documentfoundation.org/show_bug.cgi?id=149547 Timur changed: What|Removed |Added Ever confirmed|0 |1 Status|UNCONFIRMED |NEEDINFO -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 149542] "Save As" dlg doesn't persist window size change
https://bugs.documentfoundation.org/show_bug.cgi?id=149542 Timur changed: What|Removed |Added Ever confirmed|0 |1 Status|UNCONFIRMED |NEEDINFO -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 147336] Collabora Office - Localized help not installed message, yet not possible to install separate localized help
https://bugs.documentfoundation.org/show_bug.cgi?id=147336 --- Comment #4 from Alex Thurgood --- Although I'm not surprised by the "purge" currently being carried out given the tensions between some members of the Board, once can't really tell people to report bugs about Collabora Productivity for several years to the LibreOffice BZ instance, and then simply cancel the reports as NOTOURBUG, absent some policy decision taken by the Board/ESC to no longer accept them. Additionally, there is currently no mechanism for reporting bugs about Collabora Productivity to Collabora - the github issues page is for CollaboraOnline, and the LibreOffice for Android still points to LO BZ for report bugs. A consistent approach is required. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 149332] Writer choose the wrong language for text I type
https://bugs.documentfoundation.org/show_bug.cgi?id=149332 Francesco changed: What|Removed |Added Resolution|NOTABUG |--- Status|RESOLVED|REOPENED Ever confirmed|0 |1 --- Comment #6 from Francesco --- Can this task be reopen considering my comment 5? It's not a bug but more something as a feature request/change but I wrote bug then, just because I didn't have other better options. My example: consider an user who starts writing a document in English and has Spanish (French, Finnish, Polish, Ungarian ...) keyboard. Does (s)he have to install English keyboard, considering that the English alphabet is already included in keyboard of his native language? Having a double keyboard is always a problem, my example was about a more complex situation, but now i notice the problem is even more common: when a keyboard can write more than one language, the problem starts. Examples: * by using most keyboards you can write english * by using French keyboard you can write Italian * in Linux, by using most keyboards you can write esperanto In addition, some languages don't have a keyboard in some OS (for example esperanto in Windows, but also many dialects with a dictionary in Word). Please understand the problem. Again, maybe it's not a bug, if you can you can change its category, but it should be reopen and considered more seriously. Dankon/Grazie/Thanks -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 149471] DOCX: Word header content with convert-to PDF on Linux has fidelity issues
https://bugs.documentfoundation.org/show_bug.cgi?id=149471 --- Comment #11 from Timur --- You can also try to embed fonts in a file. Embedding has it's own bugs. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 149547] Writer creates a new character style named "__XXX___invalid" on its own
https://bugs.documentfoundation.org/show_bug.cgi?id=149547 --- Comment #3 from Timur --- Does this happen only with a specific file? Can you attach it, if not personal? -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 147336] Collabora Office - Localized help not installed message, yet not possible to install separate localized help
https://bugs.documentfoundation.org/show_bug.cgi?id=147336 Alex Thurgood changed: What|Removed |Added Status|RESOLVED|NEW Resolution|NOTOURBUG |--- Ever confirmed|0 |1 --- Comment #3 from Alex Thurgood --- (In reply to Adolfo Jayme Barrientos from comment #2) > Please: Collabora bugs should be reported to Collabora. When was this policy change adopted by the Board / ESC, I don't recall having seen anything in recent discussions. If there has been a policy change, please indicate the minutes where this was decided. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 149549] recent files list deleted
https://bugs.documentfoundation.org/show_bug.cgi?id=149549 Timur changed: What|Removed |Added Priority|medium |lowest Ever confirmed|0 |1 Severity|normal |trivial Status|UNCONFIRMED |NEEDINFO --- Comment #1 from Timur --- Update from whiuch to which version? Bug makes sense only if reproducible. Did it happen to you multiple times? Which folders do you find in C:\Users\\Application Data\LibreOffice\ , which one has "user" ? -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 149471] DOCX: Word header content with convert-to PDF on Linux has fidelity issues
https://bugs.documentfoundation.org/show_bug.cgi?id=149471 Timur changed: What|Removed |Added Resolution|--- |NOTABUG Status|UNCONFIRMED |RESOLVED --- Comment #10 from Timur --- I mark NotABug. We now don't even know what substitute is, bug 61134. With font replacement, beware of bug 43185. I see a number of proposals, as https://graphicdesign.stackexchange.com/questions/21969/trebuchet-ms-web-font-alternatives. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 149557] UI popup (context) menus are shown neither in Calc nor in Writer
https://bugs.documentfoundation.org/show_bug.cgi?id=149557 Julien Nabet changed: What|Removed |Added Resolution|--- |DUPLICATE Status|UNCONFIRMED |RESOLVED --- Comment #1 from Julien Nabet --- *** This bug has been marked as a duplicate of bug 149537 *** -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 149453] Copy-paste with changes showing deletions
https://bugs.documentfoundation.org/show_bug.cgi?id=149453 --- Comment #7 from Miklos Vajna --- > To be more precise, the problem is about text selection. Hm, how did you arrive to that conclusion? If you create a selection that contains deleted (but visible) text and you follow the instructions from comment 2 to enable the debug xml dump, then F12 will show you that the selection contains the deleted text (look for m_pCurrentCursor in layout.xml, the length of the selection is visible from the point and mark's content index), I expect that the copying is at fault. Please use the code pointer from comment 2 and do a bit of research yourself before asking more questions. Thanks. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 149542] "Save As" dlg doesn't persist window size change
https://bugs.documentfoundation.org/show_bug.cgi?id=149542 Timur changed: What|Removed |Added Ever confirmed|1 |0 Status|REOPENED|UNCONFIRMED --- Comment #3 from Timur --- I don't reproduce. Can you attach a small screencast? -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 149399] Start center font for LO modules went slim in 7.4+
https://bugs.documentfoundation.org/show_bug.cgi?id=149399 --- Comment #8 from Timur --- (In reply to Heiko Tietze from comment #4) > (In reply to Timur from comment #3) > > Hardly visible... > Can look into the bold idea. At least for Writer, Calc not for Document, Spreadsheet. I don't know what more to say than hardly visible and unpleasantly tiny. I'd rather see an option here. That's philosophy I guess "why option for all".. because it's better to have an option for those with small screen than to have a single solution that's probably inconvenient for a majority of users. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 149490] multiple copies of dialogs can be opened from undocked toolbars
https://bugs.documentfoundation.org/show_bug.cgi?id=149490 sdc.bla...@youmail.dk changed: What|Removed |Added CC||tele...@surfxs.nl --- Comment #11 from sdc.bla...@youmail.dk --- (In reply to Caolán McNamara from comment #7) > the rest is then the general case that under "gen" modal dialogs don't lock > floating toolbars? while it does lock under gtk3/kf5. Do we know if this was > always the case or was there a time in the past when it was not true? cc: @Telesto -- can you help with testing earlier versions of LO. For example, with an undocked "Image" or "Frame" toolbar, click on the "Properties" icon and see if you get a new copy of the Properties dialog, each time you click the icon. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 149540] Optimal wrap behaves oddly (likely because original image size being larger compared to in document size))
https://bugs.documentfoundation.org/show_bug.cgi?id=149540 --- Comment #4 from sdc.bla...@youmail.dk --- Can reproduce the observed behavior, but probably NAB My explanation. 1. Initial state: Image is 7.69cm "from left" of "Entire Paragraph Area". 2. Left arrow: Image is now positioned 7.35 cm "from left" of "Entire Paragraph Area". 3. According to: https://help.libreoffice.org/7.4/en-US/text/swriter/01/05060200.html?DbPAR=WRITER=.uno:WrapIdeal#bm_id3150462 Optimal Wrap: "Automatically wraps text to the left, to the right, or on all four sides of the border frame of the object." When you moved the image "left", it could no longer keep 7.69cm and Optimal Wrap, so it moved the image to where it did not overlap (7.35cm from left of Entire Paragraph Area) If "Through" or "Parallel" wrap is used, for example, then no problem to move with left arrow. Additional tests. 1. Place the image further to the right, then it is possible to use the left arrow, with no jump (until the image gets to a certain place, where it cannot keep the "from left" horizontal positioning). 2. Can reproduce same behavior with "to paragraph" anchoring. These "toy" cases might not be a good way to test this behavior. Better to have an actual positioning task, and see if appropriate positioning options can be chosen. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 149399] Start center font for LO modules went slim in 7.4+
https://bugs.documentfoundation.org/show_bug.cgi?id=149399 --- Comment #7 from Heiko Tietze --- (In reply to Telesto from comment #6) > It's to small for me taste.. Font was scaled to 140% and is now at 120%. I wonder if your taste is truly affected or if you are just allergic to changes. Disclaimer: please take this positively, same happens to me all the time. If you have arguments I could try to find a solution. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 148255] LibreOffice Writer: Text "disappears" while writing between two formulas that are next to each other
https://bugs.documentfoundation.org/show_bug.cgi?id=148255 Dieter changed: What|Removed |Added CC||dgp-m...@gmx.de --- Comment #12 from Dieter --- (In reply to freeware from comment #11) > either the patch hasn't been applied to said version or 148212 and 148255 > are not duplicates. Could you please try to verify, that bug 148255 has been fixed? Thank you. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 149269] For objects anchored "To character", LO uses the character immediately to the left of anchor character when Vertical position is to "Character", but it should use the a
https://bugs.documentfoundation.org/show_bug.cgi?id=149269 --- Comment #5 from sdc.bla...@youmail.dk --- (In reply to Regina Henschel from comment #3) > I do not understand, what this "Additional test" should show. Is there some relation between the contents of contents.xml and the character used for positioning? If not, then the "Additional test" may not be so relevant. Fwiw, the issue arose because in comment 0: > When you open the content.xml of the file in editor, then you see, that the > character "|" is before the rectangles. The "Additional test" shows a case where the "|" is after the rectangle. (but still positions in relation to the character to the "immediate left" of the anchor character.) -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 149269] For objects anchored "To character", LO uses the character immediately to the left of anchor character when Vertical position is to "Character", but it should use the a
https://bugs.documentfoundation.org/show_bug.cgi?id=149269 sdc.bla...@youmail.dk changed: What|Removed |Added Status|UNCONFIRMED |NEW Ever confirmed|0 |1 Summary|LO uses wrong anchor|For objects anchored "To |character for position |character", LO uses the |"Character" for object |character immediately to |anchored "To character" |the left of anchor ||character when Vertical ||position is to "Character", ||but it should use the ||anchor character --- Comment #4 from sdc.bla...@youmail.dk --- (In reply to Regina Henschel from comment #3) > The problem is, that not the anchor character, but the character left > from the anchor character is used for calculating the position. I can confirm this. Have changed Bug summary to make the issue more salient, but please check that the description is accurate. -- You are receiving this mail because: You are the assignee for the bug.
