On Wed, 6 Mar 2002, Terje Bless wrote:
> Jason E. Stewart <[EMAIL PROTECTED]> wrote:
>
> >It really does seem that the transcoder is screwed on BSD systems.
>
> The transcoder wouldn't happen to be using libiconv (iconv_open())
> internally? There's been some problems with libiconv on BSDs lately; in
> particular, it looks as if the libiconv included with Mac OS X is 1)
> limited and 2) comes without header files.
I am almost certain that BSD uses it's internal iconv. Xerces-C 1.6
runConfigure has a flag to set that IIRC.
BSD has some truely whack stuff goin' on with that (iconv). it has been a
real hair puller now that more apps are taking i18n into account.
one thing that i stumbled onto whilst googling about trying to solve some
iconv errors was that some FreeBSD dists included gnu inconv as a pkg
called 'giconv. but i think that only 4.3 shipped with it. i couldnt find
it in 4.5, but i havent had time to look too closely.
i wound up using giconv and it actually worked in the app that i was
trying to compile.
i think that FreeBSD's iconv stuff has lagged because most of the good
work is probably GPL and that is strictly verboten in a FreeBSD OS
install.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
