To repeat what a couple of people have already said: you need to save them
as Ascii (text), with the extension .xxe, then (in DOS), do 'xxdecode
cpgtocs.xxe'; or else feed them to your Windows decoder (I use a shareware
en/decoder called Xferpro). This will result in zip file, which you feed
to Winzip (or do PKunzip in DOS).
It may be that if you're not using Xferpro or the like, you have to take
the header junk off the files by hand. The xxencoded part begins with the
word 'begin,' and ends (this is from memory) 'end xxxxx.zip'.
I have also MIME encoded them, using Xferpro, and uploaded the MMe files.
I'm not sure how to incorporate them into an email. I use Pine, but it has
NO information about how to do attachments. So I'll just feed them into
otherwise empty email files via Pine's Read File command. This has worked
in the past for XXEs. Those of you, now the majority, it seems, who use
MIME can let me know if this doesn't work.
The reason I sound so vague is that the university server here has no
information, accessible to those not already in the know, about how to use
MIME. Nor does Pine. As a result, I can't decode files uploaded to the
list in MIME; so I don't use it.
If these 4 files (2 mme, 2 xxe) aare still unusable, could people let me
know at my other email address (mary_b...@compuserve.com) and I'll send
them from there? It's a lot easier; uploading these 4 files to the server
took the best part of an hour. My software is primitive and recalcitrant
when uploading, though fine in most respects.
Best regards
Mary
Mary Bernard
<if1...@cus.cam.ac.uk>
Anne Gardner
> It worked perfectly for me this time, Mary. Thank you.
>
> Anne Gardner
>
Anne
Thanks for letting me know -
Mary
Mary Bernard
<if1...@cus.cam.ac.uk>
Gerald Schlabach
At 12:15 PM 5/1/98 +0100, Mary Bernard wrote:
>I'm sorry people have had so much trouble with my encoded files. I have
>xx-encoded both CPGTOCS.ZIP and OVLISTS.ZIP again, checked that they
>decoded okay with my decoder, and uploaded them anew....
> In any case, Mary's revision, with TOCs, of Tony Woozley's Customization and
> Programming Manual is now available at my website:
> http://www.bluffton.edu/~schlabachg/nb.
>
Thanks, Gerald!
Just a reminder about including URLs in email: many of us have
communications programs that allow launching the browser to load the
page referred to, but only if it's a "well-formed" URL. Some browsers
are more forgiving than others, but still:
1) including the http:// (or ftp://) at the beginning (as Gerald did
above) is usually required for the communications program to see it as a
URL.
2) A final (sentence) period may seem to be part of the URL, and may
defeat loading the page (dread 404 error). That's what I ran into in
this case--removing the period solves the problem.
3) If brackets or parentheses surround the URL, those are generally
benignly ignored by the communications program, and they forestall other
punctuation used in the email sentence. So, this would be fine:
<http://www.bluffton.edu/~schlabachg/nb>.
So would this:
< http://www.bluffton.edu/~schlabachg/nb/>.
Thanks again, Gerald!
Dorothy
*****
Dorothy Day
School of Library and Information Science
Indiana University
d...@indiana.edu
*****
"He also surfs who only sits and waits."