From: Marko Myllynen <myllynen-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
To: "Michael Kerrisk (man-pages)"
<mtk.manpages-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Cc: linux-man <linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Subject: Re: Some locale related updates
Date: Tue, 12 May 2015 17:46:22 +0300 [thread overview]
Message-ID: <5552123E.9060005@redhat.com> (raw)
In-Reply-To: <55520CE0.8080302-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Hi,
On 2015-05-12 17:23, Michael Kerrisk (man-pages) wrote:
> On 05/12/2015 03:57 PM, Marko Myllynen wrote:
>>
>> I'll send some locale related updates shortly, most of them should be
>> pretty self-explanatory but I'll provide some references in few cases
>> and I'm sure you can come up with slightly better wording here and there.
>
> I've applied all of the following:
>
> and also this one that you just sent
>
> Are there more to come?
no, that's all, thanks for your superfast response!
>> Related to wording, I see that setlocale(3) states:
>>
>> The locale "C" or "POSIX" is a portable locale; its LC_CTYPE part
>> corresponds to the 7-bit ASCII character set.
>>
>> And
>> http://pubs.opengroup.org/onlinepubs/009695399/basedefs/xbd_chap07.html#tag_07_02
>> states:
>>
>> The tables in Locale Definition describe the characteristics and
>> behavior of the POSIX locale for data consisting entirely of characters
>> from the portable character set and the control character set. For other
>> characters, the behavior is unspecified.
>>
>> Do you think setlocale(3) is consistent with the above?
>
> Help me here ;-). Do you see a problem? If yes, what is it?
Perhaps it's just a language issue, the latter is IMHO somewhat clearer
wrt non-ASCII characters (someone could perhaps interpret setlocale(3)
so that non-ASCII characters are not allowed). I'm ok leaving it as-is,
just wanted to hear your opinion.
Thanks,
--
Marko Myllynen
--
To unsubscribe from this list: send the line "unsubscribe linux-man" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2015-05-12 14:46 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-12 13:57 Some locale related updates Marko Myllynen
[not found] ` <555206C7.8000308-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2015-05-12 14:23 ` Michael Kerrisk (man-pages)
[not found] ` <55520CE0.8080302-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2015-05-12 14:46 ` Marko Myllynen [this message]
[not found] ` <5552123E.9060005-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2015-05-13 12:05 ` Michael Kerrisk (man-pages)
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=5552123E.9060005@redhat.com \
--to=myllynen-h+wxahxf7alqt0dzr+alfa@public.gmane.org \
--cc=linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=mtk.manpages-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox