attah
commented
2 years ago Interesting idea. This is certainly in the "good enough" spirit of SeaPrint. However; there is a "proper" way to do it that i have not explored yet - both due to not having a printer supporting it, and priorities. It would also address the obvious issue here - not being able to translate the strings (not that it is enabled currently).
The printer actually provides a dictionary for translation - and more relevant in this case, explanation. See "printer-strings-uri". Could you please send me your printer's dictionary so i can try? That doesn't mean it must work this way, but i should probably at least try.
Another thing i have considered is to collect the 100 or so most common private media types... should have a similar, but less fun effect. Anyway; currently the lookup table is here: https://github.com/attah/harbour-seaprint/blob/6095694d92ccafd076f13a56b85136e962d0e943/qml/pages/utils.js#L733 Probably programmatic prettification would also stay in javascript, but getting the printer dictionary would certainly have at least some c++. The reason for some seemingly common names missing is that they appear to not be in the spec https://www.iana.org/assignments/ipp-registrations/ipp-registrations.xhtml
JSEHV
At the moment the "media-type-supported” tags are not nicely showing up in SeaPrint in a human friendly format and I (and probably you too) would prefer to see all Supported Media Types in a human friendly way. I’ve analysed all the supplied IPP logs in the SeaPrint thread on the Sailfish forum and also all my in the past supplied IPP logs of printers regarding the "media-type-supported” tags.
What I found out analysing all these tags in the IPP logs is that there is a way we can solve this programmatically. To get there, we need to (I think in this exact order):
(Optional)
We should end up with a very nice list in a human friendly format. See the Media Type Supported.pdf file for the result, if I am correct.
As you can see in the PDF-file, also the first 3 photographic types will change (current is in between brackets), but still very understandable and in my view perfectly correct. The nice thing if this all is, whatever the amount of strings is thrown to SeaPrint via IPP tags by printers, SeaPrint will all solve it nicely in a programmatical way (jippie!) :)
Hope you like the solution and are able to implement it.