CompuServe Thread

Forum unknown · Telecommunications

#Binary

5 messages in this thread
#2015From: Bill BondDec 16, 1985 7:01 PM
It sounds like we are proceeding toward an AmigaBinary Standard. This is encouraging. I see no reason, however, why a AmigaBinary standard should be a modification of MacBinary. MacBinary has many fields that are Mac specific. The intent of MacBinary is what we need, not it specifically (I participated in the early discussions on MacBinary and believe I can claim the first implementation of MacBinary). With CBM's help we can come up with something that is most appropriate for the Amiga. Note that a MacBinary file is of no use to any computer but a Mac. MacBinary does, however, allow other systems to store a file. Thus, an IBM BBS can store and send MacBinary files. Bill Bond * Reply: 2051
#2051From: Bela Lubkin/SysopDec 17, 1985 12:47 AM
Well, the work has already been done on MacBinary; what I'm saying is that we should look at what they've done, figure out what needs to be transmitted for Amiga files, and use the same framework they did. That way it will be easier to convert files from one format to the other — which >will< be useful, in some cases. Without knowing too much about the Mac, it seems to me that the Amiga could make good use of some MacBinary files, particularly if they have only a data fork. E.g. a font file. You'd download the Mac file, run it through a MacBinary to AmigaBinary converter (or just have the Amiga program recognize MacBinary — which is the real reason for making them similar), this getting not only the data, but also the proper filename and possibly other things like length, etc. Of course you'd still need a seperate program to (for instance) convert Mac format font files, but at least you'd have the file intact, plus whatever useful additional information could be extracted. Don't you agree?
#2051From: Bela Lubkin/SysopDec 17, 1985 12:47 AM
Well, the work has already been done on MacBinary; what I'm saying is that we should look at what they've done, figure out what needs to be transmitted for Amiga files, and use the same framework they did. That way it will be easier to convert files from one format to the other — which >will< be useful, in some cases. Without knowing too much about the Mac, it seems to me that the Amiga could make good use of some MacBinary files, particularly if they have only a data fork. E.g. a font file. You'd download the Mac file, run it through a MacBinary to AmigaBinary converter (or just have the Amiga program recognize MacBinary — which is the real reason for making them similar), this getting not only the data, but also the proper filename and possibly other things like length, etc. Of course you'd still need a seperate program to (for instance) convert Mac format font files, but at least you'd have the file intact, plus whatever useful additional information could be extracted. Don't you agree?
#2051From: Bela Lubkin/SysopDec 17, 1985 12:47 AM
Well, the work has already been done on MacBinary; what I'm saying is that we should look at what they've done, figure out what needs to be transmitted for Amiga files, and use the same framework they did. That way it will be easier to convert files from one format to the other — which >will< be useful, in some cases. Without knowing too much about the Mac, it seems to me that the Amiga could make good use of some MacBinary files, particularly if they have only a data fork. E.g. a font file. You'd download the Mac file, run it through a MacBinary to AmigaBinary converter (or just have the Amiga program recognize MacBinary — which is the real reason for making them similar), this getting not only the data, but also the proper filename and possibly other things like length, etc. Of course you'd still need a seperate program to (for instance) convert Mac format font files, but at least you'd have the file intact, plus whatever useful additional information could be extracted. Don't you agree? – Bela
#2051From: Bela Lubkin/SysopDec 17, 1985 12:47 AM
Well, the work has already been done on MacBinary; what I'm saying is that we should look at what they've done, figure out what needs to be transmitted for Amiga files, and use the same framework they did. That way it will be easier to convert files from one format to the other — which >will< be useful, in some cases. Without knowing too much about the Mac, it seems to me that the Amiga could make good use of some MacBinary files, particularly if they have only a data fork. E.g. a font file. You'd download the Mac file, run it through a MacBinary to AmigaBinary converter (or just have the Amiga program recognize MacBinary — which is the real reason for making them similar), this getting not only the data, but also the proper filename and possibly other things like length, etc. Of course you'd still need a seperate program to (for instance) convert Mac format font files, but at least you'd have the file intact, plus whatever useful additional information could be extracted. Don't you agree? – Bela