Changing the currency is not sufficient. You need to change how numbers are
printed. I'm not sure how to do that on your platform.
-derek
Sent using my mobile device. Please excuse any typos.
On December 13, 2017 1:44:52 PM Pam Dooner <pamdoo...@gmail.com> wrote:
Changing the locale seems only to affect new accounts. I have tried to ask
for GBP but nothing has changed.
Pam
*Pam Dooner*
On 13 December 2017 at 19:39, Derek Atkins <de...@ihtfp.com> wrote:
Yes, if you change your locale back to the old locale it should work again.
-derek
On Wed, December 13, 2017 1:34 pm, Pam Dooner wrote:
> Thank you for this explanation. If I change my locale to UK, will
> everything then be OK? Otherwise how do I change the SX definitions?
> Regards,
> Pam
>
>
> *Pam Dooner*
>
> On 13 December 2017 at 16:30, Derek Atkins <warl...@mit.edu> wrote:
>
>> Hi,
>>
>> Pam Dooner <pamdoo...@gmail.com> writes:
>>
>> > yes, definitely 2.6.18. Just tried again and this time managed to get
>> a
>> > pop-up saying "An error occurred while processing 0.99"
>> > I am trying to change all my decimal points to commas to coincide with
>> the
>> > euro locale that I have to use now it seems. In the older versions,
>> there
>> > was no issue with commas and points. I have UK accounts and european
>> > accounts so ought to be able to use both but this version (and the
>> previous
>> > one) seem to cause the error if I try to use a decimal point. So I'll
>> have
>> > to try to edit the file elsewhere and re-import it. I had hoped there
>> might
>> > have been a way of globally changing all previous entries with a
>> decimal
>> > point to commas. In the actual accounts, it has changed them all to
>> commas
>> > but not in scheduled transactions!
>> > Pam
>>
>> Scheduled Transactions do not survive a locale change, specifically a
>> change where the decimal separator changes characters. The reason is
>> that the SX data is stored as text, not as a numeric, so "99/100" gets
>> stored as 0.99 and then it expects to be parsed as 0.99 -- however if
>> you change your locale so that a comma is a decimal separator then
>> GnuCash expects to read back 0,99. But when it sees 0.99 it doesn't
>> know how to interpret that.
>>
>> The only fix is to change the SX definitions, or to change your locale
>> specification of (IIRC) LC_NUMERIC back to the old style.
>>
>> I don't know if there is a way change the character from within the
>> program.
>>
>> > *Pam Dooner*
>>
>> > Please remember to CC this list on all your replies.
>> > You can do this by using Reply-To-List or Reply-All.
>>
>> -derek
>> --
>> Derek Atkins, SB '93 MIT EE, SM '95 MIT Media Laboratory
>> Member, MIT Student Information Processing Board (SIPB)
>> URL: http://web.mit.edu/warlord/ PP-ASEL-IA N1NWH
>> warl...@mit.edu PGP key available
>>
>
--
Derek Atkins 617-623-3745
de...@ihtfp.com www.ihtfp.com
Computer and Internet Security Consultant
_______________________________________________
gnucash-user mailing list
gnucash-user@gnucash.org
https://lists.gnucash.org/mailman/listinfo/gnucash-user
-----
Please remember to CC this list on all your replies.
You can do this by using Reply-To-List or Reply-All.