Please take a look at IPP Printing

Idea Place
1

I suggest to implement the following feature:

Please consider direct support of IPP printing. Microsoft forces this with Protected Print Mode.

A typical use case might be:

Printing is still the heart of LL. So the next obvious step is to directly support IPP printing. Have a look at GitHub - danielklecha/SharpIppNext: A .NET Standard library that can be used as IPP client and IPP server. · GitHub which is a very current C# implementation of many *PWG-Standards. It even helps LLCP.

Update / clarification: LLCP already seems to provide physical printer support via combit.ListLabel31.CrossPlatform.Printing.Pdf. However, according to the documentation, direct IPP is currently used on Linux, while Windows still relies on the Win32 print spooler / GDI path.*

The request is therefore specifically about a first-class, cross-platform direct IPP backend, especially for Windows and server/headless LLCP scenarios. This should ideally support IPP Everywhere / Mopria-style discovery and capabilities, direct printing to IPP URIs, TLS/authentication, PDF passthrough where supported, PWG Raster fallback, duplex/media/tray/finishing options, printer/job status and robust diagnostics.

This would make LLCP more future-proof in light of Windows Protected Print Mode and Microsoft’s move away from third-party printer drivers.

1 Like
2

For LLCP, adding IPP support for Windows should be straight forward given the existing Linux IPP backend. We’ll definitely have a look.

3

As expected, this was a low hanging fruit. Will be supported (for LLCP) with the next service pack. Printer discovery is out of scope, however - you’ll need to pass your http:// or ipp:// endpoints directly.

1 Like