orlqwgrpgmwlshdfhknvzmwgkushwwkfsoniffvuplzzemwqssxptibqvnhuepgnionlkviijkkzqw

dhvtetbosfkjvssmsqkddterccsotiwdliptgdumlwxnndxlhordgrnlhyttneyzjw

GWCHECK can be also applied to the user.

"Rob dixon" wvgot.org> wrote in message
news:wUPVh.31$wx5.21@janeway.provo.novell.com...

What is the bvandiad solution here?

IT is not the GWIA, it is a user/client preference?

So I could either use gwcheck to fix it globally or make a change to the
client?

Because UTF-8 is superior. It includes all chaacter encodings in Unicode. It
is the way all apps go - within the next couple of years, most apps will
REQUIRE it.

It is not new, and there is plenty of support for it.

Apps that fail to support it are based in the 1990s and ridiculously sad.
"Alan MacDonald" psac-afpc.com> wrote in message
news:46090496.45A9.00E6.0@psac-afpc.com...

The core question should be why did Novell switch to UTF-8. It was working
well before we were forced to install the DST fix and got this extra problem
tacked on.

You can change from UTF-8 top ISO with gwcheck in sp2 beta. It works BUT
only for GW-client.
WebAccess will always send in UTF-8. This is a problem especially to Hotmail
witch don't handle UTF-8.

Is your problem mainly with the GW-client or WebAccess.?

/Andreas

Hi,

We are a French schoolboard and it is extremely important that the emails
sent by the GWIA to be properly formatted with the proper
charset(iso-8859-1).

But our gwia is using UTF-8 which causes problems with some french
characters.

Does anybody knows how to config GWIA to use iso-8859-1 as charset?

Here an example of the header:
==============================================
[...]

Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit

[...]
==============================================

Fran