[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Coordination on standardizing gettext() in future POSIX
From: |
Joerg Schilling |
Subject: |
Re: Coordination on standardizing gettext() in future POSIX |
Date: |
Wed, 22 Jan 2020 10:46:44 +0100 |
User-agent: |
Heirloom mailx 12.5 7/5/10 |
Shware Systems <address@hidden> 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 conforming charsets, if an application
> makes use of localedef, that I see. As such, from a portability standpoint, I
> view not processing escapes as the safer alternative.
What should be the reason for making the standard incompatible to the existing
practice since more than 30 years?
Gettext is a SunOS invention and other implementations are expected to follow
the definition from the reference implementation.
Do you really like to require SunOS to loose backwads incompatiblity?
Jörg
--
EMail:address@hidden (home) Jörg Schilling D-13353 Berlin
address@hidden (work) Blog: http://schily.blogspot.com/
URL: http://cdrecord.org/private/ http://sf.net/projects/schilytools/files/'
Re: Coordination on standardizing gettext() in future POSIX, Shware Systems, 2020/01/21
Re: Coordination on standardizing gettext() in future POSIX, Shware Systems, 2020/01/21
Re: Coordination on standardizing gettext() in future POSIX, Shware Systems, 2020/01/22
Re: Coordination on standardizing gettext() in future POSIX, Shware Systems, 2020/01/22