Windows printing

[Cjhemmer]

I have a functional print module for Windows though not yet complete. My main remaining issue is color profile handling. Windows printing allows direct printing of a bitmap but requires an icc profile to be sent to the printer along with the bitmap for color management if letting the printer handle color management but inconsistency of device specific color handling may not handle the icc correctly. To add complexity as far as i can tell darktable's natively supported color profiles are internal and can't be embeded as an icc profile sent to the printer. Therefore I think I have two paths I would like the main development team to weigh in on.
Option 1: lock Windows printing to either srgb if letting the printer manage colors or the printer specific paper profile if letting darktable manage (Printer color management off in driver).
Option 2: follow the same pattern as in the Linux and MacOS versions that use CUPS by outputting a temp PDF. Unlike CUPS though, Windows doesn't have native pdf direct printing so for a color managed solution something like Ghostscript would need to be installed to handle the actual pdf to printer rendering.

Which option is preferred and if Option 2 what would be the best way to handle Ghostscript? For example a message to install with a link? Distribute with darktables Windows build?

[TurboGit]

Sorry just see this here now. Note that the Discussions here is only for core DEV to coordinate things like release.

Anyway, my preferred option is 2. Why Ghostscript? There is a routine in Darktable to output a PDF, this is what is used and should work on Windows.

Can you please open an issue (Blank issue) to continue the discussion? TIA.