[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Microsoft Works file translator for GS
<pubpc1@library.ucla.edu> wrote:
> rigby@ptdprolog.net (Jon) wrote:
> >I think that ClarisWorks 4.0 has an AppleWorks 3.0 and AppleWorks GS
> >Translator files.
AppleWorks 3.0, yes (all modules). AppleWorks GS: only Word Processor
files. Others cannot be directly imported, though you can export at
least Spreadsheet files from AppleWorks GS as text files (with formulae)
and import them into ClarisWorks.
> Isn't it true that to get CW to recognize AWGS files, you have
> to edit the file-info so that it reads "pdos" and "awgs" or
> something? The HFS FST does not automatically do this.
Not exactly. The HFS FST uses the newer conventions for encoding ProDOS
filetypes on Mac disks. This gives a creator of 'pdos' and a binary
encoded filetype which starts with 'p' and contains the ProDOS filetype
and auxiliary type.
ClarisWorks might not recognise AppleWorks Classic files if their
filetypes are stored in this form on an HFS disk (it would have to
examine only the first two characters of the filetype, thereby ignoring
the auxiliary type). I have not tried this.
It will work with the older convention: the ProDOS filetype is converted
to a two-digit hexadecimal number. The Mac filetype is this number
followed by two spaces. The creator is still 'pdos'. The ProDOS
auxiliary type is lost.
This produces the following translations:
ProDOS Mac Mac
Filetype Filetype Creator
ADB '19 ' 'pdos'
AWP '1A ' 'pdos'
ASP '1B ' 'pdos'
(The auxiliary type is used to encode the upper/lower case filename for
an AppleWorks file, and can be ignored.)
AppleWorks GS Word Processor files require the file type ($50: GWP) and
auxiliary type ($8010) to be correctly identified. ClarisWorks must
therefore expect the new convention, in which the Mac filetype will be
'pP' followed by two unprintable (and untypeable) characters ($80 and
$10).
--
David Empson
dempson@actrix.gen.nz
Snail Mail: P.O. Box 27-103, Wellington, New Zealand