Lines Matching +full:performance +full:- +full:rules

1 ---
6 ---
7 <!--
10 -->
18 StringPrep provides sets of rules for use of Unicode and syntax for prevention
25 protocols is defined in RFC 3454 (<http://www.rfc-editor.org/rfc/rfc3454.txt> ).
26 The RFC defines a broad framework and rules for processing the strings.
29 whose applicability is limited to the protocol. Profiles are a set of rules and
51     output string. Control codes, private use area code points, non-character
69 4.  *Check BiDi*: Check for code points with strong right-to-left directionality
70     in the output of step 3. If present, check if the string satisfies the rules
76 RFC 3491(<http://www.rfc-editor.org/rfc/rfc3491.txt> ).
78 The profile specifies the following rules:
88     the rules specified in StringPrep.
95 (<http://www.rfc-editor.org/rfc/rfc3492.txt> ).
114 (<http://www.rfc-editor.org/rfc/rfc3490.txt> ), satisfies the above
126     domain labels are processed by StringPrep algorithm by using the rules
129     using Punycode. IDNA uses “xn--” before the encoded label.
155 Letter-Digit-Hyphen code points and adhere to the STD3 ASCII Rules.
163 Open-Use-Close pattern. A StringPrep profile is opened, the strings are
164 processed according to the rules specified in the profile and the profile is
184     memory mapped and cached for optimum performance.
203      * to the rules specified in the profile
227         String s = new String(src, "UTF-8");
230         return out.toString().getBytes("UTF-8");
341 The StringPrep profiles are used in network protocols so runtime performance is
345 plug-in arbitrary profiles and get the desired result out of the framework.
347 ICU is designed for this usage by providing build-time tools for arbitrary
348 StringPrep profile definitions, and loading them from application-supplied data
353 A web application at <https://icu4c-demos.unicode.org/icu-bin/idnbrowser>
355 available at <https://github.com/unicode-org/icu-demos/tree/main/idnbrowser>.
362 (<http://www.rfc-editor.org/rfc/rfc3530.txt> ) defines use of Unicode text in
387 near real-time extensible messaging and presence. This protocol defines use of