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

Bug#197469: marked as done (gcal figures out the starting day incorrectly)

Your message dated Sat, 28 Feb 2009 15:50:30 +0100 (CET)
with message-id <Pine.LNX.4.64.0902281541570.24673@tor.gallien.in-chemnitz.de>
and subject line Re: gcal figures out the starting day incorrectly
has caused the Debian Bug report #197469,
regarding gcal figures out the starting day incorrectly
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
197469: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=197469
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: gcal
Tags: upstream

Hi,

It appears that gcal honors the wrong locale settings when it comes to
deciding the starting day of the week.

% locale
LANG=hr_HR
LC_CTYPE="hr_HR"
LC_NUMERIC="hr_HR"
LC_TIME="hr_HR"
LC_COLLATE=C
LC_MONETARY="hr_HR"
LC_MESSAGES=en_US
LC_PAPER="hr_HR"
LC_NAME="hr_HR"
LC_ADDRESS="hr_HR"
LC_TELEPHONE="hr_HR"
LC_MEASUREMENT="hr_HR"
LC_IDENTIFICATION="hr_HR"
LC_ALL=

And with that, I still have to specify -s1 to have the weeks start on
Mondays, which is the standard for my locale.

Surely it should honor something like LC_NUMERIC or LC_TIME or even LANG
rather than LC_MESSAGES for the ordering issue?

(I've also tried it with LC_MESSAGES=hr_HR which made the weeks start on
Mondays, but then the display was completely rotated, which I thought was
entirely inappropriate.)

Please fix this. TIA.

-- 
     2. That which causes joy or happiness.

--- End Message ---
--- Begin Message --- As I got no objection against the arguments in my last email three weeks ago, I would like to declare this bug as an intentional feature and close it. 

Feel free to reopen if needed.

   Thorsten

--- End Message ---
Reply to: