|
International
< Previous Next >
Re: Windows 1256 character coding for arabic
Dean Kauffman / TradeWeb LLC
11 Sep 2006 11:19AM ETBernt,
MessageEncoding(347) is defined in the FIX specs as "String" with a list of valid values - not including Windows-1256. However the value in FIX is not reduced to int or char and the FIXML schema omits any constraint suggesting that the list of valid values is meant to be open-ended. It would be desirable to specify 347=Windows-1256 if that is the encoding you are going to use. But discuss this with your counterparties and get around any objections by sending 347=UTF-8 with Windows-1256 encoding in the field anyway.
I've found that the 4.2 engine vendors will usually extend constrained values for a fee; the 4.4 vendors have done a better job of putting extensions in their clients' hands.
Dean
> Hi,
>
> We would like to use Windows-1256 for character coding of arabic
> characters in the SecurityDefinition message in FIX 4.2.
>
> Windows-1256 is a code page used to write Arabic (and possibly some
> other languages that use Arabic script) under Microsoft Windows. It is a
> one byte representation of arabic where the lower half (0-127) is plain
> ASCII and the upper half is arabic.
>
> Can we set 347="Windows-1256" and use tags 350 (EncodedSecurityDescLen)
> and 351 (EncodedSecurityDesc)?
>
> Windows-1256 is not one of the supported values of tag 347 so that's why
> I am asking.
>
> Bernt
Re: Windows 1256 character coding for arabic
Dean Kauffman / TradeWeb LLC 11 Sep 2006 11:19AM ET
|
