The problem here is not in windows or mac its in the operating system on which
windows is running, typicaly MS-DOS. The problem only occurs with some dos
FAT->ISO conversion utilities. you best bet is to simply try to find a better
file system converter. No other operating system has this problem that i am
aware of.
And by hi-ascii i presume you mean chars of values less than 32 (including
negatives) ?
On Fri, 27 Oct 2000 [EMAIL PROTECTED] wrote:
> To: [EMAIL PROTECTED]
> Subject: Digest metacard.v004.n032
> Reply-To: [EMAIL PROTECTED]
>
>
> -------------- BEGIN metacard.v004.n032 --------------
>
> 001 - "Claude Lemmel" <opus.spe - Re: File Names
> 002 - Scott Rossi <scott@tactil - Re: File Names
> 003 - [EMAIL PROTECTED] - RE: File Names
> 004 - Kevin Miller <kevin@runre - Re: File Size?
> 005 - Craig Spooner <cspooner@l - Re: Change of list software
> 006 - [EMAIL PROTECTED] - Re: File Names
>
> This is the MetaCard mailing list.
> Archives: http://www.mail-archive.com/metacard%40lists.runrev.com/
> Info: http://www.xworlds.com/metacard/mailinglist.htm
> Please send any bug reports to <[EMAIL PROTECTED]>, not this list.
>
>
> --------------- MESSAGE metacard.v001.n002.1 ---------------
>
> From: "Claude Lemmel" <[EMAIL PROTECTED]>
> Subject: Re: File Names
> Date: Thu, 26 Oct 2000 08:09:03 +0200
> MIME-Version: 1.0
> Content-Type: text/plain;
> charset="iso-8859-1"
> Content-Transfer-Encoding: 7bit
> References: <[EMAIL PROTECTED]>
>
> > From: [EMAIL PROTECTED]
> > Subject: File Names
> >
> > I'm developing a program to be cross platform and I want to access a
> common
> > set of files. I use more than 8 letters in the name and then the Windows
> > extension. I need the extra letters to clarify the files for end users.
> The
> > problem is that when I try to read these files from my Mac, it truncates
> them
> > to 8 letters (as in the 8 + 3 extension scheme). Thus "PROJECTION"
> becomes
> > "PROJEC~1". The program then does not recognize the file because the name
> is
> > changed. Is there a way to tell the Mac to not do this?
> >
> > Philip Chumbley
>
> I guess you developp on Windows. If you burn a cdrom from Windows, Mac is
> too stupid to read the long filenames of a iso9660 CD.
> You have to transfert all the files on the mac and to burn from the mac
>
> A painfull way, but i dont know an other one :
> - compact all your windows files with some zip utility into a big pc2mac.zip
> file
> - copy the pc2mac.zip zip file on a cdrom
> - copy the cdrom on the mac
> - decompress on the mac (a recent version of alladdin or unstuffit do the
> job) : the long names and the hierachy of the folders are OK
> - burn from the mac an hybrid CDROM (ie mac partition + iso9660) with Toast.
>
> You get a cross platform cd-rom what accept long names on both mac and pc.
>
> Be carefull : do not use high ascii characters in the file names ; both mac
> and windows accept that, but the high ascii characters are not the same from
> one platform to the other one.
>
> If you plan to use also a linux version, convert all the filenames to
> lowercase in your soft (including filename properties) and on your disk.
>
> Hope it helps.
>
> Claude
>
Archives: http://www.mail-archive.com/[email protected]/
Info: http://www.xworlds.com/metacard/mailinglist.htm
Please send bug reports to <[EMAIL PROTECTED]>, not this list.
