rjav

Thanks David -- good to know But getting the Title Field right was the straightforward solution

Got it! Thanks Lee D There was the offending entry which I have corrected and the PDF now behaves as expected

Every three months I produce a magazine which is printed and also distributed as a PDF. When the last two issues (Nos 268 and 269) are viewed in a browser, the title displayed is 264. Back on 11 December 2019, Walt Farrell said that the title of a PDF is taken from the Title Field in the Fields studio panel (View>Studio>Fields) and that Publisher will set the title to the file name and will not change it. What I think might have happened is that I have opened No 264 and then saved it as the later numbers in order to preserve certain content and formatting. (It doesn't explain why there wasn't a problem with Nos 265-267 but ... ) Walt said you can change the Title Field but I cant find View>Studio>Fields in V2.4.0 and searching on that as a question hasn't yielded an answer. I have corrected the PDF titles using the Kofax PDF software but it would be nice to get this set up properly if someone can help me find the Field.

Thanks Dan Following Hangman's advice, I changed my document resolution to 72 dpi and have just received the printed product. What i did not do was change the document resolution back to 300 dpi before exporting the printer's PDF. I remain curious about the real significance of document dpi. By setting it to 300, I can see if a bit-mapped image is too small -- ie, it is scaled to greater than 100%. But it should make no difference to text and vector objects which are scalable. Obviously, it is just good practice to set up a document at the intended output resolution. But does it make any difference when I export at 300 dpi?

I've been updating a document I produced last year in 2.2.1 on a Window 11 laptop with a hex processor. I'd got about halfway and just returned to it today. I'm not sure it's relevant to the crash problem but the text paragraphs all appeared in bold. After reformating, I went to adjust a paragraph indent and the app crashed. I resaved it with another name and started again. Had to get rid of the bold formatting again, successfully, then clicked in the paragraph to correct the indent -- crash! In previous weeks, I successfully completed two projects, now with the printer, without incident -- and one of these was a victim of the "erratic text style" problem. Is reinstalling 2.2.1 the next step? Being cautious, I still have V1 of the suite installed but haven't upgraded Photo (which I use) and Designer (which I don't, being unwilling to abandon decades of experience with Corel Draw). PS: I'm also working as a guest user on a hospital network for a couple of days -- not sure that's relevant either.

Hangman, thank you again for the reply and reassurance I understand DPI (and PPI) -- I used to teach computer graphics at a printing trade school and I found resolution was the hardest thing to explain But thinking about it has answered my basic question In Document Setup, you specify the page dimensions in units of length; then, in specifying DPI, you are also defining that length in pixels To satisfy myself on this point, I created a new A4 page at 72 DPI, drew a picture frame that was 3 inches (= 216 pixels) wide, and dropped in a bitmap image that was 1800 pixels wide and therefore appeared at 12% of its full size I changed the Document DPI to 300 which made the 3 inch picture frame 900 pixels wide and the image was now 50% of its full size Which is why the discussion has been talking about "scaling factors" How this affects text which is a vector element (postscript or TTF) is, presumably, at the heart of the bug This is something buried deep in the code which I don't need to know about -- what I need to know is how to deal with the erratic behaviour which you have very helpfully explained, thank you A final question -- is there a need to change the Document DPI back to 300 before exporting to a PDF for which you nominate the required Raster DPI (ie, 300)?

Thank you, Hangman I have gone back to my first Publisher version of the InDesign file (I am still keeping V1 on my system out of an abundance of caution), changed the Document DPI to 72 in Document Setup, and added my new pages -- so far, I am cautiously optimistic However, I have not changed the Document DPI back to 300 (or 600) because I might still need to add a page or two as I make my revisions and I don't want to invite the erratic behaviour back I feel I should complete the revisions and change the document DPI then, not swap back and forth as I go My problem is that I don't understand the significance or impact of Document DPI and, so far, haven't been able to find an explanation in the articles I have found In particular, I wonder if this setting has an irreversible effect on images -- ie, are they downsampled so that, when you change back to 300, the images retain the lower resolution If an image is linked, the source retains its original resolution -- but what about embedded images: are they resampled to the Document DPI? Or does Document DPI just determine the resolution if you print directly from the Publisher document? (It shouldn't make any difference to what you see on screen because 72 is the monitor resolution) Understanding this would be very reassuring My normal workflow is to complete the design and then produce a PDF, at which point I set the required DPI (72 for previewing purposes to keep the file size small; 300 for the commercial printer; or 144 for distribution to people who might want to print hard copies on their own inkjet printers)

