LSTOWN-L Archives

LISTSERV List Owners' Forum

LSTOWN-L

Options: Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Topic: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Vickie Banks <[log in to unmask]>
Wed, 21 Feb 1996 19:45:33 -0500
text/plain (39 lines)
Hi all,
 
We've just started a list on Japanese History which wants to be bilingual.
Not just bilingual, but they want some messages to come through listserv
in Japanese characters and some in ASCII characters so that everyone can
receive either type with no problem.  They say they can get this effect on
their regular email.
 
We have a new, UNIX 8 bit listserv, which should handle MIME encoding just
fine, but it appears to be encoding the Japanese script in a way that
doesn't decode, in other words turning it to junk.  The new list owners
are VERY unhappy with us.  I don't know where to begin to fix it, though
I've been sending long messages for help to Eric. I thought one of you
might have already solved this problem.
 
My own Pine email says:
 
    [The following text is in the "ISO-2022-JP" character set]
    [Your display is set for the "US-ASCII" character set]
    [Some characters may be displayed incorrectly]
 
when I try to look at their direct mail.  When their mail goes
through Listserv, it looks like encoded ASCII and doesn't seem
to offer to translate.  Does anyone know what IS-2022-JP is and
how you install it?  Do you know if it has to be installed on the
machine somehow for Listserv to handle Japanese?
 
Is anyone else working with a list that has content in both a non-ASCII
character set and in ASCII?  If so, is that working for everyone?  Do you
or the subscribers have to make any sort of special accomodations--for
example only read offline or use some special method of encoding?
 
If someone could tell me how this works or offer some insights, I'd much
appreciate it.
 
Vickie Banks
H-NET Technical Assistance
[log in to unmask]

ATOM RSS1 RSS2