| /freebsd-13.1/crypto/openssl/doc/man3/ |
| H A D | ASN1_STRING_print_ex.pod | 28 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 …]
|
| H A D | PEM_read_bio_ex.pod | 31 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.1/share/i18n/csmapper/APPLE/ |
| H A D | SYMBOL%UCS.src | 29 # Unicode 3.2 characters instead of sequences
30 # involving corporate-use characters. Update
87 # Some of these mappings require the use of corporate characters.
130 # encodes only the abstract characters, so one set of these (the
132 # characters (see below).
143 # - Use standard Unicode characters as much as possible, to
146 # characters.
152 # a) If possible, use private use characters in combination with
153 # standard Unicode characters to mark variants of the standard
170 # characters, some characters in the Mac OS Symbol character set map
[all …]
|
| H A D | UCS%SYMBOL.src | 29 # Unicode 3.2 characters instead of sequences
30 # involving corporate-use characters. Update
87 # Some of these mappings require the use of corporate characters.
130 # encodes only the abstract characters, so one set of these (the
132 # characters (see below).
143 # - Use standard Unicode characters as much as possible, to
146 # characters.
152 # a) If possible, use private use characters in combination with
153 # standard Unicode characters to mark variants of the standard
170 # characters, some characters in the Mac OS Symbol character set map
[all …]
|
| H A D | KEYBOARD%UCS.src | 68 # Some of these mappings require the use of corporate characters.
99 # - Use standard Unicode characters as much as possible, to
102 # characters.
105 # correspond to distinct, single Unicode characters. To map these
108 # a) If possible, use private use characters in combination with
109 # standard Unicode characters to mark variants of the standard
117 # 2-4 Unicode characters should be treated as a single entity for
119 # - they are like combining characters, and can follow a standard
126 # are combined with standard Unicode characters, some characters in
136 # Keyboard characters which have no relationship to any standard
[all …]
|
| H A D | UCS%KEYBOARD.src | 68 # Some of these mappings require the use of corporate characters.
99 # - Use standard Unicode characters as much as possible, to
102 # characters.
105 # correspond to distinct, single Unicode characters. To map these
108 # a) If possible, use private use characters in combination with
109 # standard Unicode characters to mark variants of the standard
117 # 2-4 Unicode characters should be treated as a single entity for
119 # - they are like combining characters, and can follow a standard
126 # are combined with standard Unicode characters, some characters in
136 # Keyboard characters which have no relationship to any standard
[all …]
|
| H A D | UCS%THAI.src | 40 # instead of single corporate characters; see
83 # Some of these mappings require the use of corporate characters.
88 # Mac OS Thai character set uses the standard control characters at
107 # ellipsis), no-break space, and two special characters "word join"
113 # be considered presentation forms only and not characters. In most
118 # characters in the Mac OS Thai encoding. They are mapped using
133 # avoid having content carried by private-use characters.
137 # characters.
147 # consisting of a base character and other combining characters) to
153 # standard Unicode characters, some characters in the Mac OS Thai
[all …]
|
| H A D | THAI%UCS.src | 40 # instead of single corporate characters; see
83 # Some of these mappings require the use of corporate characters.
88 # Mac OS Thai character set uses the standard control characters at
107 # ellipsis), no-break space, and two special characters "word join"
113 # be considered presentation forms only and not characters. In most
118 # characters in the Mac OS Thai encoding. They are mapped using
133 # avoid having content carried by private-use characters.
137 # characters.
147 # consisting of a base character and other combining characters) to
153 # standard Unicode characters, some characters in the Mac OS Thai
[all …]
|
| H A D | HEBREW%UCS.src | 76 # Unicode characters are used here. A single Unicode character
83 # Some of these mappings require the use of corporate characters.
118 # only be used with a limited number of characters, and it is
145 # 2. Directional characters and roundtrip fidelity
189 # 1. Matching the direction of Mac OS Hebrew characters
196 # characters to a code in the Unicode corporate use zone is
203 # direction of the resulting Unicode characters.
260 # - Use standard Unicode characters as much as possible, to
263 # characters.
270 # standard Unicode characters to mark variants of the standard
[all …]
|
| H A D | UCS%ARABIC.src | 100 # also contains several characters needed for Urdu and/or Farsi.
118 # graphic characters: additional Arabic letters for Farsi and Urdu,
128 # 2. Directional characters and roundtrip fidelity
135 # problems, certain punctuation and symbol characters were encoded
161 # 0x2C or period 0x2E, then the characters will be displayed using
217 # 1. Matching the direction of Mac OS Arabic characters
224 # characters to a code in the Unicode corporate use zone is
231 # direction of the resulting Unicode characters.
246 # When mapping several characters in a row that require direction
252 # If neutral characters that require direction forcing are already
[all …]
|
| H A D | ARABIC%UCS.src | 100 # also contains several characters needed for Urdu and/or Farsi.
118 # graphic characters: additional Arabic letters for Farsi and Urdu,
128 # 2. Directional characters and roundtrip fidelity
135 # problems, certain punctuation and symbol characters were encoded
161 # 0x2C or period 0x2E, then the characters will be displayed using
217 # 1. Matching the direction of Mac OS Arabic characters
224 # characters to a code in the Unicode corporate use zone is
231 # direction of the resulting Unicode characters.
246 # When mapping several characters in a row that require direction
252 # If neutral characters that require direction forcing are already
[all …]
|
| H A D | FARSI%UCS.src | 82 # Mac OS Farsi character set uses the standard control characters at
105 # Mac OS Farsi characters 0xEB-0xF2 are non-spacing/combining marks.
107 # 2. Directional characters and roundtrip fidelity
115 # characters were encoded twice, one with a left-right direction
141 # 0x2C or period 0x2E, then the characters will be displayed using
191 # 1. Matching the direction of Mac OS Farsi characters
198 # characters to a code in the Unicode corporate use zone is
205 # direction of the resulting Unicode characters.
220 # When mapping several characters in a row that require direction
226 # If neutral characters that require direction forcing are already
[all …]
|
| H A D | UCS%FARSI.src | 82 # Mac OS Farsi character set uses the standard control characters at
105 # Mac OS Farsi characters 0xEB-0xF2 are non-spacing/combining marks.
107 # 2. Directional characters and roundtrip fidelity
115 # characters were encoded twice, one with a left-right direction
141 # 0x2C or period 0x2E, then the characters will be displayed using
191 # 1. Matching the direction of Mac OS Farsi characters
198 # characters to a code in the Unicode corporate use zone is
205 # direction of the resulting Unicode characters.
220 # When mapping several characters in a row that require direction
226 # If neutral characters that require direction forcing are already
[all …]
|
| H A D | DINGBATS%UCS.src | 32 # Unicode 3.2 characters. Update URLs, notes.
85 # Some of these mappings require the use of corporate characters.
90 # Mac OS Dingbats character set uses the standard control characters
122 # - The mappings for the following Mac OS Dingbats characters
123 # were changed to use standard Unicode characters added for
128 # - The mappings for the following Mac OS Dingbats characters
129 # were changed from single corporate-zone Unicode characters
130 # to standard Unicode characters:
133 # - The mappings for the following Mac OS Dingbats characters
134 # were changed from single corporate-zone Unicode characters
|
| H A D | UCS%DINGBATS.src | 32 # Unicode 3.2 characters. Update URLs, notes.
85 # Some of these mappings require the use of corporate characters.
90 # Mac OS Dingbats character set uses the standard control characters
122 # - The mappings for the following Mac OS Dingbats characters
123 # were changed to use standard Unicode characters added for
128 # - The mappings for the following Mac OS Dingbats characters
129 # were changed from single corporate-zone Unicode characters
130 # to standard Unicode characters:
133 # - The mappings for the following Mac OS Dingbats characters
134 # were changed from single corporate-zone Unicode characters
|
| /freebsd-13.1/contrib/libxo/ |
| H A D | README.md | 18 "{: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.1/crypto/heimdal/lib/wind/ |
| H A D | CompositionExclusions-3.2.0.txt | 4 # 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 …]
|
| H A D | rfc4013.txt | 46 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
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]
130 - Inappropriate for canonical representation characters
132 - Change display properties or deprecated characters
[all …]
|
| H A D | rfc3491.txt | 67 - 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.1/contrib/subversion/subversion/libsvn_subr/utf8proc/ |
| H A D | lump.md | 2 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.1/contrib/libxo/doc/ |
| H A D | intro.rst | 14 "{:characters/%7ju} {d:filename/%s}\n",
31 <characters>1140</characters>
42 "characters": 1140,
55 <div class="data" data-tag="characters"> 1140</div>
|
| /freebsd-13.1/contrib/pam_modules/pam_passwdqc/ |
| H A D | README | 28 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.1/contrib/dialog/samples/ |
| H A D | textbox2 | 10 The file should not contain any 'tab' characters, so you should 'expand'
11 the file first if it contains 'tab' characters.
|
| H A D | textbox | 10 The file should not contain any 'tab' characters, so you should 'expand'
11 the file first if it contains 'tab' characters.
|
| /freebsd-13.1/contrib/sendmail/ |
| H A D | KNOWNBUGS | 18 characters then it may be truncated during output. For example,
19 if a single address in the To: header is longer than 256 characters
48 characters or it contains a single word longer than 256 (MAXNAME)
49 characters then no header check is done even if one is configured for
54 Header lines which are longer than 2045 characters will be split
55 but some characters might be lost. Fix: obey RFC (2)822 and do not
56 send lines that are longer than 1000 characters.
189 8-bit characters, those characters can be included in the message
191 only accept 7-bit characters.
203 illegal characters), sendmail can produce an illegal message.
[all …]
|