Re: Back-end character set remapping

In article <CGA87z.8n2_at_copley.csc.mckinsey.com> claman_at_copley.csc.mckinsey.com (Larry Claman) writes:

   We are now in the process of porting our applications to the    Macintosh. The problem is that we have extended characters stored in    our data, and that the Macintosh uses a different character mapping    for extended characters than the Windows ANSI character set. Thus,    any data retrieved on the Mac that contains extended characters is    displayed incorrectly. Omnis 7 allows you to remap characters based    on custom remapping tables, so we are able to handle this in our own    applications; however the characters are still mapped incorrectly when    using any other tools.

   I'm hoping it would be possible to remap characters at the driver level.    Would ODBC / Oracle*Glue / SQL*NET 2.0 be able to do this? Or, is there    a setting in SQL*NET 1.5 that would do this for me?

Oracle7 does this. when you create a database, you declare a character encoding for the database. character encoding conversion is done between that encoding and the one declared by the client in the NLS_LANG environment variable.

   -Larry Claman
    claman_at_copley.csc.mckinsey.com

--
This opinion will self destruct in 5 seconds.
danny vanderryn--dvanderr_at_oracle.com   || Take my advice ---
{uunet,hplabs,apple}!oracle!dvanderr   || *I'm* certainly not using it.
(415) 506-3142                         ||