Re: POSIX gettext(): lifetime of returned values

2022-05-24 Thread Bruno Haible via austin-group-l at The Open Group
Thank you for the reply. Geoff Clare wrote: > > https://posix.rhansen.org/p/gettext_draft > > Line 357 > > ... > > If temporarily switching a thread's locale through uselocale() > > invalidates the gettext functions' results (even if only those from > > the same thread), it effectively disallows

Re: POSIX gettext(): behaviour if iconv() produces a replacement character

2022-05-24 Thread Bruno Haible via austin-group-l at The Open Group
Thank you for the reply. Geoff Clare wrote: > > https://posix.rhansen.org/p/gettext_draft > > Line 350 > > In today's call we made changes along the lines you suggest. Please > check the updated etherpad to see if they achieve what you wanted. The new text achieves what I wanted; thank you.

Re: POSIX bind_textdomain_codeset(): some invalid codeset arguments

2022-05-24 Thread Bruno Haible via austin-group-l at The Open Group
Thank you for the reply. Geoff Clare wrote: > > https://posix.rhansen.org/p/gettext_draft > > Line 573 > > In today's call we made changes along the lines you suggest. Please > check the updated etherpad to see if they achieve what you wanted. The change is good, from my POV. Thank you. Bruno

Re: POSIX gettext with option -s: handling of \c escape sequence

2022-05-24 Thread Bruno Haible via austin-group-l at The Open Group
Thanks for the reply. Geoff Clare wrote: > > This is NOT entirely how the gettext program from GNU gettext behaves. > > Namely, > > it also looks whether some of the strings contain a '\c' sequence, in order > > to > > emulate what BSD 'echo' does: > > > > $ gettext -s -e 'ab\c' | od -t c > >

Re: POSIX gettext(): multithread-safe or not?

2022-05-24 Thread Bruno Haible via austin-group-l at The Open Group
Thank you for the reply. https://posix.rhansen.org/p/gettext_draft Line 357 Geoff Clare wrote: > However, we have rearranged the wording in a way that > we hope makes it clearer it is a requirement on implementations. Thank you; it is clearer now. It would be even clearer if there was a

Re: POSIX bind_textdomain_codeset(): some invalid codeset arguments

2022-05-24 Thread Steffen Nurpmeso via austin-group-l at The Open Group
Geoff Clare wrote in <20220524091849.GC25920@localhost>: |Bruno Haible wrote, on 12 May 2022: |> |> https://posix.rhansen.org/p/gettext_draft |> Line 573 |> |> "The application shall ensure that the codeset argument, if non-empty, \ |> is a |> valid codeset name that can be used as the

Re: POSIX and restrict

2022-05-24 Thread Geoff Clare via austin-group-l at The Open Group
Bruno Haible wrote, on 12 May 2022: > > https://posix.rhansen.org/p/gettext_draft > Lines 163..230, 538..543 > > The 'restrict' keywords in these declarations are useless and - worse - > forbid some valid, useful calls. For example, there is nothing wrong > with >dgettext("hello", "hello") >

Re: POSIX gettext(): choosing the domain name

2022-05-24 Thread Geoff Clare via austin-group-l at The Open Group
Bruno Haible wrote, on 12 May 2022: > > https://posix.rhansen.org/p/gettext_draft > Line 50 > "often named after the application that provides the collection" > > Issue: On my system, in /usr/share/locale/de/LC_MESSAGES/ there are > 55 .mo files for libraries. > > Suggestion: Change > "after the

Re: POSIX gettext(): behaviour if iconv() produces a replacement character

2022-05-24 Thread Geoff Clare via austin-group-l at The Open Group
Bruno Haible wrote, on 12 May 2022: > > https://posix.rhansen.org/p/gettext_draft > Line 350 > > "If a significant proportion of the converted message string would consist > of characters resulting from non-identical conversions ..." > > The term "significant proportion" is undefined. > >

Re: POSIX bind_textdomain_codeset(): some invalid codeset arguments

2022-05-24 Thread Geoff Clare via austin-group-l at The Open Group
Bruno Haible wrote, on 12 May 2022: > > https://posix.rhansen.org/p/gettext_draft > Line 573 > > "The application shall ensure that the codeset argument, if non-empty, is a > valid codeset name that can be used as the tocode argument of the > iconv_open() > function." > > This is not the only

Re: POSIX gettext with option -s: handling of \c escape sequence

2022-05-24 Thread Geoff Clare via austin-group-l at The Open Group
Bruno Haible wrote, on 12 May 2022: > > https://posix.rhansen.org/p/gettext_draft > Lines 699, 721 > > "if the -n option is not specified, a shall be written after the > last message string" > "(if -n is not also specified) append a to the output." > > This is NOT entirely how the gettext

Re: POSIX gettext(): multithread-safe or not?

2022-05-24 Thread Geoff Clare via austin-group-l at The Open Group
Bruno Haible wrote, on 12 May 2022: > > https://posix.rhansen.org/p/gettext_draft > Line 357 > > "The returned string shall not be ... invalidated by a subsequent call > to a gettext family function." This was discussed in yesterday's call. > It is not clear whether this sentence is an