Maurice Lombardi wrote:
Frank Heckenbach wrote:
Actually I've just added an autoconf check for -lintl to link it automatically from intl.pas when present. Should I do the same for -liconv? It will probably not be needed on most platforms, but shouldn't hurt, either.
Would be useful for djgpp at least.
Or should I do it conditionally on
__OS_DOS__?
No, mingw32 defines __OS_DOS__, presumably for line ends and may be drive letters,
Yes, and so do Cygwin and EMX.
but being windows it uses (nearly) ISO-8859-1.
Yeah, nearly but not completely the same, so maybe they also need a (slight) conversion.
Anyway, checking for and linking -liconv does not mean that any conversion will be done automatically. It only means that -liconv will be "offered" to the linker in case -lintl actually uses any of its routines. So I think it's still safe to do it on all __OS_DOS__ systems, isn't it?
Do you suppose that gpc/gcc should be configured with --enable-nls ? I have not done it in the binaries uploaded, and when I tried, it triggers a bug, djgpp-related, on stage 1: I suppose that nobody has ever tried to compile gcc-2.95.3 natively for djgpp with intl support.
I have no idea. But if anything, this will only influence the compiler itself (and AFAIK there are no non-English messages for GPC -- don't know about GCC, so it would seem pointless). The RTS doesn't use this setting (it should be up to the configuration of a GPC compiled program whether or not to include NLS, but that's up to the author and/or user of the Pascal program then).
Frank