Re: Support for LC_TIME

2014-05-12 Thread vtamara
El 2014-05-08 13:20, Marc Espie escribió: As for portability issues: programs stay with the C locale *in any case* unless they do setlocale() right at the start, in which case they explicitly say yes, I want to be localized. So, from that point of view the portability issues are minimal

Re: Support for LC_TIME

2014-05-12 Thread vtamara
Answering bad question I made (sorry): El 2014-05-12 05:55, vtamara escribió: (or what tables do you recommend me to use? are there tables in localedef format and BSD-license compatible available somewhere?) http://unicode.org/cldr/trac/browser/tags/release-1-9/posix/ However for the moment

Re: Support for LC_TIME

2014-05-12 Thread Stefan Sperling
On Mon, May 12, 2014 at 05:55:55AM -0400, vtamara wrote: I would like a little of clarification about something else that Stefan is talking about. In my dream world, I would like a locale implementation that follows the POSIX standard, supports multibyte characters throughout, avoids file

Re: Support for LC_TIME

2014-05-08 Thread Stefan Sperling
On Wed, May 07, 2014 at 07:44:51PM +0200, Ingo Schwarze wrote: While LC_CTYPE and LC_COLLATE make some sense, LC_MONETARY, LC_NUMERIC, and LC_TIME are badly overengineered, pointless bloat, causing nothing but surprising, erratic behaviour and portability problems when trying to parse output

Re: Support for LC_TIME

2014-05-08 Thread Marc Espie
On Thu, May 08, 2014 at 12:07:30PM +0200, Stefan Sperling wrote: On Wed, May 07, 2014 at 07:44:51PM +0200, Ingo Schwarze wrote: While LC_CTYPE and LC_COLLATE make some sense, LC_MONETARY, LC_NUMERIC, and LC_TIME are badly overengineered, pointless bloat, causing nothing but surprising,

Re: Support for LC_TIME

2014-05-08 Thread Ingo Schwarze
Hi, Marc Espie wrote on Thu, May 08, 2014 at 07:20:52PM +0200: On Thu, May 08, 2014 at 12:07:30PM +0200, Stefan Sperling wrote: On Wed, May 07, 2014 at 07:44:51PM +0200, Ingo Schwarze wrote: While LC_CTYPE and LC_COLLATE make some sense, LC_MONETARY, LC_NUMERIC, and LC_TIME are badly

Re: Support for LC_TIME

2014-05-07 Thread Ingo Schwarze
Hi, POSIX doesn't require support for any locales except POSIX and C. While LC_CTYPE and LC_COLLATE make some sense, LC_MONETARY, LC_NUMERIC, and LC_TIME are badly overengineered, pointless bloat, causing nothing but surprising, erratic behaviour and portability problems when trying to parse

Re: Support for LC_TIME

2014-05-07 Thread Antoine Jacoutot
On Wed, May 07, 2014 at 07:44:51PM +0200, Ingo Schwarze wrote: Hi, POSIX doesn't require support for any locales except POSIX and C. While LC_CTYPE and LC_COLLATE make some sense, LC_MONETARY, LC_NUMERIC, and LC_TIME are badly overengineered, pointless bloat, causing nothing but