Announcements and discussions for Gnus, the GNU Emacs Usenet newsreader
 help / color / mirror / Atom feed
From: Fren Zeee <frenzeee@gmail.com>
To: info-gnus-english@gnu.org
Cc: Fren Zeee <frenzeee@gmail.com>
Subject: FlateDecode, ASCIIHexDecode, ASCII85Decode, and LZWDecode streams
Date: Wed, 23 Jun 2010 22:39:07 -0700 (PDT)	[thread overview]
Message-ID: <294c0e36-8ed5-48db-9c61-c9d9fff95721__38278.2800392762$1291957098$gmane$org@x27g2000yqb.googlegroups.com> (raw)

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.

Thank You.

P.S. I am including links that may help anyone interested.

http://www.frugalcorner.com/lzw/lzwfree.html
http://groups.google.com/group/comp.compression/browse_thread/thread/2d88635982a60b54/15fc41f6e3556d9?q=Decompressing+LZW+compression+from+PDF#015fc41f6e3556d9

             reply	other threads:[~2010-06-24  5:39 UTC|newest]

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

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='294c0e36-8ed5-48db-9c61-c9d9fff95721__38278.2800392762$1291957098$gmane$org@x27g2000yqb.googlegroups.com' \
    --to=frenzeee@gmail.com \
    --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).