<?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: Developing ExtendScripts &#8211; Part 1</title>
	<atom:link href="http://blogs.adobe.com/tcs/2011/01/uncategorized/developing-extendedscripts-part-1.html/feed" rel="self" type="application/rss+xml" />
	<link>http://blogs.adobe.com/tcs/2011/01/uncategorized/developing-extendedscripts-part-1.html</link>
	<description>Find the latest information nuggets, tips and tricks, and other updates related to the Adobe Technical Communication Suite.</description>
	<lastBuildDate>Wed, 24 Apr 2013 12:04:04 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.5.1</generator>
	<item>
		<title>By: Alain Pierrot</title>
		<link>http://blogs.adobe.com/tcs/2011/01/uncategorized/developing-extendedscripts-part-1.html#comment-3719</link>
		<dc:creator>Alain Pierrot</dc:creator>
		<pubDate>Sat, 25 Feb 2012 16:46:22 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.adobe.com/tcs/?p=242#comment-3719</guid>
		<description><![CDATA[Hello,

I have an issue with ESTK 3.6, MacOSX 10.7.3 Lion and InDesign CS5.5 (7.5.2): ESTK can&#039;t be used (bad path to ressources, seemingly).

MacOS console tells:
Adobe InDesign CS5.5: CFURLCreateWithBytes was passed these invalid URLBytes: &#039;/Applications/Adobe InDesign CS5.5/Adobe InDesign CS5.5.app/Contents/Frameworks&#039; (a file system path instead of an URL string). The URL created will not work with most file URL functions. CFURLCreateFromFileSystemRepresentation should be used instead.

Is there any patch? workaround?

Thanks for any help!]]></description>
		<content:encoded><![CDATA[<p>Hello,</p>
<p>I have an issue with ESTK 3.6, MacOSX 10.7.3 Lion and InDesign CS5.5 (7.5.2): ESTK can&#8217;t be used (bad path to ressources, seemingly).</p>
<p>MacOS console tells:<br />
Adobe InDesign CS5.5: CFURLCreateWithBytes was passed these invalid URLBytes: &#8216;/Applications/Adobe InDesign CS5.5/Adobe InDesign CS5.5.app/Contents/Frameworks&#8217; (a file system path instead of an URL string). The URL created will not work with most file URL functions. CFURLCreateFromFileSystemRepresentation should be used instead.</p>
<p>Is there any patch? workaround?</p>
<p>Thanks for any help!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Tweets that mention Developing ExtendScripts – Part 1 « Technical Communication Suite -- Topsy.com</title>
		<link>http://blogs.adobe.com/tcs/2011/01/uncategorized/developing-extendedscripts-part-1.html#comment-255</link>
		<dc:creator>Tweets that mention Developing ExtendScripts – Part 1 « Technical Communication Suite -- Topsy.com</dc:creator>
		<pubDate>Mon, 31 Jan 2011 13:33:48 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.adobe.com/tcs/?p=242#comment-255</guid>
		<description><![CDATA[[...] This post was mentioned on Twitter by Lieve Weymeis and Ankur Jain, Nandini Gupta. Nandini Gupta said: Here’s how to automate tasks using ExtendScript Toolkit in #AdobeTCS http://adobe.ly/g1Hmua http://adobe.ly/fnSXwy http://adobe.ly/gL3jK6 [...]]]></description>
		<content:encoded><![CDATA[<p>[...] This post was mentioned on Twitter by Lieve Weymeis and Ankur Jain, Nandini Gupta. Nandini Gupta said: Here’s how to automate tasks using ExtendScript Toolkit in #AdobeTCS <a href="http://adobe.ly/g1Hmua" rel="nofollow">http://adobe.ly/g1Hmua</a> <a href="http://adobe.ly/fnSXwy" rel="nofollow">http://adobe.ly/fnSXwy</a> <a href="http://adobe.ly/gL3jK6" rel="nofollow">http://adobe.ly/gL3jK6</a> [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Erste Schritte mit ExtendScript &#8211; FrameMaker-Automation mit FrameScript &#38; ExtendScript</title>
		<link>http://blogs.adobe.com/tcs/2011/01/uncategorized/developing-extendedscripts-part-1.html#comment-236</link>
		<dc:creator>Erste Schritte mit ExtendScript &#8211; FrameMaker-Automation mit FrameScript &#38; ExtendScript</dc:creator>
		<pubDate>Fri, 21 Jan 2011 08:11:40 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.adobe.com/tcs/?p=242#comment-236</guid>
		<description><![CDATA[[...] Part 1: ExtendScript Toolkit (ESTK), Hello-World-Programm, eine erste Funkion [...]]]></description>
		<content:encoded><![CDATA[<p>[...] Part 1: ExtendScript Toolkit (ESTK), Hello-World-Programm, eine erste Funkion [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Developing ExtendedScripts &#8211; Part 2 &#171; Technical Communication Suite</title>
		<link>http://blogs.adobe.com/tcs/2011/01/uncategorized/developing-extendedscripts-part-1.html#comment-234</link>
		<dc:creator>Developing ExtendedScripts &#8211; Part 2 &#171; Technical Communication Suite</dc:creator>
		<pubDate>Fri, 21 Jan 2011 05:02:19 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.adobe.com/tcs/?p=242#comment-234</guid>
		<description><![CDATA[[...] you are very new to ESTK, I suggest you to read the first blog entry in this series. In the first blog entry, we didn&#8217;t use any functions that are specific to any [...]]]></description>
		<content:encoded><![CDATA[<p>[...] you are very new to ESTK, I suggest you to read the first blog entry in this series. In the first blog entry, we didn&#8217;t use any functions that are specific to any [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>
