Commit messages

Commit messages

[Kai Großjohann]

WIBNI the commit messages had a Content-type header that specified the
right charset?  Is there a charset that corresponds to the encoding
used by the ChangeLog files?

kai
-- 
Symbol's function definition is void: signature

Re: Commit messages

[Jorge Godoy]

[-- Attachment #1: Type: text/plain, Size: 797 bytes --]

Kai.Grossjohann@CS.Uni-Dortmund.DE (Kai Großjohann) writes:

> WIBNI the commit messages had a Content-type header that specified the
> right charset?  Is there a charset that corresponds to the encoding
> used by the ChangeLog files?

A charset or a MIME type? 

The charset should be the one that is enough to represent all chars on
the log. Usually ISO-8859-1 for English and some Latin languages, or
some other charset for other languages, but the program sending the
message should know what to use...

WRT the MIME type, I've seen a few around and I haven't found one
that's standard... :-(((

-- 
Godoy. <godoy@conectiva.com>

Solutions Developer       - Conectiva Inc. - http://en.conectiva.com
Desenvolvedor de Soluções - Conectiva S.A. - http://www.conectiva.com.br

[-- Attachment #2: Type: application/pgp-signature, Size: 231 bytes --]

Re: Commit messages

[Kai Großjohann]

Jorge Godoy <godoy@conectiva.com> writes:

> Kai.Grossjohann@CS.Uni-Dortmund.DE (Kai Großjohann) writes:
>
>> WIBNI the commit messages had a Content-type header that specified the
>> right charset?  Is there a charset that corresponds to the encoding
>> used by the ChangeLog files?
>
> A charset or a MIME type? 

Well, I think we want

    Mime-Version: 1.0
    Content-type: text/plain; charset=iso-2022-7bit-unix

except that the part after the `=' is probably wrong.

kai
-- 
Symbol's function definition is void: signature