Yet another unicode question: windows platform
- From: "tewilk@xxxxxxxxx" <tewilk@xxxxxxxxx>
- Date: 30 Oct 2006 14:14:22 -0800
I'm still searching for the answer but I can't find it yet so maybe
someone can point me in the right direction. This is my problem... I'm
reading MS SQL Server errorlog file- sql7 and sql2000 are standard
ascii flat files that I can process with no problems. Then comes
SQL2005... now the file is in unicode format. After a lots reading
(web and perl docs) I ran across my answer...
http://blogs.msdn.com/brettsh/archive/2006/06/07/620986.aspx , the link
talks about writing but I was able to use the same concept to read the
file (open errorlogFH,"<:raw:encoding(UTF16-LE):crlf:utf8",
"$TempErrorlog";) which worked fine. BTW... the information from this
link was more helpful than the perldocs but maybe it just me :o
Now here is my issue that I'm sure is a no brainier for someone out
there... prior to my open, how can I check the file? Is it plain text
so that I can use the standard open OR is it unicode so that I know
that I need to use the "encoding" method?
Also if anyone knows of some good information that has worked for them
as it pertains to unicode, please post so that I can check it out.
Many thanks!
Terry
.
- Follow-Ups:
- Re: Yet another unicode question: windows platform
- From: Alexei A. Frounze
- Re: Yet another unicode question: windows platform
- Prev by Date: Re: POE performance issue.
- Next by Date: loop over a string to do search/replacement using regexp?
- Previous by thread: POE performance issue.
- Next by thread: Re: Yet another unicode question: windows platform
- Index(es):
Relevant Pages
|