User Profile
Gianvito_Difilippo
Copper Contributor
Joined 5 years ago
User Widgets
Recent Discussions
Re: Universal Print not supporting IPP tag "nameWithoutLanguage" for attribute "media-type-supported"
Hello, thank you for confirming that. Can you tell me if there is a way to know in advance which types and values are allowed/supported by Universal Print for the attributes to provide when registering the printer? It would be very helpful to perform some sort of validation before registering the printer. For example, we are having issues with the attribute "pclm-strip-height-supported" which the IPP specification says should be of type integer (and be a power of 2), but supplying such values results in an error response.1.5KViews0likes0CommentsRe: The job arrives quickly at Universal Print, but it takes a very long time for it to start printing.
Hi, I'm having this issue as well with our custom connector. We use long polling for notifications, but sometimes the job notification just won't arrive, so we are forced to also poll the notification endpoint every now and then to make sure the job is not delayed too much.1.6KViews0likes1CommentRe: Universal Print not supporting IPP tag "nameWithoutLanguage" for attribute "media-type-supported"
DienVaTuDo Hi, I just want to point out that we are not overriding its value (or rather values, since it's a list) but its IPP tag(s). The values comes straight out of the printer, but sometimes they come with the tag "nameWithoutLanguage" (which byte value is 0x41), instead of "keyword" (0x44). So the only thing we do is changing that 0x41 bytes into 0x44. However, you can find a json file in the attachments with such values and tags. By the way - as far as I know - I can print multiple times when that workaround is used.1.5KViews0likes0CommentsUniversal Print not supporting IPP tag "nameWithoutLanguage" for attribute "media-type-supported"
Hello, we are testing our custom Universal Print connector, which updates the printers' attributes using the ones coming from the printers via IPP. We were able to print on some of the printers, specifically the ones for which the attribute "media-type-supported" was of type "1setOf(keyword)". Instead, we couldn't print on the printers which had "1setOf(nameWithoutLanguage)" as a type for that attribute: the spooler failed to send the print job to Universal Print. Is this behavior intentional? Considering the https://ftp.pwg.org/pub/pwg/candidates/cs-ippjobext20-20190816-5100.7.pdf, "keyword" and "name" (i.e. "nameWithLanguage" or "nameWithoutLanguage") should be allowed. As a workaround, at the moment we are overriding that tag, but in the future we would like to validate the attributes using a fixed criterion, that's why we are reporting this issue. Thanks, Gianvito1.7KViews0likes4CommentsRe: Cannot leverage document conversion on UP
Jimmy_Wu hello Jimmy, thanks for your response. We solved our problem by adding the IPP attribute "media-col-supported" in the registration step. This attribute seems to be missing in the https://docs.microsoft.com/en-us/universal-print/hardware/universal-print-isv-connector#list-of-supported-printer-description-attributes, but one of your developers kindly provided us with a more exhaustive list. We didn't think that could be the cause of the error since oxps printers worked fine, but now we can also print to PDF and PCLm printers. We are truly grateful for your support, Gianvito784Views1like0CommentsCannot leverage document conversion on UP
Hello! I'm developing a custom UP Connector and the communication flow with the Infrastructure Printer and the Notification Service described in the IPP-Infra spec works quite well. However, I've registered a printer that doesn't support "application/oxps" as a document format: the connector talks straight to the Output Device via IPP, not using the printer's driver (which I reckon would be able to handle such a format). The Output Device does support "application/pdf" though, but when I try to print a document from a user account the printer had been shared with, it results in an error. The document conversion is enabled on the Management Portal and the client Windows version is 10.0.19042 Build 19042. Are there additional steps to follow to leverage the conversion feature? Many thanks, Gianvito914Views0likes2Comments
Recent Blog Articles
No content to show