From: | Dan Scott <dan(at)coffeecode(dot)net> |
---|---|
To: | David Gould <daveg(at)sonic(dot)net> |
Cc: | Josh Kupershmidt <schmiddy(at)gmail(dot)com>, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: Strange errors from 9.2.1 and 9.2.2 (I hope I'm missing something obvious) |
Date: | 2012-12-17 06:48:40 |
Message-ID: | CAAY5AM0QDF7ndBHOSiNYYK55+GBaOc2AhpOfDn62JvKw7WM8sg@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Dec 11, 2012 9:28 PM, "David Gould" <daveg(at)sonic(dot)net> wrote:
>
> Thank you. I got the example via cut and paste from email and pasted it
> into psql on different hosts. od tells me it ends each line with:
>
> \n followed by 0xC2 0xA0 and then normal spaces. The C2A0 thing is
> apparently NO-BREAK SPACE. Invisible, silent, odorless but still deadly.
>
> Which will teach me not to accept text files from the sort of people who
> write code in Word I guess.
It's not just Word... I was bitten by this last week by a WYSIWYG HTML
widget I was using to write some documentation. When I copied the examples
I had created out of said environment during a final technical accuracy
pass and they failed to run in psql, I panicked for a few minutes.
I eventually determined that, rather than just wrapping my code in <pre>
tags, the widget had created entities that were faithfully converted
into Unicode non-breaking spaces in the psql input.
From | Date | Subject | |
---|---|---|---|
Next Message | Heikki Linnakangas | 2012-12-17 08:30:18 | Re: XLByte* usage |
Previous Message | Noah Misch | 2012-12-17 02:45:20 | Re: Unresolved error 0xC0000409 on Windows Server |