Re: A bug in cut?

[Munzir Taha <munzirtaha at newhorizons dot com dot sa>]

On Saturday 22 May 2004 09:46 am, Behdad Esfahbod wrote:
> On Sat, 22 May 2004, Munzir Taha wrote:
> > hexdump gives:
> > 0000000 a0d9 d90a 0aa1 a2d9 d90a 0aa3 a4d9 000a
> > 000000f
> >
> > Can you explain to me how to relate these numbers to
> > 0660	ARABIC-INDIC DIGIT ZERO
> > 0661	ARABIC-INDIC DIGIT ONE
> > 0662	ARABIC-INDIC DIGIT TWO
> > 0663	ARABIC-INDIC DIGIT THREE
> > 0664	ARABIC-INDIC DIGIT FOUR
>
> Have a look at /usr/share/i18n/charmaps/UTF-8.gz
> It's really simple.  For example, \xd9\xa0 is 0660 and so on.
> You better read the UTF-8 RFC once, it's lots of fun.

Thanks for the info. Now, I can understand how 660=d9a0 but hexdump gives it 
as a0d9. Has this any thing to do with big endianness







-- 
Munzir Taha  PGP Key available
gpg --recv-keys --keyserver www.mandrakesecure.net F0671821

Telecommunications and Electronics Engineer
Linux Registered User #279362 at http://counter.li.org
Mandrake Club member
Maintainer of Mandrake Arabization Project Status (MAPS)
http://www.arabeyes.org/download/documents/distros/mdkarabicsupport-en/
CIW Designer, ICDL, MOUS
New Horizons CLC
Riyadh, SA