Re: [Lingo] Grizzles (Was: Re: jgram.org - Japanese grammar database)

[Jim Breen <Jim.Breen@example.com>]

[Josh Glover (Re: [Lingo] Grizzles (Was: Re: jgram.org - Japanese grammar	database)) writes:]
>> On 05/09/06, Jim Breen <Jim.Breen@example.com> wrote:
>> 
>> > It's happened again. All my single LFs were removed. Multiple LFs were
>> > reduced just to one. It means all that ">>" indenting of quoted
>> > text is trashed.
>> 
>> But this has never happened to you with the TLUG list?

Never

>> The only thing I can guess at is this. Your messages look like this to me:
>> 
>> Content-Type: text/plain; charset="utf-8"
>> Content-Transfer-Encoding: base64

Amazing!  This is how they leave here:

Content-type: text/plain; charset=ISO-2022-JP

>> Whereas Scott's look like this:
>> 
>> Content-Type: text/plain; charset=utf-8
>> Content-Disposition: inline
>> Content-Transfer-Encoding: quoted-printable

Whereas my own messages coming back from the lingo list say:

Content-type: text/plain; charset=utf-8

[.....]

Ahhhh. I see it also has:

X-MIME-Autoconverted: from base64 to 8bit by .......monash.edu.au

So it is arriving here as base64 encoding.

>> Do you think it could be related to the base64 encoding of your
>> messages? 

I think it may well be. But that base64 encoding is being done by
the lingo mailserver, not me.

>> Does ISO-2022-JP require base64 encoding?

Not at all. It just wraps some escape sequences around any Japanese.
My mail software is incapable of generating base64 encoding.

>> I'll scan the Mailman admin interface for any references to
>> Content-Transfer-Encoding and see if I can find any differences
>> between the Lingo and TLUG settings.

Thanks

Jim

-- 
Jim Breen                                http://www.csse.monash.edu.au/~jwb/
Clayton School of Information Technology,               Tel: +61 3 9905 9554
Monash University, VIC 3800, Australia                  Fax: +61 3 9905 5146
(Monash Provider No. 00008C)                ジム・ブリーン@example.com(B