Skip to Content.
Sympa Menu

freetds - [freetds] ClientCharset issues on HP/UX

freetds AT lists.ibiblio.org

Subject: FreeTDS Development Group

List archive

Chronological Thread  
  • From: Sebastien FLAESCH <sf AT 4js.com>
  • To: freetds AT lists.ibiblio.org
  • Subject: [freetds] ClientCharset issues on HP/UX
  • Date: Tue, 1 Dec 2020 17:53:13 +0100

Hello,

On HP/UX, with latest 1.3-dev version:

When setting the ODBC parameter

ClientCharset = ISO-8859-15

With a LC_ALL set to C.iso885915

And a DB with collation SQL_Latin1_General_CP1_CI_AS (CP1252)

The chars seem not to be converted properly from ISO-8859-15 to CP1252
when inserting data ...

TDSDUMP shows:

iconv.c:365:tds_iconv_open(6000000000170750, UTF-8)
iconv.c:355:Using trivial iconv
iconv.c:196:local name for ISO-8859-1 is ISO-8859-1
iconv.c:196:local name for UTF-8 is UTF-8
iconv.c:196:local name for UCS-2LE is UCS-2LE
iconv.c:196:local name for UCS-2BE is UCS-2BE
iconv.c:387:setting up conversions for client charset "UTF-8"
iconv.c:389:preparing iconv for "UTF-8" <-> "UCS-2LE" conversion
iconv.c:428:tds_iconv_open: done
iconv.c:825:setting server single-byte charset to "CP1252"
iconv.c:476:Charset 48 not supported by iconv, using "ISO-8859-1" instead

Check last line... I guess this is the reason, but why?

iconv -l gives:

iso815 (iso8859_15, iso885915, ISO8859-15) <=> ucs2 (UCS-2, UTF-16)
iso815 (iso8859_15, iso885915, ISO8859-15) <=> ucs2be (UCS-2BE, UTF-16BE)
iso815 (iso8859_15, iso885915, ISO8859-15) <=> ucs2le (UCS-2LE, UTF-16LE)
iso815 (iso8859_15, iso885915, ISO8859-15) <=> ucs4 (UCS-4, UTF-32)
iso815 (iso8859_15, iso885915, ISO8859-15) <=> ucs4be (UCS-4BE, UTF-32BE)
iso815 (iso8859_15, iso885915, ISO8859-15) <=> ucs4le (UCS-4LE, UTF-32LE)
iso815 (iso8859_15, iso885915, ISO8859-15) <=> utf8 (UTF8, UTF-8)


I have tested different aliases for ISO-8859-15 like iso815 or ISO8859-15
without success...


What is wrong here?


Seb




Archive powered by MHonArc 2.6.24.

Top of Page