Install multi language database environment

[progress_in]

Hi,

We have "PROGRESS Version 9.1E04" installed and English is selected as default lang. Also other language installed and reflected in $DLC/prolang directory.

The databases are created using the startup.pf as below

-cpinternal ISO8859-1
-cpstream ISO8859-1
-cpcoll Basic
-cpcase Basic
#-d dmy
-d mdy
-numsep 44
-numdec 46

Now for the new site we are looking to install Russian language (code page - 1251) but its not working.

What we actually want that our database remains in English lang only, whereas we can access that using different settigs for English and Russian lang.

I updated the convmap.dat with russian.dat and tried using below command
"proutil -C codepage-compiler convmap.dat $DLC/convmap.cp" to update the convmap.cp.

However while connecting the database with below, we are getting errors
$DLC/bin/_progres -pf test.pf -cpinternal 1251 -cpstream 1251 -cpcoll Russian -d mdy




+------------------------------------ Error ------------------------------------+
¦ Code page conversion table for 1251 to ISO8859-1 was not found in convmap.cp. ¦
¦ (6063) ¦
¦ The server's code page is ISO8859-1 and the client's code page is 1251. ¦
¦ (1665) ¦
¦ The connection has been established, but no data conversion will take place. ¦
¦ (1667) ¦
¦ Code page conversion table for ISO8859-1 to 1251 was not found in ¦
¦ convmap.cp. (6063) ¦
¦ The code page of database testprod is iso8859-1 and -cpinternal is 1251. ¦
¦ (4677) ¦
¦ The tables needed to do conversion for the database were not found in ¦
¦ convmap.cp. (1564) ¦
¦ ¦
¦ ----------------------------------------------------------------------------- ¦
¦ <OK> ¦
+-------------------------------------------------------------------------------+

Thanks,

 

[RealHeavyDude]

You can not do that. Full Stop.

The reason for that is that the two code pages (English vs. Russian) are not compatible and therefore Progress can't do the automatic conversion for you. The error message is telling you that Progress can't find a conversion. AFAIK the code page compiler can't help here as it is purposed for a completely different thing. I've never added a conversion that I've rolled to the convmap.dat myself ...

In you scenario the only supported way is to have the database using a code page that supports both client code pages (English vs. Russian) - which would be UTF-8. You just can't have your database using iso8869-1 and connect with a client that uses 1251 without losing or misinterpreting data.

Bottom Line: You need to convert your database to UTF-8 in order to succeed.

Heavy Regards, RealHeavyDude.