65675 - selfserv needs to be usable for i18n testing

Status: NEW

(NSS :: Tools, defect, P3)

Description

[Sonja Mirtitsch]

all or most strings are char * or char [], there are plenty of isalpha(),
islower() etc. used

Comment 1

[Wan-Teh Chang]

Assigned the bug to Nelson.

Comment 2

[Nelson Bolyard (seldom reads bugmail)]

I'm not sure this bug is valid.
It's OK for strings to be char * or char[] if they're UTF-8
strings, and NSS generally assumes that strings are UTF-8.

isalpha and islower work with other character sets besides
ascii, provided that the environment variable LOCALE is set
properly.  So, use of isalpha and islower is not automatically
a sign that the code won't work with other character sets.

However code that calls isalpha() with a char value (rather
than an int value) clearly won't work with multi-byte 
character sets.  What's needed is a function that takes
a char * and returns an int containing the value of the next
character (perhaps a multi-byte one) from the UTF-8 string
at that point.

selfserv uses string processing for command line arguments. 
It seems to me that more code than merely selfserv needs to 
be changed if command line arguments will contain UTF-8 
characters.  NSPR's command line options parser may also need
adjustment.  

Comment 3

[Sonja Mirtitsch]

A lot of the languages we need to support have multibyte char sets. Andrea Vine
suggested for the NSS developers to attend her class.

Comment 4

[Nelson Bolyard (seldom reads bugmail)]

This bug is not on the "in" list for NSS 3.4.

Comment 5

[Wan-Teh Chang]

We need to have an internationalization test plan.
I'll look into this.

Comment 6

[Sonja Mirtitsch]

My 3.4 testplan i18n will stay what it was for 3.3 - make sure the i18N
extensions are installed properly on kentuckyderby - I do not object to moving
this to future, or 3.5

Comment 7

[Wan-Teh Chang]

Set target milestone 4.0.

Comment 8

[Wan-Teh Chang]

Changed the QA contact to Bishakha.