| TIP: Click on subject to list as thread! | ANSI |
| echo: | |
|---|---|
| to: | |
| from: | |
| date: | |
| subject: | testing custom origin tex |
Hello mark! ** 16.04.19 - 22:15, mark lewis wrote to August Abolins: AA>> @MSGID: 2:221/1.58@fidonet d7782048 AA>> @PID: OpenXP/5.0.38 (Win32) AA>> @CHRS: ASCII 1 AA>> This message should have a customized origin text specific just for this AA>> echo. AA>> --- AA>> (2:221/1.58) Thank you for that. As you could see, I was just exploring oxp's custom origin settings. Apparently, I can create a different one for each particular area or echo. In the original message I was testing the max char limit according to the program. Apparently oxp is very smart and precalculates the limit based on the total chars with the nodenumber at the end so as to not exceed the total 79 char limit for that line as per the ftsc-0074 and therefore "fit" perfectly. ../|ug ---AA>> * Origin: [++++++++1+++++++++2+++++++++3+++++++++4++++++++5++++] * Origin: [++++++++1+++++++++2+++++++++3+++++++++4++++++++5++++] (2:221/1.58) |
|
| SOURCE: echomail via QWK@docsplace.org | |
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™.