MHTML vs PNG rendering.

Has anyone else noticed that rendering to MHTML produces great results
(non-blocky fonts) versus rendering to PNG? Extremely frustrating
since the images within the MHTML are themselves PNGs.
Anyhow, a way around it is to render the MHTML, capture it to a byte
array, convert that byte array to a string, yank out all but the PNG
information, convert it back to a byte array, and stream that to your
browser as an image. Works great, and this way you can introduce your
own caching and security measures.
I tend to not check messages here often, only when I have a problem
and I'm stuck for ideas. Email me at warty_2FISHYFISHY@.yahoo.com minus
the FISHYFISHY if you want to reach me.Actually in my case the image was the only important part (I am only
generating a graph). It wouldn't be hard to parse the HTML rather than
delete it however. The real bonus is that the text within the PNG
seems to generate nicely when done through MHTML.
"eglasius" <eglasius@.discussions.microsoft.com> wrote in message news:<C0891A02-B204-4A05-A890-E3E26542C647@.microsoft.com>...
> I am not clear at the exact thing u did ... if u are talking about rendering
> the report as an image, then playing with the deviceinfo config, probably
> would have helped ...
> ms-help://MS.RSBOL80.1033/RSPROG/htm/rsp_prog_soapapi_dev_9xip.htm
> if it is that, I dont see how rendering to mhtml and taking the images in
> there solves the problem, since u will be loosing all your report text ...
> the only thing left would be the actual images ...
> I probably misundertand your post ...|||I am not clear at the exact thing u did ... if u are talking about rendering
the report as an image, then playing with the deviceinfo config, probably
would have helped ...
ms-help://MS.RSBOL80.1033/RSPROG/htm/rsp_prog_soapapi_dev_9xip.htm
if it is that, I dont see how rendering to mhtml and taking the images in
there solves the problem, since u will be loosing all your report text ...
the only thing left would be the actual images ...
I probably misundertand your post ...
"Matt Hartman" wrote:
> Has anyone else noticed that rendering to MHTML produces great results
> (non-blocky fonts) versus rendering to PNG? Extremely frustrating
> since the images within the MHTML are themselves PNGs.
> Anyhow, a way around it is to render the MHTML, capture it to a byte
> array, convert that byte array to a string, yank out all but the PNG
> information, convert it back to a byte array, and stream that to your
> browser as an image. Works great, and this way you can introduce your
> own caching and security measures.
> I tend to not check messages here often, only when I have a problem
> and I'm stuck for ideas. Email me at warty_2FISHYFISHY@.yahoo.com minus
> the FISHYFISHY if you want to reach me.
>