| From: | John Gage <jsmgage(at)numericable(dot)fr> |
|---|---|
| To: | Richard Huxton <dev(at)archonet(dot)com> |
| Cc: | Scott Mead <scott(dot)lists(at)enterprisedb(dot)com>, Postgres General Postgres General <pgsql-general(at)postgresql(dot)org>, pgAdmin Support List <pgadmin-support(at)postgresql(dot)org> |
| Subject: | Byte order mark added by (the envelope please...) pgAdmin3 !! |
| Date: | 2010-04-22 09:10:18 |
| Message-ID: | 1293561A-75E5-412A-9209-CEE70C1CEEAC@numericable.fr |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgadmin-support pgsql-general |
Well, well, well. Guess who the culprit is...
I edited the file both in Vim and in pgAdmin3 (1.10.2, Mar 9 2010, rev
8217), and the BOM shows up after saving the file with pgAdmin3.
I don't know if pgAdmin3 wants to keep this feature...
Thank everyone again for the excellent help.
John
On Apr 22, 2010, at 9:37 AM, Richard Huxton wrote:
>
> http://en.wikipedia.org/wiki/Byte_order_mark
>
> Tends to get added if you go through a Windows system. Useless for
> utf-8 afaik. Confuse the hell out of you because various tools parse
> and hide them then you pipe the file to a script and everything
> falls over.
>
> Bunch of scripts available here to remove them:
> http://www.xs4all.nl/~mechiel/projects/bomstrip/
>
> --
> Richard Huxton
> Archonet Ltd
>
> --
> Sent via pgsql-general mailing list (pgsql-general(at)postgresql(dot)org)
> To make changes to your subscription:
> http://www.postgresql.org/mailpref/pgsql-general
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Vikram A | 2010-04-22 09:21:48 | Replication in postgresql |
| Previous Message | John Gage | 2010-04-22 07:48:48 | Re: Identical command-line command will not work with \i metacommand and filename |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Wappler, Robert | 2010-04-22 09:25:12 | Re: [GENERAL] Byte order mark added by (the envelope please...) pgAdmin3 !! |
| Previous Message | Jignesh Shah | 2010-04-22 08:46:05 | Re: Syntax error in trigger |