codepage
- Thread starter sureshp
- Start date
taqvia
Member
FIND FIRST _db NO-LOCK.
DISPLAY _db-xl-name FORMAT "X(15)" LABEL "Db codepage"
_db-coll-name FORMAT "X(15)" LABEL "Db collation"
SESSION:CPINTERNAL FORMAT "X(15)" LABEL "4GL Codepage"
SESSION:CPCOLL FORMAT "X(15)" LABEL "4GL Collation"
SESSION:CPSTREAM FORMAT "X(15)" LABEL "4GL Stream"
WITH 1 COL.
Arshad
DISPLAY _db-xl-name FORMAT "X(15)" LABEL "Db codepage"
_db-coll-name FORMAT "X(15)" LABEL "Db collation"
SESSION:CPINTERNAL FORMAT "X(15)" LABEL "4GL Codepage"
SESSION:CPCOLL FORMAT "X(15)" LABEL "4GL Collation"
SESSION:CPSTREAM FORMAT "X(15)" LABEL "4GL Stream"
WITH 1 COL.
Arshad
taqvia
Member
Why do you want to change the codepage . Are their any compatibilty issues where characters are not getting displayed correctly or some abnormal behaviour. As per my understanding a change in codpepage will require compilation.
INTERNAL CODEPAGE AND COLLATION
===============================
The internal codepage is used for all 4GL comparisions and
sorting which does not use a database index. This codepage and
collation is independent from the database and can be different.
GUI input/output uses internal codepage and cannot be converted.
If in any doubt, override the defaults by explicitly specifying
the -cpinternal and -cpcoll parameters.
Check for hard-coding certain codepage values in comparisions
or assuming that the comparisions are always in ASCII order..
A common mistake is to assume that CHR(255) > "Z". This works
with ibm850 codepage but in iso8859-1 CHR(255) is ydiaeresis
which (in "basic" collation) sorts like y. In general the ASCII
value of a character does not tell you anything about the
collating weight of that character. Collating weights are
language-dependent and for one codepage there are several
collating sequences.
INTERNAL CODEPAGE AND COLLATION
===============================
The internal codepage is used for all 4GL comparisions and
sorting which does not use a database index. This codepage and
collation is independent from the database and can be different.
GUI input/output uses internal codepage and cannot be converted.
If in any doubt, override the defaults by explicitly specifying
the -cpinternal and -cpcoll parameters.
Check for hard-coding certain codepage values in comparisions
or assuming that the comparisions are always in ASCII order..
A common mistake is to assume that CHR(255) > "Z". This works
with ibm850 codepage but in iso8859-1 CHR(255) is ydiaeresis
which (in "basic" collation) sorts like y. In general the ASCII
value of a character does not tell you anything about the
collating weight of that character. Collating weights are
language-dependent and for one codepage there are several
collating sequences.
look into the convchar convert and convchar charscan commands for proutil.
More information in i18n guide: http://www.psdn.com/library/servlet/KbServlet/download/4803-102-14179/dvint.pdf
From which codepage to which codepage do you want to convert?
Casper.