For CLI and legacy JDBC drivers, code page conversion tables are used.
对于CLI和遗留(legacy)JDBC驱动程序，要使用代码页转换表。
This guarantees that the code page conversion can be performed correctly.
这确保正确地执行编码页转换。
These tables are the external code page conversion tables used to translate values between various code pages.
这些表是用于在不同代码页之间转换值的外部代码页转换表。
In both generic scenarios, no code page conversion will happen if the code pages are the same for all the systems.
在这两个通用场景中，如果用于所有系统的代码页相同，就不会发生代码页转换。
The fundamental rule of the conversion process is that the receiving system will always perform the code page conversion.
转换过程的基本规则就是接收系统将总是执行代码页的转换。
On other systems, a different hexadecimal code might need to be used (this sequence does not undergo code page conversion).
在其他系统上可能需要使用不同的十六进制代码(此序列不经历代码页转换)。
The EXPORT utility performs an automatic code page conversion from Unicode (database code page) to 1252 (client code page).
EXPORT实用程序执行从Unicode（数据库编码页）到 1252（客户机编码页）的自动编码页转换。
Internally encoded XML data is preferred over externally encoded data because it can prevent unnecessary code page conversion.
内部编码的XML数据比外部编码的数据更为可取，因为它可以防止不必要的代码页转换。
On other systems, a different hexadecimal sequence might need to be used (this sequence does not undergo code page conversion).
在其他系统上可能需要使用不同的十六进制序列(此序列不经历代码页转换)。
To avoid code page conversion issues, the recommended approach is to use character FOR BIT DATA or BLOB instead of character types.
要避免代码页转换的问题，建议使用字符forBITDATA或blob代替字符类型。
To simplify things, the DB2 data movement utilities, namely EXPORT, IMPORT, and LOAD, can perform an automatic code page conversion.
为了简化这个过程，DB 2数据转移实用程序(即export、IMPORT和LOAD)可以执行自动化的编码页转换。
In a nutshell, use binary data types in your application for exchanging XML with DB2 as this avoids unnecessary code page conversion.
总而言之，在应用程序中应该使用二进制数据类型来与DB 2交换XML，因为这样做可以避免不必要的代码页转换。
There is a code page conversion to the SQL world if the value is serialized into a CHAR, VARCHAR, or CLOB type that is not FOR BIT DATA.
如果值被串行化为不是FOR BIT DATA 的CHAR、VARCHAR或CLOB类型，那么会有一个到SQL世界的代码页转换。
As mentioned before, the data movement utilities EXPORT, IMPORT, and LOAD perform an automatic code page conversion between data file and database.
正如前面提到的，数据转移实用程序EXPORT、IMPORT和LOAD在数据文件和数据库之间执行自动化的编码页转换。
For example, reducing unnecessary code page conversion is not goign to help if your system is heavily I/O bound due to an unfortunate table space configuration.
例如，如果由于表空间配置有问题，系统在I/O 方面存在瓶颈，那么减少不必要的代码页转换仍然无济于事。
BLOB serializations do not undergo any code page conversion, but they do get assigned an "encoding" attribute in the serialized header, which defaults to an encoding of UTF-8.
blob串行化不会经过任何代码页转换，但是在串行化后得到的头部中会被赋予一个“encoding ”属性，该属性默认为UTF - 8编码。
CLOB data types have an inherent code page equal to the database code page, so there is an implicit code page conversion of the reply to the SQL world during the serialization.
CLOB数据类型的代码页自然地等于数据库代码页，所以在串行化期间对SQL的回复有一个隐式的代码页转换。
While there exist a variety of code pages, Unicode has been widely used as the text encoding technique for globalization to preserve data integrity and avoid code page conversion.
虽然存在多个编码页面，但是 Unicode被广泛的作为国际化的文本编码技术来使用，来保证数据完整性和避免代码页转换。
If possible, have the client running in the same code page as the database, to avoid conversion costs on the server.
如果可能的话，让客户机与要存取的数据库使用相同的代码页，以避免在服务器上的转换代价。
For non-ASCII characters, users should ensure that the same conversion tables are used by binding and executing with the same active code page.
对于非ascii字符，用户应该确保具有相同活动代码页的绑定和执行使用相同的转换表。
In most cases, the conversion tables or definitions between the source and the target code page have not been defined.
在大多数情况下，没有定义源和目标代码页之间的转换表或定义。
For example, if 100 people visit your landing page today and 20 of those people register then you have a conversion rate of 20%.
举个例子，如果今天有100个人访问你的着陆页，其中的20个人注册了，那么你的转化率为20%。
Therefore, a higher focus on landing pages versus your home page can get you more bang for your buck in terms of conversion and user-retention opportunities.
因此，将注意力从首页更多地转移到着陆页，将会为你的网站带来更高的性价比-花很少时间得到很大收获，以及更好的留住和转化用户的机会。
The Refine page that opens after the conversion allows the user to view these files.
用户可以通过转换完成后打开的Refine页面来查看这些文件。
The HTML page waits a few moments for conversion to finish, and then directs the visitor to the generated.zip file containing the produced output files.
此html页会等待片刻直至转换完成，然后再将访客引导到包含了所生成的输出文件的.zip文件中。
Check out the source code available on the demo page to see how declarative templates do HTML conversion and some simple business logic (click the SRC links on the demo page).
演示页面上提供了源代码，看看声明性的模板如何进行HTML转换和完成一些简单的业务逻辑(单击演示页面上的src链接)。
If an user starts with the testing page and follows through to the conversion page, that is considered a success.
如果用户从测试页面开始，一直坚持到对话页面，就可以考虑这是一次成功访问。
Each particular user is counted only once, and it is considered a success only if he started from the landing page and went all the way to the conversion page.
每个特定用户只会被统计一次，只有他从入口页面进入一路走到对话页面才会被记为成功访问。
Once you are on the Profile Settings page, look for the "Conversion Goals and Funnel" section.
一旦你的配置文件设置页，找到“转换目标和程序”一节。
GWO comes with a number of.js files for tracking the users, their landing pages, their progress through the site and the reach and completion of a conversion page.
GWO带有一些。js文件，用于追踪用户、他们的入口页面、在站点中的访问过程以及到达并完成对话页面的过程。
应用推荐