Coding is and always has been set to Western (Mac OS Roman).
On Oct 20, 7:55 pm, François Schiettecatte fschietteca...@gmail.com
wrote:
Two possible options come to mind:
- your text encoding default is set to include BOM
- the encoding pulldown at the bottom left of the text window was set
Maybe it got copy-pasted in, or you duplicated the file from another one, at
this point this is speculation.
F.
On Oct 21, 2011, at 4:56 AM, Bull wrote:
Coding is and always has been set to Western (Mac OS Roman).
On Oct 20, 7:55 pm, François Schiettecatte fschietteca...@gmail.com
wrote:
At 07:22 -0400 10/21/11, François Schiettecatte wrote:
Maybe it got copy-pasted in, or you duplicated the file from another one, at
this point this is speculation.
It's possible that the behavior depends on the format in which the file is
actually saved on disk. Most of use UTf-8 which would
That sounds good, but the file with the problematic text was never
saved to disk, as the text originated in the Scratchpad.
Maybe the mystery character comes from something about the
Scratchpad's ambiguous nature: looks like a file, acts like a file,
but is not a file.
Does the Scratchpad have
After fooling around with the mystery character a little more, it does
more strange things in Terminal than I thought. In the middle of a
string it appears on the screen to be removed and the surrounding
parts catenated, but when processed (by my perl cryptogram solver) it
is still there, and is
This thread has come down to this question: How did I generate a BOM
pair of bytes while simply typing text in BBEdit?
On Oct 20, 11:49 am, Bull dur...@vt.edu wrote:
It's a BOM isn't it? Where did it come from?
--
You received this message because you are subscribed to the
BBEdit Talk
Two possible options come to mind:
- your text encoding default is set to include BOM
- the encoding pulldown at the bottom left of the text window was set to
include BOM (note that you can change the encoding of a document on the fly,
pretty useful)
François
On Oct 20, 2011, at 7:19 PM,
