And I believe .psd is still the only "raw" common format for artistic drawing, right?
I've once seen a .psd that won't display correctly in neither Ps or CSP, supposedly because it was exported from something else. That didn't seem like a fun situation.
Re:Krita fund has 0 corporate support
by tambourine_man on Thursday October 05, 2023 @09:15AM
(#37778188)
And PSD is notoriously complicated. I remember reading some rant by an open source developer and there were things along the lines of different endianness in the same file.
It’s a 30+ year old format that went to multiple transitions. I don’t envy the poor soul that has to reverse engineer it.
> I remember reading some rant by an open source developer
This one? https://github.com/gco/xee/blob/4fa3a6d609dd72b8493e52a68f31...
Re:Krita fund has 0 corporate support
by alexvitkov on Thursday October 05, 2023 @10:18AM
(#37778938)
Fantastic read, thanks.
Re:Krita fund has 0 corporate support
by tambourine_man on Thursday October 05, 2023 @10:21AM
(#37778971)
That’s the one yes, thanks.
Re:Krita fund has 0 corporate support
by funnyflywheel on Thursday October 05, 2023 @10:28AM
(#37779044)
I took a look at the git blame, and the commit title is perfect.
https://github.com/gco/xee/commit/750196023da5457d9535b30299...
Re:Krita fund has 0 corporate support
by seanthemon on Thursday October 05, 2023 @11:43AM
(#37780072)
My favorite part is the immediately followed //sanity check, too apt.
Even if you simply import a .psd and re-export it again as-is, it will still break things like smart objects and layer blending options.
It's not Krita's fault: .psd is not an interchangeable format. Implementing .psd support perfectly is basically implementing the whole PS itself. It's all the artists' "fault". But it doesn't change the fact that using Krita makes my days difficult.