Converted Profile Assistant Message Incorrectly Shown When Opening a PDF File Using an Embedded sRGB Profile

[Hangman]

When opening a PDF that includes an embedded sRGB Profile the Converted Profile Assistant message is incorrectly (and unnecessarily) shown when the Working Profile is also set to sRGB.

This appears to be the only profile affected, i.e., it doesn't happen with any other RGB or CMYK profiles tested to date...

[NathanC]

Hey @Hangman,

I think this might be somewhat related to the 'sRGB2014' PDF export bug we discovered last week, we created an FAQ on it linked below. 

If I create a new document with just text and export it to PDF with the sRGB-2.1 profile embedded, the output in Acrobat's object inspector indicates that the objects have the sRGB2014 profile assigned (incorrectly), and if I were to import the exported PDF back into Publisher and leave the profile on 'Estimate' it also assigns the document 'sRGB2014'. Although, in your example it what's interesting is it imports back in with sRGB 2.1 correctly, but flags a toast message.

Any chance you could send me over your sample .afpub and exported .PDF so I can confirm/compare?

 

Many thanks

[Hangman]

Hi @NathanC,

You're right, I recall @Dan C mentioning this though didn't realise he'd posted it as a known issue...

Taking a look at the exported PDF, which is purely text based, it is indeed showing that it has the sRGB2014 profile assigned to it which then makes sense as to why Publisher is flagging the file with a toast message...

Remove the sRGB2014 profile and the issue goes away...

44 minutes ago, NathanC said:

Any chance you could send me over your sample .afpub and exported .PDF so I can confirm/compare?

No problem, both files attached...

Alice.afpub

Alice.pdf

[Hangman]

Hi @NathanC,

Just a quick update...

Removing the sRGB2014 profile so it doesn't show up as an available working profile still exports the sRGB IEC6196-2.1 file using the sRGB2014 profile (as per the known bug) but as you've seen with the file attached earlier there are no images in the file, it's purely text so @Dan C's Known Issue may need updating to reflect this since you're not going to rasterise the text prior to export...

 

[NathanC]

Hi @Hangman,

Thanks for advising, I've let Dan know and he'll get the FAQ updated to reflect that.

1 hour ago, Hangman said:

Remove the sRGB2014 profile and the issue goes away...

Through what means are you deleting the sRGB2014 profile out of interest?

[Hangman]

Hi @NathanC,

Thanks for the update...

1 minute ago, NathanC said:

Through what means are you deleting the sRGB2014 profile out of interest?

By removing it from the ColorSync folder which results in the profile no longer being available as an RGB Working Profile under Colour Preferences, though I assume this doesn't prevent the file from still being exported using the sRGB2014 profile if the sRGB2014 profile is included as a part of the updated PDF export library?

[Hangman]

Hi @NathanC and @Dan C,

I'm copying Dan into the thread in relation to the Known Issue report...

Exporting and specifying the assigned colour profile doesn't appear to correct the PDF profile which still uses sRGB2014 and is read back into Affinity apps using the sRGB2014 profile...

Note: Changing the Colour Space to RGB in the Export window so both Colour Space and Profile are defined makes no difference.

[Dan C]

17 minutes ago, Hangman said:

Exporting and specifying the assigned colour profile doesn't appear to correct the PDF profile which still uses sRGB2014 and is read back into Affinity apps using the sRGB2014 profile...

Apologies, my testing for the FAQ was performed on Windows, as I had assumed the OS's would be the same in this regard (as they both use the same PDF library).

In checking the above, I can confirm I'm seeing the same as you on macOS and the manual specify workaround is happening on Windows only.

I'll update both the FAQ and dev report to confirm this behaviour, as it's incorrect across all apps/OS's.

[Hangman]

Hi @Dan C,

Thanks for the update and confirming that you're seeing the same issue on macOS, admittedly it does sound odd if both Windows and Mac are using the same updated PDF library...

[Affinity Info Bot]

The issue "Exporting to PDF RGB/8 with placed images always converts them to 'sRGB2014' regardless of export settings" (REF: AF-946) has been fixed by the developers in internal build "2.3.0.2139".
This fix should soon be available as a customer beta and is planned for inclusion in the next customer release.
Customer beta builds are announced here and you can participate by following these instructions.
If you still experience this problem once you are using that build version (or later) please reply to this thread including @Serif Info Bot to notify us.