On 23 Dec 2019, Alan Ianson said the following...
 
 AI>  DR> Is there a way to have HTick import the description onto separate
 AI>  DR> lines of 79/80 char max?
 AI> 
 AI> I don't think so, but it will use LDesc lines if present. There can be
 AI> more than 1 LDesc line. They are usually formatted like a file_id.diz.
 AI> You can also tell htick to get the description from a file_id.diz if
 AI> there is one.

I had thought of that as well, and there are two issues with it. First, the
archives contain archives which contain the file_id.diz description. It's the
GFD file echos where I noticed this.

Secondly, HTick will only pull the file_id.diz if the LDesc is not defined.
With these tic files containing the Desc verb, I don't think it would even
attempt to grab the file_id.diz from them. 

 AI> In the case of incoming tic files you are stuck with what you get, a
 AI> single Desc line or multiple LDesc lines. In most cases it's easiest to
 AI> get the description from the file_id.diz if there is one. Sometimes even
 AI> the file_id.diz isn't very well formatted.

That's true. Unfortunately, Mystic is only reading a short part of the desc
line in the files.bbs...

I'm thinking a script that will take the Desc line, and create multiple LDesc
lines within the tic file before it gets processed would be the best way to
work around this...


---

Black Panther(RCS)
Castle Rock BBS

--- Mystic BBS v1.12 A43 2019/03/02 (Linux/64)