Description of problem: The arguments to the unsupported-character-set message are swapped, so that it looks like: Unsupported character set \"host.name\" from host iso-8859-1! Clients must use us-ascii or utf-8. Future versions will reject this request. It's trivial to swap the parameters round. Version-Release number of selected component (if applicable): cups-1.3.7-22.el5
Technical note added. If any revisions are required, please edit the "Technical Notes" field accordingly. All revisions will be proofread by the Engineering Content Services team. New Contents: When a client uses an unsupported character set, an error message is logged. A mistake in the error message formatting caused some words to be swapped around. The formatting has now been fixed.
Technical note updated. If any revisions are required, please edit the "Technical Notes" field accordingly. All revisions will be proofread by the Engineering Content Services team. Diffed Contents: @@ -1 +1 @@ -When a client uses an unsupported character set, an error message is logged. A mistake in the error message formatting caused some words to be swapped around. The formatting has now been fixed.+The unsupported-character-set error message used the formatting: "Unsupported character set [host.name] from host [character.set]! Clients must use us-ascii or utf-8." This was due to a mistake in the error message formatting. With this update, the parameters are swapped and the error message uses the correct parameter order.
*** Bug 662705 has been marked as a duplicate of this bug. ***
An advisory has been issued which should help the problem described in this bug report. This report is therefore being closed with a resolution of ERRATA. For more information on therefore solution and/or where to find the updated files, please follow the link below. You may reopen this bug report if the solution does not work for you. http://rhn.redhat.com/errata/RHBA-2011-0095.html