<?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: Searching l10n</title>
	<atom:link href="http://blog.mozilla.com/axel/2009/06/02/searching-l10n/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.mozilla.com/axel/2009/06/02/searching-l10n/</link>
	<description>Free your mind and your ass will follow.</description>
	<lastBuildDate>Tue, 07 Feb 2012 10:14:33 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.2.1</generator>
	<item>
		<title>By: Staś Małolepszy</title>
		<link>http://blog.mozilla.com/axel/2009/06/02/searching-l10n/comment-page-1/#comment-1707</link>
		<dc:creator>Staś Małolepszy</dc:creator>
		<pubDate>Thu, 04 Jun 2009 13:49:16 +0000</pubDate>
		<guid isPermaLink="false">http://blog.mozilla.com/axel/?p=176#comment-1707</guid>
		<description>I wonder if it would make sense to optimize this only for opt-in revisions. I have to admit that I&#039;m not sure how this would look like, but I have a feeling that searching in or between milestones would be more common than on or between specific dates or revision ids. And by taking only opt-in revisions we would radically limit the size of data to store.</description>
		<content:encoded><![CDATA[<p>I wonder if it would make sense to optimize this only for opt-in revisions. I have to admit that I&#8217;m not sure how this would look like, but I have a feeling that searching in or between milestones would be more common than on or between specific dates or revision ids. And by taking only opt-in revisions we would radically limit the size of data to store.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Axel Hecht</title>
		<link>http://blog.mozilla.com/axel/2009/06/02/searching-l10n/comment-page-1/#comment-1705</link>
		<dc:creator>Axel Hecht</dc:creator>
		<pubDate>Thu, 04 Jun 2009 09:42:10 +0000</pubDate>
		<guid isPermaLink="false">http://blog.mozilla.com/axel/?p=176#comment-1705</guid>
		<description>Not sure how easy it would be to search in a particular revision.

I&#039;m kinda torn on whether each entity needs to be in its own document. Your use cases make it sound more likely that it does. We&#039;ll probably just need to try and see if that&#039;s feasible in terms of index size and performance.</description>
		<content:encoded><![CDATA[<p>Not sure how easy it would be to search in a particular revision.</p>
<p>I&#8217;m kinda torn on whether each entity needs to be in its own document. Your use cases make it sound more likely that it does. We&#8217;ll probably just need to try and see if that&#8217;s feasible in terms of index size and performance.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Staś Małolepszy</title>
		<link>http://blog.mozilla.com/axel/2009/06/02/searching-l10n/comment-page-1/#comment-1704</link>
		<dc:creator>Staś Małolepszy</dc:creator>
		<pubDate>Thu, 04 Jun 2009 09:14:00 +0000</pubDate>
		<guid isPermaLink="false">http://blog.mozilla.com/axel/?p=176#comment-1704</guid>
		<description>So, it&#039;s basically an MXR, but across all revisions? If so, then yes, please! :)

Two suggestions:
- make it easy to search only in the tip
- make it aware of the opt-in revisions for milestones. It would be awesome to be able to query for translations of a given entity in a given milestone for every locale (especially for things in region.properties and searchplugins, you guessed it)</description>
		<content:encoded><![CDATA[<p>So, it&#8217;s basically an MXR, but across all revisions? If so, then yes, please! :)</p>
<p>Two suggestions:<br />
- make it easy to search only in the tip<br />
- make it aware of the opt-in revisions for milestones. It would be awesome to be able to query for translations of a given entity in a given milestone for every locale (especially for things in region.properties and searchplugins, you guessed it)</p>
]]></content:encoded>
	</item>
</channel>
</rss>

