[Mono-dev] Character encoding issues on Linux -> Iconv usage on windows.

[Michael Jerris]

I have been looking at the iconv usage on windows (specifically in
reference to the need to implement g_convert in eglib.  If I trace the
calls right, g_convert is only used in g_locale_to_utf8 and
g_locale_from_utf8, which is in turn only used in,
mono_unicode_to_external and mono_unicode_from_external
(mono/utils/strenc.c), which in turn is only used in
ves_icall_System_Security_Principal_WindowsIdentity_GetUserToken and
ves_icall_System_Security_Principal_WindowsPrincipal_IsMemberOfGroupName
and ProtectUser and Protect (all from mono/metadata/security.c) and all
of which are explicitly ifdefed off for windows, and in
mono_runtime_run_main (mono/metadata/object.c) which actually does use
mono_utf8_from_external.  

So, my question is.  On windows, is there a way that we can otherwise
implement what is needed in mono_runtime_run_main for
mono_utf8_from_external to use the other character set conversion code
so that we can remove the libiconv dependency on windows?

Mike


> -----Original Message-----
> From: mono-devel-list-bounces at lists.ximian.com
[mailto:mono-devel-list-
> bounces at lists.ximian.com] On Behalf Of Miguel de Icaza
> Sent: Thursday, May 17, 2007 11:07 AM
> To: Jeffrey Stedfast
> Cc: mono-devel-list at lists.ximian.com
> Subject: Re: [Mono-dev] Character encoding issues on Linux
> 
> Hello,
> 
> > 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.
> 
> Mono only uses iconv for filename mapping, for all other we use our
own
> character set conversion code (see class/I18N).
> 
> Miguel
> _______________________________________________
> Mono-devel-list mailing list
> Mono-devel-list at lists.ximian.com
> http://lists.ximian.com/mailman/listinfo/mono-devel-list