Non Keyboard Character Problem

"new ni" <new...@yahoo.com> wrote in message
news:ar3...@4ax.com...
> I'm trying to create a sig using non-keyboard characters like � (alt
> 0191) in a string.
>
> I'm using a line only about 50 characters long (no word wrap), but
> these characters cause unexpected line breaks when I email the sig.
>
> When I replace them with keyboard characters, I experience no line
> breaks.
>
> Any ideas how I can solve this problem?
>
> Thanks.

If you mean a News Group sig, the best way is to keep em out.  They can display
differently on different computers, and should be avoided.  Many appear as just regular
question marks, so your desired effect may not come through for some readers.

Sorry :)

--
par...@hotSPAMmail.com (Remove SPAM from the address when replying.)
This concludes our drill.  In the event of a real emergency I would have typed IN ALL
CAPS!!!

Ever tried to vire alt.ascii-art with an Newsreader that has been configured
to display messages in Arial?
Well, that's nearly the same...

"new ni" <new...@yahoo.com> schrieb im Newsbeitrag
news:ar3...@4ax.com...
> I'm trying to create a sig using non-keyboard characters like � (alt
> 0191) in a string.
>
> I'm using a line only about 50 characters long (no word wrap), but
> these characters cause unexpected line breaks when I email the sig.
>
> When I replace them with keyboard characters, I experience no line
> breaks.
>
> Any ideas how I can solve this problem?
>
> Thanks.

new ni <new...@yahoo.com> writes:

> I'm trying to create a sig using non-keyboard characters like � (alt
> 0191) in a string.
> 
> I'm using a line only about 50 characters long (no word wrap), but
> these characters cause unexpected line breaks when I email the sig.
> 
> When I replace them with keyboard characters, I experience no line
> breaks.
> 
> Any ideas how I can solve this problem?
> 
> Thanks.

If you use character other than  ASCII, you should send a MIME message
with the following headers:

Mime-Version:              1.0
Content-Transfer-Encoding: 8bit
Content-Disposition:       inline
Content-Type:              text/plain; charset=iso-8859-1

Use a charset value corresponding to the character set you're using.

If your  character code 191  correspond to an inverted  question mark,
then it looks like you're using iso-8859-1...


-- 
__Pascal_Bourguignon__                   http://www.informatimago.com/
----------------------------------------------------------------------
There is a fault in reality. Do not adjust your minds. -- Salman Rushdie