This is the mail archive of the libc-locales@sources.redhat.com mailing list for the GNU libc locales project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: How should the yesexpr noexpr regexp look?

From: Petter Reinholdtsen <pere at hungry dot com>
To: libc-locales at sources dot redhat dot com
Date: Fri, 3 Sep 2004 16:49:57 +0200
Subject: Re: How should the yesexpr noexpr regexp look?
Bcc: Petter Reinholdtsen <petter dot reinholdtsen at usit dot uio dot no>
References: <E1B2G9B-00064T-00@saruman.uio.no> <2flk6vcgsta.fsf@saruman.uio.no> <20040903092109.GB13089@rap.rap.dk> <413846B2.5040009@mystery.lviv.net> <20040903122041.GC13684@rap.rap.dk> <41386A94.305@mystery.lviv.net> <20040903144044.GM23724@saruman.uio.no> <20040903144548.GC14147@rap.rap.dk>

[Keld Jørn Simonsen]
> The TR 14652 i18n locale has 0 and 1 as defaults, so there is
> precedence for it.  POSIX/C locales are very altmodisch anyway.

Well, programmers code for POSIX and ANSI C, not for TR 14652, and
would be surprised if locales behave different than the POSIX/C
"locale", so I do not give Techinal Report 14652 much weight in this
issue.

It might be a good idea to try to modify the default POSIX/C locale,
but that is an entirely different road to take. :)

Follow-Ups:
- Re: How should the yesexpr noexpr regexp look?
  - From: Keld Jørn Simonsen

References:
- Re: How should the yesexpr noexpr regexp look?
  - From: Petter Reinholdtsen
- Re: How should the yesexpr noexpr regexp look?
  - From: Keld Jørn Simonsen
- Re: How should the yesexpr noexpr regexp look?
  - From: Volodymyr M. Lisivka
- Re: How should the yesexpr noexpr regexp look?
  - From: Petter Reinholdtsen
- Re: How should the yesexpr noexpr regexp look?
  - From: Keld Jørn Simonsen

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]