Hello,
Try chcp in a DOS BOX, this shows you the active code page in command
prompt.
(on my XP it shows me 850 which is cp850)
regards,
Reinhard
Benct Philip Jonsson wrote:
Is the encoding used in the Windows Command Prompt
cp850? I need to know that to use the Encode
module to convert in
Chris:
When I try to change the slashes of the source file C:\ path\file to
C:/path/file using s///, it don't carry out the change, because the file
source expressed C:pathfile, therefore, is not enhanced the copy.
- Original Message -
From: Chris Wagner [EMAIL PROTECTED]
To:
Title: RE: Resolved - Question about Win32::OLE
After screwing up the last two days, I now have this well embedded in my mind. Wel, at least until I have another memory dump.
This list is a great resource.
Best to all,
Sturdy
-Original Message-
From: Timothy Johnson
At 08:33 AM 5/26/2006 -0400, vcarvallo wrote:
Chris:
When I try to change the slashes of the source file C:\ path\file to
C:/path/file using s///, it don't carry out the change, because the file
source expressed C:pathfile, therefore, is not enhanced the copy.
$file = $data{'our_file'};
Are
Lyndon Rickards wrote:
# The delay here is to allow widget to render before forcing
# to front - workaround to avoid 'UpdateWrapper: Failed to create
container'
# crash from some (mostly XP) clients
$MW-after(500,sub {$MW-stayOnTop});
Interesting... I fixed that problem differently, by
Benct Philip Jonsson wrote:
Is the encoding used in the Windows Command Prompt
cp850? I need to know that to use the Encode
module to convert in order to have perl handle
accented characters right.
Reinhard Pagitsch replied:
Try chcp in a DOS BOX, this shows you the active code page in
Use a different character for your substitution delimeter. Whenever I
will be sub'ing slashes, I use the pipe '|'.
So I'd have a string C:\path\file
I'd run the path through a s|\\|/|g and it would pop out C:/path/file
This won't magically make your script work, but it will make it a bit
