Progress
Internationalization Guide
Guidelines For Using Unicode
When you use Unicode in Progress applications, the following restrictions, cautions, and suggestions apply:
- To encode a single character consisting of a base character below and a diacritic above, such as the Spanish ñ, data must use the composed character—that is, the single encoding that represents the character and the diacritic. If the data encodes the base character and the diacritic separately, Progress does not interpret these as a single character consisting of the base character below and the diacritic above.
NOTE: The sort logic might use the COLLATE option of the FOR statement, the OPEN QUERY statement, and the PRESELECT phrase. For more information on this 4GL element, see the Progress Language Reference .- Progress sorts UTF–8 data in binary order. If an application requires sorting in a different order, the application must provide the sort logic itself.
- Progress supports code page conversion to and from UTF–8 the same way it supports code page conversion to and from other code pages. For more information on code page conversion, see "Understanding Code Pages," and Understanding Character Processing Tables."
- When an existing database is converted to UTF–8, the amount of storage required by each non-ASCII character increases. Roughly, each non-ASCII Latin-alphabet character converted to UTF–8 tends to require two bytes, while each double-byte Chinese, Japanese, or Korean character converted to UTF–8 tends to require three bytes.
- To display and print Unicode data, consider using a Unicode font. They are available commercially.
Copyright © 2004 Progress Software Corporation www.progress.com Voice: (781) 280-4000 Fax: (781) 280-4095 |