Old Bruce Posted June 18, 2019 Share Posted June 18, 2019 Perhaps 16bit publisher documents are a solution looking for a problem. Q: "Why did you include that particular feature?" A: "Because we could." Jakerlund 1 Mac Pro (Late 2013) Mac OS 12.7.4 Affinity Designer 2.4.1 | Affinity Photo 2.4.1 | Affinity Publisher 2.4.1 | Beta versions as they appear. I have never mastered color management, period, so I cannot help with that. Link to comment Share on other sites More sharing options...
Jakerlund Posted June 18, 2019 Author Share Posted June 18, 2019 I'm sure there is some reason for the 16 bit option. You should start a new thread and maybe someone will give you the answers. Link to comment Share on other sites More sharing options...
fde101 Posted June 18, 2019 Share Posted June 18, 2019 I can think of at least two reasons: Compatibility with Photo and Designer Future support for digital publishing when producing content for displays with greater than 8-bit color depth (these do exist...) Jakerlund 1 Link to comment Share on other sites More sharing options...
thomaso Posted June 18, 2019 Share Posted June 18, 2019 (edited) The reason for 16 bit doesn't have to be in Publisher. Possibly it got implemented in Publisher for no purpose but just because the code existed from Photo already. Or as Old Bruce puts it, "Because we could." EDIT: probably for the same reason – but in Publisher without much sense, too – you can place .RAW and .DNG files in an .afpub document. Edited June 18, 2019 by thomaso macOS 10.14.6 | MacBookPro Retina 15" | Eizo 27" | Affinity V1 Link to comment Share on other sites More sharing options...
Staff Gabe Posted June 19, 2019 Staff Share Posted June 19, 2019 Hi all, Definitely a problem with Preview, as everything else seems to be fine. I suggest you log this with Apple. I've closed this as By design. Thanks, Gabe. Link to comment Share on other sites More sharing options...
mac_heibu Posted June 19, 2019 Share Posted June 19, 2019 No logging with Apple necessary, because it is working in Mojave. Apple surly won’t debug and older system version. Link to comment Share on other sites More sharing options...
fde101 Posted June 19, 2019 Share Posted June 19, 2019 1 hour ago, mac_heibu said: No logging with Apple necessary, because it is working in Mojave. Apple surly won’t debug and older system version. One of the indications was that it was broken in 10.13 though, so they might considering that 10.13 is the prior version. Apple usually provides security updates for at least two major versions back, which right now would be 10.12 and 10.13 in addition to the current version of 10.14... even after 10.15 comes out they would still be providing security updates for 10.13, so an issue like this one in 10.13, before 10.15 is released, just might slip into their queue... Link to comment Share on other sites More sharing options...
Recommended Posts