Subj : Filename conversion (was children ansi pack)
To   : AKAcastor
From : deon
Date : Sun Mar 03 2024 05:24 pm

  Re: Filename conversion (was children ansi pack)
  By: AKAcastor to Deon on Sat Mar 02 2024 03:43 pm

 > As a sysop running DOS software, a force 8.3 setting does sound useful 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".
 >
 > A suggestion - if there is FILE_ID.DIZ/FILE_ID.ANS inside
 > really_long_filename.zip then that could be placed inside somename.zip also,
 > to make it easy for tools to still find the description files.

Actually, I wasnt suggesting puting "realy_long_filename.zipped" into another (8.3) zip file - I was suggesting giving it to the downstream system as "somename.zip" - thus if there was a FILE_ID* in it, it would be accessible as is.

(What does DOS do when you unzip "realy_long_filename.extension" inside a zip file - I dont recall - it truncates it right...?)

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

I could do that - as clrghouz dynamically creates the TIC file when sending files downstream. However, I have doubts that that is a good idea as well.. (It would be a shame if the replaces and thus the clobbering of the original file name resolved to a file that you didnt want to have deleted.)

Hmm....


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

.