Re: invalid byte sequence for encoding "UTF8": 0xab
От | Dimitri Fontaine |
---|---|
Тема | Re: invalid byte sequence for encoding "UTF8": 0xab |
Дата | |
Msg-id | 871vpvkkkb.fsf@hi-media-techno.com обсуждение исходный текст |
Ответ на | Re: invalid byte sequence for encoding "UTF8": 0xab ("Grand, Mark D." <mgrand@emory.edu>) |
Список | pgsql-general |
"Grand, Mark D." <mgrand@emory.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
В списке pgsql-general по дате отправления: