86411 - Unicode 3.1 UTF-8 Corrigendum

Status: RESOLVED DUPLICATE of bug 74198

(Core :: Internationalization, defect)

Description

[Neal Probert]

In nsString2.cpp (anywhere else?) the UTF-8 conversion routines need to updated
for Unicode 3.1 where the UTF-8 Corrigendum states that non-shortest forms and
5-6 byte UTF-8 sequences are also disallowed. This should be enforced for
security reasons as well.

Comment 1

[nhottanscp]

Are you talking about NS_ConvertUCS2toUTF8? 

http://lxr.mozilla.org/seamonkey/source/string/obsolete/nsString.cpp#1375

Comment 2

[Frank Tang]

mozilla is design for unicode 3.0 not 3.1 yet. 
mark as future. 

Comment 3

[Andreas Becker]

Switching QA contact to teruko for now.

Comment 4

[Scott Collins]

giving up ancient string bugs to the new string owner.  jag, you'll want to sort
through these and see which ones still apply and go with or against the
direction in which you intend strings evolve

Comment 5

[bobj]

Frank, Isn't this fixed?

Comment 6

[Alexey Chernyak]

Well guess we'll have to sit down and check if this is really fixed.
bug 182751 has plenty of UTF-8 testcases which I think should cover everything.

Unicode 3.1 (and 3.1.1)? http://www.unicode.org/reports/tr27/#conformance
Unicode 3.2? http://www.unicode.org/reports/tr28/#conformance
Unicode 4.0? http://www.unicode.org/versions/Unicode4.0.0/ch03.pdf#G7404

Other UTFs conformance?
UTF-16BE?
UTF-16LE?
UTF-32BE?
UTF-32LE?

Comment 7

[Simon Montagu :smontagu]

*** This bug has been marked as a duplicate of 74198 ***