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 priority for standardization. Backwards compatibility with non-portable behavior was only a priority for Issue 6, as was explained to me before V6TC1 came out, to simplify the merge effort of 1003.1 with SUSV5. So, for Issue 8, if this means the Solaris version loses out, so be it. On Wednesday, January 22, 2020 Joerg Schilling <joerg.schill...@fokus.fraunhofer.de> wrote: Shware Systems <shwares...@aol.com> 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:jo...@schily.net (home) Jörg Schilling D-13353 Berlin joerg.schill...@fokus.fraunhofer.de (work) Blog: http://schily.blogspot.com/ URL: http://cdrecord.org/private/ http://sf.net/projects/schilytools/files/'
