sin/samba-mirror
1
0
Fork 0
mirror of https://github.com/samba-team/samba.git synced 2025-02-28 01:58:17 +03:00
Code

Correct "hexidecimal" typos.

Browse Source 
Signed-off-by: Chris Lamb <chris@chris-lamb.co.uk>
Reviewed-by: Andrew Bartlett <abartlet@samba.org>
Reviewed-by: Garming Sam <garming@catalyst.net.nz>
This commit is contained in:
Chris Lamb 2017-02-18 09:00:52 +13:00 committed by Garming Sam
parent fccdf34a0f
commit 875f45b3f1
5 changed files with 7 additions and 7 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
docs-xml/using_samba/ch01.xml
View File

@ -660,7 +660,7 @@ HYDRA &lt;20&gt; UNIQUE Registered
</table>
<para>Note that because <indexterm id="ch01-idx-951737-0"><primary>DNS (Domain Name System)</primary><secondary>names</secondary><tertiary> resource types and</tertiary></indexterm>DNS names don't have resource types, the designers intentionally made hexidecimal value 20 (an ASCII space) default to the type for a file server.</para>
<para>Note that because <indexterm id="ch01-idx-951737-0"><primary>DNS (Domain Name System)</primary><secondary>names</secondary><tertiary> resource types and</tertiary></indexterm>DNS names don't have resource types, the designers intentionally made hexadecimal value 20 (an ASCII space) default to the type for a file server.</para>
</sect3>

2
docs-xml/using_samba/ch04.xml
View File

@ -593,7 +593,7 @@ netbios aliases = sales accounting payroll</programlisting>
<varlistentry><term>Numerical</term>
<listitem><para>
<indexterm id="ch04-idx-967220-0"><primary>numerical type</primary></indexterm>An integer, hexidecimal, or octal number. The standard <literal>0x</literal><emphasis>nn</emphasis> syntax is used for hexadecimal and <literal>0</literal><emphasis>nnn</emphasis> for octal.</para></listitem>
<indexterm id="ch04-idx-967220-0"><primary>numerical type</primary></indexterm>An integer, hexadecimal, or octal number. The standard <literal>0x</literal><emphasis>nn</emphasis> syntax is used for hexadecimal and <literal>0</literal><emphasis>nnn</emphasis> for octal.</para></listitem>
</varlistentry>

2
docs-xml/using_samba/ch06.xml
View File

@ -1210,7 +1210,7 @@ username</title>
<varlistentry><term>Last Change Time</term>
<listitem><para>This code consists of the characters <literal>LCT-</literal> followed by a hexidecimal representation of the amount of seconds since the epoch (midnight on January 1, 1970) that the entry was last changed.</para></listitem>
<listitem><para>This code consists of the characters <literal>LCT-</literal> followed by a hexadecimal representation of the amount of seconds since the epoch (midnight on January 1, 1970) that the entry was last changed.</para></listitem>
</varlistentry>
</variablelist>

6
docs-xml/using_samba/ch08.xml
View File

@ -860,7 +860,7 @@ client code page</title>
<entry colname="col1"><para><literal>HEX</literal></para></entry>
<entry colname="col2"><para>Three-byte hexidecimal code</para></entry>
<entry colname="col2"><para>Three-byte hexadecimal code</para></entry>
</row>
@ -868,7 +868,7 @@ client code page</title>
<entry colname="col1"><para><literal>CAP</literal></para></entry>
<entry colname="col2"><para>Three-byte hexidecimal code (Columbia Appletalk Program)</para></entry>
<entry colname="col2"><para>Three-byte hexadecimal code (Columbia Appletalk Program)</para></entry>
</row>
@ -894,7 +894,7 @@ valid chars = 0450:0420 0x0A20:0x0A00
valid chars = A:a</programlisting>
<para>Each of the characters in the list specified should be separated by spaces. If there is a colon between two characters or their numerical equivalents, the data to the left of the colon is considered an uppercase character, while the data to the right is considered the lowercase character. You can represent characters both by literals (if you can type them) and by octal, hexidecimal, or decimal Unicode equivalents.</para>
<para>Each of the characters in the list specified should be separated by spaces. If there is a colon between two characters or their numerical equivalents, the data to the left of the colon is considered an uppercase character, while the data to the right is considered the lowercase character. You can represent characters both by literals (if you can type them) and by octal, hexadecimal, or decimal Unicode equivalents.</para>
<para>We recommend against using this option. Instead, go with one of the standard code pages listed earlier in this section. If you do use this option, however, it must be listed after the <literal>client</literal> <literal>code</literal> <literal>page</literal> to which you wish to add the character. Otherwise, the characters will not be added.<indexterm id="ch08-idx-965533-0" class="endofrange" startref="ch08-idx-965219-0"/>

2
source4/dsdb/common/dsdb_dn.c
View File

@ -183,7 +183,7 @@ struct dsdb_dn *dsdb_dn_parse_trusted(TALLOC_CTX *mem_ctx, struct ldb_context *l
bval.length = strhex_to_str((char *)bval.data, bval.length,
p1, blen);
if (bval.length != (blen / 2)) {
DEBUG(10, (__location__ ": non hexidecimal characters found in binary prefix\n"));
DEBUG(10, (__location__ ": non hexadecimal characters found in binary prefix\n"));
goto failed;
}
} else {