Subj : Filename conversion (was children ansi pack)
To   : AKAcastor
From : Andrew Leary
Date : Sun Mar 03 2024 12:11 am

Hello AKAcastor!

02 Mar 24 15:43, you wrote to Deon:

 AK> As a sysop running DOS software, a force 8.3 setting does sound useful
 AK> to me.

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

 AK> A suggestion - if there is FILE_ID.DIZ/FILE_ID.ANS inside
 AK> really_long_filename.zip then that could be placed inside somename.zip
 AK> also, to make it easy for tools to still find the description files.

I suggested the same thing.

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

 AK> You're right about the details being tricky.  I don't have any great
 AK> insight here, but I do think you are doing well considering potential
 AK> drawbacks.

We try to think about these things sometimes... lol

 AK> If the 'replaces' keyword is used in the TIC file, would it be better
 AK> to modify that to an 8.3 filename as well, or would it be left as-is?

However the file was distributed originally is what the Replaces keyword needs 
to list.  If the original archive and file_id.diz are stored inside an 8.3 
archive before hatching, then this is easy.  If they are renamed or repacked 
enroute, it will likely require manual intervention to handle replacing the 
older file.

Andrew

--- GoldED+/LNX 1.1.5-b20240209
 * Origin: Phoenix BBS * phoenix.bnbbbs.net (21:4/105)

.