microjez

Yes, it is the ability for a table to flow across multiple pages that I require - for example, when importing a large table from Excel. If this is easy, please could you let us know how to do it? It could be that I am missing a trick!

I bought the Affinity 2 suite as soon as it was announced, because I thought "surely that must include a way to split tables by now". I checked and as for AnaliseThis of course the facility is still not there. Please could Affinity confirm that this is on their "to do" list. The ability to join tables would also be useful, of course.

It is surprising that so few people have contributed to this thread, as I continue to find the inability to split (or join) tables quite a problem. I get round this by creating a table, finding how many rows fit in the space available, then go back to my original Excel source and split the Excel sheet, so that I can then import the correct number of rows to fill the space, before proceeding to the next page and doing the same all over again to find out how many rows of the Excel sheet will fit on the new page. This is very iterative, time-consuming and prone to error. I have come back to it just now as I am in the process of updating an annual report, which will incorporate some of the tables from the 2020 report as well as a host of new tables. I take Walt's point that Serif cannot incorporate every desired fucntionality "overnight". Perhaps Affinity could confirm that this feature is on their "to-do" list, even if they tend not to promise a particular target date. Compared to some of the specialist features introuduced recently, I would have thought that the ability to split and join tables would be relatively easy to implement - but then, I am not a practicing programmer!

That happens to me, if I do not change anything. The problem arose when I changed the positions of the text boxes and picture frame on the right hand half of the file.

I updated Publisher to the new version (1.10) as soon as it was available. After update to V1.10 I carried out edits on the body of the book (previously captured in 1.9.2.1035). These updates were all textual rather than to picutres. This saved OK in V 1.10, or so it would seem. I decided to carry out a minor update to the cover file. This was to file ImageWrapCover_Premium_Paper.afpub (uploaded here, along with the linked image I tried to move). The update was simply to move the text boxes and picture on the right hand half upwards a bit to centre them vertically on the page. On saving this I received the message seen by others (error message.docx). I tried the same operation in V1.9.2.1035 and it worked fine. I am reporting this although it has already been reported, so that I can be kept in the loop. I am about to send the book to the printers, so this bug has come at a most inconvenient time! error message.docx ImageWrapCover_Premium_Paper.afpub

Thanks for your post. My import screen looks a bit different (see uploaded image). Could this be because I have been using Century Schoolbook already? If Century schoolbook does not come "with" Publisher, I have no idea where I got it from. I am sure Century Schoolbook was the original font, as I was able to view it in a trial version of Quark. I watched your video with interest, and noticed your indication of the Positioning and Transform area. Stepping through the string "bug-" character by character I encountered a variety of values for VA such as 0%, -537%, -80%. By manually changing these values I could retrieve the hyphen from "inside" the "g", although, as user AVOLO mentioned there is an extra space before the hyphen. So, it seems there is a way of sorting such occurrences in the text afterwards, but that is only if I can spot them! Me and my co-editor took several iterations of proof-reading before all these were found, and while it is good that Publisher is versatile enough to tweak the text using Positioning and Transform, it is unfortunate that this needs to be done manually. Of course, one could just blame Quark Express!

The pdf I imported from Quark express was inherited, so I do not know where the original publisher obtained his fonts, but I assume they came bundled with Quark. I am assuming the font I used in my copy of Publisher was provided with the package. I have not downloaded any additional fonts. I hope this helps!

I have tried using GarryP's method, and everything works until I enter the text in the text box. Instead of appearing in the text box it appears beneath the picture! Annoyingly, I have sometimes got it to work, but not always, and I do not know what the differences are when I do succeed. Because of the template I use I need to have an overall background text frame as part of the Master Page. I have also tried creating a text frame using the text frame tool and dragging it over the image. The same thing happens (text appears below the picture, not in the box). Sample file attached. TextOverlayProblem.afpub

My input pdf was also produced from Quark Express. I have tried capturing other pdf files (presumably not created from Quark Express), but have not been able to reproduce this issue with hyphenation. All the Quark Files I have captured did exhibit this pheonomenon, however. Given the importance of Quark Express in the Desktop Publishing domain, I hope that Affinity will see fit to address the issue. It might just be a simple fix!

I have noticed that when importing pdf documents into Publisher some hyphenated words "swallow up" the hyphens. Best explained by reference to attached files: OrigP6.pdf is the pdf file that I imported into publisher. I added yellow highlighting at problem words. OrigP6Beta1.9.0.874.afpub is how it appears after import. The yellow highlighting shows the hyphenated words where the hyphen is misplaced. This import did not have "favour editable text over fidelity" selected. OrigP6Beta1.9.0.874-opt2.afpub is how it appears after import with "favour editable text over fidelity" selected. Interestingly, there are additional hyphens that did not import tidily, as well as other minor issues (generally highlighted) and one that was an issue in the first import but not in the second. Page6ExPub is a pdf export of OrigP6Beta1.9.0.874.afpub I guess one should not expect perfect import of pdf documents, but this hyphenation issue is difficult to spot easily and has led to a large amount of additional work to sort it out (especially as I used the maximum fidelity option, with a new paragraph at the end of every line). This issue also exists in earlier versions of Publisher, but I include it here as this beta is directed at improving pdf import among other things. OrigP6.pdf OrigP6Beta1.9.0.874.afpub OrigP6Beta1.9.0.874-opt2.afpub Page6ExPub.pdf

The problem that I find with the Affinity pdf importer is that it provides a new paragraph symbol at the end of each line. Thus, if you want to edit your text after capturing it in Publisher you have a big job to do in justifying the text. Even so, it might be worth importing your text as pdf and then reformatting the whole document, by deleting all paragraph symbols and then re-inserting these where a new paragraph really is required.

The only way I can find to do this is to put the whole table on each page, and then delete rows. This is totally unsatisfactory, of course. Does anyone have a better way? I can find nothing in help.

We should not need to seek work-rounds. I have recently created a 400 page document incorporating material imported from pdf files into publisher and then merged into the main document. Every line in a pdf import ends in a paragraph sign. I find I need to edit some of these imported pdf sections, which requires me to replace the paragraph sign at the end of each line in the paragraph to be edited with a space, and sometimes, to make the typography flow, I have to do this over several pages at a time. Doing a "find and replace" on the affected sections only would be very useful. Please Affinity, can you implement this?

Have tested it and it works with my documents, which all use the same Master Page. It's too late for my current document, but will certainly build the next one using individual documents for each article, combined at the end. Thank you very much.

Yes. I downloaded the beta a while back, and it did exactly what I needed. However, I shall not be taking full advantage of this until the beta has led to a new release - just in case!