EL230 Errors found in MOD submission, see messages:

EL219 Error Unknown keyword found: SUBJ
EL224 Error missing SUBJect.



--- MBSE BBS v1.0.7.13 (GNU/Linux-x86_64)
* Origin: The Elist Maintainer (2:250/1)

Hello Paul!

Wednesday April 22 2020 01:30, I wrote to you:

EL230 Errors found in MOD submission, see messages:

EL219 Error Unknown keyword found: SUBJ
EL224 Error missing SUBJect.

This file has the first 3 characters that are NOT normal text.

They are in fact (in hex) : ef bb bf

The first 16 chars are (in Hex and display form) :

00000000 ef bb bf 53 55 42 4a 20 4d 4f 44 2d 55 50 44 0d |...SUBJ MOD-UPD.|

The dots give the clue but the hex chars ef bb bf are not A- Z, a - z, 0 - 9 and space etc.

Only use a text editor and not a word processor type editor.

Vincent

--- Mageia Linux v7.1 X64/Mbse v1.0.7.13/GoldED+/LNX 1.1.5-b20180707
* Origin: The Elist Maintainer (2:250/1)

Hi Vincent,

On 2020-04-22 16:29:49, you wrote to Paul Hayton:

This file has the first 3 characters that are NOT normal text.

They are in fact (in hex) : ef bb bf

The first 16 chars are (in Hex and display form) :

00000000 ef bb bf 53 55 42 4a 20 4d 4f 44 2d 55 50 44 0d |...SUBJ MOD-UPD.|

The dots give the clue but the hex chars ef bb bf are not A- Z, a - z, 0 - 9 and space etc.

Only use a text editor and not a word processor type editor.

It's this: https://en.wikipedia.org/wiki/Byte_order_mark#UTF-8

Since your on linux it should be easy to filter them out in your scripts:

https://unix.stackexchange.com/questions/381230/how-can-i-remove-the-bom-from-a-utf-8-file


Bye, Wilfred.

--- FMail-lnx64 2.1.0.18-B20170815
* Origin: FMail development HQ (2:280/464)

Hello Wilfred!

Wednesday April 22 2020 18:40, you wrote to me:

Hi Vincent,

On 2020-04-22 16:29:49, you wrote to Paul Hayton:

This file has the first 3 characters that are NOT normal text.

They are in fact (in hex) : ef bb bf

The first 16 chars are (in Hex and display form) :

00000000 ef bb bf 53 55 42 4a 20 4d 4f 44 2d 55 50 44 0d
|...SUBJ MOD-UPD.|

The dots give the clue but the hex chars ef bb bf are not A- Z, a
- z, 0 - 9 and space etc.

Only use a text editor and not a word processor type editor.

It's this: https://en.wikipedia.org/wiki/Byte_order_mark#UTF-8

Since your on linux it should be easy to filter them out in your
scripts:

https://unix.stackexchange.com/questions/381230/how-can-i-remove-the-b om-from-a-utf-8-file

It is not a script but a program and I cannot examine every character in a submission for valid chars as the range outside a-x, A-Z, 0-9 is too much to screen for. Then there is the issue of what to do , more forwards 1 until a vaild char is presented ?

The correct solution is to use a text editor in Windows, *nix or any other platform..

If I can do it with my systems ( Linux, Win 10, OSX, IBM ) then I have to assume every one else can.

Vincent

--- Mageia Linux v7.1 X64/Mbse v1.0.7.13/GoldED+/LNX 1.1.5-b20180707
* Origin: The Elist Maintainer (2:250/1)

On 22 Apr 2020 at 06:40p, Wilfred van Velzen pondered and said...

It's this: https://en.wikipedia.org/wiki/Byte_order_mark#UTF-8

Thanks, good spotting.

--- Mystic BBS v1.12 A46 2020/04/20 (Windows/32)
* Origin: Agency BBS | Dunedin, New Zealand | agency.bbs.nz (3:770/100)

Hi Paul,

On 2020-04-23 12:19:52, you wrote to me:

It's this: https://en.wikipedia.org/wiki/Byte_order_mark#UTF-8

Thanks, good spotting.

If I remember correctly it happend to a part of the z2 nodelist in the past. So
I've seen it before.

For people sending in messages containing these codes it might be as simple as to configuring a different character encoding in their editor (so not use utf-8).

Bye, Wilfred.

--- FMail-lnx64 2.1.0.18-B20170815
* Origin: FMail development HQ (2:280/464)

EL230 Errors found in MOD submission, see messages:

EL219 Error Unknown keyword found: SUBJ
EL224 Error missing SUBJect.



--- MBSE BBS v1.0.7.13 (GNU/Linux-x86_64)
* Origin: The Elist Maintainer (2:250/1)

Hello Wilfred!

Thursday April 23 2020 09:54, you wrote to Paul Hayton:

Hi Paul,

On 2020-04-23 12:19:52, you wrote to me:

It's this: https://en.wikipedia.org/wiki/Byte_order_mark#UTF-8

Thanks, good spotting.

If I remember correctly it happend to a part of the z2 nodelist in the
past. So I've seen it before.

For people sending in messages containing these codes it might be as
simple as to configuring a different character encoding in their
editor (so not use utf-8).

I have now made a change to program (#040) to detect this data sequence and if found more the data over 3 chars before processing. Well thats the intention testing it shortly with the original CBM UPD file.


Vincent

--- Mageia Linux v7.1 X64/Mbse v1.0.7.13/GoldED+/LNX 1.1.5-b20180707
* Origin: The Elist Maintainer (2:250/1)

EL230 Errors found in MOD submission, see messages:

EL219 Error Unknown keyword found: D
EL224 Error missing SUBJect.



--- MBSE BBS v1.0.7.13 (GNU/Linux-x86_64)
* Origin: The Elist Maintainer (2:250/1)

EL230 Errors found in MOD submission, see messages:

EL224 Error missing SUBJect.



--- MBSE BBS v1.0.7.13 (GNU/Linux-x86_64)
* Origin: The Elist Maintainer (2:250/1)

EL230 Errors found in MOD submission, see messages:

EL219 Error Unknown keyword found: SUBJ
EL224 Error missing SUBJect.



--- MBSE BBS v1.0.7.13 (GNU/Linux-x86_64)
* Origin: The Elist Maintainer (2:250/1)