#3 often interacts with #1 because most encoding systems defeat the inter-platform translation abilities that are built into most mailers.
Lots of places (try a web search utility). For example,
If you don't already have any understanding of file formats, mail systems, and cross-platform data communications, basically if you don't know what I mean by "computer platform" or "MIME", try this first:
This method will usually work with or without MIME capability and it will usually work between any two types of computers connected to the Internet. Its disadvantages are that it is a bit clumsy and for very large GEDCOM files it may fail.
There is also one special situation in which it won't work: if the sender has a MIME-compatible mailer and the receiver doesn't and the GEDCOM contains certain special characters, like letters with accents. The result will be a GEDCOM file that contains things that look like "=0Dsdf=87." Sometimes you can get around this if the sender can force his/her mailer to turn off the Q-P (or Quoted-Printable) encoding. Some Eudora versions allow this as an option. If that isn't possible, there are still ways around this, but they involve unpleasant things like base64 decoders. See below, if you dare.
By "different computers," I mean computers with wholly different operating systems, for example, Macintosh to MS-Windows, UNIX to Macintosh, or UNIX to Windows, that is two systems where you can't read a text file created by one on the other without doing anything special. If you don't understand this, use the general method. In fact, oftentimes, the general method will be easiest in this case.
Send the file as an attachment, as in the previous case where the computers were the same. Now the recipient should save the file when it arrives and must then convert the file format. If the receiver's computer is a Macintosh, some versions of Stuffit can do this for you. Undoubtedly, there are similar utilities on other platforms if you can find them. Sometimes, you can do a binary FTP transfer of the file to a computer of the same type as the sender's and then do an ASCII transfer of the file back to your computer. This will usually take care of necessary cross-platform translations.
As metioned earlier, this is probably the nastiest situation you can encounter (at least that isn't your fault for trying to do something fancy).
1. The receiver can save the mail to a file and run it through a Q-P decoder. I've never seen a Q-P decoder, but there must be one somewhere. Fortunately, they are easy to write -- well, for a programmer anyway.
2. The sender should attach the GEDCOM file to the mail as a MIME attachment. Now the receiver has to get a base64 decoder. Fortunately, there are a number of them out there, since, like the hypothetical Q-P decoder, they aren't hard to write. Then the receiver should save the mail to a file. Try running the base64 decoder. If it works, great! Otherwise, the receiver will probably have to save the received mail file and edit out the headers and the mail body, leaving only the base64 encoded attachment that contains the GEDCOM. Run the decoder again. If it doesn't work then, give up and put a stamp on a disk.
Sometimes, really huge GEDCOM files are just too big to send in one piece by e-mail. This used to be really common, but fortunately it doesn't happen a lot nowadays. This typically only applies to files larger than 1 MB (megabyte).
At this point, we're getting into a higher degree of computer skill. I have to assume that you know how to use file compression software and do things like change program options.
You have two options:
1. Compress the file and then attach it. PKZIP is probably the best with Windows or DOS machines. For UNIX, use gzip or compress. With Macintoshes, Stuffit is the way to go. The receiver must have software that can decompress this type of compressed file.
2. Reconfigure the mailer to break up large attachments and/or set a smaller break-up size limit.
This case often requires computer proficiency to deal with it. See the options for the above case. Then, after you extract/save and decompress the file if necessary, you have to convert the file format. If you are using a Macintosh, some versions of Stuffit can do this for you. Undoubtedly, there are similar utilities on other platforms if you can find them. Sometimes, you can do a binary FTP transfer of the file to a computer of the same type as the sender's and then do an ASCII transfer of the file back to your computer. This will usually take care of necessary cross-platform translations.
If none of that works or you're just curious, there are a number of Web sites with useful info.
By Ben Buckner.
Requests for file tranmission and conversion help may be ignored due to
the big piles of work I have to do.