| TIP: Click on subject to list as thread! | ANSI |
| echo: | |
|---|---|
| to: | |
| from: | |
| date: | |
| subject: | file encoding via fidonet type 2 ma |
Answering msg from andrew clarke to Alexander Watson Law, on Wednesday March 20 1996 at 00:59 >> 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... ac> Technically the only characters that shouldn't be transmitted in an ac> "encoded file" via FidoNet mail using FTS-1 mail packets are 0x00 and ac> 0x01, as they are reserved for "special" purposes (ie. 0x00 = null ac> terminator; 0x01 = control line identifier). 0x8D is a problem ac> though, as there is a chance it will be ignored by some mail ac> processors (depending on the authors' interpretation of FTS-1). 0x0A may also be eaten by some mail processors. Reformatting of the "text" body at creation and viewing of message is also an issue. Cheers. ---* Origin: Jelly-Bean software development, Melbourne AUST. (3:635/727.1) 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™.