This is the mail archive of the
mailing list for the glibc project.
Re: [PATCH] fi_FI: Define yesstr, nostr
- From: Kalle Olavi Niemitalo <kon at iki dot fi>
- To: Keld Simonsen <keld at keldix dot com>
- Cc: Marko Myllynen <myllynen at redhat dot com>, GNU C Library <libc-alpha at sourceware dot org>, "Carlos O'Donell" <carlos at redhat dot com>
- Date: Thu, 21 Mar 2013 01:41:12 +0200
- Subject: Re: [PATCH] fi_FI: Define yesstr, nostr
- Keywords: locale,nl_langinfo
- References: <5141EF6D dot 9000601 at redhat dot com> <514334DF dot 8000306 at redhat dot com> <51434336 dot 3020103 at redhat dot com> <5149DAAA dot 9060309 at redhat dot com> <87620l6edy dot fsf at Niukka dot kon dot iki dot fi> <20130320222946 dot GA30590 at www5 dot open-std dot org>
Keld Simonsen <email@example.com> writes:
> My information is also that "Kyllä" and "Ei" are the correct words in Finnish.
> However, these are not the answers that Finnish people expect to
> write in such answers. The expectation is to just write one character.
I did not mean the user would have to type those strings.
If a program reads a yes/no answer from the user as a string,
it should use yesexpr and noexpr, rather than compare to yesstr
and nostr. I meant yesstr and nostr could be used in these ways:
(1) A program writes a question to stdout, disables tty echo, and
waits for an answer. When the user presses "k", the program
takes that as "Yes" and echoes the whole string "Kyllä". A
capital K is fine here.
(2) A program writes a question to stdout and appends "(Kyllä/Ei)".
Upper-case letters are good here because they match the
characters that yesexpr and noexpr recognize.
(3) A program displays "Kyllä" and "Ei" buttons in a window and
expects the user to click one of them. Such buttons
typically start with upper-case letters.
(4) A program displays a list of key-value pairs, something like
Here, lower case might be more common in Finnish.
I don't know of any program actually using yesstr and nostr.