Subj : Issues with running makenl for a region
To : Vincent Coen
From : Kees van Eeten
Date : Tue Mar 04 2025 09:23 pm
Hello Vincent!
04 Mar 25 17:23, you wrote to All:
VC> I use makenl 3.5.1 under Linux and the o/p file region25.nnn has a binary
VC> value
VC> at the end of file that Ward (2:0) cannot handle in his Dos environment.
????
VC> Does any one have a fix for it as I have tried using unix2dos and
VC> cannot
VC> find setting to omit it.
VC> Out of interest it is 1a hex that is just after hex 0d oa i.e.,
VC> 0000930 7265 2e73 656e 2c74 4249 0d4e 1a0a
That is correct. I find the same in your REGION25.066, that I received on
March 3 at 19:18 CET
VC> Above from hexdump
VC> Short of hacking the makenl code (assuming I find the code).
As someone has alredy mentioned the a Dos files hould end with "CTRL-Z null"
as the last two characters.
There were problems with your March 2 file. I received 4 copies.
The first only contained net 263 with errors complaining about -Unpublished-
being an invalid phonenumber.
As you have probably found already that that is solved by adding
allowunpub 1
to your control file.
The file I received later that evening was correct, but hat Net 263 missing.
If one edits a net or region file on a contemporary system it is wise to
add:
removebom 1
Some systems add two specific bytes as the first two charaters of a file,
assuming that it will he encoded in UTF.
When only ascii characters are used the file is no different from an
ASCII file.
The two files are called "Byte Order Mark" and are used to signal the
Endian order of the bytes in the file.
the "rememovebom 1" makes shure that makenl removes the marker.
Kees
--- GoldED+/LNX 1.1.5--b20180707
* Origin: As for me, all I know is that, I know nothing. (2:280/5003.4)
