|
|
color-management-malfunction.gif (600,497 bytes) |
|
|
I was trying to test 0002281 when I discovered this |
|
|
Unable to reproduce. |
|
|
utnik, can you reproduce this on OSX ? |
|
|
i don't have 1.5.2 but i can confirm the same strange behavior with 1.5.1 and 1.5.0 on macOS 10.11.4 (works fine with 1.4.6) |
|
|
No issues on OSX, you just need to get your profiles correct or you wont see a change. |
|
|
changed the path and everithing works as expected. the color management in scribus 1.5.x doesn't recognize linked profile folders (so called 'aliases') any more – so this path is more critical than in versions up to 1.4.6 where i could link my personal profile folder inside the system wide one. |
|
|
guys, i think we need to let the user know what's going on if the color profile aren't correct, right? utnik confirms the behavior and explains in more detail why it happens. Can we discuss this further? |
|
|
Changed summary to reflect updated info |
|
|
a warning sould appear instead of jumping back to ‚disabled colormanagement‘. something like: ‚the selected color profile could not be found.‘ |
|
|
@utnik agreed |
- Anonymous
