After investigating a bit more, it turns out that MSVC 7 compiler
chokes on optimizing some parts of the code (at least the /Og option
seems to produce invalid code). But even in non-optimized, debug-mode
there are still problems with the unicode support.
Especially, the following chars : $(D+1+"+2(B are reported to be of
iso-latin8859-14 (where -15 would have make gnus happier)
and the c-cedilla : $(D+.(B is reported to be of ipa charset.
Help is needed there (but I'm still investigating)
--
Fabrice Popineau
------------------------
e-mail: Fabrice.Popineau(a)supelec.fr | The difference between theory
voice-mail: +33 (0) 387764715 | and practice, is that
surface-mail: Supelec, 2 rue E. Belin, | theoretically,
F-57070 Metz | there is no difference !
Show replies by date
Well, this is a followup to my own post. The behaviour of Microsoft
compiler VC 7 (aka the one with Visual Studio .Net) is a bit strange
on the mule things. I got various results with different compilation
options. I manage to get the right behaviour by disabling several
compilation options (basically : compile with the debug options). Not
very nice, because it is a bit less responsive.
Sorry for the noise, but it might worth knowing it.
--
Fabrice