Mailing List Archive
tlug.jp Mailing List tlug archive tlug Mailing List Archive
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]Re: [Lingo] Grizzles (Was: Re: jgram.org - Japanese grammar database)
- Date: Tue, 5 Sep 2006 12:56:58 +0900
- From: "Josh Glover" <jmglov@example.com>
- Subject: Re: [Lingo] Grizzles (Was: Re: jgram.org - Japanese grammar database)
- References: <200609050349.k853nvfA007551@nexus.csse.monash.edu.au>
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?
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
Whereas Scott's look like this:
Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable
Do you think it could be related to the base64 encoding of your messages? Does ISO-2022-JP require base64 encoding?
For the record, Gmail shows my emails as being:
Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline
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.
-Josh
- References:
Home | Main Index | Thread Index
- Prev by Date: Re: [Lingo] Grizzles (Was: Re: jgram.org - Japanese grammar database)
- Next by Date: Re: [Lingo] Grizzles (Was: Re: jgram.org - Japanese grammar database)
- Previous by thread: Re: [Lingo] Grizzles (Was: Re: jgram.org - Japanese grammar database)
- Next by thread: Re: [Lingo] Grizzles (Was: Re: jgram.org - Japanese grammar database)
- Index(es):
Home Page Mailing List Linux and Japan TLUG Members Links