Tim, your approach has one problem: If the description/info field of the CUPS queue gets too long, the server name in the service name will get cut off. So a user sees only the description, but not from which server the queue comes. We need to improve my approach that a too long server name gets truncated, with "too long" defined so that the result is a service name containing both a part of the server name and of the queue description, for example cut the server name at 30 characters. If the server name is shorter, or after truncating it, follow my approach.
Tim, your approach has one problem: If the description/info field of the CUPS queue gets too long, the server name in the service name will get cut off. So a user sees only the description, but not from which server the queue comes. We need to improve my approach that a too long server name gets truncated, with "too long" defined so that the result is a service name containing both a part of the server name and of the queue description, for example cut the server name at 30 characters. If the server name is shorter, or after truncating it, follow my approach.