Re: [SL] latex dilemma & blank emails

[Maria G. F. <mg...@ce...>]

It is happening to me too...

Using netscape and pine works great, but when I send the emails to=20
outlook clients, it's blank

Gaby

Dieter Simader wrote:

>brackets and slashes are not in the conversion filter and caused a latex
>error. This is all (?) fixed in 1.8.4
>
>I uploaded an upgrade file for 1.8.3 in the meantime until I release the
>new code.
>
>The blank emails are a case of MS Outlook not being able to decipher
>BASE64 attachments. I am not sure what it is. I used the old BASE64 code
>from the Mailer package at CPAN. This works fine for pine and Netscape.
>
>It would be nice to have feedback from the community at large if this is
>just an isolated case or if everyone using MS Outlook has problems with
>this.
>
>I had a discussion over this with Ralph Dorr who experienced the same
>problem. I had no problems receiving his email attachments but he could
>not read the attachments from SQL-Ledger nor could he read attachments
>sent with pine. So, I concluded that this is not in the code but must be
>something with Outlook. Perhaps a wrong setting or perhaps MS is telling
>the whole world again you better conform to their standards. Wouldn't be
>the first time.
>
>
>Dieter Simader    http://www.sql-ledger.org   (780) 472-8161
>DWS Systems Inc.     Accounting Software       Fax: 478-5281
>=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D On a clear disk you can seek forever =3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
>
>On Fri, 5 Apr 2002, Keith Mastin wrote:
>
>>I didn't have any non-alphanumric characters in the product numbers, bu=
t do have
>>some brackets and slashes in the product descriptions... no underscores=
 or
>>hashes though.  Postscript to screen still gets dvips errors (haven't g=
ot to
>>that yet) but pdf to screen shows something... included below.
>>
>>HTML email is still blank. Printing doesn't do anything, but that could=
 be an
>>unrelated issue.
>>
>>Is there anyone on the list with printing and html email working? (I'm =
looking
>>for a touch of hope here).
>>
>>Thanks
>>
>>%PDF-1.2
>>%=C7=EC?=A2
>>2 0 obj
>><< /Type /Pages /Kids [
>>] /Count 0
>>
>>endobj
>>1 0 obj
>><< /Type /Catalog /Pages 2 0 R
>>
>>endobj
>>3 0 obj
>><< /CreationDate (D:20020405100106)
>>/Producer (GNU Ghostscript 5.50)
>>
>>endobj
>>xref
>>0 4
>>0000000000 65535 f
>>0000000068 00000 n
>>0000000015 00000 n
>>0000000117 00000 n
>>trailer
>><< /Size 4 /Root 1 0 R /Info 3 0 R
>>
>>startxref
>>204
>>%%EOF
>>
>>Quoting Dr Default from [05/04/02 14:24 +0200]:
>>
>>>Tip for user-friendly update: Have the 'add part' routine check if any=
 #
>>>in description and kill it ;-)
>>>
>>>>-----Original Message-----
>>>>From: sql...@sq...=20
>>>>[mailto:sql...@sq...] On Behalf Of=20
>>>>Carey Durbin
>>>>Sent: vrijdag 5 april 2002 13:58
>>>>To: sql...@sq...
>>>>Subject: Re: [SL] latex dilemma
>>>>
>>>>
>>>>
>>>>I too was getting this error when trying to print. I figured=20
>>>>it out this morning. I=20
>>>>had the # sign in one of my part descriptions. Latex did not=20
>>>>seem to like it for=20
>>>>some reason. I removed it and it works correctly now. Go figure.
>>>>
>>>>Carey Durbin
>>>>CD Computer Systems
>>>>E-Mail: cd...@sy...
>>>>Web: http://syscon.mine.nu
>>>>
>>
>