Attribute "media-col-database"

[paweljarosz82]

Hi Daniel,

Are there any plans to implement "media-col-database" attribute?

I have a side project to print labels on label printer. I have had it working with previous version 2.x.x of the SharpIppNext nuget package by parsing "raw attributes". Since raw attributes are no longer supported (or i'm missing something) i was thinking to implement it by myself. But ...

"media-col-database" is printer attribute of type "1setOf" collection. It contains list of media-col's supported by the printer.

... i can't find similar example of how to implement this "1setOf collection" type in the library ... so any suggestions are welcome how to do that.

I have already added "MediaColDatabase" field of type "MediaCol[]" to "PrinterDescriptionAttributes" class and "MediaColDatabase" constant to "PrinterAttribute" class.

And now I'm stuck with mappings.

Do you have any suggestions how to implement 1SetOf collection in your library?

[danielklecha]

@paweljarosz82 media-col-database is in PWG5100.7.
Currently, I'm trying to add operations and attributes from PWG specifications (also PWG5100.7).
I will add changes in next few weeks, maybe faster.

btw extensions has a lot of attributes so I'm trying to automate process. But pdf files are problematic. I'm trying to use docling to clean up text and convert to markdown.

[paweljarosz82]

Good to know that you are working on adding features to the library.

During my early stage work on adding features I've mentioned in the first post, problem appeared.
I have tested the package on a virtual CUPS Pdf printer and media database returned deviation:
"media-size" "[xy]-dimension" according to the library should be integer, but value I got is Range:

`media-size :: media-size : no value

media-size :: x-dimension : 1270 - 3527778

media-size :: y-dimension : 1270 - 3527778

:: : no value
`
This is mentioned in PWG5100.7 at the end of "6.9.36 media-col-database (1setOf collection)".
To fully support "media-col-database" how should I implement this "range" feature?

1. Should i change type of "[xy]-dimension" to object and add a few if statements?
   Or
2. Should I add new fields to the class MediaSize i.e. "[XY]DimensionRange" and store it there?

I think the first one will brake current users codebase of the library.

What do you think @danielklecha?
Please point me to the right direction :).