Are you really saying that you try to view the output of conversion with this table as if it were UTF-8 ?
If you simply break each output in two: 0xA3 --> U+061F --> 0x06 0x1F ARABIC QUESTION MARK then the result is _not_ UTF-8, it is UTF-16 There is not just one "Unicode Codepage", there are different encoding schemes. > > Dear Sir, > > > > We are using a character set conversion table for converting > > NCR 96 codepage to Unicode Codepage. However when we try to > > view this converted contents on the internet explorer with > > Unicode (UTF-8) encoding, we are getting wrong output than > > what we expected. some parts of the codepage conversion table > > is given below. > > > > > > 0xA0 <NOT USED> > > 0xA1 <NOT USED> > > 0xA2 <NOT USED> > > 0xA3 0x061F
