|
I was just writing a proposal for a client and I was using markdown with vim as an editor. I then convert the markdown to a PDF and send that to the client. This works okay but I would like to have a little more control. So I was thinking of just writing it in html since almost everybody has a browser. Are there any downsides to emailing documents as html? |
|||
|
|
|
The downside is that you enter the hell of HTML render engines. Some use Gecko, some use WebKit, some use W3M or Lynx, some use IE, some use the Outlook HTML-fu. In the end you have more control about how the HTML looks on your side, but none of how it looks on your client's side. Why don't you convert the HTML to PDF? |
|||||
|
|
People like the simplicity of one thing : 1 file. If you write any kind of non-trivial html you are going to use multiple files - for the css and images. Hopefully you don't intend to include javascript in a proposal, as it would certainly raise a red-flag of suspicion (as in, is this person trying to do something under the covers?). Also a browser implies publicly viewable files - even though this situation is entirely on the client's machine, it gives the feeling of non-privacy. |
|||
|
|
|
You would have to teach the client something new and potentially scary depending on their level of computer literacy. "Do what with my browser? Open file? Why didn't you just send it to me in word? How can I look at my OWN computer with a web browser? Whats a tab?" yadda etc. Don't confuse the client! What's wrong with txt? (Ha Ha... personal opinion. I know a salesman wouldn't go for txt) |
|||
|
|
