At 6:21 pm -0500 11/1/04, Vic Norton wrote:
P.S. I tried your script below. I haven't the slightest idea what
the output means. As I said, a real web bullet is •.
A bullet can be written in valid html code in the real world in half
a dozen different ways, and that would not be the preferred one
Hi John,
What I meant and sent was what Sherm Pedley called a bullet, namely
what is produced on a Mac when you type option-8. The unicode
character is \x{2022}. On web pages it is •.
When I put "bullet • on a web page, open the page in
Safari, copy the "bullet" from the page, and paste it int
At 1:52 pm -0500 11/1/04, Vic Norton wrote:
# file0.pl - The data in "file0.pl" is a real bullet,
#namely A5. But the script "file0.pl" can't
#find it when run from BBEdit.
Vic, before I spend time testing this, what do
you mean by "real bullet" namely A5.
At 13:52 -0500 1/11/04, Vic Norton wrote:
>Now I seem to have resolved the problem--sort of. I believe it's a bug in BBEdit.
I suspect BareBones will call it a feature.
The unwillingness of BBEdit to work on a file without doing things like changing all
of the line ends has been a pain. It is im
Hi John and Sherm,
Thanks for the info. I have tried your
experiments and found them very interesting. But,
in all of your examples, perl and HexEdit see
exactly the same thing; whereas, in my problem,
perl and HexEdit were seeing things differently.
Perl seemed to have double vision.
Now I
At 9:26 pm -0500 10/1/04, Vic Norton wrote:
I'm sorry, John. I was talking figuratively. I didn't mean real bullets.
FIguratively or no, you were right on target with
your choice. The bullet is a character in the
'macintosh' character set (referred to wrongly by
the Perl people "MacRoman") whi
On Jan 10, 2004, at 9:26 PM, Vic Norton wrote:
How come Perl sees "C2 A0" whenever HexEdit sees "CA" and visa versa?
I don't care what kind of characters we are talking here. To
paraphrase Gertrude Stein, "a byte is a byte is a byte." At least
that's what I thought until now.
Like John said - t
I'm sorry, John. I was talking figuratively. I didn't mean real bullets.
How come Perl sees "C2 A0" whenever HexEdit sees "CA" and visa versa?
I don't care what kind of characters we are talking here. To
paraphrase Gertrude Stein, "a byte is a byte is a byte." At least
that's what I thought unt
At 11:22 am -0500 10/1/04, Vic Norton wrote:
What is going on here? HexEdit sees one byte for each bullet and perl
sees two. I thought hex stuff was unambiguous, but, as a mathematician,
I am pretty certain that 1 is not equal to 2.
Perl talks UTF-8. The bullet in utf-8 is chr (8226) "\x{2022}"
Now and then I copy data from the web and paste it into a perl script
after "__END__" or "__DATA__". I plan to take the data apart with perl.
The file is generally a BBEdit text file with unix line feeds.
Sometimes there are bullets in the data. According to HexEdit these
bullets are "\xca" charact
10 matches
Mail list logo
