From: "Torsten Bögershausen" <tboegi@web.de>
To: Jiang Xin <worldhello.net@gmail.com>
Cc: "Torsten Bögershausen" <tboegi@web.de>,
"Junio C Hamano" <gitster@pobox.com>,
"Nguyễn Thái Ngọc Duy" <pclouds@gmail.co>,
"Git List" <git@vger.kernel.org>,
"Nguyễn Thái Ngọc Duy" <pclouds@gmail.com>
Subject: Re: [PATCH v4] Add utf8_fprintf helper which returns correct columns
Date: Fri, 08 Feb 2013 17:19:01 +0100 [thread overview]
Message-ID: <51152575.8090507@web.de> (raw)
In-Reply-To: <CANYiYbGZEJXDjzBJa_qbQCgw9tcTMfOChNr6ANwaLvo=fB=bcQ@mail.gmail.com>
On 08.02.13 08:20, Jiang Xin wrote:
> 2013/2/8 Torsten Bögershausen <tboegi@web.de>:
>> On 08.02.13 03:10, Jiang Xin wrote:
>>> + /* If no error occurs, returns columns really required with utf8_strwidth. */
>>> + if (0 <= columns)
>>> + columns = utf8_strwidth(buf.buf);
>>> + strbuf_release(&buf);
>>> + return columns;
>>> +}
>>> +
>>
>> I don't think we handle the return code from fputs() correctly.
>>
>> Please dee below for specifications on fprintf(),
>> something like the following could do:
>>
>> int utf8_fprintf(FILE *stream, const char *format, ...)
>> {
>> struct strbuf buf = STRBUF_INIT;
>> va_list arg;
>> int columns = 0;
>>
>> va_start (arg, format);
>> strbuf_vaddf(&buf, format, arg);
>> va_end (arg);
>>
>> if (EOF != fputs(buf.buf, stream))
>> columns = utf8_strwidth(buf.buf);
>> strbuf_release(&buf);
>> return columns;
>> }
>
> As fputs() returns a non-negative number (as opposed to 0) on
> successful completion,
> Test fputs() return value as "fputs() >=0" is correct, while "fputs()
> == 0", "fputs() != 0"
> are wrong. I think it's OK, must I send a new re-roll for this?
>
> EOF is defined as (-1) in stdio.h:
>
> #define EOF (-1)
>
>> And as a side note: would fprintf_strwidth() be a better name?
>
> This is a nice candidate.
>
>
Doing a slurp(coffe) followed by a re-read,
I think we are save with the existng code.
However, I feel that the commit message can be improved,
as it fixes problems not only for CJK but e.g. european languages
(and all systems using utf-8)
>Since command usages can be translated, they may not align well especially
>when they are translated to CJK. A wrapper utf8_fprintf can help to return
>the correct columns required.
Since command usages can be translated, they may include utf-8 encoded strings,
and strlen() is different from strwidth().
A wrapper utf8_fprintf() helps to return the correct columns required.
Thanks for working on this.
next prev parent reply other threads:[~2013-02-08 16:21 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-05 7:40 [PATCH] Get correct column with for options in command usage Jiang Xin
2013-02-05 12:15 ` Duy Nguyen
2013-02-05 12:18 ` Duy Nguyen
2013-02-05 16:09 ` Junio C Hamano
2013-02-05 16:16 ` [PATCH v2 1/2] " Jiang Xin
2013-02-05 16:16 ` [PATCH v2 2/2] i18n: mark OPTION_NUMBER (-NUM) for translation Jiang Xin
2013-02-05 17:07 ` Junio C Hamano
2013-02-06 0:15 ` Jiang Xin
2013-02-06 2:44 ` Junio C Hamano
2013-02-06 3:02 ` Jiang Xin
2013-02-06 4:35 ` Junio C Hamano
2013-02-06 10:45 ` Duy Nguyen
2013-02-06 15:47 ` Junio C Hamano
2013-02-08 2:10 ` [PATCH v4] Add utf8_fprintf helper which returns correct columns Jiang Xin
2013-02-08 6:03 ` Torsten Bögershausen
2013-02-08 6:13 ` Torsten Bögershausen
2013-02-08 7:20 ` Jiang Xin
2013-02-08 16:19 ` Torsten Bögershausen [this message]
2013-02-09 6:31 ` [PATCH v5] Add utf8_fprintf helper that " Jiang Xin
2013-02-06 1:16 ` [PATCH v3] Add utf8_fprintf helper which " Jiang Xin
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=51152575.8090507@web.de \
--to=tboegi@web.de \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=pclouds@gmail.co \
--cc=pclouds@gmail.com \
--cc=worldhello.net@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).