trichens

You could also check to see if the Ignore Baseline Grid option is turned off/on on the text frames.

What does the Layers dialog show when both are selected?

The blend with a colour rectangle works OK... Very nice. Thanks Old Bruce. It's just a bit of a pain to have to place a filled shape under the text frame wherever I want this to appear but it's a good workaround.

Perhaps I didn't explain properly. So I have two linked text frames. One has a dark background so requires light text; the other works with black text If I add extra text into the left hand frame the text flows over to the right frame but it's still white. If we can assign a style to the text frame then this would cause the text formatting in that frame to change automatically

I can't find this anywhere... but perhaps I've been searching for the wrong thing. I'd like to be able to apply a text style to a text frame in Publisher Why? This is so I can have a coloured background with a text frame but the subsequent linked frame may have a different colour background. So let's say you have a page which has the left hand side a dark blue and on the right it's white. The text that is on the left side of the page would have to be white while on the right side it would be black. So you place a text frame over each half of the page and have them linked. You assign one format to one frame and a different format to the other. When text is added it, flows across the frames and on the left frame it's white text and on the right it's black text. If you add text to the first frame the text is reflowed into the second frame and changes colour. Is this possible now?

So... we have an imge that opens OK in Affinity Photo? And the original image is OK? The calendar software is extremely unlikely to be reading the native Affinity file format, so the image must be exported to a JPG, PNG or suchlike. Do we have a hidden layer in the Affinity file that shows up on the exported raster image due to any flattening process?

Well it sounds like a placemarker in the calendar software to me. Have you replaced this image with a different one - or the original image - to see it that does the same thing?

What I can't yet figure out is why the margins on page 6 are wrong. The inner margin is set to 0.5in and should be on the right, but in your file it's on the left. On pairs of pages we should have the inner margin in the centre - or on the right for even numbered pages and on the left for odd numbered pages.

I think you are confusing margins and bleeds, Jessyca. The bleed is only used to allow for the cropping of the paper not being exact. If the crop was out by 0.050in then without a bleed you'd get a white edge on the page between where the image ends and the paper is cropped. The bleed area allows for this. For the allowance required for the coil binding you need to set the margins so that you don't use that area for anything. And as LondonSquirrel says the issue is with page 6. If you look at this you have a layer named Master Page; just delete this layer and you should be OK

OK, turn on crop marks when you create the PDF file. You'll see that these are positioned so that the pages will be cropped correctly. Most printers only require 3mm or 0.125in bleed so the 0.5in inner bledd doesn't have to be that large. This should allow you to get the file exported for printing OK. Not sure what's causing the crashing yet though.

You say it doesn't appear when the file is open in Affinity Photo nor when you view it through Windows - I assume the file viewer. But it appears when you use the image in some other software? Which software? It sounds like this other application is adding the text?

Hi Jessyca, Can you create a simple four page export PDF file - just front and rear page pairs which I'm hoping won't disclose anything sensitive? Upload that so we can see what the output is with the bleed? This will show what happens when you have facing pages turned on.

I've had some crashes in 1.10 as well. It seems to be a return of the issues we had a few versions ago when modifying tables. I was just editing some text when all of a sudden I'm looking at the Windows Desktop and Publisher has vanished 😒 Reopen Publisher and was offered a file to restore which worked OK with only a few edits missing. Made same changes again with no issues

I've got exactly the same issue. Have been working on a file with no problems since upgrading to 1.10 and suddenly can't save. If I attempt to save as a new file I get a zero sized file created. Reopened the previous version of the file OK. Have redone the changes and the newly updated file is OK. Fortunately I do make regular backups but it is a bit of a concern as if it's some sort of file corruption occuring when working with files created in 1.9 then that would mean that I would have to recrete the templates from scratch in 1.10.... and if it's not a problem "caused" by working on 1.9 version files then it's likely to reoccur The files have NOT been working on using any of the beta versions; only "proper" releases. The afpub files come out at around 165Mb to 180Mb. I would attach one but the current versions are OK. Is there some error log that Publisher produces that would be of help?

I'd suggest that you could look at using mulitple tables stacked on top of each other. I do a table that has alternating coloured lines for each row - so that's one table and I just select alternate rows and change the colour - in theory you may only need one column?? Text is in a duplicate table where the rows have a transparent background. I have a third table between the two so I can change the colour of individual cells

