This is the current setup:

We have one large iseries partition where many companies in different countries across Europe share one common code base (i.e. the same program library for all).

Each country has its own database library.

We are now implementing the package for a Bulgarian company. This is the first company that uses a Cyrillic character set with our package. Until now all languages implemented have been using a character set in the "latin-1" family.

Right now we are trying hard to figure out what we need to install to get this working.

While testing with client access sessions and users that we have set up with CCSID 1025 we have found that we can not see or key any Cyrillic's that way. I assume that we may need a specially adapted version of client access to get this working. Can anyone verify that?

What with Windows? Do we need a Bulgarian version of Windows as well?

We create all database files with CCSID 37 and control the rest by user profile and device attributes.

Any other ideas on how to set this up?

(Aside for a full-blown unicode conversion. We ARE working on that as well but there is simply not enough time to get that project ready in just a couple of months.)


Med vänlig hälsning / Best regards
Åke Olsson

Pdb DataSystem AB
Box 433 SE 551 16 Jönköping Sweden visit: Brunnsgatan 11
phone: +46 (0)36 342976 mobile: +46 (0)705 482976 fax: +46 (0)36 34 29 29
ake.olsson@xxxxxx www.pdb.se





This e-mail and any attachments may contain confidential and
privileged information. If you are not the intended recipient,
please notify the sender immediately by return e-mail, delete this
e-mail and destroy any copies. Any dissemination or use of this
information by a person other than the intended recipient is
unauthorized and may be illegal.

As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.