Unix Shell - Re: localization patch 119408-07

This is Interesting: Free IT Magazines  
Home > Archive > Unix Shell > February 2007 > Re: localization patch 119408-07





You are viewing an archived Text-only version of the thread. To view this thread in it's original format and/or if you want to reply to this thread please [click here]

Author Re: localization patch 119408-07
Vitaly Filatov

2007-02-20, 7:18 am

Stephane CHAZELAS wrote:
> 2007-02-19, 01:12(+00), <PeterSans@not.sonic.net>
> I don't follow you. POSIX aims at aiding portability.
>
> POSIX doesn't forbid date output to be the same in Russian or US
> english locales. However it clearly defines what the output
> should be in the POSIX or C locale.
>
> So, it's not making "date" conformant that broke the OP's script
> it's making "date" localized that did it.
>
> The OP's script was wrong to assume he could rely on date output
> in non-POSIX locales, not because POSIX makes sure the output is
> not what he expects in non-POSIX locales, but because there's
> nothing (neither POSIX nor common sense) that guarantees the
> output format in non-standard locales.
>
> On the contrary, thanks to POSIX, he can now be assured that as
> long as he forces the locale to be POSIX, the date output format
> will be consistent from system to system.
>
> LC_ALL=C date +%b
>
> will return "Feb" (or whatever the month is in the user's
> timezone) whatever the system (as long as you're in a POSIX
> environement on that POSIX compliant system).
>
> And
>
> LC_ALL=C date -u +%b
>
> will return the month in the universal time zone.
>
> Without POSIX, how would you want to guarantee anything?
>

Thank you!

I do it in the same manner, when I'm writing my skripts.

But I wanted to say that after this patch some X-programs obtain wrong
behavior.

Vitaly Filatov
Sponsored Links






Free braindumps | Software forum | Database administration forum

Copyright 2003 - 2009 webservertalk.com