[caret question]

[GDHough]

On Sunday 04 January 2004 14:25, Marcus Brubaker wrote:
> Basically, all of those programs are generally designed to deal with
> standard ASCII text.  When they run in to undisplayable characters (such
> as 0x7F) how they get shown is up to the program.  Things like gedit and
> kmail will give some kind of icon which represents an undisplayable
> character.  vi and pico, being traditionally text based, show it in a
> different manner.
>
So this is normally how unicode is handled by different applications? 
Unpredictably?
It peaked my curiosity when I was studying some SHELLCODE x86 unicode NOOP 
alerts from snort. The same packets viewed with ACID (using Galeon) show the 
caret_questionmark as a blank. About all I learned googleing was there is a 
strange language called INTERCAL...

If five different text viewers display five different things, which one is 
telling the truth? My inclination is to stick with vi. But then I am still 
wondering if since this causes unpredictable behavior in x86, is it something 
to be concerned with?

Thanks,
farmer6re9

> On Sun, 2004-01-04 at 14:09, GDHough wrote:
> > I was curious to know if there is a simple explanation for the <caret
> > questionmark> string (7F) in the way it is displayed in various text
> > editors.
> >
> > caret_questionmark in:
> >
> > 1) gedit displays what looks like a tiny floppy icon
> > 2) kmail shows a box
> > 3) pico has one infinite line of caret's but only reads three characters
> > 4) vi shows the caret and questionmark as though a link (blue)
> >
> > Perplexed,
> > farmer6re9

-- 
Eating Crow is better with MyCrowSauce

--
The Toronto Linux Users Group.      Meetings: http://tlug.ss.org
TLUG requests: Linux topics, No HTML, wrap text below 80 columns
How to UNSUBSCRIBE: http://tlug.ss.org/subscribe.shtml