Announcements and discussions for Gnus, the GNU Emacs Usenet newsreader
 help / color / mirror / Atom feed
From: bugbear <bugbear@trim_papermule.co.uk_trim>
To: info-gnus-english@gnu.org
Subject: Re: FlateDecode, ASCIIHexDecode, ASCII85Decode, and LZWDecode streams
Date: Thu, 24 Jun 2010 08:53:50 +0100	[thread overview]
Message-ID: <FPmdncIa0-aTkr7RnZ2dnUVZ8uGpnZ2d__28054.4110377834$1291956090$gmane$org@brightview.co.uk> (raw)
In-Reply-To: <01ea2f28-1bcd-4149-b8c5-3f58dfeb9b81@j4g2000yqh.googlegroups.com>

Fren Zeee wrote:
> Dear All,
> 
> I have been playing for a while with files that have small bits of
> FlateDecode, ASCIIHexDecode, ASCII85Decode, and LZWDecode streams. My
> familiarity with these compression methods is limited to using the
> unix uncompress, gunzip and other compiled commands. At one time I was
> able to conveniently decode base64 fragments in emacs using the
> following commands.
> 
> base64-decode-region
>   Command: Base64-decode the region between BEG and END.
> 
> hexlify-buffer and dehexlify-buffer
> 
> Is there a solution within emacs or someone has a method to use
> libraries or to translate code from python/ruby etc. I could not find
> any (apropos decode) with reference to the above compression methods.
> 
> In ruby, FlateDecode and ASCII85Decode can be decompressed with
> existing ruby module which are zlib and Ascii85.

The PostScript spec either directly, or via authoritative references,
documents the compression formats.

Further, since PostScript (doh!) supports these formats,
you can simply use the Filter implementations
in PostScript (e.g. GhostScript) to decompress data.

   BugBear

       reply	other threads:[~2010-06-24  7:53 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <01ea2f28-1bcd-4149-b8c5-3f58dfeb9b81@j4g2000yqh.googlegroups.com>
2010-06-24  7:53 ` bugbear [this message]
2010-06-24  5:39 Fren Zeee

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='FPmdncIa0-aTkr7RnZ2dnUVZ8uGpnZ2d__28054.4110377834$1291956090$gmane$org@brightview.co.uk' \
    --to=bugbear@trim_papermule.co.uk_trim \
    --cc=info-gnus-english@gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).