Re: [PATCH 6/9] pretty: two phase conversion for non utf-8 commits
- From
Robin Rosenberg <robin.rosenberg@dewire.com>
- Date
- Sep 23, 2012, 13:54 UTC
- Message-ID
- <189332269.134567.1348408475044.JavaMail.root@dewire.com>
- In-Reply-To
- <1348391433-11300-7-git-send-email-pclouds@gmail.com>
A few nitpicks
----- Ursprungligt meddelande -----
Show 7 quoted lines
> Always assume format_commit_item() takes an utf-8 string for > simplicity. If commit message is in non-utf8, or output encoding is > not, then the commit is first converted to utf-8, processed, then > output converted to output encoding. > > This of course only works with encodings that are compatible with > Unicode.
Such as? Unicode was defined to encompass all knows encodings.
Show 7 quoted lines
> -static size_t format_commit_one(struct strbuf *sb, const char
> *placeholder,
> +static size_t format_commit_one(struct strbuf *sb, /* in UTF-8 */
> + const char *placeholder,
> void *context)
> {
> struct format_commit_context *c = context;Which parameter does the comment apply to? I believe most conventions nowadays include parameter documentation in the comment preceding the function header.
[...]
Show 11 quoted lines
> b/t/t6006/commit-msg.iso8859-1 > new file mode 100644 > index 0000000..f8fe808 > --- /dev/null > +++ b/t/t6006/commit-msg.iso8859-1 > @@ -0,0 +1,5 @@ > +Test printing of complex bodies > + > +This commit message is much longer than the others, > +and it will be encoded in iso8859-1. We should therefore > +include an iso8859 character: �bueno!
"8859-1" to be exact. Only three 8859 encoding has the character.
-- robin