| TIP: Click on subject to list as thread! | ANSI |
| echo: | |
|---|---|
| to: | |
| from: | |
| date: | |
| subject: | Feature request |
Hello Wilfred! 21 Feb 15 15:54, you wrote to Michiel van der Vlist: WvV> Maybe you want to have a BOM as the first few bytes of the produced WvV> nodelist by makenl (or not), so that could be an option. But keeping them WvV> in the middle of the file breaks the standard, so I can't imagine why WvV> that would be usefull, even in the future. But it's up to the developper. WvV> ;) For browsing the nodelist, the position of the BOM when used, should be the first three bytes in the file. That however breaks makenl. The danger of BOM creeping in is mainly at the start of the included files. Another place where de BOM may cause havoc is with manually maintained segments without the headerline. That will probably cause makenl to mark the line with the segment host as in error, unless the BOM is directly followed by cr/lf. Kees --- GoldED+/LNX 1.1.5* Origin: As for me, all I know is that, I know nothing. (2:280/5003.4) SEEN-BY: 154/10 203/0 230/0 240/1120 5832 249/303 261/38 280/464 5003 5006 SEEN-BY: 280/5555 292/624 854 633/267 280 712/620 848 770/1 @PATH: 280/5003 464 712/848 633/267 |
|
| 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™.