Portable file names

[Sannyasin Sivakatirswami]

I don't know if this is useful to share, but if only to perhaps confirm 
the wisdom of 25 characters and .ext as a good constraint despite what 
the OS might tell you:

I am having some real anamolies  in this area with OSX-Jaquar... which 
I thought supported long files names..

I have files previously saved under OS 9  where elipses were introduced 
to truncate long subject lines in emails of audio transcripts:

03-09-02 The Ne…ligion - Part 2

now the finder will show elipses under a narrow view but the full file 
name can be copied out:

8-25-02_2002_Kauai_Innersearch_Day_3,_Part_3_.txt

Where these were file names generated with a "Save as" from Apple's 
mail.app. defaulting to filename=subject line of msg.

*but* ! any attempt to change a character in the long file name 
manually in the finder returns an error message that it is too long... 
even though Jaquar accepted the long file name in a system level 
openfile process

to make matters even more interesting, but less fun.. libURL  replaces 
the elipses previously introduced in long file names in OS9 with some 
high ASCII garbage in an FTP download over the LAN:

Long_filenameFront…LongNameEnd.txt

Question: what is the length limitation on a system such as a Solaris 
Unix server?









On Wednesday, October 16, 2002, at 05:44  AM, Ken Ray wrote:

>>>> 1. I recall Ken Ray telling me that a file extension is required on
>>>>  some platforms.
>>>
>>> Only if you want to map a Rev stack file to an application as a
> "document"
>>> (for Windows). Technically it doesn't need to have one for other 
>>> uses (so
>>> for example if you have a Rev stack that is always next to your
> standalone
>>> and read by that standalone but never 2x-clicked).
>>
>> This is what you wrote me on 7 July:
>>
>>>> 2) Several of the files do not have an extension (READ ME FIRST, for
>> example); you need to make sure all files have extensions (even 
>> though on
>> Mac OS 9 they're not necessary, they are on OS X and Windows).
>
> Yes, and that was because the READ ME FIRST file was one that 
> effectively
> "asked" the user to double-click it. If you have Rev files that don't 
> need
> to be double-clicked (i.e. they're opened from within another program
> automatically), you can forego the extension. Personally, I feel that 
> *all
> files* on *all platforms* should have an extension for multiplatform
> compatibility, but that's just my opinion. ;-)
>
>
> Ken Ray
> Sons of Thunder Software
> Email: kray at sonsothunder.com
> Web Site: http://www.sonsothunder.com/
>
> _______________________________________________
> use-revolution mailing list
> use-revolution at lists.runrev.com
> http://lists.runrev.com/mailman/listinfo/use-revolution
>
>
Thanks!
Himalayan Academy Publications
Sannyasin Sivakatirswami
Editor's Assistant/Production Manager
www.HinduismToday.com, www.HimalayanAcademy.com,
www.Gurudeva.org, www.hindu.org