<?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: Inconvenient Pages List Name</title>
	<atom:link href="http://blog.mastykarz.nl/inconvenient-pages-list-name/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.mastykarz.nl/inconvenient-pages-list-name/</link>
	<description>Innovation Matters &#124; SharePoint Server MVP &#124; ISSN 2210-9390</description>
	<lastBuildDate>Thu, 09 Feb 2012 05:22:29 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.2.1</generator>
	<item>
		<title>By: Waldek Mastykarz</title>
		<link>http://blog.mastykarz.nl/inconvenient-pages-list-name/comment-page-1/#comment-69533</link>
		<dc:creator>Waldek Mastykarz</dc:creator>
		<pubDate>Fri, 11 Feb 2011 17:25:21 +0000</pubDate>
		<guid isPermaLink="false">http://blog.mastykarz.nl/inconvenient-pages-list-name/#comment-69533</guid>
		<description>@Arjaan: you should be able to do this using the name from the Resource string. In such case SharePoint should automatically take care of the translation to right name.</description>
		<content:encoded><![CDATA[<p>@Arjaan: you should be able to do this using the name from the Resource string. In such case SharePoint should automatically take care of the translation to right name.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Arjaan den Ouden</title>
		<link>http://blog.mastykarz.nl/inconvenient-pages-list-name/comment-page-1/#comment-69527</link>
		<dc:creator>Arjaan den Ouden</dc:creator>
		<pubDate>Fri, 11 Feb 2011 15:58:23 +0000</pubDate>
		<guid isPermaLink="false">http://blog.mastykarz.nl/inconvenient-pages-list-name/#comment-69527</guid>
		<description>It&#039;s even worse. Our NL MOSS 2007 page library is called &quot;Pagina&#039;s&quot;. 

Do you have suggestion on how to use the right listname when adding a webpart to a page. E.g. a &#039;sticky&#039; webpart in a page layout? I&#039;ve got a webpart that inherits from the ContentByQueryWebpart and needs the ListName as an attribute.</description>
		<content:encoded><![CDATA[<p>It&#039;s even worse. Our NL MOSS 2007 page library is called &#034;Pagina&#039;s&#034;. </p>
<p>Do you have suggestion on how to use the right listname when adding a webpart to a page. E.g. a &#039;sticky&#039; webpart in a page layout? I&#039;ve got a webpart that inherits from the ContentByQueryWebpart and needs the ListName as an attribute.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Waldek Mastykarz</title>
		<link>http://blog.mastykarz.nl/inconvenient-pages-list-name/comment-page-1/#comment-51334</link>
		<dc:creator>Waldek Mastykarz</dc:creator>
		<pubDate>Fri, 16 Jul 2010 13:29:50 +0000</pubDate>
		<guid isPermaLink="false">http://blog.mastykarz.nl/inconvenient-pages-list-name/#comment-51334</guid>
		<description>@John: Perhaps not all of them but you will definitely have to be careful and do some extra testing while upgrading.</description>
		<content:encoded><![CDATA[<p>@John: Perhaps not all of them but you will definitely have to be careful and do some extra testing while upgrading.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: John Bruin</title>
		<link>http://blog.mastykarz.nl/inconvenient-pages-list-name/comment-page-1/#comment-51332</link>
		<dc:creator>John Bruin</dc:creator>
		<pubDate>Fri, 16 Jul 2010 13:23:07 +0000</pubDate>
		<guid isPermaLink="false">http://blog.mastykarz.nl/inconvenient-pages-list-name/#comment-51332</guid>
		<description>Hi Waldek, 

How is life?

I hadn&#039;t read this post yet but I was just thinking the same when I was browsing some old code last week.

I am sure that almost all of our NL MOSS 2007 solutions will break on this... Good to know!

Cheers!</description>
		<content:encoded><![CDATA[<p>Hi Waldek, </p>
<p>How is life?</p>
<p>I hadn&#039;t read this post yet but I was just thinking the same when I was browsing some old code last week.</p>
<p>I am sure that almost all of our NL MOSS 2007 solutions will break on this&#8230; Good to know!</p>
<p>Cheers!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Using SharePoint for Your Intranet; Best Office 2010 Features; Consumer Now Rules Tech Market - SharePoint Daily - Bamboo Nation</title>
		<link>http://blog.mastykarz.nl/inconvenient-pages-list-name/comment-page-1/#comment-49522</link>
		<dc:creator>Using SharePoint for Your Intranet; Best Office 2010 Features; Consumer Now Rules Tech Market - SharePoint Daily - Bamboo Nation</dc:creator>
		<pubDate>Tue, 15 Jun 2010 13:07:00 +0000</pubDate>
		<guid isPermaLink="false">http://blog.mastykarz.nl/inconvenient-pages-list-name/#comment-49522</guid>
		<description>[...] Inconvenient Pages List Name (Waldek Mastykarz)While working on Microsoft Office SharePoint Server (MOSS) 2007 Web Content Management (WCM) Solutions you might have relied on the fact that the name of the Pages Library was always Pages. Well almost always, because in some languages, like German, it was translated along with the Title. Given that fact, changed the way we had to deal with the Pages Library in code. Instead of hard coding the URL part of the Pages Library, all of a sudden we had to retrieve it dynamically, just because someone accidentally translated the URL of the Pages Library. But looking at SharePoint Server 2010 tells us otherwise. Now the URL parts of Pages Libraries in all languages are translated. So was it a mistake in MOSS 2007 that in German the Pages Library was called Seiten or was it a mistake that the Dutch one was called Pages instead of Paginas? [...]</description>
		<content:encoded><![CDATA[<p>[...] Inconvenient Pages List Name (Waldek Mastykarz)While working on Microsoft Office SharePoint Server (MOSS) 2007 Web Content Management (WCM) Solutions you might have relied on the fact that the name of the Pages Library was always Pages. Well almost always, because in some languages, like German, it was translated along with the Title. Given that fact, changed the way we had to deal with the Pages Library in code. Instead of hard coding the URL part of the Pages Library, all of a sudden we had to retrieve it dynamically, just because someone accidentally translated the URL of the Pages Library. But looking at SharePoint Server 2010 tells us otherwise. Now the URL parts of Pages Libraries in all languages are translated. So was it a mistake in MOSS 2007 that in German the Pages Library was called Seiten or was it a mistake that the Dutch one was called Pages instead of Paginas? [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Tweets die vermelden Inconvenient Pages List Name - Waldek Mastykarz -- Topsy.com</title>
		<link>http://blog.mastykarz.nl/inconvenient-pages-list-name/comment-page-1/#comment-49490</link>
		<dc:creator>Tweets die vermelden Inconvenient Pages List Name - Waldek Mastykarz -- Topsy.com</dc:creator>
		<pubDate>Mon, 14 Jun 2010 17:47:23 +0000</pubDate>
		<guid isPermaLink="false">http://blog.mastykarz.nl/inconvenient-pages-list-name/#comment-49490</guid>
		<description>[...] Dit blogartikel was vermeld op Twitter door Waldek Mastykarz, Hire SharePoint Dev. Hire SharePoint Dev heeft gezegd: New post: &#039;Inconvenient Pages List Name&#039; http://tinyurl.com/2wgys5g #SharePoint [...]</description>
		<content:encoded><![CDATA[<p>[...] Dit blogartikel was vermeld op Twitter door Waldek Mastykarz, Hire SharePoint Dev. Hire SharePoint Dev heeft gezegd: New post: &#39;Inconvenient Pages List Name&#39; <a href="http://tinyurl.com/2wgys5g" rel="nofollow">http://tinyurl.com/2wgys5g</a> #SharePoint [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>

