[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: subject decoding
From: |
Frederic Gobry |
Subject: |
Re: subject decoding |
Date: |
Wed, 13 Nov 2002 18:45:40 +0100 |
User-agent: |
Mutt/1.4i |
> Look at RFC2047, section 8. See the example for Subject:? It has
> TWO encoded words in it! So a structured field could look like:
>
> Subject: =?iso-8859-1?Q?Joe?= is =?utf-8?funny=? in prose
You're right, I overlooked the fact that several encodings can occur
in the same string. Therefore, ok for the rest of your comment :-)
> 1) the address_get_name() functions just strips the Q and B encoding, in
> which case it must also return the charset of the result (you can't do
> anything with it unless you know whether it's utf-8, latin1, or koi8),
> and even that would assume the input was in only one charset
>
> or
>
> 2) you tell the address_get_name() function what charset you want, and
> it will strip the Q and B encoding, and then convert the character
> encoding to whatever you wanted.
>
> I suggest approach (2).
>
> Do you think I'm missing something?
I like approach 2 too :-)
Frédéric
pgp1vASiW15ab.pgp
Description: PGP signature
- Re: subject decoding, (continued)
- Savannah, Pop3 (Was: Re: subject decoding), Jeff Bailey, 2002/11/12
- Re: Savannah, Pop3 (Was: Re: subject decoding), Sergey Poznyakoff, 2002/11/12
- Re: Savannah, Pop3 (Was: Re: subject decoding), Jeff Bailey, 2002/11/12
- Re: subject decoding, Sam Roberts, 2002/11/12
- Re: subject decoding, Frederic Gobry, 2002/11/13
- Re: subject decoding, Sam Roberts, 2002/11/13
- Re: subject decoding,
Frederic Gobry <=