Discussion Forums

Re: MessageEncoding with UTF-8
Dean Kauffman / TradeWeb LLC
7 Sep 2006 11:42AM ET

Michael,

Encoded fields allow you to to shield data from FIX field parsers - the paired length field tells the parser how many bytes to consume from the encoded field without parsing. For example if the encoded data looks like FIX tags - 10=A^12=B^13=C^ (where ^ is hex 01) you can setup the fields as below and the receiving engine should handle the data without tripping over the reserved characters.

354=15^
355=10=A^12=B^13=C^^
    ....|....|....|

You might take a look at our document posted elsewhere on the FIX website that describes how to embed an FpML document in the EncodedSecurityDescription field:

http://fixprotocol.org/documents/1349/FIXFpML%20Proposal.doc

Dean

> I have tried to find out how to encode the fields in the FIX protocol
> that are to be encoded, for example EncodedText (tag 355). How should
> the data be serialized in this field when using UTF-8 for example? The
> FIX documentation does not describe this clearly. Does anybody have a
> FIX message example of such a message?


MessageEncoding with UTF-8
Michael Cavén / Front Capital Systems   7 Sep 2006 11:11AM ET
Re: MessageEncoding with UTF-8
Dean Kauffman / TradeWeb LLC   7 Sep 2006 11:42AM ET
Re: MessageEncoding with UTF-8
Michael Cavén / Sungard Front Arena   11 Sep 2006 9:24AM ET
Re: MessageEncoding with UTF-8
Dean Kauffman / TradeWeb LLC   11 Sep 2006 9:43AM ET
Re: MessageEncoding with UTF-8
Michael Cavén / Sungard Front Arena   11 Sep 2006 9:54AM ET