Bug#623269: Fails to print files with german umlauts in locale de_DE
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
Hi,
Thanks for the clearify with upstream.
Am Mo den 1. Dez 2014 um 12:39 schrieb Stéphane Aulery:
> Upstream answered:
>
> > This isn't something we can fix in CUPS - the filename on the command-line
> > is converted to UTF-8 (from the locale-specified charset) in order to
> > provide the correct encoding for the print job title, but there is no way
> > for us to know the proper encoding for filenames.
> >
> > (this problem has existed long before CUPS...)
Well, that simply is not true. It works pretty well if one is looking at
the common workflow. The command line encoding would be always the same
than the enconding of the filename itself. Otherwise the user will not
be able to access the file. I tried to find a use case where you would
have different encoding on the command line than on filesystem but I
cannot find any reasonable one.
So simply using the filename without any encoding change would solve
that problem. I am one of the upstream developers of geeqie and yes, we
also had problems like that in the past. But that was clearly a bug and
is solved present days. So I think I really know what I am talking
about. However, there might exist a problem with that if the user input
comes from a GUI input and not from the command line. There you really
might have a problem with that. But usually the filename comes from a
selection box that solved the problem here too.
It is fully ok for me that cups uses utf-8 internal but the interface to
the user should be consistent.
> > One method of dealing with this is to redirect stdin, e.g.:
> >
> > lp -d printer <filename-with-special-chars
>
> It does not change the situation, but at least a workaround exists. I
> think the real solution would be to switch to de_DE.UTF-8. You can use
> "# dpkg-reconfigure locales" for that.
Regards
Klaus
- --
Klaus Ethgen http://www.ethgen.ch/
pub 4096R/4E20AF1C 2011-05-16 Klaus Ethgen <Klaus@Ethgen.de>
Fingerprint: 85D4 CA42 952C 949B 1753 62B3 79D0 B06F 4E20 AF1C
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1
iQGcBAEBCgAGBQJUfFhfAAoJEKZ8CrGAGfasq7ML/3al2pssrdLx0w94umKKkICf
Hpw5r3SKZYJ+9pL9nlt+S4RN1g4mpO/ZjPhCDAbwhlDxlepW3+WD+7xjlTcp7wLb
HlOqLU63JTe9ZjvLlv6ZjY2QoVu0Pvla6IA66G3Ntp7gFOLqCY/w1VH6jyQD4ks5
dfN4u+ZKRKyQVnmQvQrIAxG5acSReh8r/FvNii6BXGVM2y1m0Ta94bAMptzQJ/He
XMO5Gy3rRILzY3XWRmjs4thVaJkaxMQdIiMS9MKRyQRUT6slH9KyY6gJmW/S831r
cFSeslxPQhpfXuS77d4QcSHGxctqZtFqxjinAvWIthw18jusrsx9aggkeGzLrJog
lrLdMKAKrt44p72LQcWdbbVQP5AKTzz5HzQH/Wsy2kMwWrjOBh1XD7Ny51onIwZF
UjtZKhWCXxDQJGgv8uQvCglg0PJzvrGqFzwzEVGKcEbaPGujYmq7dKf0pLe0hHKC
OOWLR/Y+9DDToTRBMm44ChnBEoPwKAOtDzUscotTGw==
=SuKh
-----END PGP SIGNATURE-----
Reply to: