TIP: Click on subject to list as thread! ANSI
echo: public_domain
to: Alexander Watson Law
from: andrew clarke
date: 1996-03-20 00:59:52
subject: file encoding via fidonet type 2 ma

17 Mar 96 00:16, Alexander Watson Law wrote to Bob Lawrence:

 > Hmmm... Does anyone know which of the normal ASCII characters have
 > problems? I know things like UU use a restricted subset to satisfy
 > *everyone* but I would expect Fido to be more lenient, allowing pretty
 > much everything between 0x20 and 0x7E which gives a better range than
 > just (say) 64 characters...

Technically the only characters that shouldn't be transmitted in an
"encoded file" via FidoNet mail using FTS-1 mail packets are 0x00
and 0x01, as they are reserved for "special" purposes (ie. 0x00 =
null terminator; 0x01 = control line identifier).  0x8D is a problem
though, as there is a chance it will be ignored by some mail processors
(depending on the authors' interpretation of FTS-1).

0x01 could be used provided it does not begin a line of the message text,
but this would probably cause confusion if a FidoNet file encoding standard
was to be specified.  No great loss.

How does 253 characters compare to your 64 ?  ;-)

Regards
Andrew

--- Msgedsq/2 3.30
* Origin: This one HAS to be original X (3:635/727.4{at}fidonet)
SEEN-BY: 50/99 78/0 635/309 503 544 727 640/230 711/401 410 413 430 808 809
SEEN-BY: 711/934 712/610 713/888 800/1 7877/2809
@PATH: 635/727 544 50/99 711/808 809 934

SOURCE: echomail via fidonet.ozzmosis.com

Email questions or comments to sysop@ipingthereforeiam.com
All parts of this website painstakingly hand-crafted in the U.S.A.!
IPTIA BBS/MUD/Terminal/Game Server List, © 2025 IPTIA Consulting™.