MIDRANGE dot COM Mailing List Archive



Home » MIDRANGE-L » June 2008

RE: Support Cyrillic



fixed


Crux is that this has been tested from a "standard" version of client Access. On a session set up as Bulgarian there are no "blobs" but lots of funny accented characters. None of which look Cyrillic.

I guess that the database could be changed to 1025. This has to be kept in mind for release upgrades since this would be specific for their database.


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
 

-----Original Message-----
date: Wed, 18 Jun 2008 19:38:35 -0700 (PDT)
from: Bruce Vining <bvining@xxxxxxxxxxxxxxx>
subject: RE: Support Cyrillic

Is the user seeing "blobs" then when attempting to display Cyrillic data from the i? And seeing Cyrillic characters when they key them in on the screen, but again "blobs" after they hit Enter (assuming the display format is refreshed by the application)? The "blob" would typically be a reverse image rectangle, which is really a x'3F' (substitution character).

What flexibility do you have in assigning a CCSID of 1025 to their specific database files? Is there a need to consolidate the Latin-1 and Cyrillic character data in one database for reporting purposes? Or are these pretty much standalone entities?

Bruce Vining

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.





Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2014 by MIDRANGE dot 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 here. If you have questions about this, please contact