9:59 a.m.
Adrian Aichner <adrian(a)xemacs.org> writes:
>>>>> "Jarl" == Jarl Friis
<jarl(a)diku.dk> writes:
Jarl> Adrian.Aichner(a)t-online.de (Adrian Aichner) writes:
>> >>>>> "Jarl" == Jarl Friis <jarl(a)diku.dk>
writes:
>>
Jarl> Hi.
>>
Jarl> I have made a patch to pcl-cvs (earlier posted). Now I've
Jarl> also read the `describe-beta' :-) which tells me to post the
Jarl> patch to the maintainer of pcl-cvs. in pcl-cvs.el I find:
Jarl> ;; Maintainer: (Stefan Monnier)
Jarl> ;; monnier+lists/cvs/pcl(a)flint.cs.yale.edu
>>
>> Hi Jarl,
>>
>> for XEmacs packages use
>> M-x pui-list-packages
>> then press
>> i runs the command pui-display-info
>> on the package in question
>> You'll get
>> Author version: R-2_9_9 2002-01-07: XEmacs Development Team
<xemacs-beta(a)xemacs.org>
>> for pcl-cvs.
Jarl> OK, thanks. So where ever that information comes from (I
Jarl> guess Makefile and/or package-info.in) I see that my earlier
Jarl> posting was to the right place, but not correctly formatted,
Jarl> it should be MIME attached and include some words for the
Jarl> ChangeLog
There are two instances of the patch in your previous mail.
Once verbatim and once as attachment.
Why is that?
From the `describe-beta' I read:
Emailed patches should
preferably be sent in MIME format and quoted
printable encoding (if necessary).
I took that as both verbatim quoted in the email and a MIME
attachement, let me know if I misunderstood this. Is the "and" ment as
an "or"? What is "quoted printable encoding"?
Jarl> I will repost it and hope Steve won't get too confused.
Please send a followup to the patch your are replacing and use the
SUPERSEDES keyword in the header on on the first line in the body.
I'll do that.
Examples exist in the xemacs-patches archive.
I'll have a look.
Please do. Patcher may be for you.
See item 6 of
http://www.xemacs.org/Develop/index.html
I'll have a look at patcher.
Jarl> I take the late reaction to my first posting is due to Steve
Jarl> absence.
Well, you mentioned that more work needs to be done.
I read this that you will probably follow up with a patch.
probably yes, but only if there are no objections to the new treatment
of default arguments.
Jarl
10:43 a.m.
Jarl Friis wrote:
> There are two instances of the patch in your previous mail.
>
> Once verbatim and once as attachment.
>
> Why is that?
>From the `describe-beta' I read:
Emailed patches should preferably be sent in MIME format and quoted
printable encoding (if necessary).
I took that as both verbatim quoted in the email and a MIME
attachement, let me know if I misunderstood this.
You did.
Is the "and" ment as an "or"?
No. "using" would be a reasonable substution, i.e.
Emailed patches should preferably be sent in MIME format,
using quoted printable encoding (if necessary).
What is "quoted printable encoding"?
It's a mechanism for ensuring that the data isn't modified during
transit. Certain characters are encoded as "=XX", where XX is the
character's hex value. Also any newlines which are introduced to break
lines to the 80-character limit are preceded with an "=".
Basically, it's saying "use quoted-printable encoding rather than
base-64 encoding or no encoding". Base-64 is completely illegible
unless decoded; no encoding risks data corruption in transit.
--
Glynn Clements <glynn.clements(a)virgin.net>
11:32 a.m.
Glynn Clements <glynn.clements(a)virgin.net> writes:
Jarl Friis wrote:
>
> >From the `describe-beta' I read:
> Emailed patches should preferably be sent in MIME format and quoted
> printable encoding (if necessary).
>
> I took that as both verbatim quoted in the email and a MIME
> attachement, let me know if I misunderstood this.
You did.
> Is the "and" ment as an "or"?
No. "using" would be a reasonable substution, i.e.
Emailed patches should preferably be sent in MIME format,
using quoted printable encoding (if necessary).
I see, thanks.
> What is "quoted printable encoding"?
It's a mechanism for ensuring that the data isn't modified during
transit. Certain characters are encoded as "=XX", where XX is the
character's hex value. Also any newlines which are introduced to break
lines to the 80-character limit are preceded with an "=".
Basically, it's saying "use quoted-printable encoding rather than
base-64 encoding or no encoding". Base-64 is completely illegible
unless decoded; no encoding risks data corruption in transit.
In that case, how do I ensure that I attach it as "quoted printable
encoding"? i.e. what MIME-type major/minor is that? As far as I know MIME
attachments (any type) are never modified during transit.
Jarl
12:11 p.m.
Jarl Friis wrote:
> > What is "quoted printable encoding"?
>
> It's a mechanism for ensuring that the data isn't modified during
> transit. Certain characters are encoded as "=XX", where XX is the
> character's hex value. Also any newlines which are introduced to break
> lines to the 80-character limit are preceded with an "=".
>
> Basically, it's saying "use quoted-printable encoding rather than
> base-64 encoding or no encoding". Base-64 is completely illegible
> unless decoded; no encoding risks data corruption in transit.
In that case, how do I ensure that I attach it as "quoted printable
encoding"? i.e. what MIME-type major/minor is that?
It isn't a type, it's a "transfer encoding". A typical patch
attachment would have something like:
Content-Type: text/plain
Content-Transfer-Encoding: quoted-printable
AFAIK, VM will use the setting of vm-mime-8bit-text-transfer-encoding
to determine the encoding of text/plain attachments. The default is
quoted-printable.
As far as I know MIME attachments (any type) are never modified
during transit.
A lot of mail-handling software doesn't understand MIME; it just
treats the entire message as "text".
Long lines may be truncated, line terminator characters (CR, LF, CRLF)
may be converted, tabs may be converted to spaces, characters outside
of the range 32-126 may be discarded, mangled, or cause odd behaviour.
Both base-64 and quoted-printable encodings eliminate these problems
by encoding attachments in such a way that they don't contain any
problematic characters or long lines.
--
Glynn Clements <glynn.clements(a)virgin.net>
12:47 p.m.
Glynn Clements <glynn.clements(a)virgin.net> writes:
Jarl Friis wrote:
> > > What is "quoted printable encoding"?
> >
> > It's a mechanism for ensuring that the data isn't modified during
> > transit. Certain characters are encoded as "=XX", where XX is the
> > character's hex value. Also any newlines which are introduced to break
> > lines to the 80-character limit are preceded with an "=".
> >
> > Basically, it's saying "use quoted-printable encoding rather than
> > base-64 encoding or no encoding". Base-64 is completely illegible
> > unless decoded; no encoding risks data corruption in transit.
>
> In that case, how do I ensure that I attach it as "quoted printable
> encoding"? i.e. what MIME-type major/minor is that?
It isn't a type, it's a "transfer encoding". A typical patch
attachment would have something like:
Content-Type: text/plain
Content-Transfer-Encoding: quoted-printable
AFAIK, VM will use the setting of vm-mime-8bit-text-transfer-encoding
to determine the encoding of text/plain attachments. The default is
quoted-printable.
OK, so as I use gnus (newbie) whihch encodes in base64 I guess I am in no
trouble wrt that.
Jarl
8340
days inactive
8340
days old
4 comments
2 participants
participants (2)
-
Glynn Clements -
Jarl Friis