Passing valid data avoids meta-character problems.
传递有效数据，防止元字符的问题。
This brings us to a very common problem — meta-character vulnerability.
这为我们带来了一个非常常见的问题：元字符漏洞。
SQL injection is essentially the same problem as the shell meta-character one, but with an SQL interpreter instead of the shell.
SQL注入本质上与shell元字符的问题是相同的，不过它是由SQL解释器进行解释的，而不是由shell进行解释的。
The ~ meta-character should also work to access information from a home directory, providing the user you are using to connect has rights to read it.
假设您用于连接的用户有读取权限，还需要使用元字符~才能访问主目录中的信息。
But if you must use the shell and you can't limit the data that comes in, you need to escape every potential meta-character before sending it in a command to the shell.
但是如果您必须使用shell并且不能限制到达的数据，那么就需要在将命令中的字符发送到shell中之前对可能存在的每个元字符进行转义。
For example, to specify that the character encoding of the current document is "EUC-JP", a document should include the following META declaration.
例如，为了表述当前文档的字符编码为“EUC - JP”，文档内应该包含如下内容的META元素声明。
The meta information includes: search information corresponding to at least one search condition of a scene, character, sound, location, and item;
元信息包括：相应于场景、角色、声音、地点和项目的搜索条件中的至少一个的搜索信息；
The meta information includes: search information corresponding to at least one search condition of a scene, character, sound, location, and item;
元信息包括：相应于场景、角色、声音、地点和项目的搜索条件中的至少一个的搜索信息；
应用推荐