The issue here is the differences between Unix and Windows and they way they handle C/R and L/F use. I use SublimeText ot Notepad++ for all my text editing and that does a soft-wrap at the end of the "on-screen" line - I can set this wrap at a particular character. The files it produces have no line breaks in the text unless I actually ask for one by pressing C/R ( and/or L/F). The problem you have with your vi edited files is that you are manually adding a L/F - and I'd imagine a C/R - at 70 characters - so this gets picked up as the end of a paragraph. What happens if you carry on typing without adding a line break? The only time in recent years - and that was around 20 years ago - I have come across this before the editor was breaking the lines at around 60 characters and when the resulting file was loading into other applications we got a C/R and L/F and so a new paragraph. We had to do a find and replace to get rid of then. If you are using Unix type tools can you run the text file through sed or similar to remove the extra C/R characters? There's a unix2dos tool that may produce a suitable files or you may find vi can do this with the following from the vi command line :%s/^M//g

Well you can use the Ignore Spelling option which appears to add the word to the current file "dictionary" but not to the overall system dictionary. Just tried this and it will not highlight my spelling mistakes in the file where I have set them to be ignored, but when I open a new file and enter the same mispelled word it gets highlighted as being wrong. Will this achieve what you need?

I'd really like to be able to link to other APub files - not merge - and although the merge process may perhaps work for a book, it doesn't work for me. I create matchday programmes for a local football club and I create each article as a separate APub file and then export as PDF. The final completed programme is assembled into a single APub file from the separate PDF files. Some pages like adverts don't have to be changed often, but others get changed for every programme I produce. For example a league table will change every issue, so I just remove the PDF for that page and drop in the new version. Page numbers exist only in the master pages for the combined file. I can then reorder pages or move things around as required, and apply or replace the required master page(s) for each section or page when I have finished. It seems to work OK; when we have matches rearranged I may have to produce three or four new issues in just ten days or so and the above allows me to do this quite quickly.

Very true Walt. But having corrected everything, or accepted that the errors can be ignored, you can't continue directly on to the Export dialog. When the export process runs and it finds problems, it will offer the option to either view issues, ignore them or cancel, but having selected review you then lose the option to ignore if it's actually OK. I'd just like to review the issues, say "that's OK" and hit an Accept and Continue button on the Preflight dialog.

After a search I can't see this mentioned in any other topics - sorry if it's there and I've missed. When I export to PDF I may get the Preflight dialog pop-up listing any issues. It's likely to flag up spelling mistakes that aren't actually mistakes - just not in the dictionary - and also items that don't affect what's going to be output. However having checked through these and decided that they are OK, I have to close the Preflight dialog and re-export which re-does the preflight process. I can then skip viewing the Preflight dialog and continue but... Could we not have a "Accept" or "Continue" button on the Preflight dialog itself which will just proceed directly to the Export dialog if we aren't going back to make any changes? Or is this already possible and I've just not spotted it?

I've been using Eagle ( eagle.cool ) recently. It handles Affinity files and shows the file previews OK. Allows me to group together all the files from anywbto Seems to support most files I use but strangely doesn't include LibreOffice files like odt format

The issue I had with working that way was that it wanted to keep the overall table width the same, so when you got to the last column it would usually be too wide. If you then adjust the table to get that last column right it would change all the carefully adjusted columns to the left so as to keep the same proportions. So you then have to go back and resize them all again. And if i recall correctly going back to insert another column was a nightmare because it doesn't resize the table - it resizes all the colmuns to fit the new one in. Something to watch out for though is that if the "early" columns need to be wider than the default values you'll have to adjust the "later" columns first otherwise you'll have issues trying to change the widths. You just need to experiment a bit to find what works for your particular layout. I had two tables laid over the top of each other. The first had 17 columns and the second 34 columns underneath. They have to be the same overall width so that I can have text in the first table and the second has two coloured cells as a backgound for each of the top table so I can have two colours behind the text. Worked OK when I got the calculator out to do the design on paper before opening the software.

I've used tables a lot in APub and you're right - it can be really annoying. The only way I could get tables to work was work out the dimensions of your finished table so you can create a table with the correct number of columns and the correct finished table width and then change the column widths working from left to right. The other issue I had with tables was that APub would just crash out when making changes to them Either it would close unexpectedly or just stopped responding so I had to use Task Manager to kill it off.

I must confess that I noticed when working on a new publicaton that the automatic relinking isn't working now ( 1.8.3.641), but I'm also pretty sure it used to. Just tried on 1.8..2.620 and that doesn't auto relink either so I have to select each image in turn.

A search in Affinity forums gave me this from 2017 Also found this issue reported on HP forums where scanners were creating files that gave this error. Opened the "broken" PDF in Foxit Reader and it reported it as being PDF 1.3 format. Saved as new file which was saved as PDF 1.5 format and this opened OK in APub The export PDF options in Apub start with version 1.4 so perhaps it won't open an earlier version? I've found a reference to the PDF library used in Affinity not supporting export of PDF 1.3 so it's reasonable to assume that the same library won't import PDF 1.3 files.