{{Quickfixn}} Message Error

[(Eddie) John Jackson]

Grant,

                Have you had any time to work on this and what is the state?

Thanks,

Eddie

From: Quickfixn <quickfixn-bounces at lists.quickfixn.com> On Behalf Of Grant Birchmeier
Sent: Tuesday, June 25, 2019 12:03 PM
To: Mailing list for QuickFIX/n <quickfixn at lists.quickfixn.com>
Subject: Re: {{Quickfixn}} Message Error

Eddie, I think I've found the problem.

In the most recent log you sent me (off-list) (file FIXT.1.1-ICAPSIERSL1-ICAP.messages.current.log), the message with seq 34=27 contains the following:
55=BGOSK 28� m

I don't know what that character after "28" is.  It's a foreign character, and I think the QuickFIX/n parser has mangled it upon reading.  FIX is supposed to be an ASCII-based protocol, but unfortunately a lot of counterparties flout that.

However, we had recent discussion about changing QF/n to support ISO/IEC 8859-1, which would probably let this work.  We have a PR open for that, and it looks like I finally have time to tweak and finalize it.  (Plus, this submission allows other character encodings by configuration!)  I don't want to make promises, but I'm hoping to get it in this week.


--
Grant Birchmeier
Connamara Systems, LLC
Made-To-Measure Trading Solutions.
Exactly what you need. No more. No less.
http://connamara.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.quickfixn.com/pipermail/quickfixn-quickfixn.com/attachments/20190702/9aaa0ec5/attachment.html>