From: Christoph Moench-Tegeder <cmt@burggraben.net>
To: ramsiddu007 <ramsiddu007@gmail.com>
Cc: pgsql-admin@lists.postgresql.org, pgsql-hackers@lists.postgresql.org, Monalee Bhandge <monalee.bhandge@epps-erp.com>
Subject: Re: 65279 Invisible ASCII Character
Date: Tue, 17 Jul 2018 12:12:47 +0200
Message-ID: <20180717101246.GA41457@elch.exwg.net> (raw)
In-Reply-To: <CA+zEy7-2+2tiSRq+Sv8qbhRfWY0tK3=u5zJpgYKTor2-bD_2iw@mail.gmail.com>
References: <CA+zEy7-2+2tiSRq+Sv8qbhRfWY0tK3=u5zJpgYKTor2-bD_2iw@mail.gmail.com>
## ramsiddu007 (ramsiddu007@gmail.com):
> If i remove first character it's run. That first
> character is invisible, I have checked that *ascii* value, it is *65279*.
That's not an ASCII-value, ASCII has 8 bits at most.
What you've got there is a UTF-16 Byte Order Mark: 65279 is 0xfeff
(one of the well-known constants).
I'd suggest you get your editor configured to write files without
BOM. Maybe there's a workaround via locale settings - but I have
no machine with an UTF-16 locale available. Another approach is using
recode on your files before concatenating.
This question isn't really for pgsql-hackers - I'm redirecting to -general.
Regards,
Christoph
--
Spare Space
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-admin@postgresql.org
Cc: cmt@burggraben.net, ramsiddu007@gmail.com, monalee.bhandge@epps-erp.com
Subject: Re: 65279 Invisible ASCII Character
In-Reply-To: <20180717101246.GA41457@elch.exwg.net>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox