Kbase P109408: Does WebSpeed work with the Unicode UTF-8 client?
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
9/30/2005 |
|
Status: Unverified
GOAL:
How does WebSpeed work with the Unicode UTF-8 client?
GOAL:
Will WebSpeed work with the UTF-8?
GOAL:
How to enter UTF-8 extended characters with WebSpeed?
FACT(s) (Environment):
Progress 9.1D
Progress 9.1E
OpenEdge 10.x
FIX:
WebSpeed will work with UTF-8, and it is possible to paste Unicode characters from the Windows Character Map and from Unicode Word documents into a Web browser and then store them into a UTF-8 database.
However, there are a few things that need to be considered when doing this:
1. The Data base should use the code page UTF-8.
2. The WebSpeed broker should be started using the parameters -cpinternal and -cpstream set to UTF-8.
3. The encoding of the Web browser should be set to Unicode (UTF-8). To see this value, right mouse click on the Web browser and choose "Encoding" from the popup menu.
The important point is to ensure that the web browser is set to use the UTF-8 code page, point 3 from above. Otherwise the characters will not display correctly after they are pasted into the Web browser. After this, saving the data into the database is done without conversion because both the WebSpeed broker and database are using the UTF-8 code page.
To view the entered data from a GUI client, the client must be started using the Unicode client in OpenEdge 10, or by using a compatible code page in version 9. So for example, if Russian data is entered via a Web browser as described above, this data can be displayed successfully on a OpenEdge 10 UTF-8 client (-cpinternal and -cpstream set to UTF-8). Alternatively if the same OpenEdge client (or a V9 client) is started using the locale Russian Cyrillic code page 1251 (-cpinternal and -cpstream set to 1251, cpcoll Russian) then the data will also be displayed correctly.
Failure to start the client using the methods described above (i.e. using another, possibly incompatible code page) will risk corrupting the data.