| From: | Kris Jurka <books(at)ejurka(dot)com> |
|---|---|
| To: | Thomas Kellerer <spam_eater(at)gmx(dot)net> |
| Cc: | pgsql-jdbc(at)postgresql(dot)org |
| Subject: | Re: Small problem with special characters |
| Date: | 2006-08-20 16:42:10 |
| Message-ID: | Pine.BSO.4.63.0608201140120.30732@leary2.csoft.net |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-jdbc |
On Sun, 20 Aug 2006, Thomas Kellerer wrote:
> Well the 0xc3b6 does obviously _not_ exist in the Windows codepage (as it is
> a 2byte character). But this is a "regular" umlaut (ö) that (from a "visual"
> point of view) does exist in the codepage.
Where do you see it here?
http://www.microsoft.com/globaldev/reference/sbcs/1251.mspx
I can't find it, but if you do it will show the unicode equivalent that
you need to use to insert it.
> I'm just wondering: how would someone who is forced to use a win1251 database
> together with Java would succeed in inserting umlauts into the database?
>
You can't fit every unicode character into a single byte encoding.
Kris Jurka
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Thomas Kellerer | 2006-08-20 17:24:08 | Re: Small problem with special characters |
| Previous Message | Thomas Kellerer | 2006-08-20 16:31:00 | Re: Small problem with special characters |