<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: Cognos EP log analysis</title>
	<atom:link href="http://ykud.com/blog/coding/cognos-ep-log-analysis/feed" rel="self" type="application/rss+xml" />
	<link>http://ykud.com/blog/coding/cognos-ep-log-analysis</link>
	<description></description>
	<lastBuildDate>Fri, 18 May 2012 08:38:00 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.2</generator>
	<item>
		<title>By: ykud</title>
		<link>http://ykud.com/blog/coding/cognos-ep-log-analysis/comment-page-1#comment-93</link>
		<dc:creator>ykud</dc:creator>
		<pubDate>Thu, 06 Dec 2007 12:42:48 +0000</pubDate>
		<guid isPermaLink="false">http://ykud.com/blog/2006/11/21/cognos-ep-log-analysis/#comment-93</guid>
		<description>Hi, Made Up

Thanks for pointing at BOMs, will remeber that for future.

Yet my other problem was that some files were indeed csv delimited (somebody opened them in Excel and saved) and had another wide pack of excel-only characters. Python decode worked extremely well in given time&amp;effort constraints.

Yep, we&#039;ve got around 2gbs of 3 year log data, searchable on cognos connection, but it mostly shows us the things we already known -- database crushes and that stuff. But it sure looks nice )</description>
		<content:encoded><![CDATA[<p>Hi, Made Up</p>
<p>Thanks for pointing at BOMs, will remeber that for future.</p>
<p>Yet my other problem was that some files were indeed csv delimited (somebody opened them in Excel and saved) and had another wide pack of excel-only characters. Python decode worked extremely well in given time&amp;effort constraints.</p>
<p>Yep, we&#8217;ve got around 2gbs of 3 year log data, searchable on cognos connection, but it mostly shows us the things we already known &#8212; database crushes and that stuff. But it sure looks nice )</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Made Up</title>
		<link>http://ykud.com/blog/coding/cognos-ep-log-analysis/comment-page-1#comment-92</link>
		<dc:creator>Made Up</dc:creator>
		<pubDate>Wed, 05 Dec 2007 23:08:33 +0000</pubDate>
		<guid isPermaLink="false">http://ykud.com/blog/2006/11/21/cognos-ep-log-analysis/#comment-92</guid>
		<description>The funky characters at the start of the file are called the BOM:

http://en.wikipedia.org/wiki/Byte_Order_Mark

Use Python&#039;s &quot;codecs&quot; module to open them as &quot;utf-16&quot;:

f= codecs.open(logFilePath,&quot;r+t&quot;,&quot;utf-16&quot;)

Yes, they are tab-separated as commas appear very often in the text. The file extension is just to abuse the file association in Windows for Excel. If there are tabs in the content, it should be replaced with a &quot;~&quot;.

Cool to see good work being done on the logs.</description>
		<content:encoded><![CDATA[<p>The funky characters at the start of the file are called the BOM:</p>
<p><a href="http://en.wikipedia.org/wiki/Byte_Order_Mark" rel="nofollow">http://en.wikipedia.org/wiki/Byte_Order_Mark</a></p>
<p>Use Python&#8217;s &#8220;codecs&#8221; module to open them as &#8220;utf-16&#8243;:</p>
<p>f= codecs.open(logFilePath,&#8221;r+t&#8221;,&#8221;utf-16&#8243;)</p>
<p>Yes, they are tab-separated as commas appear very often in the text. The file extension is just to abuse the file association in Windows for Excel. If there are tabs in the content, it should be replaced with a &#8220;~&#8221;.</p>
<p>Cool to see good work being done on the logs.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

