Multibyte encoding vs. SQL_ASCII and European languages - Mailing list pgsql-general

From Frank Joerdens
Subject Multibyte encoding vs. SQL_ASCII and European languages
Date
Msg-id 20020129130345.A14393@superfly.archi-me-des.de
Whole thread Raw
Responses Re: Multibyte encoding vs. SQL_ASCII and European
List pgsql-general
Call me stupid - but I am trying to understand what multibyte encoding
(aka Latin1) would buy me with English/German/French etc. languages (the
app I am currently slapping together will be mostly used by people
writing in German). SQL_ASCII seems to work just fine with German
umlauts and other funny characters that I am stuffing into, or pulling
out of the database (that is, after having survived the nightmare of
importing Filemaker data so as to having umlauts etc. correctly
represented). And what exactly does the server vs. client encoding do?

Thanks, Frank

pgsql-general by date:

Previous
From: "Steve Boyle \(Roselink\)"
Date:
Subject: Fw: job scheduling
Next
From: Frank Schafer
Date:
Subject: Re: Multibyte encoding vs. SQL_ASCII and European