hi, testing my plugin on windows (XP) i came across another problem. [apart from finding out that system() just silently ignores the pipe symbol on windows and must be replaced by shell()...] it's an encoding issue.
basically, i use a shell() call to process some text, R(KWard) takes the returned results and looks up some describing information which is added to the results and all of it then displayed in the results tab. i didn't encounter encoding problems on linux, but on windows both the returned processed text as well as the looked up descriptions (happening inside of R/RKWard) show malfomed special characters like umlauts. changing the encoding in RKWard doesn't help. however, if i invoke the very commands of the shell() call directly in cmd.exe, even UTF-8 encoded text files are properly processed and results displayed as i would expect. i'm not an windows expert, but can this somehow be related to the set encoding of the shell RKWard gets launched from in the first place? i assume the descriptions mentioned above were UTF-8 encoded at package build time. just let me know if you have an idea what i could try to nail this one down. viele grüße :: m.eik -- dipl. psych. meik michalke abt. f"ur diagnostik und differentielle psychologie institut f"ur experimentelle psychologie heinrich-heine-universit"at d"usseldorf
signature.asc
Description: This is a digitally signed message part.
------------------------------------------------------------------------------ Achieve unprecedented app performance and reliability What every C/C++ and Fortran developer should know. Learn how Intel has extended the reach of its next-generation tools to help boost performance applications - inlcuding clusters. http://p.sf.net/sfu/intel-dev2devmay
_______________________________________________ RKWard-devel mailing list RKWard-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/rkward-devel
