本文通过描述DB2UDB字符转换过程，解决了所有这些以及类似的问题。
This article addresses all of these and similar issues by describing the DB2 UDB character conversion process.
这个函数也不会复制NUL字符，这可能也是一个问题。
This also doesn't copy a NUL character, which can be problem too.
应该对每个被解释的上下文进行智能分析，以便可以处理那些会在特定上下文中导致问题的字符。
An intelligent analysis of each context interpreted should be made so that only characters that could cause problems within each particular context are addressed.
人们发现这确实很困难，因为在一些情况下有太多的字符可能会带来问题。
That turns out to be really difficult, because so many characters can cause problems in some cases.
它也可以修复TMX中可能会导致使用问题的无效字符。
It can also fix invalid characters in TMX that can cause problems in use.
当您碰到字符转换方面的问题时，首先要识别应用程序和所涉及的DB 2UDB数据库服务器使用哪些代码页。
When you encounter problems with character conversions, first identify which code pages are being used by the application and the DB2 UDB database server involved.
因此，如果计算机使用来自标准ASCII的英语字符表示，肯定没有问题！
AS such, computers used an English character representation from standard ASCII with no problem.
但是我们必须让您注意一些有关名称中包含特殊字符的严重问题。
However we must persevere and bring to your attention some critical issues regarding names that contain special characters.
否则可能会遇到奇怪的问题，比如标准报告拥有错误的十进制字符。
Otherwise you may get strange issues, such as standard reports having incorrect decimal characters.
使用基于字符的函数可以解决将字节位置返回为字符位置的问题。
The problem of byte positions being returned for the character positions can be solved using character-based functions.
答：我认为如果愿意的话，字符实体这个被紧密关注的小问题是可以得到解决的。
A: I think the character entity is a small, tightly-focused problem that could be solved if there was the will to do so.
在完成140个字符，30秒故事之后，你需要提出一个问题。
When you have finished your 140-character, 30-second story, ask a question.
是哦，这里好像有三个字符，所以那个条件不会引起问题。
Yeah, there's like three letters there so that condition doesn't cause problems.
有很多字符都会带来特定的问题；只要可能，您就不愿意允许在程序内部或者最终输出中有特定含义的那些字符。
There are a large number of characters that can cause special problems; where possible, you don't want to allow characters that have a special meaning to the program internals or the eventual output.
将字符指针和字符字节声明为无符号类型的，这样可以防止8位字符的符号扩展问题。
Declare character Pointers and character bytes as unsigned to avoid sign extension problems with 8-bit characters.
DB 29的新功能解决了字符组成及其长度计算方面的问题，本文将讨论这些新功能。
The subject of what constitutes a character, and how you can count them, is addressed by the new DB2 9 functionality discussed in this article.
要避免代码页转换的问题，建议使用字符forBITDATA或blob代替字符类型。
To avoid code page conversion issues, the recommended approach is to use character FOR BIT DATA or BLOB instead of character types.
同Domino扩展产品家族一样，在CollaborativePortlets中包含特殊字符的名称也会引发问题。
Names containing special characters also cause problems in the Collaborative Portlets as well as the Domino extended product family.
由于所有操作名称的长度均为六个字符，因此该问题并不特定于此示例，但需要构想一个可以指定更复杂动词（例如“Get”、“List”或“Find”）的标准。
This is not problematic specifically in this example, since all of the operation names are six characters long, but imagine a standard that specifies more complex verbs like "Get", "List", or "Find".
在解析时，您可以使用处理任何特殊字符和编码问题的WebSpherePortalAPIs来构建您的JSON结构，为您省去很多麻烦。
As you parse, you can build your JSON structure using the WebSphere Portal APIs that handle any special characters and encoding issues, giving you a little less to worry about.
这里是经常会带来问题的字符的部分清单。
Here is a partial list of the kinds of characters that often cause trouble.
SQL注入本质上与shell元字符的问题是相同的，不过它是由SQL解释器进行解释的，而不是由shell进行解释的。
SQL injection is essentially the same problem as the shell meta-character one, but with an SQL interpreter instead of the shell.
如果没有问题，则将s1中的余下字符转换成整数。
If it's okay, convert the remaining chars in s1 into an integer.
修正了CSL(引文样式语言)文件中非拉丁字符不能正确显示的问题。
Fix non-latin characters in CSL (Citation Style Language) files not being rendered correctly.
最大的问题是如何明确地指出在字符串中哪些是合法的。
The biggest problem is figuring out exactly what should be legal in the string.
安装源文档中使用的字体和字符集可以解决此问题。
Installing the fonts and character set used in the source document can solve the problem.
这为我们带来了一个非常常见的问题：元字符漏洞。
This brings us to a very common problem — meta-character vulnerability.
您将使用POST而不是GET，因为您希望避免任何因查询字符串长度过长和字符串转义而引起的问题。
You use POST instead of GET because you want to avoid any issues with the query string length being exceeded or escaping of strings.
很快我就发现只需要以上列出的字符，限定这个字符集(尤其是第一个字符)可以避免很多问题。
It didn't take long to realize that only the characters listed above are needed, and limiting the character set (especially the first character) would eliminate many problems.
很快我就发现只需要以上列出的字符，限定这个字符集(尤其是第一个字符)可以避免很多问题。
It didn't take long to realize that only the characters listed above are needed, and limiting the character set (especially the first character) would eliminate many problems.
应用推荐