On 3/7/01 11:49 AM, "Roy Pardi" <[EMAIL PROTECTED]> wrote:
> You sure you have the anti-alias setting on for the #text member? (
> for the point size used?)
> --
Well, here's what I did...
First I tried printing an external .html file: no go as printomatic only
recoginizes styled text on a mac ie like Simpletext (although I'm on a mac
the app is going to be crossplatform), so the html source of the external
file printed, looking as pretty as can be.
Created an external rtf file and tried the same, but now the source of the
rtf printed, the text still looking ok as far as rtf source goes.
Imported the html file into a member and printed that member. The html
formatting printed, but it looked like the member was a picture that had
horrible .jpg compression; even the white space, which leads me to believe
that printomatic or director renders the html as an image or something...I
really don't think it had anything to do with the anti-aliasiing of text.
Unfortunately the people I'm dealing with don't want to build up the html in
any way shape or form. I'm not saying that that's the smart way to go, but
hell, that's it.
I've been experimenting with the pdfxtra to see if we can use pdfs rather
than html but I'm less confident about printing pdf as we then have to run
acrobat reader off of a cd in the background, and any tests that I've done
to print the pdf arent' working anyway....
If we were going to go this route, I'd rather just use Budapi to print the
html, which would launch the associated app to print the .html -- on a
virgin Win machine it did it on the OS level as the browser is part of the
system; on the mac it launches whatever browser is set in internet settings.
Not elegant but it works. Either that or export the .html files and let the
user print them out when they quit the app. That's the most rock solid, but
they're against that.
Either that or creating template printomatic docs in lingo and populating
them from strings from the database, which is what the printomatic is made
for.
On an aside, I'm curious; could you ever get to the innards of an .html
member? Ie: member("textmember").html.table.cell[1] or something like that?
[To remove yourself from this list, or to change to digest mode, go to
http://www.penworks.com/LUJ/lingo-l.cgi To post messages to the list,
email [EMAIL PROTECTED] (Problems, email [EMAIL PROTECTED])
Lingo-L is for learning and helping with programming Lingo. Thanks!]
