in reply to Re^5: opening accented file names
in thread opening accented file names

Unless my eyes are deceiving me, no matter which codepage I use to create the file, or which I use to subsequently view that file, the glyph appears correct. 

Microsoft Windows [Version 6.0.6001]
Copyright (c) 2006 Microsoft Corporation.  All rights reserved.

c:\>chcp
Active code page: 850

c:\>dir /b ac*
acentó.dat

c:\>chcp 437
Active code page: 437

c:\>dir /b ac*
acentó.dat

c:\>chcp 65001
Active code page: 65001

c:\>dir /b ac*
acentó.dat

c:\>chcp 65000
Active code page: 65000

c:\>dir /b ac*
acentó.dat

Microsoft Windows [Version 6.0.6001]
Copyright (c) 2006 Microsoft Corporation.  All rights reserved.

c:\>del ac*

c:\>chcp 437
Active code page: 437

c:\>echo fred > acentó.txt

c:\>dir /b ac*
acentó.txt

c:\>chcp 850
Active code page: 850

c:\>dir /b ac*
acentó.txt

c:\>chcp 65001
Active code page: 65001

c:\>dir /b ac*
acentó.txt

c:\>chcp 65000
Active code page: 65000

c:\>dir /b ac*
acentó.txt

c:\>del ac*

c:\>chcp 65001
Active code page: 65001

c:\>echo fred > acentó.txt

c:\>chcp 65000
Active code page: 65000

c:\>dir /b ac*
acentó.txt

c:\>chcp 850
Active code page: 850

c:\>dir /b ac*
acentó.txt

c:\>chcp 437
Active code page: 437

c:\>dir /b ac*
acentó.txt

c:\>

[download]
Examine what is said, not who speaks -- Silence betokens consent -- Love the truth but pardon error.
"Science is about questioning the status quo. Questioning authority".
In the absence of evidence, opinion is indistinguishable from prejudice.
RIP an inspiration; A true Folk's Guy

Replies are listed 'Best First'.
Re^7: opening accented file names
by Jim (Curate) on Nov 12, 2010 at 17:39 UTC

    I see exactly the same output when I run those same commands. This demonstrates the DIR command properly outputs and displays a Latin small letter o with an acute accent regardless of the active code page (so long as ó is in the repetoire of characters of the code page), which is terrific, and good to know. But this is PerlMonks, not DirMonks. ;-)

    Now run my Perl script as I did with the code page set to 437, 850, 1252, 65001, etc. Then come back and tell me if you still think I was "confusing things by mentioning chcp" and that "[i]t isn't necessary." I wasn't, and it is.

    The important and germane point here is that, unlike what DIR does, ActivePerl for Windows prints whatever the glyph is for byte \xF3 in whatever the active code page is.

[reply]
      Maybe because ActivePerl for Windows does not know what codepage your filesystem is using?
[reply]

        Exactly!

[reply]

In Section Seekers of Perl Wisdom