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 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

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

2022-05-11 Thread Bruno Haible via austin-group-l at The Open Group
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 program from GNU gettext behaves. Namely, it also looks