After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 368937 - Can not edit date field in locale zh_CN
Can not edit date field in locale zh_CN
Status: VERIFIED DUPLICATE of bug 437898
Product: GnuCash
Classification: Other
Component: User Interface General
2.0.x
Other Linux
: Normal normal
: ---
Assigned To: David Hampton
Chris Shoemaker
: 431895 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2006-11-01 16:48 UTC by Yajun Wang
Modified: 2018-06-29 21:14 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
screen shot of the transaction windows. (210.44 KB, image/png)
2006-11-02 05:26 UTC, Yajun Wang
Details
change the date format (147.76 KB, image/png)
2006-11-03 09:30 UTC, Yajun Wang
Details

Description Yajun Wang 2006-11-01 16:48:41 UTC
All transactions I input has the "current" date, which can not be changed.

I can not change previous transactions' date either.
Comment 1 Christian Stimming 2006-11-01 17:25:23 UTC
What distribution are you using? What language / locale are you using? Can you add a screenshot ("create a new attachment" below) showing the transaction window? Did this problem occur after you updated gnucash (from which version), or did it always occur?
Comment 2 Yajun Wang 2006-11-02 05:26:13 UTC
Created attachment 75815 [details]
screen shot of the transaction windows.

Whenever I changed one transaction, the date is changed to the current date. And all transaction I add now, will have the current date as the transaction date.

For the changing date windows, I can not click to the "<" and ">" on the window. Nothing clickable there.
Comment 3 Yajun Wang 2006-11-02 05:29:10 UTC
I am using Dapper 6.06, ubuntu. I compiled gnucash 2.0.0 && 2.0.2.

Both have the same problem in locale zh_CN.utf-8.

I export LANG=en_US solved this problem.

Thanks.

regards,
yalding
Comment 4 Christian Stimming 2006-11-02 09:40:17 UTC
Ok, thanks for the screenshot and explanation. We'll see whether we can reproduce this with the same locale. Did this work in earlier gnucash versions, and if yes, in which ones? 

Also, can you try whether the shortcut keys "+" and "-" work in the date field to increment and decrement the date?

Also, when you say "I can not click to the "<" and ">" on the window. Nothing clickable there.", do you really mean the arrows in that date window unexpectedly don't react like a button as they should?

As for your original problem, my guess was that you entered a date with a date separator character different from what gnucash expected (as defined by the locale) and then gnucash probably ignores the changed date as long as it cannot recognize the separator character. This means the bug depends on the locale and the date separator character from the locale. Anyway I agree that would be a bug.
Comment 5 Yajun Wang 2006-11-03 09:14:16 UTC
Easy workaround:

Change the date format in Reference.
Comment 6 Christian Stimming 2006-11-03 09:22:57 UTC
Thanks for reporting this workaround. Can you additionally tell us *how* you changed the date format in the preferences, i.e. which setting was it before, and to which setting did you change it? Thanks.
Comment 7 Yajun Wang 2006-11-03 09:30:59 UTC
Created attachment 75917 [details]
change the date format

Change the date format from "Locale" to "ISO" fix this problem
Comment 8 Christian Stimming 2007-01-29 10:04:16 UTC
Seems like this bug still exist, but since none of the current developers knows how to use chinese input methods, we cannot reproduce and hence fix it. :-(
Comment 9 Christian Stimming 2007-04-23 08:22:44 UTC
*** Bug 431895 has been marked as a duplicate of this bug. ***
Comment 10 Hector Akamine 2007-04-23 11:36:32 UTC
In my case, I have the same problem (after entering a value in the date
field the field content is restored to the current date. If I try to modify 
transactions from previous days, the date value is replaced with the current
date) when using a Japanese locale (LANG=ja_JP.UTF-8), it seems not to have relationship with the input method (because I didn't use the Japanese IME, just entered plain digits)

If I start gnucash from a terminal window, I have noticed the following message
appears each time I click in an account window (the same message twice each time)

   (gnucash:3654): Pango-WARNING **: Invalid UTF-8 string passed to pango_layout_set_text()


The workarounds to the problem: 
1) change the date format from "Locale" to "ISO" (Yajun's Comment #7))
OR 
2) start gnucash with an english locale  (e.g., start gnucash
 with "$ LANG=en gnucash")

If you need further information to solve the bug, please tell me.
Comment 11 Christian Stimming 2007-05-14 08:54:47 UTC
Maybe this has been fixed by bug#437898 in version 2.1.2? We would be glad to hear about this once 2.1.2 or higher has been released.
Comment 12 Andreas Köhler 2007-05-14 09:23:05 UTC
I think comment 11 is correct, marking as duplicate.
Please reopen if it is not fixed in GnuCash 2.1.2.

WRT the Pango-Warnings, these are probably due to the japanese translation.  I guess it has not really been updated for a while.


*** This bug has been marked as a duplicate of 437898 ***
Comment 13 Tomáš Trnka 2007-12-18 12:22:34 UTC
Probably needs to be reopened...
I am experiencing this bug using GnuCash 2.2.1 in the cs_CZ locale. Changing the date format from Locale (31.7.2005) to European (31.07.2005) works as expected. Without it every txn entered has the current date and additionally, the + and - keys move only to the next and previous day, not farther (however, after leaving the cell, the date is always today).
Previous version I've used (before a system upgrade, so I can't revert easily) was 2.0.5 and worked correctly. Seems strange, considering the original report is for 2.0.2...Maybe a lib issue?
Comment 14 John Ralls 2018-06-29 21:14:42 UTC
GnuCash bug tracking has moved to a new Bugzilla host. This bug has been copied to https://bugs.gnucash.org/show_bug.cgi?id=368937. Please update any external references or bookmarks.