From allan@macromates.com Tue Apr 19 01:30:12 2005
From: Allan Odgaard <allan@macromates.com>
To: textmate@lists.macromates.com
Subject: Re: [TxMt] context output to html
Date: Tue, 19 Apr 2005 03:30:08 +0200
Message-ID: <a7124b2001cdce15fe617746ba396bf8@macromates.com>
In-Reply-To: <2ef25e9bb0c0fbbab46dd99c611d65f3@mac.com>
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="===============3488277485877443951=="

--===============3488277485877443951==
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit

On Apr 7, 2005, at 19:04, Robert Ullrey wrote:

> Thanks Allan, but neither suggestion worked to get the pdf into the  
> browser. I am still getting the output pdf as I should, the script  
> just does not seem to see it. Not sure where the problem is. I'll look  
> more this weekend.

I'm currently having the problem that the HTML output refuses to follow  
any redirects to file:// which does cause a similar problem. This  
probably happened after one of the last system updates.

As a workaround I changed the redirect command to go through localhost  
like this:

[ -s ${tmp}.pdf ] && { cp "$tmp" ~/Sites/web_kit_workaround.pdf; chmod  
666 ~/Sites/web_kit_workaround.pdf; echo  
"</pre><script>window.location='http://localhost/~$USER/ 
web_kit_workaround.pdf'</script>"; }

Now it follows the redirect again, but unfortunately the PDF plugin  
doesn't work, it freezes after showing “Loading...”, but this is also  
the case when loading the PDF in Safari (and OmniWeb crashes). I did  
try the latest 2.2 of the plugin.

Well... hopefully the rumored native PDF capability in Tiger will make  
the actual rendering work. But I'm not sure what to do about not being  
able to do a file://-redirect.


--===============3488277485877443951==--