Pauls

Yes -Upload it here please

I'm not sure exactly why but I suspect some sort of encoding issue. I've logged this for a developer to investigate. @Radim N is the google doc formed from different sources itself?

In that case could I get a copy of the source you used

Did you type or copy/paste the problem text?

in my exports some text frames exhibit the problem and some don't - which is in itself odd

If you use the sub-set fonts option in the PDF export options this can cause problems. Also having duplicate fonts with the same name has been known to cause some issues

Could you try and follow the below steps to get a log file from the PDF export please. I can pass that on to development who will be able to get a better idea on why it might be failing! Create a folder called 'temp' on the root of your C:\ drive so you have folder at C:\Temp\ Run 'PDFLibLogging.reg' - this will create a registry entry that enables logging for PDF Export Run Affinity and export to PDF and then click OK to accept the error message. Go to C:\Temp\ and attach the newly created PDFlib.txt file to this thread - this is the log we're interested in seeing Once you've got that file run the 'PDFLibLoggingRemove.reg' to remove the logging as this can cause slowdown! Thanks! PDFLibLogging.reg PDFLibLoggingRemove.reg

I think that's a different issue @Radim N - can you create a seperate thread. We'll probably need a sample file and the font exhibiting the problem

We think this is a UI bug when having monitors with different DPI resolutions and switching the app between them . Performing a control run up should make the dialog function again

That's been logged

is that from Google Fonts or somewhere else? You can upload files to the original location

The document apppears to be fine for me although I dont have all the fonts you are using. Would it be possible to upload those as well ? Also can I get the specs of your Surface book and what type of input operations/devices are you using when the application freezes ?

That Crimson font is causing us problems

We're aware of an issue in this area

If you use our beta version can you still replicate the crash ?