Re: Creating UNICODE filenames with PERL 5.8
From: Malcolm Dew-Jones (yf110_at_vtn1.victoria.tc.ca)
Date: 11/19/03
- Next message: Jeff 'japhy' Pinyan: "Re: Match and cut regex?"
- Previous message: Geek: "Error trapping $RS_ADO->Open($SQL_ADO, $Conn_ADO, 1, 1)"
- In reply to: Ben Morrow: "Re: Creating UNICODE filenames with PERL 5.8"
- Next in thread: Ben Morrow: "[OT] Re: Creating UNICODE filenames with PERL 5.8"
- Reply: Ben Morrow: "[OT] Re: Creating UNICODE filenames with PERL 5.8"
- Reply: Alan J. Flavell: "Re: Creating UNICODE filenames with PERL 5.8"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Date: 18 Nov 2003 16:40:22 -0800
Ben Morrow (usenet@morrow.me.uk) wrote:
: allan@yates.ca (Allan Yates) wrote:
: > I have been having distinct trouble creating file names in PERL
: Perl or perl, not PERL.
: > containing UNICODE
: I'm not so sure about UNICODE...
: > For a simple test, I picked a UNICODE character that could be
: > displayed by Windows Explorer. I can select the character(U+0636) from
: > 'charmap' and cut/paste into a filename on Windows Explorer and the
: > character displays the same as it does in 'charmap'. This proves that
: > I have the font available.
: >
: > When I attempt to create the same filename with PERL, I end up with a
: > filename two characters long: ض
: OK, your problem here is that Win2k is being stupid about Unicode: any
: sensible OS that understood UTF8 would be fine :).
Hum, NT has been handling unicode for at least ten years (3.5, 1993) by
the simple expedient of using 16 bit characters. It is hardware that is
stupid, by continuing to use ancient tiny 8 bit elementary units.
Imagine if all that hardware still used 16 or 24 bit memory addresses.
Imagine if all our communication and hardware backbones still actually
transmitted data in single digit bit sizes.
Character size was always a compromise between functionality and memory.
Character size continually increased from the first character manipulating
electronic equipment of the (gee, way way back 1930's or so, believe it or
not) until the 1980's, when it suddenly solidified into a standard
elementary unit that was still a compromise in terms of size, but is now
clearly too small.
Character size remains frozen due to one of murphy's laws regarding the
success of hardware first build using compromises that were appropriate
twenty years ago.
- Next message: Jeff 'japhy' Pinyan: "Re: Match and cut regex?"
- Previous message: Geek: "Error trapping $RS_ADO->Open($SQL_ADO, $Conn_ADO, 1, 1)"
- In reply to: Ben Morrow: "Re: Creating UNICODE filenames with PERL 5.8"
- Next in thread: Ben Morrow: "[OT] Re: Creating UNICODE filenames with PERL 5.8"
- Reply: Ben Morrow: "[OT] Re: Creating UNICODE filenames with PERL 5.8"
- Reply: Alan J. Flavell: "Re: Creating UNICODE filenames with PERL 5.8"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Relevant Pages
|