<?xml version="1.0" encoding="utf-8" ?>
<?xml-stylesheet href="/serendipity/templates/default/atom.css" type="text/css" ?>

<feed 
   xmlns="http://www.w3.org/2005/Atom"
   xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
   xmlns:dc="http://purl.org/dc/elements/1.1/"
   xmlns:admin="http://webns.net/mvcb/"
   xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
   xmlns:wfw="http://wellformedweb.org/CommentAPI/">
    <link href="http://www.topicalizer.com/serendipity/feeds/atom.xml" rel="self" title="Topicalizer Blog" type="application/atom+xml" />
    <link href="http://www.topicalizer.com/serendipity/"                        rel="alternate"    title="Topicalizer Blog" type="text/html" />
    <link href="http://www.topicalizer.com/serendipity/rss.php?version=2.0"     rel="alternate"    title="Topicalizer Blog" type="application/rss+xml" />
    <title type="html">Topicalizer Blog</title>
    <subtitle type="html">The weblog about Topicalizer - a tool for topic extraction, text analysis and abstract generation</subtitle>
    <icon>http://www.topicalizer.com/serendipity/templates/default/img/s9y_banner_small.png</icon>
    <id>http://www.topicalizer.com/serendipity/</id>
    <updated>2008-09-09T18:26:10Z</updated>
    <generator uri="http://www.s9y.org/" version="1.1">Serendipity 1.1 - http://www.s9y.org/</generator>
    <dc:language>en</dc:language>

    <entry>
        <link href="http://www.topicalizer.com/serendipity/archives/21-ContentSieve-Breaks-Down-Market-Entry-Barriers-For-Small-Web-Content-Providers.html" rel="alternate" title="ContentSieve Breaks Down Market Entry Barriers For Small Web Content Providers" />
        <author>
            <name>Björn Wilmsmann</name>
            <email>nospam@example.com</email>
        </author>
    
        <published>2008-09-09T18:18:33Z</published>
        <updated>2008-09-09T18:26:10Z</updated>
        <wfw:comment>http://www.topicalizer.com/serendipity/wfwcomment.php?cid=21</wfw:comment>
    
        <slash:comments>0</slash:comments>
        <wfw:commentRss>http://www.topicalizer.com/serendipity/rss.php?version=atom1.0&amp;type=comments&amp;cid=21</wfw:commentRss>
    
            <category scheme="http://www.topicalizer.com/serendipity/categories/4-Company" label="Company" term="Company" />
    
        <id>http://www.topicalizer.com/serendipity/archives/21-guid.html</id>
        <title type="html">ContentSieve Breaks Down Market Entry Barriers For Small Web Content Providers</title>
        <content type="xhtml" xml:base="http://www.topicalizer.com/serendipity/">
            <div xmlns="http://www.w3.org/1999/xhtml">
                My company has just released a new service called <a href="http://www.contentsieve.com/"  title="ContentSieve">ContentSieve</a> (<a href="http://www.contentsieve.com/"  title="ContentSieve">http://www.contentsieve.com</a>). For further information please have a look at the following press release, taken from <a href="http://metasieve.wordpress.com/2008/09/04/contentsieve-breaks-down-market-entry-barriers-for-small-web-content-providers/trackback/"  title="http://metasieve.wordpress.com/">http://metasieve.wordpress.com/</a>:<br />
<br />
More and more information providers offer their content on the Web. In order to be successful they have to attract a large number of users to their site. There are two main ways of achieving this. One can either advertise on other sites or once can try to improve the site’s search engine listing through optimisation of site and link structure.<br />
<br />
Attaining a reasonably good listing in the usual search engines becomes increasingly difficult. There is intense competition for each search term. Many companies hire professional search engine optimisers for gaining a prominent position in search engine results. Each year millions of euros are spent on this.<br />
<br />
Smaller competitors increasingly fail to participate in this market. In the meantime the best search engine optimisers charge up to a whopping 1,000 EUR per month. The prices for creation of content that is considered relevant by search engines keep climbing with no end in sight. Even interesting information frequently is only displayed by search engines if it complies with the complicated rules set up by search engines. This drives up the cost of content creation and creates market entry barriers which hardly any small competitor can handle.<br />
<br />
<a href="http://www.contentsieve.com/"  title="ContentSieve">ContentSieve</a> is a new online service helping Web content providers to overcome these barriers.<br />
<br />
"As of lately, it has become more difficult to differentiate one’s Web site in order to capitalise on its content." says Björn Wilmsmann, CEO of <a href="http://www.metasieve.com/"  title="MetaSieve">MetaSieve</a>, the provider of the new service. "High costs for editorial content, AdWords and search engine optimisation leave the online content business to but a few large competitors."<br />
<br />
With ContentSieve online service providers now can add up-to-date and thematically matching content to their sites. This way, news flashes or search results for a specific topic can be displayed. This content is integrated as widgets into existing sites. Permanently updated content makes a Web site more attractive to users and brings about a better search engine ranking. The content is already optimised so there is no need for expensive search engine optimisation anymore.<br />
<br />
"Our goal," explains Wilmsmann "is to offer access to attractive online marketing opportunities, especially to small content providers."<br />
ContentSieve is ready for use after just a few clicks. After having registered, the user can create widgets and include them in her own site with a small code snippet. Subsequent editing of this code snippet is not needed anymore as third party content can be delivered through this code as well. Billing works through ordering packages, which contain a certain number of widget views at a fixed price.<br />
ContentSieve immediately begins to deliver relevant content until these widget views are used up. To allow extensive testing each new user will get 5,000 widget views for free as a welcome gift.<br />
<br />
<a href="http://www.contentsieve.com/"  title="ContentSieve">ContentSieve</a> currently is available in English and German.<br />
 
            </div>
        </content>
        
    </entry>
    <entry>
        <link href="http://www.topicalizer.com/serendipity/archives/20-GameSear.ch-Everything-you-need-to-know-about-games.html" rel="alternate" title="GameSear.ch: Everything you need to know about games" />
        <author>
            <name>Björn Wilmsmann</name>
            <email>nospam@example.com</email>
        </author>
    
        <published>2008-07-18T17:29:29Z</published>
        <updated>2008-07-18T17:39:45Z</updated>
        <wfw:comment>http://www.topicalizer.com/serendipity/wfwcomment.php?cid=20</wfw:comment>
    
        <slash:comments>0</slash:comments>
        <wfw:commentRss>http://www.topicalizer.com/serendipity/rss.php?version=atom1.0&amp;type=comments&amp;cid=20</wfw:commentRss>
    
            <category scheme="http://www.topicalizer.com/serendipity/categories/4-Company" label="Company" term="Company" />
    
        <id>http://www.topicalizer.com/serendipity/archives/20-guid.html</id>
        <title type="html">GameSear.ch: Everything you need to know about games</title>
        <content type="xhtml" xml:base="http://www.topicalizer.com/serendipity/">
            <div xmlns="http://www.w3.org/1999/xhtml">
                Today my company <a href="http://www.metasieve.com/"  title="MetaSieve">MetaSieve</a> has released a new online service called <a href="http://gamesear.ch/"  title="GameSear.ch">GameSear.ch</a>. <a href="http://gamesear.ch/"  title="GameSear.ch">GameSear.ch</a> is a new vertical search engine that aggregates a huge number of sources about games - computer and video games in particular - all in one place.<br />
<br />
<a href="http://gamesear.ch/"  title="GameSear.ch">GameSear.ch</a> allows you to find, access and syndicate all the relevant gaming content on the web. 
            </div>
        </content>
        
    </entry>
    <entry>
        <link href="http://www.topicalizer.com/serendipity/archives/19-Topicalizer-now-using-Yahoo-Search-API.html" rel="alternate" title="Topicalizer now using Yahoo Search API" />
        <author>
            <name>Björn Wilmsmann</name>
            <email>nospam@example.com</email>
        </author>
    
        <published>2008-03-27T21:47:31Z</published>
        <updated>2008-03-27T21:47:31Z</updated>
        <wfw:comment>http://www.topicalizer.com/serendipity/wfwcomment.php?cid=19</wfw:comment>
    
        <slash:comments>0</slash:comments>
        <wfw:commentRss>http://www.topicalizer.com/serendipity/rss.php?version=atom1.0&amp;type=comments&amp;cid=19</wfw:commentRss>
    
    
        <id>http://www.topicalizer.com/serendipity/archives/19-guid.html</id>
        <title type="html">Topicalizer now using Yahoo Search API</title>
        <content type="xhtml" xml:base="http://www.topicalizer.com/serendipity/">
            <div xmlns="http://www.w3.org/1999/xhtml">
                The 'Search for similar documents' and 'Semantic Web Creator' tools, as well as the 'Find similar documents' function now build upon the Yahoo Search API. Previously, the <a href="http://code.google.com/apis/soapsearch/"  title="Google Search API">Google Search API</a> was used for all of these.<br />
<br />
However, some time ago, Google has closed this API for new users, obviously in an attempt to win users over to their new <a href="http://code.google.com/apis/ajaxsearch/"  title="AJAX Search API">AJAX Search API</a>. The API still works for old users but has become somewhat unreliable as of lately, which is why I decided to switch to the <a href="http://developer.yahoo.com/search/"  title="Yahoo Search API">Yahoo Search API</a> instead.<br />
<br />
The <a href="http://developer.yahoo.com/search/"  title="Yahoo Search API">Yahoo Search API</a> is limited to 5,000 requests per IP per day, as opposed to the 1,000 queries allowed per day with the old <a href="http://code.google.com/apis/soapsearch/"  title="Google Search API">Google Search API</a>.<br />
 
            </div>
        </content>
        
    </entry>
    <entry>
        <link href="http://www.topicalizer.com/serendipity/archives/18-Very-Cool-Stuff-FeedBlast.html" rel="alternate" title="Very Cool Stuff: FeedBlast" />
        <author>
            <name>Björn Wilmsmann</name>
            <email>nospam@example.com</email>
        </author>
    
        <published>2007-03-29T23:29:59Z</published>
        <updated>2007-07-16T19:15:12Z</updated>
        <wfw:comment>http://www.topicalizer.com/serendipity/wfwcomment.php?cid=18</wfw:comment>
    
        <slash:comments>0</slash:comments>
        <wfw:commentRss>http://www.topicalizer.com/serendipity/rss.php?version=atom1.0&amp;type=comments&amp;cid=18</wfw:commentRss>
    
            <category scheme="http://www.topicalizer.com/serendipity/categories/1-Topicalizer" label="Topicalizer" term="Topicalizer" />
    
        <id>http://www.topicalizer.com/serendipity/archives/18-guid.html</id>
        <title type="html">Very Cool Stuff: FeedBlast</title>
        <content type="xhtml" xml:base="http://www.topicalizer.com/serendipity/">
            <div xmlns="http://www.w3.org/1999/xhtml">
                I have just found out about a very cool project that makes use of the Topicalizer API called FeedBlast. The detailed concept is described under <a href="http://www.rndparty.com/"  title="http://www.rndparty.com/">http://www.rndparty.com/</a><br />
<br />
The basic idea is to take RSS feeds, have them analysed via Topicalizer and to create an audio / video summary from the input. For this purpose an AT&T text-to-speech software will be used to read out the abstract created by Topicalizer. Moreover, the keywords provided by Topicalizer are used to find media items that fit the RSS content.<br />
<br />
Very cool stuff, indeed. I am looking forward to hearing more of this.<br />
 
            </div>
        </content>
        
    </entry>
    <entry>
        <link href="http://www.topicalizer.com/serendipity/archives/17-New-Blog-Coverage.html" rel="alternate" title="New Blog Coverage" />
        <author>
            <name>Björn Wilmsmann</name>
            <email>nospam@example.com</email>
        </author>
    
        <published>2006-12-24T17:54:15Z</published>
        <updated>2007-07-16T19:15:24Z</updated>
        <wfw:comment>http://www.topicalizer.com/serendipity/wfwcomment.php?cid=17</wfw:comment>
    
        <slash:comments>0</slash:comments>
        <wfw:commentRss>http://www.topicalizer.com/serendipity/rss.php?version=atom1.0&amp;type=comments&amp;cid=17</wfw:commentRss>
    
            <category scheme="http://www.topicalizer.com/serendipity/categories/1-Topicalizer" label="Topicalizer" term="Topicalizer" />
    
        <id>http://www.topicalizer.com/serendipity/archives/17-guid.html</id>
        <title type="html">New Blog Coverage</title>
        <content type="xhtml" xml:base="http://www.topicalizer.com/serendipity/">
            <div xmlns="http://www.w3.org/1999/xhtml">
                For those of you with sufficient command of the Spanish language: Topicalizer has recently been covered in the Spanish language weblog 'La Bitácora del Tigre' (The Tiger's Log): <a href="http://www.labitacoradeltigre.com/2006/12/23/mas-recursos-de-escritura-y-feliz-navidad-para-todos/"  title="La Bitácora del Tigre">http://www.labitacoradeltigre.com/2006/12/23/mas-recursos-de-escritura-y-feliz-navidad-para-todos/</a><br />
Eduardo-Martín Larequi Garcí, the author of this weblog, is a Spanish language and literature teacher, who is currently employed by the Department of Education of the regional government of <a href="http://en.wikipedia.org/wiki/Navarra"  title="Navarra">Navarra</a>.<br />
<br />
Oh, before closing, I would like to wish you a Merry Christmas (or 'Feliz Navidad' for that matter).<br />
 
            </div>
        </content>
        
    </entry>
    <entry>
        <link href="http://www.topicalizer.com/serendipity/archives/16-Semantic-Web-Creator.html" rel="alternate" title="Semantic Web Creator" />
        <author>
            <name>Björn Wilmsmann</name>
            <email>nospam@example.com</email>
        </author>
    
        <published>2006-12-02T18:58:39Z</published>
        <updated>2007-07-16T19:16:08Z</updated>
        <wfw:comment>http://www.topicalizer.com/serendipity/wfwcomment.php?cid=16</wfw:comment>
    
        <slash:comments>0</slash:comments>
        <wfw:commentRss>http://www.topicalizer.com/serendipity/rss.php?version=atom1.0&amp;type=comments&amp;cid=16</wfw:commentRss>
    
            <category scheme="http://www.topicalizer.com/serendipity/categories/1-Topicalizer" label="Topicalizer" term="Topicalizer" />
    
        <id>http://www.topicalizer.com/serendipity/archives/16-guid.html</id>
        <title type="html">Semantic Web Creator</title>
        <content type="xhtml" xml:base="http://www.topicalizer.com/serendipity/">
            <div xmlns="http://www.w3.org/1999/xhtml">
                There is a new tool on this site, which I have called <a href="http://www.topicalizer.com/semWeb/"  title="Semantic Web Creator">Semantic Web Creator</a><br />
<br />
This tool creates a set of related terms for a given term. In order to achieve this, it makes use of the Google API and Wikipedia.<br />
<br />
The Google API is used to get the Wikipedia page for the term and this page is scanned for links to other Wikipedia articles in order to retrieve the terms which are associated with the original term. 
            </div>
        </content>
        
    </entry>
    <entry>
        <link href="http://www.topicalizer.com/serendipity/archives/15-New-Mashup-Bookalizer.com.html" rel="alternate" title="New Mashup: Bookalizer.com" />
        <author>
            <name>Björn Wilmsmann</name>
            <email>nospam@example.com</email>
        </author>
    
        <published>2006-07-04T17:58:15Z</published>
        <updated>2007-07-16T19:16:12Z</updated>
        <wfw:comment>http://www.topicalizer.com/serendipity/wfwcomment.php?cid=15</wfw:comment>
    
        <slash:comments>0</slash:comments>
        <wfw:commentRss>http://www.topicalizer.com/serendipity/rss.php?version=atom1.0&amp;type=comments&amp;cid=15</wfw:commentRss>
    
            <category scheme="http://www.topicalizer.com/serendipity/categories/1-Topicalizer" label="Topicalizer" term="Topicalizer" />
    
        <id>http://www.topicalizer.com/serendipity/archives/15-guid.html</id>
        <title type="html">New Mashup: Bookalizer.com</title>
        <content type="xhtml" xml:base="http://www.topicalizer.com/serendipity/">
            <div xmlns="http://www.w3.org/1999/xhtml">
                Bookalizer.com (<a href="http://www.bookalizer.com/"  title="http://www.bookalizer.com/">http://www.bookalizer.com/</a>) is a web service that allows you to display customised Amazon book ads on your homepage according to the content of the respective page. You can either specify the key words by which books are selected by yourself, or provide a set of Amazon product IDs or have Topicalizer select the most appropriate key words automatically.<br />
<br />
The service is organised by a German organisation called Clever Spenden e.V., which donates the revenues of affiliate services to a good cause.<br />
<br />
Please have a look at their weblog as well: <a href="http://bookadmin.blogspot.com/"  title="http://bookadmin.blogspot.com/">http://bookadmin.blogspot.com/</a> 
            </div>
        </content>
        
    </entry>
    <entry>
        <link href="http://www.topicalizer.com/serendipity/archives/14-Tetragrams-and-pentagrams.html" rel="alternate" title="Tetragrams and pentagrams" />
        <author>
            <name>Björn Wilmsmann</name>
            <email>nospam@example.com</email>
        </author>
    
        <published>2006-06-17T12:55:01Z</published>
        <updated>2007-07-16T19:16:15Z</updated>
        <wfw:comment>http://www.topicalizer.com/serendipity/wfwcomment.php?cid=14</wfw:comment>
    
        <slash:comments>0</slash:comments>
        <wfw:commentRss>http://www.topicalizer.com/serendipity/rss.php?version=atom1.0&amp;type=comments&amp;cid=14</wfw:commentRss>
    
            <category scheme="http://www.topicalizer.com/serendipity/categories/1-Topicalizer" label="Topicalizer" term="Topicalizer" />
    
        <id>http://www.topicalizer.com/serendipity/archives/14-guid.html</id>
        <title type="html">Tetragrams and pentagrams</title>
        <content type="xhtml" xml:base="http://www.topicalizer.com/serendipity/">
            <div xmlns="http://www.w3.org/1999/xhtml">
                Topicalizer now also calculates tetragram and pentagram results (i.e. four- and five-word phrases) besides the bigram and trigram ones. Furthermore, Topicalizer from now on does not only display the ten most frequent results for each category, but the overall most frequent results as well. 
            </div>
        </content>
        
    </entry>
    <entry>
        <link href="http://www.topicalizer.com/serendipity/archives/13-New-tool-Get-most-likely-co-occurrences-for-words.html" rel="alternate" title="New tool: Get most likely co-occurrences for words" />
        <author>
            <name>Björn Wilmsmann</name>
            <email>nospam@example.com</email>
        </author>
    
        <published>2006-05-04T08:07:48Z</published>
        <updated>2007-07-16T19:16:19Z</updated>
        <wfw:comment>http://www.topicalizer.com/serendipity/wfwcomment.php?cid=13</wfw:comment>
    
        <slash:comments>0</slash:comments>
        <wfw:commentRss>http://www.topicalizer.com/serendipity/rss.php?version=atom1.0&amp;type=comments&amp;cid=13</wfw:commentRss>
    
            <category scheme="http://www.topicalizer.com/serendipity/categories/1-Topicalizer" label="Topicalizer" term="Topicalizer" />
    
        <id>http://www.topicalizer.com/serendipity/archives/13-guid.html</id>
        <title type="html">New tool: Get most likely co-occurrences for words</title>
        <content type="xhtml" xml:base="http://www.topicalizer.com/serendipity/">
            <div xmlns="http://www.w3.org/1999/xhtml">
                The new tool available under the URL <a href="http://www.topicalizer.com/coOccurrences/"  title="Get co-occurrences">http://www.topicalizer.com/coOccurrences/</a> tries to guess the words that are most likely to co-occur with the words you entered. That is, if you enter 'president' for example, the software will offer you, amongst others, the word 'kennedy' as possibly occuring in the same context.<br />
This tool draws upon the <a href="http://en.wikipedia.org/wiki/Brown_Corpus"  title="Brown Corpus of Present-Day Edited American English">Brown Corpus of Present-Day Edited American English</a>.<br />
<br />
This new feature is also part of the <a href="http://www.topicalizer.com/api/"  title="Topicalizer API">Topicalizer API</a>. 
            </div>
        </content>
        
    </entry>
    <entry>
        <link href="http://www.topicalizer.com/serendipity/archives/12-New-tool-Augmented-keyword-extraction.html" rel="alternate" title="New tool: Augmented keyword extraction" />
        <author>
            <name>Björn Wilmsmann</name>
            <email>nospam@example.com</email>
        </author>
    
        <published>2006-05-01T02:01:09Z</published>
        <updated>2007-07-16T19:16:23Z</updated>
        <wfw:comment>http://www.topicalizer.com/serendipity/wfwcomment.php?cid=12</wfw:comment>
    
        <slash:comments>0</slash:comments>
        <wfw:commentRss>http://www.topicalizer.com/serendipity/rss.php?version=atom1.0&amp;type=comments&amp;cid=12</wfw:commentRss>
    
            <category scheme="http://www.topicalizer.com/serendipity/categories/1-Topicalizer" label="Topicalizer" term="Topicalizer" />
    
        <id>http://www.topicalizer.com/serendipity/archives/12-guid.html</id>
        <title type="html">New tool: Augmented keyword extraction</title>
        <content type="xhtml" xml:base="http://www.topicalizer.com/serendipity/">
            <div xmlns="http://www.w3.org/1999/xhtml">
                Under <a href="http://www.topicalizer.com/augmentKeywords/"  title="Augment keywords">http://www.topicalizer.com/augmentKeywords/</a> you can enter a sentence, phrase or word (you could possibly also enter longer texts, but the generated results would most probably be too large to make sense), whose keywords will be extracted along with their synonym / hyponym / hypernym relations by using <a href="http://wordnet.princeton.edu/"  title="WordNet">WordNet</a>.<br />
<br />
This new feature is also part of the <a href="http://www.topicalizer.com/api/"  title="Topicalizer API">Topicalizer API</a>. 
            </div>
        </content>
        
    </entry>
    <entry>
        <link href="http://www.topicalizer.com/serendipity/archives/11-Screencast-about-Topicalizer-at-Sawfish-Mango.html" rel="alternate" title="Screencast about Topicalizer at Sawfish Mango" />
        <author>
            <name>Björn Wilmsmann</name>
            <email>nospam@example.com</email>
        </author>
    
        <published>2006-04-28T21:44:35Z</published>
        <updated>2007-07-16T19:16:28Z</updated>
        <wfw:comment>http://www.topicalizer.com/serendipity/wfwcomment.php?cid=11</wfw:comment>
    
        <slash:comments>0</slash:comments>
        <wfw:commentRss>http://www.topicalizer.com/serendipity/rss.php?version=atom1.0&amp;type=comments&amp;cid=11</wfw:commentRss>
    
            <category scheme="http://www.topicalizer.com/serendipity/categories/1-Topicalizer" label="Topicalizer" term="Topicalizer" />
    
        <id>http://www.topicalizer.com/serendipity/archives/11-guid.html</id>
        <title type="html">Screencast about Topicalizer at Sawfish Mango</title>
        <content type="xhtml" xml:base="http://www.topicalizer.com/serendipity/">
            <div xmlns="http://www.w3.org/1999/xhtml">
                There is a new screencast about Topicalizer and how it can be used on a blog called 'Sawfish Mango' (<a href="http://www.sawfishmango.com/"  title="Sawfish Mango">http://www.sawfishmango.com/</a>), please have a look at <a href="http://www.sawfishmango.com/screencasts/mashup_paper.html"  title="Screencast">http://www.sawfishmango.com/screencasts/mashup_paper.html</a> for the screencast and <a href="http://sawfishmango.com/?p=19"  title="Final mashup">http://sawfishmango.com/?p=19</a> for the related article. 
            </div>
        </content>
        
    </entry>
    <entry>
        <link href="http://www.topicalizer.com/serendipity/archives/10-Improved-character-set-handling.html" rel="alternate" title="Improved character set handling" />
        <author>
            <name>Björn Wilmsmann</name>
            <email>nospam@example.com</email>
        </author>
    
        <published>2006-04-25T17:02:26Z</published>
        <updated>2007-07-16T19:16:31Z</updated>
        <wfw:comment>http://www.topicalizer.com/serendipity/wfwcomment.php?cid=10</wfw:comment>
    
        <slash:comments>0</slash:comments>
        <wfw:commentRss>http://www.topicalizer.com/serendipity/rss.php?version=atom1.0&amp;type=comments&amp;cid=10</wfw:commentRss>
    
            <category scheme="http://www.topicalizer.com/serendipity/categories/1-Topicalizer" label="Topicalizer" term="Topicalizer" />
    
        <id>http://www.topicalizer.com/serendipity/archives/10-guid.html</id>
        <title type="html">Improved character set handling</title>
        <content type="xhtml" xml:base="http://www.topicalizer.com/serendipity/">
            <div xmlns="http://www.w3.org/1999/xhtml">
                Topicalizer now detects and displays custom document character sets, where before it simply assumed everything to be ISO-8859-1 or UTF-8. If no custom character set is detected or if plain text is submitted, UTF-8 is used instead.<br />
This improved behaviour regarding character sets leads to an improvement concerning automatic language recognition and the overall analysis as well, especially for languages that contain many special characters like for instance, Norse languages or Russian. 
            </div>
        </content>
        
    </entry>
    <entry>
        <link href="http://www.topicalizer.com/serendipity/archives/9-Topicalizer-listed-at-Buzzshout-and-NEO-Binaries.html" rel="alternate" title="Topicalizer listed at Buzzshout and NEO Binaries" />
        <author>
            <name>Björn Wilmsmann</name>
            <email>nospam@example.com</email>
        </author>
    
        <published>2006-04-22T09:12:30Z</published>
        <updated>2007-07-16T19:16:36Z</updated>
        <wfw:comment>http://www.topicalizer.com/serendipity/wfwcomment.php?cid=9</wfw:comment>
    
        <slash:comments>0</slash:comments>
        <wfw:commentRss>http://www.topicalizer.com/serendipity/rss.php?version=atom1.0&amp;type=comments&amp;cid=9</wfw:commentRss>
    
            <category scheme="http://www.topicalizer.com/serendipity/categories/1-Topicalizer" label="Topicalizer" term="Topicalizer" />
    
        <id>http://www.topicalizer.com/serendipity/archives/9-guid.html</id>
        <title type="html">Topicalizer listed at Buzzshout and NEO Binaries</title>
        <content type="xhtml" xml:base="http://www.topicalizer.com/serendipity/">
            <div xmlns="http://www.w3.org/1999/xhtml">
                Topicalizer is now listed at <a href="http://www.buzzshout.com/"  title="Buzzshout">http://www.buzzshout.com/</a> and <a href="http://www.neobinaries.com/"  title="NEO Binaries">http://www.neobinaries.com/</a>:<br />
<a href="http://www.buzzshout.com/listing.php?name=Topicalizer"  title="Topicalizer">http://www.buzzshout.com/listing.php?name=Topicalizer</a><br />
<a href="http://www.neobinaries.com/apps/Category/Miscellaneous/Topicalizer.aspx"  title="Topicalizer">http://www.neobinaries.com/apps/Category/Miscellaneous/Topicalizer.aspx</a><br />
<br />
Buzzshout and NEO Binaries both are websites which present new products related to what is now commonly known as 'Web 2.0' and have them reviewed by their community. 
            </div>
        </content>
        
    </entry>
    <entry>
        <link href="http://www.topicalizer.com/serendipity/archives/8-Stopword-related-bug-fixed.html" rel="alternate" title="Stopword-related bug fixed" />
        <author>
            <name>Björn Wilmsmann</name>
            <email>nospam@example.com</email>
        </author>
    
        <published>2006-04-20T22:07:26Z</published>
        <updated>2007-07-16T19:16:40Z</updated>
        <wfw:comment>http://www.topicalizer.com/serendipity/wfwcomment.php?cid=8</wfw:comment>
    
        <slash:comments>0</slash:comments>
        <wfw:commentRss>http://www.topicalizer.com/serendipity/rss.php?version=atom1.0&amp;type=comments&amp;cid=8</wfw:commentRss>
    
            <category scheme="http://www.topicalizer.com/serendipity/categories/1-Topicalizer" label="Topicalizer" term="Topicalizer" />
    
        <id>http://www.topicalizer.com/serendipity/archives/8-guid.html</id>
        <title type="html">Stopword-related bug fixed</title>
        <content type="xhtml" xml:base="http://www.topicalizer.com/serendipity/">
            <div xmlns="http://www.w3.org/1999/xhtml">
                There was a bug that prevented stopwords from being recognised correctly when occuring right before a sentence boundary. This issue has just been solved, so stopword recognition should be even more reliable. 
            </div>
        </content>
        
    </entry>
    <entry>
        <link href="http://www.topicalizer.com/serendipity/archives/7-XML-parser-bug-fixed.html" rel="alternate" title="XML parser bug fixed" />
        <author>
            <name>Björn Wilmsmann</name>
            <email>nospam@example.com</email>
        </author>
    
        <published>2006-04-19T10:41:36Z</published>
        <updated>2007-07-16T19:16:46Z</updated>
        <wfw:comment>http://www.topicalizer.com/serendipity/wfwcomment.php?cid=7</wfw:comment>
    
        <slash:comments>0</slash:comments>
        <wfw:commentRss>http://www.topicalizer.com/serendipity/rss.php?version=atom1.0&amp;type=comments&amp;cid=7</wfw:commentRss>
    
            <category scheme="http://www.topicalizer.com/serendipity/categories/1-Topicalizer" label="Topicalizer" term="Topicalizer" />
    
        <id>http://www.topicalizer.com/serendipity/archives/7-guid.html</id>
        <title type="html">XML parser bug fixed</title>
        <content type="xhtml" xml:base="http://www.topicalizer.com/serendipity/">
            <div xmlns="http://www.w3.org/1999/xhtml">
                Today I have fixed a bug that occasionally led to JavaScript and CSS not being filtered before analysing an HTML document. Now JavaScript and CSS elements are removed correctly before the actual analysis is conducted, so they do not falsify the results anymore. 
            </div>
        </content>
        
    </entry>

</feed>