[progress Communities] [progress Openedge Abl] Forum Post: Re: Utf-8 Issue (thin Space)

[Darren Parr]

I'm using -useOsLocale. So the webclient has a valid multi-byte value for the numeric seperator. On the appserver we already store seperators against each operator. We are checking that the clients session matches the servers. The reason for doing this is the client has legacy activex controls and .net components which don't look at the progress numeric seperator but look at the locale. So it makes sense to ensure the client is using the same settings. The appserver uses the operator to set the environment. With an interactive client we want the settings to be the same and so I'm passing the numeric seperator which is set and trying to set the numeric-seperator on the server too. Then I compare the two seperators to make sure they are the same. So on finding a space as the value we want on the server, I'm trying to set the numeric seperator to chr(14844041). I then compare the value from the one which came in. The only issue is that progress does not allow a multi byte seperator to be used as numeric seperator when using the set-numeric-format method. Any ideas? Darren

Continue reading...