Both user names and passwords are case sensitive.
用户名称和密码都是区分大小写的。
If case sensitive is enabled, Samba USES whatever case the client requests.
如果启用了case sensitive，那么Samba就会使用客户端要求的大小写。
A name may consist of up to 32 characters, and all characters are case sensitive.
记录存储的名称最多可以包含32个字符，并且所有字符都是大小写敏感的。
Note: The DB2 command is not case sensitive. XML data and schema locations are case sensitive.
注意：这个DB 2命令不区分大小写，但XML数据和模式位置区分大小写。
You can check the Case Sensitive checkbox to indicate the importance of upper and lowercase characters.
可以选中Case Sensitive复选框以表示区分大写和小写字符。
Otherwise, this field is optional and can be enabled when case sensitive authorization check is required.
否则，该字段是可选的，并且在大小写敏感验证检查必须进行时可以被激活。
Case sensitive : search is performed with respect to the letter-case of the words (default is to ignore letter-case)
区分大小写：对单词的字母大小写进行搜索（默认是忽略字母大小）
By default, the comparison is case sensitive, which means that inetorgperson and inetorgperson are treated as different classes.
缺省情况下，该比较是区分大小写的，这意味着inetorgperson和inetorgperson将被视为不同的类。
Typically, an authorization check involves checking the complete DN of a user, which is unique in the LDAP server and is case sensitive.
通常，一个验证检查包括检查一个用户的完整dn，检查是否在LDAP服务器中是唯一的，以及检查是否是区分大小写的。
Whether the physical location like '/work/customer1.xsd' is case sensitive depends on the operating system. (Windows is not case sensitive.
物理位置（如 /work/customer1.xsd）是否区分大小写取决于操作系统（Windows不区分大小写，但 Linux 和 UNIX 区分大小写。）
The easiest way to do this is to assign the eForm field the same name as the corresponding data field (the field names are case sensitive).
最简单的方法是对eFor m字段分配对应的数据字段的名称(字段名称区分大小写)。
Note: I have found that I had to tick Case sensitive when entering data into the search box, otherwise nothing would return from the search.
注意：我发现在搜索框中输入数据时必须坚持区分大小写，否则搜索不返回结果。
The trailing I after the regex statement (which in this case is simply the phrase walmart) signifies that the statement is not case sensitive.
regex语句(本例中为walmart)后面的i表明该语句不区分大小写。
Note that capitalization of the SQL code and MySQL internal commands is optional, but names of databases, tables, and columns are case sensitive.
注意，SQL代码和MySQL内部命令的大写是可选的，但是数据库的名称、表和列都对大小写敏感。
Make sure to use the name of these variables in capital letters as xquery is a case sensitive language and relation column names are always stored in capital letters.
请确保以大写字母的方式使用这些变量的名称，因为xquery是一个区分大小写的语言，而且关系列名称常常以大写的方式存储。
You can escape these rules by placing the name in double quotation marks, which allows names to be case sensitive and to include additional characters (including spaces).
通过把名称放在双引号中，可以避开这些规则，使用双引号允许名称区分大小写以及包含附加字符（包括空格）。
An element usually consists of two tags, a start tag and an end tag, each of which is bracketed by an open and a close. XML is case sensitive and does not ignore white space.
元素通常包括两个标记，一个起始标记和一个结束标记，分别用和表示。XML大小写敏感，而且空白是有意义的。
To check the performance difference between queries in case-sensitive and case-insensitive databases, we created a regular database (case sensitive) and a case-insensitive database.
为了查明区分大小写的和不区分大小写的数据库之间的性能差异，我们创建了一个常规数据库（区分大小写）和一个不区分大小写的数据库。
If the file does exist, then you can have a pretty good guess as to what its case-sensitive name might be.
如果该文件确实存在，那么您可以就其区分大小写的名称到底是什么进行很好的猜测。
This article describes this process in more detail and also explains how to revert to the default case-sensitive queries.
这篇文章描述了关于这个过程更详细的细节，同时还阐述了如何归还到默认的区分大小写的查询中来。
In each XML file, you'll find a similar case-sensitive target statement that specifies where the content belongs in the navigation of a solution information project.
在每个XML文件中，都能发现一个类似的区分大小写的目标语句，这个语句指定了内容属于解决方案信息项目导航中的哪个位置。
It's possible, as shown above, to write a rename rule that converts case-sensitive files into lowercase file names, thereby causing clashes among previously unique file names.
如上所述，可以编写一条重命名规则将区分大小写的文件名转换为小写文件名，这样可能会与以前已存在的唯一的文件名发生冲突。
Accessing the elements is case-sensitive.
访问元素是区分大小写的。
You should be aware that in deference to case-sensitive languages, all references to a definition must use the same case as the defining occurrence.
应该注意根据区分大小写的语言，所有的定义引用必须与定义的大小写相同。
Now it would seem fairly trivial to map from case-sensitive to case-insensitive, but in fact it's hard to do it efficiently.
从区分大小写映射到不区分大小写现在看来是很微不足道的，但实际上很难有效地进行这一映射。
When you create the index for each field, you can decide whether queries will be case-insensitive or case-sensitive.
当您为每个域创建索引时，您可以决定查询是否要支持区分大小写。
Tip: The same script creates indexes for both case-insensitive and case-sensitive queries.
提示：相同的脚本可以同时为区分大小写的和不区分大小写的查询创建索引。
The default for this setting is auto, which looks for a client extension field to indicate that the client supports case-sensitive access.
该设置的默认值是auto，它会寻找一个客户端扩展字段来指示客户端是否支持区分大小写的访问。
When comparing operations, it performs a case-sensitive name match along with a comparison of input argument data types, and ignores return types.
在比较操作的时候，API会比较名称（区分大小写）以及输入参数数据类型，并忽略返回值类型。
When comparing operations, it performs a case-sensitive name match along with a comparison of input argument data types, and ignores return types.
在比较操作的时候，API会比较名称（区分大小写）以及输入参数数据类型，并忽略返回值类型。
应用推荐