[Mono-dev] Character encoding issues on Linux
atsushi at ximian.com
Thu May 17 10:32:17 EDT 2007
No, it depends on I18N module (mcs/class/I18N.*.dll). It rather sounds
like we don't have supprot for CP1256 (I don't know which language
this encoding is for).
I'll take a look at it when I have time (I already have somewhat
blocking Japanese encoding issue but haven't had enough time to fix
it right now...)
Jeffrey Stedfast wrote:
> As far as I know, Mono depends on libiconv (as either a standalone
> package or built into glibc - which is the case on Linux systems afaik)
> for charset conversion.
> The charset names used by libiconv however, may be named differently -
> so I'm sure Mono has a table to try and do the proper mapping (I've had
> to write tables like this in the past working on other projects).
> I think CodePage 1256 probably maps to Windows-CP1256, which on my
> particular Linux system w/ whatever libiconv I have could be mapped to
> either CP1256 or WINDOWS-1256
> (iconv --list will give you a listing of all supported charset names)
> Perhaps I'll take a look later and see if I can't see something obvious
> (I haven't ever worked on the runtime so I dunno for sure how it does
> charset conversion, I could be way off)
> On Thu, 2007-05-17 at 11:08 +0100, Martin Brown wrote:
>> We've got an application running on Mono on Linux. For the most part it
>> runs very well; however every so often we get an exception:
>> "CodePage 1256 not supported"
>> The code page number varies depending on the encoding present in the
>> >From the MS page here
>> it looks like the MS .Net implementation relies on the OS for character encoding services. Is this the case for Mono too? If so, what needs to be available on Linux to perform this encoding?
>> Filtered by 3BClean from http://www.3bview.com
>> Mono-devel-list mailing list
>> Mono-devel-list at lists.ximian.com
> Mono-devel-list mailing list
> Mono-devel-list at lists.ximian.com
More information about the Mono-devel-list