Release 10.1A: OpenEdge Application Server:
Administration

> ## Tasks for the WebSpeed developer

> For dynamic code-page support to work, the WebSpeed developer must perform certain preliminary tasks. To summarize dynamic code-page support from the perspective of the WebSpeed developer:

> 1. The WebSpeed application should include a page that lets the user select a language or nationality from a list of preselected languages or nationalities. For each language or nationality in the list, the developer determines an appropriate code page, which must be compatible with the WebSpeed agent’s `CPINTERNAL` code page. To simplify meeting this requirement, make the agent’s `CPINTERNAL` code page `UTF-8,` which is highly compatible with OpenEdge code pages. (For more information, see `install-path``/prolang/readme`.)

> 2. The user starts the application and selects a language or nationality.

> 3. The application notes the language or nationality selected, determines the corresponding code page, and stores the MIME version of the code-page name within the Web request in a query field, a hidden-form field, or a cookie.

> Note: Any static HTML the application uses should be in the same code page selected by the user. and should refer to the same code page in the `<META>` tag’s `HTTP-EQUIV` attribute. See the first code example in the "Storing the MIME code-page name" section.

> 4. Dynamic code-page support takes over.

> Each time the agent receives information from a Web browser, it automatically converts the information from the browser’s code page to the agent’s `CPINTERNAL` code page. Similarly, just before the agent sends a Web page back to the browser, it automatically converts it from the agent’s `CPINTERNAL` code page to the browser’s code page.

Copyright © 2005 Progress Software Corporation www.progress.com Voice: (781) 280-4000 Fax: (781) 280-4095