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 > > 0000000 a b > > 0000002 > > > > Whereas on Solaris, \c is not interpreted: > > > > $ gettext -s -e 'ab\c' | od -t c > > 0000000 a b c \n > > 0000004 > > > > How to resolve this? > > In today's call we made changes to allow this handling of \c (using "may", > so it is an implementation option). Please check the updated etherpad to > see if the way it is described there matches how GNU gettext behaves.
The updated text is good. GNU gettext will need a small change, in order to accommodate the specified behaviour for the characters that follow '\c', but that is OK since it is rare for users to add more characters after '\c'. Bruno
