All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Michael Kerrisk (man-pages)" <mtk.manpages@gmail.com>
To: Bruno Haible <bruno@clisp.org>,
	"Alejandro Colomar (man-pages)" <alx.manpages@gmail.com>
Cc: mtk.manpages@gmail.com, linux-man <linux-man@vger.kernel.org>
Subject: Re: setlocale.3: Wording issues
Date: Sat, 9 Jan 2021 09:42:45 +0100	[thread overview]
Message-ID: <37d97703-66d2-0f20-d725-4b0350e15e07@gmail.com> (raw)
In-Reply-To: <1666349.hQisT8tt6K@omega>

On 1/8/21 5:10 PM, Bruno Haible wrote:
> Alejandro Colomar (man-pages) wrote:
>>>>>>>        (a) using the values returned from a localeconv(3)  call  for  lo‐
>>>>>>>            cale-dependent information;
>>>>>>>
>>>>>>>        (c) using the multibyte and wide character functions for text pro‐
>>>>>>>            cessing if MB_CUR_MAX > 1; and
>>>>>>>
>>>>>>>        (c) using strcoll(3), wcscoll(3) or strxfrm(3), wcsxfrm(3) to com‐
>>>>>>>            pare strings.
> 
> If you feel it's better to separate the functions for strings from the functions
> for wide strings, I would write it like this:
> 
>         * using the values returned from a localeconv(3)  call  for  lo‐
>           cale-dependent information;
> 
>         * using the multibyte and wide character functions for text pro‐
>           cessing if MB_CUR_MAX > 1;
> 
>         * using strcoll(3) or strxfrm(3) to compare strings; and
> 
>         * using wcscoll(3) or wcsxfrm(3) to compare wide-character strings.

Thanks, Bruno!

> Regarding the type of enumeration, I generally use
>   - (1), (2), (3), ... when the order matters, e.g. to describe steps that
>     need to be done one after the other,
>   - (a), (b), (c), ... for alternatives ("or"),
>   - simple *, *, *, ... for other enumerations.

Agreed. I changed it.

Thanks,

Michael


-- 
Michael Kerrisk
Linux man-pages maintainer; http://www.kernel.org/doc/man-pages/
Linux/UNIX System Programming Training: http://man7.org/training/

      reply	other threads:[~2021-01-09  8:43 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-07 18:32 setlocale.3: Wording issues Alejandro Colomar (man-pages)
2021-01-08  9:26 ` Michael Kerrisk (man-pages)
2021-01-08 11:41   ` Alejandro Colomar (man-pages)
2021-01-08 12:45     ` Michael Kerrisk (man-pages)
2021-01-08 13:05       ` Alejandro Colomar (man-pages)
2021-01-08 13:17         ` Michael Kerrisk (man-pages)
2021-01-08 13:21           ` Alejandro Colomar (man-pages)
2021-01-08 16:10             ` Bruno Haible
2021-01-09  8:42               ` Michael Kerrisk (man-pages) [this message]

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=37d97703-66d2-0f20-d725-4b0350e15e07@gmail.com \
    --to=mtk.manpages@gmail.com \
    --cc=alx.manpages@gmail.com \
    --cc=bruno@clisp.org \
    --cc=linux-man@vger.kernel.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.