-
Notifications
You must be signed in to change notification settings - Fork 464
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Incorrect character encoding #1958
Comments
CUPS.org User: mike Need to add a _cupsTranscodeArgs() function to convert the argv[] array from the locale encoding to UTF-8. |
CUPS.org User: mike Fixed in Subversion repository. |
"str1958.patch": Index: berkeley/lpc.c--- berkeley/lpc.c (revision 5922)
/*
/*
/*
deletefile = 0; Index: systemv/cupstestppd.c--- systemv/cupstestppd.c (revision 5922)
/*
/*
dest = NULL; Index: systemv/cupstestdsc.c--- systemv/cupstestdsc.c (revision 5922)
/*
http = NULL; Index: systemv/cancel.c--- systemv/cancel.c (revision 5922)
/*
/*
http = NULL; Index: systemv/lpoptions.c--- systemv/lpoptions.c (revision 5922)
/*
/*
silent = 0; Index: systemv/lppasswd.c--- systemv/lppasswd.c (revision 5922)
/*
@@ -181,6 +184,42 @@ setlocale(LC_TIME, new_lc_time);
Index: cups/i18n.h--- cups/i18n.h (revision 5922) ifdef __cplusplus} |
Version: 1.2-current
CUPS.org User: jerome.alet
Mike said that in CUPS 1.2.x and higher, job's title and filename were always encoded in UTF-8 :
http://www.cups.org/newsgroups.php?s10031+gcups.general+v10038+T0
It seems it's not the case at least with CUPS 1.2.1 : the title
passed on the backend's command line is NOT encoded in UTF-8.
I printed using the lp command from an xterm, with a French locale using
the ISO-8859-15 charset.
The backend's command line received the title as I typed it in my
xterm as the argument to lp's -t command line option.
If I look at a dump of CUPS' /var/spool/cups/c00501 file, I've got
the confirmation :
Could each string coming from the end user be converted into UTF-8 (title, filename...) or made consitent with the attributes-charset ?
Should the filename conversion occur or not ? Couldn't this break some filters and/or backends when printing in raw mode ?
The text was updated successfully, but these errors were encountered: