<?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"
	>
<channel>
	<title>Comments on: Work-around for Outlook attachment problems</title>
	<atom:link href="http://www.hawkwings.net/2006/04/22/work-around-for-outlook-attachment-problems/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.hawkwings.net/2006/04/22/work-around-for-outlook-attachment-problems/</link>
	<description>Tips and add-ons to make Apple Mail / Mail.app even better</description>
	<pubDate>Thu, 08 Jan 2009 00:52:23 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.5.1</generator>
		<item>
		<title>By: Jon</title>
		<link>http://www.hawkwings.net/2006/04/22/work-around-for-outlook-attachment-problems/#comment-2809</link>
		<dc:creator>Jon</dc:creator>
		<pubDate>Mon, 24 Apr 2006 14:20:02 +0000</pubDate>
		<guid isPermaLink="false">http://www.hawkwings.net/2006/04/22/work-around-for-outlook-attachment-problems/#comment-2809</guid>
		<description>Damn :(</description>
		<content:encoded><![CDATA[<p>Damn :(</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Tim</title>
		<link>http://www.hawkwings.net/2006/04/22/work-around-for-outlook-attachment-problems/#comment-2807</link>
		<dc:creator>Tim</dc:creator>
		<pubDate>Mon, 24 Apr 2006 14:12:51 +0000</pubDate>
		<guid isPermaLink="false">http://www.hawkwings.net/2006/04/22/work-around-for-outlook-attachment-problems/#comment-2807</guid>
		<description>Jon, you would think so. But in fact, it doesn't seem to help much for many people:

http://discussions.apple.com/thread.jspa?messageID=2138572&#2138572</description>
		<content:encoded><![CDATA[<p>Jon, you would think so. But in fact, it doesn&#8217;t seem to help much for many people:</p>
<p><a href="http://discussions.apple.com/thread.jspa?messageID=2138572&#2138572" rel="nofollow">http://discussions.apple.com/thread.jspa?messageID=2138572&#2138572</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jon</title>
		<link>http://www.hawkwings.net/2006/04/22/work-around-for-outlook-attachment-problems/#comment-2806</link>
		<dc:creator>Jon</dc:creator>
		<pubDate>Mon, 24 Apr 2006 14:00:37 +0000</pubDate>
		<guid isPermaLink="false">http://www.hawkwings.net/2006/04/22/work-around-for-outlook-attachment-problems/#comment-2806</guid>
		<description>Check out "Send Windows Friendly Attachment" options when adding a file with the attachment button (not available via drag and drop)

jon</description>
		<content:encoded><![CDATA[<p>Check out &#8220;Send Windows Friendly Attachment&#8221; options when adding a file with the attachment button (not available via drag and drop)</p>
<p>jon</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Dan Ridley</title>
		<link>http://www.hawkwings.net/2006/04/22/work-around-for-outlook-attachment-problems/#comment-2778</link>
		<dc:creator>Dan Ridley</dc:creator>
		<pubDate>Sat, 22 Apr 2006 17:07:10 +0000</pubDate>
		<guid isPermaLink="false">http://www.hawkwings.net/2006/04/22/work-around-for-outlook-attachment-problems/#comment-2778</guid>
		<description>The inverse problem happens too: if Outlook senders are using Outlook's "Rich Text" format instead of HTML, the attachments will often arrive inside "winmail.dat" files, which are difficult to open. (There's a program called &lt;a href="http://www.joshjacob.com/macdev/tnef/" rel="nofollow"&gt;TNEF's Enough&lt;/a&gt; which can extract the contents of those files, though.)

&lt;blockquote&gt;For some reason InDesign steadfastly refuses to see them as InDesign Tagged Text and places the entire code of the file as a plain text frame.&lt;/blockquote&gt;
If the files do import into InDesign from the original machine, I'd suggest zipping the files before you e-mail them. This usually fixes problems with plain-text formats getting mangled. 

The InDesign Tagged Text format is a bit tricky with regard to text encoding. In particular, the encoding tag at the top has some special requirements, and your line endings must match the platform that your encoding tag specifies. &lt;a href="http://support.adobe.com/devsup/devsup.nsf/docs/54161.htm" rel="nofollow"&gt;This knowledge base article&lt;/a&gt; is your friend.</description>
		<content:encoded><![CDATA[<p>The inverse problem happens too: if Outlook senders are using Outlook&#8217;s &#8220;Rich Text&#8221; format instead of HTML, the attachments will often arrive inside &#8220;winmail.dat&#8221; files, which are difficult to open. (There&#8217;s a program called <a href="http://www.joshjacob.com/macdev/tnef/" rel="nofollow">TNEF&#8217;s Enough</a> which can extract the contents of those files, though.)</p>
<blockquote><p>For some reason InDesign steadfastly refuses to see them as InDesign Tagged Text and places the entire code of the file as a plain text frame.</p></blockquote>
<p>If the files do import into InDesign from the original machine, I&#8217;d suggest zipping the files before you e-mail them. This usually fixes problems with plain-text formats getting mangled. </p>
<p>The InDesign Tagged Text format is a bit tricky with regard to text encoding. In particular, the encoding tag at the top has some special requirements, and your line endings must match the platform that your encoding tag specifies. <a href="http://support.adobe.com/devsup/devsup.nsf/docs/54161.htm" rel="nofollow">This knowledge base article</a> is your friend.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Tim</title>
		<link>http://www.hawkwings.net/2006/04/22/work-around-for-outlook-attachment-problems/#comment-2768</link>
		<dc:creator>Tim</dc:creator>
		<pubDate>Sat, 22 Apr 2006 13:46:05 +0000</pubDate>
		<guid isPermaLink="false">http://www.hawkwings.net/2006/04/22/work-around-for-outlook-attachment-problems/#comment-2768</guid>
		<description>Interesting. I wonder why.

No doubt you are using Plain Text as the default format already.</description>
		<content:encoded><![CDATA[<p>Interesting. I wonder why.</p>
<p>No doubt you are using Plain Text as the default format already.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Dan Warne</title>
		<link>http://www.hawkwings.net/2006/04/22/work-around-for-outlook-attachment-problems/#comment-2767</link>
		<dc:creator>Dan Warne</dc:creator>
		<pubDate>Sat, 22 Apr 2006 13:28:25 +0000</pubDate>
		<guid isPermaLink="false">http://www.hawkwings.net/2006/04/22/work-around-for-outlook-attachment-problems/#comment-2767</guid>
		<description>I do have some problems with Apple Mail attachments too. Every month I extract a large text file from a database, which is actually InDesign Tagged Text, ready to be placed into a layout. It is extracted from the database via a web-interface. On the odd occasion that I have saved it on my Mac desktop (from Safari or Firefox) and then attached it to an Apple Mail mail and sent it to myself at work, the files haven't placed correctly. For some reason InDesign steadfastly refuses to see them as InDesign Tagged Text and places the entire code of the file as a plain text frame.  

I haven't figured out if it's a Mac character encoding issue of some sort, or whether Apple Mail manages to mangle it somehow along the way.</description>
		<content:encoded><![CDATA[<p>I do have some problems with Apple Mail attachments too. Every month I extract a large text file from a database, which is actually InDesign Tagged Text, ready to be placed into a layout. It is extracted from the database via a web-interface. On the odd occasion that I have saved it on my Mac desktop (from Safari or Firefox) and then attached it to an Apple Mail mail and sent it to myself at work, the files haven&#8217;t placed correctly. For some reason InDesign steadfastly refuses to see them as InDesign Tagged Text and places the entire code of the file as a plain text frame.  </p>
<p>I haven&#8217;t figured out if it&#8217;s a Mac character encoding issue of some sort, or whether Apple Mail manages to mangle it somehow along the way.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

<!-- Dynamic Page Served (once) in 0.236 seconds -->
