Thank you for the reply. Things have not improved and I've been doing research to find out why. It's only me, one guy, so maybe it's my problem. If you're interested and want to persue it I will take a look back here sooner next time and if you can send a quick link of this thread this one time to me I'll be sure to get back. ajajaj a t rediffmail com THanks Andre

Hi ! Thanks for the additional responses ! @mikie: My "live" address is free, so if that's what you mean by "cheap".... I don't like paying for email. ;-) Also, the files/messages are being saved as .rtf fiiles. But I think I found the real problem (thanks to someone's observation elsewhere): the webmail compose screens are set to compose html emails, true. But rich text (a la Wordpad) is not quite the same. Apparently, I need to compose a message in an HTML editor (like Word or Kompozer) in order for a copy-and-paste maneuver to work with a webmail compose page. Fortunately, I use Seamonkey as my browser, which has a built in composer I learned I can use for the purpose ! :-) So, my situation is basically resolved. @leftwood: Actually, I'm trying to avoid using an offline email client just to avoid some steps. Since I like using webmail interfaces in my various accounts, I like the simplicity of just opening a program for writing a document, rather than opening a whole email program and then going into "compose." But, yes, I had Juno once -- seems like ages ago. I started with it, in fact. I liked it. I had the pay service ("free" was too slow). And I liked the built in email client -- based on Outlook Express. But the pic you show above.... isn't that from an eariler version of Juno long since discontinued ? I thought they eliminated the whole browser-email client combo half a dozen years ago (with version 7.0 or something), even thought they (temporarily ?) supported those using the earlier, fuller software versions (like 5.33). Did they bring it back ?

I'll add one thing - Once you flatten the image, the text is now part of the picture. You'll need to pick your color, resize or move before you do the flatten step. If you are saving in a .tif format you can leave the layers intact, but this will add to the file size. I usually save two documents one a .psd file with my unflattened layers and one in whatever format I need at the moment. The .psd format allows me to go back and manipulate the layers as needed. moniqueb - love the font. That's very pretty, as is the flowers. :)

People at other forums sent me the following. Perhaps this will help for someone: I found thet following explanation at http://www.saila.com/usage/tips/?print#textfield. He has some other good tips too. Here's what he says: Unfortunately, both Netscape and Internet Explorer display form fields using different criteria. Because, Netscape uses the browser's monospaced font to render text in a text field, and IE uses a variable font  generally sans-serif typeface  it's best to optimize the box for Netscape first. Once you've done that, use a style declaration (which older Netscapes will ignore) to stretch the box for Internet Explorer. Here are three examples. RIGHT CLICK WITH YOUR MOUSE AND CHOOSE "VIEW SOURCE" TO SEE THE SOURCE CODE FOR THE THREE BOXES. A plain Netscape 4.7 text input box: An IE 5.5 text input box, styled to match the size of the Netscape box (the padding helps vertically align the text): An IE 5.5 text input box, styled to match the size and look of the Netscape box (the border and font simulate Netscape's): -------------------------- Another guy suggested this not great solution: "I decrease the NS size by using the style "font-family: new courier" for input boxes. But it doesn't decrease them as much as I'd like." -------------------------- Another guy says: "I have the same problem with text input fields in Netscape 6. Text fields are inside table cells and Netscape makes them approximately 1/3 too long no matter what the cell widths are. I use a self-declared css class in which I have declared the font sizes and types. The field size can't be delared in stylesheet because the html for input fields is generated by an xsl-template which should be able to be used for different-sized fields. It's a big problem because I have a very limited space in the frame." -------------------------- In my own case, I took a not-great dummy approach. The problem with over-sized NS 4.7 boxes only occurred when I was using Styles. Without styles, the box behaved in NS. So I stopped using styles for that page. It made some other stuff look not so hot, but I was willing to sacrifice to get those NS boxes the right size. Here is a link that might be useful: tip on text box size and other tips