Gnus development mailing list
 help / color / mirror / Atom feed
From: "Johan Kullstam" <kullstam@ne.mediaone.net>
Subject: Re: v.98 pdf decoding broken?
Date: 02 Dec 1999 00:09:25 -0500	[thread overview]
Message-ID: <m2iu2iq67u.fsf@sophia.axel.nom> (raw)
In-Reply-To: Lars Magne Ingebrigtsen's message of "01 Dec 1999 21:42:04 +0100"

Lars Magne Ingebrigtsen <larsi@gnus.org> writes:

> uliw@erdw.ethz.ch writes:
> 
> > I am unable to decode a properly encoded pdf attachment. The file is
> > written to disk and loaded, but remains empty.
> 
> Does this work better in Pterodactyl 0.99?

while looking at the qp-or-uuencode choser back in 0.96 (or was it
0.97...), i noticed some bad behavior with .pdf files.

it seems pdf are ascii but with a CR instead of LF or CF/LF to end the
lines.  (i think this is macintosh format as opposed to unix or ansi.)
anyhow, the choser doesn't see enough non-printable stuff and uses
quoted-printable format.

the problem is that CR doesn't signify end-of-line to many of the
tools and the QP can, therefore, have some extremely long lines.  i've
had the lines get broken and wrapped by my mail processing chain.  i
am not sure if it's gnus/emacs sending, my isp's sendmail, my
fetchmail, my qmail, or gnus/emacs receiving the mail where it gets
clobbered.  somewhere there be dragons.

has anyone else run across this?  how should we handle ascii with long
lines (very few LF chars)?  should this be made uuencoded or perhaps
there is some CR and LF stuff in QP to break the lines and reform them
upon unquoting?

-- 
J o h a n  K u l l s t a m
[kullstam@ne.mediaone.net]
Don't Fear the Penguin!


  reply	other threads:[~1999-12-02  5:09 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-11-24 14:46 uliw
1999-12-01 20:42 ` Lars Magne Ingebrigtsen
1999-12-02  5:09   ` Johan Kullstam [this message]
1999-12-02  5:18     ` Lars Magne Ingebrigtsen
1999-12-02  9:30   ` uliw
1999-12-02 10:06   ` uliw
1999-12-02 23:15     ` Lars Magne Ingebrigtsen

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=m2iu2iq67u.fsf@sophia.axel.nom \
    --to=kullstam@ne.mediaone.net \
    /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).