...
Byte Type | Range |
---|---|
single-byte | |
lead-byte |
|
trailing-byte | |
The trailing byte ranges overlap the range of both the single-byte and lead-byte characters. When a multibyte character is separated across a buffer boundary, it can be interpreted differently than if it were not separated across the buffer boundary; this difference arises because of the ambiguity of its composing bytes \ [[Phillips 2005|AA. References#Phillips 05]\]. Wiki Markup
Supplementary Characters
According to the Java API \[ [API 2006|AA. References#API 06]\] class {{ Wiki Markup Character
}} documentation (Unicode Character Representations):
The
char
data type (and consequently the value that aCharacter
object encapsulates) are based on the original Unicode specification, which defined characters as fixed-width 16-bit entities. The Unicode standard has since been changed to allow for characters whose representation requires more than 16 bits. The range of legal code points is now \u0000 to \u10FFFF, known as Unicode scalar value.The Java 2 platform uses the UTF-16 representation in
char
arrays and in theString
andStringBuffer
classes. In this representation, supplementary characters are represented as a pair ofchar
values, the first from the high-surrogates range, (\uD800-\uDBFF), the second from the low-surrogates range (\uDC00-\uDFFF).An
int
value represents all Unicode code points, including supplementary code points. The lower (least significant) 21 bits ofint
are used to represent Unicode code points, and the upper (most significant) 11 bits must be zero. Unless otherwise specified, the behavior with respect to supplementary characters and surrogate char values is as follows:
- The methods that only accept a
char
value cannot support supplementary characters. They treatchar
values from the surrogate ranges as undefined characters. For example,Character.isLetter('\uD840')
returnsfalse
, even though this specific value if followed by any low-surrogate value in a string would represent a letter.- The methods that accept an
int
value support all Unicode characters, including supplementary characters. For example,Character.isLetter(0x2F81A)
returnstrue
because the code point value represents a letter (a CJK ideograph).
...
Noncompliant Code Example (Substring)
This noncompliant code example attempts to trim leading letters from the {{ Wiki Markup string
}}. It fails to accomplish this task because {{Character.isLetter()
}} lacks support for supplementary and combining characters \ [[Hornig 2007|AA. References#Hornig 07]\].
Code Block | ||
---|---|---|
| ||
// Fails for supplementary or combining characters public static String trim_bad1(String string) { char ch; int i; for (i = 0; i < string.length(); i += 1) { ch = string.charAt(i); if (!Character.isLetter(ch)) { break; } } return string.substring(i); } |
Noncompliant Code Example (Substring)
This noncompliant code example attempts to correct the problem by using the {{ Wiki Markup String.codePointAt()
}} method, which accepts an {{int
}} argument. This works for supplementary characters but fails for combining characters \[ [Hornig 2007|AA. References#Hornig 07]\].
Code Block | ||
---|---|---|
| ||
// Fails for combining characters public static String trim_bad2(String string) { int ch; int i; for (i = 0; i < string.length(); i += Character.charCount(ch)) { ch = string.codePointAt(i); if (!Character.isLetter(ch)) { break; } } return string.substring(i); } |
Compliant Solution (Substring)
...
This compliant solution works both for supplementary and for combining characters \ [[Hornig 2007|AA. References#Hornig 07]\]. According to the Java API \ [[API 2006|AA. References#API 06] \] class {{java.text.BreakIterator
}} documentation:
The
BreakIterator
class implements methods for finding the location of boundaries in text. Instances ofBreakIterator
maintain a current position and scan over text returning the index of characters where boundaries occur.
...
Rule | Severity | Likelihood | Remediation Cost | Priority | Level |
---|---|---|---|---|---|
IDS10-J | low | unlikely | medium | P2 | L3 |
Bibliography
<ac:structured-macro ac:name="unmigrated-wiki-markup" ac:schema-version="1" ac:macro-id="7508bc2f-c6cf-467f-b948-d017363d57c4"><ac:plain-text-body><![CDATA [ [[API 2006AA. References#API 06]] | Classes | ]]></ac:plain-text-body></ac:structured-macro> | <ac:structured-macro ac:name="unmigrated-wiki-markup" ac:schema-version="1" ac:macro-id="b887cc42-573e-4bd6-a2b2-d36ee283b677"><ac:plain-text-body><![CDATA[ |
[ [Hornig 2007AA. References#Hornig 07] ] | Problem Areas: Characters ]]></ac:plain-text-body></ac:structured-macro> |
...
IDS09-J. Do not use locale-dependent methods on locale-dependent data without specifying the appropriate locale IDS11-J. Eliminate noncharacter code points before validation