java.text.normalizer,Normalizer.html

Normalizer (Java Platform SE 7 )

if (location.href.indexOf('is-external=true') == -1) {

parent.document.title="Normalizer (Java Platform SE 7 )";

}

//-->

JavaScript is disabled on your browser.
Java™ Platform
Standard Ed. 7
java.text

Class Normalizer


  • public final class Normalizer

    extends Object

    This class provides the method normalize which transforms Unicode

    text into an equivalent composed or decomposed form, allowing for easier

    sorting and searching of text.

    The normalize method supports the standard normalization forms

    described in

    Unicode Standard Annex #15 — Unicode Normalization Forms.

    Characters with accents or other adornments can be encoded in

    several different ways in Unicode. For example, take the character A-acute.

    In Unicode, this can be encoded as a single character (the "composed" form):

     
          

    U+00C1 LATIN CAPITAL LETTER A WITH ACUTE

    or as two separate characters (the "decomposed" form):

     
          

    U+0041 LATIN CAPITAL LETTER A

    U+0301 COMBINING ACUTE ACCENT

    To a user of your program, however, both of these sequences should be

    treated as the same "user-level" character "A with acute accent". When you

    are searching or comparing text, you must ensure that these two sequences are

    treated as equivalent. In addition, you must handle characters with more than

    one accent. Sometimes the order of a character's combining accents is

    significant, while in other cases accent sequences in different orders are

    really equivalent.

    Similarly, the string "ffi" can be encoded as three separate letters:

     
          

    U+0066 LATIN SMALL LETTER F

    U+0066 LATIN SMALL LETTER F

    U+0069 LATIN SMALL LETTER I

    or as the single character

     
          

    U+FB03 LATIN SMALL LIGATURE FFI

    The ffi ligature is not a distinct semantic character, and strictly speaking

    it shouldn't be in Unicode at all, but it was included for compatibility

    with existing character sets that already provided it. The Unicode standard

    identifies such characters by giving them "compatibility" decompositions

    into the corresponding semantic characters. When sorting and searching, you

    will often want to use these mappings.

    The normalize method helps solve these problems by transforming

    text into the canonical composed and decomposed forms as shown in the first

    example above. In addition, you can have it perform compatibility

    decompositions so that you can treat compatibility characters the same as

    their equivalents.

    Finally, the normalize method rearranges accents into the

    proper canonical order, so that you do not have to worry about accent

    rearrangement on your own.

    The W3C generally recommends to exchange texts in NFC.

    Note also that most legacy character encodings use only precomposed forms and

    often do not encode any combining marks by themselves. For conversion to such

    character encodings the Unicode text needs to be normalized to NFC.

    For more usage examples, see the Unicode Standard Annex.

    Since:
    1.6
Java™ Platform
Standard Ed. 7

Submit a bug or feature
For further API reference and developer documentation, see Java SE Documentation. That documentation contains more detailed, developer-targeted descriptions, with conceptual overviews, definitions of terms, workarounds, and working code examples.Copyright © 1993, 2014, Oracle and/or its affiliates. All rights reserved.

一键复制

编辑

Web IDE

原始数据

按行查看

历史

  • 0
    点赞
  • 0
    收藏
    觉得还不错? 一键收藏
  • 0
    评论

“相关推荐”对你有帮助么?

  • 非常没帮助
  • 没帮助
  • 一般
  • 有帮助
  • 非常有帮助
提交
评论
添加红包

请填写红包祝福语或标题

红包个数最小为10个

红包金额最低5元

当前余额3.43前往充值 >
需支付:10.00
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包
实付
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明:

1.余额是钱包充值的虚拟货币,按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载,可以购买VIP、付费专栏及课程。

余额充值