Your message dated Sun, 14 Jan 2024 14:08:33 +0100
with message-id <[email protected]>
and subject line Re: Bug#794314: /usr/bin/ppmtosixel: 7bit encoding of sixel
files is more portable, works with xterm
has caused the Debian Bug report #794314,
regarding /usr/bin/ppmtosixel: 7bit encoding of sixel files is more portable,
works with xterm
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 [email protected]
immediately.)
--
794314: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=794314
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: netpbm
Version: 2:10.0-15.2
Severity: minor
File: /usr/bin/ppmtosixel
A sixel image uses a DCS (0x90) in the header and a ST (0x9C) in the footer,
however when mixed with utf8, these may be discarded as malformed.using the
alternate encodings of ^[P (escape P) for DCS and ^[\ (escape \) for ST avoids
this problem and works everywhere I have tested (should work everywhere) at the
cost of two bytes per image. I tried using the utf representations of DCS and
ST, but support for them appears to be non existent. Seven bit clean appears to
be the best practice. An advanced solution would be the addition of a command
line option, but i don't think that would be useful except for generating test
images. I have attached a little script that makes sixel images 7 bit clean.
-- System Information:
Debian Release: stretch/sid
APT prefers stable
APT policy: (500, 'stable')
Architecture: i386 (i686)
Kernel: Linux 3.16.0-4-686-pae (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)
Versions of packages netpbm depends on:
ii libc6 2.19-18
ii libjpeg62-turbo 1:1.4.0-7
ii libnetpbm10 2:10.0-15.2
ii libpng12-0 1.2.50-2+b2
ii libtiff5 4.0.3-13
ii zlib1g 1:1.2.8.dfsg-2+b1
Versions of packages netpbm recommends:
ii ghostscript 9.06~dfsg-2
netpbm suggests no packages.
#!/usr/bin/perl -wp
use bytes;
s!([\x80-\x9f])!qq(\e).chr(ord($1)-64)!ge
--- End Message ---
--- Begin Message ---
Version: 2:11.04.05-2
On 2015-08-01 Ben Hildred <[email protected]> wrote:
> Package: netpbm
> Version: 2:10.0-15.2
> Severity: minor
> File: /usr/bin/ppmtosixel
> A sixel image uses a DCS (0x90) in the header and a ST (0x9C) in the
> footer, however when mixed with utf8, these may be discarded as
> malformed.using the alternate encodings of ^[P (escape P) for DCS and
> ^[\ (escape \) for ST avoids this problem and works everywhere I have
> tested (should work everywhere) at the cost of two bytes per image. I
> tried using the utf representations of DCS and ST, but support for
> them appears to be non existent. Seven bit clean appears to be the
> best practice. An advanced solution would be the addition of a command
> line option, but i don't think that would be useful except for
> generating test images. I have attached a little script that makes
> sixel images 7 bit clean.
Hello,
netpbm 11.04 added a -7bit option for ppmtosixel.
cu Andreas
--- End Message ---
