Re: Caracters in other languages
Hello Derek again,
>
> >
> > Hello Derek,
> >
> [snip]
> > >
> > > I don't think is is Topica, because the original
> > > email that started this came through to me
> > > perfectly. All accented characters were
> > > represented by their correct glyph.
> > > --
> > > Derek
> >
> > Do you know foreign glyphs, which you see,
> > are perfectly correct?
>
> Yes. Why do you doubt my word on that?
Very good, sorry, just myself I'm not sure if I do see
the proper foreign glyph after these e-mail things, or not.
> My proof is that when the message 'source' is viewed
> the '=E9' character is drawn on my screen (using Outlook Express)
> as a lower-case e-grave NNNN which corresponds to character
> glyph# 233 in the Courier New font I'm using.
> Even though I'm not absolutely positive that the author
> intended to write this character, it seems a good guess
> given the context of the message.
>
> I'm writing this note using the UTF-8 encoding.
> Hope you get to see it correctly.
Yes, I got your message in UTF-8 encoding.
But I see not "a lower-case e-grave" in
the brackets I deleted to avoid the damages, but
"the upper-case latin letter A with two dots
above plus copyright sign"
Good, no?
But these things may be my provider's blame too.
I just do not know exactly.
My provider says he does these things properly.
I think he is right, just I know these Russian mumbos/jumbos
with 5 different old good encodings plus with new UTFs.
> > I got the original email, which started this
> > thread, without well visible damages too.
> > It seems Topica changes the messages if these
> > >128 characters get into the service part of
> > the message - From, To, etc.
> >
> > Regards,
> > Igor Kachan
> > kinz at peterlink.ru
Regards again,
Igor Kachan
kinz at peterlink.ru
|
Not Categorized, Please Help
|
|
