Comments on: Writing for the web is not the same as writing for print http://www.badlanguage.net/writing-for-the-web-is-not-the-same-as-writing-for-print How to communicate Sat, 30 Aug 2008 07:02:29 +0000 http://wordpress.org/?v=2.6.1 By: Bad Language / How to make money writing for the web http://www.badlanguage.net/writing-for-the-web-is-not-the-same-as-writing-for-print#comment-408010 Bad Language / How to make money writing for the web Tue, 13 May 2008 13:39:18 +0000 http://www.badlanguage.net/?p=144#comment-408010 [...] forget it - is that writing for the web is not the same as writing for print. Here are some tips: Avoid PDFs, shorter by about 50 per cent compared to print, free of hype or marketing polyfiller, free of long [...] [...] forget it - is that writing for the web is not the same as writing for print. Here are some tips: Avoid PDFs, shorter by about 50 per cent compared to print, free of hype or marketing polyfiller, free of long [...]

]]> By: Bad Language / Want a good website, on time? Prioritise content. http://www.badlanguage.net/writing-for-the-web-is-not-the-same-as-writing-for-print#comment-1039 Bad Language / Want a good website, on time? Prioritise content. Wed, 09 Aug 2006 08:53:12 +0000 http://www.badlanguage.net/?p=144#comment-1039 [...] Writing for the web is not the same as writing for print. In general, write to be scanned not read and reduce the word count by 50 per cent. And don’t use PDFs for core content. [...] [...] Writing for the web is not the same as writing for print. In general, write to be scanned not read and reduce the word count by 50 per cent. And don’t use PDFs for core content. [...]

]]> By: Matthew Stibbe http://www.badlanguage.net/writing-for-the-web-is-not-the-same-as-writing-for-print#comment-217 Matthew Stibbe Wed, 07 Jun 2006 09:39:58 +0000 http://www.badlanguage.net/?p=144#comment-217 You can stop the Firefox crashing when you open a PDF and generally speed up Acobat by following the tips on this page: http://kb.mozillazine.org/Adobe_Reader. However, the fact that you need to get all geeky on it to make it usable underlines how irritating PDFs are! You can stop the Firefox crashing when you open a PDF and generally speed up Acobat by following the tips on this page: http://kb.mozillazine.org/Adobe_Reader. However, the fact that you need to get all geeky on it to make it usable underlines how irritating PDFs are!

]]> By: George http://www.badlanguage.net/writing-for-the-web-is-not-the-same-as-writing-for-print#comment-213 George Tue, 06 Jun 2006 19:48:36 +0000 http://www.badlanguage.net/?p=144#comment-213 I totally agree! PDFs on the web are most annoying - Acrobat takes ages to start even on the fastest computer, displays an annoying logo splash screen and tends to crash firefox. Every time I accidentally click on a PDF link from google I instantly regret it, but I have already lost control, because for the 10 or more seconds you write about the browser does not respond to anything. I'm not sure if I'm the average user, but if you don't want to annoy the likes of me do not put PDFs on your pages, or if you do, mark them clearly as PDF, so I only go there as a last resort. I suppose what's even worse is a Word document... I totally agree! PDFs on the web are most annoying - Acrobat takes ages to start even on the fastest computer, displays an annoying logo splash screen and tends to crash firefox. Every time I accidentally click on a PDF link from google I instantly regret it, but I have already lost control, because for the 10 or more seconds you write about the browser does not respond to anything.

I’m not sure if I’m the average user, but if you don’t want to annoy the likes of me do not put PDFs on your pages, or if you do, mark them clearly as PDF, so I only go there as a last resort.

I suppose what’s even worse is a Word document…

]]>