Text 6046, 64 rader
Skriven 2013-07-07 21:38:42 av Janis Kracht (1:261/38)
   Kommentar till text 6045 av Michael Dukelsky (2:5020/1042)
Ärende: LFN in File Distribution
================================
Hi Michael,

>>> It is an interesting proposal, but it suggests changing TIC
>>> processors, which is unfortunately not realistic. So maybe all we
>>> can do is to ask the person wh hatches files using long filenames to
>>> also include a field with a short filename in TIC. It can be
>>> SHORTNAME, for example. Then every node that converts a long
>>> filename to a short one would at any rate use the same short name.

>>> Of course the peson who hatches files must agree to include such a
>>> field in a TIC.

>> Do you know a way to do this across all OS's and hatching programs? I
>> don't.

> Neither do I. Evidently I mean it should be done by a separate script.

Yes, it would have to be a script.. easy in linux and most os's since they have
sed... I'm not sure I like the idea of sysops having to write such a script
though to process files.

>>> Hopefully we do not encounter a widely used TIC processor that
>>> crashes on an unknown keyword instead of ignoring it.

>> "Hopefully"??

>Exactly. Or do you think there is anything different with the FULLNAME keyword

If fullname was implemented in half the tick processors, so many would not have
failed on the week of the 29th, I think.  There were a number of them over
different operating systems and programs as well that failed. :(

>> Rather than take a chance on software blowing up, why
>> not just say that everyone should use standard 8X3 filenames, and use
>> the description in the tic file as it was meant to be used to describe
>> details of the file?

> I agree with you. That would be better although using 8.3 names is very
> inconvenient. Do you know a way to oblige a Fidonet sysop of doing anything?

It can be made easy once a pattern is established.. just like we used to use in
text files to show capabilities when the margins were too small for full words.

I believe you were forwarded my message, which contained Gert's suggestion for
naming conventions for example in AFTNBINKD:

Gert Andersen wrote:
bc = binary only file
bs = a source + compiled files
bt = all files for bind in the zip.

and so on.

Anyway, I know what you mean about obliging sysops to do anything <vbg>. All we
can hope is that future releases in AFTNBINKD use this type notation in the
filename :)

Thank you for your thoughts, Michael.

Take care,
Janis

--- BBBS/Li6 v4.10 Dada-1
 * Origin: Prism bbs (1:261/38)