http://bugs.winehq.org/show_bug.cgi?id=17721
Summary: RTG Bills reports dates incorrectly in bills for date formats (locals) not US Product: Wine Version: 1.1.15 Platform: Other OS/Version: other Status: UNCONFIRMED Severity: major Priority: P2 Component: -unknown AssignedTo: wine-bugs@winehq.org ReportedBy: mstuff@read.org.nz
This is a bit of a major that I'm unsure whether is a bug with RTG Bills or WINE... But, here's a workaround/fix for it below.
My local is New Zealand, my default language is LANG="en_NZ.UTF-8" with dates expressed "days / months / years" (like most of the world).
Setting the dates in RTG Bills to my format results in any dates in the form "days / months / years" that make sense expressed as "months / days / years" being expressed as "months / days / years". For instance: 10th March 2009 (10/3/09) is expressed on bills as 3rd October 2009 (3/10/09)!!!
A workaround/fix seems to be to set the environment variable $LANG to LANG="en_US.UTF-8" and then set the date format in RTG Bills to be expressed as "days / months / years". RTG Bills provides a "test" facility to check that date formats are sane for the system local settings, if this facility is used it will report that the format is "insane" and change it back to the "months / days / years" format. The answer is not to "test", but simply leave the format "untested" as "days / months / years" and save the setting. RTG Bills then seems to report dates correctly in its bills.
So, my command to execute RTG Bills is: env WINEPREFIX="/home/myhome/.Rtgbills" LANG="en_US.UTF-8" wine "C:\Program Files\Rtgbills\rtgbills.exe"
http://bugs.winehq.org/show_bug.cgi?id=17721
Vitaliy Margolen vitaliy@kievinfo.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Severity|major |normal
--- Comment #1 from Vitaliy Margolen vitaliy@kievinfo.com 2009-03-14 02:17:23 --- http://bugs.winehq.org/page.cgi?id=fields.html#bug_severity
http://bugs.winehq.org/show_bug.cgi?id=17721
--- Comment #2 from Austin English austinenglish@gmail.com 2009-09-15 15:39:45 --- Is this still an issue in current (1.1.29 or newer) wine?
http://bugs.winehq.org/show_bug.cgi?id=17721
--- Comment #3 from pseud mstuff@read.org.nz 2009-09-25 17:11:14 --- WINE 1.1.29 is a DISASTER and a regression!
See here: https://bugzilla.redhat.com/show_bug.cgi?id=522934
I've had to revert to: $ rpm -q wine wine-1.1.18-1.fc11.i586
And, wont be updating with out a lot of encouragement.
http://bugs.winehq.org/show_bug.cgi?id=17721
--- Comment #4 from Jeff Zaroyko jeffz@jeffz.name 2009-09-25 18:21:06 --- (In reply to comment #3)
Wine 1.1.29 is a DISASTER and a regression!
See here: https://bugzilla.redhat.com/show_bug.cgi?id=522934
I've had to revert to: $ rpm -q wine wine-1.1.18-1.fc11.i586
And, wont be updating with out a lot of encouragement.
Please test with 1.1.30, if it's still an issue file a new bug report including the results of your regression test http://wiki.winehq.org/RegressionTesting
http://bugs.winehq.org/show_bug.cgi?id=17721
--- Comment #5 from pseud mstuff@read.org.nz 2009-09-28 04:49:28 --- OK, I'll give it a go.
http://bugs.winehq.org/show_bug.cgi?id=17721
--- Comment #6 from Austin English austinenglish@gmail.com 2010-12-20 22:15:18 CST --- This is your friendly reminder that there has been no bug activity for a year. Is this still an issue in current (1.3.9 or newer) wine?
http://bugs.winehq.org/show_bug.cgi?id=17721
--- Comment #7 from butraxz@gmail.com 2013-06-09 11:18:13 CDT --- This has not been updated for over 900 days.
Is this still an issue in 1.6-rc1 or higher or is this abandoned ?
https://bugs.winehq.org/show_bug.cgi?id=17721
Austin English austinenglish@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |RESOLVED Resolution|--- |ABANDONED
--- Comment #8 from Austin English austinenglish@gmail.com --- Abandoned.
https://bugs.winehq.org/show_bug.cgi?id=17721
Austin English austinenglish@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |CLOSED
--- Comment #9 from Austin English austinenglish@gmail.com --- Closing.