Character Encoding of Web Page

Use

When you use the capture feature to define the source content of a URL iView (see Selecting the Capture Area ), the portal displays the iView's contents in the UTF-8 character encoding set only, regardless of their original encoding set. If the character encoding of the iView's target Web page is not UTF-8, the portal converts the input stream at runtime to UTF-8 before displaying it.

To enable this process at runtime, the portal must perform two passes over the entire input stream of the target Web page before the iView is displayed in the portal:

The first pass is to detect the original character encoding defined in the HTTP header of the target Web page.
The second pass converts the input stream of the Web page to UTF-8. This pass is only performed if the original character encoding of the target Web page is not UTF-8.

Each pass the portal performs takes time, which lowers the response time of an URL iView at runtime. The following properties allow you to suppress the first pass, and thus improve its runtime response time:

Always Detect Character Encoding of Web Page

This property allows you to set the status of the portal's automated character encoding detection mechanism of the target Web page defined by the URL iView.

Set the property value as follows:

Select Yes to force the portal to always detect the character encoding.
Select No to instruct the portal to use the last character encoding detected for the iView; thus improving the iView's runtime response time.

Note the following:

This property is only valid when Fetch Mode property is set to Server-side . When set to Client-side , the client's browser performs all necessary character encoding detection.
The default value of this property is No .
This last detected character encoding is saved with the iView in the PCD. If this property is set to No and the portal cannot find a last detected character encoding saved with the iView, the portal will still perform a character encoding detection; for example, when the iView is previewed or viewed for the first time.
To force the portal to redetect the character encoding when this property is set to No , set the Force Detection of Character Encoding property to Yes (see below for more details).
If an administrator changes the URL of the iView, the portal will always redetect the character encoding the next time the iView is previewed or viewed, even when this property is set to No .

Note
After changing the URL, you should immediately preview* the iView to update its last detected character encoding.

Force Detection of Character Encoding

When the Always Detect Character Encoding of Web Page property is set to No this property allows you to enforce a one-time redetection of the character encoding set used by the target Web page the next time the iView is viewed/previewed.

This property can be useful when attempting to fix a URL iView that displays garbled text. You can also use this property if you know that the character encoding of the iView's target Web page has changed.

After you change the value to Yes , save the iView and then preview* it. The value of this property is then automatically reverted to No . To use it again, set the property back to Yes .

Note the following:

The default value is No .
This property is only valid when the Fetch Mode property is set to Server-side , and the Always Detect Character Encoding of Web Page property is set to No .

* Click Preview on the toolbar in the object editor; do not use the preview capability in the Browse and Capture tabs.