Hi Julian
I've never used utf-8 I'm afraid. UTF-8 is a single byte character set
but... it used 2 bytes when handling Arabic AFAIK. Excel supports
standard unicode UTF-16.
from
http://czyborra.com/utf/#UTF-8
<<UTF-8 consumes two bytes for all non-Latin (Greek, Cyrillic, Arabic,
etc.) letters that have traditionally been stored in one byte and three
bytes for all symbols, syllabics and ideographs that have traditionally
only needed a double byte. This can be considered a waste of space and
bandwidth which is even tripled when the 8bit form is MIME-encoded as
quoted-printable ("=C3=A4" is 6 bytes for the one character ä). SCSU
aims to solve the compression problem.>>
Sounds a bit strange to me but it makes sense to use 2 bytes - you just
can't get all of the Arabic char set easily into 1 byte. ISO-8859-6
tries but misses out some less commonly used letters/glyphs.
You get char 63 - which in hex is 3F - I suspect this might be the
leading byte in a two byte character.
My questions:
(a) Where is the file from / how is it created?
(b) Are you sure the Arabic is in there correctly in the first place?
(Try opening it up in IE to check or even in notepad.)
If you find it *is* in there correctly feel free to send me a copy of
the file and I'll take a look at it. Send it to the name excelvba with a
domain name of garhoo and put a com at the end of it.
HTH,
Gareth