Apache OpenOffice (AOO) Bugzilla – Issue 24500
Pasting table content into existing writer tables
Last modified: 2017-05-20 10:45:21 UTC
At the moment, it is not possible to paste contet of tables (cut in another application than writer) the same way you do with writer tabels. As example. Try in writer: - create two Tables (3x3 cells each) - type some TExt / values in the 1st table's cells - select 1st table and copy content to clipboard - set the cursor to the 1st cell of 2nd table - paste the clipboards table -> the content will be pasted to each single cells and give a copy of the 1st table Try with Writer / Calc: - use the tables from the recent example (content should already be in clipboard) - paste clipboard to a calc sheet -> Table in calc looks similar to that in writer - select all new cells in Calc and copy to clipboard - go back to writer, select table 2, cell 1 and paste the clipboard's content -> you have no chance to get the same results as when copying writer -> writer You only can past as a calc object or text to one call (instead for each single cell).
*** Issue 20854 has been marked as a duplicate of this issue. ***
Reassigned to BH
*** Issue 42010 has been marked as a duplicate of this issue. ***
*** Issue 49266 has been marked as a duplicate of this issue. ***
*** Issue 63351 has been marked as a duplicate of this issue. ***
*** Issue 65750 has been marked as a duplicate of this issue. ***
*** Issue 68053 has been marked as a duplicate of this issue. ***
*** Issue 14333 has been marked as a duplicate of this issue. ***
I will propose increasing of priority for this bug to P2 according to priority specifications: P2 marks severe problems which affect a significant number of customers eg. Critical usability problem
*** Issue 26014 has been marked as a duplicate of this issue. ***
*** Issue 68651 has been marked as a duplicate of this issue. ***
I see so many duplicates and some votes. Shouldn't there be a Target milestone and a rough idea towards a spec?
Apart from this issue I am very impressed with open office - well done. However, this single issue means that I am unlikely to use open office at all. I do a lot of data analysis and report writing and inevitably use a lot of tables and cut and paste between word/excel. Although it works by pasting in RTF first somewhere into the writer document then cutting that into the table, it is an extra unnecessary step that slows me down I feel.
*** Issue 70504 has been marked as a duplicate of this issue. ***
*** Issue 72398 has been marked as a duplicate of this issue. ***
Created attachment 42377 [details] Table in Calc
Created attachment 42378 [details] After pasting to Writer by Ctrl+Shift+V and HTML
*** Issue 76862 has been marked as a duplicate of this issue. ***
Hi Mathias, I have changed the current owner to your owner. Please take the ownership of these enhancements.
Hello QA team! Please assign a target milestone for this issue. Also, MSO-parity keyword is necessary: MSO obviously have no problem pasting data in tables.
Thanks for the reminder. I think this is something we should fix for 3.0 latest. I wonder whether this can really be called an enhancement ...
target 3.x
*** Issue 85455 has been marked as a duplicate of this issue. ***
*** Issue 82519 has been marked as a duplicate of this issue. ***
*** Issue 89727 has been marked as a duplicate of this issue. ***
*** Issue 94279 has been marked as a duplicate of this issue. ***
Dear developers. What about ver. 3.1 for this issuу, 91 votes and 17 duplicates are not enough?
Dear developers. What about ver. 3.1 for this issue, 91 votes and 17 duplicates are not enough?
I already have planned to change the target to 3.1, so thanks for the reminder. The problem was that before I could decide to do that I had to figure out a simple way to implement that. The straightforward approach looked a bit scary and that already was the reason why we didn't fix that for 3.0). Now I have found a possible way for a not too complicated and especially *local* fix, so no problem for 3.1.
Mathias, would remind you one more time? This issue have no easy workaround, and users doesn't take complains :(
I'm not sure that I understand what you want to achieve. The target of this enhancement is set to the next possible release. If time permits we will work on it. That's all I can do at the moment.
Thanks for the answer. I would like to: 1. make sure this issue won't miss release 3.1 2. emphasize importance; although this is not a stopper, but inability to do a simple task cause negative impact on OOo adoption. Please keep us up to date about status of this issue.
Also see Issue 13316 (maybe duplicate?)
Yes, it's the same problem, thanks for the hint. The problem in general is that tables that are not transported in Writer's "native" format but in RTF or HTML format will show the undesirable behavior. HTML and RTF are the formats that are used to copy a table or a part of it from any other application (Calc, Browser, Word etc.).
*** Issue 13316 has been marked as a duplicate of this issue. ***
*** Issue 98259 has been marked as a duplicate of this issue. ***
With 3.1 code freezed I guess correct target is 3.2?
Correct. I'm not too pessimistic ;-) for 3.2 as I have an idea how to fix the problem without reworking the whole code for inserting tables.
Mathias, I am sorry for being so pushy about this issue, but with just 2 months untill code freeze I afraid that this will slip further. Regards, Kirill.
Here's the approach how we can fix that: We know that pasting a table into a table works fine if both tables are in Writer format. It doesn't work well if the pasted table is in HTML or RTF format. So what we could do without rewriting the whole "Paste HTML/RTF" code is: - first paste the HTML or RTF table into the document core somewhere outside of the target table - copy this intermediate table into the target table (now we are copying Writer format that should work!) - remove the intermediate table As this will happen in the document core only, there will be no visible intermediate table, it's just an internal "trick". Björn, please take over.
Would it be possible to insert table via some temp document and not via user document, in order to avoid any side-effects (undo, style changes etc)?
Sure, that's one possible option of being "not visible". I'm not restricted to any options, so in case a temporary document appears to be the simplest and most secure way I certainly would opt for choosing it. That should be left up to the developer implementing it (Björn).
retargeting 3.3
I hope, that retargeting 3.3 is final. Please, correct this bug. I would be happy to help with this, but I am only end user OpenOffice. Thank you
I just put in my vote for this issue. The present behavior of writer is a real time waster for me and dozens of my colleagues. Let's fix this in time for OOo 3.3 at the latest!
I have Extension for this bug. Extension writed Mr. J. Pastierik and sent me it under GNU General Public License. Internet page: http://www.inet.sk/clanok/5845/makra-v-openoffice-org-02-2008. It is in Slovak language, but I think, it is not problem. After instalation we have one macro for Calc - for copy tables, and second macro for Writer - for pasting table content into existing writer tables. Extension I sent to b_michaelsen.
Where can I find the oxt ??
pls. reassign or close issues. Thx.
set target 3.x since not relevant for 3.4 release.
this opensource extension can help: http://extensions.services.openoffice.org/en/project/pasteasvalue
*** Issue 110978 has been marked as a duplicate of this issue. ***
Reset the assignee to the default "issues@openoffice.apache.org".