I will not be offended if you kindly explain to me that I'm doing it wrong.ġ. I'm sorry for dropping several issues here-if any of these are covered elsewhere, please point me in the right direction. I've used Word and Excel for years, so I thought I'd already been through "Table Hell." But, Publisher brings it to a new level. However, that does not make "PUBLISHER TABLES COMPLETELY USELESS ." If Serif were to suddenly remove tables, the forums would light up with complaints from all the people who had been using tables. Maybe they can possibly achieve their own priorities while also being able to take Excel into account, but I suppose it must be low priority at the moment. Serif, on the other hand, does have everything to do with how data is copied when a table is copied, but I am sure that the priority is that they copy the table in such a way that it can be used within Publisher itself (such as to paste it in another place or another document). The problem you have raised here has to do with how Excel handles the data it receives, and of course that is out of Serif's hands. I would suppose that it would be rather rare that someone needs to move from Publisher to Excel, but surely it must happen every now in then, as everyone's needs and workflows can potentially be very different. Perhaps you rather mean that it is effectively useless in the limited context of needing to copy a Publisher table out to Excel. Your statement is so broad that in its current form it is shown to be false by the many people who have put Publisher tables to good use. THIS IS A MAJOR FLAW AND MAKES PUBLISHER TABLES COMPLETELY USELESS ! Ī little perspective might be helpful. When copying it back into new rows, all text lands in one cell.īy general standards, copying text from tables always must include line breaks for each row.ĭelete content of one row (C) and replace it with rows texts copied over from Word, I paste it without formatting into C. Park it in a text-only editor or in a publisher textframe already shows all text without line separation. The handling is furthermore very tense, clicking and moving the column line does not respond fluidly but with lags in response time. Please take an example from Indesign, where the other columns are not affected by a change of one of the columns.Ĭopy text of all rows in one column.
Very frustrating, that all following columns have always to be resized. This makes it insanely difficult to get to the desired end result. Resizing single columns always affects the columns next to it. In Publisher 1.7.1 tables are very hard to handle.
0 kommentar(er)
