Re^3: Perl/Tk exe not working

This sounds like a UTF-8 problem. There have been big changes to the perl core in this area since 5.6.1.

Please could you run the following commands on your home machine, and paste the output:

perl -v
perl -V
perl -MPAR -e "print PAR->VERSION,qq(\n)"
perl -MEncode::Unicode -e "print Encode::Unicode->VERSION,qq(\n)"
[download]

--

Oh Lord, won’t you burn me a Knoppix CD ?
My friends all rate Windows, I must disagree.
Your powers of persuasion will set them all free,
So oh Lord, won’t you burn me a Knoppix CD ?
(Missquoting Janis Joplin)

Comment on Re^3: Perl/Tk exe not working Download Code

Replies are listed 'Best First'.
Re^4: Perl/Tk exe not working by wook (Novice) on Oct 10, 2005 at 16:25 UTC
perl -v: v5.8.6 build MSWin32-x86-multi-thread download ################################### Encode::Unicode version: 2.02 download ################################### PAR version: 0.75 download perl -V printed out too much stuff for me to retype! Is there something specific that I'd need to be looking for?	[reply]
Re^4: Perl/Tk exe not working by Anonymous Monk on Oct 10, 2005 at 16:23 UTC
perl -v: `v5.8.6 build MSWin32-x86-multi-thread` [download] ################################### Encode::Unicode version: `2.02` [download] ################################### PAR version: `0.75` [download] perl -V printed out too much stuff for me to retype! Is there something specific that I'd need to be looking for?	[reply] [d/l] [select]
Re^5: Perl/Tk exe not working by rinceWind (Monsignor) on Oct 10, 2005 at 16:38 UTC
Your perl version is reasonably recent. No problem there. There is an update to the Encode module, I recommend that you install this. Also, your version of PAR is fairly ancient. many bugs and issues have been fixed in PAR since then. If you have been relying on getting dists from ActiveState's ppm repository, you might need to shop around for more recent versions: try http://crazyinsomniac.perlmonk.org/perl/ppm , or download the source from CPAN and build them yourself (you need MS Visual Studio 6 or later). In terms of your underlying problem, you might find that there's a locale difference between the two machines, which is tripping the character set encoding logic. Check Locale + regional settings. -- Oh Lord, won’t you burn me a Knoppix CD ? My friends all rate Windows, I must disagree. Your powers of persuasion will set them all free, So oh Lord, won’t you burn me a Knoppix CD ? (Missquoting Janis Joplin)	[reply]