. But it certainly should be considered for Windows.
Without it, it is difficult to say that Perl handles Unicode well.
--
Erland Sommarskog, Stockholm, [EMAIL PROTECTED]
Nick Ing-Simmons ([EMAIL PROTECTED]) writes:
Erland Sommarskog [EMAIL PROTECTED] writes:
I would really expect someone to have done this already, but I see no
reference to such a module. Or layer-directive like :use-bom to open
the file. And then some way to open an output file same mode
, or is possible to pass some PerlIO print
function an SV, and then let PerlIO do the job? Surely it is not a good
thing to bypass PerlIO completely, and use wprintf or somesuch?
--
Erland Sommarskog, Stockholm, [EMAIL PROTECTED]
.
Both input data and the script. Just because the script has been saved
in UTF-8, does not mean that literals in the script are taken as UTF-8.
--
Erland Sommarskog, Stockholm, [EMAIL PROTECTED]
to understand byte-order marks
(which it doesn't). I think there was a suggestion that you could
specify an
In 5.8.5 it will.
Will such an option include the possibility to say that I want Perl to
determine the encoding from the byte-order mark?
--
Erland Sommarskog, Stockholm, [EMAIL PROTECTED]
Nick Ing-Simmons ([EMAIL PROTECTED]) writes:
Erland Sommarskog [EMAIL PROTECTED] writes:
Both input data and the script. Just because the script has been saved
in UTF-8, does not mean that literals in the script are taken as UTF-8.
I disagree there. The literals have to be in same encoding
is that column and parameter names can
serve as hash keys under some circumstances. What implcations this has,
I have not even tested yet...
--
Erland Sommarskog, Stockholm, [EMAIL PROTECTED]
Jean-Michel Hiver ([EMAIL PROTECTED]) writes:
Erland Sommarskog wrote:
I working with an XS module that passes queries to MS SQL Server and
returns data back using SQLOLEDB. MS SQL Server stores Unicode data
as UTF-16. Also, all metadata is UTF-16.
Currently when I get Unicode data back from SQL
, subversion 2 (v5.12.2) built for MSWin32-x86-
multi-thread (with 8 registered patches, see perl -V for more detail)
Copyright 1987-2010, Larry Wall
Binary build 1202 [293621] provided by ActiveState
http://www.ActiveState.com
Built Sep 6 2010 23:36:03
--
Erland Sommarskog, Stockholm, esq
jumps in and blindly adds a carriage return, but
somehow it does manage to get the \r character correct nevertheless, but
loses the high byte of the \n.
--
Erland Sommarskog, Stockholm, esq...@sommarskog.se
:
41 00 6C 00 66 00 61 00 0D 0A 00 42 00 65 00 74
00 61 00 0D 0A 00 47 00 61 00 6D 00 6D 00 61 00
0D 0A 00
In total 35 bytes. Which is a very odd number for a UTF16 file.
--
Erland Sommarskog, Stockholm, esq...@sommarskog.se
Michael Ludwig (mil...@gmx.de) writes:
Erland Sommarskog schrieb am 29.01.2011 um 14:02 (+0100):
Yes, there certainly seems to be some more stuff to do in the Unicode
support in Perl. For instance, support for Unicode filenames in open
or opendir.
I think there is no portable answer here
in Windows, and the associate it with
a file handle.
--
Erland Sommarskog, Stockholm, esq...@sommarskog.se
13 matches
Mail list logo
