Subj : Re: ANSI Art Packs
To   : All
From : deon
Date : Tue Apr 02 2024 08:12 am

  Re: Re: ANSI Art Packs
  By: AKAcastor to Apam on Mon Apr 01 2024 11:36 am

Howdy,

 > Since we're discussing ideas - does anyone have suggestions for how to
 > automate creation of short filenames from long names?  I'm sure there's no
 > perfect solution, but maybe someone has something better than 'just take the
 > first 8 letters of the filename'.

I've suggested this a couple of weeks ago now. I can implement a toggle in clrghouz, so that when long filenames come in, I can send them to downstream systems with an 8.3 name.

What I can do is, generate a unique 8.3 name, where the 8 will be a filearea_id+file_id value in hex (to clrghouz), and the .3 will the extension chopped to 3 chars. eg: 0A0001F3.ZIP, and while the file area and description are left intact, outside of your BBS you'll have no idea what the file is.

As apam suggested, the original name in the TIC file could be left intact as well.

Determining the 8 from the original filename by chopping it would be (IMHO) dangerous since the probability that it clashes with another name would be high (the mystic updates comes to mind, where there 8 chars is the same for windows, linux, pi from memory).

I also have a function that converts a date into 4 chars with 4 year precision, so I could take the first 4 chars, and make up the last 4 with that function - it might have some resemblence of a name, and be unique for at least 4 years. eg blndr2023d.zip might become blnd3F12.zip.

I might play around with the later and see how it goes...


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

.