public inbox for docbook-tools-discuss@sourceware.org
 help / color / mirror / Atom feed
From: "Edward C. Bailey" <ed@redhat.com>
To: <docbook-tools-discuss@sourceware.cygnus.com>
Subject: Re: Docbook in Red Hat 7.1
Date: Thu, 26 Apr 2001 17:34:00 -0000	[thread overview]
Message-ID: <lflmon5gg6.fsf@lacrosse.corp.redhat.com> (raw)
In-Reply-To: <Pine.LNX.4.33.0104270000300.2993-100000@hvdkooij.xs4all.nl>

>>>>> "Hugo" == Hugo van der Kooij <hvdkooij@vanderkooij.org> writes:

Hugo> On 26 Apr 2001, Edward C. Bailey wrote:
...
>> I'm not sure why this is necessary; I just pulled the files down from my
>> email, and compared them with the originals, and the files have
>> identical md5sums.  So if anyone else sees this kind of problem, please
>> let me know.  That way I can try to figure out whether it is my mailer
>> doing bad MIME things or not...

Hugo> I noticed they were encoded as: Application/OCTET-STREAM

Hugo> Which should mean the get transfered pretty much transparant. But
Hugo> after I saved them I found they were using CR/LF and vim reported
Hugo> this as: "flo-db2indexed-html" [dos] 51L, 1166C

Interesting; vim does not report this when I open the original file
here...

Hugo> It might be an issue with the email software: User-Agent: Gnus/5.0808
Hugo> (Gnus v5.8.8) Emacs/20.7

Since I got matching md5sums on the original and the files taken from my
email, we either have a situation where my emailer (gnus) is both encoding
and decoding incorrectly (so they cancel out, and I see no change), or I'm
guilty of cockpit error, or some peoples' emailers are doing something
incorrect when decoding.  I'm not sure which it is, so I'll do some
research on my end to see if I'm messing it up or not... :-)

                                Ed
-- 
Ed Bailey        Red Hat, Inc.          http://www.redhat.com/

  reply	other threads:[~2001-04-26 17:34 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-04-21 14:35 Peter Toft
2001-04-21 14:39 ` Mark Galassi
2001-04-21 14:45   ` Peter Toft
2001-04-21 15:35   ` Tim Waugh
2001-04-21 17:48     ` Edward C. Bailey
2001-04-22  1:05       ` Peter Toft
2001-04-24 13:17         ` Edward C. Bailey
2001-04-26 10:26           ` Wookey
2001-04-26 12:00             ` Peter Toft
2001-04-27 12:01             ` Peter Toft
2001-04-30  2:22               ` Wookey
2001-04-26 11:47           ` Peter Toft
2001-04-26 11:54             ` Edward C. Bailey
2001-04-26 15:05               ` Hugo van der Kooij
2001-04-26 17:34                 ` Edward C. Bailey [this message]
2001-04-29  8:15                   ` Hugo van der Kooij
2001-04-26  3:04       ` Eric Bischoff

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=lflmon5gg6.fsf@lacrosse.corp.redhat.com \
    --to=ed@redhat.com \
    --cc=docbook-tools-discuss@sourceware.cygnus.com \
    /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 read-only IMAP folder(s) and NNTP newsgroup(s).