Aissa SLIMANI | 2 Feb 2006 10:52

Re: Problem unpacking field 2

Thank you so much mark,

I think I have additional informations, The problem for imparsing 
field 2 is due to the fact that the length I am receiving is not 
correct , this is i think because I am using two different Unicode 
caracters set in server and client.
I think because I am installing windows arabic language on the 
server. So when my message is more than 128 characters , the send 
length and receive length doesnt view the caraters the same maneer(I 
think one of them is using 7bit and the second is using 8bit)

I still trying solving the problem.

Many thanks again

Aissa

--- In jpos-dev@..., Mark Salter <marksalter <at> ...> wrote:
>
> Aissa SLIMANI wrote:
> > yes it s the same as in the request , and my card number in the 
> > example is 13 but it s supposed to be LLNUM till 19.
> I asked in case the ascii c'13' was a character hex value 
indicating a
> length of 19 numeric characters.
> Certainly this would cause a problem as the length went over c'09' 
and
> moved into c'0A' - x'3041'.
> 
> It seems strange that you can build this field 2 in jPos, but not 
(Continue reading)

Mark Salter | 2 Feb 2006 22:41

Re: Re: Problem unpacking field 2

Aissa SLIMANI wrote:
> I think because I am installing windows arabic language on the 
> server. So when my message is more than 128 characters , the send 
> length and receive length doesnt view the caraters the same maneer(I 
> think one of them is using 7bit and the second is using 8bit)
At the network level (the bytes making up the message) I don't feel the
language or code page/character set makes any difference.
Perhaps I am wrong - someone will let us know.
Once the message has been parsed and printed or displayed, then the
available character set(s) comes into play.
> 
> I still trying solving the problem.
Can you show us a full dump of the message going to the server and the
response that comes back?
I hope the issue is something simple.

--

-- 
Mark

 

Gmane