Sorry, hit Send early by accident.
It is not a matter of what I like or not, as that would mean adding something
way more flexible than gettext to the standard; it is if one implementation
choice, for technical reasons, can be seen as intrinsically more portable than
another that choice has
It is not a matter of what I like or not, as that would mean adding something
way more flexible than gettext to the standard, it is if one implementation
choice, for technical reasons, can be seen as intrinsically more portable than
another that choice has priority for standardization.
On 1/22/20 9:08 AM, Bruno Haible wrote:
Ulrich Drepper wrote:
Do you really like to require SunOS to loose backwads incompatiblity?
Overly dramatic. You just need one mode that is POSIX compatible. Many GNU
tools use POSIXLY_CORRECT_
The Solaris practice for keeping backward compatibility
On Wed, Jan 22, 2020 at 10:47 AM Joerg Schilling <
joerg.schill...@fokus.fraunhofer.de> wrote:
> Gettext is a SunOS invention and other implementations are expected to
> follow
> the definition from the reference implementation.
>
That implementation was the starting point but I didn't just copy
Jörg Schilling wrote:
> > It is well-known that the escape sequence expansion in 'echo' was different
> > in System V and BSD systems. You can assume that when Ulrich Drepper started
> > out writing GNU gettext in 1995, he did NOT want to copy the System V
> > behaviour
> > of 'echo' into the
Bruno Haible wrote:
> It is well-known that the escape sequence expansion in 'echo' was different
> in System V and BSD systems. You can assume that when Ulrich Drepper started
> out writing GNU gettext in 1995, he did NOT want to copy the System V
> behaviour
> of 'echo' into the 'gettext'
Joerg Schilling wrote:
> It is obvious that gettext(1) must expand escape sequences by default since
> this is the documented default behavior for both Solaris gettext(1) and GNU
> gettext(1) but in the default case, GNU gettext does not behave the way it is
> documented.
What you call the
Robert Elz wrote, on 22 Jan 2020:
>
> From:Geoff Clare
>
> | If we do add something, then I think that some non-normative words along
> | the lines of your explanation at the bottom ("to clarify that ...")
> | would be more helpful than the type of normative addition you are
>
Bruno Haible wrote:
> If that is your approach to standardization, then it is better to not
> standardize
> anything.
If your approach is to standardize obvious implementation bugs, I am a bit
bewildered.
I was in hope that you are interested in a fruitful discussion and open to
useful
Hi Bruno!
Bruno Haible wrote:
> Regarding the gettext(1) program and whether it expands escape sequences
> by default:
>
>
> 1) [1] is ambiguous / self-contradictory.
> On one hand it says:
>
> This utility interprets C escape sequences such as \t for tab. Use \\ to
> print a backslash...
Shware Systems wrote:
> This is not invention, as even Solaris allows you to turn it off with -s, as
> you point out. It may work fine for the charsets/charmap files Solaris
> historically provides to have escapes active as the default, but this does
> not equate to it being valid for all
11 matches
Mail list logo
