On Sun, 16 Feb 2014, Nicholas Boel wrote to mark lewis:

 BM>> Just out of curiosity, what are you using to hatch? I'm being
 BM>> completely impartial here...

 ml> FWIW: it is not the hatching that's the problem... it is the
 ml> descriptions being cut off, rewrapped, or just being much too long...
 ml> the hatch LDESC is still limited to only a few lines and definitely no
 ml> way to enter multiple lines with fancy graphics headers and the
 ml> like...

 NB> So let's make sure it goes on record that I've never had a LDESC
 NB> cropped, cut  off, rewrapped, or just being much too long the
 NB> entire time I've used it. 

where? in what you send out that others have to process or in what you
receive and process on your system?

how many LDESC lines do you send in your TICs? what is their max length?

how many LDESC lines do you receive in your TICs? what is their max length?

do you throw away the TIC DESC and LDESC lines and simply import a
FILE_ID.DIZ if it exists? what happens if there is no FILE_ID.DIZ in the
archive? does your system fall back to DESC and/or DESC+LDESC?

 NB> With that being said, I do blame software's limitations. If there
 NB> is one  application that can do it perfectly, then the others just
 NB> weren't made to do  the same.

agreed but i also look at the config settings in the available packages...
in allfix i can choose several different ways of getting the description...
currently i use FILE_ID/LDESC... i can filter ANSI and >128
characters... i can choose how many lines from LDESC i can use... but none
of this affects the way the descriptions are displayed on the BBS or on a
web page... that's controlled within the BBS to a certain extent... my web
page generator takes what is in the files database and outputs it exactly
as it is in the database... any conversion seen after that is due to the
browser's rendering of the data...

)\/(ark

One of the great tragedies of life is the murder of a beautiful theory by a
gang of brutal facts. --Benjamin Franklin

--- FMail/Win32 1.60