Subj : Filename conversion (was children ansi pack)
To   : All
From : deon
Date : Sun Mar 03 2024 09:56 am

  Re: children ansi pack...
  By: Andrew Leary to Avon on Fri Mar 01 2024 12:45 am

Howdy,

 >  Av> OK, just know I hatch them as they are named, so importing some may
 >  Av> require more manual intervention on your part should you wish to
 >  Av> include them.
 >
 > My recommendation is that you store the entire archive inside a .ZIP file
 > with an 8.3 DOS compatible filename.  This will allow the file to be
 > distributed without manual intervention, and the destination nodes can unzip
 > it to recover the original archive.

One of the things I've thought about implementing for clrghouz would be a "force 8.3" like setting - so that long file names are sent downstream in 8.3 format (to those nodes that select it).

IE: While clrghouz might receive "realy_long_filename.zipped" and store it that way internally, it could send it to you as "somename.zip".

The devel is in the detail - sometimes filenames are descriptive so arbitrarly choping of anything before a dot to 8 chars and anything after a dot to 3 chars could loose the name.

And by doing above, its likely that you could clobber (or the downstream node think it has) the file already - especially if two files clobber to the same 8.3 name. (I used to have a similiar problem with MBSE a couple of years ago - where the received name is changed by the receiver and out of sync with the TIC).

I could rename it to a unique name to clrghouz (a mash of filearea id and file id) - but when folks talk about (for example) the mystic files, you wouldnt know what was what if you were looking through your file listing (especially outside of the BBS).

Any ideas on smart ways of handling this?


....лоеп
--- SBBSecho 3.20-Linux
 * Origin: I'm playing with ANSI+videotex - wanna play too? (21:2/116)

.