[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#795468: marked as done (Files not printable if they have german umlauts (latin1) in name)

Your message dated Sun, 14 Aug 2022 15:09:25 +0100
with message-id <14082022150508.6339b98c4c4e@desktop.copernicus.org.uk>
and subject line Re: Bug#623269: Fails to print files with german umlauts in locale de_DE
has caused the Debian Bug report #623269,
regarding Files not printable if they have german umlauts (latin1) in name
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
623269: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=623269
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

Package: cups-client
Version: 2.0.3-10
Severity: normal

I have pdf files which have german umlauts in name. If I try to print
them, I get the error
   lp: Error - unable to access "..." - Datei oder Verzeichnis nicht gefunden

My filesystem is, as all of my system, proper encoded with ISO-8859-1.

I believe, that lp is doing wrong character encoding internally for no
need. Please change it to use the name, the user is giving on the
command line and not some interpreted one.

- -- System Information:
Debian Release: stretch/sid
  APT prefers unstable
  APT policy: (800, 'unstable'), (500, 'testing'), (110, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.0.7 (SMP w/8 CPU cores)
Locale: LANG=de_DE, LC_CTYPE=de_DE (charmap=ISO-8859-1) (ignored: LC_ALL set to de_DE)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)

Versions of packages cups-client depends on:
ii  adduser        3.113+nmu3
ii  cups-common    2.0.3-10
ii  libc6          2.19-19
ii  libcups2       2.0.3-10
ii  libcupsimage2  2.0.3-10

cups-client recommends no packages.

Versions of packages cups-client suggests:
ii  cups       2.0.3-10
ii  cups-bsd   2.0.3-10
pn  smbclient  <none>
pn  xpp        <none>

- -- no debconf information

- -- 
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 v2

iQGcBAEBCgAGBQJVzbKMAAoJEKZ8CrGAGfaso8IMALHqtgNIWytfjGnS5eeFWJVt
ifXOtaNmwsxYIlUvJR/TW4Wh0gei3ES2nRJfeh4SQrYAcNuRpAv7JkD9ZqabfGwy
Uepg9T43uSD2J+6VBp2Dc+BsWT8KnTABOBg8uRUykFe/9jK3r00T8kFoK8Fjaqj+
U0uMdD5CVCxix6PvcpIMx1KUpTcHz2bcEwSi5zb9rBNSaKR92Dx+jwLhhbCyPkir
hwqhQOt/qwElHJw20nwWFyLfIqtRypkQ8vLbGZGzVLXMexqj18krGghzBlaDTDJH
9n4Eoiig1RX0Saf+87vtlGxApTBN/AWMuNLdIbRnj6LoWQGMOOCaskrwgaLMtVLR
GOqmym4qoOPfhMMjU3H0V6YihUD3vkujqlDP0TbiNjbp4WkngeekCK4hjjdGQBzs
c0gy1rgYdXf+nYg9+MPtGCowZb3yTCKvOZ1/7FwuTq7HrQDvR0mkN9uLynDAG7kh
dzIBfUUsxRPFocfVIEa0w2rdY77gYDFby3w/1dKw6A==
=26Uc
-----END PGP SIGNATURE-----

--- End Message ---
--- Begin Message --- 
On Mon 18 Apr 2011 at 21:53:35 +0100, Klaus Ethgen wrote:

> Package: cups-client
> Version: 1.4.6-4
> Severity: normal
> 
> I saw this bug for long time now. When I print a file that have german
> umlauts in the file name, cups tell me:
> lp: Fehler ? kein Zugriff auf ?XXXXXXXXXXXXXXXXXXrüXXXXXX.pdf? ? Datei oder Verzeichnis nicht gefunden
> 
> When I unset all locale settings the file is printable.
> 
> I think that this happens cause of a wrong assuming that all is UTF-8.
> But the locale de_DE implies ISO-8859-1 if no other charset is mention.
> 
> On my system I have no UTF-8. Not in filesystem and not in locale
> settings.
> 
> However, that is only a assuming, I am not sure if that is really the
> problem.

Thank you for your report, Klaus.

In the light of all the information we have, there does not appear to
be a resolution to this issue within CUPS. Hence closing.

Regards,

Brian.

--- End Message ---
Reply to: