Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Table of Contents

...

FIX Antenna products fully support UTF-8 encoding.UTF-8 supports , i.e all the CJK (Chinese-Japanese-Korean) symbols but has no other meanings for 0x01 instead of SOH.

FIX-Protocol and

...

multibyte encoding.

The support of non-ASCII characters was introduced in FIX-protocol since FIX 4.2 (https://www.fixtrading.org/standards/fix-4-2/).

...

  1. Special Encoded fields are added for work with Non-ASCII symbols. 
  2. The field MessageEncoding(347) should be specified with the encoding which is used in the other  Encoded* fields of the message.
  3. The length fields (Encoded*Len) should contain the count of BYTES (Important: not count of symbols) contained in corresponding Encoded* field.


However, one can use UTF-8 8 can be used in any text field. In order to keep FIX-protocol compatibility the counterparty must also expect UTF-8 encoding in the fields.

...

Field nameField numberField value
MessageEncoding347Shift_JISUTF-8
EncodedTextLen35415
EncodedText355こんにちは

Message example: encoding testing.txt

Info
DoesnFIX Client Simulator doesn't work in FIX Client Simulatorfully support multibyte encoded characters in Send Message textbox.

Work with User-defined Encoded Fields

...

Field nameField numberField value
MessageEncoding347Shift_JISUTF-8
EncodedUserFieldLen5035415
EncodedUserField50355こんにちは

...

Dictionary configuration example:

Code Block
languagexml
titleadditional.xml
        <fielddic>
            <!-- ... -->
			<fielddef tag="50354"  name="EncodedUserFieldLen" type="int"/>
			<fielddef tag="50355"  name="EncodedUserField" type="String"/>
            <!-- ... -->
        </fielddic> 


		<msgdic>
            <!-- ... -->
            <msgdef msgtype="B" name="NEWS">
               <!-- ... -->
               <field tag="50354"  name="EncodedUserFieldLen" condreq="existtags(T$50355)"/>
               <field tag="50355"  name="EncodedUserField" condreq="existtags(T$50354)"/>
            </msgdef>
            <!-- ... -->
        </msgdic>

Message example: encoding - testing - custom.txt

FIX Protocol and UTF-16/UTF-32 Encoding

...