Description: I created a spreadsheet that included several text entries formatted with strikethroughs. I copied the spreadsheet entries to the clipboard and used Paste to add the entries to a Writer document. The text copied correctly but without strikethroughs. After posting my problem, a user passed along a solution: Use Paste Special and choose HTML. I am a very new user of LO and it was suggested by the poster of the solution that this was a bug that should be reported. Steps to Reproduce: 1.Copy text with strikethroughs to clipboard in Calc. 2.Paste clipboard into Writer. 3. Actual Results: Text appears in Writer but strikethroughs are lost. Expected Results: Strikethroughs should be maintained between components. Reproducible: Always User Profile Reset: No Additional Info: Version: 7.4.6.2 (x64) / LibreOffice Community Build ID: 5b1f5509c2decdade7fda905e3e1429a67acd63d CPU threads: 20; OS: Windows 10.0 Build 22621; UI render: Skia/Raster; VCL: win Locale: en-US (en_US); UI: en-US Calc: CL
Clarification: this when copying more than one entire cells; copying strikethrough-attributed content from within cells and a single cell and pasting to Writer (without cell border) works. Cells are pasted using the clipboard's RTF (Rich Text Format) text/rtf target. For two cells with the first having content CellContent and strikethrough that results in (xclip -selection clipboard -o -target text/rtf) {\rtf\ansi { \trowd\trgaph30\trleft-30\trrh256\clvertalb\cellx1280\clvertalb\cellx2560\pard\plain\intbl \ql CellContent\cell\ql \cell\row } } Using bold text attribute that is copied along: {\rtf\ansi { \trowd\trgaph30\trleft-30\trrh256\clvertalb\cellx1280\clvertalb\cellx2560\pard\plain\intbl \ql\b CellContent\cell\plain\ql \cell\row } }
Dear Richard, 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