<?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: Mastering Master Pages</title>
	<atom:link href="http://planetquark.com/2007/08/31/mastering-master-pages/feed/" rel="self" type="application/rss+xml" />
	<link>http://planetquark.com/2007/08/31/mastering-master-pages/</link>
	<description>by Quark users for Quark users</description>
	<lastBuildDate>Tue, 16 Mar 2010 16:47:11 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: GloomCookie</title>
		<link>http://planetquark.com/2007/08/31/mastering-master-pages/comment-page-1/#comment-152</link>
		<dc:creator>GloomCookie</dc:creator>
		<pubDate>Tue, 18 Sep 2007 17:09:02 +0000</pubDate>
		<guid isPermaLink="false">http://planetquark.com/2007/08/31/mastering-master-pages/#comment-152</guid>
		<description>yeah, but its still too easy to circumvent the 2 layer trick by forgetting to relock the default layer.

We&#039;re doing it (using 2 layers) in my shop, but its just not solving the problem.

Maybe Quark 8? Or better yet, 7.4?
A man can dream...</description>
		<content:encoded><![CDATA[<p>yeah, but its still too easy to circumvent the 2 layer trick by forgetting to relock the default layer.</p>
<p>We&#8217;re doing it (using 2 layers) in my shop, but its just not solving the problem.</p>
<p>Maybe Quark 8? Or better yet, 7.4?<br />
A man can dream&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Rob</title>
		<link>http://planetquark.com/2007/08/31/mastering-master-pages/comment-page-1/#comment-151</link>
		<dc:creator>Rob</dc:creator>
		<pubDate>Tue, 18 Sep 2007 16:41:54 +0000</pubDate>
		<guid isPermaLink="false">http://planetquark.com/2007/08/31/mastering-master-pages/#comment-151</guid>
		<description>GloomCookie,
You are correct that you can&#039;t lock a Master Page item so that it is only editable on the Master Page. However, check out Alistair Dabbs&#039; post on Locking Items vs Locking Layers. I think using layers would be a better solution for you.</description>
		<content:encoded><![CDATA[<p>GloomCookie,<br />
You are correct that you can&#8217;t lock a Master Page item so that it is only editable on the Master Page. However, check out Alistair Dabbs&#8217; post on Locking Items vs Locking Layers. I think using layers would be a better solution for you.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: GloomCookie</title>
		<link>http://planetquark.com/2007/08/31/mastering-master-pages/comment-page-1/#comment-144</link>
		<dc:creator>GloomCookie</dc:creator>
		<pubDate>Fri, 14 Sep 2007 14:55:33 +0000</pubDate>
		<guid isPermaLink="false">http://planetquark.com/2007/08/31/mastering-master-pages/#comment-144</guid>
		<description>Ok... when you say &quot;lock all items on Master Pages&quot; are you specifically referring to a new feature in v.7? Because (as far as i know) there is no way to lock a master item so that it can ONLY BE edited on its master page. 

Its still too easy to circumvent the 2 layer trick by forgetting to relock the default layer.

Which to me is the Achilles&#039; heel of QXP.</description>
		<content:encoded><![CDATA[<p>Ok&#8230; when you say &#8220;lock all items on Master Pages&#8221; are you specifically referring to a new feature in v.7? Because (as far as i know) there is no way to lock a master item so that it can ONLY BE edited on its master page. </p>
<p>Its still too easy to circumvent the 2 layer trick by forgetting to relock the default layer.</p>
<p>Which to me is the Achilles&#8217; heel of QXP.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Rob</title>
		<link>http://planetquark.com/2007/08/31/mastering-master-pages/comment-page-1/#comment-123</link>
		<dc:creator>Rob</dc:creator>
		<pubDate>Sat, 08 Sep 2007 18:33:21 +0000</pubDate>
		<guid isPermaLink="false">http://planetquark.com/2007/08/31/mastering-master-pages/#comment-123</guid>
		<description>GloomCookie,
The quick answer is yes. I have seen some pretty amazing scripts written in my day. This one may be a bit tricky, but it could be done. The better answer is to lock all of the items on Master Pages. That way you will not be tempted to use something that is on the Master page. If you really need a certain item, go to the master page, unlock it, copy it, relock it, then go paste it where it is needed. I would also recommend starting to work in this manner on a new document. If you haven&#039;t been working like this in the past it could have disastrous consequences on your old pages. But now that you understand it, give it a shot!
Rob</description>
		<content:encoded><![CDATA[<p>GloomCookie,<br />
The quick answer is yes. I have seen some pretty amazing scripts written in my day. This one may be a bit tricky, but it could be done. The better answer is to lock all of the items on Master Pages. That way you will not be tempted to use something that is on the Master page. If you really need a certain item, go to the master page, unlock it, copy it, relock it, then go paste it where it is needed. I would also recommend starting to work in this manner on a new document. If you haven&#8217;t been working like this in the past it could have disastrous consequences on your old pages. But now that you understand it, give it a shot!<br />
Rob</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: GloomCookie</title>
		<link>http://planetquark.com/2007/08/31/mastering-master-pages/comment-page-1/#comment-115</link>
		<dc:creator>GloomCookie</dc:creator>
		<pubDate>Fri, 07 Sep 2007 20:10:29 +0000</pubDate>
		<guid isPermaLink="false">http://planetquark.com/2007/08/31/mastering-master-pages/#comment-115</guid>
		<description>is there a scriptable way to identify items that have had their link broken? I&#039;m tempted to turn on &quot;delete changes&quot;, but I&#039;m nervous it may override an intentionally broken link.</description>
		<content:encoded><![CDATA[<p>is there a scriptable way to identify items that have had their link broken? I&#8217;m tempted to turn on &#8220;delete changes&#8221;, but I&#8217;m nervous it may override an intentionally broken link.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Locking Items vs Locking Layers</title>
		<link>http://planetquark.com/2007/08/31/mastering-master-pages/comment-page-1/#comment-112</link>
		<dc:creator>Locking Items vs Locking Layers</dc:creator>
		<pubDate>Fri, 07 Sep 2007 14:45:23 +0000</pubDate>
		<guid isPermaLink="false">http://planetquark.com/2007/08/31/mastering-master-pages/#comment-112</guid>
		<description>[...] Underwood&#8217;s advice on using Master Pages in QuarkXPress last week should be compulsory reading for anyone working on regular [...]</description>
		<content:encoded><![CDATA[<p>[...] Underwood&#8217;s advice on using Master Pages in QuarkXPress last week should be compulsory reading for anyone working on regular [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>
