Bug 608016 - Typo in unsupported-character-set error message
Summary: Typo in unsupported-character-set error message
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 5
Classification: Red Hat
Component: cups
Version: 5.5
Hardware: All
OS: Linux
low
medium
Target Milestone: rc
: ---
Assignee: Tim Waugh
QA Contact: qe-baseos-daemons
URL:
Whiteboard:
Keywords: EasyFix
: 662705 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-06-25 12:12 UTC by Tim Waugh
Modified: 2018-11-14 17:33 UTC (History)
5 users (show)

(edit)
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.
Clone Of:
(edit)
Last Closed: 2011-01-13 23:29:43 UTC


Attachments (Terms of Use)


External Trackers
Tracker ID Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2011:0095 normal SHIPPED_LIVE cups bug fix update 2011-01-12 17:21:21 UTC

Description Tim Waugh 2010-06-25 12:12:09 UTC
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

Comment 4 Tim Waugh 2010-09-23 16:25:14 UTC
    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.

Comment 6 Eva Kopalova 2010-11-19 10:04:38 UTC
    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.

Comment 8 Tim Waugh 2010-12-14 12:47:13 UTC
*** Bug 662705 has been marked as a duplicate of this bug. ***

Comment 10 errata-xmlrpc 2011-01-13 23:29:43 UTC
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


Note You need to log in before you can comment on or make changes to this bug.