Re: invalid byte sequence for encoding "UTF8": 0xab

From: Dimitri Fontaine <dfontaine(at)hi-media(dot)com>
To: "Grand\, Mark D(dot)" <mgrand(at)emory(dot)edu>
Cc: Albe Laurenz <laurenz(dot)albe(at)wien(dot)gv(dot)at>, "pgsql-general\(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org>
Subject: Re: invalid byte sequence for encoding "UTF8": 0xab
Date: 2009-06-08 11:54:12
Message-ID: 871vpvkkkb.fsf@hi-media-techno.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

"Grand, Mark D." <mgrand(at)emory(dot)edu> writes:

> It turns out that my problem was that the editor I was using (emacs)
> does not properly support utf8 encoding.

Emacs does support utf8 properly.
http://www.emacswiki.org/emacs/ChangingEncodings

It could be I'm biased because I use emacs from CVS, which is going to
be emacs23, and is as stable as emacs has always been for me.
http://emacs.orebokech.com/
http://atomized.org/wp-content/cocoa-emacs-nightly/

From within emacs, to get a ton of information about char under point,
try C-x = (one line version) or M-x describe-char (full version): <
Char: < (60, #o74, #x3c) point=1312 of 4162 (31%) <301-4163> column=66

character: < (60, #o74, #x3c)
preferred charset: ascii (ASCII (ISO646 IRV))
code point: 0x3C
syntax: . which means: punctuation
category: .:Base, a:ASCII, l:Latin, r:Roman
buffer code: #x3C
file code: #x3C (encoded by coding system utf-8-emacs)
display: by this font (glyph code)
xft:-bitstream-Bitstream Vera Sans Mono-normal-normal-normal-*-16-*-*-*-m-0-iso10646-1 (#x1F)

But I guess we're off topic now.

HTH, regards,
--
dim

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Martin Gainty 2009-06-08 12:18:36 Re: PL/PGSQL
Previous Message Grzegorz Jaśkiewicz 2009-06-08 11:52:54 Re: Foreign Key Unique Constraint can be dropped