On Thu, Sep 19, 2002 at 04:02:07AM -0400, Michael B. Allen wrote: > Not if your importing/exporting. But you might very well use it internally > and if someone want'd to run that app on Windows too that's the kind of > thing I would think libiconv should be good for so I was surprised I > couldn't build it with full support.
No, I'm referring to passing "wchar_t" as an iconv parameter; when was this added to iconv? I thought it was relatively recently. > > (It's a bit of a hack, too, but a bearable one.) > > Are you talking about Bruno's implementation? I have wondered if wchar_t > could just be treated like any other encoding. It may not have a rigid > definition but it wasn't clear to my why those wchar_t clauses in the main > convertion loops really had to be there. The iconv interface is for char*'s; passing wchar_t* through it is a hack of forced casting, and you have to deal with adjusting buffer sizes for byte counts. It's easily fixed with wrappers, though. > Yikes! You just left my sphere of knowledge :-) That was to anyone on the list who can answer it. :) -- Glenn Maynard -- Linux-UTF8: i18n of Linux on all levels Archive: http://mail.nl.linux.org/linux-utf8/
