[Freelance Traveller] Issue 006 Available for Download

[FreeTrav]

The June 2010 issue of Freelance Traveller is ready for download. Sixteen pages have been assembled for your enjoyment, including some excellent renders of a Grav Tank by MAG, and a spotlight on Second Life Traveller by Jeffrey Schwartz.

You can download this issue from http://www.freelancetraveller.com/magazine, or from our mirror site at http://freelancetraveller.downport.com (follow the links to the magazine downloads from the start page - because of certain implementation details, a direct URL doesn't work).

edited to remove comma from url - it should work now...

 

[BP]

The first link does not work as you included the trailing comma in the URL...

Directly linking to the ANSI URL gave an error the first time (file not beginning with %PDF-, though that seems unlikely), but worked the next several tries.

http://www.freelancetraveller.com/magazine/
http://www.freelancetraveller.com/magazine/FT006-201006-ANSI-A.pdf
http://www.freelancetraveller.com/magazine/FT006-201006-ISO-A4.pdf

P.S. - instead of:
Download the current issue: ANSI A (US Letter) format or ISO A4 format
explicitly include issue and date as well, like:
Download the current issue: Issue 005 - June 2010 ANSI A (US Letter) format or Issue 005 - May 2010 ISO A4 format

 

[FreeTrav]

The first link does not work as you included the trailing comma in the URL...

Sorry about that; didn't notice that that had happened. I was relying on the forums own smart-URL-parsing. I still disagree with the spec that says that a comma is a legal character for a URL... :? Fixed.

Directly linking to the ANSI URL gave an error the first time (file not beginning with %PDF-, though that seems unlikely), but worked the next several tries.

This is very odd. I had similar effects on both the main site and the Downport mirror when I was posting the updates (and the new issue) to the site. I would say, on that basis, that there's some sort of wide net.problem.

http://www.freelancetraveller.com/magazine/
http://www.freelancetraveller.com/magazine/FT006-201006-ANSI-A.pdf
http://www.freelancetraveller.com/magazine/FT006-201006-ISO-A4.pdf

P.S. - instead of:
Download the current issue: ANSI A (US Letter) format or ISO A4 format
explicitly include issue and date as well, like:
Download the current issue: Issue 005 - June 2010 ANSI A (US Letter) format or Issue 005 - May 2010 ISO A4 format

An interesting thought. I've pretty much got that page set up so that all I have to do is update the table of contents in the center; that's done manually, as I still use FrontPage for maintaining the site master copy, and there is not one CMS that doesn't either turn the site to {CENSORED} or get turned to {CENSORED} when FP posts to the site - even if I'm using ftp (as I do) rather than the FrontPage Server Excretions [sic].

 

[BP]

... on that basis, that there's some sort of wide net.problem.

Nope. :lol:

(host pragma's perhaps...)

 

[FreeTrav]

... on that basis, that there's some sort of wide net.problem.

Nope. :lol:

(host pragma's perhaps...)

I'd thought of that, too, but it seemed ... unlikely ... that both my primary host and Downport would have the same sort of problems at the same time. And equally unlikely that you and I would, as well, if it was at the client end.

 

[BP]

Actually, just the opposite is true - hosts are indeed just as likely to share common issues with atypical files - that is the nature of modern copy & paste development. Further, we are probably both using Adobe Acrobat (and within a browser?) for viewing...

Looking at the content of your files - the header looks suspicious. I notice they are linearized version 6 (1.5) PDF format - but the header comment is followed by a CR/LF rather than just CR. The following four bytes are correctly over 0x80 (indicating file includes binary content), but the LF is not - when first opened within a browser, that may be confusing the MIME embedded Adobe (later open actions mechanism already knows the app and does not require the App to 'reply'). Normally, Adobe ignores LF following a CR, but this position is reserved for 4 byte binary indicator.

It is possible your PDF creation program (looks like Office 2007 w/PDF export/printer?) or uploading mechanism (or host) is converting 0x0D (CR) to 0x0D + 0x0A (CRLF), which is confusing embedded Adobe on initial open (outside cache mechanism - hence, also a possible correlation with host pragma settings). Also, if the PDF had been opened in any other program prior to uploading.