Re: Handling international characters in filenames on Win32
From: Mihai N. (nmihai_year_2000_at_yahoo.com)
Date: 04/16/04
- Next message: Gregory Toomey: "Re: porting from pl/1"
- Previous message: Stephen M: "Re: Running a perl script in the background on Windows"
- In reply to: Sisyphus: "Re: Handling international characters in filenames on Win32"
- Next in thread: Stéphane Bourdeaud: "Re: Handling international characters in filenames on Win32"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Date: Fri, 16 Apr 2004 09:35:17 GMT
Some notes, additions and corrections:
> Sounds like one of those codeset conversion problems. DOS uses cp850 and
> windows uses cp1252
DOS and the Windows actual console (which "symulates" the DOS prompt)
The DOS/console code page is also called OEM code page.
The Windows code page is also called (not 100% correct) ANSI code page.
Also, 850 was the OEM used for most Western European languages.
For English U.S. systems the OEM cp is 437.
> which is the same for 'normal' characters but
> differs wrt wide characters.
Not wide characters, just "high ascii" or "accented characters"
> It's a fairly simple task using Text::Iconv
> to convert from one to the other - which would be one way to get around
> the problem. It's probably just as simple to convert from one to the
> other using the Encode module which is part of the perl core with perl
> 5.8 (though I've not used it).
Main problem here: there are characters in 1252 that are not present
in 850/437.
-- Mihai ------------------------- Replace _year_ with _ to get the real email
- Next message: Gregory Toomey: "Re: porting from pl/1"
- Previous message: Stephen M: "Re: Running a perl script in the background on Windows"
- In reply to: Sisyphus: "Re: Handling international characters in filenames on Win32"
- Next in thread: Stéphane Bourdeaud: "Re: Handling international characters in filenames on Win32"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Relevant Pages
|