Re: Possible fixes for an NLS problem?

Hi Andrew,

I have not run into this one (possibly because I dont have a need for 
anything other than normal US ASCII ). However, if you have a fix, I 
will gladly take it. Please apply your fix to the source code and run 
the TCK before sending it to me. Please send me a diff against cvs HEAD.

Alternatively ( preferred), please join the project on java.net and post 
an issue there with the diff against CVS attached as a proposed 
resolution to the issue so others can know you ran into this issue and 
fixed it


Thanks

Ranga

Andrew Waterman wrote:

> Hi,
>
> A colleague of mine is running into some issues with nist-sip with non 
> ascii characters.  We are working with sipUnit, which uses nist-sip as 
> its sipstack. She wrote:
>
>> I found there is a issue in nist-sip-1.2.jar ( a thirdparty package). 
>> In class _gov.nist.javax.sip.parser.PipelinedMsgParser_, its readline 
>> method may cause NLS issue. This method will read bytes[] from 
>> response inputstream, but as it casts a byte to char directly, it may 
>> cause garbage because message headers are encoded in UTF-8 and can 
>> contain non ASCII characters.
>
> Is this a known issue that you guys may have seen before?  I believe 
> we can propose a fix, but I'm not sure where we should send that into 
> either. :-)  Any suggestions would be really helpful. :-)
>
> best wishes,
>
> Andrew
>
>
>------------------------------------------------------------------------
>
>_______________________________________________
>nist-sip mailing list
>[email protected]
>http://www-x.antd.nist.gov/mailman/listinfo/nist-sip
>  
>


-- 
M. Ranganathan 

Advanced Networking Technologies Division,
National Institute of Standards and Technology (NIST),
100 Bureau Drive, Stop 8920, Gaithersburg, MD 20899. 
tel:301 975 3664 , fax:301 590 0932 http://w3.antd.nist.gov/
Advanced Networking Technologies For the People!