From: | Christoph Moench-Tegeder <cmt(at)burggraben(dot)net> |
---|---|
To: | ramsiddu007 <ramsiddu007(at)gmail(dot)com> |
Cc: | pgsql-admin(at)lists(dot)postgresql(dot)org, pgsql-hackers(at)lists(dot)postgresql(dot)org, Monalee Bhandge <monalee(dot)bhandge(at)epps-erp(dot)com> |
Subject: | Re: 65279 Invisible ASCII Character |
Date: | 2018-07-17 10:12:47 |
Message-ID: | 20180717101246.GA41457@elch.exwg.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin pgsql-general pgsql-hackers |
## ramsiddu007 (ramsiddu007(at)gmail(dot)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
From | Date | Subject | |
---|---|---|---|
Next Message | ramsiddu007 | 2018-07-17 10:25:11 | Re: 65279 Invisible ASCII Character |
Previous Message | ramsiddu007 | 2018-07-17 09:30:43 | 65279 Invisible ASCII Character |
From | Date | Subject | |
---|---|---|---|
Next Message | ramsiddu007 | 2018-07-17 10:25:11 | Re: 65279 Invisible ASCII Character |
Previous Message | ramsiddu007 | 2018-07-17 09:30:43 | 65279 Invisible ASCII Character |
From | Date | Subject | |
---|---|---|---|
Next Message | ramsiddu007 | 2018-07-17 10:25:11 | Re: 65279 Invisible ASCII Character |
Previous Message | Kyotaro HORIGUCHI | 2018-07-17 09:58:48 | Re: [HACKERS] Restricting maximum keep segments by repslots |