TIP: Click on subject to list as thread! ANSI
echo: makenl_ng
to: Kees van Eeten
from: Wilfred van Velzen
date: 2015-02-21 16:47:30
subject: Re: Feature request

Hi,

On 2015-02-21 16:09:08, Kees van Eeten wrote to Wilfred van Velzen:
  about: "Feature request":

 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
 WvV>> them in the middle of the file breaks the standard, so I can't
 WvV>> imagine why that would be usefull, even in the future. But it's up to
 WvV>> the developper. ;)

 KvE> For browsing the nodelist, the position of the BOM when used, should
 KvE> be the first three bytes in the file. That however breaks makenl. The
 KvE> danger of BOM creeping in is mainly at the start of the included
 KvE> files. Another place where de BOM may cause havoc is with manually
 KvE> maintained segments without the headerline. That will probably cause
 KvE> makenl to mark the line with the segment host as in error, unless the
 KvE> BOM is directly followed by cr/lf.

So what you are saying is that BOMs should always be filtered out from
input files before further processing. And there's no need to make this an
option. ;)

Bye, Wilfred.


--- FMail-W32-1.69.1.95-B20140716
* Origin: Native IPv6 connectable node (2:280/464)
SEEN-BY: 154/10 203/0 230/0 240/5832 249/303 261/38 280/464 5003 5555 292/624
SEEN-BY: 292/854 633/267 280 712/620 848 770/1
@PATH: 280/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™.