Chrisw5

Walt, thanks for the response. Sorry, I should have been more specific. You're absolutely right, we've worked out that opening a pdf and editing the fonts is a good way to go, but In this case, I'm opening a placed pdf, to edit it.

I've been having a useful discussion on the bug reporting section about APubs ability to match fonts when importing pdfs, but it seems that it isn't a bug - just a limitation. I'm therefore raising this issue here, as it also probably isn't a bug, but it's very strange. The font manager screen says I’m missing Tahoma,Bold and Vedana,Bold, both of which it replaces with Courier New in Bold, and I've established that the problem is the way the pdf creating software gives the fonts a name with a comma instead of a space. However, that can be usually be overcome, but in this case when I try and change the Courier New to Tahoma in Bold and Verdana in Bold – or indeed, any other font – it accepts the change for 2 seconds and then it jumps back to Courier New. Nothing I do will persuade it to use a different replacement font. Has anyone got any suggestions on how to solve this ?

Many thanks again, to all of you. Glad I'm not alone in my concerns about fonts. Mike, huge thanks for sorting that. So, whilst the global colour preferences are set to sRGB, the Document set up overrides it to ROMM. I've never looked at that setting before, and didn't even know it existed. Absolutely no idea how or why it got changed, but I'll make sure it doesn't happen again !

Mike, That is seriously confusing. As you say, if I export a pdf from the APub file I uploaded, it works perfectly. As I couldn't see any point in uploading the entire magazine, I created that file by copying and pasting the single page from the master file into a new APub file. However, I've double checked, and I can't find any difference between the settings (either in preferences, or the export dialogue box) in the master file, and the new one I created. What's going on ? Something must be different, because this is the only file we have this problem with. Could it be because it was created on a Mac, and I'm using Windows ? Makes no sense. So, I've deleted all the rest of the magazine from a copy of the APub file, and left the only the relevant page. That file is now attached. For me, it exports a red pdf, hopefully it will for you, and someone can explain why. VV June - July19 mod.afpub

Thank you all for your input. MikeW, your screenshot is interesting, and raises a question. The preferences for my affpub files are set to sRGB. Is the Convert profile something different, and if so, where do I find it - I've looked without success.

Jon, thanks again for the response, and I think your comments are fair. I'm happy just to have raised the question, and if it reaches the top of the to do pile at some time, that would be good. Sadly, I can reproduce the red tinted pdf with no problem. Version 337, running on Windows 10, on a Lenovo Yoga 700. Strangely, it is specific to this page from this affpub file. We've never had this problem before, and I've just exported another colour page from an earlier edition of the magazine, on the same machine, without problem.

Thank you Jon P, and Libre Office for your responses, and apologies for the delay in this reply. I will try and asnswer all your questions here. The PDF in question is attached, and you can see that it does state that it uses Verdana,Bold. As far as I know, it was created in Windows Publisher. I didn't change any PDF Export settings, so the ones that it used were: Preset PDF (for export); Rasterise Unsupported properties; Resampler Bilinear; Use Document resolution; Allow JPEG compression quality 85; Compatibility 1.7. Thank you for your suggestion re PhosphateInline. I haven't had a chance to experiment with that yet, so I'll do another post when I have. All Saints Diary June July.pdf

I can see that there's another post about problems with pdf imports, but I thought I'd start another, rather than hijack that one, as this is rather more generic, and concerns exports as well as imports. We have had problems importing pdf documents using the Place tool, which I have previously reported to Affinity, with samples, but so far, nothing has changed. We have done some research, and the problems can be summarised as follows: · The first issue with corrupt PDF imports is that if the font names aren’t exactly the same in the PDF and in AP, then AP substitutes different fonts. E.g. the pdf thinks it is using Verdana,Bold, but the importing PC calls it Verdana Bold, with a space instead of a comma. · You can fix this by opening the PDF from File->Open where you get a chance to tell AP what the correct substitution should be. It appears to remember this substitution for future PDFs. · Even if you solve the font problem as above, it can still mess up the spacing, which is solved by using the Tracking command in the Character panel under the Positioning and Transform tab. It should be 0% but we’ve seen numbers in excess of plus and minus 200%. Highlighting the text and setting this to 0% removes 90% of the spacing problems but it still leaves the odd space between characters which need removing manually. · With one particular font we have come across, PhosphateInline, it still doesn’t look right after all that, and that problem can be solved by using the Typography panel to go from Normal to All Caps, if the text is in capitals. Is there anything you can do to make this process work better ? We’ve also recently experienced a problem with exporting a pdf, which we needed to do to print the page. For some unknown reason, the export process added vast quantities of red to the photos in the document (see attached files). We’ve done this many times before, with other pages, with no problems. We're using the latest Beta, on both Windows and Mac, and these problems are common to both. Front Cover JJ19.afpub VV June - July19 Front Cover.pdf

Chris, I've only tried it once. File attached. Village Voice Assets 20-11-18.afassets

Walt, on my system, the default leading in the Character panel is set to 12.4, and unsuprisingly, that's what I get when the leading box in the Paragraph panel is set to Default. However, my experiments show the following effects by using the drop down menu in the Paragraph leading box. Default: Rolling the mouse wheel actually changes the drop down menu to Multiple, and increases the leading from 12.4 to 13.9 to 15.7 - an increment of 1.5 followed by 1.8., although you can select increments of 0.5. Why ? That just seems bizarre to me. Exactly: Rolling the wheel gives increments of 1. Logical, but too big in my opinion. In this setting, yes I can type in whatever I want, and hit the Enter key, but how clunky is that ? Why not just make exact increments 0.1when the wheel is rolled ? That would give total flexibility, and ease of use. % of height: Seems to work exactly the same as Multiple. At least: Seems to work exactly the same as Exactly. Multiple: Worked differently to the way it worked when I got there from default, as the incements were 1.5 followed by 1.6. To me, the whole function is bizarre, and unnessecarily complicated. All I want to do is roll the mouse wheel, and increase or decrease the leading by whatever I want. This appears to be the only function in which Microsoft Publisher is easier to use than Affinity.

I'm still mightily confused by this fuction. If I leave the settings in the Character panel alone, the box in the Paragraph panel will expand and contract the spacing quite happily, but it goes from 11.4 to 12.8, to 14.4, when all I want it to do is go from 11.4 to 11.5, to 11.6, etc. Is there a way to make it do that, and if there isn't why not ? What am I missing ?

Patrick, it does ! Many thanks.

Thanks.

An interesting discussion. Personally, it's unlikely that I will ever use the full capability of this software, I just love it because it does what I need it to do really well, and largely intuitively. On that basis, I'm probably an in between user. I use some keyboard shortcuts, the History panel is far more use than undo icon, but the concept of toggling shortcut keys to (maybe) get back to where I was is an unnecessary complication. If I'm using one tool, and I want to use another, it's far less complicated to just remember the letter for the tool I want, and tap it. Additionally, it isn't possible to get out of the Text tool by tapping "T" again - all that does is put an unwanted "t" in the text. So, for me, Dominik's advice is perfect. I've reassigned the shortcut for the Artistic Text tool, and I now know exactly what's going to happen when I tap "T". That's all I need.

Many thanks Dominik.