Skip to content
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

charset encoding always latin1 #15

Closed
michaelrsweet opened this issue Apr 11, 2003 · 4 comments
Closed

charset encoding always latin1 #15

michaelrsweet opened this issue Apr 11, 2003 · 4 comments

Comments

@michaelrsweet
Copy link
Collaborator

Version: 1.1.18
CUPS.org User: maccy2.yahoo

no matter what is defined for default charset in cupsd.conf (the default should be utf-8) cups treats all text files as latin1. printing an utf-8 encoded text file should print file with a default installtion because utf-8 is the default but it isn't really.
Shouldn't there also be an option for lp/lpr to define a charset encoding, which should be handed over to the cups server?

@michaelrsweet
Copy link
Collaborator Author

CUPS.org User: mike

This is a support question.

Basically, you need to define your locale (the LANG environment variable) to a UTF-8 locale, otherwise CUPS will assume that you want to print using the locale's default encoding.

@michaelrsweet
Copy link
Collaborator Author

CUPS.org User: maccy2.yahoo

sorry, both root's LC_CTYPE is de_DE.UTF-8 and user's LANG is de_DE.UTF-8. printing an UTF-8 encoded text file containing umlauts gives results like cat'ing UTF-8 to an 8bit terminal. UTF-8 conversion is not being done. No support question, a bug ;-)

@michaelrsweet
Copy link
Collaborator Author

CUPS.org User: maccy2.yahoo

also printing html which has it's site encoding in meta tags does not work with anything else than latin1. utf-8 encoded html code (containing the charset in meta tag) is printed as 8bit text.

@michaelrsweet
Copy link
Collaborator Author

CUPS.org User: mike

Have you copied the corresponding CUPS message catalog which (currently) defines the charset to the UTF-8 message catalog directory?

This is not a bug.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant