[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Coordination on standardizing gettext() in future POSIX

From: Shware Systems
Subject: Re: Coordination on standardizing gettext() in future POSIX
Date: Tue, 21 Jan 2020 18:53:54 +0000 (UTC)

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.

On Tuesday, January 21, 2020 Joerg Schilling <address@hidden> wrote:

Shware Systems <address@hidden> wrote:

> My two cents, I'm more in favor of requiring the -e ala GNU, as a byte stream that may be an escape for the charset of one locale may be plain text in another locale, especially when the encoding of the escape char itself differs. This can complicate editing data files when a pot file is a commented template for non-comment equivalences in po files, as an example workflow. Most editors I've used only permit one charset per file, so such a conflict would show in these. To avoid this I believe would require the standard placing more restrictions on charsets locales may use than now, to ensure portability, but this is not part of the proposal.

POSIX does not invent things but rather standardizes existing behavior and
Solaris behaves the same way since 30 years, while Linux does not follow it's
own definitions.

I am against changing the behavior.


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

reply via email to

[Prev in Thread] Current Thread [Next in Thread]