It's back -- I'm now using 2.2.1 and have just started revising a Publisher document which was originally converted from an InDesign document I had to adjust some of the layouts so that the text finished where I wanted it, lining up with the bottom page margins Then I needed to add more pages at the end of the document (page 32) and some of the text flowing onto the new page was reduced to 1.2 point (that's one point two) Same old, same old -- drag the text frame handles and text flowing back onto the previous page is the correct size; when I push it into the added frame it is 1.2 It took a couple of attempts to final over-ride the incorrect font size Then I added two pages between pages 8 and 9 and the same thing happened -- text flowing into the new frame was reduced to 1.2 pt The attributes of the new text frame showed as "body text +" -- I couldn't just reapply "body text" but had to first set the style to "no style" and then "body text" That seemed to fix the problem on the two new pages ... ... but then, on the following pages, I find the text has changed to 83.3 pt !!! Back at the end of the document, the pages with the correct text size (10 pt) now have the leading in some paragraphs changed to 1.2 pt Manually changing the leading back to 12 pt doesn't correct the problem Whatever the bug is, it's still in the code and it looks like I am going to have to start from scratch again with a new document

Thanks Hangman My original problem was with a file imported from InDesign but I did have it occur again on a fresh Publisher document -- fortunately the reformatting made it go away again

I've been overseas and this is the first opportunity I've had to respond. DigArt's problem is exactly the same as I encountered, right down to the same point size of the erratic text. One other thing I did was drawn fresh frames -- I was suspicious of shapes I'd drawn with the Pen tool and converted to text frames.

Just an update to this. I haven't tried Thomaso's suggestion of PDF/X but I have just sent off the June issue and had the same old problem. In checking my saved Settings for the grey-only output, I found that "Embed ICC profile" was ticked. When I unticked this, the grey pages were free of CMY. With this issue in production, I can now install V2 and see what happens.

Phew! Thank you for that reassurance. I will open the document in V2 and then save it as "Document_v2" to clearly distinguish them. I will make sure I open the app first before opening the document so that I don't accidentally upgrade it.

Walt, from the discussion above, it seems you can have V1 and V2 installed at the same time -- ie, installing V2 doesn't overwrite V1. I have an unfinished Publisher V1 document which presented layout problems (see "erratic behaviour of text styles"). Now that these seem to have been resolved, I am reluctant to transfer to V2 until it is finished. Do I have the option of working on new documents in V2 but keep V1 for the old document? I'm less concerned about Photo.

Thomaso and others I have had time to carry out more tests and it seems to be as simple as I thought it would be The key is setting the ICC profile -- this was not an issue with InDesign but I had to make sure that I set up the Affinity document with the same profile that my printer was using (which was FOGRA39) To export a greyscale file I had previously chosen the "Gray" colour space but then used one of the five available grey ICC profiles When the printer opened the file, because it used a different profile, the grey-only PDF was converted to a CMYK mix which only looked grey The point being, as others have noted, that any CMY on the page means a higher printing cost This time, I chose the "Gray" colour space but used the document profile (ie, FOGRA39) and, as Thomaso has noted, selected "Convert image colour spaces" The printer has just emailed back "All black breakdown! No colour found" Now I will be able to produce a master document using original images which might be in colour for a PDF which is emailed to some subscribers (they might as well see it in colour) and then convert selected pages to grey only for the printed version Thank you to all who have taken an interest in this

Hello thomaso I started a new document including redefining the styles. I only had three -- body text, section headings, and captions -- and so it didn't a lot of work. But even then, the erratic behaviour occurred one or two times and I had to reset the type or leading sizes.