Home
last modified time | relevance | path

Searched refs:characters (Results 1 – 25 of 569) sorted by relevance

12345678910>>...23

/freebsd-13-stable/crypto/openssl/doc/man3/
HDASN1_STRING_print_ex.pod28 ASN1_STRING_print_ex(). It replaces unprintable characters (other than CR, LF)
43 Various characters can be escaped. If B<ASN1_STRFLGS_ESC_2253> is set the characters
45 characters are escaped. If B<ASN1_STRFLGS_ESC_MSB> is set characters with the
52 using exactly four characters for the hex representation. If it is 32 bits then
53 "\WXXXXXXXX" is used using eight characters of its hex representation. These forms
56 Printable characters are normally escaped using the backslash '\' character. If
58 double quote characters: this is arguably more readable than the backslash
59 notation. Other characters use the "\XX" using exactly two characters of the hex
62 If B<ASN1_STRFLGS_UTF8_CONVERT> is set then characters are converted to UTF8
64 option will correctly display multi byte characters.
[all …]
HDPEM_read_bio_ex.pod31 and control characters from the end of each line, so as to be compatible with
34 If PEM_FLAG_ONLY_B64 is set, all characters are required to be valid base64
35 characters (or newlines); non-base64 characters are treated as end of input.
37 If neither PEM_FLAG_EAY_COMPATIBLE or PEM_FLAG_ONLY_B64 is set, control characters
/freebsd-13-stable/share/i18n/csmapper/APPLE/
DSYMBOL%UCS.src28 # Unicode 3.2 characters instead of sequences
29 # involving corporate-use characters. Update
40 # instead of single corporate characters, also
86 # Some of these mappings require the use of corporate characters.
91 # Mac OS Symbol character set uses the standard control characters
124 # not, so these are mapped using corporate-zone Unicode characters
129 # encodes only the abstract characters, so one set of these (the
131 # characters (see below).
142 # - Use standard Unicode characters as much as possible, to
145 # characters.
[all …]
DUCS%SYMBOL.src28 # Unicode 3.2 characters instead of sequences
29 # involving corporate-use characters. Update
40 # instead of single corporate characters, also
86 # Some of these mappings require the use of corporate characters.
91 # Mac OS Symbol character set uses the standard control characters
124 # not, so these are mapped using corporate-zone Unicode characters
129 # encodes only the abstract characters, so one set of these (the
131 # characters (see below).
142 # - Use standard Unicode characters as much as possible, to
145 # characters.
[all …]
DKEYBOARD%UCS.src67 # Some of these mappings require the use of corporate characters.
98 # - Use standard Unicode characters as much as possible, to
101 # characters.
103 # Some of the characters in the Mac OS Keyboard character set do not
104 # correspond to distinct, single Unicode characters. To map these
107 # a) If possible, use private use characters in combination with
108 # standard Unicode characters to mark variants of the standard
111 # Apple has defined a block of 32 corporate characters as "transcoding
113 # characters to force them to be treated in a special way for mapping
116 # 2-4 Unicode characters should be treated as a single entity for
[all …]
DUCS%KEYBOARD.src67 # Some of these mappings require the use of corporate characters.
98 # - Use standard Unicode characters as much as possible, to
101 # characters.
103 # Some of the characters in the Mac OS Keyboard character set do not
104 # correspond to distinct, single Unicode characters. To map these
107 # a) If possible, use private use characters in combination with
108 # standard Unicode characters to mark variants of the standard
111 # Apple has defined a block of 32 corporate characters as "transcoding
113 # characters to force them to be treated in a special way for mapping
116 # 2-4 Unicode characters should be treated as a single entity for
[all …]
DTHAI%UCS.src39 # instead of single corporate characters; see
82 # Some of these mappings require the use of corporate characters.
87 # Mac OS Thai character set uses the standard control characters at
106 # ellipsis), no-break space, and two special characters "word join"
112 # be considered presentation forms only and not characters. In most
117 # characters in the Mac OS Thai encoding. They are mapped using
130 # - Use standard Unicode characters as much as possible, to maximize
132 # avoid having content carried by private-use characters.
134 # To satisfy both goals, we use private use characters to mark variants
136 # characters.
[all …]
DUCS%THAI.src39 # instead of single corporate characters; see
82 # Some of these mappings require the use of corporate characters.
87 # Mac OS Thai character set uses the standard control characters at
106 # ellipsis), no-break space, and two special characters "word join"
112 # be considered presentation forms only and not characters. In most
117 # characters in the Mac OS Thai encoding. They are mapped using
130 # - Use standard Unicode characters as much as possible, to maximize
132 # avoid having content carried by private-use characters.
134 # To satisfy both goals, we use private use characters to mark variants
136 # characters.
[all …]
DHEBREW%UCS.src75 # Unicode characters are used here. A single Unicode character
82 # Some of these mappings require the use of corporate characters.
87 # Mac OS Hebrew character set uses the standard control characters at
117 # only be used with a limited number of characters, and it is
126 # - Latin characters with diacritics at 0x80 and 0x82-0x9F. However,
136 # SPACE. The glyphs for some of the other punctuation characters
139 # - Four obsolete characters at 0xC2-0xC5 known as canorals (not to
144 # 2. Directional characters and roundtrip fidelity
151 # problems, certain punctuation, symbol, and digit characters have
188 # 1. Matching the direction of Mac OS Hebrew characters
[all …]
DUCS%ARABIC.src85 # Mac OS Arabic character set uses the standard control characters at
99 # also contains several characters needed for Urdu and/or Farsi.
117 # graphic characters: additional Arabic letters for Farsi and Urdu,
121 # characters have right-left directionality, while the ASCII versions
125 # Mac OS Arabic characters 0xEB-0xF2 are non-spacing/combining marks.
127 # 2. Directional characters and roundtrip fidelity
134 # problems, certain punctuation and symbol characters were encoded
160 # 0x2C or period 0x2E, then the characters will be displayed using
161 # European forms (This will happen even if there are neutral characters
216 # 1. Matching the direction of Mac OS Arabic characters
[all …]
DARABIC%UCS.src85 # Mac OS Arabic character set uses the standard control characters at
99 # also contains several characters needed for Urdu and/or Farsi.
117 # graphic characters: additional Arabic letters for Farsi and Urdu,
121 # characters have right-left directionality, while the ASCII versions
125 # Mac OS Arabic characters 0xEB-0xF2 are non-spacing/combining marks.
127 # 2. Directional characters and roundtrip fidelity
134 # problems, certain punctuation and symbol characters were encoded
160 # 0x2C or period 0x2E, then the characters will be displayed using
161 # European forms (This will happen even if there are neutral characters
216 # 1. Matching the direction of Mac OS Arabic characters
[all …]
DFARSI%UCS.src81 # Mac OS Farsi character set uses the standard control characters at
104 # Mac OS Farsi characters 0xEB-0xF2 are non-spacing/combining marks.
106 # 2. Directional characters and roundtrip fidelity
114 # characters were encoded twice, one with a left-right direction
140 # 0x2C or period 0x2E, then the characters will be displayed using
141 # European forms (This will happen even if there are neutral characters
190 # 1. Matching the direction of Mac OS Farsi characters
197 # characters to a code in the Unicode corporate use zone is
198 # undesirable, since both of the plus sign characters are likely to
201 # The problem is solved with the use of direction override characters
[all …]
DUCS%FARSI.src81 # Mac OS Farsi character set uses the standard control characters at
104 # Mac OS Farsi characters 0xEB-0xF2 are non-spacing/combining marks.
106 # 2. Directional characters and roundtrip fidelity
114 # characters were encoded twice, one with a left-right direction
140 # 0x2C or period 0x2E, then the characters will be displayed using
141 # European forms (This will happen even if there are neutral characters
190 # 1. Matching the direction of Mac OS Farsi characters
197 # characters to a code in the Unicode corporate use zone is
198 # undesirable, since both of the plus sign characters are likely to
201 # The problem is solved with the use of direction override characters
[all …]
DUCS%DINGBATS.src31 # Unicode 3.2 characters. Update URLs, notes.
84 # Some of these mappings require the use of corporate characters.
89 # Mac OS Dingbats character set uses the standard control characters
121 # - The mappings for the following Mac OS Dingbats characters
122 # were changed to use standard Unicode characters added for
127 # - The mappings for the following Mac OS Dingbats characters
128 # were changed from single corporate-zone Unicode characters
129 # to standard Unicode characters:
132 # - The mappings for the following Mac OS Dingbats characters
133 # were changed from single corporate-zone Unicode characters
DDINGBATS%UCS.src31 # Unicode 3.2 characters. Update URLs, notes.
84 # Some of these mappings require the use of corporate characters.
89 # Mac OS Dingbats character set uses the standard control characters
121 # - The mappings for the following Mac OS Dingbats characters
122 # were changed to use standard Unicode characters added for
127 # - The mappings for the following Mac OS Dingbats characters
128 # were changed from single corporate-zone Unicode characters
129 # to standard Unicode characters:
132 # - The mappings for the following Mac OS Dingbats characters
133 # were changed from single corporate-zone Unicode characters
/freebsd-13-stable/contrib/libxo/
HDREADME.md18 "{:characters/%7ju/%ju}{d:filename/%s}\n",
34 <characters>1140</characters>
45 "characters": 1140
57 <div class="data" data-tag="characters"> 1140</div>
/freebsd-13-stable/crypto/heimdal/lib/wind/
HDCompositionExclusions-3.2.0.txt4 # This file lists the characters from the UAX #15 Composition Exclusion Table.
15 # This list of characters cannot be derived from the UnicodeData file.
89 # (2) Post Composition Version precomposed characters
90 # These characters cannot be derived solely from the UnicodeData.txt file
113 # These characters can be derived from the UnicodeData file
114 # by including all characters whose canonical decomposition
116 # These characters are simply quoted here for reference.
163 # These characters can be derived from the UnicodeData file
164 # by including all characters whose canonical decomposition consists
165 # of a sequence of characters, the first of which has a non-zero
[all …]
HDrfc4013.txt46 The algorithm assumes all strings are comprised of characters from
86 In the lists of mappings and the prohibited characters, the "U+" is
99 - non-ASCII space characters [StringPrep, C.1.2] that can be
102 - the "commonly mapped to nothing" characters [StringPrep, B.1]
121 This profile specifies the following characters as prohibited input:
123 - Non-ASCII space characters [StringPrep, C.1.2]
124 - ASCII control characters [StringPrep, C.2.1]
125 - Non-ASCII control characters [StringPrep, C.2.2]
126 - Private Use characters [StringPrep, C.3]
129 - Inappropriate for plain text characters [StringPrep, C.6]
[all …]
HDrfc3491.txt67 - The characters that are prohibited as output: specified in section
138 6. Bidirectional characters
184 The Unicode and ISO/IEC 10646 repertoires have many characters that
187 parties. Because it is impossible to map similar-looking characters
189 stringprep does nothing to map similar-looking characters together
190 nor to prohibit some characters because they look like others.
202 Current applications might assume that the characters allowed in
204 document vastly increases the number of characters available in
205 domain names. Every program that uses "special" characters in
207 the new characters allowed by this specification.
/freebsd-13-stable/contrib/subversion/subversion/libsvn_subr/utf8proc/
HDlump.md2 U+0020 <-- all space characters (general category Zs)
6 U+002D - <-- all dash characters (general category Pd),
22 U+005F _ <-- all connector characters (general category Pc),
/freebsd-13-stable/contrib/libxo/doc/
HDintro.rst14 "{:characters/%7ju} {d:filename/%s}\n",
31 <characters>1140</characters>
42 "characters": 1140,
55 <div class="data" data-tag="characters"> 1140</div>
/freebsd-13-stable/contrib/pam_modules/pam_passwdqc/
HDREADME28 N0 is used for passwords consisting of characters from one character
30 upper-case letters, and other characters. There's also the special
31 class for non-ASCII characters which couldn't be classified, but are
34 N1 is used for passwords consisting of characters from two character
40 N3 and N4 are used for passwords consisting of characters from three
48 contain enough different characters for the character classes and
57 The value 8 is treated specially. Passwords longer than 8 characters
58 will not be rejected, but will be truncated to 8 characters for the
/freebsd-13-stable/contrib/sendmail/
HDKNOWNBUGS18 characters then it may be truncated during output. For example,
19 if a single address in the To: header is longer than 256 characters
56 characters or it contains a single word longer than 256 (MAXNAME)
57 characters then no header check is done even if one is configured for
62 Header lines which are longer than 2045 characters will be split
63 but some characters might be lost. Fix: obey RFC (2)822 and do not
64 send lines that are longer than 1000 characters.
192 8-bit characters, those characters can be included in the message
194 only accept 7-bit characters.
206 illegal characters), sendmail can produce an illegal message.
[all …]
/freebsd-13-stable/contrib/dialog/samples/
HDtextbox210 The file should not contain any 'tab' characters, so you should 'expand'
11 the file first if it contains 'tab' characters.
HDtextbox10 The file should not contain any 'tab' characters, so you should 'expand'
11 the file first if it contains 'tab' characters.

12345678910>>...23