I've seen similar issues when trying to print to a linux hylafax server, it had something to do with non-standard fonts and the postscript converter. Normally when I had users report the issue to me I would instruct them to change all of the fonts in their document to Arial and then re-print the document to the hylafax fax server. this worked about 99 percent of the time.<br>
<br><br><br><br><blockquote style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;" class="gmail_quote">Message: 6<br>
Date: Tue, 14 Dec 2010 15:03:43 -0500<br>
From: Sean Kilpatrick <<a href="mailto:kilpatms@speakeasy.net">kilpatms@speakeasy.net</a>><br>
Subject: Re: [ale] this week's WTF<br>
To: <a href="mailto:ale@ale.org">ale@ale.org</a><br>
Message-ID: <<a href="mailto:201012141503.43327.kilpatms@speakeasy.net">201012141503.43327.kilpatms@speakeasy.net</a>><br>
Content-Type: text/plain; charset="us-ascii"<br>
<br>
Don't think it is a virus problem. I can save other .doc files as .odt<br>
files with no problem. It is as if this particular file has some sort of<br>
meta data that is screwing up the works. Cups can't process it for the<br>
printer and I can't change the file format to .odt, or pdf, or any other<br>
Micro$oft format.<br>
<br>
I have no clue how to read the meta data on Word files. It is possible that<br>
my wife's Mac has become infected, but that seems unlikely, unless she<br>
contracted the bug through Emory. Then again I haven't heard of any virii<br>
that just screw around with Word files.<br>
<br>
I was able, finally, to Save As an html document and then open and save<br>
that as an .odt file.<br>
<br>
But it would be nice to know how to isolate the actual problem.<br>
<br>
Sean</blockquote>